You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by Vassilis Virvilis <v....@biovista.com> on 2012/09/10 10:16:44 UTC
cxf spring-web dependancy ivy problem
Hi everybody,
We have the following problem and I am not sure where the bug lies or if
there is a bug at all. If you think this is a problem with ivy please
say me so and I will to report there.
The problem:
------------
We are trying to switch to a semi automatic system for tracking our
dependencies so we selected ivy (instead of maven). Ivy understands
maven dependencies and can use maven repositories.
When we specify to download cxf-bundle and it dependencies it brings
everything and spring but not spring-web which is explicitly mentioned
in WHICH_JARS as a server side dependency. It brings
cxf-server-libraries/spring-aop-3.0.7.RELEASE.jar
cxf-server-libraries/spring-asm-3.0.7.RELEASE.jar
cxf-server-libraries/spring-beans-3.0.7.RELEASE.jar
cxf-server-libraries/spring-context-3.0.7.RELEASE.jar
cxf-server-libraries/spring-core-3.0.7.RELEASE.jar
cxf-server-libraries/spring-expression-3.0.7.RELEASE.jar
cxf-server-libraries/spring-jms-3.0.7.RELEASE.jar
cxf-server-libraries/spring-tx-3.0.7.RELEASE.jar
but not spring-web
I checked the pom.xml of cxf-bundle and specifically states
org.springframework* so I guess spring-web should be included.
The problem is always reproducible and here is setup needed to replicate
(build.xml, ivy.xml, ivysettings.xml)
Thanks in advance
--
__________________________________
Vassilis Virvilis Ph.D.
Head of IT
Biovista Inc.
US Offices
2421 Ivy Road
Charlottesville, VA 22903
USA
T: +1.434.971.1141
F: +1.434.971.1144
European Offices
34 Rodopoleos Street
Ellinikon, Athens 16777
GREECE
T: +30.210.9629848
F: +30.210.9647606
www.biovista.com
Biovista is a privately held biotechnology company that finds novel uses
for existing drugs, and profiles their side effects using their
mechanism of action. Biovista develops its own pipeline of drugs in CNS,
oncology, auto-immune and rare diseases. Biovista is collaborating with
biopharmaceutical companies on indication expansion and de-risking of
their portfolios and with the FDA on adverse event prediction.
Re: cxf spring-web dependancy ivy problem
Posted by Vassilis Virvilis <v....@biovista.com>.
On 09/12/2012 05:37 PM, Glen Mazza wrote:
>>
>
> That's because (1) you don't need spring-web if you're using the
> CXFNonSpringServlet in the web.xml to drive your web service (as opposed
> to CXFServlet, the only one I've used so far), so it wouldn't need to be
> in cxf-bundle under those circumstances, and (2) cxf-bundle used to have
> (pre-CXF 2.6) a heavy role in OSGi deployment of web services, which
> doesn't use a WAR. cxf-bundle is kind of deprecated today, there's
> smaller bundles to be using for OSGi and Maven deployment will put just
> the right JARs you need in the WEB-INF/lib.
>
Glen thanks again.
Is there a list of these smaller bundles? I mean what are their names?
Where I can find them?
--
__________________________________
Vassilis Virvilis Ph.D.
Head of IT
Biovista Inc.
US Offices
2421 Ivy Road
Charlottesville, VA 22903
USA
T: +1.434.971.1141
F: +1.434.971.1144
European Offices
34 Rodopoleos Street
Ellinikon, Athens 16777
GREECE
T: +30.210.9629848
F: +30.210.9647606
www.biovista.com
Biovista is a privately held biotechnology company that finds novel uses
for existing drugs, and profiles their side effects using their
mechanism of action. Biovista develops its own pipeline of drugs in CNS,
oncology, auto-immune and rare diseases. Biovista is collaborating with
biopharmaceutical companies on indication expansion and de-risking of
their portfolios and with the FDA on adverse event prediction.
Re: cxf spring-web dependancy ivy problem
Posted by Glen Mazza <gm...@talend.com>.
On 09/12/2012 09:42 AM, Vassilis Virvilis wrote:
> On 09/11/2012 06:07 PM, Glen Mazza wrote:
>> On 09/11/2012 05:02 AM, Vassilis Virvilis wrote:
>>> Hi Daniel,
>>>
>>> Thanks for the quick reply.
>>>
>>> One more question: Is there any artifact that I can specify that will
>>> bring spring-web?.
>>
>> Sure, the spring-web dependency here at line #183:
>> http://svn.apache.org/viewvc/cxf/trunk/distribution/src/main/release/samples/wsdl_first/pom.xml?revision=1373166&view=markup
>>
>
> Thanks Glen,
>
> That was not what I had in mind. This is the project file of a war
> type application explicitly depending in spring-web. I was wondering
> if there was any cxf-artifact (like cxf-bundle that brings all the
> rest of spring*). I understand that probably no CXF module directly
> links with spring-web so it is not a direct dependency. I just found
> it odd that all the other spring jars were included with cxf-bundle
> but not spring-web.
>
That's because (1) you don't need spring-web if you're using the
CXFNonSpringServlet in the web.xml to drive your web service (as opposed
to CXFServlet, the only one I've used so far), so it wouldn't need to be
in cxf-bundle under those circumstances, and (2) cxf-bundle used to have
(pre-CXF 2.6) a heavy role in OSGi deployment of web services, which
doesn't use a WAR. cxf-bundle is kind of deprecated today, there's
smaller bundles to be using for OSGi and Maven deployment will put just
the right JARs you need in the WEB-INF/lib.
>
>>
>> No, the purpose of WHICH_JARS are for those who don't use Maven but
>> instead manually work with JARs. Running mvn dependency:list on our
>> samples should will give a list of needed Maven artifacts for each
>> sample, info that can be extrapolated to one's own projects.
>>
>
> Ok got it. Thanks again.
>
> Best regards
>
> Vassilis
--
Glen Mazza
Talend Community Coders - coders.talend.com
blog: www.jroller.com/gmazza
Re: cxf spring-web dependancy ivy problem
Posted by Vassilis Virvilis <v....@biovista.com>.
On 09/11/2012 06:07 PM, Glen Mazza wrote:
> On 09/11/2012 05:02 AM, Vassilis Virvilis wrote:
>> Hi Daniel,
>>
>> Thanks for the quick reply.
>>
>> One more question: Is there any artifact that I can specify that will
>> bring spring-web?.
>
> Sure, the spring-web dependency here at line #183:
> http://svn.apache.org/viewvc/cxf/trunk/distribution/src/main/release/samples/wsdl_first/pom.xml?revision=1373166&view=markup
Thanks Glen,
That was not what I had in mind. This is the project file of a war type
application explicitly depending in spring-web. I was wondering if there
was any cxf-artifact (like cxf-bundle that brings all the rest of
spring*). I understand that probably no CXF module directly links with
spring-web so it is not a direct dependency. I just found it odd that
all the other spring jars were included with cxf-bundle but not spring-web.
>
> No, the purpose of WHICH_JARS are for those who don't use Maven but
> instead manually work with JARs. Running mvn dependency:list on our
> samples should will give a list of needed Maven artifacts for each
> sample, info that can be extrapolated to one's own projects.
>
Ok got it. Thanks again.
Best regards
Vassilis
Re: cxf spring-web dependancy ivy problem
Posted by Glen Mazza <gm...@talend.com>.
On 09/11/2012 05:02 AM, Vassilis Virvilis wrote:
> Hi Daniel,
>
> Thanks for the quick reply.
>
> One more question: Is there any artifact that I can specify that will
> bring spring-web?.
Sure, the spring-web dependency here at line #183:
http://svn.apache.org/viewvc/cxf/trunk/distribution/src/main/release/samples/wsdl_first/pom.xml?revision=1373166&view=markup
>
> You are correct though that my application is a war deployed in tomcat.
>
> I looked again at WHICH_JARS and looks like my application type also
> falls in the "XML Configuration support" which states that it requires
> - aopalliance.jar
> - spring-beans.jar
> - spring-context.jar
> - spring-core.jar
> - spring.web.jar <-----------
> - FastInfoset.jar
>
> JMS on the other hand requires only
> - geronimo-jms.jar (Or the Sun equivalent)
> - spring-jms.jar
> - spring-tx.ja
>
> or maybe this is on top of the other spring jars.
>
> So maybe WHICH_JARS is not entirely correct? I didn't see a WAR
> application type dependencies section in WHICH_JARS.
Yes, I'll update the WHICH_JARS shortly.
> Looks like the various sections of WHICH_JARS should become ... (I am
> not familiar with the terminology) ivy configurations / maven
> artifacts? Or this has already been done and I missed it during googling?
No, the purpose of WHICH_JARS are for those who don't use Maven but
instead manually work with JARs. Running mvn dependency:list on our
samples should will give a list of needed Maven artifacts for each
sample, info that can be extrapolated to one's own projects.
Thanks,
Glen
>
> Anyway thanks again
>
> On 09/11/2012 12:36 AM, Daniel Kulp wrote:
>>
>>
>> spring-web is not considered a dependency of cxf-bundle anymore, so
>> not a bug. It's only needed if you are using CXF within a war type
>> application.
>>
>> Really, the spring stuff that cxf-bundle pulls in is JUST due to the
>> JMS transport now. The spring deps that are listed are pulled in
>> via the JMS transport, not via any of the other CXF jars.
>>
>
> Vassilis
--
Glen Mazza
Talend Community Coders - coders.talend.com
blog:www.jroller.com/gmazza
Re: cxf spring-web dependancy ivy problem
Posted by Vassilis Virvilis <v....@biovista.com>.
Hi Daniel,
Thanks for the quick reply.
One more question: Is there any artifact that I can specify that will
bring spring-web?.
You are correct though that my application is a war deployed in tomcat.
I looked again at WHICH_JARS and looks like my application type also
falls in the "XML Configuration support" which states that it requires
- aopalliance.jar
- spring-beans.jar
- spring-context.jar
- spring-core.jar
- spring.web.jar <-----------
- FastInfoset.jar
JMS on the other hand requires only
- geronimo-jms.jar (Or the Sun equivalent)
- spring-jms.jar
- spring-tx.ja
or maybe this is on top of the other spring jars.
So maybe WHICH_JARS is not entirely correct? I didn't see a WAR
application type dependencies section in WHICH_JARS.
Looks like the various sections of WHICH_JARS should become ... (I am
not familiar with the terminology) ivy configurations / maven artifacts?
Or this has already been done and I missed it during googling?
Anyway thanks again
On 09/11/2012 12:36 AM, Daniel Kulp wrote:
>
>
> spring-web is not considered a dependency of cxf-bundle anymore, so not a bug. It's only needed if you are using CXF within a war type application.
>
> Really, the spring stuff that cxf-bundle pulls in is JUST due to the JMS transport now. The spring deps that are listed are pulled in via the JMS transport, not via any of the other CXF jars.
>
Vassilis
Re: cxf spring-web dependancy ivy problem
Posted by Daniel Kulp <dk...@apache.org>.
spring-web is not considered a dependency of cxf-bundle anymore, so not a bug. It's only needed if you are using CXF within a war type application.
Really, the spring stuff that cxf-bundle pulls in is JUST due to the JMS transport now. The spring deps that are listed are pulled in via the JMS transport, not via any of the other CXF jars.
Dan
On Sep 10, 2012, at 4:16 AM, Vassilis Virvilis <v....@biovista.com> wrote:
> Hi everybody,
>
> We have the following problem and I am not sure where the bug lies or if there is a bug at all. If you think this is a problem with ivy please say me so and I will to report there.
>
> The problem:
> ------------
>
> We are trying to switch to a semi automatic system for tracking our dependencies so we selected ivy (instead of maven). Ivy understands maven dependencies and can use maven repositories.
>
> When we specify to download cxf-bundle and it dependencies it brings everything and spring but not spring-web which is explicitly mentioned in WHICH_JARS as a server side dependency. It brings
> cxf-server-libraries/spring-aop-3.0.7.RELEASE.jar
> cxf-server-libraries/spring-asm-3.0.7.RELEASE.jar
> cxf-server-libraries/spring-beans-3.0.7.RELEASE.jar
> cxf-server-libraries/spring-context-3.0.7.RELEASE.jar
> cxf-server-libraries/spring-core-3.0.7.RELEASE.jar
> cxf-server-libraries/spring-expression-3.0.7.RELEASE.jar
> cxf-server-libraries/spring-jms-3.0.7.RELEASE.jar
> cxf-server-libraries/spring-tx-3.0.7.RELEASE.jar
>
>
> but not spring-web
>
> I checked the pom.xml of cxf-bundle and specifically states org.springframework* so I guess spring-web should be included.
>
>
> The problem is always reproducible and here is setup needed to replicate (build.xml, ivy.xml, ivysettings.xml)
>
>
> Thanks in advance
>
> --
>
> __________________________________
>
> Vassilis Virvilis Ph.D.
> Head of IT
> Biovista Inc.
>
> US Offices
> 2421 Ivy Road
> Charlottesville, VA 22903
> USA
> T: +1.434.971.1141
> F: +1.434.971.1144
>
> European Offices
> 34 Rodopoleos Street
> Ellinikon, Athens 16777
> GREECE
> T: +30.210.9629848
> F: +30.210.9647606
>
> www.biovista.com
>
> Biovista is a privately held biotechnology company that finds novel uses for existing drugs, and profiles their side effects using their mechanism of action. Biovista develops its own pipeline of drugs in CNS, oncology, auto-immune and rare diseases. Biovista is collaborating with biopharmaceutical companies on indication expansion and de-risking of their portfolios and with the FDA on adverse event prediction.
>
>
> <build.xml><ivysettings.xml><ivy.xml>
--
Daniel Kulp
dkulp@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com