There could be some other winners but I have a hard time mapping java.net ids to real names, so sorry if I missed you. ]]> 2008-08-30T00:20:57Z 2008-08-30T00:20:46Z tag:weblogs.java.net,2008:/blog/jitu/300.10368 2008-08-30T00:20:46Z

@WebService
@UsesJAXBContext(ServerJAXBContextFactory.class)
public class EchoImpl {
    ...
}

public class ServerJAXBContextFactory implements JAXBContextFactory {
    public JAXBRIContext createJAXBContext(...) throws JAXBException {
    ...
    }
}

Looked at IBM's JDK in recent WebSphere Application Server v7.0 (Open Beta) release. This version is supposed to be based on Java EE 5 and Java SE 6. Since I am a JAX-WS RI/Metro guy, wanted to see what implementation it is using. So just tried wsimport:

$ ./wsimport -version
JAX-WS RI IBM 2.1.1 in JDK 6

There you go, it uses JAX-WS RI. It has pretty much the same web services bits(JAXB, SAAJ etc) as Sun's Java SE 6. But it uses different StAX impl, not SJSXP. Note that Metro bits are tested with woodstox, sjsxp parsers. Now it works with IBM's StAX impl.

As far as JAX-WS implementation goes, it has all the RI extensions like FastInfoset, AsyncProvider etc.

JAX-WS RI/Metro is part of many application servers, JDKs, frameworks etc. We must have done a good job :-) ]]> 2008-07-28T19:15:59Z 2008-07-28T19:15:47Z tag:weblogs.java.net,2008:/blog/jitu/300.10186 2008-07-28T19:15:47Z

It has two features:

• Simplified "Starting from Java" development model
• See dual_binding sample to enable a same service for XML/HTTP and SOAP/HTTP. We need to do some more work in this area.

Lot of bug fixes:

• 2.1.4 bug fixes

The bits are also pushed to the JAX-WS Maven repository.

Metro 1.2 has woodstox as the default StAX parser. If you are using MTOM, you will run into this bug. The workaround is to put sjsxp.jar first in the classpath or use system properties to enable sjsxp StAX parser.

Continue sending your feedback to the forum and to the mailing list. ]]> 2008-03-06T03:06:20Z 2008-03-06T03:06:13Z tag:weblogs.java.net,2008:/blog/jitu/300.9319 2008-03-06T03:06:13Z

package pkg;

import javax.jws.WebService;
import javax.jws.WebMethod;
import javax.xml.ws.Endpoint;

@WebService
public class AddService {
    @WebMethod(exclude=true)
    public static void main(String ... args) throws Exception {
        Endpoint.publish("http://localhost:8181/add", new AddService());
        ...
    }

    public int add(int num1, int num2) {
        return num1+num2;
    }
}

$ javac pkg/AddService.java
$ wsgen.sh -d gen -keep -cp . pkg.AddService
$ ls gen/pkg/jaxws
Add.class AddResponse.class

So far with JAX-WS RI, you need to run wsgen for doc/lit wrapper case or when service throws any checked exceptions. wsgen generates request/response wrapper bean classes and exception bean classes. JAX-WS spec clearly defined rules to create these portable classes, so that the same application works on different JAX-WS implementations. But all the required information to generate these classes can be got from the SEI, so an implementation may generate these classes on the fly. From JAX-WS RI 2.1.4 onwards, you don't have to run wsgen, the runtime takes care of it by generating these classes dynamically. That's right, you don't have to run "wsgen" ! See the sample logging output, when there are no wrapper classes in the classpath:

$ javac pkg/AddService.java
$java pkg.AddService

