You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@servicemix.apache.org by Cybexion <cy...@email.de> on 2008/06/30 12:44:48 UTC
Re: JAXB jars missing in servicemix-3.3-SNAPSHOT?
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 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
>>>
>>>
>>>
>
>