On Dec 12, 2007, at 7:55 AM, Daniel Kulp wrote:
On Wednesday 12 December 2007, Vespa, Anthony J wrote:
I would be interested in this as well for Aegis bindings - it does
not
make some of the JS libraries out there too happy.
That is why doing it at the interceptor level is ideal. It
and only strip for certain agents.
Dan
On Wednesday 12 December 2007, Dain Sundstrom wrote:
On Dec 12, 2007, at 7:55 AM, Daniel Kulp wrote:
On Wednesday 12 December 2007, Vespa, Anthony J wrote:
I would be interested in this as well for Aegis bindings - it does
not
make some of the JS
I think having XmlBeans support would be great, but I'm confused by
your footprint motivation. After a quick inspection, XmlBeans is
~2.7 times as big as Jaxb impl:
[01:50:46] dain$ ls -lh ~/.m2/repository/com/sun/xml/bind/jaxb-impl/
2.0.5/jaxb-impl-2.0.5.jar
-rw-r--r-- 1 dain dain
Specifically, I believe you can not have to methods mapped to the
same operation name in JaxWS, but you can change the operation name
of one of the methods using the @WebMethod annotation (see the
example in the linked example [1]).
Unfortunately, there doesn't seem to be any equivalent
Why don't we support the xfire annotations also? It would be pretty
easy for the code to check for both.
-dain
On Jan 2, 2008, at 5:59 PM, Benson Margulies wrote:
When I created an XFire test client using the precompiled class
JAR file, I
kept getting nulls in most of the object
this configuration. The commented out code in
JaxbXmlParamTypeTest demonstrates this problem.
Besides that, everything else seems to works.
-dain
On Jan 3, 2008, at 12:31 PM, Dain Sundstrom wrote:
Sure. I need to write a TypeCreator for SOAP encoded anyway.
-dain
On Jan 3, 2008, at 10:17 AM, Benson
