|
|
||
Changshin Lee's BlogApril 2006 ArchivesJAXB 2.0 TCKPosted by iasandcb on April 18, 2006 at 10:43 PM | Permalink | Comments (1)You can download it from https://jaxb.dev.java.net/tck.html . It's still beta, but I hope we can see a final version as JAXB 2.0 spec and RI is also finalized (very soon). Terms in JWS 2.0 - PAWSDL vs PUWSDL and GISC vs GASCPosted by iasandcb on April 14, 2006 at 12:26 AM | Permalink | Comments (0)EWS 1.2 introduces two types of WSDL: PAckaged WSDL - PAWSDL (paw sdle): WSDL files packaged in a module. While JAX-RPC uses interface (java.xml.rpc.Service) for clients, JAX-WS uses class: Let's talk about JWS with some efficiency :-) 4 cases in packaing web service endpoints in Java EE 5Posted by iasandcb on April 13, 2006 at 10:54 PM | Permalink | Comments (0)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 2. No web.xml but webservices.xml 3. Partial web.xml and webservices.xml 4. Full web.xml and webservices.xml JWS ME 2.0Posted by iasandcb on April 13, 2006 at 03:00 AM | Permalink | Comments (0)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
JSR 279 Service Connection API for Java ME Eclipse 3.2M6, WTP 1.5M5, and CallistoPosted by iasandcb on April 02, 2006 at 09:47 PM | Permalink | Comments (6)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. When it comes to "simultaneity", Eclipse Callisto project may interest you. As a matter of fact, getting a right set for your overall purpose, for example, Java EE development, in Eclipse was quite tricky because there have been infra and component projects with different release plans in the Eclipse ecosystem. Callisto came up to solve the difficulty and already shows some sign for "good to go." June this year would be great for Eclipse users :-) | ||
|
|