I can second that comment.
On Oct 6, 2009, at 9:03 PM, dbruley wrote:
A.H wrote:
The Problem is that i should use the servicemix-jsr181 component in
my
implementation und not the servicemix-cxf component.
From my understanding, the servicemix-jsr181 component has been
deprecated
and they are recommending CXF. Is there a reason you need to use
the jsr181
component?
We were deploying service assemblies that packaged a http-su and
jsr181-su.
We just finished converting these to be a cxf-bc and cxf-se
combination.
The conversion went well and we did not have to change any of our
Java code
as the JSR181 annotations are supported in the cxf-se component. We
replaced the xfire-maven-plugin with the cxf-codegen-plugin in our
poms
without issue as well.
Not quite an answer to your question, but I thought I would share our
understanding of the status of the jsr181 servicemix component
before you
invest too many resources into using it.
--
View this message in context:
http://www.nabble.com/wsgen-and-generateServerStubs-tp25645181p25779783.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Johan Edstrom
[email protected]
They that can give up essential liberty to purchase a little temporary
safety, deserve neither liberty nor safety.
Benjamin Franklin, Historical Review of Pennsylvania, 1759
