You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@servicemix.apache.org by Ingo Mittrup <in...@ruhr-uni-bochum.de> on 2008/03/11 10:33:46 UTC
JAXB jars missing in servicemix-3.3-SNAPSHOT?
Hi!
I've built servicemix-3.3-SNAPSHOT following the instructions on the SMX
website. When i deploy a cxf-se service unit (correctly running under
SMX 3.2.1 and 3.2.2) into SMX 3.3-SNAPSHOT, i get an expection (see
exception stack trace below).
For building SMX 3.3-SNAPSHOT, i ran:
mvn -Dmaven.test.skip=true -Pstep1 install
mvn -Dmaven.test.skip=true -Pstep2 install
Did i miss something?
Best regards
Ingo
= = = = = = = = = = = = = =
Exception in thread "Timer-4" java.lang.NoClassDefFoundError:
com/sun/xml/bind/m
arshaller/NamespacePrefixMapper
at
org.apache.cxf.service.factory.ReflectionServiceFactoryBean.createDef
aultDataBinding(ReflectionServiceFactoryBean.java:170)
at
org.apache.cxf.service.factory.AbstractServiceFactoryBean.getDataBind
ing(AbstractServiceFactoryBean.java:56)
at
org.apache.cxf.frontend.ServerFactoryBean.applyExtraClass(ServerFacto
ryBean.java:196)
at
org.apache.cxf.frontend.ServerFactoryBean.create(ServerFactoryBean.ja
va:103)
at
org.apache.cxf.jaxws.JaxWsServerFactoryBean.create(JaxWsServerFactory
Bean.java:147)
at
org.apache.cxf.jaxws.EndpointImpl.getServer(EndpointImpl.java:310)
at
org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:240)
at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:191)
at
org.apache.servicemix.cxfse.CxfSeEndpoint.start(CxfSeEndpoint.java:21
1)
at
org.apache.servicemix.common.endpoints.SimpleEndpoint.activate(Simple
Endpoint.java:55)
at
org.apache.servicemix.common.ServiceUnit.start(ServiceUnit.java:53)
at
org.apache.servicemix.common.BaseServiceUnitManager.start(BaseService
UnitManager.java:151)
at
org.apache.servicemix.jbi.framework.ServiceUnitLifeCycle.start(Servic
eUnitLifeCycle.java:103)
at
org.apache.servicemix.jbi.framework.ServiceAssemblyLifeCycle.start(Se
rviceAssemblyLifeCycle.java:132)
at
org.apache.servicemix.jbi.framework.DeploymentService.start(Deploymen
tService.java:378)
at
org.apache.servicemix.jbi.framework.AutoDeploymentService.updateServi
ceAssembly(AutoDeploymentService.java:355)
at
org.apache.servicemix.jbi.framework.AutoDeploymentService.updateArchi
ve(AutoDeploymentService.java:256)
at
org.apache.servicemix.jbi.framework.AutoDeploymentService.monitorDire
ctory(AutoDeploymentService.java:658)
at
org.apache.servicemix.jbi.framework.AutoDeploymentService.access$800(
AutoDeploymentService.java:62)
at
org.apache.servicemix.jbi.framework.AutoDeploymentService$1.run(AutoD
eploymentService.java:622)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
Re: JAXB jars missing in servicemix-3.3-SNAPSHOT?
Posted by Cybexion <cy...@email.de>.
no I didn't
Just did a clean and then rebuild everything and now the components are
correctly inside.
With components I meant the stuff inside the hotdeploy dir, especially
servicemix-cxf....zip
Thanks Freeman, this is now clean.
Freeman Fang wrote:
>
> Did you do "mvn clean" first?
> What kind of "old" components you see?
>
> Freeman
>
> Cybexion wrote:
>> Thanks Freeman!
>> The components build worked fine now. The cxf components do now contain
>> the
>> jaxb jars.
>> However, I built the the sm 3.3 trunk but inside there there are still
>> the
>> "old" components in the hotdeployment dir. I don't think I have to copy
>> them
>> manually into there, or?
>> Did I do something wrong? How do the components get into the mail sm
>> build?
>>
>>
>>
>>
>> Freeman Fang wrote:
>>
>>> Hi,
>>>
>>> This issue get resolved, [1] track this issue.
>>>
>>> Since servicemix 3.3 trunk now have new components project, so you also
>>> need download components from [2], and build the components first
>>> cd components/components-pom/trunk; mvn install -Dmaven.test.skip=true
>>> then build the 3.3 snapshot kit from the distribution folder
>>>
>>> [1]https://issues.apache.org/activemq/browse/SM-1423
>>> [2]http://svn.apache.org/repos/asf/servicemix/components/
>>>
>>> Regards
>>> Freeman
>>>
>>> Freeman Fang wrote:
>>>
>>>> Cybexion wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I just had the same problem. This morning I build the latest 3.3
>>>>> trunk. When
>>>>> deploying the wsdl first example I got the described error.
>>>>> I'm using JDK1.6.0_05 which should include the right jaxb version.
>>>>> The cxf
>>>>> bc and se do not contain jaxb. Personally I think they even don't
>>>>> need to
>>>>> contain jaxb because it is part of the jdk! ?!?!?
>>>>> Well I got it finally to work by doing the following:
>>>>> 1. create dir %SERVICEMIX_HOME%/lib/endorsed
>>>>> 2. copy jaxb-impl-2.1.4.jar into this dir
>>>>> 3. restart servicemix
>>>>>
>>>>> Could please one of the sm developers check, why this was necessary_
>>>>>
>>>>>
>>>> IIRC, jdk 16 include jaxb api but not the jaxb impl, so jaxb impl is
>>>> necessary.
>>>>
>>>> I also see the problem today, I will fix it up asap
>>>>
>>>> Freeman
>>>>
>>>>> Thanks
>>>>>
>>>>>
>>>>>
>>>>> Will Gomes wrote:
>>>>>
>>>>>
>>>>>> In case it helps others out, I stopped getting the JAXB error when I
>>>>>> switched to use Java 1.6.0_05 which includes the 2.1 api. Before, I
>>>>>> was
>>>>>> using Java 1.6_03 endorsed with JAXB 2.1 api jars. But it turns out
>>>>>> the
>>>>>> servicemix startup script reset the endorsed directory to
>>>>>> '%SERVICEMIX_HOME%\lib\endorsed', so my endorsed jars never got
>>>>>> picked up
>>>>>> causing the linkage error.
>>>>>>
>>>>>>
>>>>>> Freeman Fang wrote:
>>>>>>
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> I just build 3.3 snapshot kit from 3.3 branch, and cxf-wsdl-first
>>>>>>> example run successfully for me.
>>>>>>> Since the linkage error is usually from version conflict, did you
>>>>>>> deploy wsdl-first-cxf-sa-3.3-SNAPSHOT.zip into previouse servicemix
>>>>>>> version?
>>>>>>> Or could you describe how you deploy the
>>>>>>> wsdl-first-cxf-sa-3.3-SNAPSHOT.zip?
>>>>>>>
>>>>>>> Regards
>>>>>>>
>>>>>>> Freeman
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>
>>>>>
>>>>
>>>
>>>
>>
>>
>
>
>
--
View this message in context: http://www.nabble.com/JAXB-jars-missing-in-servicemix-3.3-SNAPSHOT--tp15978159p18213933.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: JAXB jars missing in servicemix-3.3-SNAPSHOT?
Posted by Freeman Fang <fr...@gmail.com>.
Did you do "mvn clean" first?
What kind of "old" components you see?
Freeman
Cybexion wrote:
> Thanks Freeman!
> The components build worked fine now. The cxf components do now contain the
> jaxb jars.
> However, I built the the sm 3.3 trunk but inside there there are still the
> "old" components in the hotdeployment dir. I don't think I have to copy them
> manually into there, or?
> Did I do something wrong? How do the components get into the mail sm build?
>
>
>
>
> Freeman Fang wrote:
>
>> Hi,
>>
>> This issue get resolved, [1] track this issue.
>>
>> Since servicemix 3.3 trunk now have new components project, so you also
>> need download components from [2], and build the components first
>> cd components/components-pom/trunk; mvn install -Dmaven.test.skip=true
>> then build the 3.3 snapshot kit from the distribution folder
>>
>> [1]https://issues.apache.org/activemq/browse/SM-1423
>> [2]http://svn.apache.org/repos/asf/servicemix/components/
>>
>> Regards
>> Freeman
>>
>> Freeman Fang wrote:
>>
>>> Cybexion wrote:
>>>
>>>> Hi,
>>>>
>>>> I just had the same problem. This morning I build the latest 3.3
>>>> trunk. When
>>>> deploying the wsdl first example I got the described error.
>>>> I'm using JDK1.6.0_05 which should include the right jaxb version.
>>>> The cxf
>>>> bc and se do not contain jaxb. Personally I think they even don't
>>>> need to
>>>> contain jaxb because it is part of the jdk! ?!?!?
>>>> Well I got it finally to work by doing the following:
>>>> 1. create dir %SERVICEMIX_HOME%/lib/endorsed
>>>> 2. copy jaxb-impl-2.1.4.jar into this dir
>>>> 3. restart servicemix
>>>>
>>>> Could please one of the sm developers check, why this was necessary_
>>>>
>>>>
>>> IIRC, jdk 16 include jaxb api but not the jaxb impl, so jaxb impl is
>>> necessary.
>>>
>>> I also see the problem today, I will fix it up asap
>>>
>>> Freeman
>>>
>>>> Thanks
>>>>
>>>>
>>>>
>>>> Will Gomes wrote:
>>>>
>>>>
>>>>> In case it helps others out, I stopped getting the JAXB error when I
>>>>> switched to use Java 1.6.0_05 which includes the 2.1 api. Before, I was
>>>>> using Java 1.6_03 endorsed with JAXB 2.1 api jars. But it turns out the
>>>>> servicemix startup script reset the endorsed directory to
>>>>> '%SERVICEMIX_HOME%\lib\endorsed', so my endorsed jars never got
>>>>> picked up
>>>>> causing the linkage error.
>>>>>
>>>>>
>>>>> Freeman Fang wrote:
>>>>>
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> I just build 3.3 snapshot kit from 3.3 branch, and cxf-wsdl-first
>>>>>> example run successfully for me.
>>>>>> Since the linkage error is usually from version conflict, did you
>>>>>> deploy wsdl-first-cxf-sa-3.3-SNAPSHOT.zip into previouse servicemix
>>>>>> version?
>>>>>> Or could you describe how you deploy the
>>>>>> wsdl-first-cxf-sa-3.3-SNAPSHOT.zip?
>>>>>>
>>>>>> Regards
>>>>>>
>>>>>> Freeman
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>
>>>>
>>>
>>
>>
>
>
Re: JAXB jars missing in servicemix-3.3-SNAPSHOT?
Posted by Cybexion <cy...@email.de>.
Thanks Freeman!
The components build worked fine now. The cxf components do now contain the
jaxb jars.
However, I built the the sm 3.3 trunk but inside there there are still the
"old" components in the hotdeployment dir. I don't think I have to copy them
manually into there, or?
Did I do something wrong? How do the components get into the mail sm build?
Freeman Fang wrote:
>
> Hi,
>
> This issue get resolved, [1] track this issue.
>
> Since servicemix 3.3 trunk now have new components project, so you also
> need download components from [2], and build the components first
> cd components/components-pom/trunk; mvn install -Dmaven.test.skip=true
> then build the 3.3 snapshot kit from the distribution folder
>
> [1]https://issues.apache.org/activemq/browse/SM-1423
> [2]http://svn.apache.org/repos/asf/servicemix/components/
>
> Regards
> Freeman
>
> Freeman Fang wrote:
>> Cybexion wrote:
>>> Hi,
>>>
>>> I just had the same problem. This morning I build the latest 3.3
>>> trunk. When
>>> deploying the wsdl first example I got the described error.
>>> I'm using JDK1.6.0_05 which should include the right jaxb version.
>>> The cxf
>>> bc and se do not contain jaxb. Personally I think they even don't
>>> need to
>>> contain jaxb because it is part of the jdk! ?!?!?
>>> Well I got it finally to work by doing the following:
>>> 1. create dir %SERVICEMIX_HOME%/lib/endorsed
>>> 2. copy jaxb-impl-2.1.4.jar into this dir
>>> 3. restart servicemix
>>>
>>> Could please one of the sm developers check, why this was necessary_
>>>
>> IIRC, jdk 16 include jaxb api but not the jaxb impl, so jaxb impl is
>> necessary.
>>
>> I also see the problem today, I will fix it up asap
>>
>> Freeman
>>> Thanks
>>>
>>>
>>>
>>> Will Gomes wrote:
>>>
>>>> In case it helps others out, I stopped getting the JAXB error when I
>>>> switched to use Java 1.6.0_05 which includes the 2.1 api. Before, I was
>>>> using Java 1.6_03 endorsed with JAXB 2.1 api jars. But it turns out the
>>>> servicemix startup script reset the endorsed directory to
>>>> '%SERVICEMIX_HOME%\lib\endorsed', so my endorsed jars never got
>>>> picked up
>>>> causing the linkage error.
>>>>
>>>>
>>>> Freeman Fang wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I just build 3.3 snapshot kit from 3.3 branch, and cxf-wsdl-first
>>>>> example run successfully for me.
>>>>> Since the linkage error is usually from version conflict, did you
>>>>> deploy wsdl-first-cxf-sa-3.3-SNAPSHOT.zip into previouse servicemix
>>>>> version?
>>>>> Or could you describe how you deploy the
>>>>> wsdl-first-cxf-sa-3.3-SNAPSHOT.zip?
>>>>>
>>>>> Regards
>>>>>
>>>>> Freeman
>>>>>
>>>>>
>>>>>
>>>
>>>
>>
>>
>
>
>
--
View this message in context: http://www.nabble.com/JAXB-jars-missing-in-servicemix-3.3-SNAPSHOT--tp15978159p18212705.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: JAXB jars missing in servicemix-3.3-SNAPSHOT?
Posted by Freeman Fang <fr...@gmail.com>.
Hi,
This issue get resolved, [1] track this issue.
Since servicemix 3.3 trunk now have new components project, so you also
need download components from [2], and build the components first
cd components/components-pom/trunk; mvn install -Dmaven.test.skip=true
then build the 3.3 snapshot kit from the distribution folder
[1]https://issues.apache.org/activemq/browse/SM-1423
[2]http://svn.apache.org/repos/asf/servicemix/components/
Regards
Freeman
Freeman Fang wrote:
> Cybexion wrote:
>> Hi,
>>
>> I just had the same problem. This morning I build the latest 3.3
>> trunk. When
>> deploying the wsdl first example I got the described error.
>> I'm using JDK1.6.0_05 which should include the right jaxb version.
>> The cxf
>> bc and se do not contain jaxb. Personally I think they even don't
>> need to
>> contain jaxb because it is part of the jdk! ?!?!?
>> Well I got it finally to work by doing the following:
>> 1. create dir %SERVICEMIX_HOME%/lib/endorsed
>> 2. copy jaxb-impl-2.1.4.jar into this dir
>> 3. restart servicemix
>>
>> Could please one of the sm developers check, why this was necessary_
>>
> IIRC, jdk 16 include jaxb api but not the jaxb impl, so jaxb impl is
> necessary.
>
> I also see the problem today, I will fix it up asap
>
> Freeman
>> Thanks
>>
>>
>>
>> Will Gomes wrote:
>>
>>> In case it helps others out, I stopped getting the JAXB error when I
>>> switched to use Java 1.6.0_05 which includes the 2.1 api. Before, I was
>>> using Java 1.6_03 endorsed with JAXB 2.1 api jars. But it turns out the
>>> servicemix startup script reset the endorsed directory to
>>> '%SERVICEMIX_HOME%\lib\endorsed', so my endorsed jars never got
>>> picked up
>>> causing the linkage error.
>>>
>>>
>>> Freeman Fang wrote:
>>>
>>>> Hi,
>>>>
>>>> I just build 3.3 snapshot kit from 3.3 branch, and cxf-wsdl-first
>>>> example run successfully for me.
>>>> Since the linkage error is usually from version conflict, did you
>>>> deploy wsdl-first-cxf-sa-3.3-SNAPSHOT.zip into previouse servicemix
>>>> version?
>>>> Or could you describe how you deploy the
>>>> wsdl-first-cxf-sa-3.3-SNAPSHOT.zip?
>>>>
>>>> Regards
>>>>
>>>> Freeman
>>>>
>>>>
>>>>
>>
>>
>
>
Re: JAXB jars missing in servicemix-3.3-SNAPSHOT?
Posted by Freeman Fang <fr...@gmail.com>.
Cybexion wrote:
> Hi,
>
> I just had the same problem. This morning I build the latest 3.3 trunk. When
> deploying the wsdl first example I got the described error.
> I'm using JDK1.6.0_05 which should include the right jaxb version. The cxf
> bc and se do not contain jaxb. Personally I think they even don't need to
> contain jaxb because it is part of the jdk! ?!?!?
> Well I got it finally to work by doing the following:
> 1. create dir %SERVICEMIX_HOME%/lib/endorsed
> 2. copy jaxb-impl-2.1.4.jar into this dir
> 3. restart servicemix
>
> Could please one of the sm developers check, why this was necessary_
>
IIRC, jdk 16 include jaxb api but not the jaxb impl, so jaxb impl is
necessary.
I also see the problem today, I will fix it up asap
Freeman
> Thanks
>
>
>
> Will Gomes wrote:
>
>> In case it helps others out, I stopped getting the JAXB error when I
>> switched to use Java 1.6.0_05 which includes the 2.1 api. Before, I was
>> using Java 1.6_03 endorsed with JAXB 2.1 api jars. But it turns out the
>> servicemix startup script reset the endorsed directory to
>> '%SERVICEMIX_HOME%\lib\endorsed', so my endorsed jars never got picked up
>> causing the linkage error.
>>
>>
>> Freeman Fang wrote:
>>
>>> Hi,
>>>
>>> I just build 3.3 snapshot kit from 3.3 branch, and cxf-wsdl-first
>>> example run successfully for me.
>>> Since the linkage error is usually from version conflict, did you
>>> deploy wsdl-first-cxf-sa-3.3-SNAPSHOT.zip into previouse servicemix
>>> version?
>>> Or could you describe how you deploy the
>>> wsdl-first-cxf-sa-3.3-SNAPSHOT.zip?
>>>
>>> Regards
>>>
>>> Freeman
>>>
>>>
>>>
>
>
Re: JAXB jars missing in servicemix-3.3-SNAPSHOT?
Posted by Cybexion <cy...@email.de>.
Hi,
I just had the same problem. This morning I build the latest 3.3 trunk. When
deploying the wsdl first example I got the described error.
I'm using JDK1.6.0_05 which should include the right jaxb version. The cxf
bc and se do not contain jaxb. Personally I think they even don't need to
contain jaxb because it is part of the jdk! ?!?!?
Well I got it finally to work by doing the following:
1. create dir %SERVICEMIX_HOME%/lib/endorsed
2. copy jaxb-impl-2.1.4.jar into this dir
3. restart servicemix
Could please one of the sm developers check, why this was necessary_
Thanks
Will Gomes wrote:
>
> In case it helps others out, I stopped getting the JAXB error when I
> switched to use Java 1.6.0_05 which includes the 2.1 api. Before, I was
> using Java 1.6_03 endorsed with JAXB 2.1 api jars. But it turns out the
> servicemix startup script reset the endorsed directory to
> '%SERVICEMIX_HOME%\lib\endorsed', so my endorsed jars never got picked up
> causing the linkage error.
>
>
> Freeman Fang wrote:
>>
>> Hi,
>>
>> I just build 3.3 snapshot kit from 3.3 branch, and cxf-wsdl-first
>> example run successfully for me.
>> Since the linkage error is usually from version conflict, did you
>> deploy wsdl-first-cxf-sa-3.3-SNAPSHOT.zip into previouse servicemix
>> version?
>> Or could you describe how you deploy the
>> wsdl-first-cxf-sa-3.3-SNAPSHOT.zip?
>>
>> Regards
>>
>> Freeman
>>
>>
>
--
View this message in context: http://www.nabble.com/JAXB-jars-missing-in-servicemix-3.3-SNAPSHOT--tp15978159p18192907.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: JAXB jars missing in servicemix-3.3-SNAPSHOT?
Posted by Will Gomes <wg...@umd.edu>.
In case it helps others out, I stopped getting the JAXB error when I switched
to use Java 1.6.0_05 which includes the 2.1 api. Before, I was using Java
1.6_03 endorsed with JAXB 2.1 api jars. But it turns out the servicemix
startup script reset the endorsed directory to
'%SERVICEMIX_HOME%\lib\endorsed', so my endorsed jars never got picked up
causing the linkage error.
Freeman Fang wrote:
>
> Hi,
>
> I just build 3.3 snapshot kit from 3.3 branch, and cxf-wsdl-first
> example run successfully for me.
> Since the linkage error is usually from version conflict, did you
> deploy wsdl-first-cxf-sa-3.3-SNAPSHOT.zip into previouse servicemix
> version?
> Or could you describe how you deploy the
> wsdl-first-cxf-sa-3.3-SNAPSHOT.zip?
>
> Regards
>
> Freeman
>
>
--
View this message in context: http://www.nabble.com/JAXB-jars-missing-in-servicemix-3.3-SNAPSHOT--tp15978159p16573757.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: JAXB jars missing in servicemix-3.3-SNAPSHOT?
Posted by Freeman Fang <fr...@gmail.com>.
Hi,
I just build 3.3 snapshot kit from 3.3 branch, and cxf-wsdl-first
example run successfully for me.
Since the linkage error is usually from version conflict, did you
deploy wsdl-first-cxf-sa-3.3-SNAPSHOT.zip into previouse servicemix version?
Or could you describe how you deploy the wsdl-first-cxf-sa-3.3-SNAPSHOT.zip?
Regards
Freeman
Will Gomes wrote:
> Complete rebuild includes the correct jaxb for cxf components. But I still
> get linkage error for JAXB api when deploying:
> wsdl-first-cxf-sa-3.3-SNAPSHOT.zip.
>
>
> Freeman Fang wrote:
>
>> Hi,
>>
>> This problem which is caused by different jaxb version conflict should
>> already be resolved.
>> By my test the servicemix-cxf-se-3.3-SNAPSHOT-installer.zip contain the
>> proper jaxb-impl version, 2.1.4.
>> Would you please try to make a clean build from root folder of your
>> servicemix, not only build the cxf component.
>>
>> Regards
>>
>> Freeman
>>
>> Will Gomes wrote:
>>
>>> Freeman Fang wrote:
>>>
>>>
>>>> Hi Ingo,
>>>>
>>>> Please unzip servicemix-cxf-se-3.3-SNAPSHOT-installer.zip in the kit you
>>>> generated and check if there is a jaxb-impl-2.1.4.jar inside, this jar
>>>> contain com/sun/xml/bind/marshaller/NamespacePrefixMapper class.
>>>> It's there by my test.
>>>>
>>>> Regards
>>>>
>>>>
>>>>
>>>>
>>> I'm having the same problem. The jaxb-impl-2.1.4.jar is missing from
>>> both
>>> servicemix-cxf-se-3.3-SNAPSHOT-installer.zip and
>>> servicemix-cxf-bc-3.3-SNAPSHOT-installer.zip.
>>> I added these to the zip files and modified the respective jbi.xml files.
>>> Now when deploying i get the following error:
>>>
>>> INFO: Creating Service
>>> {http://servicemix.apache.org/samples/wsdl-first}PersonSe
>>> rvice from class org.apache.servicemix.samples.wsdl_first.Person
>>> Exception in thread "Timer-3" java.lang.LinkageError: JAXB 2.0 API is
>>> being
>>> load
>>> ed from the bootstrap classloader, but this RI (from
>>> jar:file:/C:/apache-service
>>> mix-3.3-20070312-SNAPSHOT/data/smx/components/servicemix-cxf-se/version_1/lib/ja
>>> xb-impl-2.1.4.jar!/com/sun/xml/bind/v2/model/impl/ModelBuilder.class)
>>> needs
>>> 2.1
>>> API. Use the endorsed directory mechanism to place jaxb-api.jar in the
>>> bootstrap
>>> classloader. (See http://java.sun.com/j2se/1.5.0/docs/guide/standards/)
>>> at
>>> com.sun.xml.bind.v2.model.impl.ModelBuilder.<clinit>(ModelBuilder.jav
>>> a:172)
>>> at
>>> com.sun.xml.bind.v2.runtime.JAXBContextImpl.getTypeInfoSet(JAXBContex
>>> tImpl.java:422)
>>> at
>>> com.sun.xml.bind.v2.runtime.JAXBContextImpl.<init>(JAXBContextImpl.ja
>>> va:286)
>>> at
>>> com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:
>>> 139)
>>> at
>>> com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:
>>> 117)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
>>> java:39)
>>> at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
>>> sorImpl.java:25)
>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>> at
>>> javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:210)
>>> at javax.xml.bind.ContextFinder.find(ContextFinder.java:368)
>>> at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:574)
>>> at
>>> org.apache.cxf.jaxb.JAXBDataBinding.createJAXBContext(JAXBDataBinding
>>> .java:460)
>>> at
>>> org.apache.cxf.jaxb.JAXBDataBinding.initialize(JAXBDataBinding.java:2
>>> 41)
>>> at
>>> org.apache.cxf.service.factory.ReflectionServiceFactoryBean.buildServ
>>> iceFromClass(ReflectionServiceFactoryBean.java:340)
>>> at
>>> org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean.buildServiceFrom
>>> Class(JaxWsServiceFactoryBean.java:512)
>>> at
>>> org.apache.cxf.service.factory.ReflectionServiceFactoryBean.initializ
>>> eServiceModel(ReflectionServiceFactoryBean.java:389)
>>> at
>>> org.apache.cxf.service.factory.ReflectionServiceFactoryBean.create(Re
>>> flectionServiceFactoryBean.java:177)
>>> at
>>> org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean.create(JaxWsServ
>>> iceFactoryBean.java:163)
>>> at
>>> org.apache.cxf.frontend.AbstractWSDLBasedEndpointFactory.createEndpoi
>>> nt(AbstractWSDLBasedEndpointFactory.java:77)
>>> at
>>> org.apache.cxf.frontend.ServerFactoryBean.create(ServerFactoryBean.ja
>>> va:113)
>>> at
>>> org.apache.cxf.jaxws.JaxWsServerFactoryBean.create(JaxWsServerFactory
>>> Bean.java:147)
>>> at
>>> org.apache.cxf.jaxws.EndpointImpl.getServer(EndpointImpl.java:310)
>>> at
>>> org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:240)
>>> at
>>> org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:191)
>>> at
>>> org.apache.servicemix.cxfse.CxfSeEndpoint.start(CxfSeEndpoint.java:21
>>> 5)
>>> at
>>> org.apache.servicemix.common.endpoints.SimpleEndpoint.activate(Simple
>>> Endpoint.java:55)
>>> at
>>> org.apache.servicemix.common.ServiceUnit.start(ServiceUnit.java:53)
>>> at
>>> org.apache.servicemix.common.BaseServiceUnitManager.start(BaseService
>>> UnitManager.java:151)
>>> at
>>> org.apache.servicemix.jbi.framework.ServiceUnitLifeCycle.start(Servic
>>> eUnitLifeCycle.java:103)
>>> at
>>> org.apache.servicemix.jbi.framework.ServiceAssemblyLifeCycle.start(Se
>>> rviceAssemblyLifeCycle.java:132)
>>> at
>>> org.apache.servicemix.jbi.framework.DeploymentService.start(Deploymen
>>> tService.java:378)
>>> at
>>> org.apache.servicemix.jbi.framework.AutoDeploymentService.updateServi
>>> ceAssembly(AutoDeploymentService.java:355)
>>> at
>>> org.apache.servicemix.jbi.framework.AutoDeploymentService.updateArchi
>>> ve(AutoDeploymentService.java:256)
>>> at
>>> org.apache.servicemix.jbi.framework.AutoDeploymentService.monitorDire
>>> ctory(AutoDeploymentService.java:658)
>>> at
>>> org.apache.servicemix.jbi.framework.AutoDeploymentService.access$800(
>>> AutoDeploymentService.java:62)
>>> at
>>> org.apache.servicemix.jbi.framework.AutoDeploymentService$1.run(AutoD
>>> eploymentService.java:622)
>>> at java.util.TimerThread.mainLoop(Timer.java:512)
>>> at java.util.TimerThread.run(Timer.java:462)
>>>
>>>
>>>
>>>
>>
>>
>
>
Re: JAXB jars missing in servicemix-3.3-SNAPSHOT?
Posted by Will Gomes <wg...@umd.edu>.
Complete rebuild includes the correct jaxb for cxf components. But I still
get linkage error for JAXB api when deploying:
wsdl-first-cxf-sa-3.3-SNAPSHOT.zip.
In case it helps others out, I stopped getting the JAXB error when I
switched to use Java 1.6.0_05 which includes the 2.1 api. Before, I was
using Java 1.6_03 endorsed with JAXB 2.1 api jars. But it turns out the
servicemix startup script reset the endorsed directory to
'%SERVICEMIX_HOME%\lib\endorsed', so my endorsed jars never got picked up
causing the linkage error.
--
View this message in context: http://www.nabble.com/JAXB-jars-missing-in-servicemix-3.3-SNAPSHOT--tp15978159p16573550.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: JAXB jars missing in servicemix-3.3-SNAPSHOT?
Posted by Will Gomes <wg...@umd.edu>.
Complete rebuild includes the correct jaxb for cxf components. But I still
get linkage error for JAXB api when deploying:
wsdl-first-cxf-sa-3.3-SNAPSHOT.zip.
Freeman Fang wrote:
>
> Hi,
>
> This problem which is caused by different jaxb version conflict should
> already be resolved.
> By my test the servicemix-cxf-se-3.3-SNAPSHOT-installer.zip contain the
> proper jaxb-impl version, 2.1.4.
> Would you please try to make a clean build from root folder of your
> servicemix, not only build the cxf component.
>
> Regards
>
> Freeman
>
> Will Gomes wrote:
>> Freeman Fang wrote:
>>
>>> Hi Ingo,
>>>
>>> Please unzip servicemix-cxf-se-3.3-SNAPSHOT-installer.zip in the kit you
>>> generated and check if there is a jaxb-impl-2.1.4.jar inside, this jar
>>> contain com/sun/xml/bind/marshaller/NamespacePrefixMapper class.
>>> It's there by my test.
>>>
>>> Regards
>>>
>>>
>>>
>>
>> I'm having the same problem. The jaxb-impl-2.1.4.jar is missing from
>> both
>> servicemix-cxf-se-3.3-SNAPSHOT-installer.zip and
>> servicemix-cxf-bc-3.3-SNAPSHOT-installer.zip.
>> I added these to the zip files and modified the respective jbi.xml files.
>> Now when deploying i get the following error:
>>
>> INFO: Creating Service
>> {http://servicemix.apache.org/samples/wsdl-first}PersonSe
>> rvice from class org.apache.servicemix.samples.wsdl_first.Person
>> Exception in thread "Timer-3" java.lang.LinkageError: JAXB 2.0 API is
>> being
>> load
>> ed from the bootstrap classloader, but this RI (from
>> jar:file:/C:/apache-service
>> mix-3.3-20070312-SNAPSHOT/data/smx/components/servicemix-cxf-se/version_1/lib/ja
>> xb-impl-2.1.4.jar!/com/sun/xml/bind/v2/model/impl/ModelBuilder.class)
>> needs
>> 2.1
>> API. Use the endorsed directory mechanism to place jaxb-api.jar in the
>> bootstrap
>> classloader. (See http://java.sun.com/j2se/1.5.0/docs/guide/standards/)
>> at
>> com.sun.xml.bind.v2.model.impl.ModelBuilder.<clinit>(ModelBuilder.jav
>> a:172)
>> at
>> com.sun.xml.bind.v2.runtime.JAXBContextImpl.getTypeInfoSet(JAXBContex
>> tImpl.java:422)
>> at
>> com.sun.xml.bind.v2.runtime.JAXBContextImpl.<init>(JAXBContextImpl.ja
>> va:286)
>> at
>> com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:
>> 139)
>> at
>> com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:
>> 117)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
>> java:39)
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
>> sorImpl.java:25)
>> at java.lang.reflect.Method.invoke(Method.java:597)
>> at
>> javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:210)
>> at javax.xml.bind.ContextFinder.find(ContextFinder.java:368)
>> at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:574)
>> at
>> org.apache.cxf.jaxb.JAXBDataBinding.createJAXBContext(JAXBDataBinding
>> .java:460)
>> at
>> org.apache.cxf.jaxb.JAXBDataBinding.initialize(JAXBDataBinding.java:2
>> 41)
>> at
>> org.apache.cxf.service.factory.ReflectionServiceFactoryBean.buildServ
>> iceFromClass(ReflectionServiceFactoryBean.java:340)
>> at
>> org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean.buildServiceFrom
>> Class(JaxWsServiceFactoryBean.java:512)
>> at
>> org.apache.cxf.service.factory.ReflectionServiceFactoryBean.initializ
>> eServiceModel(ReflectionServiceFactoryBean.java:389)
>> at
>> org.apache.cxf.service.factory.ReflectionServiceFactoryBean.create(Re
>> flectionServiceFactoryBean.java:177)
>> at
>> org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean.create(JaxWsServ
>> iceFactoryBean.java:163)
>> at
>> org.apache.cxf.frontend.AbstractWSDLBasedEndpointFactory.createEndpoi
>> nt(AbstractWSDLBasedEndpointFactory.java:77)
>> at
>> org.apache.cxf.frontend.ServerFactoryBean.create(ServerFactoryBean.ja
>> va:113)
>> at
>> org.apache.cxf.jaxws.JaxWsServerFactoryBean.create(JaxWsServerFactory
>> Bean.java:147)
>> at
>> org.apache.cxf.jaxws.EndpointImpl.getServer(EndpointImpl.java:310)
>> at
>> org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:240)
>> at
>> org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:191)
>> at
>> org.apache.servicemix.cxfse.CxfSeEndpoint.start(CxfSeEndpoint.java:21
>> 5)
>> at
>> org.apache.servicemix.common.endpoints.SimpleEndpoint.activate(Simple
>> Endpoint.java:55)
>> at
>> org.apache.servicemix.common.ServiceUnit.start(ServiceUnit.java:53)
>> at
>> org.apache.servicemix.common.BaseServiceUnitManager.start(BaseService
>> UnitManager.java:151)
>> at
>> org.apache.servicemix.jbi.framework.ServiceUnitLifeCycle.start(Servic
>> eUnitLifeCycle.java:103)
>> at
>> org.apache.servicemix.jbi.framework.ServiceAssemblyLifeCycle.start(Se
>> rviceAssemblyLifeCycle.java:132)
>> at
>> org.apache.servicemix.jbi.framework.DeploymentService.start(Deploymen
>> tService.java:378)
>> at
>> org.apache.servicemix.jbi.framework.AutoDeploymentService.updateServi
>> ceAssembly(AutoDeploymentService.java:355)
>> at
>> org.apache.servicemix.jbi.framework.AutoDeploymentService.updateArchi
>> ve(AutoDeploymentService.java:256)
>> at
>> org.apache.servicemix.jbi.framework.AutoDeploymentService.monitorDire
>> ctory(AutoDeploymentService.java:658)
>> at
>> org.apache.servicemix.jbi.framework.AutoDeploymentService.access$800(
>> AutoDeploymentService.java:62)
>> at
>> org.apache.servicemix.jbi.framework.AutoDeploymentService$1.run(AutoD
>> eploymentService.java:622)
>> at java.util.TimerThread.mainLoop(Timer.java:512)
>> at java.util.TimerThread.run(Timer.java:462)
>>
>>
>>
>
>
>
--
View this message in context: http://www.nabble.com/JAXB-jars-missing-in-servicemix-3.3-SNAPSHOT--tp15978159s12049p16048157.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: JAXB jars missing in servicemix-3.3-SNAPSHOT?
Posted by Freeman Fang <fr...@gmail.com>.
Hi,
This problem which is caused by different jaxb version conflict should
already be resolved.
By my test the servicemix-cxf-se-3.3-SNAPSHOT-installer.zip contain the
proper jaxb-impl version, 2.1.4.
Would you please try to make a clean build from root folder of your
servicemix, not only build the cxf component.
Regards
Freeman
Will Gomes wrote:
> Freeman Fang wrote:
>
>> Hi Ingo,
>>
>> Please unzip servicemix-cxf-se-3.3-SNAPSHOT-installer.zip in the kit you
>> generated and check if there is a jaxb-impl-2.1.4.jar inside, this jar
>> contain com/sun/xml/bind/marshaller/NamespacePrefixMapper class.
>> It's there by my test.
>>
>> Regards
>>
>>
>>
>
> I'm having the same problem. The jaxb-impl-2.1.4.jar is missing from both
> servicemix-cxf-se-3.3-SNAPSHOT-installer.zip and
> servicemix-cxf-bc-3.3-SNAPSHOT-installer.zip.
> I added these to the zip files and modified the respective jbi.xml files.
> Now when deploying i get the following error:
>
> INFO: Creating Service
> {http://servicemix.apache.org/samples/wsdl-first}PersonSe
> rvice from class org.apache.servicemix.samples.wsdl_first.Person
> Exception in thread "Timer-3" java.lang.LinkageError: JAXB 2.0 API is being
> load
> ed from the bootstrap classloader, but this RI (from
> jar:file:/C:/apache-service
> mix-3.3-20070312-SNAPSHOT/data/smx/components/servicemix-cxf-se/version_1/lib/ja
> xb-impl-2.1.4.jar!/com/sun/xml/bind/v2/model/impl/ModelBuilder.class) needs
> 2.1
> API. Use the endorsed directory mechanism to place jaxb-api.jar in the
> bootstrap
> classloader. (See http://java.sun.com/j2se/1.5.0/docs/guide/standards/)
> at
> com.sun.xml.bind.v2.model.impl.ModelBuilder.<clinit>(ModelBuilder.jav
> a:172)
> at
> com.sun.xml.bind.v2.runtime.JAXBContextImpl.getTypeInfoSet(JAXBContex
> tImpl.java:422)
> at
> com.sun.xml.bind.v2.runtime.JAXBContextImpl.<init>(JAXBContextImpl.ja
> va:286)
> at
> com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:
> 139)
> at
> com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:
> 117)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> sorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:210)
> at javax.xml.bind.ContextFinder.find(ContextFinder.java:368)
> at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:574)
> at
> org.apache.cxf.jaxb.JAXBDataBinding.createJAXBContext(JAXBDataBinding
> .java:460)
> at
> org.apache.cxf.jaxb.JAXBDataBinding.initialize(JAXBDataBinding.java:2
> 41)
> at
> org.apache.cxf.service.factory.ReflectionServiceFactoryBean.buildServ
> iceFromClass(ReflectionServiceFactoryBean.java:340)
> at
> org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean.buildServiceFrom
> Class(JaxWsServiceFactoryBean.java:512)
> at
> org.apache.cxf.service.factory.ReflectionServiceFactoryBean.initializ
> eServiceModel(ReflectionServiceFactoryBean.java:389)
> at
> org.apache.cxf.service.factory.ReflectionServiceFactoryBean.create(Re
> flectionServiceFactoryBean.java:177)
> at
> org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean.create(JaxWsServ
> iceFactoryBean.java:163)
> at
> org.apache.cxf.frontend.AbstractWSDLBasedEndpointFactory.createEndpoi
> nt(AbstractWSDLBasedEndpointFactory.java:77)
> at
> org.apache.cxf.frontend.ServerFactoryBean.create(ServerFactoryBean.ja
> va:113)
> at
> org.apache.cxf.jaxws.JaxWsServerFactoryBean.create(JaxWsServerFactory
> Bean.java:147)
> at
> org.apache.cxf.jaxws.EndpointImpl.getServer(EndpointImpl.java:310)
> at
> org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:240)
> at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:191)
> at
> org.apache.servicemix.cxfse.CxfSeEndpoint.start(CxfSeEndpoint.java:21
> 5)
> at
> org.apache.servicemix.common.endpoints.SimpleEndpoint.activate(Simple
> Endpoint.java:55)
> at
> org.apache.servicemix.common.ServiceUnit.start(ServiceUnit.java:53)
> at
> org.apache.servicemix.common.BaseServiceUnitManager.start(BaseService
> UnitManager.java:151)
> at
> org.apache.servicemix.jbi.framework.ServiceUnitLifeCycle.start(Servic
> eUnitLifeCycle.java:103)
> at
> org.apache.servicemix.jbi.framework.ServiceAssemblyLifeCycle.start(Se
> rviceAssemblyLifeCycle.java:132)
> at
> org.apache.servicemix.jbi.framework.DeploymentService.start(Deploymen
> tService.java:378)
> at
> org.apache.servicemix.jbi.framework.AutoDeploymentService.updateServi
> ceAssembly(AutoDeploymentService.java:355)
> at
> org.apache.servicemix.jbi.framework.AutoDeploymentService.updateArchi
> ve(AutoDeploymentService.java:256)
> at
> org.apache.servicemix.jbi.framework.AutoDeploymentService.monitorDire
> ctory(AutoDeploymentService.java:658)
> at
> org.apache.servicemix.jbi.framework.AutoDeploymentService.access$800(
> AutoDeploymentService.java:62)
> at
> org.apache.servicemix.jbi.framework.AutoDeploymentService$1.run(AutoD
> eploymentService.java:622)
> at java.util.TimerThread.mainLoop(Timer.java:512)
> at java.util.TimerThread.run(Timer.java:462)
>
>
>
Re: JAXB jars missing in servicemix-3.3-SNAPSHOT?
Posted by Will Gomes <wg...@umd.edu>.
Freeman Fang wrote:
>
> Hi Ingo,
>
> Please unzip servicemix-cxf-se-3.3-SNAPSHOT-installer.zip in the kit you
> generated and check if there is a jaxb-impl-2.1.4.jar inside, this jar
> contain com/sun/xml/bind/marshaller/NamespacePrefixMapper class.
> It's there by my test.
>
> Regards
>
>
I'm having the same problem. The jaxb-impl-2.1.4.jar is missing from both
servicemix-cxf-se-3.3-SNAPSHOT-installer.zip and
servicemix-cxf-bc-3.3-SNAPSHOT-installer.zip.
I added these to the zip files and modified the respective jbi.xml files.
Now when deploying i get the following error:
INFO: Creating Service
{http://servicemix.apache.org/samples/wsdl-first}PersonSe
rvice from class org.apache.servicemix.samples.wsdl_first.Person
Exception in thread "Timer-3" java.lang.LinkageError: JAXB 2.0 API is being
load
ed from the bootstrap classloader, but this RI (from
jar:file:/C:/apache-service
mix-3.3-20070312-SNAPSHOT/data/smx/components/servicemix-cxf-se/version_1/lib/ja
xb-impl-2.1.4.jar!/com/sun/xml/bind/v2/model/impl/ModelBuilder.class) needs
2.1
API. Use the endorsed directory mechanism to place jaxb-api.jar in the
bootstrap
classloader. (See http://java.sun.com/j2se/1.5.0/docs/guide/standards/)
at
com.sun.xml.bind.v2.model.impl.ModelBuilder.<clinit>(ModelBuilder.jav
a:172)
at
com.sun.xml.bind.v2.runtime.JAXBContextImpl.getTypeInfoSet(JAXBContex
tImpl.java:422)
at
com.sun.xml.bind.v2.runtime.JAXBContextImpl.<init>(JAXBContextImpl.ja
va:286)
at
com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:
139)
at
com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:
117)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:210)
at javax.xml.bind.ContextFinder.find(ContextFinder.java:368)
at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:574)
at
org.apache.cxf.jaxb.JAXBDataBinding.createJAXBContext(JAXBDataBinding
.java:460)
at
org.apache.cxf.jaxb.JAXBDataBinding.initialize(JAXBDataBinding.java:2
41)
at
org.apache.cxf.service.factory.ReflectionServiceFactoryBean.buildServ
iceFromClass(ReflectionServiceFactoryBean.java:340)
at
org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean.buildServiceFrom
Class(JaxWsServiceFactoryBean.java:512)
at
org.apache.cxf.service.factory.ReflectionServiceFactoryBean.initializ
eServiceModel(ReflectionServiceFactoryBean.java:389)
at
org.apache.cxf.service.factory.ReflectionServiceFactoryBean.create(Re
flectionServiceFactoryBean.java:177)
at
org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean.create(JaxWsServ
iceFactoryBean.java:163)
at
org.apache.cxf.frontend.AbstractWSDLBasedEndpointFactory.createEndpoi
nt(AbstractWSDLBasedEndpointFactory.java:77)
at
org.apache.cxf.frontend.ServerFactoryBean.create(ServerFactoryBean.ja
va:113)
at
org.apache.cxf.jaxws.JaxWsServerFactoryBean.create(JaxWsServerFactory
Bean.java:147)
at
org.apache.cxf.jaxws.EndpointImpl.getServer(EndpointImpl.java:310)
at
org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:240)
at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:191)
at
org.apache.servicemix.cxfse.CxfSeEndpoint.start(CxfSeEndpoint.java:21
5)
at
org.apache.servicemix.common.endpoints.SimpleEndpoint.activate(Simple
Endpoint.java:55)
at
org.apache.servicemix.common.ServiceUnit.start(ServiceUnit.java:53)
at
org.apache.servicemix.common.BaseServiceUnitManager.start(BaseService
UnitManager.java:151)
at
org.apache.servicemix.jbi.framework.ServiceUnitLifeCycle.start(Servic
eUnitLifeCycle.java:103)
at
org.apache.servicemix.jbi.framework.ServiceAssemblyLifeCycle.start(Se
rviceAssemblyLifeCycle.java:132)
at
org.apache.servicemix.jbi.framework.DeploymentService.start(Deploymen
tService.java:378)
at
org.apache.servicemix.jbi.framework.AutoDeploymentService.updateServi
ceAssembly(AutoDeploymentService.java:355)
at
org.apache.servicemix.jbi.framework.AutoDeploymentService.updateArchi
ve(AutoDeploymentService.java:256)
at
org.apache.servicemix.jbi.framework.AutoDeploymentService.monitorDire
ctory(AutoDeploymentService.java:658)
at
org.apache.servicemix.jbi.framework.AutoDeploymentService.access$800(
AutoDeploymentService.java:62)
at
org.apache.servicemix.jbi.framework.AutoDeploymentService$1.run(AutoD
eploymentService.java:622)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
--
View this message in context: http://www.nabble.com/JAXB-jars-missing-in-servicemix-3.3-SNAPSHOT--tp15978159s12049p16029626.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: JAXB jars missing in servicemix-3.3-SNAPSHOT?
Posted by Freeman Fang <fr...@gmail.com>.
Hi Ingo,
Please unzip servicemix-cxf-se-3.3-SNAPSHOT-installer.zip in the kit you
generated and check if there is a jaxb-impl-2.1.4.jar inside, this jar
contain com/sun/xml/bind/marshaller/NamespacePrefixMapper class.
It's there by my test.
Regards
Freeman
Ingo Mittrup wrote:
> Hi!
>
> I've built servicemix-3.3-SNAPSHOT following the instructions on the
> SMX website. When i deploy a cxf-se service unit (correctly running
> under SMX 3.2.1 and 3.2.2) into SMX 3.3-SNAPSHOT, i get an expection
> (see exception stack trace below).
>
> For building SMX 3.3-SNAPSHOT, i ran:
> mvn -Dmaven.test.skip=true -Pstep1 install
> mvn -Dmaven.test.skip=true -Pstep2 install
>
> Did i miss something?
>
> Best regards
> Ingo
>
>
> = = = = = = = = = = = = = =
> Exception in thread "Timer-4" java.lang.NoClassDefFoundError:
> com/sun/xml/bind/m
> arshaller/NamespacePrefixMapper
> at
> org.apache.cxf.service.factory.ReflectionServiceFactoryBean.createDef
> aultDataBinding(ReflectionServiceFactoryBean.java:170)
> at
> org.apache.cxf.service.factory.AbstractServiceFactoryBean.getDataBind
> ing(AbstractServiceFactoryBean.java:56)
> at
> org.apache.cxf.frontend.ServerFactoryBean.applyExtraClass(ServerFacto
> ryBean.java:196)
> at
> org.apache.cxf.frontend.ServerFactoryBean.create(ServerFactoryBean.ja
> va:103)
> at
> org.apache.cxf.jaxws.JaxWsServerFactoryBean.create(JaxWsServerFactory
> Bean.java:147)
> at
> org.apache.cxf.jaxws.EndpointImpl.getServer(EndpointImpl.java:310)
> at
> org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:240)
> at
> org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:191)
> at
> org.apache.servicemix.cxfse.CxfSeEndpoint.start(CxfSeEndpoint.java:21
> 1)
> at
> org.apache.servicemix.common.endpoints.SimpleEndpoint.activate(Simple
> Endpoint.java:55)
> at
> org.apache.servicemix.common.ServiceUnit.start(ServiceUnit.java:53)
> at
> org.apache.servicemix.common.BaseServiceUnitManager.start(BaseService
> UnitManager.java:151)
> at
> org.apache.servicemix.jbi.framework.ServiceUnitLifeCycle.start(Servic
> eUnitLifeCycle.java:103)
> at
> org.apache.servicemix.jbi.framework.ServiceAssemblyLifeCycle.start(Se
> rviceAssemblyLifeCycle.java:132)
> at
> org.apache.servicemix.jbi.framework.DeploymentService.start(Deploymen
> tService.java:378)
> at
> org.apache.servicemix.jbi.framework.AutoDeploymentService.updateServi
> ceAssembly(AutoDeploymentService.java:355)
> at
> org.apache.servicemix.jbi.framework.AutoDeploymentService.updateArchi
> ve(AutoDeploymentService.java:256)
> at
> org.apache.servicemix.jbi.framework.AutoDeploymentService.monitorDire
> ctory(AutoDeploymentService.java:658)
> at
> org.apache.servicemix.jbi.framework.AutoDeploymentService.access$800(
> AutoDeploymentService.java:62)
> at
> org.apache.servicemix.jbi.framework.AutoDeploymentService$1.run(AutoD
> eploymentService.java:622)
> at java.util.TimerThread.mainLoop(Timer.java:512)
> at java.util.TimerThread.run(Timer.java:462)
>
>