Please, can we stop the product plugging on this list? It's getting
rather pathetic.

Thanks,

Arjen

On 14-feb-2007, at 13:28, Davanum Srinivas wrote:

> Paul,
>
> Use AXIOM, See even the REST guys are using it :)
> http://blog.chanezon.com/articles/2006/05/31/apache-abdera-and-rome-
> alea-jacta-est
>

Paul,

Use AXIOM, See even the REST guys are using it :)
http://blog.chanezon.com/articles/2006/05/31/apache-abdera-and-rome-alea-jacta-e\
st

Just look at the performance numbers for processing a huge feed that
they posted. Yes, adding soap headers won't slow us (Axis2) down :)

thanks,
dims

On 2/14/07, Paul Downey <paul.downey@...> wrote:
>
> On 13 Feb 2007, at 21:25, Davanum Srinivas wrote:
>
>
> > Sure. Just press the off button :)
>
> >
> thread killed :)
>
>
> > Did you see this already?
> >
> > http://www.bloglines.com/blog/sanjiva?id=180
>
>
> Ah, so we learnt earlier how SOAP headers
> aren't the 80 case, and now should just use
> just use XML because databinding is evil.
>
> I wonder where the baby is now we've tossed out
> the SOAP bath water.
>
> Paul
> --
> http://blog.whatfettle.com
>
>
>
> -----------------------------------------------------------------
> This group is a forum for builders of SOAP implementations to discuss
implementation and interoperability issues.  Please stay on-topic.
> Yahoo! Groups Links
>
>
>
>


--
Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers

On 13 Feb 2007, at 21:25, Davanum Srinivas wrote:


> Sure. Just press the off button :)

>
thread killed :)


> Did you see this already?
>
> http://www.bloglines.com/blog/sanjiva?id=180


Ah, so we learnt earlier how SOAP headers
aren't the 80 case, and now should just use
just use XML because databinding is evil.

I wonder where the baby is now we've tossed out
the SOAP bath water.

Paul
--
http://blog.whatfettle.com

Sure. Just press the off button :) Did you see this already?

http://www.bloglines.com/blog/sanjiva?id=180

-- dims

On 2/13/07, Paul Downey <paul.downey@...> wrote:
> > That's why i am very interested in seeing the relative performances of
> > the two data bindings under JDK6 using woodstox running under tomcat.
> > (Since kohsuke hinted at possible problem in GlassFish and we prefer
> > woodstox, since we haven't spent any time with SJSXP).
>
> I'm quite frankly bored by this performance peeing contest:
>
> 1) Make it run.
> 2) make it right.
> 3) make it fast.
>
> Axis2, XFire, Glassfish, etc all need to try harder at (2).
>
> Paul
> --
> http://blog.whatfettle.com
>
>
>
>
> -----------------------------------------------------------------
> This group is a forum for builders of SOAP implementations to discuss
implementation and interoperability issues.  Please stay on-topic.
> Yahoo! Groups Links
>
>
>
>


--
Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers

> That's why i am very interested in seeing the relative performances of
> the two data bindings under JDK6 using woodstox running under tomcat.
> (Since kohsuke hinted at possible problem in GlassFish and we prefer
> woodstox, since we haven't spent any time with SJSXP).

I'm quite frankly bored by this performance peeing contest:

1) Make it run.
2) make it right.
3) make it fast.

Axis2, XFire, Glassfish, etc all need to try harder at (2).

Paul
--
http://blog.whatfettle.com

Got it!. Yes, i was just paraphrasing your email to me. fully
expecting you to chime in if i said something wrong :)

-- dims

On 2/13/07, Dennis Sosnoski <dms@...> wrote:
> Davanum Srinivas wrote:
> >
> > ... JIBX and ADB take very similar
> > approach. In JIBX's case, bytecode is generated that uses xpp3 and
> > populates the fields and in ADB we generate Stax/AXIOM based code to
> > the same and then compile it. So JIBX and ADB is very comparable.
> >
>
> JiBX bytecode generation is not in any way tied to XPP3 - it implements
> its own abstraction layer for both parsers and output mechanisms, and
> supports both XPP3 and StAX parsers (not difficult, since the useful
> parts of StAX were largely based on XPP3). That point aside, I agree
> that JiBX and ADB take very similar approaches so I'd expect them to
> have about equal performance when used in the Axis2 environment. In
> fact, I think I remember mentioning this to you before your last
> benchmark results... :-)
>
>   - Dennis
>
>
> -----------------------------------------------------------------
> This group is a forum for builders of SOAP implementations to discuss
implementation and interoperability issues.  Please stay on-topic.
> Yahoo! Groups Links
>
>
>
>


--
Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers

Davanum Srinivas wrote:
>
> ... JIBX and ADB take very similar
> approach. In JIBX's case, bytecode is generated that uses xpp3 and
> populates the fields and in ADB we generate Stax/AXIOM based code to
> the same and then compile it. So JIBX and ADB is very comparable.
>

JiBX bytecode generation is not in any way tied to XPP3 - it implements
its own abstraction layer for both parsers and output mechanisms, and
supports both XPP3 and StAX parsers (not difficult, since the useful
parts of StAX were largely based on XPP3). That point aside, I agree
that JiBX and ADB take very similar approaches so I'd expect them to
have about equal performance when used in the Axis2 environment. In
fact, I think I remember mentioning this to you before your last
benchmark results... :-)

   - Dennis

Thanks Dims.

