Java Web Services and XML
Business processes are made up of automated and human-performed tasks, and we need to be able to implement both types of tasks in a manner that allows them to be consumed by a multitude of applications. That's what SOA was really all about in the first place.
The JAXB RI has just posted two releases --- one is 2.0.4, a stable bug fix release to the 2.0.x line, and the other is 2.1 EA2 which implements the proposed 2.1 features.
The JAX-WS 2.1 Maintenance Review has started and will complete on November 27, 2006.
The following is a techtip I wrote which wasn't used. Since I turned out pretty well I thought I'd post it here. Let me know what you think. Would you like more of these small self-contained tips?
A Quick Introduction to HttpClient
Java is great because it has classes for almost everything. For example, if you want to open a webpage you can do it with the java.net.URL class. But what if you...
I posted a new version of Hudson, 1.59, today. Hudson is an extensible continuous integration engine.
Another Web services stack comparison at JBoss
wiki and GlassFish is looking
really good. Read more details about the feature support here.
For the past few months I've been working with a very polished Business Process Management (BPM) suite from Lombardi Software , and I have to say that I am as happy as a clam. I feel like I have discovered a tool that I've been missing for at least 20 years, maybe longer, and I'm delighted.
As I mentioned earlier,
running a marathon is all about community. So I decided to show my support for GlassFish
community by hand painting my running shirt on the day before marathon. My
dad helped me trace it and then I painted it. Learn
more about GlassFish and it's community. Get
Involved and participate in the Roadmap
Now that I took over JAXB 2.1 maintenance review spec work, a part of my job involves in updating a PDF document, that is the JAXB specification. But this is just so painful, thanks to FrameMaker.
I've been asked this question multiple times and so finally decided to
convert an internal presentation that into an external document.
WS-Addressing ? describes the different use cases served by WS-Addressing
and explains the two commonly used versions.
JAX-WS 2.1 RI
EA2 was recently released and supports W3C and Member Submission
WS-Addressing. A more recent version of this RI is integrated...
JAXB 2.1 maintenance draft review has just started. It's a 30-day review period to solicit broader feedback on the 2.1 MR. If things go well, after the review ends, we'll be able to release 2.1. So that puts up somewhere December 06 or January 07.
One of the additions in the JAX-WS RI EA2 is the support of stateful web services by using WS-Addressing underneath.
JAX-WS 2.1 EA2, with new features and better quality, is out. Read Vivek's
message about the announcement
and the list of features.
I'd like to highlight Users
Guide that has been updated with an explanation for all the newly added
features. I added a new section on WS-Addressing
support in the RI. Rama
published a blog on Support
for WS-Addressing in JAX-WS 2.1 RI EA1 4 weeks ago. Based upon...
JAX-WS 2.1 RI replaced JAX-WS
2.0.1 and JAX-WSA 1.0 EA2 in WSIT
approximately 2 weeks ago. This is where I've been spending most of my time during
the past few weeks. With this change, WSIT is now using WS-Addressing
functionality natively provided in JAX-WS 2.1 RI is used instead of relying upon
a pluggable JAX-WSA 1.0 EA2. This approach has several benefits as outlined earlier.
Jorgen's interview on The
Server Side about how the Interop plugfests at Microsoft are arranged. There is
full section talking about WSIT and WCF interoperability towards the end of the
interview. As mentioned in my previous plugfest reports (1,
have incrementally achieved a very good level of interoperability with
Microsoft. And this is also evident (Green and Yellow is good) in...
A JMS transport project for JAX-WS 2.1 has been added as a subproject of JAX-WS (http://jax-ws.dev.java.net).
Traditionally JAX-WS has never taken advantage of object state, just like servlet. That is, the container creates only one instance of your service class, and then have it serve all the requests concurrently. This makes it impossible to set values to instance fields, as you'll experience concurrency problem as soon as multiple threads hit your service.
So all too often the service code starts...
I just posted a new version of the JAXB RI 2.0.x line. This RI implements JAXB API 2.0, and is a bug fix release.
I started posting the JAXB 2.1 snapshot jars to the maven repository.
Juraj Vitko sent me his JAXB plugin that allows you to manually put additional code to the JAXB generated classes, and yet have XJC preserve them when you regenerate source files.