You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Richard S. Hall" <he...@ungoverned.org> on 2008/10/08 15:27:47 UTC
[Fwd: Re: building a felix embedding web app with maven]
I guess servlet gets dragged into the framework dependencies from
compendium. Should we put excluding servlet in our own POMs? Would it
excluding it in the framework POM be sufficient?
-> richard
-------- Original Message --------
Subject: Re: building a felix embedding web app with maven
Date: Wed, 8 Oct 2008 17:08:49 +0800
From: Stuart McCulloch <mc...@gmail.com>
Reply-To: users@felix.apache.org
To: users@felix.apache.org
References:
<OF...@qbe.com>
2008/10/8 Maxim Suponya <ma...@qbe.com>
> Hi,
> I have a web app that is built using maven 2.0.8. The application's
> pom.xml contains following dependency:
>
> <dependency>
> <groupId>org.apache.felix</groupId>
> <artifactId>org.apache.felix.framework</artifactId>
> <version>1.2.1</version>
> </dependency>
>
> But felix, in turn, depends on a project defined in
> javax.servlet-1.0.0.pom which subsequently makes a jar file called
> javax.servlet-1.0.0.jar ending up in WEB-INF/lib together with
> org.apache.felix.framework-1.2.1.jar.
have you tried using:
<dependency>
<groupId>org.apache.felix</groupId>
<artifactId>org.apache.felix.framework</artifactId>
<version>1.2.1</version>
<exclusions>
<exclusion>
<groupId>org.apache.felix</groupId>
<artifactId>javax.servlet</artifactId>
</exclusion>
</exclusions>
</dependency>
to tell Maven to exclude the transitive servlet dependency?
> When the web application starts and the servlet that launches felix gets
> initialized, a ClassCastException is thrown saying that this servlet is
> not a Servlet.. this is due to presence of javax.servlet-1.0.0.jar with
> Servlet.class in WEB-INF/lib which comes in conflict with the one that's
> provided by Tomcat.
>
> Adding <scope>provided</scope> in my app's pom.xml doesn't make any
> difference.
>
> <dependency>
> <groupId>org.apache.felix</groupId>
> <artifactId>javax.servlet</artifactId>
> <version>1.0.0</version>
> <scope>provided</scope>
> </dependency>
>
> Is there any way around this?
>
> Thanks a lot,
>
> Maxim
>
> - ----------------
> IMPORTANT NOTICE : The information in this email is confidential and may
> also be privileged. If you are not the intended recipient, any use or
> dissemination of the information and any disclosure or copying of this email
> is unauthorised and strictly prohibited. If you have received this email in
> error, please promptly inform us by reply email or telephone. You should
> also delete this email and destroy any hard copies produced.
--
Cheers, Stuart
Re: [Fwd: Re: building a felix embedding web app with maven]
Posted by "Richard S. Hall" <he...@ungoverned.org>.
Stuart McCulloch wrote:
> 2008/10/8 Richard S. Hall <he...@ungoverned.org>
>
>
>> Richard S. Hall wrote:
>>
>>
>>> I guess servlet gets dragged into the framework dependencies from
>>> compendium. Should we put excluding servlet in our own POMs? Would it
>>> excluding it in the framework POM be sufficient?
>>>
>>>
>> Wow. This message is unreadable.
>>
>> "Should we exclude servlet in our own POMs? Would excluding it in the
>> framework POM be sufficient?"
>>
>>
>
> another approach is to mark the dependency as:
>
> <optional>true</optional>
>
> in the compendium pom - this tells Maven to use it when compiling the
> project, but not to include it when calculating transitive dependencies
>
> see: http://maven.apache.org/pom.html#Dependencies
>
> "optional:
>
> Marks optional a dependency when this project itself is a dependency.
> Confused? For example, imagine a project A that depends upon project
> B to compile a portion of code that may not be used at runtime, then we
> may have no need for project B for all project. So if project X adds
> project
> A as its own dependency, then Maven will not need to install project B at
> all.
>
> Symbolically, if => represents a required dependency, and --> represents
> optional, although A=>B may be the case when building A X=>A-->B would
> be the case when building X.
>
> In the shortest terms, optional lets other projects know that, when you
> use
> this project, you do not require this dependency in order to work
> correctly."
>
> HTH
>
Yes, this sounds like it would also do the trick. I think this would be
a good addition to the compendium POM.
-> richard
> -> richard
>
>>> -> richard
>>>
>>> -------- Original Message --------
>>> Subject: Re: building a felix embedding web app with maven
>>> Date: Wed, 8 Oct 2008 17:08:49 +0800
>>> From: Stuart McCulloch <mc...@gmail.com>
>>> Reply-To: users@felix.apache.org
>>> To: users@felix.apache.org
>>> References: <
>>> OFCCA70B5C.64DDF772-ONCA2574DC.00289F6B-CA2574DC.002A02B1@qbe.com>
>>>
>>>
>>>
>>> 2008/10/8 Maxim Suponya <ma...@qbe.com>
>>>
>>> Hi,
>>>
>>>> I have a web app that is built using maven 2.0.8. The application's
>>>> pom.xml contains following dependency:
>>>>
>>>> <dependency>
>>>> <groupId>org.apache.felix</groupId>
>>>> <artifactId>org.apache.felix.framework</artifactId>
>>>> <version>1.2.1</version>
>>>> </dependency>
>>>>
>>>> But felix, in turn, depends on a project defined in
>>>> javax.servlet-1.0.0.pom which subsequently makes a jar file called
>>>> javax.servlet-1.0.0.jar ending up in WEB-INF/lib together with
>>>> org.apache.felix.framework-1.2.1.jar.
>>>>
>>>>
>>> have you tried using:
>>>
>>> <dependency>
>>> <groupId>org.apache.felix</groupId>
>>> <artifactId>org.apache.felix.framework</artifactId>
>>> <version>1.2.1</version>
>>> <exclusions>
>>> <exclusion>
>>> <groupId>org.apache.felix</groupId>
>>> <artifactId>javax.servlet</artifactId>
>>> </exclusion>
>>> </exclusions>
>>> </dependency>
>>>
>>> to tell Maven to exclude the transitive servlet dependency?
>>>
>>>
>>> When the web application starts and the servlet that launches felix gets
>>>
>>>> initialized, a ClassCastException is thrown saying that this servlet is
>>>> not a Servlet.. this is due to presence of javax.servlet-1.0.0.jar with
>>>> Servlet.class in WEB-INF/lib which comes in conflict with the one that's
>>>> provided by Tomcat.
>>>>
>>>> Adding <scope>provided</scope> in my app's pom.xml doesn't make any
>>>> difference.
>>>>
>>>> <dependency>
>>>> <groupId>org.apache.felix</groupId>
>>>> <artifactId>javax.servlet</artifactId>
>>>> <version>1.0.0</version>
>>>> <scope>provided</scope>
>>>> </dependency>
>>>>
>>>> Is there any way around this?
>>>>
>>>> Thanks a lot,
>>>>
>>>> Maxim
>>>>
>>>> - ----------------
>>>> IMPORTANT NOTICE : The information in this email is confidential and may
>>>> also be privileged. If you are not the intended recipient, any use or
>>>> dissemination of the information and any disclosure or copying of this
>>>> email
>>>> is unauthorised and strictly prohibited. If you have received this email
>>>> in
>>>> error, please promptly inform us by reply email or telephone. You should
>>>> also delete this email and destroy any hard copies produced.
>>>>
>>>>
Re: [Fwd: Re: building a felix embedding web app with maven]
Posted by "Richard S. Hall" <he...@ungoverned.org>.
I modified the framework's dependency on compendium to exclude
compendium's servlet dependency. I think this makes more sense than
marking the servlet dependency as optional in compendium. My reasoning
is that compendium does have a dependency on servlet, but framework has
no such dependency, so it make sense to exclude it in framework.
Hopefully this will be helpful for people just using the framework JAR
in the future.
-> richard
Stuart McCulloch wrote:
> 2008/10/8 Richard S. Hall <he...@ungoverned.org>
>
>
>> Richard S. Hall wrote:
>>
>>
>>> I guess servlet gets dragged into the framework dependencies from
>>> compendium. Should we put excluding servlet in our own POMs? Would it
>>> excluding it in the framework POM be sufficient?
>>>
>>>
>> Wow. This message is unreadable.
>>
>> "Should we exclude servlet in our own POMs? Would excluding it in the
>> framework POM be sufficient?"
>>
>>
>
> another approach is to mark the dependency as:
>
> <optional>true</optional>
>
> in the compendium pom - this tells Maven to use it when compiling the
> project, but not to include it when calculating transitive dependencies
>
> see: http://maven.apache.org/pom.html#Dependencies
>
> "optional:
>
> Marks optional a dependency when this project itself is a dependency.
> Confused? For example, imagine a project A that depends upon project
> B to compile a portion of code that may not be used at runtime, then we
> may have no need for project B for all project. So if project X adds
> project
> A as its own dependency, then Maven will not need to install project B at
> all.
>
> Symbolically, if => represents a required dependency, and --> represents
> optional, although A=>B may be the case when building A X=>A-->B would
> be the case when building X.
>
> In the shortest terms, optional lets other projects know that, when you
> use
> this project, you do not require this dependency in order to work
> correctly."
>
> HTH
>
> -> richard
>
>>> -> richard
>>>
>>> -------- Original Message --------
>>> Subject: Re: building a felix embedding web app with maven
>>> Date: Wed, 8 Oct 2008 17:08:49 +0800
>>> From: Stuart McCulloch <mc...@gmail.com>
>>> Reply-To: users@felix.apache.org
>>> To: users@felix.apache.org
>>> References: <
>>> OFCCA70B5C.64DDF772-ONCA2574DC.00289F6B-CA2574DC.002A02B1@qbe.com>
>>>
>>>
>>>
>>> 2008/10/8 Maxim Suponya <ma...@qbe.com>
>>>
>>> Hi,
>>>
>>>> I have a web app that is built using maven 2.0.8. The application's
>>>> pom.xml contains following dependency:
>>>>
>>>> <dependency>
>>>> <groupId>org.apache.felix</groupId>
>>>> <artifactId>org.apache.felix.framework</artifactId>
>>>> <version>1.2.1</version>
>>>> </dependency>
>>>>
>>>> But felix, in turn, depends on a project defined in
>>>> javax.servlet-1.0.0.pom which subsequently makes a jar file called
>>>> javax.servlet-1.0.0.jar ending up in WEB-INF/lib together with
>>>> org.apache.felix.framework-1.2.1.jar.
>>>>
>>>>
>>> have you tried using:
>>>
>>> <dependency>
>>> <groupId>org.apache.felix</groupId>
>>> <artifactId>org.apache.felix.framework</artifactId>
>>> <version>1.2.1</version>
>>> <exclusions>
>>> <exclusion>
>>> <groupId>org.apache.felix</groupId>
>>> <artifactId>javax.servlet</artifactId>
>>> </exclusion>
>>> </exclusions>
>>> </dependency>
>>>
>>> to tell Maven to exclude the transitive servlet dependency?
>>>
>>>
>>> When the web application starts and the servlet that launches felix gets
>>>
>>>> initialized, a ClassCastException is thrown saying that this servlet is
>>>> not a Servlet.. this is due to presence of javax.servlet-1.0.0.jar with
>>>> Servlet.class in WEB-INF/lib which comes in conflict with the one that's
>>>> provided by Tomcat.
>>>>
>>>> Adding <scope>provided</scope> in my app's pom.xml doesn't make any
>>>> difference.
>>>>
>>>> <dependency>
>>>> <groupId>org.apache.felix</groupId>
>>>> <artifactId>javax.servlet</artifactId>
>>>> <version>1.0.0</version>
>>>> <scope>provided</scope>
>>>> </dependency>
>>>>
>>>> Is there any way around this?
>>>>
>>>> Thanks a lot,
>>>>
>>>> Maxim
>>>>
>>>> - ----------------
>>>> IMPORTANT NOTICE : The information in this email is confidential and may
>>>> also be privileged. If you are not the intended recipient, any use or
>>>> dissemination of the information and any disclosure or copying of this
>>>> email
>>>> is unauthorised and strictly prohibited. If you have received this email
>>>> in
>>>> error, please promptly inform us by reply email or telephone. You should
>>>> also delete this email and destroy any hard copies produced.
>>>>
>>>>
Re: [Fwd: Re: building a felix embedding web app with maven]
Posted by Stuart McCulloch <mc...@gmail.com>.
2008/10/8 Richard S. Hall <he...@ungoverned.org>
> Richard S. Hall wrote:
>
>> I guess servlet gets dragged into the framework dependencies from
>> compendium. Should we put excluding servlet in our own POMs? Would it
>> excluding it in the framework POM be sufficient?
>>
>
> Wow. This message is unreadable.
>
> "Should we exclude servlet in our own POMs? Would excluding it in the
> framework POM be sufficient?"
>
another approach is to mark the dependency as:
<optional>true</optional>
in the compendium pom - this tells Maven to use it when compiling the
project, but not to include it when calculating transitive dependencies
see: http://maven.apache.org/pom.html#Dependencies
"optional:
Marks optional a dependency when this project itself is a dependency.
Confused? For example, imagine a project A that depends upon project
B to compile a portion of code that may not be used at runtime, then we
may have no need for project B for all project. So if project X adds
project
A as its own dependency, then Maven will not need to install project B at
all.
Symbolically, if => represents a required dependency, and --> represents
optional, although A=>B may be the case when building A X=>A-->B would
be the case when building X.
In the shortest terms, optional lets other projects know that, when you
use
this project, you do not require this dependency in order to work
correctly."
HTH
-> richard
>
>>
>> -> richard
>>
>> -------- Original Message --------
>> Subject: Re: building a felix embedding web app with maven
>> Date: Wed, 8 Oct 2008 17:08:49 +0800
>> From: Stuart McCulloch <mc...@gmail.com>
>> Reply-To: users@felix.apache.org
>> To: users@felix.apache.org
>> References: <
>> OFCCA70B5C.64DDF772-ONCA2574DC.00289F6B-CA2574DC.002A02B1@qbe.com>
>>
>>
>>
>> 2008/10/8 Maxim Suponya <ma...@qbe.com>
>>
>> Hi,
>>> I have a web app that is built using maven 2.0.8. The application's
>>> pom.xml contains following dependency:
>>>
>>> <dependency>
>>> <groupId>org.apache.felix</groupId>
>>> <artifactId>org.apache.felix.framework</artifactId>
>>> <version>1.2.1</version>
>>> </dependency>
>>>
>>> But felix, in turn, depends on a project defined in
>>> javax.servlet-1.0.0.pom which subsequently makes a jar file called
>>> javax.servlet-1.0.0.jar ending up in WEB-INF/lib together with
>>> org.apache.felix.framework-1.2.1.jar.
>>>
>>
>>
>> have you tried using:
>>
>> <dependency>
>> <groupId>org.apache.felix</groupId>
>> <artifactId>org.apache.felix.framework</artifactId>
>> <version>1.2.1</version>
>> <exclusions>
>> <exclusion>
>> <groupId>org.apache.felix</groupId>
>> <artifactId>javax.servlet</artifactId>
>> </exclusion>
>> </exclusions>
>> </dependency>
>>
>> to tell Maven to exclude the transitive servlet dependency?
>>
>>
>> When the web application starts and the servlet that launches felix gets
>>> initialized, a ClassCastException is thrown saying that this servlet is
>>> not a Servlet.. this is due to presence of javax.servlet-1.0.0.jar with
>>> Servlet.class in WEB-INF/lib which comes in conflict with the one that's
>>> provided by Tomcat.
>>>
>>> Adding <scope>provided</scope> in my app's pom.xml doesn't make any
>>> difference.
>>>
>>> <dependency>
>>> <groupId>org.apache.felix</groupId>
>>> <artifactId>javax.servlet</artifactId>
>>> <version>1.0.0</version>
>>> <scope>provided</scope>
>>> </dependency>
>>>
>>> Is there any way around this?
>>>
>>> Thanks a lot,
>>>
>>> Maxim
>>>
>>> - ----------------
>>> IMPORTANT NOTICE : The information in this email is confidential and may
>>> also be privileged. If you are not the intended recipient, any use or
>>> dissemination of the information and any disclosure or copying of this
>>> email
>>> is unauthorised and strictly prohibited. If you have received this email
>>> in
>>> error, please promptly inform us by reply email or telephone. You should
>>> also delete this email and destroy any hard copies produced.
>>>
>>
--
Cheers, Stuart
Re: [Fwd: Re: building a felix embedding web app with maven]
Posted by "Richard S. Hall" <he...@ungoverned.org>.
Richard S. Hall wrote:
> I guess servlet gets dragged into the framework dependencies from
> compendium. Should we put excluding servlet in our own POMs? Would it
> excluding it in the framework POM be sufficient?
Wow. This message is unreadable.
"Should we exclude servlet in our own POMs? Would excluding it in the
framework POM be sufficient?"
-> richard
>
> -> richard
>
> -------- Original Message --------
> Subject: Re: building a felix embedding web app with maven
> Date: Wed, 8 Oct 2008 17:08:49 +0800
> From: Stuart McCulloch <mc...@gmail.com>
> Reply-To: users@felix.apache.org
> To: users@felix.apache.org
> References:
> <OF...@qbe.com>
>
>
>
> 2008/10/8 Maxim Suponya <ma...@qbe.com>
>
>> Hi,
>> I have a web app that is built using maven 2.0.8. The application's
>> pom.xml contains following dependency:
>>
>> <dependency>
>> <groupId>org.apache.felix</groupId>
>> <artifactId>org.apache.felix.framework</artifactId>
>> <version>1.2.1</version>
>> </dependency>
>>
>> But felix, in turn, depends on a project defined in
>> javax.servlet-1.0.0.pom which subsequently makes a jar file called
>> javax.servlet-1.0.0.jar ending up in WEB-INF/lib together with
>> org.apache.felix.framework-1.2.1.jar.
>
>
> have you tried using:
>
> <dependency>
> <groupId>org.apache.felix</groupId>
> <artifactId>org.apache.felix.framework</artifactId>
> <version>1.2.1</version>
> <exclusions>
> <exclusion>
> <groupId>org.apache.felix</groupId>
> <artifactId>javax.servlet</artifactId>
> </exclusion>
> </exclusions>
> </dependency>
>
> to tell Maven to exclude the transitive servlet dependency?
>
>
>> When the web application starts and the servlet that launches felix gets
>> initialized, a ClassCastException is thrown saying that this servlet is
>> not a Servlet.. this is due to presence of javax.servlet-1.0.0.jar with
>> Servlet.class in WEB-INF/lib which comes in conflict with the one that's
>> provided by Tomcat.
>>
>> Adding <scope>provided</scope> in my app's pom.xml doesn't make any
>> difference.
>>
>> <dependency>
>> <groupId>org.apache.felix</groupId>
>> <artifactId>javax.servlet</artifactId>
>> <version>1.0.0</version>
>> <scope>provided</scope>
>> </dependency>
>>
>> Is there any way around this?
>>
>> Thanks a lot,
>>
>> Maxim
>>
>> - ----------------
>> IMPORTANT NOTICE : The information in this email is confidential and may
>> also be privileged. If you are not the intended recipient, any use or
>> dissemination of the information and any disclosure or copying of
>> this email
>> is unauthorised and strictly prohibited. If you have received this
>> email in
>> error, please promptly inform us by reply email or telephone. You should
>> also delete this email and destroy any hard copies produced.
>
>
RE: [Fwd: Re: building a felix embedding web app with maven]
Posted by Craig Phillips <lc...@praxiseng.com>.
Hi,
This is probably slightly off topic, as below seems to be focused on maven / build stuff...
I have a demonstration, which I could provide the eclipse project/workspace if anyone is interested, of a tomcat web app that embeds felix... The idea was a bit more decoupling than what most attempts have tried, from what I've seen... My tenants were: A). Tomcat has no idea that embedded OSGi ('er, felix as the equinox has a NPE bug in it, for which I logged a bugzilla report) is occurring, and B). the embedded OSGi (bundles and services thereof) have no idea that they are in a web app (tomcat or otherwise); After all, OSGi is loose coupling taken to another stratosphere (for which I am not complaining in the least, certainly pleased with the mentality/mind-set), and thus the embedding of which should also be loosely coupled;
Now, with the loose coupling mantra said, I still had to modify the bootdelegation line to include my embedded services API, but that was acceptable to me -- So, the trick was to have a small piece of glue code that takes the web app request(s) and translates to an embedded bundle service a la the API -- hence, if the API changes, my glue code would need to change -- so, the bootdelegation entry didn't bother me; I have a few ideas to make my embedded API in a "meta model" scheme, at which point the API would barely need to change.... but I leave that to your imagination... One big thing I've always liked about OSGi (and Felix even better): minimal agenda (like the "Lego" analogy); I don't get that mentality from Sun or even other implementations (and, don't get me started on J-7);
Well, thought I'd throw that out there, sort of related fodder to embedding and web apps...
Craig Phillips, Praxis
________________________________
From: Richard S. Hall [mailto:heavy@ungoverned.org]
Sent: Wed 10/8/2008 9:27 AM
To: dev@felix.apache.org
Subject: [Fwd: Re: building a felix embedding web app with maven]
I guess servlet gets dragged into the framework dependencies from
compendium. Should we put excluding servlet in our own POMs? Would it
excluding it in the framework POM be sufficient?
-> richard
-------- Original Message --------
Subject: Re: building a felix embedding web app with maven
Date: Wed, 8 Oct 2008 17:08:49 +0800
From: Stuart McCulloch <mc...@gmail.com>
Reply-To: users@felix.apache.org
To: users@felix.apache.org
References:
<OF...@qbe.com>
2008/10/8 Maxim Suponya <ma...@qbe.com>
> Hi,
> I have a web app that is built using maven 2.0.8. The application's
> pom.xml contains following dependency:
>
> <dependency>
> <groupId>org.apache.felix</groupId>
> <artifactId>org.apache.felix.framework</artifactId>
> <version>1.2.1</version>
> </dependency>
>
> But felix, in turn, depends on a project defined in
> javax.servlet-1.0.0.pom which subsequently makes a jar file called
> javax.servlet-1.0.0.jar ending up in WEB-INF/lib together with
> org.apache.felix.framework-1.2.1.jar.
have you tried using:
<dependency>
<groupId>org.apache.felix</groupId>
<artifactId>org.apache.felix.framework</artifactId>
<version>1.2.1</version>
<exclusions>
<exclusion>
<groupId>org.apache.felix</groupId>
<artifactId>javax.servlet</artifactId>
</exclusion>
</exclusions>
</dependency>
to tell Maven to exclude the transitive servlet dependency?
> When the web application starts and the servlet that launches felix gets
> initialized, a ClassCastException is thrown saying that this servlet is
> not a Servlet.. this is due to presence of javax.servlet-1.0.0.jar with
> Servlet.class in WEB-INF/lib which comes in conflict with the one that's
> provided by Tomcat.
>
> Adding <scope>provided</scope> in my app's pom.xml doesn't make any
> difference.
>
> <dependency>
> <groupId>org.apache.felix</groupId>
> <artifactId>javax.servlet</artifactId>
> <version>1.0.0</version>
> <scope>provided</scope>
> </dependency>
>
> Is there any way around this?
>
> Thanks a lot,
>
> Maxim
>
> - ----------------
> IMPORTANT NOTICE : The information in this email is confidential and may
> also be privileged. If you are not the intended recipient, any use or
> dissemination of the information and any disclosure or copying of this email
> is unauthorised and strictly prohibited. If you have received this email in
> error, please promptly inform us by reply email or telephone. You should
> also delete this email and destroy any hard copies produced.
--
Cheers, Stuart