Davanum Srinivas wrote:
>
> I guess, you were asking me to respond to it :) Dan sums it up nicely:
>
> "However that will be quite tricky to achieve because now the limiting
> factor in web service performance is probably not XFire or Axis2, its
> going to be your XML parser, HTTP provider, and/or your data-binding
> implementation."
>
> That's a total turn around from original assertions of the XFire team
> both on-record and off-the-record about Axis2 vs XFire. So that's good
> news :)
>
> Better news is now it's ADB vs JAXB2. Looking at profiler outputs i
> can say that the reflection based stuff in JAXB2 slows things down
> especially for huge data sets. JIBX and ADB take very similar
> approach. In JIBX's case, bytecode is generated that uses xpp3 and
> populates the fields and in ADB we generate Stax/AXIOM based code to
> the same and then compile it. So JIBX and ADB is very comparable.
> FWIW, you guys have the upper hand as you can speed up reflection in
> the JVM/JDK itself, which you did as per comments i saw from one of
> the team members (in JDK6).
>
> That's why i am very interested in seeing the relative performances of
> the two data bindings under JDK6 using woodstox running under tomcat.
> (Since kohsuke hinted at possible problem in GlassFish and we prefer
> woodstox, since we haven't spent any time with SJSXP).
>
> thanks,
> dims
>
> On 2/12/07, Davanum Srinivas <davanum@...
> <mailto:davanum%40gmail.com>> wrote:
> > Yep. We did.
> >
> > thanks,
> > dims
> >
> > On 2/12/07, Doug Kohlert <doug.kohlert@...
> <mailto:doug.kohlert%40sun.com>> wrote:
> > > Dims,
> > > I just found an interesting blog questioning the Axis2 benchmarks
> > > (http://netzooid.com/blog/2007/02/08/dodgy-benchmarks-indeed/
> <http://netzooid.com/blog/2007/02/08/dodgy-benchmarks-indeed/>), have you
> > > seen it?
> > >
> > > Davanum Srinivas wrote:
> > > >
> > > > Doug,
> > > >
> > > > There is no mention of apples-to-apples comparison on kohsuke's
> blog.
> > > > There is no mention of XMLBeans in vivek's blog. This is the first
> > > > time i hear this new argument that Axis2/XmlBeans is a
> > > > apples-to-apples comparison....
> > > >
> > > > If you really wanted to test the perf, you should compare multiple
> > > > options including the default settings for both stacks :) In this
> > > > case, it would mean Axis2/JAXB, Axis2/ADB, JAXWS-RI/JAXB. Running
> > > > Axis2/XMLBeans and claiming huge perf improvements is ridiculous as
> > > > dennis mentioned.
> > > >
> > > > -- dims
> > > >
> > > > On 2/8/07, Doug Kohlert <doug.kohlert@...
> <mailto:doug.kohlert%40sun.com>
> > > > <mailto:doug.kohlert%40sun.com>> wrote:
> > > > > Oh, you are talking about the data corruption mentioned in
> Kohsuke's
> > > > > blog
> > > > >
> > > >
> (http://weblogs.java.net/blog/kohsuke/archive/2007/02/jaxws_ri_21_ben.html
> <http://weblogs.java.net/blog/kohsuke/archive/2007/02/jaxws_ri_21_ben.html>
> > > >
> <http://weblogs.java.net/blog/kohsuke/archive/2007/02/jaxws_ri_21_ben.html
> <http://weblogs.java.net/blog/kohsuke/archive/2007/02/jaxws_ri_21_ben.html>>).
> > > > > Yea Dims, we made that up; get real dude. Kohsuke even
> mentioned in
> > > > > his blog that we were not sure why it happened and that it
> might even be
> > > > > a Glassfish issue.
> > > > >
> > > > > Doug Kohlert wrote:
> > > > > >
> > > > > > What data corruption are you talking about? I didn't mention
> anything
> > > > > > about data corruption.
> > > > > >
> > > > > > Davanum Srinivas wrote:
> > > > > > >
> > > > > > > Doug,
> > > > > > >
> > > > > > > Nice party line! So the ADB data corruption issue was
> something you
> > > > > > > made up? Or did it really happen?
> > > > > > >
> > > > > > > -- dims
> > > > > > >
> > > > > > > On 2/8/07, Doug Kohlert <doug.kohlert@...
> <mailto:doug.kohlert%40sun.com>
> > > > <mailto:doug.kohlert%40sun.com>
> > > > > > <mailto:doug.kohlert%40sun.com>
> > > > > > > <mailto:doug.kohlert%40sun.com>> wrote:
> > > > > > > > Good point, you may want to post your comment to Vivek's
> blog.
> > > > That
> > > > > > > > said, since there are limitations in both
> > > > > > > > ADB and JiBX when compiling schema to Java, we felt this was
> > > > the most
> > > > > > > > appropriate match of capabilities.
> > > > > > > > So this benchmark really is more of an apples-to-apples
> comparison
> > > > > > > > rather than an apples-to-oranges comparison that you
> suggest.
> > > > > > > >
> > > > > > > > Dennis Sosnoski wrote:
> > > > > > > > > "Benchmarking" against Axis2-XMLBeans (as shown in the
> linked
> > > > > > blog) is
> > > > > > > > > ridiculous. XMLBeans is much slower than either ADB or
> JiBX data
> > > > > > > binding
> > > > > > > > > for Axis2. If you're going to make performance claims
> for your
> > > > > > > software,
> > > > > > > > > at least try to make the tests half way reasonable.
> > > > > > > > >
> > > > > > > > > - Dennis
> > > > > > > > >
> > > > > > > > > Dennis M. Sosnoski
> > > > > > > > > SOA and Web Services in Java
> > > > > > > > > Training and Consulting
> > > > > > > > > http://www.sosnoski.com <http://www.sosnoski.com>
> <http://www.sosnoski.com <http://www.sosnoski.com>>
> > > > <http://www.sosnoski.com <http://www.sosnoski.com>
> <http://www.sosnoski.com <http://www.sosnoski.com>>>
> > > > > > <http://www.sosnoski.com <http://www.sosnoski.com>
> <http://www.sosnoski.com <http://www.sosnoski.com>>
> > > > <http://www.sosnoski.com <http://www.sosnoski.com>
> <http://www.sosnoski.com <http://www.sosnoski.com>>>> -
> > > > > > > http://www.sosnoski.co.nz <http://www.sosnoski.co.nz>
> <http://www.sosnoski.co.nz <http://www.sosnoski.co.nz>>
> > > > <http://www.sosnoski.co.nz <http://www.sosnoski.co.nz>
> <http://www.sosnoski.co.nz <http://www.sosnoski.co.nz>>>
> > > > > > <http://www.sosnoski.co.nz <http://www.sosnoski.co.nz>
> <http://www.sosnoski.co.nz <http://www.sosnoski.co.nz>>
> > > > <http://www.sosnoski.co.nz <http://www.sosnoski.co.nz>
> <http://www.sosnoski.co.nz <http://www.sosnoski.co.nz>>>>
> > > > > > > > > Seattle, WA +1-425-939-0576 - Wellington, NZ
> +64-4-298-6117
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > Doug Kohlert wrote:
> > > > > > > > >
> > > > > > > > >> We are proud to announce the release of JAX-WS 2.1 RI
> FCS.
> > > > JAX-WS
> > > > > > > 2.1 is
> > > > > > > > >> a major re-architecture over JAX-WS 2.0 without
> changing the
> > > > > > standard
> > > > > > > > >> JAX-WS APIs or programming model. The benefits of
> this is a
> > > > > > very fast
> > > > > > > > >> implementation and an extremely flexible, extensible
> > > > > > architecture. To
> > > > > > > > >> read more about how fast the RI is and the new
> functionality
> > > > > > that it
> > > > > > > > >> contains, read Vivek's blog at:
> > > > > > > > >>
> > > > > > >
> > > > > >
> > > >
> http://weblogs.java.net/blog/vivekp/archive/2007/02/jaxws_21_fcs_fa_1.html
> <http://weblogs.java.net/blog/vivekp/archive/2007/02/jaxws_21_fcs_fa_1.html>
> > > >
> <http://weblogs.java.net/blog/vivekp/archive/2007/02/jaxws_21_fcs_fa_1.html
> <http://weblogs.java.net/blog/vivekp/archive/2007/02/jaxws_21_fcs_fa_1.html>>
> > > > > >
> > > >
> <http://weblogs.java.net/blog/vivekp/archive/2007/02/jaxws_21_fcs_fa_1.html
> <http://weblogs.java.net/blog/vivekp/archive/2007/02/jaxws_21_fcs_fa_1.html>
> > > >
> <http://weblogs.java.net/blog/vivekp/archive/2007/02/jaxws_21_fcs_fa_1.html
> <http://weblogs.java.net/blog/vivekp/archive/2007/02/jaxws_21_fcs_fa_1.html>>>
> > > > > >
> > > > > > >
> > > > > >
> > > >
> <http://weblogs.java.net/blog/vivekp/archive/2007/02/jaxws_21_fcs_fa_1.html
> <http://weblogs.java.net/blog/vivekp/archive/2007/02/jaxws_21_fcs_fa_1.html>
> > > >
> <http://weblogs.java.net/blog/vivekp/archive/2007/02/jaxws_21_fcs_fa_1.html
> <http://weblogs.java.net/blog/vivekp/archive/2007/02/jaxws_21_fcs_fa_1.html>>
> > > > > >
> > > >
> <http://weblogs.java.net/blog/vivekp/archive/2007/02/jaxws_21_fcs_fa_1.html
> <http://weblogs.java.net/blog/vivekp/archive/2007/02/jaxws_21_fcs_fa_1.html>
> > > >
> <http://weblogs.java.net/blog/vivekp/archive/2007/02/jaxws_21_fcs_fa_1.html
>
<http://weblogs.java.net/blog/vivekp/archive/2007/02/jaxws_21_fcs_fa_1.html>>>>
> > > > > > > > >>
> > > > > > > > >> Here is an excerpt from Vivek's blog about the Key
> Features.
> > > > > > > > >>
> > > > > > > > >> * Reference Implementation (RI) of JAX-WS 2.1. Full
> JAX-WS 2.1
> > > > > > > > >> Specification <http://jcp.org/en/jsr/detail?id=224
> <http://jcp.org/en/jsr/detail?id=224>
> > > > <http://jcp.org/en/jsr/detail?id=224
> <http://jcp.org/en/jsr/detail?id=224>>
> > > > > > <http://jcp.org/en/jsr/detail?id=224
> <http://jcp.org/en/jsr/detail?id=224>
> > > > <http://jcp.org/en/jsr/detail?id=224
> <http://jcp.org/en/jsr/detail?id=224>>>
> > > > > > > <http://jcp.org/en/jsr/detail?id=224
> <http://jcp.org/en/jsr/detail?id=224>
> > > > <http://jcp.org/en/jsr/detail?id=224
> <http://jcp.org/en/jsr/detail?id=224>>
> > > > > > <http://jcp.org/en/jsr/detail?id=224
> <http://jcp.org/en/jsr/detail?id=224>
> > > > <http://jcp.org/en/jsr/detail?id=224
> <http://jcp.org/en/jsr/detail?id=224>>>>> compliance
> > > > > > > > >> * Development Tools
> > > > > > > > >> o WSDL to Java generator
> > > > > > > > >> + Wsimport command line tool
> > > > > > > > >>
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimport.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimport.html>
> > > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimport.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimport.html>>
> > > > > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimport.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimport.html>
> > > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimport.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimport.html>>>
> > > > > > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimport.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimport.html>
> > > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimport.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimport.html>>
> > > > > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimport.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimport.html>
> > > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimport.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimport.html>>>>>,
> > > > > > > > >> ant task
> > > > > > > > >>
> > > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimportant.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimportant.html>
> > > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimportant.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimportant.html>>
> > > > > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimportant.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimportant.html>
> > > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimportant.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimportant.html>>>
> > > > > > >
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimportant.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimportant.html>
> > > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimportant.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimportant.html>>
> > > > > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimportant.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimportant.html>
> > > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimportant.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimportant.html>>>>>
> > > > > > > > >> and Maven2 plugin
> > > > > > > > >>
> <http://mojo.codehaus.org/jaxws-maven-plugin/index.html
> <http://mojo.codehaus.org/jaxws-maven-plugin/index.html>
> > > > <http://mojo.codehaus.org/jaxws-maven-plugin/index.html
> <http://mojo.codehaus.org/jaxws-maven-plugin/index.html>>
> > > > > > <http://mojo.codehaus.org/jaxws-maven-plugin/index.html
> <http://mojo.codehaus.org/jaxws-maven-plugin/index.html>
> > > > <http://mojo.codehaus.org/jaxws-maven-plugin/index.html
> <http://mojo.codehaus.org/jaxws-maven-plugin/index.html>>>
> > > > > > > <http://mojo.codehaus.org/jaxws-maven-plugin/index.html
> <http://mojo.codehaus.org/jaxws-maven-plugin/index.html>
> > > > <http://mojo.codehaus.org/jaxws-maven-plugin/index.html
> <http://mojo.codehaus.org/jaxws-maven-plugin/index.html>>
> > > > > > <http://mojo.codehaus.org/jaxws-maven-plugin/index.html
> <http://mojo.codehaus.org/jaxws-maven-plugin/index.html>
> > > > <http://mojo.codehaus.org/jaxws-maven-plugin/index.html
> <http://mojo.codehaus.org/jaxws-maven-plugin/index.html>>>>>
> > > > > > > > >> o Java to WSDL generator
> > > > > > > > >> + Wsgen command line tool
> > > > > > > > >>
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgen.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgen.html>
> > > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgen.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgen.html>>
> > > > > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgen.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgen.html>
> > > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgen.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgen.html>>>
> > > > > > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgen.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgen.html>
> > > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgen.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgen.html>>
> > > > > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgen.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgen.html>
> > > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgen.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgen.html>>>>>,
> > > > > > > > >> ant Task
> > > > > > > > >>
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgenant.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgenant.html>
> > > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgenant.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgenant.html>>
> > > > > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgenant.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgenant.html>
> > > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgenant.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgenant.html>>>
> > > > > > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgenant.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgenant.html>
> > > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgenant.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgenant.html>>
> > > > > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgenant.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgenant.html>
> > > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgenant.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgenant.html>>>>>
> > > > > > > > >> and Maven2 plugin
> > > > > > > > >>
> <http://mojo.codehaus.org/jaxws-maven-plugin/index.html
> <http://mojo.codehaus.org/jaxws-maven-plugin/index.html>
> > > > <http://mojo.codehaus.org/jaxws-maven-plugin/index.html
> <http://mojo.codehaus.org/jaxws-maven-plugin/index.html>>
> > > > > > <http://mojo.codehaus.org/jaxws-maven-plugin/index.html
> <http://mojo.codehaus.org/jaxws-maven-plugin/index.html>
> > > > <http://mojo.codehaus.org/jaxws-maven-plugin/index.html
> <http://mojo.codehaus.org/jaxws-maven-plugin/index.html>>>
> > > > > > > <http://mojo.codehaus.org/jaxws-maven-plugin/index.html
> <http://mojo.codehaus.org/jaxws-maven-plugin/index.html>
> > > > <http://mojo.codehaus.org/jaxws-maven-plugin/index.html
> <http://mojo.codehaus.org/jaxws-maven-plugin/index.html>>
> > > > > > <http://mojo.codehaus.org/jaxws-maven-plugin/index.html
> <http://mojo.codehaus.org/jaxws-maven-plugin/index.html>
> > > > <http://mojo.codehaus.org/jaxws-maven-plugin/index.html
> <http://mojo.codehaus.org/jaxws-maven-plugin/index.html>>>>>
> > > > > > > > >> o Integrated with NetBeans 5.5.1
> > > > > > > > >> <http://www.netbeans.info/downloads/dev.php
> <http://www.netbeans.info/downloads/dev.php>
> > > > <http://www.netbeans.info/downloads/dev.php
> <http://www.netbeans.info/downloads/dev.php>>
> > > > > > <http://www.netbeans.info/downloads/dev.php
> <http://www.netbeans.info/downloads/dev.php>
> > > > <http://www.netbeans.info/downloads/dev.php
> <http://www.netbeans.info/downloads/dev.php>>>
> > > > > > > <http://www.netbeans.info/downloads/dev.php
> <http://www.netbeans.info/downloads/dev.php>
> > > > <http://www.netbeans.info/downloads/dev.php
> <http://www.netbeans.info/downloads/dev.php>>
> > > > > > <http://www.netbeans.info/downloads/dev.php
> <http://www.netbeans.info/downloads/dev.php>
> > > > <http://www.netbeans.info/downloads/dev.php
> <http://www.netbeans.info/downloads/dev.php>>>>>
> > > > > > > > >> * Standards
> > > > > > > > >> o Web Services Addressing 1.0 - Core, SOAP Binding
> and WSDL
> > > > > > > > >> Binding
> > > > > > > > >> o WS-Addressing - Member Submission
> > > > > > > > >> o SOAP 1.1 and 1.2
> > > > > > > > >> o REST and XML/HTTP
> > > > > > > > >> o WS-I Basic Profile 1.1, Simple SOAP Binding Profile
> 1.0 and
> > > > > > > > >> Attachment Profile 1.0
> > > > > > > > >> o MTOM
> > > > > > > > >> * Extensions (May not be final unless says so)
> > > > > > > > >> o Web Services Interoperable Technologies ( WSIT
> > > > > > > > >> <https://wsit.dev.java.net/index.html#downloads
> <https://wsit.dev.java.net/index.html#downloads>
> > > > <https://wsit.dev.java.net/index.html#downloads
> <https://wsit.dev.java.net/index.html#downloads>>
> > > > > > <https://wsit.dev.java.net/index.html#downloads
> <https://wsit.dev.java.net/index.html#downloads>
> > > > <https://wsit.dev.java.net/index.html#downloads
> <https://wsit.dev.java.net/index.html#downloads>>>
> > > > > > > <https://wsit.dev.java.net/index.html#downloads
> <https://wsit.dev.java.net/index.html#downloads>
> > > > <https://wsit.dev.java.net/index.html#downloads
> <https://wsit.dev.java.net/index.html#downloads>>
> > > > > > <https://wsit.dev.java.net/index.html#downloads
> <https://wsit.dev.java.net/index.html#downloads>
> > > > <https://wsit.dev.java.net/index.html#downloads
> <https://wsit.dev.java.net/index.html#downloads>>>>>) - enables
> > > > > > > > >> .NET 3.0 interoperability
> > > > > > > > >> + WS-ReliableMessaging
> > > > > > > > >> + WS-Policy
> > > > > > > > >> + WS-MEX
> > > > > > > > >> + WS-Security/WS-Security Policy
> > > > > > > > >> + WS-Trust/WS-Secure Conversation
> > > > > > > > >> + WS-AT/WS-Tx (Supported only on Glassfish v2)
> > > > > > > > >> + SOAP/TCP
> > > > > > > > >> o Spring support
> > > > <https://jax-ws-commons.dev.java.net/spring/
> <https://jax-ws-commons.dev.java.net/spring/>
> > > > <https://jax-ws-commons.dev.java.net/spring/
> <https://jax-ws-commons.dev.java.net/spring/>>
> > > > > > <https://jax-ws-commons.dev.java.net/spring/
> <https://jax-ws-commons.dev.java.net/spring/>
> > > > <https://jax-ws-commons.dev.java.net/spring/
> <https://jax-ws-commons.dev.java.net/spring/>>>
> > > > > > > <https://jax-ws-commons.dev.java.net/spring/
> <https://jax-ws-commons.dev.java.net/spring/>
> > > > <https://jax-ws-commons.dev.java.net/spring/
> <https://jax-ws-commons.dev.java.net/spring/>>
> > > > > > <https://jax-ws-commons.dev.java.net/spring/
> <https://jax-ws-commons.dev.java.net/spring/>
> > > > <https://jax-ws-commons.dev.java.net/spring/
> <https://jax-ws-commons.dev.java.net/spring/>>>>>
> > > > > > > > >> o Pluggable Transport
> > > > > > > > >> <https://jax-ws.dev.java.net/transport.html
> <https://jax-ws.dev.java.net/transport.html>
> > > > <https://jax-ws.dev.java.net/transport.html
> <https://jax-ws.dev.java.net/transport.html>>
> > > > > > <https://jax-ws.dev.java.net/transport.html
> <https://jax-ws.dev.java.net/transport.html>
> > > > <https://jax-ws.dev.java.net/transport.html
> <https://jax-ws.dev.java.net/transport.html>>>
> > > > > > > <https://jax-ws.dev.java.net/transport.html
> <https://jax-ws.dev.java.net/transport.html>
> > > > <https://jax-ws.dev.java.net/transport.html
> <https://jax-ws.dev.java.net/transport.html>>
> > > > > > <https://jax-ws.dev.java.net/transport.html
> <https://jax-ws.dev.java.net/transport.html>
> > > > <https://jax-ws.dev.java.net/transport.html
> <https://jax-ws.dev.java.net/transport.html>>>>>
> > > > > > > > >> + In-VM transport
> > > > > > > > >> + Servlet transport (bundled with the RI)
> > > > > > > > >> + JMS transport
> <http://jms-ws-transport.dev.java.net/
> <http://jms-ws-transport.dev.java.net/>
> > > > <http://jms-ws-transport.dev.java.net/
> <http://jms-ws-transport.dev.java.net/>>
> > > > > > <http://jms-ws-transport.dev.java.net/
> <http://jms-ws-transport.dev.java.net/>
> > > > <http://jms-ws-transport.dev.java.net/
> <http://jms-ws-transport.dev.java.net/>>>
> > > > > > > <http://jms-ws-transport.dev.java.net/
> <http://jms-ws-transport.dev.java.net/>
> > > > <http://jms-ws-transport.dev.java.net/
> <http://jms-ws-transport.dev.java.net/>>
> > > > > > <http://jms-ws-transport.dev.java.net/
> <http://jms-ws-transport.dev.java.net/>
> > > > <http://jms-ws-transport.dev.java.net/
> <http://jms-ws-transport.dev.java.net/>>>>>
> > > > > > > > >> + SOAP over TCP transport (part of WSIT
> > > > > > > > >> <https://wsit.dev.java.net
> <https://wsit.dev.java.net> <https://wsit.dev.java.net
> <https://wsit.dev.java.net>>
> > > > <https://wsit.dev.java.net <https://wsit.dev.java.net>
> <https://wsit.dev.java.net <https://wsit.dev.java.net>>>
> > > > > > <https://wsit.dev.java.net <https://wsit.dev.java.net>
> <https://wsit.dev.java.net <https://wsit.dev.java.net>>
> > > > <https://wsit.dev.java.net <https://wsit.dev.java.net>
> <https://wsit.dev.java.net <https://wsit.dev.java.net>>>>>)
> > > > > > > > >> o FastInfoset (bundled with JAX-WS 2.1 RI)
> > > > > > > > >> <https://fi.dev.java.net/ <https://fi.dev.java.net/>
> <https://fi.dev.java.net/ <https://fi.dev.java.net/>>
> > > > <https://fi.dev.java.net/ <https://fi.dev.java.net/>
> <https://fi.dev.java.net/ <https://fi.dev.java.net/>>>
> > > > > > <https://fi.dev.java.net/ <https://fi.dev.java.net/>
> <https://fi.dev.java.net/ <https://fi.dev.java.net/>>
> > > > <https://fi.dev.java.net/ <https://fi.dev.java.net/>
> <https://fi.dev.java.net/ <https://fi.dev.java.net/>>>>>
> > > > > > > > >> + ITU-T Rec. X.891 | ISO/IEC 24824-1
> > > > > > > > >> <http://www.itu.int/rec/T-REC-X.891-200505-I/e
> <http://www.itu.int/rec/T-REC-X.891-200505-I/e>
> > > > <http://www.itu.int/rec/T-REC-X.891-200505-I/e
> <http://www.itu.int/rec/T-REC-X.891-200505-I/e>>
> > > > > > <http://www.itu.int/rec/T-REC-X.891-200505-I/e
> <http://www.itu.int/rec/T-REC-X.891-200505-I/e>
> > > > <http://www.itu.int/rec/T-REC-X.891-200505-I/e
> <http://www.itu.int/rec/T-REC-X.891-200505-I/e>>>
> > > > > > > <http://www.itu.int/rec/T-REC-X.891-200505-I/e
> <http://www.itu.int/rec/T-REC-X.891-200505-I/e>
> > > > <http://www.itu.int/rec/T-REC-X.891-200505-I/e
> <http://www.itu.int/rec/T-REC-X.891-200505-I/e>>
> > > > > > <http://www.itu.int/rec/T-REC-X.891-200505-I/e
> <http://www.itu.int/rec/T-REC-X.891-200505-I/e>
> > > > <http://www.itu.int/rec/T-REC-X.891-200505-I/e
> <http://www.itu.int/rec/T-REC-X.891-200505-I/e>>>>>
> > > > > > > > >> o JBI Service Engine and Binding Component(part of
> > > > Glassfish v2)
> > > > > > > > >> o HTTP Binding Component
> > > > > > > > >>
> <http://www.glassfishwiki.org/jbiwiki/Wiki.jsp?page=HTTPBC
> <http://www.glassfishwiki.org/jbiwiki/Wiki.jsp?page=HTTPBC>
> > > > <http://www.glassfishwiki.org/jbiwiki/Wiki.jsp?page=HTTPBC
> <http://www.glassfishwiki.org/jbiwiki/Wiki.jsp?page=HTTPBC>>
> > > > > > <http://www.glassfishwiki.org/jbiwiki/Wiki.jsp?page=HTTPBC
> <http://www.glassfishwiki.org/jbiwiki/Wiki.jsp?page=HTTPBC>
> > > > <http://www.glassfishwiki.org/jbiwiki/Wiki.jsp?page=HTTPBC
> <http://www.glassfishwiki.org/jbiwiki/Wiki.jsp?page=HTTPBC>>>
> > > > > > > <http://www.glassfishwiki.org/jbiwiki/Wiki.jsp?page=HTTPBC
> <http://www.glassfishwiki.org/jbiwiki/Wiki.jsp?page=HTTPBC>
> > > > <http://www.glassfishwiki.org/jbiwiki/Wiki.jsp?page=HTTPBC
> <http://www.glassfishwiki.org/jbiwiki/Wiki.jsp?page=HTTPBC>>
> > > > > > <http://www.glassfishwiki.org/jbiwiki/Wiki.jsp?page=HTTPBC
> <http://www.glassfishwiki.org/jbiwiki/Wiki.jsp?page=HTTPBC>
> > > > <http://www.glassfishwiki.org/jbiwiki/Wiki.jsp?page=HTTPBC
> <http://www.glassfishwiki.org/jbiwiki/Wiki.jsp?page=HTTPBC>>>>>,
> > > > > > > > >> used by Open JBI component
> > > > > > > > >> <https://open-jbi-components.dev.java.net/
> <https://open-jbi-components.dev.java.net/>
> > > > <https://open-jbi-components.dev.java.net/
> <https://open-jbi-components.dev.java.net/>>
> > > > > > <https://open-jbi-components.dev.java.net/
> <https://open-jbi-components.dev.java.net/>
> > > > <https://open-jbi-components.dev.java.net/
> <https://open-jbi-components.dev.java.net/>>>
> > > > > > > <https://open-jbi-components.dev.java.net/
> <https://open-jbi-components.dev.java.net/>
> > > > <https://open-jbi-components.dev.java.net/
> <https://open-jbi-components.dev.java.net/>>
> > > > > > <https://open-jbi-components.dev.java.net/
> <https://open-jbi-components.dev.java.net/>
> > > > <https://open-jbi-components.dev.java.net/
> <https://open-jbi-components.dev.java.net/>>>>>
> > > > > > > > >> * Data binding - JAXB 2.1.2 RI
> > > > > > <https://jaxb.dev.java.net/2.1.2/
> <https://jaxb.dev.java.net/2.1.2/>
> > > > <https://jaxb.dev.java.net/2.1.2/
> <https://jaxb.dev.java.net/2.1.2/>> <https://jaxb.dev.java.net/2.1.2/
> <https://jaxb.dev.java.net/2.1.2/>
> > > > <https://jaxb.dev.java.net/2.1.2/
> <https://jaxb.dev.java.net/2.1.2/>>>
> > > > > > > <https://jaxb.dev.java.net/2.1.2/
> <https://jaxb.dev.java.net/2.1.2/>
> > > > <https://jaxb.dev.java.net/2.1.2/
> <https://jaxb.dev.java.net/2.1.2/>> <https://jaxb.dev.java.net/2.1.2/
> <https://jaxb.dev.java.net/2.1.2/>
> > > > <https://jaxb.dev.java.net/2.1.2/
> <https://jaxb.dev.java.net/2.1.2/>>>>>
> > > > > > > > >> * Server Side Asynchrony - AsyncProvider
> > > > > > > > >>
> > > > <https://jax-ws.dev.java.net/nonav/2.1/docs/asyncprovider.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/asyncprovider.html>
> > > > <https://jax-ws.dev.java.net/nonav/2.1/docs/asyncprovider.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/asyncprovider.html>>
> > > > > >
> <https://jax-ws.dev.java.net/nonav/2.1/docs/asyncprovider.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/asyncprovider.html>
> > > > <https://jax-ws.dev.java.net/nonav/2.1/docs/asyncprovider.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/asyncprovider.html>>>
> > > > > > >
> <https://jax-ws.dev.java.net/nonav/2.1/docs/asyncprovider.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/asyncprovider.html>
> > > > <https://jax-ws.dev.java.net/nonav/2.1/docs/asyncprovider.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/asyncprovider.html>>
> > > > > >
> <https://jax-ws.dev.java.net/nonav/2.1/docs/asyncprovider.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/asyncprovider.html>
> > > > <https://jax-ws.dev.java.net/nonav/2.1/docs/asyncprovider.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/asyncprovider.html>>>>>
> > > > > > > > >> * Stateful Web Services
> > > > > > > > >>
> > > > > > >
> > > >
> <https://jax-ws.dev.java.net/nonav/2.1/docs/statefulWebservice.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/statefulWebservice.html>
> > > >
> <https://jax-ws.dev.java.net/nonav/2.1/docs/statefulWebservice.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/statefulWebservice.html>>
> > > > > >
> > > >
> <https://jax-ws.dev.java.net/nonav/2.1/docs/statefulWebservice.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/statefulWebservice.html>
> > > >
> <https://jax-ws.dev.java.net/nonav/2.1/docs/statefulWebservice.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/statefulWebservice.html>>>
> > > > > > >
> > > >
> <https://jax-ws.dev.java.net/nonav/2.1/docs/statefulWebservice.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/statefulWebservice.html>
> > > >
> <https://jax-ws.dev.java.net/nonav/2.1/docs/statefulWebservice.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/statefulWebservice.html>>
> > > > > >
> > > >
> <https://jax-ws.dev.java.net/nonav/2.1/docs/statefulWebservice.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/statefulWebservice.html>
> > > >
> <https://jax-ws.dev.java.net/nonav/2.1/docs/statefulWebservice.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/statefulWebservice.html>>>>>
> > > > > > > > >> * Support for custom WebServiceFeature
> > > > > > > > >>
> > > > > > >
> > > > > >
> > > >
>
<http://weblogs.java.net/blog/ramapulavarthi/archive/2007/01/extending_jaxws.htm\
l
>
<http://weblogs.java.net/blog/ramapulavarthi/archive/2007/01/extending_jaxws.htm\
l>
> > > >
>
<http://weblogs.java.net/blog/ramapulavarthi/archive/2007/01/extending_jaxws.htm\
l
>
<http://weblogs.java.net/blog/ramapulavarthi/archive/2007/01/extending_jaxws.htm\
l>>
> > > > > >
> > > >
>
<http://weblogs.java.net/blog/ramapulavarthi/archive/2007/01/extending_jaxws.htm\
l
>
<http://weblogs.java.net/blog/ramapulavarthi/archive/2007/01/extending_jaxws.htm\
l>
> > > >
>
<http://weblogs.java.net/blog/ramapulavarthi/archive/2007/01/extending_jaxws.htm\
l
>
<http://weblogs.java.net/blog/ramapulavarthi/archive/2007/01/extending_jaxws.htm\
l>>>
> > > > > >
> > > > > > >
> > > > > >
> > > >
>
<http://weblogs.java.net/blog/ramapulavarthi/archive/2007/01/extending_jaxws.htm\
l
>
<http://weblogs.java.net/blog/ramapulavarthi/archive/2007/01/extending_jaxws.htm\
l>
> > > >
>
<http://weblogs.java.net/blog/ramapulavarthi/archive/2007/01/extending_jaxws.htm\
l
>
<http://weblogs.java.net/blog/ramapulavarthi/archive/2007/01/extending_jaxws.htm\
l>>
> > > > > >
> > > >
>
<http://weblogs.java.net/blog/ramapulavarthi/archive/2007/01/extending_jaxws.htm\
l
>
<http://weblogs.java.net/blog/ramapulavarthi/archive/2007/01/extending_jaxws.htm\
l>
> > > >
>
<http://weblogs.java.net/blog/ramapulavarthi/archive/2007/01/extending_jaxws.htm\
l
>
<http://weblogs.java.net/blog/ramapulavarthi/archive/2007/01/extending_jaxws.htm\
l>>>>>
> > > > > > > > >> * Hosting API
> > > > > > > > >>
> > > > > > >
> > > > > >
> > > >
>
<https://jax-ws-architecture-document.dev.java.net/nonav/doc21/index.html?com/su\
n/xml/ws/api/server/package-summary.html
>
<https://jax-ws-architecture-document.dev.java.net/nonav/doc21/index.html?com/su\
n/xml/ws/api/server/package-summary.html>
> > > >
>
<https://jax-ws-architecture-document.dev.java.net/nonav/doc21/index.html?com/su\
n/xml/ws/api/server/package-summary.html
>
<https://jax-ws-architecture-document.dev.java.net/nonav/doc21/index.html?com/su\
n/xml/ws/api/server/package-summary.html>>
> > > > > >
> > > >
>
<https://jax-ws-architecture-document.dev.java.net/nonav/doc21/index.html?com/su\
n/xml/ws/api/server/package-summary.html
>
<https://jax-ws-architecture-document.dev.java.net/nonav/doc21/index.html?com/su\
n/xml/ws/api/server/package-summary.html>
> > > >
>
<https://jax-ws-architecture-document.dev.java.net/nonav/doc21/index.html?com/su\
n/xml/ws/api/server/package-summary.html
>
<https://jax-ws-architecture-document.dev.java.net/nonav/doc21/index.html?com/su\
n/xml/ws/api/server/package-summary.html>>>
> > > > > >
> > > > > > >
> > > > > >
> > > >
>
<https://jax-ws-architecture-document.dev.java.net/nonav/doc21/index.html?com/su\
n/xml/ws/api/server/package-summary.html
>
<https://jax-ws-architecture-document.dev.java.net/nonav/doc21/index.html?com/su\
n/xml/ws/api/server/package-summary.html>
> > > >
>
<https://jax-ws-architecture-document.dev.java.net/nonav/doc21/index.html?com/su\
n/xml/ws/api/server/package-summary.html
>
<https://jax-ws-architecture-document.dev.java.net/nonav/doc21/index.html?com/su\
n/xml/ws/api/server/package-summary.html>>
> > > > > >
> > > >
>
<https://jax-ws-architecture-document.dev.java.net/nonav/doc21/index.html?com/su\
n/xml/ws/api/server/package-summary.html
>
<https://jax-ws-architecture-document.dev.java.net/nonav/doc21/index.html?com/su\
n/xml/ws/api/server/package-summary.html>
> > > >
>
<https://jax-ws-architecture-document.dev.java.net/nonav/doc21/index.html?com/su\
n/xml/ws/api/server/package-summary.html
>
<https://jax-ws-architecture-document.dev.java.net/nonav/doc21/index.html?com/su\
n/xml/ws/api/server/package-summary.html>>>>>
> > > > > > > > >>
> > > > > > > > >> o These APIs can be used by a J2EE application server to
> > > > > > > > >> integrate JAX-WS 2.1 RI for hosting JAX-WS services
> > > > > > > > >> * Endpoint Deployment
> > > > > > > > >> o Glassfish v2 <https://glassfish.dev.java.net
> <https://glassfish.dev.java.net>
> > > > <https://glassfish.dev.java.net <https://glassfish.dev.java.net>>
> > > > > > <https://glassfish.dev.java.net
> <https://glassfish.dev.java.net> <https://glassfish.dev.java.net
> <https://glassfish.dev.java.net>>>
> > > > > > > <https://glassfish.dev.java.net
> <https://glassfish.dev.java.net> <https://glassfish.dev.java.net
> <https://glassfish.dev.java.net>>
> > > > <https://glassfish.dev.java.net <https://glassfish.dev.java.net>
> <https://glassfish.dev.java.net <https://glassfish.dev.java.net>>>>>
> > > > > > > > >> + Tightly integrated with Glassfish
> > > > > > > > >> + Supports EJB and Web endpoints
> > > > > > > > >> + 109 based deployment support for better portability
> > > > > > > > >> + JAX-WS RI specific deployment descriptor support
> > > > > > > > >> o Sun One Application Server 9.0 ur1
> > > > > > > > >>
> <http://www.sun.com/software/products/appsrvr_pe/index.xml
> <http://www.sun.com/software/products/appsrvr_pe/index.xml>
> > > > <http://www.sun.com/software/products/appsrvr_pe/index.xml
> <http://www.sun.com/software/products/appsrvr_pe/index.xml>>
> > > > > > <http://www.sun.com/software/products/appsrvr_pe/index.xml
> <http://www.sun.com/software/products/appsrvr_pe/index.xml>
> > > > <http://www.sun.com/software/products/appsrvr_pe/index.xml
> <http://www.sun.com/software/products/appsrvr_pe/index.xml>>>
> > > > > > > <http://www.sun.com/software/products/appsrvr_pe/index.xml
> <http://www.sun.com/software/products/appsrvr_pe/index.xml>
> > > > <http://www.sun.com/software/products/appsrvr_pe/index.xml
> <http://www.sun.com/software/products/appsrvr_pe/index.xml>>
> > > > > > <http://www.sun.com/software/products/appsrvr_pe/index.xml
> <http://www.sun.com/software/products/appsrvr_pe/index.xml>
> > > > <http://www.sun.com/software/products/appsrvr_pe/index.xml
> <http://www.sun.com/software/products/appsrvr_pe/index.xml>>>>>
> > > > > > > > >> o Light weight HTTP server
> > > > > > > > >> + On JDK 1.5 through http.jar distributed with the
> > > > > > > > >> JAX-WS 2.1 RI bundle
> > > > > > > > >> + Bundled with JDK 6
> > > > > > > > >> o Any other container that supports Servlet 2.4, such as
> > > > > > > > >> Tomcat, Jetty, Geronimo, JBoss, Resin, ... You name it!
> > > > > > > > >>
> > > > > > > > >>
> > > > > > > > >>
> > > > > > > > >>
> > > > > > > > >>
> ----------------------------------------------------------
> > > > > > > > >> This group is a forum for builders of SOAP
> implementations to
> > > > > > > discuss implementation and interoperability issues. Please
> stay
> > > > > > on-topic.
> > > > > > > > >> Yahoo! Groups Links
> > > > > > > > >>
> > > > > > > > >>
> > > > > > > > >>
> > > > > > > > >>
> > > > > > > > >>
> > > > > > > > >>
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > ----------------------------------------------------------
> > > > > > > > > This group is a forum for builders of SOAP
> implementations to
> > > > > > > discuss implementation and interoperability issues. Please
> stay
> > > > > > on-topic.
> > > > > > > > > Yahoo! Groups Links
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > ----------------------------------------------------------
> > > > > > > > This group is a forum for builders of SOAP
> implementations to
> > > > > > > discuss implementation and interoperability issues. Please
> stay
> > > > > > on-topic.
> > > > > > > > Yahoo! Groups Links
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > Davanum Srinivas :: http://wso2.org/ <http://wso2.org/>
> <http://wso2.org/ <http://wso2.org/>>
> > > > <http://wso2.org/ <http://wso2.org/> <http://wso2.org/
> <http://wso2.org/>>>
> > > > > > <http://wso2.org/ <http://wso2.org/> <http://wso2.org/
> <http://wso2.org/>> <http://wso2.org/ <http://wso2.org/>
> > > > <http://wso2.org/ <http://wso2.org/>>>> :: Oxygen for
> > > > > > > Web Services Developers
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > ----------------------------------------------------------
> > > > > This group is a forum for builders of SOAP implementations to
> > > > discuss implementation and interoperability issues. Please stay
> on-topic.
> > > > > Yahoo! Groups Links
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > > > --
> > > > Davanum Srinivas :: http://wso2.org/ <http://wso2.org/>
> <http://wso2.org/ <http://wso2.org/>> :: Oxygen for
> > > > Web Services Developers
> > > >
> > > >
> > >
> > >
> > > ----------------------------------------------------------
> > > This group is a forum for builders of SOAP implementations to
> discuss implementation and interoperability issues. Please stay on-topic.
> > > Yahoo! Groups Links
> > >
> > >
> > >
> > >
> >
> >
> > --
> > Davanum Srinivas :: http://wso2.org/ <http://wso2.org/> :: Oxygen
> for Web Services Developers
> >
>
> --
> Davanum Srinivas :: http://wso2.org/ <http://wso2.org/> :: Oxygen for
> Web Services Developers
>
>

I guess, you were asking me to respond to it :) Dan sums it up nicely:

"However that will be quite tricky to achieve because now the limiting
factor in web service performance is probably not XFire or Axis2, its
going to be your XML parser, HTTP provider, and/or your data-binding
implementation."

That's a total turn around from original assertions of the XFire team
both on-record and off-the-record about Axis2 vs XFire. So that's good
news :)

Better news is now it's ADB vs JAXB2. Looking at profiler outputs i
can say that the reflection based stuff in JAXB2 slows things down
especially for huge data sets. JIBX and ADB take very similar
approach. In JIBX's case, bytecode is generated that uses xpp3 and
populates the fields and in ADB we generate Stax/AXIOM based code to
the same and then compile it. So JIBX and ADB is very comparable.
FWIW, you guys have the upper hand as you can speed up reflection in
the JVM/JDK itself, which you did as per comments i saw from one of
the team members (in JDK6).

That's why i am very interested in seeing the relative performances of
the two data bindings under JDK6 using woodstox running under tomcat.
(Since kohsuke hinted at possible problem in GlassFish and we prefer
woodstox, since we haven't spent any time with SJSXP).

thanks,
dims

On 2/12/07, Davanum Srinivas <davanum@...> wrote:
> Yep. We did.
>
> thanks,
> dims
>
> On 2/12/07, Doug Kohlert <doug.kohlert@...> wrote:
> > Dims,
> > I just found an interesting blog questioning the Axis2 benchmarks
> > (http://netzooid.com/blog/2007/02/08/dodgy-benchmarks-indeed/), have you
> > seen it?
> >
> > Davanum Srinivas wrote:
> > >
> > > Doug,
> > >
> > > There is no mention of apples-to-apples comparison on kohsuke's blog.
> > > There is no mention of XMLBeans in vivek's blog. This is the first
> > > time i hear this new argument that Axis2/XmlBeans is a
> > > apples-to-apples comparison....
> > >
> > > If you really wanted to test the perf, you should compare multiple
> > > options including the default settings for both stacks :) In this
> > > case, it would mean Axis2/JAXB, Axis2/ADB, JAXWS-RI/JAXB. Running
> > > Axis2/XMLBeans and claiming huge perf improvements is ridiculous as
> > > dennis mentioned.
> > >
> > > -- dims
> > >
> > > On 2/8/07, Doug Kohlert <doug.kohlert@...
> > > <mailto:doug.kohlert%40sun.com>> wrote:
> > > > Oh, you are talking about the data corruption mentioned in Kohsuke's
> > > > blog
> > > >
> > > (http://weblogs.java.net/blog/kohsuke/archive/2007/02/jaxws_ri_21_ben.html
> > >
<http://weblogs.java.net/blog/kohsuke/archive/2007/02/jaxws_ri_21_ben.html>).
> > > > Yea Dims, we made that up; get real dude. Kohsuke even mentioned in
> > > > his blog that we were not sure why it happened and that it might even be
> > > > a Glassfish issue.
> > > >
> > > > Doug Kohlert wrote:
> > > > >
> > > > > What data corruption are you talking about? I didn't mention anything
> > > > > about data corruption.
> > > > >
> > > > > Davanum Srinivas wrote:
> > > > > >
> > > > > > Doug,
> > > > > >
> > > > > > Nice party line! So the ADB data corruption issue was something you
> > > > > > made up? Or did it really happen?
> > > > > >
> > > > > > -- dims
> > > > > >
> > > > > > On 2/8/07, Doug Kohlert <doug.kohlert@...
> > > <mailto:doug.kohlert%40sun.com>
> > > > > <mailto:doug.kohlert%40sun.com>
> > > > > > <mailto:doug.kohlert%40sun.com>> wrote:
> > > > > > > Good point, you may want to post your comment to Vivek's blog.
> > > That
> > > > > > > said, since there are limitations in both
> > > > > > > ADB and JiBX when compiling schema to Java, we felt this was
> > > the most
> > > > > > > appropriate match of capabilities.
> > > > > > > So this benchmark really is more of an apples-to-apples comparison
> > > > > > > rather than an apples-to-oranges comparison that you suggest.
> > > > > > >
> > > > > > > Dennis Sosnoski wrote:
> > > > > > > > "Benchmarking" against Axis2-XMLBeans (as shown in the linked
> > > > > blog) is
> > > > > > > > ridiculous. XMLBeans is much slower than either ADB or JiBX data
> > > > > > binding
> > > > > > > > for Axis2. If you're going to make performance claims for your
> > > > > > software,
> > > > > > > > at least try to make the tests half way reasonable.
> > > > > > > >
> > > > > > > > - Dennis
> > > > > > > >
> > > > > > > > Dennis M. Sosnoski
> > > > > > > > SOA and Web Services in Java
> > > > > > > > Training and Consulting
> > > > > > > > http://www.sosnoski.com <http://www.sosnoski.com>
> > > <http://www.sosnoski.com <http://www.sosnoski.com>>
> > > > > <http://www.sosnoski.com <http://www.sosnoski.com>
> > > <http://www.sosnoski.com <http://www.sosnoski.com>>> -
> > > > > > http://www.sosnoski.co.nz <http://www.sosnoski.co.nz>
> > > <http://www.sosnoski.co.nz <http://www.sosnoski.co.nz>>
> > > > > <http://www.sosnoski.co.nz <http://www.sosnoski.co.nz>
> > > <http://www.sosnoski.co.nz <http://www.sosnoski.co.nz>>>
> > > > > > > > Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > Doug Kohlert wrote:
> > > > > > > >
> > > > > > > >> We are proud to announce the release of JAX-WS 2.1 RI FCS.
> > > JAX-WS
> > > > > > 2.1 is
> > > > > > > >> a major re-architecture over JAX-WS 2.0 without changing the
> > > > > standard
> > > > > > > >> JAX-WS APIs or programming model. The benefits of this is a
> > > > > very fast
> > > > > > > >> implementation and an extremely flexible, extensible
> > > > > architecture. To
> > > > > > > >> read more about how fast the RI is and the new functionality
> > > > > that it
> > > > > > > >> contains, read Vivek's blog at:
> > > > > > > >>
> > > > > >
> > > > >
> > > http://weblogs.java.net/blog/vivekp/archive/2007/02/jaxws_21_fcs_fa_1.html
> > >
<http://weblogs.java.net/blog/vivekp/archive/2007/02/jaxws_21_fcs_fa_1.html>
> > > > >
> > >
<http://weblogs.java.net/blog/vivekp/archive/2007/02/jaxws_21_fcs_fa_1.html
> > >
<http://weblogs.java.net/blog/vivekp/archive/2007/02/jaxws_21_fcs_fa_1.html>>
> > > > >
> > > > > >
> > > > >
> > >
<http://weblogs.java.net/blog/vivekp/archive/2007/02/jaxws_21_fcs_fa_1.html
> > >
<http://weblogs.java.net/blog/vivekp/archive/2007/02/jaxws_21_fcs_fa_1.html>
> > > > >
> > >
<http://weblogs.java.net/blog/vivekp/archive/2007/02/jaxws_21_fcs_fa_1.html
> > >
<http://weblogs.java.net/blog/vivekp/archive/2007/02/jaxws_21_fcs_fa_1.html>>>
> > > > > > > >>
> > > > > > > >> Here is an excerpt from Vivek's blog about the Key Features.
> > > > > > > >>
> > > > > > > >> * Reference Implementation (RI) of JAX-WS 2.1. Full JAX-WS 2.1
> > > > > > > >> Specification <http://jcp.org/en/jsr/detail?id=224
> > > <http://jcp.org/en/jsr/detail?id=224>
> > > > > <http://jcp.org/en/jsr/detail?id=224
> > > <http://jcp.org/en/jsr/detail?id=224>>
> > > > > > <http://jcp.org/en/jsr/detail?id=224
> > > <http://jcp.org/en/jsr/detail?id=224>
> > > > > <http://jcp.org/en/jsr/detail?id=224
> > > <http://jcp.org/en/jsr/detail?id=224>>>> compliance
> > > > > > > >> * Development Tools
> > > > > > > >> o WSDL to Java generator
> > > > > > > >> + Wsimport command line tool
> > > > > > > >> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimport.html
> > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimport.html>
> > > > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimport.html
> > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimport.html>>
> > > > > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimport.html
> > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimport.html>
> > > > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimport.html
> > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimport.html>>>>,
> > > > > > > >> ant task
> > > > > > > >>
> > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimportant.html
> > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimportant.html>
> > > > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimportant.html
> > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimportant.html>>
> > > > > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimportant.html
> > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimportant.html>
> > > > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimportant.html
> > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimportant.html>>>>
> > > > > > > >> and Maven2 plugin
> > > > > > > >> <http://mojo.codehaus.org/jaxws-maven-plugin/index.html
> > > <http://mojo.codehaus.org/jaxws-maven-plugin/index.html>
> > > > > <http://mojo.codehaus.org/jaxws-maven-plugin/index.html
> > > <http://mojo.codehaus.org/jaxws-maven-plugin/index.html>>
> > > > > > <http://mojo.codehaus.org/jaxws-maven-plugin/index.html
> > > <http://mojo.codehaus.org/jaxws-maven-plugin/index.html>
> > > > > <http://mojo.codehaus.org/jaxws-maven-plugin/index.html
> > > <http://mojo.codehaus.org/jaxws-maven-plugin/index.html>>>>
> > > > > > > >> o Java to WSDL generator
> > > > > > > >> + Wsgen command line tool
> > > > > > > >> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgen.html
> > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgen.html>
> > > > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgen.html
> > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgen.html>>
> > > > > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgen.html
> > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgen.html>
> > > > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgen.html
> > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgen.html>>>>,
> > > > > > > >> ant Task
> > > > > > > >> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgenant.html
> > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgenant.html>
> > > > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgenant.html
> > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgenant.html>>
> > > > > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgenant.html
> > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgenant.html>
> > > > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgenant.html
> > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgenant.html>>>>
> > > > > > > >> and Maven2 plugin
> > > > > > > >> <http://mojo.codehaus.org/jaxws-maven-plugin/index.html
> > > <http://mojo.codehaus.org/jaxws-maven-plugin/index.html>
> > > > > <http://mojo.codehaus.org/jaxws-maven-plugin/index.html
> > > <http://mojo.codehaus.org/jaxws-maven-plugin/index.html>>
> > > > > > <http://mojo.codehaus.org/jaxws-maven-plugin/index.html
> > > <http://mojo.codehaus.org/jaxws-maven-plugin/index.html>
> > > > > <http://mojo.codehaus.org/jaxws-maven-plugin/index.html
> > > <http://mojo.codehaus.org/jaxws-maven-plugin/index.html>>>>
> > > > > > > >> o Integrated with NetBeans 5.5.1
> > > > > > > >> <http://www.netbeans.info/downloads/dev.php
> > > <http://www.netbeans.info/downloads/dev.php>
> > > > > <http://www.netbeans.info/downloads/dev.php
> > > <http://www.netbeans.info/downloads/dev.php>>
> > > > > > <http://www.netbeans.info/downloads/dev.php
> > > <http://www.netbeans.info/downloads/dev.php>
> > > > > <http://www.netbeans.info/downloads/dev.php
> > > <http://www.netbeans.info/downloads/dev.php>>>>
> > > > > > > >> * Standards
> > > > > > > >> o Web Services Addressing 1.0 - Core, SOAP Binding and WSDL
> > > > > > > >> Binding
> > > > > > > >> o WS-Addressing - Member Submission
> > > > > > > >> o SOAP 1.1 and 1.2
> > > > > > > >> o REST and XML/HTTP
> > > > > > > >> o WS-I Basic Profile 1.1, Simple SOAP Binding Profile 1.0 and
> > > > > > > >> Attachment Profile 1.0
> > > > > > > >> o MTOM
> > > > > > > >> * Extensions (May not be final unless says so)
> > > > > > > >> o Web Services Interoperable Technologies ( WSIT
> > > > > > > >> <https://wsit.dev.java.net/index.html#downloads
> > > <https://wsit.dev.java.net/index.html#downloads>
> > > > > <https://wsit.dev.java.net/index.html#downloads
> > > <https://wsit.dev.java.net/index.html#downloads>>
> > > > > > <https://wsit.dev.java.net/index.html#downloads
> > > <https://wsit.dev.java.net/index.html#downloads>
> > > > > <https://wsit.dev.java.net/index.html#downloads
> > > <https://wsit.dev.java.net/index.html#downloads>>>>) - enables
> > > > > > > >> .NET 3.0 interoperability
> > > > > > > >> + WS-ReliableMessaging
> > > > > > > >> + WS-Policy
> > > > > > > >> + WS-MEX
> > > > > > > >> + WS-Security/WS-Security Policy
> > > > > > > >> + WS-Trust/WS-Secure Conversation
> > > > > > > >> + WS-AT/WS-Tx (Supported only on Glassfish v2)
> > > > > > > >> + SOAP/TCP
> > > > > > > >> o Spring support
> > > <https://jax-ws-commons.dev.java.net/spring/
> > > <https://jax-ws-commons.dev.java.net/spring/>
> > > > > <https://jax-ws-commons.dev.java.net/spring/
> > > <https://jax-ws-commons.dev.java.net/spring/>>
> > > > > > <https://jax-ws-commons.dev.java.net/spring/
> > > <https://jax-ws-commons.dev.java.net/spring/>
> > > > > <https://jax-ws-commons.dev.java.net/spring/
> > > <https://jax-ws-commons.dev.java.net/spring/>>>>
> > > > > > > >> o Pluggable Transport
> > > > > > > >> <https://jax-ws.dev.java.net/transport.html
> > > <https://jax-ws.dev.java.net/transport.html>
> > > > > <https://jax-ws.dev.java.net/transport.html
> > > <https://jax-ws.dev.java.net/transport.html>>
> > > > > > <https://jax-ws.dev.java.net/transport.html
> > > <https://jax-ws.dev.java.net/transport.html>
> > > > > <https://jax-ws.dev.java.net/transport.html
> > > <https://jax-ws.dev.java.net/transport.html>>>>
> > > > > > > >> + In-VM transport
> > > > > > > >> + Servlet transport (bundled with the RI)
> > > > > > > >> + JMS transport <http://jms-ws-transport.dev.java.net/
> > > <http://jms-ws-transport.dev.java.net/>
> > > > > <http://jms-ws-transport.dev.java.net/
> > > <http://jms-ws-transport.dev.java.net/>>
> > > > > > <http://jms-ws-transport.dev.java.net/
> > > <http://jms-ws-transport.dev.java.net/>
> > > > > <http://jms-ws-transport.dev.java.net/
> > > <http://jms-ws-transport.dev.java.net/>>>>
> > > > > > > >> + SOAP over TCP transport (part of WSIT
> > > > > > > >> <https://wsit.dev.java.net <https://wsit.dev.java.net>
> > > <https://wsit.dev.java.net <https://wsit.dev.java.net>>
> > > > > <https://wsit.dev.java.net <https://wsit.dev.java.net>
> > > <https://wsit.dev.java.net <https://wsit.dev.java.net>>>>)
> > > > > > > >> o FastInfoset (bundled with JAX-WS 2.1 RI)
> > > > > > > >> <https://fi.dev.java.net/ <https://fi.dev.java.net/>
> > > <https://fi.dev.java.net/ <https://fi.dev.java.net/>>
> > > > > <https://fi.dev.java.net/ <https://fi.dev.java.net/>
> > > <https://fi.dev.java.net/ <https://fi.dev.java.net/>>>>
> > > > > > > >> + ITU-T Rec. X.891 | ISO/IEC 24824-1
> > > > > > > >> <http://www.itu.int/rec/T-REC-X.891-200505-I/e
> > > <http://www.itu.int/rec/T-REC-X.891-200505-I/e>
> > > > > <http://www.itu.int/rec/T-REC-X.891-200505-I/e
> > > <http://www.itu.int/rec/T-REC-X.891-200505-I/e>>
> > > > > > <http://www.itu.int/rec/T-REC-X.891-200505-I/e
> > > <http://www.itu.int/rec/T-REC-X.891-200505-I/e>
> > > > > <http://www.itu.int/rec/T-REC-X.891-200505-I/e
> > > <http://www.itu.int/rec/T-REC-X.891-200505-I/e>>>>
> > > > > > > >> o JBI Service Engine and Binding Component(part of
> > > Glassfish v2)
> > > > > > > >> o HTTP Binding Component
> > > > > > > >> <http://www.glassfishwiki.org/jbiwiki/Wiki.jsp?page=HTTPBC
> > > <http://www.glassfishwiki.org/jbiwiki/Wiki.jsp?page=HTTPBC>
> > > > > <http://www.glassfishwiki.org/jbiwiki/Wiki.jsp?page=HTTPBC
> > > <http://www.glassfishwiki.org/jbiwiki/Wiki.jsp?page=HTTPBC>>
> > > > > > <http://www.glassfishwiki.org/jbiwiki/Wiki.jsp?page=HTTPBC
> > > <http://www.glassfishwiki.org/jbiwiki/Wiki.jsp?page=HTTPBC>
> > > > > <http://www.glassfishwiki.org/jbiwiki/Wiki.jsp?page=HTTPBC
> > > <http://www.glassfishwiki.org/jbiwiki/Wiki.jsp?page=HTTPBC>>>>,
> > > > > > > >> used by Open JBI component
> > > > > > > >> <https://open-jbi-components.dev.java.net/
> > > <https://open-jbi-components.dev.java.net/>
> > > > > <https://open-jbi-components.dev.java.net/
> > > <https://open-jbi-components.dev.java.net/>>
> > > > > > <https://open-jbi-components.dev.java.net/
> > > <https://open-jbi-components.dev.java.net/>
> > > > > <https://open-jbi-components.dev.java.net/
> > > <https://open-jbi-components.dev.java.net/>>>>
> > > > > > > >> * Data binding - JAXB 2.1.2 RI
> > > > > <https://jaxb.dev.java.net/2.1.2/
> > > <https://jaxb.dev.java.net/2.1.2/> <https://jaxb.dev.java.net/2.1.2/
> > > <https://jaxb.dev.java.net/2.1.2/>>
> > > > > > <https://jaxb.dev.java.net/2.1.2/
> > > <https://jaxb.dev.java.net/2.1.2/> <https://jaxb.dev.java.net/2.1.2/
> > > <https://jaxb.dev.java.net/2.1.2/>>>>
> > > > > > > >> * Server Side Asynchrony - AsyncProvider
> > > > > > > >>
> > > <https://jax-ws.dev.java.net/nonav/2.1/docs/asyncprovider.html
> > > <https://jax-ws.dev.java.net/nonav/2.1/docs/asyncprovider.html>
> > > > > <https://jax-ws.dev.java.net/nonav/2.1/docs/asyncprovider.html
> > > <https://jax-ws.dev.java.net/nonav/2.1/docs/asyncprovider.html>>
> > > > > > <https://jax-ws.dev.java.net/nonav/2.1/docs/asyncprovider.html
> > > <https://jax-ws.dev.java.net/nonav/2.1/docs/asyncprovider.html>
> > > > > <https://jax-ws.dev.java.net/nonav/2.1/docs/asyncprovider.html
> > > <https://jax-ws.dev.java.net/nonav/2.1/docs/asyncprovider.html>>>>
> > > > > > > >> * Stateful Web Services
> > > > > > > >>
> > > > > >
> > > <https://jax-ws.dev.java.net/nonav/2.1/docs/statefulWebservice.html
> > > <https://jax-ws.dev.java.net/nonav/2.1/docs/statefulWebservice.html>
> > > > >
> > > <https://jax-ws.dev.java.net/nonav/2.1/docs/statefulWebservice.html
> > > <https://jax-ws.dev.java.net/nonav/2.1/docs/statefulWebservice.html>>
> > > > > >
> > > <https://jax-ws.dev.java.net/nonav/2.1/docs/statefulWebservice.html
> > > <https://jax-ws.dev.java.net/nonav/2.1/docs/statefulWebservice.html>
> > > > >
> > > <https://jax-ws.dev.java.net/nonav/2.1/docs/statefulWebservice.html
> > > <https://jax-ws.dev.java.net/nonav/2.1/docs/statefulWebservice.html>>>>
> > > > > > > >> * Support for custom WebServiceFeature
> > > > > > > >>
> > > > > >
> > > > >
> > >
<http://weblogs.java.net/blog/ramapulavarthi/archive/2007/01/extending_jaxws.htm\
l
> > >
<http://weblogs.java.net/blog/ramapulavarthi/archive/2007/01/extending_jaxws.htm\
l>
> > > > >
> > >
<http://weblogs.java.net/blog/ramapulavarthi/archive/2007/01/extending_jaxws.htm\
l
> > >
<http://weblogs.java.net/blog/ramapulavarthi/archive/2007/01/extending_jaxws.htm\
l>>
> > > > >
> > > > > >
> > > > >
> > >
<http://weblogs.java.net/blog/ramapulavarthi/archive/2007/01/extending_jaxws.htm\
l
> > >
<http://weblogs.java.net/blog/ramapulavarthi/archive/2007/01/extending_jaxws.htm\
l>
> > > > >
> > >
<http://weblogs.java.net/blog/ramapulavarthi/archive/2007/01/extending_jaxws.htm\
l
> > >
<http://weblogs.java.net/blog/ramapulavarthi/archive/2007/01/extending_jaxws.htm\
l>>>>
> > > > > > > >> * Hosting API
> > > > > > > >>
> > > > > >
> > > > >
> > >
<https://jax-ws-architecture-document.dev.java.net/nonav/doc21/index.html?com/su\
n/xml/ws/api/server/package-summary.html
> > >
<https://jax-ws-architecture-document.dev.java.net/nonav/doc21/index.html?com/su\
n/xml/ws/api/server/package-summary.html>
> > > > >
> > >
<https://jax-ws-architecture-document.dev.java.net/nonav/doc21/index.html?com/su\
n/xml/ws/api/server/package-summary.html
> > >
<https://jax-ws-architecture-document.dev.java.net/nonav/doc21/index.html?com/su\
n/xml/ws/api/server/package-summary.html>>
> > > > >
> > > > > >
> > > > >
> > >
<https://jax-ws-architecture-document.dev.java.net/nonav/doc21/index.html?com/su\
n/xml/ws/api/server/package-summary.html
> > >
<https://jax-ws-architecture-document.dev.java.net/nonav/doc21/index.html?com/su\
n/xml/ws/api/server/package-summary.html>
> > > > >
> > >
<https://jax-ws-architecture-document.dev.java.net/nonav/doc21/index.html?com/su\
n/xml/ws/api/server/package-summary.html
> > >
<https://jax-ws-architecture-document.dev.java.net/nonav/doc21/index.html?com/su\
n/xml/ws/api/server/package-summary.html>>>>
> > > > > > > >>
> > > > > > > >> o These APIs can be used by a J2EE application server to
> > > > > > > >> integrate JAX-WS 2.1 RI for hosting JAX-WS services
> > > > > > > >> * Endpoint Deployment
> > > > > > > >> o Glassfish v2 <https://glassfish.dev.java.net
> > > <https://glassfish.dev.java.net>
> > > > > <https://glassfish.dev.java.net <https://glassfish.dev.java.net>>
> > > > > > <https://glassfish.dev.java.net <https://glassfish.dev.java.net>
> > > <https://glassfish.dev.java.net <https://glassfish.dev.java.net>>>>
> > > > > > > >> + Tightly integrated with Glassfish
> > > > > > > >> + Supports EJB and Web endpoints
> > > > > > > >> + 109 based deployment support for better portability
> > > > > > > >> + JAX-WS RI specific deployment descriptor support
> > > > > > > >> o Sun One Application Server 9.0 ur1
> > > > > > > >> <http://www.sun.com/software/products/appsrvr_pe/index.xml
> > > <http://www.sun.com/software/products/appsrvr_pe/index.xml>
> > > > > <http://www.sun.com/software/products/appsrvr_pe/index.xml
> > > <http://www.sun.com/software/products/appsrvr_pe/index.xml>>
> > > > > > <http://www.sun.com/software/products/appsrvr_pe/index.xml
> > > <http://www.sun.com/software/products/appsrvr_pe/index.xml>
> > > > > <http://www.sun.com/software/products/appsrvr_pe/index.xml
> > > <http://www.sun.com/software/products/appsrvr_pe/index.xml>>>>
> > > > > > > >> o Light weight HTTP server
> > > > > > > >> + On JDK 1.5 through http.jar distributed with the
> > > > > > > >> JAX-WS 2.1 RI bundle
> > > > > > > >> + Bundled with JDK 6
> > > > > > > >> o Any other container that supports Servlet 2.4, such as
> > > > > > > >> Tomcat, Jetty, Geronimo, JBoss, Resin, ... You name it!
> > > > > > > >>
> > > > > > > >>
> > > > > > > >>
> > > > > > > >>
> > > > > > > >> ----------------------------------------------------------
> > > > > > > >> This group is a forum for builders of SOAP implementations to
> > > > > > discuss implementation and interoperability issues. Please stay
> > > > > on-topic.
> > > > > > > >> Yahoo! Groups Links
> > > > > > > >>
> > > > > > > >>
> > > > > > > >>
> > > > > > > >>
> > > > > > > >>
> > > > > > > >>
> > > > > > > >
> > > > > > > >
> > > > > > > > ----------------------------------------------------------
> > > > > > > > This group is a forum for builders of SOAP implementations to
> > > > > > discuss implementation and interoperability issues. Please stay
> > > > > on-topic.
> > > > > > > > Yahoo! Groups Links
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > ----------------------------------------------------------
> > > > > > > This group is a forum for builders of SOAP implementations to
> > > > > > discuss implementation and interoperability issues. Please stay
> > > > > on-topic.
> > > > > > > Yahoo! Groups Links
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > > > --
> > > > > > Davanum Srinivas :: http://wso2.org/ <http://wso2.org/>
> > > <http://wso2.org/ <http://wso2.org/>>
> > > > > <http://wso2.org/ <http://wso2.org/> <http://wso2.org/
> > > <http://wso2.org/>>> :: Oxygen for
> > > > > > Web Services Developers
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > > ----------------------------------------------------------
> > > > This group is a forum for builders of SOAP implementations to
> > > discuss implementation and interoperability issues. Please stay on-topic.
> > > > Yahoo! Groups Links
> > > >
> > > >
> > > >
> > > >
> > >
> > > --
> > > Davanum Srinivas :: http://wso2.org/ <http://wso2.org/> :: Oxygen for
> > > Web Services Developers
> > >
> > >
> >
> >
> > -----------------------------------------------------------------
> > This group is a forum for builders of SOAP implementations to discuss
implementation and interoperability issues.  Please stay on-topic.
> > Yahoo! Groups Links
> >
> >
> >
> >
>
>
> --
> Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers
>


--
Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers

Yep. We did.

thanks,
dims

On 2/12/07, Doug Kohlert <doug.kohlert@...> wrote:
> Dims,
> I just found an interesting blog questioning the Axis2 benchmarks
> (http://netzooid.com/blog/2007/02/08/dodgy-benchmarks-indeed/), have you
> seen it?
>
> Davanum Srinivas wrote:
> >
> > Doug,
> >
> > There is no mention of apples-to-apples comparison on kohsuke's blog.
> > There is no mention of XMLBeans in vivek's blog. This is the first
> > time i hear this new argument that Axis2/XmlBeans is a
> > apples-to-apples comparison....
> >
> > If you really wanted to test the perf, you should compare multiple
> > options including the default settings for both stacks :) In this
> > case, it would mean Axis2/JAXB, Axis2/ADB, JAXWS-RI/JAXB. Running
> > Axis2/XMLBeans and claiming huge perf improvements is ridiculous as
> > dennis mentioned.
> >
> > -- dims
> >
> > On 2/8/07, Doug Kohlert <doug.kohlert@...
> > <mailto:doug.kohlert%40sun.com>> wrote:
> > > Oh, you are talking about the data corruption mentioned in Kohsuke's
> > > blog
> > >
> > (http://weblogs.java.net/blog/kohsuke/archive/2007/02/jaxws_ri_21_ben.html
> >
<http://weblogs.java.net/blog/kohsuke/archive/2007/02/jaxws_ri_21_ben.html>).
> > > Yea Dims, we made that up; get real dude. Kohsuke even mentioned in
> > > his blog that we were not sure why it happened and that it might even be
> > > a Glassfish issue.
> > >
> > > Doug Kohlert wrote:
> > > >
> > > > What data corruption are you talking about? I didn't mention anything
> > > > about data corruption.
> > > >
> > > > Davanum Srinivas wrote:
> > > > >
> > > > > Doug,
> > > > >
> > > > > Nice party line! So the ADB data corruption issue was something you
> > > > > made up? Or did it really happen?
> > > > >
> > > > > -- dims
> > > > >
> > > > > On 2/8/07, Doug Kohlert <doug.kohlert@...
> > <mailto:doug.kohlert%40sun.com>
> > > > <mailto:doug.kohlert%40sun.com>
> > > > > <mailto:doug.kohlert%40sun.com>> wrote:
> > > > > > Good point, you may want to post your comment to Vivek's blog.
> > That
> > > > > > said, since there are limitations in both
> > > > > > ADB and JiBX when compiling schema to Java, we felt this was
> > the most
> > > > > > appropriate match of capabilities.
> > > > > > So this benchmark really is more of an apples-to-apples comparison
> > > > > > rather than an apples-to-oranges comparison that you suggest.
> > > > > >
> > > > > > Dennis Sosnoski wrote:
> > > > > > > "Benchmarking" against Axis2-XMLBeans (as shown in the linked
> > > > blog) is
> > > > > > > ridiculous. XMLBeans is much slower than either ADB or JiBX data
> > > > > binding
> > > > > > > for Axis2. If you're going to make performance claims for your
> > > > > software,
> > > > > > > at least try to make the tests half way reasonable.
> > > > > > >
> > > > > > > - Dennis
> > > > > > >
> > > > > > > Dennis M. Sosnoski
> > > > > > > SOA and Web Services in Java
> > > > > > > Training and Consulting
> > > > > > > http://www.sosnoski.com <http://www.sosnoski.com>
> > <http://www.sosnoski.com <http://www.sosnoski.com>>
> > > > <http://www.sosnoski.com <http://www.sosnoski.com>
> > <http://www.sosnoski.com <http://www.sosnoski.com>>> -
> > > > > http://www.sosnoski.co.nz <http://www.sosnoski.co.nz>
> > <http://www.sosnoski.co.nz <http://www.sosnoski.co.nz>>
> > > > <http://www.sosnoski.co.nz <http://www.sosnoski.co.nz>
> > <http://www.sosnoski.co.nz <http://www.sosnoski.co.nz>>>
> > > > > > > Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > Doug Kohlert wrote:
> > > > > > >
> > > > > > >> We are proud to announce the release of JAX-WS 2.1 RI FCS.
> > JAX-WS
> > > > > 2.1 is
> > > > > > >> a major re-architecture over JAX-WS 2.0 without changing the
> > > > standard
> > > > > > >> JAX-WS APIs or programming model. The benefits of this is a
> > > > very fast
> > > > > > >> implementation and an extremely flexible, extensible
> > > > architecture. To
> > > > > > >> read more about how fast the RI is and the new functionality
> > > > that it
> > > > > > >> contains, read Vivek's blog at:
> > > > > > >>
> > > > >
> > > >
> > http://weblogs.java.net/blog/vivekp/archive/2007/02/jaxws_21_fcs_fa_1.html
> > <http://weblogs.java.net/blog/vivekp/archive/2007/02/jaxws_21_fcs_fa_1.html>
> > > >
> > <http://weblogs.java.net/blog/vivekp/archive/2007/02/jaxws_21_fcs_fa_1.html
> >
<http://weblogs.java.net/blog/vivekp/archive/2007/02/jaxws_21_fcs_fa_1.html>>
> > > >
> > > > >
> > > >
> > <http://weblogs.java.net/blog/vivekp/archive/2007/02/jaxws_21_fcs_fa_1.html
> > <http://weblogs.java.net/blog/vivekp/archive/2007/02/jaxws_21_fcs_fa_1.html>
> > > >
> > <http://weblogs.java.net/blog/vivekp/archive/2007/02/jaxws_21_fcs_fa_1.html
> >
<http://weblogs.java.net/blog/vivekp/archive/2007/02/jaxws_21_fcs_fa_1.html>>>
> > > > > > >>
> > > > > > >> Here is an excerpt from Vivek's blog about the Key Features.
> > > > > > >>
> > > > > > >> * Reference Implementation (RI) of JAX-WS 2.1. Full JAX-WS 2.1
> > > > > > >> Specification <http://jcp.org/en/jsr/detail?id=224
> > <http://jcp.org/en/jsr/detail?id=224>
> > > > <http://jcp.org/en/jsr/detail?id=224
> > <http://jcp.org/en/jsr/detail?id=224>>
> > > > > <http://jcp.org/en/jsr/detail?id=224
> > <http://jcp.org/en/jsr/detail?id=224>
> > > > <http://jcp.org/en/jsr/detail?id=224
> > <http://jcp.org/en/jsr/detail?id=224>>>> compliance
> > > > > > >> * Development Tools
> > > > > > >> o WSDL to Java generator
> > > > > > >> + Wsimport command line tool
> > > > > > >> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimport.html
> > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimport.html>
> > > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimport.html
> > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimport.html>>
> > > > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimport.html
> > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimport.html>
> > > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimport.html
> > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimport.html>>>>,
> > > > > > >> ant task
> > > > > > >>
> > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimportant.html
> > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimportant.html>
> > > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimportant.html
> > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimportant.html>>
> > > > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimportant.html
> > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimportant.html>
> > > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimportant.html
> > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimportant.html>>>>
> > > > > > >> and Maven2 plugin
> > > > > > >> <http://mojo.codehaus.org/jaxws-maven-plugin/index.html
> > <http://mojo.codehaus.org/jaxws-maven-plugin/index.html>
> > > > <http://mojo.codehaus.org/jaxws-maven-plugin/index.html
> > <http://mojo.codehaus.org/jaxws-maven-plugin/index.html>>
> > > > > <http://mojo.codehaus.org/jaxws-maven-plugin/index.html
> > <http://mojo.codehaus.org/jaxws-maven-plugin/index.html>
> > > > <http://mojo.codehaus.org/jaxws-maven-plugin/index.html
> > <http://mojo.codehaus.org/jaxws-maven-plugin/index.html>>>>
> > > > > > >> o Java to WSDL generator
> > > > > > >> + Wsgen command line tool
> > > > > > >> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgen.html
> > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgen.html>
> > > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgen.html
> > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgen.html>>
> > > > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgen.html
> > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgen.html>
> > > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgen.html
> > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgen.html>>>>,
> > > > > > >> ant Task
> > > > > > >> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgenant.html
> > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgenant.html>
> > > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgenant.html
> > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgenant.html>>
> > > > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgenant.html
> > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgenant.html>
> > > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgenant.html
> > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgenant.html>>>>
> > > > > > >> and Maven2 plugin
> > > > > > >> <http://mojo.codehaus.org/jaxws-maven-plugin/index.html
> > <http://mojo.codehaus.org/jaxws-maven-plugin/index.html>
> > > > <http://mojo.codehaus.org/jaxws-maven-plugin/index.html
> > <http://mojo.codehaus.org/jaxws-maven-plugin/index.html>>
> > > > > <http://mojo.codehaus.org/jaxws-maven-plugin/index.html
> > <http://mojo.codehaus.org/jaxws-maven-plugin/index.html>
> > > > <http://mojo.codehaus.org/jaxws-maven-plugin/index.html
> > <http://mojo.codehaus.org/jaxws-maven-plugin/index.html>>>>
> > > > > > >> o Integrated with NetBeans 5.5.1
> > > > > > >> <http://www.netbeans.info/downloads/dev.php
> > <http://www.netbeans.info/downloads/dev.php>
> > > > <http://www.netbeans.info/downloads/dev.php
> > <http://www.netbeans.info/downloads/dev.php>>
> > > > > <http://www.netbeans.info/downloads/dev.php
> > <http://www.netbeans.info/downloads/dev.php>
> > > > <http://www.netbeans.info/downloads/dev.php
> > <http://www.netbeans.info/downloads/dev.php>>>>
> > > > > > >> * Standards
> > > > > > >> o Web Services Addressing 1.0 - Core, SOAP Binding and WSDL
> > > > > > >> Binding
> > > > > > >> o WS-Addressing - Member Submission
> > > > > > >> o SOAP 1.1 and 1.2
> > > > > > >> o REST and XML/HTTP
> > > > > > >> o WS-I Basic Profile 1.1, Simple SOAP Binding Profile 1.0 and
> > > > > > >> Attachment Profile 1.0
> > > > > > >> o MTOM
> > > > > > >> * Extensions (May not be final unless says so)
> > > > > > >> o Web Services Interoperable Technologies ( WSIT
> > > > > > >> <https://wsit.dev.java.net/index.html#downloads
> > <https://wsit.dev.java.net/index.html#downloads>
> > > > <https://wsit.dev.java.net/index.html#downloads
> > <https://wsit.dev.java.net/index.html#downloads>>
> > > > > <https://wsit.dev.java.net/index.html#downloads
> > <https://wsit.dev.java.net/index.html#downloads>
> > > > <https://wsit.dev.java.net/index.html#downloads
> > <https://wsit.dev.java.net/index.html#downloads>>>>) - enables
> > > > > > >> .NET 3.0 interoperability
> > > > > > >> + WS-ReliableMessaging
> > > > > > >> + WS-Policy
> > > > > > >> + WS-MEX
> > > > > > >> + WS-Security/WS-Security Policy
> > > > > > >> + WS-Trust/WS-Secure Conversation
> > > > > > >> + WS-AT/WS-Tx (Supported only on Glassfish v2)
> > > > > > >> + SOAP/TCP
> > > > > > >> o Spring support
> > <https://jax-ws-commons.dev.java.net/spring/
> > <https://jax-ws-commons.dev.java.net/spring/>
> > > > <https://jax-ws-commons.dev.java.net/spring/
> > <https://jax-ws-commons.dev.java.net/spring/>>
> > > > > <https://jax-ws-commons.dev.java.net/spring/
> > <https://jax-ws-commons.dev.java.net/spring/>
> > > > <https://jax-ws-commons.dev.java.net/spring/
> > <https://jax-ws-commons.dev.java.net/spring/>>>>
> > > > > > >> o Pluggable Transport
> > > > > > >> <https://jax-ws.dev.java.net/transport.html
> > <https://jax-ws.dev.java.net/transport.html>
> > > > <https://jax-ws.dev.java.net/transport.html
> > <https://jax-ws.dev.java.net/transport.html>>
> > > > > <https://jax-ws.dev.java.net/transport.html
> > <https://jax-ws.dev.java.net/transport.html>
> > > > <https://jax-ws.dev.java.net/transport.html
> > <https://jax-ws.dev.java.net/transport.html>>>>
> > > > > > >> + In-VM transport
> > > > > > >> + Servlet transport (bundled with the RI)
> > > > > > >> + JMS transport <http://jms-ws-transport.dev.java.net/
> > <http://jms-ws-transport.dev.java.net/>
> > > > <http://jms-ws-transport.dev.java.net/
> > <http://jms-ws-transport.dev.java.net/>>
> > > > > <http://jms-ws-transport.dev.java.net/
> > <http://jms-ws-transport.dev.java.net/>
> > > > <http://jms-ws-transport.dev.java.net/
> > <http://jms-ws-transport.dev.java.net/>>>>
> > > > > > >> + SOAP over TCP transport (part of WSIT
> > > > > > >> <https://wsit.dev.java.net <https://wsit.dev.java.net>
> > <https://wsit.dev.java.net <https://wsit.dev.java.net>>
> > > > <https://wsit.dev.java.net <https://wsit.dev.java.net>
> > <https://wsit.dev.java.net <https://wsit.dev.java.net>>>>)
> > > > > > >> o FastInfoset (bundled with JAX-WS 2.1 RI)
> > > > > > >> <https://fi.dev.java.net/ <https://fi.dev.java.net/>
> > <https://fi.dev.java.net/ <https://fi.dev.java.net/>>
> > > > <https://fi.dev.java.net/ <https://fi.dev.java.net/>
> > <https://fi.dev.java.net/ <https://fi.dev.java.net/>>>>
> > > > > > >> + ITU-T Rec. X.891 | ISO/IEC 24824-1
> > > > > > >> <http://www.itu.int/rec/T-REC-X.891-200505-I/e
> > <http://www.itu.int/rec/T-REC-X.891-200505-I/e>
> > > > <http://www.itu.int/rec/T-REC-X.891-200505-I/e
> > <http://www.itu.int/rec/T-REC-X.891-200505-I/e>>
> > > > > <http://www.itu.int/rec/T-REC-X.891-200505-I/e
> > <http://www.itu.int/rec/T-REC-X.891-200505-I/e>
> > > > <http://www.itu.int/rec/T-REC-X.891-200505-I/e
> > <http://www.itu.int/rec/T-REC-X.891-200505-I/e>>>>
> > > > > > >> o JBI Service Engine and Binding Component(part of
> > Glassfish v2)
> > > > > > >> o HTTP Binding Component
> > > > > > >> <http://www.glassfishwiki.org/jbiwiki/Wiki.jsp?page=HTTPBC
> > <http://www.glassfishwiki.org/jbiwiki/Wiki.jsp?page=HTTPBC>
> > > > <http://www.glassfishwiki.org/jbiwiki/Wiki.jsp?page=HTTPBC
> > <http://www.glassfishwiki.org/jbiwiki/Wiki.jsp?page=HTTPBC>>
> > > > > <http://www.glassfishwiki.org/jbiwiki/Wiki.jsp?page=HTTPBC
> > <http://www.glassfishwiki.org/jbiwiki/Wiki.jsp?page=HTTPBC>
> > > > <http://www.glassfishwiki.org/jbiwiki/Wiki.jsp?page=HTTPBC
> > <http://www.glassfishwiki.org/jbiwiki/Wiki.jsp?page=HTTPBC>>>>,
> > > > > > >> used by Open JBI component
> > > > > > >> <https://open-jbi-components.dev.java.net/
> > <https://open-jbi-components.dev.java.net/>
> > > > <https://open-jbi-components.dev.java.net/
> > <https://open-jbi-components.dev.java.net/>>
> > > > > <https://open-jbi-components.dev.java.net/
> > <https://open-jbi-components.dev.java.net/>
> > > > <https://open-jbi-components.dev.java.net/
> > <https://open-jbi-components.dev.java.net/>>>>
> > > > > > >> * Data binding - JAXB 2.1.2 RI
> > > > <https://jaxb.dev.java.net/2.1.2/
> > <https://jaxb.dev.java.net/2.1.2/> <https://jaxb.dev.java.net/2.1.2/
> > <https://jaxb.dev.java.net/2.1.2/>>
> > > > > <https://jaxb.dev.java.net/2.1.2/
> > <https://jaxb.dev.java.net/2.1.2/> <https://jaxb.dev.java.net/2.1.2/
> > <https://jaxb.dev.java.net/2.1.2/>>>>
> > > > > > >> * Server Side Asynchrony - AsyncProvider
> > > > > > >>
> > <https://jax-ws.dev.java.net/nonav/2.1/docs/asyncprovider.html
> > <https://jax-ws.dev.java.net/nonav/2.1/docs/asyncprovider.html>
> > > > <https://jax-ws.dev.java.net/nonav/2.1/docs/asyncprovider.html
> > <https://jax-ws.dev.java.net/nonav/2.1/docs/asyncprovider.html>>
> > > > > <https://jax-ws.dev.java.net/nonav/2.1/docs/asyncprovider.html
> > <https://jax-ws.dev.java.net/nonav/2.1/docs/asyncprovider.html>
> > > > <https://jax-ws.dev.java.net/nonav/2.1/docs/asyncprovider.html
> > <https://jax-ws.dev.java.net/nonav/2.1/docs/asyncprovider.html>>>>
> > > > > > >> * Stateful Web Services
> > > > > > >>
> > > > >
> > <https://jax-ws.dev.java.net/nonav/2.1/docs/statefulWebservice.html
> > <https://jax-ws.dev.java.net/nonav/2.1/docs/statefulWebservice.html>
> > > >
> > <https://jax-ws.dev.java.net/nonav/2.1/docs/statefulWebservice.html
> > <https://jax-ws.dev.java.net/nonav/2.1/docs/statefulWebservice.html>>
> > > > >
> > <https://jax-ws.dev.java.net/nonav/2.1/docs/statefulWebservice.html
> > <https://jax-ws.dev.java.net/nonav/2.1/docs/statefulWebservice.html>
> > > >
> > <https://jax-ws.dev.java.net/nonav/2.1/docs/statefulWebservice.html
> > <https://jax-ws.dev.java.net/nonav/2.1/docs/statefulWebservice.html>>>>
> > > > > > >> * Support for custom WebServiceFeature
> > > > > > >>
> > > > >
> > > >
> >
<http://weblogs.java.net/blog/ramapulavarthi/archive/2007/01/extending_jaxws.htm\
l
> >
<http://weblogs.java.net/blog/ramapulavarthi/archive/2007/01/extending_jaxws.htm\
l>
> > > >
> >
<http://weblogs.java.net/blog/ramapulavarthi/archive/2007/01/extending_jaxws.htm\
l
> >
<http://weblogs.java.net/blog/ramapulavarthi/archive/2007/01/extending_jaxws.htm\
l>>
> > > >
> > > > >
> > > >
> >
<http://weblogs.java.net/blog/ramapulavarthi/archive/2007/01/extending_jaxws.htm\
l
> >
<http://weblogs.java.net/blog/ramapulavarthi/archive/2007/01/extending_jaxws.htm\
l>
> > > >
> >
<http://weblogs.java.net/blog/ramapulavarthi/archive/2007/01/extending_jaxws.htm\
l
> >
<http://weblogs.java.net/blog/ramapulavarthi/archive/2007/01/extending_jaxws.htm\
l>>>>
> > > > > > >> * Hosting API
> > > > > > >>
> > > > >
> > > >
> >
<https://jax-ws-architecture-document.dev.java.net/nonav/doc21/index.html?com/su\
n/xml/ws/api/server/package-summary.html
> >
<https://jax-ws-architecture-document.dev.java.net/nonav/doc21/index.html?com/su\
n/xml/ws/api/server/package-summary.html>
> > > >
> >
<https://jax-ws-architecture-document.dev.java.net/nonav/doc21/index.html?com/su\
n/xml/ws/api/server/package-summary.html
> >
<https://jax-ws-architecture-document.dev.java.net/nonav/doc21/index.html?com/su\
n/xml/ws/api/server/package-summary.html>>
> > > >
> > > > >
> > > >
> >
<https://jax-ws-architecture-document.dev.java.net/nonav/doc21/index.html?com/su\
n/xml/ws/api/server/package-summary.html
> >
<https://jax-ws-architecture-document.dev.java.net/nonav/doc21/index.html?com/su\
n/xml/ws/api/server/package-summary.html>
> > > >
> >
<https://jax-ws-architecture-document.dev.java.net/nonav/doc21/index.html?com/su\
n/xml/ws/api/server/package-summary.html
> >
<https://jax-ws-architecture-document.dev.java.net/nonav/doc21/index.html?com/su\
n/xml/ws/api/server/package-summary.html>>>>
> > > > > > >>
> > > > > > >> o These APIs can be used by a J2EE application server to
> > > > > > >> integrate JAX-WS 2.1 RI for hosting JAX-WS services
> > > > > > >> * Endpoint Deployment
> > > > > > >> o Glassfish v2 <https://glassfish.dev.java.net
> > <https://glassfish.dev.java.net>
> > > > <https://glassfish.dev.java.net <https://glassfish.dev.java.net>>
> > > > > <https://glassfish.dev.java.net <https://glassfish.dev.java.net>
> > <https://glassfish.dev.java.net <https://glassfish.dev.java.net>>>>
> > > > > > >> + Tightly integrated with Glassfish
> > > > > > >> + Supports EJB and Web endpoints
> > > > > > >> + 109 based deployment support for better portability
> > > > > > >> + JAX-WS RI specific deployment descriptor support
> > > > > > >> o Sun One Application Server 9.0 ur1
> > > > > > >> <http://www.sun.com/software/products/appsrvr_pe/index.xml
> > <http://www.sun.com/software/products/appsrvr_pe/index.xml>
> > > > <http://www.sun.com/software/products/appsrvr_pe/index.xml
> > <http://www.sun.com/software/products/appsrvr_pe/index.xml>>
> > > > > <http://www.sun.com/software/products/appsrvr_pe/index.xml
> > <http://www.sun.com/software/products/appsrvr_pe/index.xml>
> > > > <http://www.sun.com/software/products/appsrvr_pe/index.xml
> > <http://www.sun.com/software/products/appsrvr_pe/index.xml>>>>
> > > > > > >> o Light weight HTTP server
> > > > > > >> + On JDK 1.5 through http.jar distributed with the
> > > > > > >> JAX-WS 2.1 RI bundle
> > > > > > >> + Bundled with JDK 6
> > > > > > >> o Any other container that supports Servlet 2.4, such as
> > > > > > >> Tomcat, Jetty, Geronimo, JBoss, Resin, ... You name it!
> > > > > > >>
> > > > > > >>
> > > > > > >>
> > > > > > >>
> > > > > > >> ----------------------------------------------------------
> > > > > > >> This group is a forum for builders of SOAP implementations to
> > > > > discuss implementation and interoperability issues. Please stay
> > > > on-topic.
> > > > > > >> Yahoo! Groups Links
> > > > > > >>
> > > > > > >>
> > > > > > >>
> > > > > > >>
> > > > > > >>
> > > > > > >>
> > > > > > >
> > > > > > >
> > > > > > > ----------------------------------------------------------
> > > > > > > This group is a forum for builders of SOAP implementations to
> > > > > discuss implementation and interoperability issues. Please stay
> > > > on-topic.
> > > > > > > Yahoo! Groups Links
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > > ----------------------------------------------------------
> > > > > > This group is a forum for builders of SOAP implementations to
> > > > > discuss implementation and interoperability issues. Please stay
> > > > on-topic.
> > > > > > Yahoo! Groups Links
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > > --
> > > > > Davanum Srinivas :: http://wso2.org/ <http://wso2.org/>
> > <http://wso2.org/ <http://wso2.org/>>
> > > > <http://wso2.org/ <http://wso2.org/> <http://wso2.org/
> > <http://wso2.org/>>> :: Oxygen for
> > > > > Web Services Developers
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> > > ----------------------------------------------------------
> > > This group is a forum for builders of SOAP implementations to
> > discuss implementation and interoperability issues. Please stay on-topic.
> > > Yahoo! Groups Links
> > >
> > >
> > >
> > >
> >
> > --
> > Davanum Srinivas :: http://wso2.org/ <http://wso2.org/> :: Oxygen for
> > Web Services Developers
> >
> >
>
>
> -----------------------------------------------------------------
> This group is a forum for builders of SOAP implementations to discuss
implementation and interoperability issues.  Please stay on-topic.
> Yahoo! Groups Links
>
>
>
>


--
Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers

Dims,
I just found an interesting blog questioning the Axis2 benchmarks
(http://netzooid.com/blog/2007/02/08/dodgy-benchmarks-indeed/), have you
seen it?

Davanum Srinivas wrote:
>
> Doug,
>
> There is no mention of apples-to-apples comparison on kohsuke's blog.
> There is no mention of XMLBeans in vivek's blog. This is the first
> time i hear this new argument that Axis2/XmlBeans is a
> apples-to-apples comparison....
>
> If you really wanted to test the perf, you should compare multiple
> options including the default settings for both stacks :) In this
> case, it would mean Axis2/JAXB, Axis2/ADB, JAXWS-RI/JAXB. Running
> Axis2/XMLBeans and claiming huge perf improvements is ridiculous as
> dennis mentioned.
>
> -- dims
>
> On 2/8/07, Doug Kohlert <doug.kohlert@...
> <mailto:doug.kohlert%40sun.com>> wrote:
> > Oh, you are talking about the data corruption mentioned in Kohsuke's
> > blog
> >
> (http://weblogs.java.net/blog/kohsuke/archive/2007/02/jaxws_ri_21_ben.html
> <http://weblogs.java.net/blog/kohsuke/archive/2007/02/jaxws_ri_21_ben.html>).
> > Yea Dims, we made that up; get real dude. Kohsuke even mentioned in
> > his blog that we were not sure why it happened and that it might even be
> > a Glassfish issue.
> >
> > Doug Kohlert wrote:
> > >
> > > What data corruption are you talking about? I didn't mention anything
> > > about data corruption.
> > >
> > > Davanum Srinivas wrote:
> > > >
> > > > Doug,
> > > >
> > > > Nice party line! So the ADB data corruption issue was something you
> > > > made up? Or did it really happen?
> > > >
> > > > -- dims
> > > >
> > > > On 2/8/07, Doug Kohlert <doug.kohlert@...
> <mailto:doug.kohlert%40sun.com>
> > > <mailto:doug.kohlert%40sun.com>
> > > > <mailto:doug.kohlert%40sun.com>> wrote:
> > > > > Good point, you may want to post your comment to Vivek's blog.
> That
> > > > > said, since there are limitations in both
> > > > > ADB and JiBX when compiling schema to Java, we felt this was
> the most
> > > > > appropriate match of capabilities.
> > > > > So this benchmark really is more of an apples-to-apples comparison
> > > > > rather than an apples-to-oranges comparison that you suggest.
> > > > >
> > > > > Dennis Sosnoski wrote:
> > > > > > "Benchmarking" against Axis2-XMLBeans (as shown in the linked
> > > blog) is
> > > > > > ridiculous. XMLBeans is much slower than either ADB or JiBX data
> > > > binding
> > > > > > for Axis2. If you're going to make performance claims for your
> > > > software,
> > > > > > at least try to make the tests half way reasonable.
> > > > > >
> > > > > > - Dennis
> > > > > >
> > > > > > Dennis M. Sosnoski
> > > > > > SOA and Web Services in Java
> > > > > > Training and Consulting
> > > > > > http://www.sosnoski.com <http://www.sosnoski.com>
> <http://www.sosnoski.com <http://www.sosnoski.com>>
> > > <http://www.sosnoski.com <http://www.sosnoski.com>
> <http://www.sosnoski.com <http://www.sosnoski.com>>> -
> > > > http://www.sosnoski.co.nz <http://www.sosnoski.co.nz>
> <http://www.sosnoski.co.nz <http://www.sosnoski.co.nz>>
> > > <http://www.sosnoski.co.nz <http://www.sosnoski.co.nz>
> <http://www.sosnoski.co.nz <http://www.sosnoski.co.nz>>>
> > > > > > Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117
> > > > > >
> > > > > >
> > > > > >
> > > > > > Doug Kohlert wrote:
> > > > > >
> > > > > >> We are proud to announce the release of JAX-WS 2.1 RI FCS.
> JAX-WS
> > > > 2.1 is
> > > > > >> a major re-architecture over JAX-WS 2.0 without changing the
> > > standard
> > > > > >> JAX-WS APIs or programming model. The benefits of this is a
> > > very fast
> > > > > >> implementation and an extremely flexible, extensible
> > > architecture. To
> > > > > >> read more about how fast the RI is and the new functionality
> > > that it
> > > > > >> contains, read Vivek's blog at:
> > > > > >>
> > > >
> > >
> http://weblogs.java.net/blog/vivekp/archive/2007/02/jaxws_21_fcs_fa_1.html
> <http://weblogs.java.net/blog/vivekp/archive/2007/02/jaxws_21_fcs_fa_1.html>
> > >
> <http://weblogs.java.net/blog/vivekp/archive/2007/02/jaxws_21_fcs_fa_1.html
> <http://weblogs.java.net/blog/vivekp/archive/2007/02/jaxws_21_fcs_fa_1.html>>
> > >
> > > >
> > >
> <http://weblogs.java.net/blog/vivekp/archive/2007/02/jaxws_21_fcs_fa_1.html
> <http://weblogs.java.net/blog/vivekp/archive/2007/02/jaxws_21_fcs_fa_1.html>
> > >
> <http://weblogs.java.net/blog/vivekp/archive/2007/02/jaxws_21_fcs_fa_1.html
> <http://weblogs.java.net/blog/vivekp/archive/2007/02/jaxws_21_fcs_fa_1.html>>>
> > > > > >>
> > > > > >> Here is an excerpt from Vivek's blog about the Key Features.
> > > > > >>
> > > > > >> * Reference Implementation (RI) of JAX-WS 2.1. Full JAX-WS 2.1
> > > > > >> Specification <http://jcp.org/en/jsr/detail?id=224
> <http://jcp.org/en/jsr/detail?id=224>
> > > <http://jcp.org/en/jsr/detail?id=224
> <http://jcp.org/en/jsr/detail?id=224>>
> > > > <http://jcp.org/en/jsr/detail?id=224
> <http://jcp.org/en/jsr/detail?id=224>
> > > <http://jcp.org/en/jsr/detail?id=224
> <http://jcp.org/en/jsr/detail?id=224>>>> compliance
> > > > > >> * Development Tools
> > > > > >> o WSDL to Java generator
> > > > > >> + Wsimport command line tool
> > > > > >> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimport.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimport.html>
> > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimport.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimport.html>>
> > > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimport.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimport.html>
> > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimport.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimport.html>>>>,
> > > > > >> ant task
> > > > > >>
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimportant.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimportant.html>
> > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimportant.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimportant.html>>
> > > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimportant.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimportant.html>
> > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimportant.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimportant.html>>>>
> > > > > >> and Maven2 plugin
> > > > > >> <http://mojo.codehaus.org/jaxws-maven-plugin/index.html
> <http://mojo.codehaus.org/jaxws-maven-plugin/index.html>
> > > <http://mojo.codehaus.org/jaxws-maven-plugin/index.html
> <http://mojo.codehaus.org/jaxws-maven-plugin/index.html>>
> > > > <http://mojo.codehaus.org/jaxws-maven-plugin/index.html
> <http://mojo.codehaus.org/jaxws-maven-plugin/index.html>
> > > <http://mojo.codehaus.org/jaxws-maven-plugin/index.html
> <http://mojo.codehaus.org/jaxws-maven-plugin/index.html>>>>
> > > > > >> o Java to WSDL generator
> > > > > >> + Wsgen command line tool
> > > > > >> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgen.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgen.html>
> > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgen.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgen.html>>
> > > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgen.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgen.html>
> > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgen.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgen.html>>>>,
> > > > > >> ant Task
> > > > > >> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgenant.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgenant.html>
> > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgenant.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgenant.html>>
> > > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgenant.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgenant.html>
> > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgenant.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgenant.html>>>>
> > > > > >> and Maven2 plugin
> > > > > >> <http://mojo.codehaus.org/jaxws-maven-plugin/index.html
> <http://mojo.codehaus.org/jaxws-maven-plugin/index.html>
> > > <http://mojo.codehaus.org/jaxws-maven-plugin/index.html
> <http://mojo.codehaus.org/jaxws-maven-plugin/index.html>>
> > > > <http://mojo.codehaus.org/jaxws-maven-plugin/index.html
> <http://mojo.codehaus.org/jaxws-maven-plugin/index.html>
> > > <http://mojo.codehaus.org/jaxws-maven-plugin/index.html
> <http://mojo.codehaus.org/jaxws-maven-plugin/index.html>>>>
> > > > > >> o Integrated with NetBeans 5.5.1
> > > > > >> <http://www.netbeans.info/downloads/dev.php
> <http://www.netbeans.info/downloads/dev.php>
> > > <http://www.netbeans.info/downloads/dev.php
> <http://www.netbeans.info/downloads/dev.php>>
> > > > <http://www.netbeans.info/downloads/dev.php
> <http://www.netbeans.info/downloads/dev.php>
> > > <http://www.netbeans.info/downloads/dev.php
> <http://www.netbeans.info/downloads/dev.php>>>>
> > > > > >> * Standards
> > > > > >> o Web Services Addressing 1.0 - Core, SOAP Binding and WSDL
> > > > > >> Binding
> > > > > >> o WS-Addressing - Member Submission
> > > > > >> o SOAP 1.1 and 1.2
> > > > > >> o REST and XML/HTTP
> > > > > >> o WS-I Basic Profile 1.1, Simple SOAP Binding Profile 1.0 and
> > > > > >> Attachment Profile 1.0
> > > > > >> o MTOM
> > > > > >> * Extensions (May not be final unless says so)
> > > > > >> o Web Services Interoperable Technologies ( WSIT
> > > > > >> <https://wsit.dev.java.net/index.html#downloads
> <https://wsit.dev.java.net/index.html#downloads>
> > > <https://wsit.dev.java.net/index.html#downloads
> <https://wsit.dev.java.net/index.html#downloads>>
> > > > <https://wsit.dev.java.net/index.html#downloads
> <https://wsit.dev.java.net/index.html#downloads>
> > > <https://wsit.dev.java.net/index.html#downloads
> <https://wsit.dev.java.net/index.html#downloads>>>>) - enables
> > > > > >> .NET 3.0 interoperability
> > > > > >> + WS-ReliableMessaging
> > > > > >> + WS-Policy
> > > > > >> + WS-MEX
> > > > > >> + WS-Security/WS-Security Policy
> > > > > >> + WS-Trust/WS-Secure Conversation
> > > > > >> + WS-AT/WS-Tx (Supported only on Glassfish v2)
> > > > > >> + SOAP/TCP
> > > > > >> o Spring support
> <https://jax-ws-commons.dev.java.net/spring/
> <https://jax-ws-commons.dev.java.net/spring/>
> > > <https://jax-ws-commons.dev.java.net/spring/
> <https://jax-ws-commons.dev.java.net/spring/>>
> > > > <https://jax-ws-commons.dev.java.net/spring/
> <https://jax-ws-commons.dev.java.net/spring/>
> > > <https://jax-ws-commons.dev.java.net/spring/
> <https://jax-ws-commons.dev.java.net/spring/>>>>
> > > > > >> o Pluggable Transport
> > > > > >> <https://jax-ws.dev.java.net/transport.html
> <https://jax-ws.dev.java.net/transport.html>
> > > <https://jax-ws.dev.java.net/transport.html
> <https://jax-ws.dev.java.net/transport.html>>
> > > > <https://jax-ws.dev.java.net/transport.html
> <https://jax-ws.dev.java.net/transport.html>
> > > <https://jax-ws.dev.java.net/transport.html
> <https://jax-ws.dev.java.net/transport.html>>>>
> > > > > >> + In-VM transport
> > > > > >> + Servlet transport (bundled with the RI)
> > > > > >> + JMS transport <http://jms-ws-transport.dev.java.net/
> <http://jms-ws-transport.dev.java.net/>
> > > <http://jms-ws-transport.dev.java.net/
> <http://jms-ws-transport.dev.java.net/>>
> > > > <http://jms-ws-transport.dev.java.net/
> <http://jms-ws-transport.dev.java.net/>
> > > <http://jms-ws-transport.dev.java.net/
> <http://jms-ws-transport.dev.java.net/>>>>
> > > > > >> + SOAP over TCP transport (part of WSIT
> > > > > >> <https://wsit.dev.java.net <https://wsit.dev.java.net>
> <https://wsit.dev.java.net <https://wsit.dev.java.net>>
> > > <https://wsit.dev.java.net <https://wsit.dev.java.net>
> <https://wsit.dev.java.net <https://wsit.dev.java.net>>>>)
> > > > > >> o FastInfoset (bundled with JAX-WS 2.1 RI)
> > > > > >> <https://fi.dev.java.net/ <https://fi.dev.java.net/>
> <https://fi.dev.java.net/ <https://fi.dev.java.net/>>
> > > <https://fi.dev.java.net/ <https://fi.dev.java.net/>
> <https://fi.dev.java.net/ <https://fi.dev.java.net/>>>>
> > > > > >> + ITU-T Rec. X.891 | ISO/IEC 24824-1
> > > > > >> <http://www.itu.int/rec/T-REC-X.891-200505-I/e
> <http://www.itu.int/rec/T-REC-X.891-200505-I/e>
> > > <http://www.itu.int/rec/T-REC-X.891-200505-I/e
> <http://www.itu.int/rec/T-REC-X.891-200505-I/e>>
> > > > <http://www.itu.int/rec/T-REC-X.891-200505-I/e
> <http://www.itu.int/rec/T-REC-X.891-200505-I/e>
> > > <http://www.itu.int/rec/T-REC-X.891-200505-I/e
> <http://www.itu.int/rec/T-REC-X.891-200505-I/e>>>>
> > > > > >> o JBI Service Engine and Binding Component(part of
> Glassfish v2)
> > > > > >> o HTTP Binding Component
> > > > > >> <http://www.glassfishwiki.org/jbiwiki/Wiki.jsp?page=HTTPBC
> <http://www.glassfishwiki.org/jbiwiki/Wiki.jsp?page=HTTPBC>
> > > <http://www.glassfishwiki.org/jbiwiki/Wiki.jsp?page=HTTPBC
> <http://www.glassfishwiki.org/jbiwiki/Wiki.jsp?page=HTTPBC>>
> > > > <http://www.glassfishwiki.org/jbiwiki/Wiki.jsp?page=HTTPBC
> <http://www.glassfishwiki.org/jbiwiki/Wiki.jsp?page=HTTPBC>
> > > <http://www.glassfishwiki.org/jbiwiki/Wiki.jsp?page=HTTPBC
> <http://www.glassfishwiki.org/jbiwiki/Wiki.jsp?page=HTTPBC>>>>,
> > > > > >> used by Open JBI component
> > > > > >> <https://open-jbi-components.dev.java.net/
> <https://open-jbi-components.dev.java.net/>
> > > <https://open-jbi-components.dev.java.net/
> <https://open-jbi-components.dev.java.net/>>
> > > > <https://open-jbi-components.dev.java.net/
> <https://open-jbi-components.dev.java.net/>
> > > <https://open-jbi-components.dev.java.net/
> <https://open-jbi-components.dev.java.net/>>>>
> > > > > >> * Data binding - JAXB 2.1.2 RI
> > > <https://jaxb.dev.java.net/2.1.2/
> <https://jaxb.dev.java.net/2.1.2/> <https://jaxb.dev.java.net/2.1.2/
> <https://jaxb.dev.java.net/2.1.2/>>
> > > > <https://jaxb.dev.java.net/2.1.2/
> <https://jaxb.dev.java.net/2.1.2/> <https://jaxb.dev.java.net/2.1.2/
> <https://jaxb.dev.java.net/2.1.2/>>>>
> > > > > >> * Server Side Asynchrony - AsyncProvider
> > > > > >>
> <https://jax-ws.dev.java.net/nonav/2.1/docs/asyncprovider.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/asyncprovider.html>
> > > <https://jax-ws.dev.java.net/nonav/2.1/docs/asyncprovider.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/asyncprovider.html>>
> > > > <https://jax-ws.dev.java.net/nonav/2.1/docs/asyncprovider.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/asyncprovider.html>
> > > <https://jax-ws.dev.java.net/nonav/2.1/docs/asyncprovider.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/asyncprovider.html>>>>
> > > > > >> * Stateful Web Services
> > > > > >>
> > > >
> <https://jax-ws.dev.java.net/nonav/2.1/docs/statefulWebservice.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/statefulWebservice.html>
> > >
> <https://jax-ws.dev.java.net/nonav/2.1/docs/statefulWebservice.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/statefulWebservice.html>>
> > > >
> <https://jax-ws.dev.java.net/nonav/2.1/docs/statefulWebservice.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/statefulWebservice.html>
> > >
> <https://jax-ws.dev.java.net/nonav/2.1/docs/statefulWebservice.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/statefulWebservice.html>>>>
> > > > > >> * Support for custom WebServiceFeature
> > > > > >>
> > > >
> > >
>
<http://weblogs.java.net/blog/ramapulavarthi/archive/2007/01/extending_jaxws.htm\
l
>
<http://weblogs.java.net/blog/ramapulavarthi/archive/2007/01/extending_jaxws.htm\
l>
> > >
>
<http://weblogs.java.net/blog/ramapulavarthi/archive/2007/01/extending_jaxws.htm\
l
>
<http://weblogs.java.net/blog/ramapulavarthi/archive/2007/01/extending_jaxws.htm\
l>>
> > >
> > > >
> > >
>
<http://weblogs.java.net/blog/ramapulavarthi/archive/2007/01/extending_jaxws.htm\
l
>
<http://weblogs.java.net/blog/ramapulavarthi/archive/2007/01/extending_jaxws.htm\
l>
> > >
>
<http://weblogs.java.net/blog/ramapulavarthi/archive/2007/01/extending_jaxws.htm\
l
>
<http://weblogs.java.net/blog/ramapulavarthi/archive/2007/01/extending_jaxws.htm\
l>>>>
> > > > > >> * Hosting API
> > > > > >>
> > > >
> > >
>
<https://jax-ws-architecture-document.dev.java.net/nonav/doc21/index.html?com/su\
n/xml/ws/api/server/package-summary.html
>
<https://jax-ws-architecture-document.dev.java.net/nonav/doc21/index.html?com/su\
n/xml/ws/api/server/package-summary.html>
> > >
>
<https://jax-ws-architecture-document.dev.java.net/nonav/doc21/index.html?com/su\
n/xml/ws/api/server/package-summary.html
>
<https://jax-ws-architecture-document.dev.java.net/nonav/doc21/index.html?com/su\
n/xml/ws/api/server/package-summary.html>>
> > >
> > > >
> > >
>
<https://jax-ws-architecture-document.dev.java.net/nonav/doc21/index.html?com/su\
n/xml/ws/api/server/package-summary.html
>
<https://jax-ws-architecture-document.dev.java.net/nonav/doc21/index.html?com/su\
n/xml/ws/api/server/package-summary.html>
> > >
>
<https://jax-ws-architecture-document.dev.java.net/nonav/doc21/index.html?com/su\
n/xml/ws/api/server/package-summary.html
>
<https://jax-ws-architecture-document.dev.java.net/nonav/doc21/index.html?com/su\
n/xml/ws/api/server/package-summary.html>>>>
> > > > > >>
> > > > > >> o These APIs can be used by a J2EE application server to
> > > > > >> integrate JAX-WS 2.1 RI for hosting JAX-WS services
> > > > > >> * Endpoint Deployment
> > > > > >> o Glassfish v2 <https://glassfish.dev.java.net
> <https://glassfish.dev.java.net>
> > > <https://glassfish.dev.java.net <https://glassfish.dev.java.net>>
> > > > <https://glassfish.dev.java.net <https://glassfish.dev.java.net>
> <https://glassfish.dev.java.net <https://glassfish.dev.java.net>>>>
> > > > > >> + Tightly integrated with Glassfish
> > > > > >> + Supports EJB and Web endpoints
> > > > > >> + 109 based deployment support for better portability
> > > > > >> + JAX-WS RI specific deployment descriptor support
> > > > > >> o Sun One Application Server 9.0 ur1
> > > > > >> <http://www.sun.com/software/products/appsrvr_pe/index.xml
> <http://www.sun.com/software/products/appsrvr_pe/index.xml>
> > > <http://www.sun.com/software/products/appsrvr_pe/index.xml
> <http://www.sun.com/software/products/appsrvr_pe/index.xml>>
> > > > <http://www.sun.com/software/products/appsrvr_pe/index.xml
> <http://www.sun.com/software/products/appsrvr_pe/index.xml>
> > > <http://www.sun.com/software/products/appsrvr_pe/index.xml
> <http://www.sun.com/software/products/appsrvr_pe/index.xml>>>>
> > > > > >> o Light weight HTTP server
> > > > > >> + On JDK 1.5 through http.jar distributed with the
> > > > > >> JAX-WS 2.1 RI bundle
> > > > > >> + Bundled with JDK 6
> > > > > >> o Any other container that supports Servlet 2.4, such as
> > > > > >> Tomcat, Jetty, Geronimo, JBoss, Resin, ... You name it!
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >> ----------------------------------------------------------
> > > > > >> This group is a forum for builders of SOAP implementations to
> > > > discuss implementation and interoperability issues. Please stay
> > > on-topic.
> > > > > >> Yahoo! Groups Links
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >
> > > > > >
> > > > > > ----------------------------------------------------------
> > > > > > This group is a forum for builders of SOAP implementations to
> > > > discuss implementation and interoperability issues. Please stay
> > > on-topic.
> > > > > > Yahoo! Groups Links
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > ----------------------------------------------------------
> > > > > This group is a forum for builders of SOAP implementations to
> > > > discuss implementation and interoperability issues. Please stay
> > > on-topic.
> > > > > Yahoo! Groups Links
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > > > --
> > > > Davanum Srinivas :: http://wso2.org/ <http://wso2.org/>
> <http://wso2.org/ <http://wso2.org/>>
> > > <http://wso2.org/ <http://wso2.org/> <http://wso2.org/
> <http://wso2.org/>>> :: Oxygen for
> > > > Web Services Developers
> > > >
> > > >
> > >
> > >
> >
> >
> > ----------------------------------------------------------
> > This group is a forum for builders of SOAP implementations to
> discuss implementation and interoperability issues. Please stay on-topic.
> > Yahoo! Groups Links
> >
> >
> >
> >
>
> --
> Davanum Srinivas :: http://wso2.org/ <http://wso2.org/> :: Oxygen for
> Web Services Developers
>
>

Thanks Steve,
I will bring this up internally and get back to you next week.

Steve Loughran wrote:
>
> On 2/9/07, Davanum Srinivas <davanum@...
> <mailto:davanum%40gmail.com>> wrote:
> > Doug,
> >
> > Just to be on the record..."Use endorsed mechanism" works for RI
> > because of this:
> >
> http://weblogs.java.net/blog/kohsuke/archive/2007/02/howitworks_runn.html
> <http://weblogs.java.net/blog/kohsuke/archive/2007/02/howitworks_runn.html>
>
> >
> > It's a bit unfair to other jaxws implementors to have to implement
> > hacks like this to get our stuff working under JDK6. I brought his up
> > before:
> > http://blogs.cocoondev.org/dims/archives/004717.html
> <http://blogs.cocoondev.org/dims/archives/004717.html>
>
> oh, that is devious. We could probably put a block on that in ant if
> it was felt to endanger the stability of hosting IDEs. We'll have to
> see what the eclipse perf team say about it, they being the best team
> at tracking down memory leaks -and classloaders do leak if you dont
> clean up very carefully. AntClassLoader extends BuildListener purely
> to clean itself up at the end of an IDE-hosted build (
>
http://svn.apache.org/viewvc/ant/core/trunk/src/main/org/apache/tools/ant/AntCla\
ssLoader.java?view=markup
>
<http://svn.apache.org/viewvc/ant/core/trunk/src/main/org/apache/tools/ant/AntCl\
assLoader.java?view=markup>
> )
>
> More subtly, AntClassLoader already blocks all classes from the parent
> except for those that come with the JRE; look at buildJrePackages()
> in
>
http://svn.apache.org/viewvc/ant/core/trunk/src/main/org/apache/tools/ant/util/J\
avaEnvUtils.java?view=markup
>
<http://svn.apache.org/viewvc/ant/core/trunk/src/main/org/apache/tools/ant/util/\
JavaEnvUtils.java?view=markup>
>
> Doug. please communicate to your team that Ant too welcomes
> constructive code contributions, and one Sun employee does in fact
> have commit rights.
>
> If having JAX-WS 2.0 on the classpath of Java6 is felt to be a
> problem, we could just block it out entirely; it would cease to exist
> for tasks and java code in the same VM, but return for forked apps.
> Its kind of a brutal solution, but it may suit Dims, who no doubt has
> to field support requests of the kind "Axis 2 stops working on Java
> 6".
>
> Dims, what do you think? de-endorse JAX-WS 2.0 in Ant1.7.1?
>
> -steve
>
>

Steve,
I am still poking around on the interop tests. I did discover that when
doing WS-Policy interop testing about a year ago, the turned out to be a
full-blown security interop test.  Participants there were MS, IBM, BEA,
SAP, Sun, Apache, Layer 7.  The results can be view at:
http://lists.w3.org/Archives/Public/public-ws-policy/2006Jun/att-0010/ws-policy-\
workshop-minutes-April-2006.doc

Everyone was able to fully interop with everyone else except for one
company that did not have a security implementation at that time.  In
the chart, Sun is P6.

Steve Loughran wrote:
>
> On 2/8/07, Doug Kohlert <doug.kohlert@...
> <mailto:doug.kohlert%40sun.com>> wrote:
> > Oh, you are talking about the data corruption mentioned in Kohsuke's
> > blog
> >
> (http://weblogs.java.net/blog/kohsuke/archive/2007/02/jaxws_ri_21_ben.html
> <http://weblogs.java.net/blog/kohsuke/archive/2007/02/jaxws_ri_21_ben.html>).
> > Yea Dims, we made that up; get real dude. Kohsuke even mentioned in
> > his blog that we were not sure why it happened and that it might even be
> > a Glassfish issue.
>
> Well I for one celebrate the release, and think the dev team should be
> congratulated and given the rest of the week off to celebrate, even
> though I personally have no intention of using JAX-WS or anything that
> goes from Java to WSDL.
>
> o It is the SOAP client built in to Java 6, so any improvements in
> performance are good, because they will help on the client.
>
> o Any improvements in interop can only be a good thing.
>
> o The async stuff looks interesting, though I fear that the Java
> community is reading "Java Concurrency in Practise" and going
> overboard with futures and callables the way Java1.1 and Swing did
> with nested classes.
>
> As for the benchmarking, well, I don't know what you can conclude.
> Probably comparing the new version against the old one is the best
> metric, and here things are better. And the fact that the team has
> managed to find a concurrency problem on a 4-way box with glassfish
> means everyone is partway to fixing it -dims and dennis are now aware
> of its existence.
>
> Doug :
>
> 1. any plans to slip this out into a Java 6 point release? Or is that
> going to be stuck with the old codebase for its entire product
> lifespan?
>
> 2. what's your current interop test process?
>
> -Steve
>
>

On 2/9/07, Davanum Srinivas <davanum@...> wrote:
> Doug,
>
> Just to be on the record..."Use endorsed mechanism" works for RI
> because of this:
> http://weblogs.java.net/blog/kohsuke/archive/2007/02/howitworks_runn.html


>
> It's a bit unfair to other jaxws implementors to have to implement
> hacks like this to get our stuff working under JDK6. I brought his up
> before:
> http://blogs.cocoondev.org/dims/archives/004717.html

oh, that is devious. We could probably put a block on that in ant if
it was felt to endanger the stability of hosting IDEs. We'll have to
see what the eclipse perf team say about it, they being the best team
at tracking down memory leaks -and classloaders do leak if you dont
clean up very carefully. AntClassLoader extends BuildListener purely
to clean itself up at the end of an IDE-hosted build (
http://svn.apache.org/viewvc/ant/core/trunk/src/main/org/apache/tools/ant/AntCla\
ssLoader.java?view=markup
)

More subtly, AntClassLoader already blocks all classes from the parent
except for those that come with the JRE; look at  buildJrePackages()
in
http://svn.apache.org/viewvc/ant/core/trunk/src/main/org/apache/tools/ant/util/J\
avaEnvUtils.java?view=markup

Doug. please communicate to your team that Ant too welcomes
constructive code contributions, and one Sun employee does in fact
have commit rights.

If having JAX-WS 2.0 on the classpath of Java6 is felt to be a
problem, we could just block it  out entirely; it would cease to exist
for tasks and java code in the same VM, but return for forked apps.
Its kind of a brutal solution, but it may suit Dims, who no doubt has
to field support requests of the kind "Axis 2 stops working on Java
6".

Dims, what do you think? de-endorse JAX-WS 2.0 in Ant1.7.1?

-steve

Doug,

Just to be on the record..."Use endorsed mechanism" works for RI
because of this:
http://weblogs.java.net/blog/kohsuke/archive/2007/02/howitworks_runn.html

It's a bit unfair to other jaxws implementors to have to implement
hacks like this to get our stuff working under JDK6. I brought his up
before:
http://blogs.cocoondev.org/dims/archives/004717.html

I guess, we have to live with it. I wonder what the app server vendors
think about it....

thanks,
dims

On 2/9/07, Doug Kohlert <doug.kohlert@...> wrote:
> Thank you Steve,
>  >>... I personally have no intention of using JAX-WS or anything that
> goes from Java to WSDL.
>
> The JAX-WS teams fully realizes that for more advanced web services, the
> best approach is to do contract first by defining the WSDL and schema
> first and then implementing the contract.  JAX-WS with its JAXB 2.0
> databinding supports 100% mapping of schema to Java making it relatively
> straight forward to do this.
>
>  >>  1. any plans to slip this out into a Java 6 point release? Or is that
>  >>  going to be stuck with the old codebase for its entire product
>  >>  lifespan?
>
> Unfortunately, the JAX-WS 2.1 RI is based on the JAX-WS 2.1
> specification, which means that it added new functionality/APIs and as
> such can't be added into a point release of Java 6.  I believe it will
> be included in the next
> release of Java 7.  In the meantime, one can use the endorsed directory
> mechanism to replace JAX-WS 2.0 in Java 6 with JAX-WS 2.1.
>
>  >> 2. what's your current interop test process?
>
> To be honest I am not completely sure but I will check.  I do know that
> the WSIT project (soon to be released as FCS, http://wsit.dev.java.net)
> which is an extension to JAX-WS that enables many of the WS-* specs, has
> worked very closely with the Microsoft developers to make sure that WSIT
> interoperates with WCF.  During some of the Microsoft sponsered interop
> tests, we not only tested interop with MS but also with some other
> companies attending ant if I remember correctly things went well. I
> don't believe we are allowed to disclose or discuss the results of those
> tests.
>
> By the way, since the JAX-WS RI is an open source project, we are
> looking for some good non-Sun developers to work on the project.  We
> have been playing with the idea of a pluggable databinding but have had
> higher priorities arise.  If anyone is interested in contributing to the
> RI, please let me know.  We are open to any and all suggestions on ways
> to improve the RI and the spec, and if you can even contribute all the
> better.
>
> Thanks again for your support.
>
> Steve Loughran wrote:
> >
> > On 2/8/07, Doug Kohlert <doug.kohlert@...
> > <mailto:doug.kohlert%40sun.com>> wrote:
> > > Oh, you are talking about the data corruption mentioned in Kohsuke's
> > > blog
> > >
> > (http://weblogs.java.net/blog/kohsuke/archive/2007/02/jaxws_ri_21_ben.html
> >
<http://weblogs.java.net/blog/kohsuke/archive/2007/02/jaxws_ri_21_ben.html>).
> > > Yea Dims, we made that up; get real dude. Kohsuke even mentioned in
> > > his blog that we were not sure why it happened and that it might even be
> > > a Glassfish issue.
> >
> > Well I for one celebrate the release, and think the dev team should be
> > congratulated and given the rest of the week off to celebrate, even
> > though I personally have no intention of using JAX-WS or anything that
> > goes from Java to WSDL.
> >
> > o It is the SOAP client built in to Java 6, so any improvements in
> > performance are good, because they will help on the client.
> >
> > o Any improvements in interop can only be a good thing.
> >
> > o The async stuff looks interesting, though I fear that the Java
> > community is reading "Java Concurrency in Practise" and going
> > overboard with futures and callables the way Java1.1 and Swing did
> > with nested classes.
> >
> > As for the benchmarking, well, I don't know what you can conclude.
> > Probably comparing the new version against the old one is the best
> > metric, and here things are better. And the fact that the team has
> > managed to find a concurrency problem on a 4-way box with glassfish
> > means everyone is partway to fixing it -dims and dennis are now aware
> > of its existence.
> >
> > Doug :
> >
> > 1. any plans to slip this out into a Java 6 point release? Or is that
> > going to be stuck with the old codebase for its entire product
> > lifespan?
> >
> > 2. what's your current interop test process?
> >
> > -Steve
> >
> >
>
>
> -----------------------------------------------------------------
> This group is a forum for builders of SOAP implementations to discuss
implementation and interoperability issues.  Please stay on-topic.
> Yahoo! Groups Links
>
>
>
>


--
Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers

Thank you Steve,
  >>... I personally have no intention of using JAX-WS or anything that
goes from Java to WSDL.

The JAX-WS teams fully realizes that for more advanced web services, the
best approach is to do contract first by defining the WSDL and schema
first and then implementing the contract.  JAX-WS with its JAXB 2.0
databinding supports 100% mapping of schema to Java making it relatively
straight forward to do this.

  >>  1. any plans to slip this out into a Java 6 point release? Or is that
  >>  going to be stuck with the old codebase for its entire product
  >>  lifespan?

Unfortunately, the JAX-WS 2.1 RI is based on the JAX-WS 2.1
specification, which means that it added new functionality/APIs and as
such can't be added into a point release of Java 6.  I believe it will
be included in the next
release of Java 7.  In the meantime, one can use the endorsed directory
mechanism to replace JAX-WS 2.0 in Java 6 with JAX-WS 2.1.

  >> 2. what's your current interop test process?

To be honest I am not completely sure but I will check.  I do know that
the WSIT project (soon to be released as FCS, http://wsit.dev.java.net)
which is an extension to JAX-WS that enables many of the WS-* specs, has
worked very closely with the Microsoft developers to make sure that WSIT
interoperates with WCF.  During some of the Microsoft sponsered interop
tests, we not only tested interop with MS but also with some other
companies attending ant if I remember correctly things went well. I
don't believe we are allowed to disclose or discuss the results of those
tests.

By the way, since the JAX-WS RI is an open source project, we are
looking for some good non-Sun developers to work on the project.  We
have been playing with the idea of a pluggable databinding but have had
higher priorities arise.  If anyone is interested in contributing to the
RI, please let me know.  We are open to any and all suggestions on ways
to improve the RI and the spec, and if you can even contribute all the
better.

Thanks again for your support.

Steve Loughran wrote:
>
> On 2/8/07, Doug Kohlert <doug.kohlert@...
> <mailto:doug.kohlert%40sun.com>> wrote:
> > Oh, you are talking about the data corruption mentioned in Kohsuke's
> > blog
> >
> (http://weblogs.java.net/blog/kohsuke/archive/2007/02/jaxws_ri_21_ben.html
> <http://weblogs.java.net/blog/kohsuke/archive/2007/02/jaxws_ri_21_ben.html>).
> > Yea Dims, we made that up; get real dude. Kohsuke even mentioned in
> > his blog that we were not sure why it happened and that it might even be
> > a Glassfish issue.
>
> Well I for one celebrate the release, and think the dev team should be
> congratulated and given the rest of the week off to celebrate, even
> though I personally have no intention of using JAX-WS or anything that
> goes from Java to WSDL.
>
> o It is the SOAP client built in to Java 6, so any improvements in
> performance are good, because they will help on the client.
>
> o Any improvements in interop can only be a good thing.
>
> o The async stuff looks interesting, though I fear that the Java
> community is reading "Java Concurrency in Practise" and going
> overboard with futures and callables the way Java1.1 and Swing did
> with nested classes.
>
> As for the benchmarking, well, I don't know what you can conclude.
> Probably comparing the new version against the old one is the best
> metric, and here things are better. And the fact that the team has
> managed to find a concurrency problem on a 4-way box with glassfish
> means everyone is partway to fixing it -dims and dennis are now aware
> of its existence.
>
> Doug :
>
> 1. any plans to slip this out into a Java 6 point release? Or is that
> going to be stuck with the old codebase for its entire product
> lifespan?
>
> 2. what's your current interop test process?
>
> -Steve
>
>

On 2/8/07, Doug Kohlert <doug.kohlert@...> wrote:
> Oh, you are talking about the data corruption mentioned in Kohsuke's
> blog
> (http://weblogs.java.net/blog/kohsuke/archive/2007/02/jaxws_ri_21_ben.html).
> Yea Dims, we made that up;  get real dude.  Kohsuke even mentioned in
> his blog that we were not sure why it happened and that it might even be
> a Glassfish issue.

Well I for one celebrate the release, and think the dev team should be
congratulated and given the rest of the week off to celebrate, even
though I personally have no intention of using JAX-WS or anything that
goes from Java to WSDL.

o It is the SOAP client built in to Java 6, so any improvements in
performance are good, because they will help on the client.

o Any improvements in interop can only be a good thing.

o The async stuff looks interesting, though I fear that the Java
community is reading "Java Concurrency  in Practise" and going
overboard with futures and callables the way Java1.1 and Swing did
with nested classes.

As for the benchmarking, well, I don't know what you can conclude.
Probably comparing the new version against the old one is the best
metric, and here things are better. And the fact that the team has
managed to find a concurrency problem on a 4-way box with glassfish
means everyone is partway to fixing it -dims and dennis are now aware
of its existence.

Doug :

1. any plans to slip this out into a Java 6 point release? Or is that
going to be stuck with the old codebase for its entire product
lifespan?

2. what's your current interop test process?

-Steve

Thanks Dims, we are working on it.  In the meantime, if you are
concerned about it, you certainly can post your own results.

Davanum Srinivas wrote:
>
> Doug,
>
> There is no mention of apples-to-apples comparison on kohsuke's blog.
> There is no mention of XMLBeans in vivek's blog. This is the first
> time i hear this new argument that Axis2/XmlBeans is a
> apples-to-apples comparison....
>
> If you really wanted to test the perf, you should compare multiple
> options including the default settings for both stacks :) In this
> case, it would mean Axis2/JAXB, Axis2/ADB, JAXWS-RI/JAXB. Running
> Axis2/XMLBeans and claiming huge perf improvements is ridiculous as
> dennis mentioned.
>
> -- dims
>
> On 2/8/07, Doug Kohlert <doug.kohlert@...
> <mailto:doug.kohlert%40sun.com>> wrote:
> > Oh, you are talking about the data corruption mentioned in Kohsuke's
> > blog
> >
> (http://weblogs.java.net/blog/kohsuke/archive/2007/02/jaxws_ri_21_ben.html
> <http://weblogs.java.net/blog/kohsuke/archive/2007/02/jaxws_ri_21_ben.html>).
> > Yea Dims, we made that up; get real dude. Kohsuke even mentioned in
> > his blog that we were not sure why it happened and that it might even be
> > a Glassfish issue.
> >
> > Doug Kohlert wrote:
> > >
> > > What data corruption are you talking about? I didn't mention anything
> > > about data corruption.
> > >
> > > Davanum Srinivas wrote:
> > > >
> > > > Doug,
> > > >
> > > > Nice party line! So the ADB data corruption issue was something you
> > > > made up? Or did it really happen?
> > > >
> > > > -- dims
> > > >
> > > > On 2/8/07, Doug Kohlert <doug.kohlert@...
> <mailto:doug.kohlert%40sun.com>
> > > <mailto:doug.kohlert%40sun.com>
> > > > <mailto:doug.kohlert%40sun.com>> wrote:
> > > > > Good point, you may want to post your comment to Vivek's blog.
> That
> > > > > said, since there are limitations in both
> > > > > ADB and JiBX when compiling schema to Java, we felt this was
> the most
> > > > > appropriate match of capabilities.
> > > > > So this benchmark really is more of an apples-to-apples comparison
> > > > > rather than an apples-to-oranges comparison that you suggest.
> > > > >
> > > > > Dennis Sosnoski wrote:
> > > > > > "Benchmarking" against Axis2-XMLBeans (as shown in the linked
> > > blog) is
> > > > > > ridiculous. XMLBeans is much slower than either ADB or JiBX data
> > > > binding
> > > > > > for Axis2. If you're going to make performance claims for your
> > > > software,
> > > > > > at least try to make the tests half way reasonable.
> > > > > >
> > > > > > - Dennis
> > > > > >
> > > > > > Dennis M. Sosnoski
> > > > > > SOA and Web Services in Java
> > > > > > Training and Consulting
> > > > > > http://www.sosnoski.com <http://www.sosnoski.com>
> <http://www.sosnoski.com <http://www.sosnoski.com>>
> > > <http://www.sosnoski.com <http://www.sosnoski.com>
> <http://www.sosnoski.com <http://www.sosnoski.com>>> -
> > > > http://www.sosnoski.co.nz <http://www.sosnoski.co.nz>
> <http://www.sosnoski.co.nz <http://www.sosnoski.co.nz>>
> > > <http://www.sosnoski.co.nz <http://www.sosnoski.co.nz>
> <http://www.sosnoski.co.nz <http://www.sosnoski.co.nz>>>
> > > > > > Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117
> > > > > >
> > > > > >
> > > > > >
> > > > > > Doug Kohlert wrote:
> > > > > >
> > > > > >> We are proud to announce the release of JAX-WS 2.1 RI FCS.
> JAX-WS
> > > > 2.1 is
> > > > > >> a major re-architecture over JAX-WS 2.0 without changing the
> > > standard
> > > > > >> JAX-WS APIs or programming model. The benefits of this is a
> > > very fast
> > > > > >> implementation and an extremely flexible, extensible
> > > architecture. To
> > > > > >> read more about how fast the RI is and the new functionality
> > > that it
> > > > > >> contains, read Vivek's blog at:
> > > > > >>
> > > >
> > >
> http://weblogs.java.net/blog/vivekp/archive/2007/02/jaxws_21_fcs_fa_1.html
> <http://weblogs.java.net/blog/vivekp/archive/2007/02/jaxws_21_fcs_fa_1.html>
> > >
> <http://weblogs.java.net/blog/vivekp/archive/2007/02/jaxws_21_fcs_fa_1.html
> <http://weblogs.java.net/blog/vivekp/archive/2007/02/jaxws_21_fcs_fa_1.html>>
> > >
> > > >
> > >
> <http://weblogs.java.net/blog/vivekp/archive/2007/02/jaxws_21_fcs_fa_1.html
> <http://weblogs.java.net/blog/vivekp/archive/2007/02/jaxws_21_fcs_fa_1.html>
> > >
> <http://weblogs.java.net/blog/vivekp/archive/2007/02/jaxws_21_fcs_fa_1.html
> <http://weblogs.java.net/blog/vivekp/archive/2007/02/jaxws_21_fcs_fa_1.html>>>
> > > > > >>
> > > > > >> Here is an excerpt from Vivek's blog about the Key Features.
> > > > > >>
> > > > > >> * Reference Implementation (RI) of JAX-WS 2.1. Full JAX-WS 2.1
> > > > > >> Specification <http://jcp.org/en/jsr/detail?id=224
> <http://jcp.org/en/jsr/detail?id=224>
> > > <http://jcp.org/en/jsr/detail?id=224
> <http://jcp.org/en/jsr/detail?id=224>>
> > > > <http://jcp.org/en/jsr/detail?id=224
> <http://jcp.org/en/jsr/detail?id=224>
> > > <http://jcp.org/en/jsr/detail?id=224
> <http://jcp.org/en/jsr/detail?id=224>>>> compliance
> > > > > >> * Development Tools
> > > > > >> o WSDL to Java generator
> > > > > >> + Wsimport command line tool
> > > > > >> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimport.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimport.html>
> > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimport.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimport.html>>
> > > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimport.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimport.html>
> > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimport.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimport.html>>>>,
> > > > > >> ant task
> > > > > >>
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimportant.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimportant.html>
> > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimportant.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimportant.html>>
> > > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimportant.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimportant.html>
> > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimportant.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimportant.html>>>>
> > > > > >> and Maven2 plugin
> > > > > >> <http://mojo.codehaus.org/jaxws-maven-plugin/index.html
> <http://mojo.codehaus.org/jaxws-maven-plugin/index.html>
> > > <http://mojo.codehaus.org/jaxws-maven-plugin/index.html
> <http://mojo.codehaus.org/jaxws-maven-plugin/index.html>>
> > > > <http://mojo.codehaus.org/jaxws-maven-plugin/index.html
> <http://mojo.codehaus.org/jaxws-maven-plugin/index.html>
> > > <http://mojo.codehaus.org/jaxws-maven-plugin/index.html
> <http://mojo.codehaus.org/jaxws-maven-plugin/index.html>>>>
> > > > > >> o Java to WSDL generator
> > > > > >> + Wsgen command line tool
> > > > > >> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgen.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgen.html>
> > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgen.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgen.html>>
> > > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgen.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgen.html>
> > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgen.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgen.html>>>>,
> > > > > >> ant Task
> > > > > >> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgenant.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgenant.html>
> > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgenant.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgenant.html>>
> > > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgenant.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgenant.html>
> > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgenant.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgenant.html>>>>
> > > > > >> and Maven2 plugin
> > > > > >> <http://mojo.codehaus.org/jaxws-maven-plugin/index.html
> <http://mojo.codehaus.org/jaxws-maven-plugin/index.html>
> > > <http://mojo.codehaus.org/jaxws-maven-plugin/index.html
> <http://mojo.codehaus.org/jaxws-maven-plugin/index.html>>
> > > > <http://mojo.codehaus.org/jaxws-maven-plugin/index.html
> <http://mojo.codehaus.org/jaxws-maven-plugin/index.html>
> > > <http://mojo.codehaus.org/jaxws-maven-plugin/index.html
> <http://mojo.codehaus.org/jaxws-maven-plugin/index.html>>>>
> > > > > >> o Integrated with NetBeans 5.5.1
> > > > > >> <http://www.netbeans.info/downloads/dev.php
> <http://www.netbeans.info/downloads/dev.php>
> > > <http://www.netbeans.info/downloads/dev.php
> <http://www.netbeans.info/downloads/dev.php>>
> > > > <http://www.netbeans.info/downloads/dev.php
> <http://www.netbeans.info/downloads/dev.php>
> > > <http://www.netbeans.info/downloads/dev.php
> <http://www.netbeans.info/downloads/dev.php>>>>
> > > > > >> * Standards
> > > > > >> o Web Services Addressing 1.0 - Core, SOAP Binding and WSDL
> > > > > >> Binding
> > > > > >> o WS-Addressing - Member Submission
> > > > > >> o SOAP 1.1 and 1.2
> > > > > >> o REST and XML/HTTP
> > > > > >> o WS-I Basic Profile 1.1, Simple SOAP Binding Profile 1.0 and
> > > > > >> Attachment Profile 1.0
> > > > > >> o MTOM
> > > > > >> * Extensions (May not be final unless says so)
> > > > > >> o Web Services Interoperable Technologies ( WSIT
> > > > > >> <https://wsit.dev.java.net/index.html#downloads
> <https://wsit.dev.java.net/index.html#downloads>
> > > <https://wsit.dev.java.net/index.html#downloads
> <https://wsit.dev.java.net/index.html#downloads>>
> > > > <https://wsit.dev.java.net/index.html#downloads
> <https://wsit.dev.java.net/index.html#downloads>
> > > <https://wsit.dev.java.net/index.html#downloads
> <https://wsit.dev.java.net/index.html#downloads>>>>) - enables
> > > > > >> .NET 3.0 interoperability
> > > > > >> + WS-ReliableMessaging
> > > > > >> + WS-Policy
> > > > > >> + WS-MEX
> > > > > >> + WS-Security/WS-Security Policy
> > > > > >> + WS-Trust/WS-Secure Conversation
> > > > > >> + WS-AT/WS-Tx (Supported only on Glassfish v2)
> > > > > >> + SOAP/TCP
> > > > > >> o Spring support
> <https://jax-ws-commons.dev.java.net/spring/
> <https://jax-ws-commons.dev.java.net/spring/>
> > > <https://jax-ws-commons.dev.java.net/spring/
> <https://jax-ws-commons.dev.java.net/spring/>>
> > > > <https://jax-ws-commons.dev.java.net/spring/
> <https://jax-ws-commons.dev.java.net/spring/>
> > > <https://jax-ws-commons.dev.java.net/spring/
> <https://jax-ws-commons.dev.java.net/spring/>>>>
> > > > > >> o Pluggable Transport
> > > > > >> <https://jax-ws.dev.java.net/transport.html
> <https://jax-ws.dev.java.net/transport.html>
> > > <https://jax-ws.dev.java.net/transport.html
> <https://jax-ws.dev.java.net/transport.html>>
> > > > <https://jax-ws.dev.java.net/transport.html
> <https://jax-ws.dev.java.net/transport.html>
> > > <https://jax-ws.dev.java.net/transport.html
> <https://jax-ws.dev.java.net/transport.html>>>>
> > > > > >> + In-VM transport
> > > > > >> + Servlet transport (bundled with the RI)
> > > > > >> + JMS transport <http://jms-ws-transport.dev.java.net/
> <http://jms-ws-transport.dev.java.net/>
> > > <http://jms-ws-transport.dev.java.net/
> <http://jms-ws-transport.dev.java.net/>>
> > > > <http://jms-ws-transport.dev.java.net/
> <http://jms-ws-transport.dev.java.net/>
> > > <http://jms-ws-transport.dev.java.net/
> <http://jms-ws-transport.dev.java.net/>>>>
> > > > > >> + SOAP over TCP transport (part of WSIT
> > > > > >> <https://wsit.dev.java.net <https://wsit.dev.java.net>
> <https://wsit.dev.java.net <https://wsit.dev.java.net>>
> > > <https://wsit.dev.java.net <https://wsit.dev.java.net>
> <https://wsit.dev.java.net <https://wsit.dev.java.net>>>>)
> > > > > >> o FastInfoset (bundled with JAX-WS 2.1 RI)
> > > > > >> <https://fi.dev.java.net/ <https://fi.dev.java.net/>
> <https://fi.dev.java.net/ <https://fi.dev.java.net/>>
> > > <https://fi.dev.java.net/ <https://fi.dev.java.net/>
> <https://fi.dev.java.net/ <https://fi.dev.java.net/>>>>
> > > > > >> + ITU-T Rec. X.891 | ISO/IEC 24824-1
> > > > > >> <http://www.itu.int/rec/T-REC-X.891-200505-I/e
> <http://www.itu.int/rec/T-REC-X.891-200505-I/e>
> > > <http://www.itu.int/rec/T-REC-X.891-200505-I/e
> <http://www.itu.int/rec/T-REC-X.891-200505-I/e>>
> > > > <http://www.itu.int/rec/T-REC-X.891-200505-I/e
> <http://www.itu.int/rec/T-REC-X.891-200505-I/e>
> > > <http://www.itu.int/rec/T-REC-X.891-200505-I/e
> <http://www.itu.int/rec/T-REC-X.891-200505-I/e>>>>
> > > > > >> o JBI Service Engine and Binding Component(part of
> Glassfish v2)
> > > > > >> o HTTP Binding Component
> > > > > >> <http://www.glassfishwiki.org/jbiwiki/Wiki.jsp?page=HTTPBC
> <http://www.glassfishwiki.org/jbiwiki/Wiki.jsp?page=HTTPBC>
> > > <http://www.glassfishwiki.org/jbiwiki/Wiki.jsp?page=HTTPBC
> <http://www.glassfishwiki.org/jbiwiki/Wiki.jsp?page=HTTPBC>>
> > > > <http://www.glassfishwiki.org/jbiwiki/Wiki.jsp?page=HTTPBC
> <http://www.glassfishwiki.org/jbiwiki/Wiki.jsp?page=HTTPBC>
> > > <http://www.glassfishwiki.org/jbiwiki/Wiki.jsp?page=HTTPBC
> <http://www.glassfishwiki.org/jbiwiki/Wiki.jsp?page=HTTPBC>>>>,
> > > > > >> used by Open JBI component
> > > > > >> <https://open-jbi-components.dev.java.net/
> <https://open-jbi-components.dev.java.net/>
> > > <https://open-jbi-components.dev.java.net/
> <https://open-jbi-components.dev.java.net/>>
> > > > <https://open-jbi-components.dev.java.net/
> <https://open-jbi-components.dev.java.net/>
> > > <https://open-jbi-components.dev.java.net/
> <https://open-jbi-components.dev.java.net/>>>>
> > > > > >> * Data binding - JAXB 2.1.2 RI
> > > <https://jaxb.dev.java.net/2.1.2/
> <https://jaxb.dev.java.net/2.1.2/> <https://jaxb.dev.java.net/2.1.2/
> <https://jaxb.dev.java.net/2.1.2/>>
> > > > <https://jaxb.dev.java.net/2.1.2/
> <https://jaxb.dev.java.net/2.1.2/> <https://jaxb.dev.java.net/2.1.2/
> <https://jaxb.dev.java.net/2.1.2/>>>>
> > > > > >> * Server Side Asynchrony - AsyncProvider
> > > > > >>
> <https://jax-ws.dev.java.net/nonav/2.1/docs/asyncprovider.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/asyncprovider.html>
> > > <https://jax-ws.dev.java.net/nonav/2.1/docs/asyncprovider.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/asyncprovider.html>>
> > > > <https://jax-ws.dev.java.net/nonav/2.1/docs/asyncprovider.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/asyncprovider.html>
> > > <https://jax-ws.dev.java.net/nonav/2.1/docs/asyncprovider.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/asyncprovider.html>>>>
> > > > > >> * Stateful Web Services
> > > > > >>
> > > >
> <https://jax-ws.dev.java.net/nonav/2.1/docs/statefulWebservice.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/statefulWebservice.html>
> > >
> <https://jax-ws.dev.java.net/nonav/2.1/docs/statefulWebservice.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/statefulWebservice.html>>
> > > >
> <https://jax-ws.dev.java.net/nonav/2.1/docs/statefulWebservice.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/statefulWebservice.html>
> > >
> <https://jax-ws.dev.java.net/nonav/2.1/docs/statefulWebservice.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/statefulWebservice.html>>>>
> > > > > >> * Support for custom WebServiceFeature
> > > > > >>
> > > >
> > >
>
<http://weblogs.java.net/blog/ramapulavarthi/archive/2007/01/extending_jaxws.htm\
l
>
<http://weblogs.java.net/blog/ramapulavarthi/archive/2007/01/extending_jaxws.htm\
l>
> > >
>
<http://weblogs.java.net/blog/ramapulavarthi/archive/2007/01/extending_jaxws.htm\
l
>
<http://weblogs.java.net/blog/ramapulavarthi/archive/2007/01/extending_jaxws.htm\
l>>
> > >
> > > >
> > >
>
<http://weblogs.java.net/blog/ramapulavarthi/archive/2007/01/extending_jaxws.htm\
l
>
<http://weblogs.java.net/blog/ramapulavarthi/archive/2007/01/extending_jaxws.htm\
l>
> > >
>
<http://weblogs.java.net/blog/ramapulavarthi/archive/2007/01/extending_jaxws.htm\
l
>
<http://weblogs.java.net/blog/ramapulavarthi/archive/2007/01/extending_jaxws.htm\
l>>>>
> > > > > >> * Hosting API
> > > > > >>
> > > >
> > >
>
<https://jax-ws-architecture-document.dev.java.net/nonav/doc21/index.html?com/su\
n/xml/ws/api/server/package-summary.html
>
<https://jax-ws-architecture-document.dev.java.net/nonav/doc21/index.html?com/su\
n/xml/ws/api/server/package-summary.html>
> > >
>
<https://jax-ws-architecture-document.dev.java.net/nonav/doc21/index.html?com/su\
n/xml/ws/api/server/package-summary.html
>
<https://jax-ws-architecture-document.dev.java.net/nonav/doc21/index.html?com/su\
n/xml/ws/api/server/package-summary.html>>
> > >
> > > >
> > >
>
<https://jax-ws-architecture-document.dev.java.net/nonav/doc21/index.html?com/su\
n/xml/ws/api/server/package-summary.html
>
<https://jax-ws-architecture-document.dev.java.net/nonav/doc21/index.html?com/su\
n/xml/ws/api/server/package-summary.html>
> > >
>
<https://jax-ws-architecture-document.dev.java.net/nonav/doc21/index.html?com/su\
n/xml/ws/api/server/package-summary.html
>
<https://jax-ws-architecture-document.dev.java.net/nonav/doc21/index.html?com/su\
n/xml/ws/api/server/package-summary.html>>>>
> > > > > >>
> > > > > >> o These APIs can be used by a J2EE application server to
> > > > > >> integrate JAX-WS 2.1 RI for hosting JAX-WS services
> > > > > >> * Endpoint Deployment
> > > > > >> o Glassfish v2 <https://glassfish.dev.java.net
> <https://glassfish.dev.java.net>
> > > <https://glassfish.dev.java.net <https://glassfish.dev.java.net>>
> > > > <https://glassfish.dev.java.net <https://glassfish.dev.java.net>
> <https://glassfish.dev.java.net <https://glassfish.dev.java.net>>>>
> > > > > >> + Tightly integrated with Glassfish
> > > > > >> + Supports EJB and Web endpoints
> > > > > >> + 109 based deployment support for better portability
> > > > > >> + JAX-WS RI specific deployment descriptor support
> > > > > >> o Sun One Application Server 9.0 ur1
> > > > > >> <http://www.sun.com/software/products/appsrvr_pe/index.xml
> <http://www.sun.com/software/products/appsrvr_pe/index.xml>
> > > <http://www.sun.com/software/products/appsrvr_pe/index.xml
> <http://www.sun.com/software/products/appsrvr_pe/index.xml>>
> > > > <http://www.sun.com/software/products/appsrvr_pe/index.xml
> <http://www.sun.com/software/products/appsrvr_pe/index.xml>
> > > <http://www.sun.com/software/products/appsrvr_pe/index.xml
> <http://www.sun.com/software/products/appsrvr_pe/index.xml>>>>
> > > > > >> o Light weight HTTP server
> > > > > >> + On JDK 1.5 through http.jar distributed with the
> > > > > >> JAX-WS 2.1 RI bundle
> > > > > >> + Bundled with JDK 6
> > > > > >> o Any other container that supports Servlet 2.4, such as
> > > > > >> Tomcat, Jetty, Geronimo, JBoss, Resin, ... You name it!
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >> ----------------------------------------------------------
> > > > > >> This group is a forum for builders of SOAP implementations to
> > > > discuss implementation and interoperability issues. Please stay
> > > on-topic.
> > > > > >> Yahoo! Groups Links
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >
> > > > > >
> > > > > > ----------------------------------------------------------
> > > > > > This group is a forum for builders of SOAP implementations to
> > > > discuss implementation and interoperability issues. Please stay
> > > on-topic.
> > > > > > Yahoo! Groups Links
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > ----------------------------------------------------------
> > > > > This group is a forum for builders of SOAP implementations to
> > > > discuss implementation and interoperability issues. Please stay
> > > on-topic.
> > > > > Yahoo! Groups Links
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > > > --
> > > > Davanum Srinivas :: http://wso2.org/ <http://wso2.org/>
> <http://wso2.org/ <http://wso2.org/>>
> > > <http://wso2.org/ <http://wso2.org/> <http://wso2.org/
> <http://wso2.org/>>> :: Oxygen for
> > > > Web Services Developers
> > > >
> > > >
> > >
> > >
> >
> >
> > ----------------------------------------------------------
> > This group is a forum for builders of SOAP implementations to
> discuss implementation and interoperability issues. Please stay on-topic.
> > Yahoo! Groups Links
> >
> >
> >
> >
>
> --
> Davanum Srinivas :: http://wso2.org/ <http://wso2.org/> :: Oxygen for
> Web Services Developers
>
>

Doug,

There is no mention of apples-to-apples comparison on kohsuke's blog.
There is no mention of XMLBeans in vivek's blog. This is the first
time i hear this new argument that Axis2/XmlBeans is a
apples-to-apples comparison....

If you really wanted to test the perf, you should compare multiple
options including the default settings for both stacks :) In this
case, it would mean Axis2/JAXB, Axis2/ADB, JAXWS-RI/JAXB. Running
Axis2/XMLBeans and claiming huge perf improvements is ridiculous as
dennis mentioned.

-- dims

On 2/8/07, Doug Kohlert <doug.kohlert@...> wrote:
> Oh, you are talking about the data corruption mentioned in Kohsuke's
> blog
> (http://weblogs.java.net/blog/kohsuke/archive/2007/02/jaxws_ri_21_ben.html).
> Yea Dims, we made that up;  get real dude.  Kohsuke even mentioned in
> his blog that we were not sure why it happened and that it might even be
> a Glassfish issue.
>
> Doug Kohlert wrote:
> >
> > What data corruption are you talking about? I didn't mention anything
> > about data corruption.
> >
> > Davanum Srinivas wrote:
> > >
> > > Doug,
> > >
> > > Nice party line! So the ADB data corruption issue was something you
> > > made up? Or did it really happen?
> > >
> > > -- dims
> > >
> > > On 2/8/07, Doug Kohlert <doug.kohlert@...
> > <mailto:doug.kohlert%40sun.com>
> > > <mailto:doug.kohlert%40sun.com>> wrote:
> > > > Good point, you may want to post your comment to Vivek's blog. That
> > > > said, since there are limitations in both
> > > > ADB and JiBX when compiling schema to Java, we felt this was the most
> > > > appropriate match of capabilities.
> > > > So this benchmark really is more of an apples-to-apples comparison
> > > > rather than an apples-to-oranges comparison that you suggest.
> > > >
> > > > Dennis Sosnoski wrote:
> > > > > "Benchmarking" against Axis2-XMLBeans (as shown in the linked
> > blog) is
> > > > > ridiculous. XMLBeans is much slower than either ADB or JiBX data
> > > binding
> > > > > for Axis2. If you're going to make performance claims for your
> > > software,
> > > > > at least try to make the tests half way reasonable.
> > > > >
> > > > > - Dennis
> > > > >
> > > > > Dennis M. Sosnoski
> > > > > SOA and Web Services in Java
> > > > > Training and Consulting
> > > > > http://www.sosnoski.com <http://www.sosnoski.com>
> > <http://www.sosnoski.com <http://www.sosnoski.com>> -
> > > http://www.sosnoski.co.nz <http://www.sosnoski.co.nz>
> > <http://www.sosnoski.co.nz <http://www.sosnoski.co.nz>>
> > > > > Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117
> > > > >
> > > > >
> > > > >
> > > > > Doug Kohlert wrote:
> > > > >
> > > > >> We are proud to announce the release of JAX-WS 2.1 RI FCS. JAX-WS
> > > 2.1 is
> > > > >> a major re-architecture over JAX-WS 2.0 without changing the
> > standard
> > > > >> JAX-WS APIs or programming model. The benefits of this is a
> > very fast
> > > > >> implementation and an extremely flexible, extensible
> > architecture. To
> > > > >> read more about how fast the RI is and the new functionality
> > that it
> > > > >> contains, read Vivek's blog at:
> > > > >>
> > >
> > http://weblogs.java.net/blog/vivekp/archive/2007/02/jaxws_21_fcs_fa_1.html
> > <http://weblogs.java.net/blog/vivekp/archive/2007/02/jaxws_21_fcs_fa_1.html>
> >
> > >
> > <http://weblogs.java.net/blog/vivekp/archive/2007/02/jaxws_21_fcs_fa_1.html
> >
<http://weblogs.java.net/blog/vivekp/archive/2007/02/jaxws_21_fcs_fa_1.html>>
> > > > >>
> > > > >> Here is an excerpt from Vivek's blog about the Key Features.
> > > > >>
> > > > >> * Reference Implementation (RI) of JAX-WS 2.1. Full JAX-WS 2.1
> > > > >> Specification <http://jcp.org/en/jsr/detail?id=224
> > <http://jcp.org/en/jsr/detail?id=224>
> > > <http://jcp.org/en/jsr/detail?id=224
> > <http://jcp.org/en/jsr/detail?id=224>>> compliance
> > > > >> * Development Tools
> > > > >> o WSDL to Java generator
> > > > >> + Wsimport command line tool
> > > > >> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimport.html
> > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimport.html>
> > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimport.html
> > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimport.html>>>,
> > > > >> ant task
> > > > >> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimportant.html
> > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimportant.html>
> > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimportant.html
> > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimportant.html>>>
> > > > >> and Maven2 plugin
> > > > >> <http://mojo.codehaus.org/jaxws-maven-plugin/index.html
> > <http://mojo.codehaus.org/jaxws-maven-plugin/index.html>
> > > <http://mojo.codehaus.org/jaxws-maven-plugin/index.html
> > <http://mojo.codehaus.org/jaxws-maven-plugin/index.html>>>
> > > > >> o Java to WSDL generator
> > > > >> + Wsgen command line tool
> > > > >> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgen.html
> > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgen.html>
> > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgen.html
> > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgen.html>>>,
> > > > >> ant Task
> > > > >> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgenant.html
> > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgenant.html>
> > > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgenant.html
> > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgenant.html>>>
> > > > >> and Maven2 plugin
> > > > >> <http://mojo.codehaus.org/jaxws-maven-plugin/index.html
> > <http://mojo.codehaus.org/jaxws-maven-plugin/index.html>
> > > <http://mojo.codehaus.org/jaxws-maven-plugin/index.html
> > <http://mojo.codehaus.org/jaxws-maven-plugin/index.html>>>
> > > > >> o Integrated with NetBeans 5.5.1
> > > > >> <http://www.netbeans.info/downloads/dev.php
> > <http://www.netbeans.info/downloads/dev.php>
> > > <http://www.netbeans.info/downloads/dev.php
> > <http://www.netbeans.info/downloads/dev.php>>>
> > > > >> * Standards
> > > > >> o Web Services Addressing 1.0 - Core, SOAP Binding and WSDL
> > > > >> Binding
> > > > >> o WS-Addressing - Member Submission
> > > > >> o SOAP 1.1 and 1.2
> > > > >> o REST and XML/HTTP
> > > > >> o WS-I Basic Profile 1.1, Simple SOAP Binding Profile 1.0 and
> > > > >> Attachment Profile 1.0
> > > > >> o MTOM
> > > > >> * Extensions (May not be final unless says so)
> > > > >> o Web Services Interoperable Technologies ( WSIT
> > > > >> <https://wsit.dev.java.net/index.html#downloads
> > <https://wsit.dev.java.net/index.html#downloads>
> > > <https://wsit.dev.java.net/index.html#downloads
> > <https://wsit.dev.java.net/index.html#downloads>>>) - enables
> > > > >> .NET 3.0 interoperability
> > > > >> + WS-ReliableMessaging
> > > > >> + WS-Policy
> > > > >> + WS-MEX
> > > > >> + WS-Security/WS-Security Policy
> > > > >> + WS-Trust/WS-Secure Conversation
> > > > >> + WS-AT/WS-Tx (Supported only on Glassfish v2)
> > > > >> + SOAP/TCP
> > > > >> o Spring support <https://jax-ws-commons.dev.java.net/spring/
> > <https://jax-ws-commons.dev.java.net/spring/>
> > > <https://jax-ws-commons.dev.java.net/spring/
> > <https://jax-ws-commons.dev.java.net/spring/>>>
> > > > >> o Pluggable Transport
> > > > >> <https://jax-ws.dev.java.net/transport.html
> > <https://jax-ws.dev.java.net/transport.html>
> > > <https://jax-ws.dev.java.net/transport.html
> > <https://jax-ws.dev.java.net/transport.html>>>
> > > > >> + In-VM transport
> > > > >> + Servlet transport (bundled with the RI)
> > > > >> + JMS transport <http://jms-ws-transport.dev.java.net/
> > <http://jms-ws-transport.dev.java.net/>
> > > <http://jms-ws-transport.dev.java.net/
> > <http://jms-ws-transport.dev.java.net/>>>
> > > > >> + SOAP over TCP transport (part of WSIT
> > > > >> <https://wsit.dev.java.net <https://wsit.dev.java.net>
> > <https://wsit.dev.java.net <https://wsit.dev.java.net>>>)
> > > > >> o FastInfoset (bundled with JAX-WS 2.1 RI)
> > > > >> <https://fi.dev.java.net/ <https://fi.dev.java.net/>
> > <https://fi.dev.java.net/ <https://fi.dev.java.net/>>>
> > > > >> + ITU-T Rec. X.891 | ISO/IEC 24824-1
> > > > >> <http://www.itu.int/rec/T-REC-X.891-200505-I/e
> > <http://www.itu.int/rec/T-REC-X.891-200505-I/e>
> > > <http://www.itu.int/rec/T-REC-X.891-200505-I/e
> > <http://www.itu.int/rec/T-REC-X.891-200505-I/e>>>
> > > > >> o JBI Service Engine and Binding Component(part of Glassfish v2)
> > > > >> o HTTP Binding Component
> > > > >> <http://www.glassfishwiki.org/jbiwiki/Wiki.jsp?page=HTTPBC
> > <http://www.glassfishwiki.org/jbiwiki/Wiki.jsp?page=HTTPBC>
> > > <http://www.glassfishwiki.org/jbiwiki/Wiki.jsp?page=HTTPBC
> > <http://www.glassfishwiki.org/jbiwiki/Wiki.jsp?page=HTTPBC>>>,
> > > > >> used by Open JBI component
> > > > >> <https://open-jbi-components.dev.java.net/
> > <https://open-jbi-components.dev.java.net/>
> > > <https://open-jbi-components.dev.java.net/
> > <https://open-jbi-components.dev.java.net/>>>
> > > > >> * Data binding - JAXB 2.1.2 RI
> > <https://jaxb.dev.java.net/2.1.2/ <https://jaxb.dev.java.net/2.1.2/>
> > > <https://jaxb.dev.java.net/2.1.2/ <https://jaxb.dev.java.net/2.1.2/>>>
> > > > >> * Server Side Asynchrony - AsyncProvider
> > > > >> <https://jax-ws.dev.java.net/nonav/2.1/docs/asyncprovider.html
> > <https://jax-ws.dev.java.net/nonav/2.1/docs/asyncprovider.html>
> > > <https://jax-ws.dev.java.net/nonav/2.1/docs/asyncprovider.html
> > <https://jax-ws.dev.java.net/nonav/2.1/docs/asyncprovider.html>>>
> > > > >> * Stateful Web Services
> > > > >>
> > > <https://jax-ws.dev.java.net/nonav/2.1/docs/statefulWebservice.html
> > <https://jax-ws.dev.java.net/nonav/2.1/docs/statefulWebservice.html>
> > > <https://jax-ws.dev.java.net/nonav/2.1/docs/statefulWebservice.html
> > <https://jax-ws.dev.java.net/nonav/2.1/docs/statefulWebservice.html>>>
> > > > >> * Support for custom WebServiceFeature
> > > > >>
> > >
> >
<http://weblogs.java.net/blog/ramapulavarthi/archive/2007/01/extending_jaxws.htm\
l
> >
<http://weblogs.java.net/blog/ramapulavarthi/archive/2007/01/extending_jaxws.htm\
l>
> >
> > >
> >
<http://weblogs.java.net/blog/ramapulavarthi/archive/2007/01/extending_jaxws.htm\
l
> >
<http://weblogs.java.net/blog/ramapulavarthi/archive/2007/01/extending_jaxws.htm\
l>>>
> > > > >> * Hosting API
> > > > >>
> > >
> >
<https://jax-ws-architecture-document.dev.java.net/nonav/doc21/index.html?com/su\
n/xml/ws/api/server/package-summary.html
> >
<https://jax-ws-architecture-document.dev.java.net/nonav/doc21/index.html?com/su\
n/xml/ws/api/server/package-summary.html>
> >
> > >
> >
<https://jax-ws-architecture-document.dev.java.net/nonav/doc21/index.html?com/su\
n/xml/ws/api/server/package-summary.html
> >
<https://jax-ws-architecture-document.dev.java.net/nonav/doc21/index.html?com/su\
n/xml/ws/api/server/package-summary.html>>>
> > > > >>
> > > > >> o These APIs can be used by a J2EE application server to
> > > > >> integrate JAX-WS 2.1 RI for hosting JAX-WS services
> > > > >> * Endpoint Deployment
> > > > >> o Glassfish v2 <https://glassfish.dev.java.net
> > <https://glassfish.dev.java.net>
> > > <https://glassfish.dev.java.net <https://glassfish.dev.java.net>>>
> > > > >> + Tightly integrated with Glassfish
> > > > >> + Supports EJB and Web endpoints
> > > > >> + 109 based deployment support for better portability
> > > > >> + JAX-WS RI specific deployment descriptor support
> > > > >> o Sun One Application Server 9.0 ur1
> > > > >> <http://www.sun.com/software/products/appsrvr_pe/index.xml
> > <http://www.sun.com/software/products/appsrvr_pe/index.xml>
> > > <http://www.sun.com/software/products/appsrvr_pe/index.xml
> > <http://www.sun.com/software/products/appsrvr_pe/index.xml>>>
> > > > >> o Light weight HTTP server
> > > > >> + On JDK 1.5 through http.jar distributed with the
> > > > >> JAX-WS 2.1 RI bundle
> > > > >> + Bundled with JDK 6
> > > > >> o Any other container that supports Servlet 2.4, such as
> > > > >> Tomcat, Jetty, Geronimo, JBoss, Resin, ... You name it!
> > > > >>
> > > > >>
> > > > >>
> > > > >>
> > > > >> ----------------------------------------------------------
> > > > >> This group is a forum for builders of SOAP implementations to
> > > discuss implementation and interoperability issues. Please stay
> > on-topic.
> > > > >> Yahoo! Groups Links
> > > > >>
> > > > >>
> > > > >>
> > > > >>
> > > > >>
> > > > >>
> > > > >
> > > > >
> > > > > ----------------------------------------------------------
> > > > > This group is a forum for builders of SOAP implementations to
> > > discuss implementation and interoperability issues. Please stay
> > on-topic.
> > > > > Yahoo! Groups Links
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > > ----------------------------------------------------------
> > > > This group is a forum for builders of SOAP implementations to
> > > discuss implementation and interoperability issues. Please stay
> > on-topic.
> > > > Yahoo! Groups Links
> > > >
> > > >
> > > >
> > > >
> > >
> > > --
> > > Davanum Srinivas :: http://wso2.org/ <http://wso2.org/>
> > <http://wso2.org/ <http://wso2.org/>> :: Oxygen for
> > > Web Services Developers
> > >
> > >
> >
> >
>
>
> -----------------------------------------------------------------
> This group is a forum for builders of SOAP implementations to discuss
implementation and interoperability issues.  Please stay on-topic.
> Yahoo! Groups Links
>
>
>
>


--
Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers

Oh, you are talking about the data corruption mentioned in Kohsuke's
blog
(http://weblogs.java.net/blog/kohsuke/archive/2007/02/jaxws_ri_21_ben.html).
Yea Dims, we made that up;  get real dude.  Kohsuke even mentioned in
his blog that we were not sure why it happened and that it might even be
a Glassfish issue.

Doug Kohlert wrote:
>
> What data corruption are you talking about? I didn't mention anything
> about data corruption.
>
> Davanum Srinivas wrote:
> >
> > Doug,
> >
> > Nice party line! So the ADB data corruption issue was something you
> > made up? Or did it really happen?
> >
> > -- dims
> >
> > On 2/8/07, Doug Kohlert <doug.kohlert@...
> <mailto:doug.kohlert%40sun.com>
> > <mailto:doug.kohlert%40sun.com>> wrote:
> > > Good point, you may want to post your comment to Vivek's blog. That
> > > said, since there are limitations in both
> > > ADB and JiBX when compiling schema to Java, we felt this was the most
> > > appropriate match of capabilities.
> > > So this benchmark really is more of an apples-to-apples comparison
> > > rather than an apples-to-oranges comparison that you suggest.
> > >
> > > Dennis Sosnoski wrote:
> > > > "Benchmarking" against Axis2-XMLBeans (as shown in the linked
> blog) is
> > > > ridiculous. XMLBeans is much slower than either ADB or JiBX data
> > binding
> > > > for Axis2. If you're going to make performance claims for your
> > software,
> > > > at least try to make the tests half way reasonable.
> > > >
> > > > - Dennis
> > > >
> > > > Dennis M. Sosnoski
> > > > SOA and Web Services in Java
> > > > Training and Consulting
> > > > http://www.sosnoski.com <http://www.sosnoski.com>
> <http://www.sosnoski.com <http://www.sosnoski.com>> -
> > http://www.sosnoski.co.nz <http://www.sosnoski.co.nz>
> <http://www.sosnoski.co.nz <http://www.sosnoski.co.nz>>
> > > > Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117
> > > >
> > > >
> > > >
> > > > Doug Kohlert wrote:
> > > >
> > > >> We are proud to announce the release of JAX-WS 2.1 RI FCS. JAX-WS
> > 2.1 is
> > > >> a major re-architecture over JAX-WS 2.0 without changing the
> standard
> > > >> JAX-WS APIs or programming model. The benefits of this is a
> very fast
> > > >> implementation and an extremely flexible, extensible
> architecture. To
> > > >> read more about how fast the RI is and the new functionality
> that it
> > > >> contains, read Vivek's blog at:
> > > >>
> >
> http://weblogs.java.net/blog/vivekp/archive/2007/02/jaxws_21_fcs_fa_1.html
> <http://weblogs.java.net/blog/vivekp/archive/2007/02/jaxws_21_fcs_fa_1.html>
>
> >
> <http://weblogs.java.net/blog/vivekp/archive/2007/02/jaxws_21_fcs_fa_1.html
> <http://weblogs.java.net/blog/vivekp/archive/2007/02/jaxws_21_fcs_fa_1.html>>
> > > >>
> > > >> Here is an excerpt from Vivek's blog about the Key Features.
> > > >>
> > > >> * Reference Implementation (RI) of JAX-WS 2.1. Full JAX-WS 2.1
> > > >> Specification <http://jcp.org/en/jsr/detail?id=224
> <http://jcp.org/en/jsr/detail?id=224>
> > <http://jcp.org/en/jsr/detail?id=224
> <http://jcp.org/en/jsr/detail?id=224>>> compliance
> > > >> * Development Tools
> > > >> o WSDL to Java generator
> > > >> + Wsimport command line tool
> > > >> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimport.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimport.html>
> > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimport.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimport.html>>>,
> > > >> ant task
> > > >> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimportant.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimportant.html>
> > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimportant.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimportant.html>>>
> > > >> and Maven2 plugin
> > > >> <http://mojo.codehaus.org/jaxws-maven-plugin/index.html
> <http://mojo.codehaus.org/jaxws-maven-plugin/index.html>
> > <http://mojo.codehaus.org/jaxws-maven-plugin/index.html
> <http://mojo.codehaus.org/jaxws-maven-plugin/index.html>>>
> > > >> o Java to WSDL generator
> > > >> + Wsgen command line tool
> > > >> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgen.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgen.html>
> > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgen.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgen.html>>>,
> > > >> ant Task
> > > >> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgenant.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgenant.html>
> > <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgenant.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgenant.html>>>
> > > >> and Maven2 plugin
> > > >> <http://mojo.codehaus.org/jaxws-maven-plugin/index.html
> <http://mojo.codehaus.org/jaxws-maven-plugin/index.html>
> > <http://mojo.codehaus.org/jaxws-maven-plugin/index.html
> <http://mojo.codehaus.org/jaxws-maven-plugin/index.html>>>
> > > >> o Integrated with NetBeans 5.5.1
> > > >> <http://www.netbeans.info/downloads/dev.php
> <http://www.netbeans.info/downloads/dev.php>
> > <http://www.netbeans.info/downloads/dev.php
> <http://www.netbeans.info/downloads/dev.php>>>
> > > >> * Standards
> > > >> o Web Services Addressing 1.0 - Core, SOAP Binding and WSDL
> > > >> Binding
> > > >> o WS-Addressing - Member Submission
> > > >> o SOAP 1.1 and 1.2
> > > >> o REST and XML/HTTP
> > > >> o WS-I Basic Profile 1.1, Simple SOAP Binding Profile 1.0 and
> > > >> Attachment Profile 1.0
> > > >> o MTOM
> > > >> * Extensions (May not be final unless says so)
> > > >> o Web Services Interoperable Technologies ( WSIT
> > > >> <https://wsit.dev.java.net/index.html#downloads
> <https://wsit.dev.java.net/index.html#downloads>
> > <https://wsit.dev.java.net/index.html#downloads
> <https://wsit.dev.java.net/index.html#downloads>>>) - enables
> > > >> .NET 3.0 interoperability
> > > >> + WS-ReliableMessaging
> > > >> + WS-Policy
> > > >> + WS-MEX
> > > >> + WS-Security/WS-Security Policy
> > > >> + WS-Trust/WS-Secure Conversation
> > > >> + WS-AT/WS-Tx (Supported only on Glassfish v2)
> > > >> + SOAP/TCP
> > > >> o Spring support <https://jax-ws-commons.dev.java.net/spring/
> <https://jax-ws-commons.dev.java.net/spring/>
> > <https://jax-ws-commons.dev.java.net/spring/
> <https://jax-ws-commons.dev.java.net/spring/>>>
> > > >> o Pluggable Transport
> > > >> <https://jax-ws.dev.java.net/transport.html
> <https://jax-ws.dev.java.net/transport.html>
> > <https://jax-ws.dev.java.net/transport.html
> <https://jax-ws.dev.java.net/transport.html>>>
> > > >> + In-VM transport
> > > >> + Servlet transport (bundled with the RI)
> > > >> + JMS transport <http://jms-ws-transport.dev.java.net/
> <http://jms-ws-transport.dev.java.net/>
> > <http://jms-ws-transport.dev.java.net/
> <http://jms-ws-transport.dev.java.net/>>>
> > > >> + SOAP over TCP transport (part of WSIT
> > > >> <https://wsit.dev.java.net <https://wsit.dev.java.net>
> <https://wsit.dev.java.net <https://wsit.dev.java.net>>>)
> > > >> o FastInfoset (bundled with JAX-WS 2.1 RI)
> > > >> <https://fi.dev.java.net/ <https://fi.dev.java.net/>
> <https://fi.dev.java.net/ <https://fi.dev.java.net/>>>
> > > >> + ITU-T Rec. X.891 | ISO/IEC 24824-1
> > > >> <http://www.itu.int/rec/T-REC-X.891-200505-I/e
> <http://www.itu.int/rec/T-REC-X.891-200505-I/e>
> > <http://www.itu.int/rec/T-REC-X.891-200505-I/e
> <http://www.itu.int/rec/T-REC-X.891-200505-I/e>>>
> > > >> o JBI Service Engine and Binding Component(part of Glassfish v2)
> > > >> o HTTP Binding Component
> > > >> <http://www.glassfishwiki.org/jbiwiki/Wiki.jsp?page=HTTPBC
> <http://www.glassfishwiki.org/jbiwiki/Wiki.jsp?page=HTTPBC>
> > <http://www.glassfishwiki.org/jbiwiki/Wiki.jsp?page=HTTPBC
> <http://www.glassfishwiki.org/jbiwiki/Wiki.jsp?page=HTTPBC>>>,
> > > >> used by Open JBI component
> > > >> <https://open-jbi-components.dev.java.net/
> <https://open-jbi-components.dev.java.net/>
> > <https://open-jbi-components.dev.java.net/
> <https://open-jbi-components.dev.java.net/>>>
> > > >> * Data binding - JAXB 2.1.2 RI
> <https://jaxb.dev.java.net/2.1.2/ <https://jaxb.dev.java.net/2.1.2/>
> > <https://jaxb.dev.java.net/2.1.2/ <https://jaxb.dev.java.net/2.1.2/>>>
> > > >> * Server Side Asynchrony - AsyncProvider
> > > >> <https://jax-ws.dev.java.net/nonav/2.1/docs/asyncprovider.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/asyncprovider.html>
> > <https://jax-ws.dev.java.net/nonav/2.1/docs/asyncprovider.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/asyncprovider.html>>>
> > > >> * Stateful Web Services
> > > >>
> > <https://jax-ws.dev.java.net/nonav/2.1/docs/statefulWebservice.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/statefulWebservice.html>
> > <https://jax-ws.dev.java.net/nonav/2.1/docs/statefulWebservice.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/statefulWebservice.html>>>
> > > >> * Support for custom WebServiceFeature
> > > >>
> >
>
<http://weblogs.java.net/blog/ramapulavarthi/archive/2007/01/extending_jaxws.htm\
l
>
<http://weblogs.java.net/blog/ramapulavarthi/archive/2007/01/extending_jaxws.htm\
l>
>
> >
>
<http://weblogs.java.net/blog/ramapulavarthi/archive/2007/01/extending_jaxws.htm\
l
>
<http://weblogs.java.net/blog/ramapulavarthi/archive/2007/01/extending_jaxws.htm\
l>>>
> > > >> * Hosting API
> > > >>
> >
>
<https://jax-ws-architecture-document.dev.java.net/nonav/doc21/index.html?com/su\
n/xml/ws/api/server/package-summary.html
>
<https://jax-ws-architecture-document.dev.java.net/nonav/doc21/index.html?com/su\
n/xml/ws/api/server/package-summary.html>
>
> >
>
<https://jax-ws-architecture-document.dev.java.net/nonav/doc21/index.html?com/su\
n/xml/ws/api/server/package-summary.html
>
<https://jax-ws-architecture-document.dev.java.net/nonav/doc21/index.html?com/su\
n/xml/ws/api/server/package-summary.html>>>
> > > >>
> > > >> o These APIs can be used by a J2EE application server to
> > > >> integrate JAX-WS 2.1 RI for hosting JAX-WS services
> > > >> * Endpoint Deployment
> > > >> o Glassfish v2 <https://glassfish.dev.java.net
> <https://glassfish.dev.java.net>
> > <https://glassfish.dev.java.net <https://glassfish.dev.java.net>>>
> > > >> + Tightly integrated with Glassfish
> > > >> + Supports EJB and Web endpoints
> > > >> + 109 based deployment support for better portability
> > > >> + JAX-WS RI specific deployment descriptor support
> > > >> o Sun One Application Server 9.0 ur1
> > > >> <http://www.sun.com/software/products/appsrvr_pe/index.xml
> <http://www.sun.com/software/products/appsrvr_pe/index.xml>
> > <http://www.sun.com/software/products/appsrvr_pe/index.xml
> <http://www.sun.com/software/products/appsrvr_pe/index.xml>>>
> > > >> o Light weight HTTP server
> > > >> + On JDK 1.5 through http.jar distributed with the
> > > >> JAX-WS 2.1 RI bundle
> > > >> + Bundled with JDK 6
> > > >> o Any other container that supports Servlet 2.4, such as
> > > >> Tomcat, Jetty, Geronimo, JBoss, Resin, ... You name it!
> > > >>
> > > >>
> > > >>
> > > >>
> > > >> ----------------------------------------------------------
> > > >> This group is a forum for builders of SOAP implementations to
> > discuss implementation and interoperability issues. Please stay
> on-topic.
> > > >> Yahoo! Groups Links
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >
> > > >
> > > > ----------------------------------------------------------
> > > > This group is a forum for builders of SOAP implementations to
> > discuss implementation and interoperability issues. Please stay
> on-topic.
> > > > Yahoo! Groups Links
> > > >
> > > >
> > > >
> > > >
> > >
> > >
> > > ----------------------------------------------------------
> > > This group is a forum for builders of SOAP implementations to
> > discuss implementation and interoperability issues. Please stay
> on-topic.
> > > Yahoo! Groups Links
> > >
> > >
> > >
> > >
> >
> > --
> > Davanum Srinivas :: http://wso2.org/ <http://wso2.org/>
> <http://wso2.org/ <http://wso2.org/>> :: Oxygen for
> > Web Services Developers
> >
> >
>
>

Dennis Sosnoski wrote:
> I did post a comment to the blog - but the comment doesn't appear to
> show up when viewing the blog page. I don't know if this is a setting
> issue for that page, or just a bug in the software.
>
OK, sorry about the confusion.
> The JiBX support in Axis2 is currently more focused around working with
> existing code than on generating code from schema, so I can understand
> if you wanted to skip that. I'm surprised you had problems with ADB code
> generation for the relatively simple schemas used in this test, though.
> If you did run into problems, posting a message to the Axis2 developers
> list or entering a bug in Jira is a sounder approach for accurate
> benchmarking than arbitrarily changing to a much slower data binding
> framework.
>
I am sure the team will figure it out (perhaps with help from the Axis
folks) and we can post additional comparisons in the near future.


>   - Dennis
>
> Doug Kohlert wrote:
>
>> Good point, you may want to post your comment to Vivek's blog.  That
>> said, since there are limitations in both
>> ADB and JiBX when compiling schema to Java, we felt this was the most
>> appropriate match of capabilities.
>> So this benchmark really is more of an apples-to-apples comparison
>> rather than an apples-to-oranges comparison that you suggest.
>>
>> Dennis Sosnoski wrote:
>>
>>
>>> "Benchmarking" against Axis2-XMLBeans (as shown in the linked blog) is
>>> ridiculous. XMLBeans is much slower than either ADB or JiBX data binding
>>> for Axis2. If you're going to make performance claims for your software,
>>> at least try to make the tests half way reasonable.
>>>
>>>   - Dennis
>>>
>>> Dennis M. Sosnoski
>>> SOA and Web Services in Java
>>> Training and Consulting
>>> http://www.sosnoski.com - http://www.sosnoski.co.nz
>>> Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117
>>>
>>>
>>>
>>> Doug Kohlert wrote:
>>>
>>>
>>>
>>>> We are proud to announce the release of JAX-WS 2.1 RI FCS. JAX-WS 2.1 is
>>>> a major re-architecture over JAX-WS 2.0 without changing the standard
>>>> JAX-WS APIs or programming model.  The benefits of this is a very fast
>>>> implementation and an extremely flexible, extensible architecture.  To
>>>> read more about how fast the RI is and the new functionality that it
>>>> contains, read Vivek's blog at:
>>>> http://weblogs.java.net/blog/vivekp/archive/2007/02/jaxws_21_fcs_fa_1.html
>>>>
>>>> Here is an excerpt from Vivek's blog about the Key Features.
>>>>
>>>>     * Reference Implementation (RI) of JAX-WS 2.1. Full JAX-WS 2.1
>>>>       Specification <http://jcp.org/en/jsr/detail?id=224> compliance
>>>>     * Development Tools
>>>>           o WSDL to Java generator
>>>>                 + Wsimport command line tool
>>>>                  
<https://jax-ws.dev.java.net/nonav/2.1/docs/wsimport.html>,
>>>>                   ant task
>>>>                  
<https://jax-ws.dev.java.net/nonav/2.1/docs/wsimportant.html>
>>>>                   and Maven2 plugin
>>>>                   <http://mojo.codehaus.org/jaxws-maven-plugin/index.html>
>>>>           o Java to WSDL generator
>>>>                 + Wsgen command line tool
>>>>                   <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgen.html>,
>>>>                   ant Task
>>>>                  
<https://jax-ws.dev.java.net/nonav/2.1/docs/wsgenant.html>
>>>>                   and Maven2 plugin
>>>>                   <http://mojo.codehaus.org/jaxws-maven-plugin/index.html>
>>>>           o Integrated with NetBeans  5.5.1
>>>>             <http://www.netbeans.info/downloads/dev.php>
>>>>     * Standards
>>>>           o Web Services Addressing 1.0 - Core, SOAP Binding and WSDL
>>>>             Binding
>>>>           o WS-Addressing  - Member Submission
>>>>           o SOAP 1.1 and 1.2
>>>>           o REST and XML/HTTP
>>>>           o WS-I Basic Profile 1.1, Simple SOAP Binding Profile 1.0 and
>>>>             Attachment Profile 1.0
>>>>           o MTOM
>>>>     * Extensions (May not be final unless says so)
>>>>           o Web Services Interoperable Technologies ( WSIT
>>>>             <https://wsit.dev.java.net/index.html#downloads>) - enables
>>>>             .NET 3.0 interoperability
>>>>                 + WS-ReliableMessaging
>>>>                 + WS-Policy
>>>>                 + WS-MEX
>>>>                 + WS-Security/WS-Security Policy
>>>>                 + WS-Trust/WS-Secure Conversation
>>>>                 + WS-AT/WS-Tx (Supported only on Glassfish v2)
>>>>                 + SOAP/TCP
>>>>           o Spring support <https://jax-ws-commons.dev.java.net/spring/>
>>>>           o Pluggable Transport
>>>>             <https://jax-ws.dev.java.net/transport.html>
>>>>                 + In-VM transport
>>>>                 + Servlet transport (bundled with the RI)
>>>>                 + JMS transport <http://jms-ws-transport.dev.java.net/>
>>>>                 + SOAP over TCP transport (part of WSIT
>>>>                   <https://wsit.dev.java.net>)
>>>>           o FastInfoset (bundled with JAX-WS 2.1 RI)
>>>>             <https://fi.dev.java.net/>
>>>>                 + ITU-T Rec. X.891 | ISO/IEC 24824-1
>>>>                   <http://www.itu.int/rec/T-REC-X.891-200505-I/e>
>>>>           o JBI Service Engine and Binding Component(part of Glassfish v2)
>>>>           o HTTP Binding Component
>>>>             <http://www.glassfishwiki.org/jbiwiki/Wiki.jsp?page=HTTPBC>,
>>>>             used by Open JBI component
>>>>             <https://open-jbi-components.dev.java.net/>
>>>>     * Data binding - JAXB 2.1.2 RI <https://jaxb.dev.java.net/2.1.2/>
>>>>     * Server Side Asynchrony - AsyncProvider
>>>>       <https://jax-ws.dev.java.net/nonav/2.1/docs/asyncprovider.html>
>>>>     * Stateful Web Services
>>>>       <https://jax-ws.dev.java.net/nonav/2.1/docs/statefulWebservice.html>
>>>>     * Support for custom WebServiceFeature
>>>>      
<http://weblogs.java.net/blog/ramapulavarthi/archive/2007/01/extending_jaxws.htm\
l>
>>>>     * Hosting API
>>>>      
<https://jax-ws-architecture-document.dev.java.net/nonav/doc21/index.html?com/su\
n/xml/ws/api/server/package-summary.html>
>>>>
>>>>           o These APIs can be used by a J2EE application server to
>>>>             integrate JAX-WS 2.1 RI for hosting JAX-WS services
>>>>     * Endpoint Deployment
>>>>           o Glassfish v2 <https://glassfish.dev.java.net>
>>>>                 + Tightly integrated with Glassfish
>>>>                 + Supports EJB and Web endpoints
>>>>                 + 109 based deployment support for better portability
>>>>                 + JAX-WS RI specific deployment descriptor support
>>>>           o Sun One Application Server 9.0 ur1
>>>>             <http://www.sun.com/software/products/appsrvr_pe/index.xml>
>>>>           o Light weight HTTP server
>>>>                 + On JDK 1.5 through http.jar distributed with the
>>>>                   JAX-WS 2.1 RI bundle
>>>>                 + Bundled with JDK 6
>>>>           o Any other container that supports Servlet 2.4, such as
>>>>             Tomcat, Jetty, Geronimo, JBoss, Resin, ... You name it!
>>>>
>>>>
>>>>
>>>>
>>>> -----------------------------------------------------------------
>>>> This group is a forum for builders of SOAP implementations to discuss
implementation and interoperability issues.  Please stay on-topic.
>>>> Yahoo! Groups Links
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>> -----------------------------------------------------------------
>>> This group is a forum for builders of SOAP implementations to discuss
implementation and interoperability issues.  Please stay on-topic.
>>> Yahoo! Groups Links
>>>
>>>
>>>
>>>
>>>
>>>
>> -----------------------------------------------------------------
>> This group is a forum for builders of SOAP implementations to discuss
implementation and interoperability issues.  Please stay on-topic.
>> Yahoo! Groups Links
>>
>>
>>
>>
>>
>>
>
>
> -----------------------------------------------------------------
> This group is a forum for builders of SOAP implementations to discuss
implementation and interoperability issues.  Please stay on-topic.
> Yahoo! Groups Links
>
>
>
>

What data corruption are you talking about? I didn't mention anything
about data corruption.

Davanum Srinivas wrote:
>
> Doug,
>
> Nice party line! So the ADB data corruption issue was something you
> made up? Or did it really happen?
>
> -- dims
>
> On 2/8/07, Doug Kohlert <doug.kohlert@...
> <mailto:doug.kohlert%40sun.com>> wrote:
> > Good point, you may want to post your comment to Vivek's blog. That
> > said, since there are limitations in both
> > ADB and JiBX when compiling schema to Java, we felt this was the most
> > appropriate match of capabilities.
> > So this benchmark really is more of an apples-to-apples comparison
> > rather than an apples-to-oranges comparison that you suggest.
> >
> > Dennis Sosnoski wrote:
> > > "Benchmarking" against Axis2-XMLBeans (as shown in the linked blog) is
> > > ridiculous. XMLBeans is much slower than either ADB or JiBX data
> binding
> > > for Axis2. If you're going to make performance claims for your
> software,
> > > at least try to make the tests half way reasonable.
> > >
> > > - Dennis
> > >
> > > Dennis M. Sosnoski
> > > SOA and Web Services in Java
> > > Training and Consulting
> > > http://www.sosnoski.com <http://www.sosnoski.com> -
> http://www.sosnoski.co.nz <http://www.sosnoski.co.nz>
> > > Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117
> > >
> > >
> > >
> > > Doug Kohlert wrote:
> > >
> > >> We are proud to announce the release of JAX-WS 2.1 RI FCS. JAX-WS
> 2.1 is
> > >> a major re-architecture over JAX-WS 2.0 without changing the standard
> > >> JAX-WS APIs or programming model. The benefits of this is a very fast
> > >> implementation and an extremely flexible, extensible architecture. To
> > >> read more about how fast the RI is and the new functionality that it
> > >> contains, read Vivek's blog at:
> > >>
> http://weblogs.java.net/blog/vivekp/archive/2007/02/jaxws_21_fcs_fa_1.html
> <http://weblogs.java.net/blog/vivekp/archive/2007/02/jaxws_21_fcs_fa_1.html>
> > >>
> > >> Here is an excerpt from Vivek's blog about the Key Features.
> > >>
> > >> * Reference Implementation (RI) of JAX-WS 2.1. Full JAX-WS 2.1
> > >> Specification <http://jcp.org/en/jsr/detail?id=224
> <http://jcp.org/en/jsr/detail?id=224>> compliance
> > >> * Development Tools
> > >> o WSDL to Java generator
> > >> + Wsimport command line tool
> > >> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimport.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimport.html>>,
> > >> ant task
> > >> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimportant.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimportant.html>>
> > >> and Maven2 plugin
> > >> <http://mojo.codehaus.org/jaxws-maven-plugin/index.html
> <http://mojo.codehaus.org/jaxws-maven-plugin/index.html>>
> > >> o Java to WSDL generator
> > >> + Wsgen command line tool
> > >> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgen.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgen.html>>,
> > >> ant Task
> > >> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgenant.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgenant.html>>
> > >> and Maven2 plugin
> > >> <http://mojo.codehaus.org/jaxws-maven-plugin/index.html
> <http://mojo.codehaus.org/jaxws-maven-plugin/index.html>>
> > >> o Integrated with NetBeans 5.5.1
> > >> <http://www.netbeans.info/downloads/dev.php
> <http://www.netbeans.info/downloads/dev.php>>
> > >> * Standards
> > >> o Web Services Addressing 1.0 - Core, SOAP Binding and WSDL
> > >> Binding
> > >> o WS-Addressing - Member Submission
> > >> o SOAP 1.1 and 1.2
> > >> o REST and XML/HTTP
> > >> o WS-I Basic Profile 1.1, Simple SOAP Binding Profile 1.0 and
> > >> Attachment Profile 1.0
> > >> o MTOM
> > >> * Extensions (May not be final unless says so)
> > >> o Web Services Interoperable Technologies ( WSIT
> > >> <https://wsit.dev.java.net/index.html#downloads
> <https://wsit.dev.java.net/index.html#downloads>>) - enables
> > >> .NET 3.0 interoperability
> > >> + WS-ReliableMessaging
> > >> + WS-Policy
> > >> + WS-MEX
> > >> + WS-Security/WS-Security Policy
> > >> + WS-Trust/WS-Secure Conversation
> > >> + WS-AT/WS-Tx (Supported only on Glassfish v2)
> > >> + SOAP/TCP
> > >> o Spring support <https://jax-ws-commons.dev.java.net/spring/
> <https://jax-ws-commons.dev.java.net/spring/>>
> > >> o Pluggable Transport
> > >> <https://jax-ws.dev.java.net/transport.html
> <https://jax-ws.dev.java.net/transport.html>>
> > >> + In-VM transport
> > >> + Servlet transport (bundled with the RI)
> > >> + JMS transport <http://jms-ws-transport.dev.java.net/
> <http://jms-ws-transport.dev.java.net/>>
> > >> + SOAP over TCP transport (part of WSIT
> > >> <https://wsit.dev.java.net <https://wsit.dev.java.net>>)
> > >> o FastInfoset (bundled with JAX-WS 2.1 RI)
> > >> <https://fi.dev.java.net/ <https://fi.dev.java.net/>>
> > >> + ITU-T Rec. X.891 | ISO/IEC 24824-1
> > >> <http://www.itu.int/rec/T-REC-X.891-200505-I/e
> <http://www.itu.int/rec/T-REC-X.891-200505-I/e>>
> > >> o JBI Service Engine and Binding Component(part of Glassfish v2)
> > >> o HTTP Binding Component
> > >> <http://www.glassfishwiki.org/jbiwiki/Wiki.jsp?page=HTTPBC
> <http://www.glassfishwiki.org/jbiwiki/Wiki.jsp?page=HTTPBC>>,
> > >> used by Open JBI component
> > >> <https://open-jbi-components.dev.java.net/
> <https://open-jbi-components.dev.java.net/>>
> > >> * Data binding - JAXB 2.1.2 RI <https://jaxb.dev.java.net/2.1.2/
> <https://jaxb.dev.java.net/2.1.2/>>
> > >> * Server Side Asynchrony - AsyncProvider
> > >> <https://jax-ws.dev.java.net/nonav/2.1/docs/asyncprovider.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/asyncprovider.html>>
> > >> * Stateful Web Services
> > >>
> <https://jax-ws.dev.java.net/nonav/2.1/docs/statefulWebservice.html
> <https://jax-ws.dev.java.net/nonav/2.1/docs/statefulWebservice.html>>
> > >> * Support for custom WebServiceFeature
> > >>
>
<http://weblogs.java.net/blog/ramapulavarthi/archive/2007/01/extending_jaxws.htm\
l
>
<http://weblogs.java.net/blog/ramapulavarthi/archive/2007/01/extending_jaxws.htm\
l>>
> > >> * Hosting API
> > >>
>
<https://jax-ws-architecture-document.dev.java.net/nonav/doc21/index.html?com/su\
n/xml/ws/api/server/package-summary.html
>
<https://jax-ws-architecture-document.dev.java.net/nonav/doc21/index.html?com/su\
n/xml/ws/api/server/package-summary.html>>
> > >>
> > >> o These APIs can be used by a J2EE application server to
> > >> integrate JAX-WS 2.1 RI for hosting JAX-WS services
> > >> * Endpoint Deployment
> > >> o Glassfish v2 <https://glassfish.dev.java.net
> <https://glassfish.dev.java.net>>
> > >> + Tightly integrated with Glassfish
> > >> + Supports EJB and Web endpoints
> > >> + 109 based deployment support for better portability
> > >> + JAX-WS RI specific deployment descriptor support
> > >> o Sun One Application Server 9.0 ur1
> > >> <http://www.sun.com/software/products/appsrvr_pe/index.xml
> <http://www.sun.com/software/products/appsrvr_pe/index.xml>>
> > >> o Light weight HTTP server
> > >> + On JDK 1.5 through http.jar distributed with the
> > >> JAX-WS 2.1 RI bundle
> > >> + Bundled with JDK 6
> > >> o Any other container that supports Servlet 2.4, such as
> > >> Tomcat, Jetty, Geronimo, JBoss, Resin, ... You name it!
> > >>
> > >>
> > >>
> > >>
> > >> ----------------------------------------------------------
> > >> This group is a forum for builders of SOAP implementations to
> discuss implementation and interoperability issues. Please stay on-topic.
> > >> Yahoo! Groups Links
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >
> > >
> > > ----------------------------------------------------------
> > > This group is a forum for builders of SOAP implementations to
> discuss implementation and interoperability issues. Please stay on-topic.
> > > Yahoo! Groups Links
> > >
> > >
> > >
> > >
> >
> >
> > ----------------------------------------------------------
> > This group is a forum for builders of SOAP implementations to
> discuss implementation and interoperability issues. Please stay on-topic.
> > Yahoo! Groups Links
> >
> >
> >
> >
>
> --
> Davanum Srinivas :: http://wso2.org/ <http://wso2.org/> :: Oxygen for
> Web Services Developers
>
>

I did post a comment to the blog - but the comment doesn't appear to
show up when viewing the blog page. I don't know if this is a setting
issue for that page, or just a bug in the software.

The JiBX support in Axis2 is currently more focused around working with
existing code than on generating code from schema, so I can understand
if you wanted to skip that. I'm surprised you had problems with ADB code
generation for the relatively simple schemas used in this test, though.
If you did run into problems, posting a message to the Axis2 developers
list or entering a bug in Jira is a sounder approach for accurate
benchmarking than arbitrarily changing to a much slower data binding
framework.

   - Dennis

Doug Kohlert wrote:
> Good point, you may want to post your comment to Vivek's blog.  That
> said, since there are limitations in both
> ADB and JiBX when compiling schema to Java, we felt this was the most
> appropriate match of capabilities.
> So this benchmark really is more of an apples-to-apples comparison
> rather than an apples-to-oranges comparison that you suggest.
>
> Dennis Sosnoski wrote:
>
>> "Benchmarking" against Axis2-XMLBeans (as shown in the linked blog) is
>> ridiculous. XMLBeans is much slower than either ADB or JiBX data binding
>> for Axis2. If you're going to make performance claims for your software,
>> at least try to make the tests half way reasonable.
>>
>>   - Dennis
>>
>> Dennis M. Sosnoski
>> SOA and Web Services in Java
>> Training and Consulting
>> http://www.sosnoski.com - http://www.sosnoski.co.nz
>> Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117
>>
>>
>>
>> Doug Kohlert wrote:
>>
>>
>>> We are proud to announce the release of JAX-WS 2.1 RI FCS. JAX-WS 2.1 is
>>> a major re-architecture over JAX-WS 2.0 without changing the standard
>>> JAX-WS APIs or programming model.  The benefits of this is a very fast
>>> implementation and an extremely flexible, extensible architecture.  To
>>> read more about how fast the RI is and the new functionality that it
>>> contains, read Vivek's blog at:
>>> http://weblogs.java.net/blog/vivekp/archive/2007/02/jaxws_21_fcs_fa_1.html
>>>
>>> Here is an excerpt from Vivek's blog about the Key Features.
>>>
>>>     * Reference Implementation (RI) of JAX-WS 2.1. Full JAX-WS 2.1
>>>       Specification <http://jcp.org/en/jsr/detail?id=224> compliance
>>>     * Development Tools
>>>           o WSDL to Java generator
>>>                 + Wsimport command line tool
>>>                  
<https://jax-ws.dev.java.net/nonav/2.1/docs/wsimport.html>,
>>>                   ant task
>>>                  
<https://jax-ws.dev.java.net/nonav/2.1/docs/wsimportant.html>
>>>                   and Maven2 plugin
>>>                   <http://mojo.codehaus.org/jaxws-maven-plugin/index.html>
>>>           o Java to WSDL generator
>>>                 + Wsgen command line tool
>>>                   <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgen.html>,
>>>                   ant Task
>>>                   <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgenant.html>
>>>                   and Maven2 plugin
>>>                   <http://mojo.codehaus.org/jaxws-maven-plugin/index.html>
>>>           o Integrated with NetBeans  5.5.1
>>>             <http://www.netbeans.info/downloads/dev.php>
>>>     * Standards
>>>           o Web Services Addressing 1.0 - Core, SOAP Binding and WSDL
>>>             Binding
>>>           o WS-Addressing  - Member Submission
>>>           o SOAP 1.1 and 1.2
>>>           o REST and XML/HTTP
>>>           o WS-I Basic Profile 1.1, Simple SOAP Binding Profile 1.0 and
>>>             Attachment Profile 1.0
>>>           o MTOM
>>>     * Extensions (May not be final unless says so)
>>>           o Web Services Interoperable Technologies ( WSIT
>>>             <https://wsit.dev.java.net/index.html#downloads>) - enables
>>>             .NET 3.0 interoperability
>>>                 + WS-ReliableMessaging
>>>                 + WS-Policy
>>>                 + WS-MEX
>>>                 + WS-Security/WS-Security Policy
>>>                 + WS-Trust/WS-Secure Conversation
>>>                 + WS-AT/WS-Tx (Supported only on Glassfish v2)
>>>                 + SOAP/TCP
>>>           o Spring support <https://jax-ws-commons.dev.java.net/spring/>
>>>           o Pluggable Transport
>>>             <https://jax-ws.dev.java.net/transport.html>
>>>                 + In-VM transport
>>>                 + Servlet transport (bundled with the RI)
>>>                 + JMS transport <http://jms-ws-transport.dev.java.net/>
>>>                 + SOAP over TCP transport (part of WSIT
>>>                   <https://wsit.dev.java.net>)
>>>           o FastInfoset (bundled with JAX-WS 2.1 RI)
>>>             <https://fi.dev.java.net/>
>>>                 + ITU-T Rec. X.891 | ISO/IEC 24824-1
>>>                   <http://www.itu.int/rec/T-REC-X.891-200505-I/e>
>>>           o JBI Service Engine and Binding Component(part of Glassfish v2)
>>>           o HTTP Binding Component
>>>             <http://www.glassfishwiki.org/jbiwiki/Wiki.jsp?page=HTTPBC>,
>>>             used by Open JBI component
>>>             <https://open-jbi-components.dev.java.net/>
>>>     * Data binding - JAXB 2.1.2 RI <https://jaxb.dev.java.net/2.1.2/>
>>>     * Server Side Asynchrony - AsyncProvider
>>>       <https://jax-ws.dev.java.net/nonav/2.1/docs/asyncprovider.html>
>>>     * Stateful Web Services
>>>       <https://jax-ws.dev.java.net/nonav/2.1/docs/statefulWebservice.html>
>>>     * Support for custom WebServiceFeature
>>>      
<http://weblogs.java.net/blog/ramapulavarthi/archive/2007/01/extending_jaxws.htm\
l>
>>>     * Hosting API
>>>      
<https://jax-ws-architecture-document.dev.java.net/nonav/doc21/index.html?com/su\
n/xml/ws/api/server/package-summary.html>
>>>
>>>           o These APIs can be used by a J2EE application server to
>>>             integrate JAX-WS 2.1 RI for hosting JAX-WS services
>>>     * Endpoint Deployment
>>>           o Glassfish v2 <https://glassfish.dev.java.net>
>>>                 + Tightly integrated with Glassfish
>>>                 + Supports EJB and Web endpoints
>>>                 + 109 based deployment support for better portability
>>>                 + JAX-WS RI specific deployment descriptor support
>>>           o Sun One Application Server 9.0 ur1
>>>             <http://www.sun.com/software/products/appsrvr_pe/index.xml>
>>>           o Light weight HTTP server
>>>                 + On JDK 1.5 through http.jar distributed with the
>>>                   JAX-WS 2.1 RI bundle
>>>                 + Bundled with JDK 6
>>>           o Any other container that supports Servlet 2.4, such as
>>>             Tomcat, Jetty, Geronimo, JBoss, Resin, ... You name it!
>>>
>>>
>>>
>>>
>>> -----------------------------------------------------------------
>>> This group is a forum for builders of SOAP implementations to discuss
implementation and interoperability issues.  Please stay on-topic.
>>> Yahoo! Groups Links
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>> -----------------------------------------------------------------
>> This group is a forum for builders of SOAP implementations to discuss
implementation and interoperability issues.  Please stay on-topic.
>> Yahoo! Groups Links
>>
>>
>>
>>
>>
>
>
> -----------------------------------------------------------------
> This group is a forum for builders of SOAP implementations to discuss
implementation and interoperability issues.  Please stay on-topic.
> Yahoo! Groups Links
>
>
>
>
>

Doug,

Nice party line! So the ADB data corruption issue was something you
made up? Or did it really happen?

-- dims

On 2/8/07, Doug Kohlert <doug.kohlert@...> wrote:
> Good point, you may want to post your comment to Vivek's blog.  That
> said, since there are limitations in both
> ADB and JiBX when compiling schema to Java, we felt this was the most
> appropriate match of capabilities.
> So this benchmark really is more of an apples-to-apples comparison
> rather than an apples-to-oranges comparison that you suggest.
>
> Dennis Sosnoski wrote:
> > "Benchmarking" against Axis2-XMLBeans (as shown in the linked blog) is
> > ridiculous. XMLBeans is much slower than either ADB or JiBX data binding
> > for Axis2. If you're going to make performance claims for your software,
> > at least try to make the tests half way reasonable.
> >
> >   - Dennis
> >
> > Dennis M. Sosnoski
> > SOA and Web Services in Java
> > Training and Consulting
> > http://www.sosnoski.com - http://www.sosnoski.co.nz
> > Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117
> >
> >
> >
> > Doug Kohlert wrote:
> >
> >> We are proud to announce the release of JAX-WS 2.1 RI FCS. JAX-WS 2.1 is
> >> a major re-architecture over JAX-WS 2.0 without changing the standard
> >> JAX-WS APIs or programming model.  The benefits of this is a very fast
> >> implementation and an extremely flexible, extensible architecture.  To
> >> read more about how fast the RI is and the new functionality that it
> >> contains, read Vivek's blog at:
> >> http://weblogs.java.net/blog/vivekp/archive/2007/02/jaxws_21_fcs_fa_1.html
> >>
> >> Here is an excerpt from Vivek's blog about the Key Features.
> >>
> >>     * Reference Implementation (RI) of JAX-WS 2.1. Full JAX-WS 2.1
> >>       Specification <http://jcp.org/en/jsr/detail?id=224> compliance
> >>     * Development Tools
> >>           o WSDL to Java generator
> >>                 + Wsimport command line tool
> >>                  
<https://jax-ws.dev.java.net/nonav/2.1/docs/wsimport.html>,
> >>                   ant task
> >>                  
<https://jax-ws.dev.java.net/nonav/2.1/docs/wsimportant.html>
> >>                   and Maven2 plugin
> >>                   <http://mojo.codehaus.org/jaxws-maven-plugin/index.html>
> >>           o Java to WSDL generator
> >>                 + Wsgen command line tool
> >>                   <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgen.html>,
> >>                   ant Task
> >>                  
<https://jax-ws.dev.java.net/nonav/2.1/docs/wsgenant.html>
> >>                   and Maven2 plugin
> >>                   <http://mojo.codehaus.org/jaxws-maven-plugin/index.html>
> >>           o Integrated with NetBeans  5.5.1
> >>             <http://www.netbeans.info/downloads/dev.php>
> >>     * Standards
> >>           o Web Services Addressing 1.0 - Core, SOAP Binding and WSDL
> >>             Binding
> >>           o WS-Addressing  - Member Submission
> >>           o SOAP 1.1 and 1.2
> >>           o REST and XML/HTTP
> >>           o WS-I Basic Profile 1.1, Simple SOAP Binding Profile 1.0 and
> >>             Attachment Profile 1.0
> >>           o MTOM
> >>     * Extensions (May not be final unless says so)
> >>           o Web Services Interoperable Technologies ( WSIT
> >>             <https://wsit.dev.java.net/index.html#downloads>) - enables
> >>             .NET 3.0 interoperability
> >>                 + WS-ReliableMessaging
> >>                 + WS-Policy
> >>                 + WS-MEX
> >>                 + WS-Security/WS-Security Policy
> >>                 + WS-Trust/WS-Secure Conversation
> >>                 + WS-AT/WS-Tx (Supported only on Glassfish v2)
> >>                 + SOAP/TCP
> >>           o Spring support <https://jax-ws-commons.dev.java.net/spring/>
> >>           o Pluggable Transport
> >>             <https://jax-ws.dev.java.net/transport.html>
> >>                 + In-VM transport
> >>                 + Servlet transport (bundled with the RI)
> >>                 + JMS transport <http://jms-ws-transport.dev.java.net/>
> >>                 + SOAP over TCP transport (part of WSIT
> >>                   <https://wsit.dev.java.net>)
> >>           o FastInfoset (bundled with JAX-WS 2.1 RI)
> >>             <https://fi.dev.java.net/>
> >>                 + ITU-T Rec. X.891 | ISO/IEC 24824-1
> >>                   <http://www.itu.int/rec/T-REC-X.891-200505-I/e>
> >>           o JBI Service Engine and Binding Component(part of Glassfish v2)
> >>           o HTTP Binding Component
> >>             <http://www.glassfishwiki.org/jbiwiki/Wiki.jsp?page=HTTPBC>,
> >>             used by Open JBI component
> >>             <https://open-jbi-components.dev.java.net/>
> >>     * Data binding - JAXB 2.1.2 RI <https://jaxb.dev.java.net/2.1.2/>
> >>     * Server Side Asynchrony - AsyncProvider
> >>       <https://jax-ws.dev.java.net/nonav/2.1/docs/asyncprovider.html>
> >>     * Stateful Web Services
> >>       <https://jax-ws.dev.java.net/nonav/2.1/docs/statefulWebservice.html>
> >>     * Support for custom WebServiceFeature
> >>      
<http://weblogs.java.net/blog/ramapulavarthi/archive/2007/01/extending_jaxws.htm\
l>
> >>     * Hosting API
> >>      
<https://jax-ws-architecture-document.dev.java.net/nonav/doc21/index.html?com/su\
n/xml/ws/api/server/package-summary.html>
> >>
> >>           o These APIs can be used by a J2EE application server to
> >>             integrate JAX-WS 2.1 RI for hosting JAX-WS services
> >>     * Endpoint Deployment
> >>           o Glassfish v2 <https://glassfish.dev.java.net>
> >>                 + Tightly integrated with Glassfish
> >>                 + Supports EJB and Web endpoints
> >>                 + 109 based deployment support for better portability
> >>                 + JAX-WS RI specific deployment descriptor support
> >>           o Sun One Application Server 9.0 ur1
> >>             <http://www.sun.com/software/products/appsrvr_pe/index.xml>
> >>           o Light weight HTTP server
> >>                 + On JDK 1.5 through http.jar distributed with the
> >>                   JAX-WS 2.1 RI bundle
> >>                 + Bundled with JDK 6
> >>           o Any other container that supports Servlet 2.4, such as
> >>             Tomcat, Jetty, Geronimo, JBoss, Resin, ... You name it!
> >>
> >>
> >>
> >>
> >> -----------------------------------------------------------------
> >> This group is a forum for builders of SOAP implementations to discuss
implementation and interoperability issues.  Please stay on-topic.
> >> Yahoo! Groups Links
> >>
> >>
> >>
> >>
> >>
> >>
> >
> >
> > -----------------------------------------------------------------
> > This group is a forum for builders of SOAP implementations to discuss
implementation and interoperability issues.  Please stay on-topic.
> > Yahoo! Groups Links
> >
> >
> >
> >
>
>
> -----------------------------------------------------------------
> This group is a forum for builders of SOAP implementations to discuss
implementation and interoperability issues.  Please stay on-topic.
> Yahoo! Groups Links
>
>
>
>


--
Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers

Good point, you may want to post your comment to Vivek's blog.  That
said, since there are limitations in both
ADB and JiBX when compiling schema to Java, we felt this was the most
appropriate match of capabilities.
So this benchmark really is more of an apples-to-apples comparison
rather than an apples-to-oranges comparison that you suggest.

Dennis Sosnoski wrote:
> "Benchmarking" against Axis2-XMLBeans (as shown in the linked blog) is
> ridiculous. XMLBeans is much slower than either ADB or JiBX data binding
> for Axis2. If you're going to make performance claims for your software,
> at least try to make the tests half way reasonable.
>
>   - Dennis
>
> Dennis M. Sosnoski
> SOA and Web Services in Java
> Training and Consulting
> http://www.sosnoski.com - http://www.sosnoski.co.nz
> Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117
>
>
>
> Doug Kohlert wrote:
>
>> We are proud to announce the release of JAX-WS 2.1 RI FCS. JAX-WS 2.1 is
>> a major re-architecture over JAX-WS 2.0 without changing the standard
>> JAX-WS APIs or programming model.  The benefits of this is a very fast
>> implementation and an extremely flexible, extensible architecture.  To
>> read more about how fast the RI is and the new functionality that it
>> contains, read Vivek's blog at:
>> http://weblogs.java.net/blog/vivekp/archive/2007/02/jaxws_21_fcs_fa_1.html
>>
>> Here is an excerpt from Vivek's blog about the Key Features.
>>
>>     * Reference Implementation (RI) of JAX-WS 2.1. Full JAX-WS 2.1
>>       Specification <http://jcp.org/en/jsr/detail?id=224> compliance
>>     * Development Tools
>>           o WSDL to Java generator
>>                 + Wsimport command line tool
>>                   <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimport.html>,
>>                   ant task
>>                  
<https://jax-ws.dev.java.net/nonav/2.1/docs/wsimportant.html>
>>                   and Maven2 plugin
>>                   <http://mojo.codehaus.org/jaxws-maven-plugin/index.html>
>>           o Java to WSDL generator
>>                 + Wsgen command line tool
>>                   <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgen.html>,
>>                   ant Task
>>                   <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgenant.html>
>>                   and Maven2 plugin
>>                   <http://mojo.codehaus.org/jaxws-maven-plugin/index.html>
>>           o Integrated with NetBeans  5.5.1
>>             <http://www.netbeans.info/downloads/dev.php>
>>     * Standards
>>           o Web Services Addressing 1.0 - Core, SOAP Binding and WSDL
>>             Binding
>>           o WS-Addressing  - Member Submission
>>           o SOAP 1.1 and 1.2
>>           o REST and XML/HTTP
>>           o WS-I Basic Profile 1.1, Simple SOAP Binding Profile 1.0 and
>>             Attachment Profile 1.0
>>           o MTOM
>>     * Extensions (May not be final unless says so)
>>           o Web Services Interoperable Technologies ( WSIT
>>             <https://wsit.dev.java.net/index.html#downloads>) - enables
>>             .NET 3.0 interoperability
>>                 + WS-ReliableMessaging
>>                 + WS-Policy
>>                 + WS-MEX
>>                 + WS-Security/WS-Security Policy
>>                 + WS-Trust/WS-Secure Conversation
>>                 + WS-AT/WS-Tx (Supported only on Glassfish v2)
>>                 + SOAP/TCP
>>           o Spring support <https://jax-ws-commons.dev.java.net/spring/>
>>           o Pluggable Transport
>>             <https://jax-ws.dev.java.net/transport.html>
>>                 + In-VM transport
>>                 + Servlet transport (bundled with the RI)
>>                 + JMS transport <http://jms-ws-transport.dev.java.net/>
>>                 + SOAP over TCP transport (part of WSIT
>>                   <https://wsit.dev.java.net>)
>>           o FastInfoset (bundled with JAX-WS 2.1 RI)
>>             <https://fi.dev.java.net/>
>>                 + ITU-T Rec. X.891 | ISO/IEC 24824-1
>>                   <http://www.itu.int/rec/T-REC-X.891-200505-I/e>
>>           o JBI Service Engine and Binding Component(part of Glassfish v2)
>>           o HTTP Binding Component
>>             <http://www.glassfishwiki.org/jbiwiki/Wiki.jsp?page=HTTPBC>,
>>             used by Open JBI component
>>             <https://open-jbi-components.dev.java.net/>
>>     * Data binding - JAXB 2.1.2 RI <https://jaxb.dev.java.net/2.1.2/>
>>     * Server Side Asynchrony - AsyncProvider
>>       <https://jax-ws.dev.java.net/nonav/2.1/docs/asyncprovider.html>
>>     * Stateful Web Services
>>       <https://jax-ws.dev.java.net/nonav/2.1/docs/statefulWebservice.html>
>>     * Support for custom WebServiceFeature
>>      
<http://weblogs.java.net/blog/ramapulavarthi/archive/2007/01/extending_jaxws.htm\
l>
>>     * Hosting API
>>      
<https://jax-ws-architecture-document.dev.java.net/nonav/doc21/index.html?com/su\
n/xml/ws/api/server/package-summary.html>
>>
>>           o These APIs can be used by a J2EE application server to
>>             integrate JAX-WS 2.1 RI for hosting JAX-WS services
>>     * Endpoint Deployment
>>           o Glassfish v2 <https://glassfish.dev.java.net>
>>                 + Tightly integrated with Glassfish
>>                 + Supports EJB and Web endpoints
>>                 + 109 based deployment support for better portability
>>                 + JAX-WS RI specific deployment descriptor support
>>           o Sun One Application Server 9.0 ur1
>>             <http://www.sun.com/software/products/appsrvr_pe/index.xml>
>>           o Light weight HTTP server
>>                 + On JDK 1.5 through http.jar distributed with the
>>                   JAX-WS 2.1 RI bundle
>>                 + Bundled with JDK 6
>>           o Any other container that supports Servlet 2.4, such as
>>             Tomcat, Jetty, Geronimo, JBoss, Resin, ... You name it!
>>
>>
>>
>>
>> -----------------------------------------------------------------
>> This group is a forum for builders of SOAP implementations to discuss
implementation and interoperability issues.  Please stay on-topic.
>> Yahoo! Groups Links
>>
>>
>>
>>
>>
>>
>
>
> -----------------------------------------------------------------
> This group is a forum for builders of SOAP implementations to discuss
implementation and interoperability issues.  Please stay on-topic.
> Yahoo! Groups Links
>
>
>
>

"Benchmarking" against Axis2-XMLBeans (as shown in the linked blog) is
ridiculous. XMLBeans is much slower than either ADB or JiBX data binding
for Axis2. If you're going to make performance claims for your software,
at least try to make the tests half way reasonable.

   - Dennis

Dennis M. Sosnoski
SOA and Web Services in Java
Training and Consulting
http://www.sosnoski.com - http://www.sosnoski.co.nz
Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117



Doug Kohlert wrote:
> We are proud to announce the release of JAX-WS 2.1 RI FCS. JAX-WS 2.1 is
> a major re-architecture over JAX-WS 2.0 without changing the standard
> JAX-WS APIs or programming model.  The benefits of this is a very fast
> implementation and an extremely flexible, extensible architecture.  To
> read more about how fast the RI is and the new functionality that it
> contains, read Vivek's blog at:
> http://weblogs.java.net/blog/vivekp/archive/2007/02/jaxws_21_fcs_fa_1.html
>
> Here is an excerpt from Vivek's blog about the Key Features.
>
>     * Reference Implementation (RI) of JAX-WS 2.1. Full JAX-WS 2.1
>       Specification <http://jcp.org/en/jsr/detail?id=224> compliance
>     * Development Tools
>           o WSDL to Java generator
>                 + Wsimport command line tool
>                   <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimport.html>,
>                   ant task
>                  
<https://jax-ws.dev.java.net/nonav/2.1/docs/wsimportant.html>
>                   and Maven2 plugin
>                   <http://mojo.codehaus.org/jaxws-maven-plugin/index.html>
>           o Java to WSDL generator
>                 + Wsgen command line tool
>                   <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgen.html>,
>                   ant Task
>                   <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgenant.html>
>                   and Maven2 plugin
>                   <http://mojo.codehaus.org/jaxws-maven-plugin/index.html>
>           o Integrated with NetBeans  5.5.1
>             <http://www.netbeans.info/downloads/dev.php>
>     * Standards
>           o Web Services Addressing 1.0 - Core, SOAP Binding and WSDL
>             Binding
>           o WS-Addressing  - Member Submission
>           o SOAP 1.1 and 1.2
>           o REST and XML/HTTP
>           o WS-I Basic Profile 1.1, Simple SOAP Binding Profile 1.0 and
>             Attachment Profile 1.0
>           o MTOM
>     * Extensions (May not be final unless says so)
>           o Web Services Interoperable Technologies ( WSIT
>             <https://wsit.dev.java.net/index.html#downloads>) - enables
>             .NET 3.0 interoperability
>                 + WS-ReliableMessaging
>                 + WS-Policy
>                 + WS-MEX
>                 + WS-Security/WS-Security Policy
>                 + WS-Trust/WS-Secure Conversation
>                 + WS-AT/WS-Tx (Supported only on Glassfish v2)
>                 + SOAP/TCP
>           o Spring support <https://jax-ws-commons.dev.java.net/spring/>
>           o Pluggable Transport
>             <https://jax-ws.dev.java.net/transport.html>
>                 + In-VM transport
>                 + Servlet transport (bundled with the RI)
>                 + JMS transport <http://jms-ws-transport.dev.java.net/>
>                 + SOAP over TCP transport (part of WSIT
>                   <https://wsit.dev.java.net>)
>           o FastInfoset (bundled with JAX-WS 2.1 RI)
>             <https://fi.dev.java.net/>
>                 + ITU-T Rec. X.891 | ISO/IEC 24824-1
>                   <http://www.itu.int/rec/T-REC-X.891-200505-I/e>
>           o JBI Service Engine and Binding Component(part of Glassfish v2)
>           o HTTP Binding Component
>             <http://www.glassfishwiki.org/jbiwiki/Wiki.jsp?page=HTTPBC>,
>             used by Open JBI component
>             <https://open-jbi-components.dev.java.net/>
>     * Data binding - JAXB 2.1.2 RI <https://jaxb.dev.java.net/2.1.2/>
>     * Server Side Asynchrony - AsyncProvider
>       <https://jax-ws.dev.java.net/nonav/2.1/docs/asyncprovider.html>
>     * Stateful Web Services
>       <https://jax-ws.dev.java.net/nonav/2.1/docs/statefulWebservice.html>
>     * Support for custom WebServiceFeature
>      
<http://weblogs.java.net/blog/ramapulavarthi/archive/2007/01/extending_jaxws.htm\
l>
>     * Hosting API
>      
<https://jax-ws-architecture-document.dev.java.net/nonav/doc21/index.html?com/su\
n/xml/ws/api/server/package-summary.html>
>
>           o These APIs can be used by a J2EE application server to
>             integrate JAX-WS 2.1 RI for hosting JAX-WS services
>     * Endpoint Deployment
>           o Glassfish v2 <https://glassfish.dev.java.net>
>                 + Tightly integrated with Glassfish
>                 + Supports EJB and Web endpoints
>                 + 109 based deployment support for better portability
>                 + JAX-WS RI specific deployment descriptor support
>           o Sun One Application Server 9.0 ur1
>             <http://www.sun.com/software/products/appsrvr_pe/index.xml>
>           o Light weight HTTP server
>                 + On JDK 1.5 through http.jar distributed with the
>                   JAX-WS 2.1 RI bundle
>                 + Bundled with JDK 6
>           o Any other container that supports Servlet 2.4, such as
>             Tomcat, Jetty, Geronimo, JBoss, Resin, ... You name it!
>
>
>
>
> -----------------------------------------------------------------
> This group is a forum for builders of SOAP implementations to discuss
implementation and interoperability issues.  Please stay on-topic.
> Yahoo! Groups Links
>
>
>
>
>

On 2/8/07, noah_mendelsohn@... <noah_mendelsohn@...> wrote:
> Steve Loughran writes:
>
> > On 2/7/07, noah_mendelsohn@...
> > <noah_mendelsohn@...> wrote: ."
>
>
> > > Furthermore, and this is the part I really wish
> > > had been highlighted a bit more, nothing says
> > > these must be separate headers. So, IMO, if you
> > > want to say >in the specification for wsa:To<
> > > "if there are multiple wsa:To headers, here's
> > > the rule for how to process them all in the
> > > presence of the others", you can do so. If they
> > > are marked mU then you can be sure that, at
> > > least per the SOAP spec, their specifications
> > > can conspire to determine an order.
> > >
> >
> > well, its a shame they dont.
>
> Yes, well, I have many concerns about how the higher level WS* specs were
> written, and whether they took sufficient care to use SOAP's details
> properly. I'm sorry that's in fact causing you trouble.
>

Sometimes I suspect complexity is the underlying problem. Like WSDL.
Its almost impossible for humans to write, so what you get is a mess,
compared to, say, COM IDL interfaces.

As for the higher order specs, well, I relish their inconsistency,
epecially WSRF, that has explicit dependencies on two different draft
WSA versions, and punts on the whole problem of whether not bulk
attribute read/write operations are atomic or not.

But that's an OASIS problem so I won't be giving my local TAG
representative a hard time, about it, or you. Liked your W3C
submission to the web of enterprisey services; interesting contrast to
the IBM 'we want a single stack' story.

-steve

Steve Loughran writes:

> On 2/7/07, noah_mendelsohn@...
> <noah_mendelsohn@...> wrote: ."
>
> > Furthermore, and this is crucial, while SOAP
> > itself mandates no fixed order when processing,
> > headers can be defined to control the order [1]:
>
> > "The processing of one or more SOAP header
> > blocks MAY control or determine the order of
> > processing for other SOAP header blocks and/or
> > the SOAP body.  For example, one could create a
> > SOAP header block to force processing of other
> > SOAP header blocks in lexical order. In the
> > absence of such a controlling SOAP header block,
> > the order of header and body processing is at
> > the discretion of the SOAP node. Header blocks
> > MAY be processed in arbitrary order. Header
> > block processing MAY precede, MAY be interleaved
> > with, or MAY follow processing of the SOAP
> > body. For example, processing of a "begin
> > transaction" header block would typically
> > precede body processing, a "logging" function
> > might run concurrently with body processing and
> > a "commit transaction" header block might be
> > honored following completion of all other work."
>
> > This is not an accident. It's why we require
> > that all mustUnderstand checking be done before
> > any other work. That's what ensures you that if
> > you have an mU header that says "do the headers
> > in reverse order" or "alphabetical order" or
> > more likely "do signatures first" then that
> > header or those headers will necessarily be
> > checked in time to determine an order.
> >
>
> aah. Soap1.2. Soap 1.1 says nothing about where
> the headers are validated, only that they must be
> validated

Well, my reading of the ws-i basic profile is that it says the same thing
regarding SOAP 1.1 [1]:

"R1025   A RECEIVER MUST handle messages in such a way that it appears
that all checking of mandatory header blocks is performed before any
actual processing. "

Like so much in the basic profile, it takes the SOAP 1.2 refinements to
the processing model, and mandates their use with SOAP 1.1.

> > "A env:mustUnderstand value of "true" means that
> > the SOAP node must process the header with the
> > semantics described in that header's
> > specification, or else generate a SOAP
> > fault. Processing the header appropriately may
> > include removing the header from any generated
> > SOAP message, reinserting the header with the same
> > or altered value, or inserting a new header. The
> > inability to process a mandatory header requires
> > that all further processing of the SOAP message
> > cease, and a SOAP fault be generated. The message
> > is not forwarded any further."
>
> This is why the release of Axis (1.0?) that didnt
> do mU checking until after the message had been
> handled was within the spirit of the spec, and not
> the law.
>
> SOAP1.2 implies that I must check all mu headers
> before having any side effect at all. hmm. My
> current stack lets you declare handlers in a
> chain, as axis has done forever, and sun's stack
> has done since last week:

Well, I'm not sure what to say.  The spec is clear that you must inspect
the headers first, and I think there are defensible reasons for that.  I
believe most of the commercial implementations (not speaking for my
employer, IBM here) are moving toward a model in which headers are
buffered so that mU checking can be done and header processing
appropriately ordered, but the body is not necessarily parsed and
processed in advance.  Thus, the body can be streamed, but not the
headers.

> AddressedEchoEndpoint extends AlpineEndpoint {
> name "wsa-echo";
> handlers [
> LogCurrentMessageHandler:classname,
> AddressHandler:classname,
> MustUnderstandChecker:classname,
> EchoHandler:classname,
> LogCurrentMessageHandler:classname
> ];
> }
>
> There's no way with this chain-of-resposibility
> design to do advance checking of handling, or
> guarantee that there are no side effects (I log
> the message -is that a side effect?), before the
> message is handed for processing.
>
> I suppose I could modify the handler interface to
> add an extra method in which every handler
> indicates if it will process a specific mU
> header. But if every handler is empowered to
> transform the incoming message during its work
> phase, things get complex. You need to create a
> provisionally transformed doc (transform, without
> side effects) just to make sure the mu headers get
> processed right.

To be precise, headers are empowered to change the interpretation of other
parts of the message, or to affect whether you can "understand" other
headers in the message, but NOT to transform the message.  In particular,
I don't see anything that says a header can cause parts of the message to
be decrypted or decompressed in a manner that would lead to the appearance
of new headers that were processed as if they were there from the start.

What I do think is there implicitly for such cases is for the
specification of a header to say:  when I am present, the SOAP processing
model is to be rerun from the start on a new infoset constructed in the
following way (e.g. by decrypting parts of the current.)  In a given
single use of the SOAP processing model, the input envelope infoset is
invariant, but the interpretations of the headers present may interact.
Indeed, it's crucial that they do.  Surely a digital signature header
affects the semantics of that which is signed, in the sense that if the
dsig doesn't check, you may want to act as if none of the other headers
are there (since they may be the result of tampering.)  SOAP is designed
to enable such scenarios, as long as the specification for the header (in
this case a dsig header) is written properly.

> Or I ignore that part of the spec on the grounds
> that its pretty much impossible for interop tests
> to catch and retain my existing SOAP1.1-compatible
> mU processing algorithm.

Whether you wish your implementation to expose that full power is up to
you.  HOWEVER, if you do not, then the only conforming response is for you
to act as if you do not in fact "understand" any headers that might
conceivably have such interacting semantics that you can't handle.  So,
unless you know that a header doesn't affect others, then if it's mU
you'll either have to mU fault or be nonconforming to ws-i basic profile
and/or SOAP 1.2.


> > Furthermore, and this is the part I really wish
> > had been highlighted a bit more, nothing says
> > these must be separate headers. So, IMO, if you
> > want to say >in the specification for wsa:To<
> > "if there are multiple wsa:To headers, here's
> > the rule for how to process them all in the
> > presence of the others", you can do so. If they
> > are marked mU then you can be sure that, at
> > least per the SOAP spec, their specifications
> > can conspire to determine an order.
> >
>
> well, its a shame they dont.

Yes, well, I have many concerns about how the higher level WS* specs were
written, and whether they took sufficient care to use SOAP's details
properly. I'm sorry that's in fact causing you trouble.

> -steve
>

Noah

[1]
http://www.ws-i.org/Profiles/BasicProfile-1.0-2004-04-16.html#refinement16468312



--------------------------------------
Noah Mendelsohn
IBM Corporation
One Rogers Street
Cambridge, MA 02142
1-617-693-4036
--------------------------------------

We are proud to announce the release of JAX-WS 2.1 RI FCS. JAX-WS 2.1 is
a major re-architecture over JAX-WS 2.0 without changing the standard
JAX-WS APIs or programming model.  The benefits of this is a very fast
implementation and an extremely flexible, extensible architecture.  To
read more about how fast the RI is and the new functionality that it
contains, read Vivek's blog at:
http://weblogs.java.net/blog/vivekp/archive/2007/02/jaxws_21_fcs_fa_1.html

Here is an excerpt from Vivek's blog about the Key Features.

     * Reference Implementation (RI) of JAX-WS 2.1. Full JAX-WS 2.1
       Specification <http://jcp.org/en/jsr/detail?id=224> compliance
     * Development Tools
           o WSDL to Java generator
                 + Wsimport command line tool
                   <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimport.html>,
                   ant task
                   <https://jax-ws.dev.java.net/nonav/2.1/docs/wsimportant.html>
                   and Maven2 plugin
                   <http://mojo.codehaus.org/jaxws-maven-plugin/index.html>
           o Java to WSDL generator
                 + Wsgen command line tool
                   <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgen.html>,
                   ant Task
                   <https://jax-ws.dev.java.net/nonav/2.1/docs/wsgenant.html>
                   and Maven2 plugin
                   <http://mojo.codehaus.org/jaxws-maven-plugin/index.html>
           o Integrated with NetBeans  5.5.1
             <http://www.netbeans.info/downloads/dev.php>
     * Standards
           o Web Services Addressing 1.0 - Core, SOAP Binding and WSDL
             Binding
           o WS-Addressing  - Member Submission
           o SOAP 1.1 and 1.2
           o REST and XML/HTTP
           o WS-I Basic Profile 1.1, Simple SOAP Binding Profile 1.0 and
             Attachment Profile 1.0
           o MTOM
     * Extensions (May not be final unless says so)
           o Web Services Interoperable Technologies ( WSIT
             <https://wsit.dev.java.net/index.html#downloads>) - enables
             .NET 3.0 interoperability
                 + WS-ReliableMessaging
                 + WS-Policy
                 + WS-MEX
                 + WS-Security/WS-Security Policy
                 + WS-Trust/WS-Secure Conversation
                 + WS-AT/WS-Tx (Supported only on Glassfish v2)
                 + SOAP/TCP
           o Spring support <https://jax-ws-commons.dev.java.net/spring/>
           o Pluggable Transport
             <https://jax-ws.dev.java.net/transport.html>
                 + In-VM transport
                 + Servlet transport (bundled with the RI)
                 + JMS transport <http://jms-ws-transport.dev.java.net/>
                 + SOAP over TCP transport (part of WSIT
                   <https://wsit.dev.java.net>)
           o FastInfoset (bundled with JAX-WS 2.1 RI)
             <https://fi.dev.java.net/>
                 + ITU-T Rec. X.891 | ISO/IEC 24824-1
                   <http://www.itu.int/rec/T-REC-X.891-200505-I/e>
           o JBI Service Engine and Binding Component(part of Glassfish v2)
           o HTTP Binding Component
             <http://www.glassfishwiki.org/jbiwiki/Wiki.jsp?page=HTTPBC>,
             used by Open JBI component
             <https://open-jbi-components.dev.java.net/>
     * Data binding - JAXB 2.1.2 RI <https://jaxb.dev.java.net/2.1.2/>
     * Server Side Asynchrony - AsyncProvider
       <https://jax-ws.dev.java.net/nonav/2.1/docs/asyncprovider.html>
     * Stateful Web Services
       <https://jax-ws.dev.java.net/nonav/2.1/docs/statefulWebservice.html>
     * Support for custom WebServiceFeature
      
<http://weblogs.java.net/blog/ramapulavarthi/archive/2007/01/extending_jaxws.htm\
l>
     * Hosting API
      
<https://jax-ws-architecture-document.dev.java.net/nonav/doc21/index.html?com/su\
n/xml/ws/api/server/package-summary.html>

           o These APIs can be used by a J2EE application server to
             integrate JAX-WS 2.1 RI for hosting JAX-WS services
     * Endpoint Deployment
           o Glassfish v2 <https://glassfish.dev.java.net>
                 + Tightly integrated with Glassfish
                 + Supports EJB and Web endpoints
                 + 109 based deployment support for better portability
                 + JAX-WS RI specific deployment descriptor support
           o Sun One Application Server 9.0 ur1
             <http://www.sun.com/software/products/appsrvr_pe/index.xml>
           o Light weight HTTP server
                 + On JDK 1.5 through http.jar distributed with the
                   JAX-WS 2.1 RI bundle
                 + Bundled with JDK 6
           o Any other container that supports Servlet 2.4, such as
             Tomcat, Jetty, Geronimo, JBoss, Resin, ... You name it!

On 2/7/07, noah_mendelsohn@... <noah_mendelsohn@...> wrote:
."
>
>  Furthermore, and this is crucial,  while SOAP itself mandates no fixed
> order when processing, headers can be defined to control the order [1]:
>
> "The processing of one or more SOAP header blocks MAY control or determine
> the order of processing for other SOAP header blocks and/or the SOAP body.
> For example, one could create a SOAP header block to force processing of
> other SOAP header blocks in lexical order. In the absence of such a
> controlling SOAP header block, the order of header and body processing is
> at the discretion of the SOAP node. Header blocks MAY be processed in
> arbitrary order. Header block processing MAY precede, MAY be interleaved
> with, or MAY follow processing of the SOAP body. For example, processing
> of a "begin transaction" header block would typically precede body
> processing, a "logging" function might run concurrently with body
> processing and a "commit transaction" header block might be honored
> following completion of all other work."
>
> This is not an accident.  It's why we require that all mustUnderstand
> checking be done before any other work.  That's what ensures you that if
> you have an mU header that says "do the headers in reverse order" or
> "alphabetical order" or more likely "do signatures first"  then that
> header or those headers will necessarily be checked in time to determine
> an order.
>

aah. Soap1.2. Soap 1.1 says nothing about where the headers are
validated, only that they must be validated

"A env:mustUnderstand value of "true" means that the SOAP node must
process the header with the semantics described in that header's
specification, or else generate a SOAP fault. Processing the header
appropriately may include removing the header from any generated SOAP
message, reinserting the header with the same or altered value, or
inserting a new header. The inability to process a mandatory header
requires that all further processing of the SOAP message cease, and a
SOAP fault be generated. The message is not forwarded any further."

This is why the release of Axis (1.0?) that didnt do mU checking until
after the message had been handled was within the spirit of the spec,
and not the law.

SOAP1.2 implies that I must check all mu headers before having any
side effect at all. hmm. My current stack lets you declare handlers in
a chain, as axis has done forever, and sun's stack has done since last
week:

AddressedEchoEndpoint extends AlpineEndpoint {
     name "wsa-echo";
     handlers [
       LogCurrentMessageHandler:classname,
       AddressHandler:classname,
       MustUnderstandChecker:classname,
       EchoHandler:classname,
       LogCurrentMessageHandler:classname
     ];
}

There's no way with this chain-of-resposibility design to do advance
checking of handling, or guarantee that there are no side effects (I
log the message -is that a side effect?), before the message is handed
for processing.

I suppose I could modify the handler interface to add an extra method
in which every handler indicates if it will process a specific mU
header. But if every handler is empowered to transform the incoming
message during its work phase, things get complex. You need to create
a provisionally transformed doc (transform, without side effects) just
to make sure the mu headers get processed right.

Or I ignore that part of the spec on the grounds that its pretty much
impossible for interop tests to catch and retain my existing
SOAP1.1-compatible mU processing algorithm.

> Furthermore, and this is the part I really wish had been highlighted a bit
> more, nothing says these must be separate headers.  So, IMO, if you want
> to say >in the specification for wsa:To<  "if there are multiple wsa:To
> headers, here's the rule for how to process them all in the presence of
> the others", you can do so.  If they are marked mU then you can be sure
> that, at least per the SOAP spec, their specifications can conspire to
> determine an order.
>

well, its a shame they dont.

-steve