Yes. That is a big problem in the camel examples. The parent poms make
it very difficult for users to use these examples as a starting point
for their own projects or
in your case to upgrade the example.
Christian
Am 17.03.2012 23:14, schrieb gsilverman:
I see where the errant jar was introd
I see where the errant jar was introduced. It was in the v 2.8.1 parent pom
versioning. Simply changing the version of some of the camel components in
the project's pom was not sufficient due to maven's transitivity.
--
View this message in context:
http://camel.465427.n5.nabble.com/Error-cannot
I just tried the same example from the 2.9.1 distro. The servlet api is
not in the war.
Why don´t you just use this one?
Christian
Am 17.03.2012 01:55, schrieb gsilverman:
Here is the maven dependency tree. As you can see, the camel-servlet verson
2.9.1 has a transitive dependency on javax.ser
Hi
Did you see my previous post?
Look at the dependency tree how there's a mix-up of Camel 2.8.1 and 2.9.1
versions. Just fix the example POM you've modified and check the dependency
tree again.
Babak
--
View this message in context:
http://camel.465427.n5.nabble.com/Error-cannot-run-camel-ser
Here is the maven dependency tree. As you can see, the camel-servlet verson
2.9.1 has a transitive dependency on javax.servlet, from the http
component. Obviously, while the 2.8.1 version scopes this as "provided",
apparently that is not the case with version 2.9.1.
Building Camel :: Example ::
Hi
If you cross-reference an example of Camel release X with Y that's the best
you
will get out of it! As you claim to run camel-example-servlet-tomcat version
2.8.1
you should consequently remove ALL the lines:
2.9.1
That you've put inside the POM manually by yourself. Or change them to
2.8.1
Can you run a mvn dependency:tree in your project.
The servet-spec dependency have been marked as provided scope by the
Camel components, and thus the WAR file
ought not to include them. But maybe there is something we have missed.
On Thu, Mar 15, 2012 at 4:27 PM, gsilverman
wrote:
> Ah. I stan
Ah. I stand corrected, somewhat. Camel servlet 2.9.1 inserts
geronimo-servlet_2.4_spec-1.1.1.jar in the war file, whereas v 2.8.1 does
not. It seems, therefore, that the newer camel is not web application server
friendly. out of the box.
--
View this message in context:
http://camel.465427.n5.nab
I'm using jdk1.6.0_26 and Tomcat 6.0.33. But that seems hardly relevant. Just
change the camel version in the pom back to the original - 2.8.1, and the
darn thing runs. Did you run the example?Something's broken in camel v
2.9.x. And, no, servlet.jar is not in WEB-INF/lib.
--
View this message in
Hi
What version of Tomcat and JDK are you using?
And make sure to not include any servlet.jar etc in WEB-INF/lib as
they are already part of Tomcat, and you may get class loading issues.
On Thu, Mar 15, 2012 at 1:41 AM, gsilverman
wrote:
> I changed the camel version in the camel-example-servl
I changed the camel version in the camel-example-servlet-tomcat pom.xml from
the apache-camel-2.8.1 package, and got the following error trying to run
*mvn package tomcat:run*;
java.lang.ClassCastException:
org.apache.camel.component.servlet.CamelHttpTransportServlet cannot be cast
to javax.servl
11 matches
Mail list logo
