Hi,

Fixed in trunk with https://issues.apache.org/jira/browse/JAMESAPP-7

You say you have a problem when upgrading to latest camel. How did you upgrade? you should do it via the pom and rebuild everything.

Alternatively, you can download a snapshot from https://repository.apache.org/content/repositories/snapshots/org/apache/james/apache-james/3.0-beta5-SNAPSHOT/

Thx, Eric


On 29/10/2012 14:10, Alan Mehio wrote:
INFO  15:02:28,783 |
org.apache.james.container.spring.context.JamesServerApplicationContext |
Refreshing org.apache.james.container.spring.context.JamesServerApplic
ationContext@54031f94: startup date [Mon Oct 29 15:02:28 CET 2012]; root of
context hierarchy
Exception in thread "main"
org.springframework.beans.factory.BeanDefinitionStoreException: Failed to
create the JAXB binder; nested exception is javax.xml.bind.JAXBE
xception: Provider com.sun.xml.internal.bind.v2.ContextFactory could not be
instantiated:
com.sun.xml.internal.bind.v2.runtime.IllegalAnnotationsException: 1 counts
of IllegalAnnotationExceptions
Class has two properties of the same name "outputs"
         this problem is related to the following location:
                 at public java.util.List
org.apache.camel.model.ResequenceDefinition.getOutputs()
                 at org.apache.camel.model.ResequenceDefinition
         this problem is related to the following location:
                 at private java.util.List
org.apache.camel.model.ResequenceDefinition.outputs
                 at org.apache.camel.model.ResequenceDefinition




Upgrading  apache camel-core to latest version does not sort the problem
but create different problem
the java version which is causing the issue is
java version "1.7.0_06"
Java(TM) SE Runtime Environment (build 1.7.0_06-b24)
Java HotSpot(TM) 64-Bit Server VM (build 23.2-b09, mixed mode)


Any idea why? and have somebody encountered this issue

Thanks
Alan Mehio


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to