EWS 1.2 introduces two types of WSDL:
PAckaged WSDL - PAWSDL (paw sdle): WSDL files packaged in a module.
PUblished WSDL - PUWSDL (poo sdle): WSDL files published during deployment.
While JAX-RPC uses interface (java.xml.rpc.Service) for clients, JAX-WS uses class:
GenerIc Service Class - GISC (g sc): javax.xml.ws.Service
GenerAted Service Class - GASC (gas c): generated service classes extend
Web services in Java EE 5, or JWS 2.0 changes a lot in packaging endpoints. There are 3 types in a web module:
1. Neither web.xml nor webservices.xml
In this case, full annotations are required.
2. No web.xml but webservices.xml
Annotations can be overriden by webservices.xml as defined by EWS (JSR 109) 1.2.
While I introduced the term JWS (Java Web Services) 2.0, I realized that the same notion can be applied to Java ME, i.e. JWS ME 2.0:
JWS ME 1.0
JSR 172 J2ME Web Services
JWS ME 2.0
JSR 279 Service Connection API for Java ME
JSR 280 XML API for Java ME
Eclipse 3.2M6 was out and is almost ready for the final. Eclipse 3.2 supports Java SE 5 as well as Java SE 6.
Eclipse Web Tools project also unveiled WTP 1.5M5, which is aimed at Java EE 5 with Dali, EJB 3 support and JSF. Once Eclipse 3.2 and WTP 1.5 cut the final simultaneously, you will be able to enjoy developing Java EE 5 applications on top of the full Eclipse support.
While I was working on preparing slides for my session on TmaxDay 2006 (http://www.tmax.co.kr/tmaxday/), I came up with some idea of grouping and classifying Java web services technologies:
Java Web Services 1.0 (adopted by J2EE 1.4)
(Optional) EWS (JSR 109) 1.1
Java Web Services 2.0 (adopted by Java EE 5 and Java SE 6)
JAXP 1.3 + StAX 1.0 (= JAXP 1.4)
I just posted a snapshot of Apache Mirae 1.0 to http://people.apache.org/~ias/mirae/ . "Mirae" in Korean means "future" and I used the word to name a project for implementing JSR 172 J2ME Web Services in Apache.
The project launched two years ago, but has gone through many things: lack of participation (and use as well), TCK delivery, and holes of JSR 172, and so on.
FreeBSD Java is based on Intel, so it might be possible to apply it to port Mustang for Darwin, the underlying OS layer of Mac OS X on Intel Macs. One more feasible idea about the porting is making a headless version of Mustang for Intel Macs, i.e. core Java without graphic facilities such as AWT, Swing, and Java 2D.
Or, we can just wait for Leopard (Mac OS X 10.5) to come up with Mustang :-)
As I'm going to deliver some presentation on widgets such as Yahoo!
Downloads are available at http://download.eclipse.org/eclipse/downloads/drops/S-3.2M5-200602171115... . This milestone is the final for API changes, and some time will be spent for feature finalization and functional stabilization. I enjoy Eclipse 3.2M5 with WTP 1.5M4 in developing JEUS because: