You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by da...@abis-reicom.de on 2008/09/22 14:30:06 UTC
Re-4: Advice on CXF OSGi Bundle
I think it would be very nice to see full support for CXF. Nevertheless
the single CXF bundle seems to be sufficient for our purpose. At
least it is better than including the whole CXF distribution + deps
in every single web service bundle. :-)
At the moment we use several complex types and MTOM. Please let me
know if one of these might cause problems at the time.
Regarding my problem with Aegis I found that creating bundles of
JDOM and Jaxen is enough to get rid of the exceptions. I also had
to import "org.jdom" in the Jaxen Bundle. Of course this is just
quick 'n' dirty and I didn't test everything.
If you need any help on creating bundles, please let me know
how I can help. We'll rely on CXF and OSGi in the future and I think
offering our help would be the least we could do.
-------- Original Message --------
Subject: Re: Re-2: Advice on CXF OSGi Bundle (22-Sep-2008 13:03)
From: Guillaume Nodet <gn...@gmail.com>
To: users@cxf.apache.org
> Not all dependencies have been released as OSGi bundles at this point.
> This is mainly because in ServiceMix, we don't provide support yet for
> all CXF features, but we'd be happy to do so.
> The main problem is that CXF can not be released as a set of bundles
> because of some OSGi limitations wrt to sharing packages, so the have
> to rely on a single CXF bundle at this point.
> However, we should provided those in the near future, so if you want,
> we could work on creating the needed bundles as patches for
> https://svn.apache.org/repos/asf/servicemix/smx4/bundles/trunk/
>
> On Mon, Sep 22, 2008 at 12:35 PM, <da...@abis-reicom.de> wrote:
> > That did the trick. :-)
> >
> >
> > Is there also a dependency on JDOM an Jaxen? I just
> > tried Aegis Databinding and I get some NoClassDefFound
> > regarding these libraries.
> >
> > It seems that there are no bundles for these libs in
> > the maven repository.
> >
> > Maybe I have to use the cxf-minimal-bundle?
> >
> >
> > -------- Original Message --------
> > Subject: Re: Advice on CXF OSGi Bundle (19-Sep-2008 16:32)
> > From: Daniel Kulp <dk...@apache.org>
> > To: users@cxf.apache.org
> >
> >>
> >> The servicemix bundles are all at:
> >> http://repo1.maven.org/maven2/org/apache/servicemix/bundles/
> >> and:
> >> http://repo1.maven.org/maven2/org/apache/servicemix/specs/
> >>
> >> Abdera is in the incubator repository:
> >> http://people.apache.org/repo/m2-incubating-repository/
> >>
> >>
> >> Hope that helps!
> >> Dan
> >>
> >>
> >> On Friday 19 September 2008 10:11:59 am dankof@abis-reicom.de wrote:
> >> > Hello,
> >> >
> >> > I managed to use the CXF bundle from the Maven2 repository (cxf-bundle
> >> > 2.1.2) in an Equinox container with Spring-DM (Spring MVC).
> >> >
> >> > Nevertheless, I had to create my own OSGi bundles for some CXF
> >> > dependencies: * jaxb-api
> >> > * jaxb-impl
> >> > * saaj-api
> >> > * wsdl4j
> >> > * xml-resolver
> >> >
> >> > Additionally, Maven needed some Apache Abdera libraries that I had to
> >> > install manually in my local repository.
> >> >
> >> > Is there anyone who knows of a more convenient way to resolve these
> >> > dependencies? I got the information that the ServiceMix project has
> these
> >> > deps in their repository. Maybe I can get them from there but I don't
> know
> >> > the correct repository entry for Maven.
> >> >
> >> > Any suggestions?
> >> >
> >> > Best regards,
> >> >
> >> > Fabian
> >>
> >>
> >>
> >> --
> >> Daniel Kulp
> >> dkulp@apache.org
> >> http://www.dankulp.com/blog
> >
> >
> > To: dkulp@apache.org
> > users@cxf.apache.org
> >
> >
> >
>
>
>
> --
> Cheers,
> Guillaume Nodet
> ------------------------
> Blog: http://gnodet.blogspot.com/
> ------------------------
> Open Source SOA
> http://open.iona.com
Re: Re-4: Advice on CXF OSGi Bundle
Posted by Daniel Kulp <dk...@apache.org>.
Sent too soon.... Was finding their jira....
I THINK the jiras/patches should be filed on the smx4 jira since that is the
OSGi runtime:
https://issues.apache.org/activemq/browse/SMX4
Dan
On Monday 22 September 2008 2:33:57 pm Daniel Kulp wrote:
> On Monday 22 September 2008 8:30:06 am dankof@abis-reicom.de wrote:
> > If you need any help on creating bundles, please let me know
> > how I can help. We'll rely on CXF and OSGi in the future and I think
> > offering our help would be the least we could do.
>
> Definitely file requests with the servicemix group and attach patches to
> get the bundles created.
> Their trunk:
> https://svn.apache.org/repos/asf/servicemix/smx4/bundles/trunk/
> Their JIRA:
>
>
> One of the IONA folks did a quick audit last week to get a list of stuff
> that needs to be done. Any patches toward reducing this list would be
> greatly appreciated. This is what it looks like as of last week broken up
> by feature/functionality:
>
> Ws-Security:
> +- bouncycastle:bcprov-jdk14:jar:136:runtime
> +- opensaml:opensaml:jar:1.1:compile
> +- xalan:xalan:jar:2.7.0:compile
> +- org.apache.ws.security:wss4j:jar:1.5.4:compile
>
> Any Json stuff:
> +- org.codehaus.jettison:jettison:jar:1.0.1:compile
>
> Jaxrs:
> +- commons-codec:commons-codec:jar:1.3:compile
> +- org.apache.abdera:abdera-extensions-json:jar:0.4.0-incubating:compile
> +- org.apache.abdera:abdera-i18n:jar:0.4.0-incubating:compile
> +- org.apache.abdera:abdera-parser:jar:0.4.0-incubating:compile
> +- org.apache.ws.commons.axiom:axiom-api:jar:1.2.7:compile
>
> | \- xml-apis:xml-apis:jar:1.3.02:compile (version managed from 1.3.04)
>
> +- org.apache.ws.commons.axiom:axiom-impl:jar:1.2.7:compile
> +- javax.ws.rs:jsr311-api:jar:0.8:compile
> +- org.apache.abdera:abdera-extensions-main:jar:0.4.0-incubating:compile
> +- jaxen:jaxen:jar:1.1:compile
> +- commons-lang:commons-lang:jar:2.4:compile
> \- org.apache.abdera:abdera-core:jar:0.4.0-incubating:compile
>
> Http binding: (older REST stuff)
> +- org.codehaus.jra:jra:jar:1.0-alpha-4:compile
>
> Javascript frontend: (not the ?js stuff)
> +- rhino:js:jar:1.6R7:compile
>
> Aegis databinding:
> +- jdom:jdom:jar:1.0:compile
>
> XMLBeans databinding:
> +- org.apache.xmlbeans:xmlbeans:jar:2.3.0:compile
>
> Jetty transport (instead of the OSGi HTTP transport that smx4 provides):
> +- org.slf4j:slf4j-api:jar:1.3.1:runtime
> +- org.mortbay.jetty:jetty:jar:6.1.9:compile
> +- org.slf4j:slf4j-jdk14:jar:1.3.1:runtime
>
> Dynamic client as well as tooling:
> +- com.sun.xml.bind:jaxb-xjc:jar:2.1.6:compile (version managed from 2.1.7)
>
> Tooling:
> +- velocity:velocity-dep:jar:1.4:runtime
> +- velocity:velocity:jar:1.4:compile
> +- antlr:antlr:jar:2.7.7:compile (corba tooling)
>
>
> Won't be needed anymore once we do a 2.1.3 but is needed for 2.1.2
> aegis/javascript:
> +- net.java.dev.stax-utils:stax-utils:jar:20060502:compile
--
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog
Re: Re-4: Advice on CXF OSGi Bundle
Posted by Daniel Kulp <dk...@apache.org>.
On Monday 22 September 2008 8:30:06 am dankof@abis-reicom.de wrote:
> If you need any help on creating bundles, please let me know
> how I can help. We'll rely on CXF and OSGi in the future and I think
> offering our help would be the least we could do.
Definitely file requests with the servicemix group and attach patches to get
the bundles created.
Their trunk:
https://svn.apache.org/repos/asf/servicemix/smx4/bundles/trunk/
Their JIRA:
One of the IONA folks did a quick audit last week to get a list of stuff that
needs to be done. Any patches toward reducing this list would be greatly
appreciated. This is what it looks like as of last week broken up by
feature/functionality:
Ws-Security:
+- bouncycastle:bcprov-jdk14:jar:136:runtime
+- opensaml:opensaml:jar:1.1:compile
+- xalan:xalan:jar:2.7.0:compile
+- org.apache.ws.security:wss4j:jar:1.5.4:compile
Any Json stuff:
+- org.codehaus.jettison:jettison:jar:1.0.1:compile
Jaxrs:
+- commons-codec:commons-codec:jar:1.3:compile
+- org.apache.abdera:abdera-extensions-json:jar:0.4.0-incubating:compile
+- org.apache.abdera:abdera-i18n:jar:0.4.0-incubating:compile
+- org.apache.abdera:abdera-parser:jar:0.4.0-incubating:compile
+- org.apache.ws.commons.axiom:axiom-api:jar:1.2.7:compile
| \- xml-apis:xml-apis:jar:1.3.02:compile (version managed from 1.3.04)
+- org.apache.ws.commons.axiom:axiom-impl:jar:1.2.7:compile
+- javax.ws.rs:jsr311-api:jar:0.8:compile
+- org.apache.abdera:abdera-extensions-main:jar:0.4.0-incubating:compile
+- jaxen:jaxen:jar:1.1:compile
+- commons-lang:commons-lang:jar:2.4:compile
\- org.apache.abdera:abdera-core:jar:0.4.0-incubating:compile
Http binding: (older REST stuff)
+- org.codehaus.jra:jra:jar:1.0-alpha-4:compile
Javascript frontend: (not the ?js stuff)
+- rhino:js:jar:1.6R7:compile
Aegis databinding:
+- jdom:jdom:jar:1.0:compile
XMLBeans databinding:
+- org.apache.xmlbeans:xmlbeans:jar:2.3.0:compile
Jetty transport (instead of the OSGi HTTP transport that smx4 provides):
+- org.slf4j:slf4j-api:jar:1.3.1:runtime
+- org.mortbay.jetty:jetty:jar:6.1.9:compile
+- org.slf4j:slf4j-jdk14:jar:1.3.1:runtime
Dynamic client as well as tooling:
+- com.sun.xml.bind:jaxb-xjc:jar:2.1.6:compile (version managed from 2.1.7)
Tooling:
+- velocity:velocity-dep:jar:1.4:runtime
+- velocity:velocity:jar:1.4:compile
+- antlr:antlr:jar:2.7.7:compile (corba tooling)
Won't be needed anymore once we do a 2.1.3 but is needed for 2.1.2
aegis/javascript:
+- net.java.dev.stax-utils:stax-utils:jar:20060502:compile
--
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog