Help coderanch get a
new server
by contributing to the fundraiser
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Book Promo: Java SOA without Java EE 5?

 
Bartender
Posts: 2968
6
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Your book SOA Using Java� Web Services (Sample Chapter: Basic SOA Using REST, amazon US) seems to cover SOA in both the Java SE 6 and Java EE 5 environments. Does it focus mainly on SOA in a Java EE 5 environment or does it seriously consider the alternative of implementing SOA in a Java SE 6 only environment � considering the bells of doom for Java EE (Analysts see Java EE dying in an SOA world)?
[ May 29, 2007: Message edited by: Peer Reynders ]
 
author
Posts: 61
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Almost everything in the book, and most of the code examples, applies to Java SE 6 as well as Java EE 5. That is because Java SE 6 includes JAX-WS and JAXB.

Besides JAX-WS and JAXB, the code examples from the book use JSR-181 (Web Services Metadata) for annotations. The only Java EE 5 specific technology used in the book is related to JSR-109 which specifies Java EE 5 deployment standards.

So, any platform that supports JAX-WS, JAXB, and JSR-181 can be used to implement the code examples and techniques described in the book. This includes platforms (with the appropriate plug-ins to provide JAX-WS, JAXB, and JSR-181):
* Tomcat
* Spring
* XFire
* Apache CXF
* etc.

The only caveat here is that each platform is slightly different with respect to deployment, so you might need to tweak the example to deploy in each of these.

On my blog, there has been discussion about porting the example code to Tomcat. Please post a comment there if you have ideas/suggestions.

Having said all that, I would strongly disagree that Java EE is "dying". The major app server vendors are bringing out support for Java EE 5. BEA is already there with WebLogic Server 10. JBoss AS 5.0 will be Java EE 5 certified and is available in beta now. And, of course, GlassFish has been hugely successful as the first Java EE 5 certified application server. It has been out for over a year.

The real problem with Java EE is that it has been so successful that it is getting to be too big for a lot of people. Java EE 6 will address that by allowing vendors to provide distributions for specific markets. This will allow vendors, for example, to provide a "Web Profile" version of Java EE 6 - just targeting Web development - and including only the features needed for that market.
 
Peer Reynders
Bartender
Posts: 2968
6
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I'm sure that Java EE�s future will be along the lines of Mark Twain's famous quote:


The reports of my death are greatly exaggerated.


even though there still seem to be some "growing pains" with the Java EE profiles as you have already mentioned on your blog.

Once again thank You for Your most detailed response.

Peer
 
rubbery bacon. crispy tiny ad:
We need your help - Coderanch server fundraiser
https://coderanch.com/t/782867/Coderanch-server-fundraiser
reply
    Bookmark Topic Watch Topic
  • New Topic