INFO: Dynamically creating request wrapper Class pkg.jaxws.Add
Mar 3, 2008 1:58:30 PM com.sun.xml.ws.model.WrapperBeanGenerator createBeanImage
INFO: 
@XmlRootElement(name=add, namespace=http://pkg/)
@XmlType(name=add, namespace=http://pkg/, propOrder={arg0, arg1})
public class pkg.jaxws.Add {

    @XmlRootElement(name=arg0, namespace=)
    public I arg0

    @XmlRootElement(name=arg1, namespace=)
    public I arg1

}

INFO: Dynamically creating response wrapper bean Class pkg.jaxws.AddResponse
Mar 3, 2008 1:58:30 PM com.sun.xml.ws.model.WrapperBeanGenerator createBeanImage
INFO: 
@XmlRootElement(name=addResponse, namespace=http://pkg/)
@XmlType(name=addResponse, namespace=http://pkg/)
public class pkg.jaxws.AddResponse {

    @XmlRootElement(name=return, namespace=)
    public I _return

}

I would say starting from java, building services have never been so easy :-) Let me know your feedback, you need to try the 2.1.x nightlies for this feature. ]]> 2008-06-24T19:17:03Z 2007-10-12T23:54:41Z tag:weblogs.java.net,2007:/blog/jitu/300.8424 2007-10-12T23:54:41Z

for e.g.:
public void parse() {
    MIMEParser parser = new MIMEParser(InputStream, boundary, ...);
    Iterator<MIMEEvent> it = parser.iterator();
    while(it.hasNext()) {
        MIMEEvent event = it.next();
        switch(event.getEventType()) {
            case START_MESSAGE :
            case START_PART :
            case HEADERS :
            case CONTENT :	// called multiple times for a attachment
            case END_PART :
            case END_MESSAGE :
       }
    }
 }

// Parts are accessed in order. The data is accessed in a streaming fashion
// using readOnce() and data is not stored in temp files.
public void parse() {
    InputStream in = ...
    String boundary = ...
    MIMEConfig config = ...
    MIMEMessage mm = new MIMEMessage(in, boundary, config);

    MIMEPart partA = mm.getPart("partA");
    InputStream ais = partA.readOnce();
    // read ais

    MIMEPart partB = mm.getPart("partB");
    InputStream bis = partB.readOnce();
    // read bis

} 

See Tomcat documentation on how to configure compression. I configured Tomcat as follows:

  <Connector port="8080" 
    ...
    compression="on"
    compressionMinSize="20"
    compressableMimeType="text/xml"
  />

Similarly, see JeanFrancois's blog on how to configure GlassFish for compression. I configured GlassFish domain as follows:

  <http-listener port="8080" ...  >
    ...
    <property name="compression" value="on"/>
    <property name="compressionMinSize" value="20"/>
    <property name="compressableMimeType" value="text/xml"/>
  </http-listener>

---[HTTP request]---
Accept-Encoding: gzip
SOAPAction: "urn:test:hello"
Content-Type: text/xml;charset="utf-8"
Accept: text/xml, multipart/related, text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
<S:Envelope ... </S:Envelope>
---[HTTP response 200]---
Date: Tue, 03 Jul 2007 19:04:19 GMT
Content-encoding: gzip
Content-type: text/xml;charset=utf-8
null: HTTP/1.1 200 OK
Transfer-encoding: chunked
Server: Apache-Coyote/1.1
Vary: Accept-Encoding
[GZIP Compressed SOAP Envelope]

The way to add Accept-Encoding HTTP header is as follows:

stub = ...
Map<String, List<String>> httpHeaders = new HashMap<String, List<String>>();
httpHeaders.put("Accept-Encoding", Collections.singletonList("gzip"));
Map<String, Object> ctxt = ((BindingProvider)stub).getRequestContext();
ctxt.put(MessageContext.HTTP_REQUEST_HEADERS, httpHeaders);

httpHeaders.put("Content-Encoding", Collections.singletonList("gzip"));

wsimport -p com.google.api.adsense.v2 -d gen https://www.google.com/api/adsense/v2/AccountService?wsdl

ObjectFactory fact = new ObjectFactory();
((WSBindingProvider)accountService).setOutboundHeaders(
    fact.createDeveloperEmail(developerEmail),
    fact.createDeveloperPassword(developerPassword),
    fact.createClientId("ignored"));

"New core Web services technologies have been implemented including the Java API for XML Web Services (JAX-WS 2.0) and Java API for XML Binding (JAXB 2.0). BEA implements JAX-WS 2.0 based on the GlassFish community project (another blended example), which provides a solid implementation supported by the Java community."

JAX-WS RI is going places. Many application servers, tool kits and frameworks are including RI's implementation of JAX-WS 2.0 based on its quality, performance and extensibility. I wonder what all Pipe/Tubes are there in WebLogic to provide more functionality.]]> 2008-06-24T19:17:03Z 2007-02-10T01:44:35Z tag:weblogs.java.net,2007:/blog/jitu/300.6523 2007-02-10T01:44:35Z

@WebService
public class DataService {
    Connection con;

    public synchronized void delete() {
        Statement stmt = con.createStatement();
        stmt.executeQuery();
    }

    public synchronized void add() {
        Statement stmt = con.createStatement();
        stmt.executeQuery();
    }
}

import org.jvnet.jax_ws_commons.thread_scope.ThreadScope;

@WebService
@ThreadScope
public class DataService {
    Connection con;

    public void delete() {
        Statement stmt = con.createStatement();
        stmt.executeQuery();
    }

    public void add() {
        Statement stmt = con.createStatement();
        stmt.executeQuery();
    }
}