You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@servicemix.apache.org by inter <ga...@126.com> on 2009/07/03 10:12:45 UTC

problems after upgrading cxf-bc and se

I am using smx3.3.
The version of it's default cxf-bc is 2008.01-SNAPSHOT,
i upgraded it to 2009.02-SNAPSHOT.

After that,I deployed the cxf-wsdl-first example to it,
i got flolowed errors:

Exception in thread "Timer-2" java.lang.NoSuchMethodError:
org.apache.ws.commons.schema.XmlSchema.getSchemaDocument()Lorg/w3c/dom/Document;
	at org.apache.cxf.service.model.SchemaInfo.getElement(SchemaInfo.java:109)
	at
org.apache.cxf.wsdl11.ServiceWSDLBuilder.buildTypes(ServiceWSDLBuilder.java:267)
	at
org.apache.cxf.wsdl11.ServiceWSDLBuilder.build(ServiceWSDLBuilder.java:188)
	at
org.apache.cxf.wsdl11.ServiceWSDLBuilder.build(ServiceWSDLBuilder.java:148)
	at org.apache.servicemix.cxfse.CxfSeEndpoint.start(CxfSeEndpoint.java:436)
	at
org.apache.servicemix.common.DefaultServiceUnit.start(DefaultServiceUnit.java:78)
	at
org.apache.servicemix.common.BaseServiceUnitManager.start(BaseServiceUnitManager.java:155)
	at
org.apache.servicemix.jbi.framework.ServiceUnitLifeCycle.start(ServiceUnitLifeCycle.java:103)
	at
org.apache.servicemix.jbi.framework.ServiceAssemblyLifeCycle.start(ServiceAssemblyLifeCycle.java:132)
	at
org.apache.servicemix.jbi.framework.DeploymentService.start(DeploymentService.java:378)
	at
org.apache.servicemix.jbi.framework.AutoDeploymentService.updateServiceAssembly(AutoDeploymentService.java:355)
	at
org.apache.servicemix.jbi.framework.AutoDeploymentService.updateArchive(AutoDeploymentService.java:256)
	at
org.apache.servicemix.jbi.framework.AutoDeploymentService.monitorDirectory(AutoDeploymentService.java:667)
	at
org.apache.servicemix.jbi.framework.AutoDeploymentService.access$2(AutoDeploymentService.java:643)
	at
org.apache.servicemix.jbi.framework.AutoDeploymentService$1.run(AutoDeploymentService.java:631)
	at java.util.TimerThread.mainLoop(Timer.java:512)
	at java.util.TimerThread.run(Timer.java:462)

Should I do anything more after upgrading cxf-bc and se?
-- 
View this message in context: http://www.nabble.com/problems-after-upgrading-cxf-bc-and-se-tp24319322p24319322.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.


Re: problems after upgrading cxf-bc and se

Posted by inter <ga...@126.com>.
Thank you ,Freeman!

I upgraded cxf-bc just to enable it's message audit.

I found  that  in smx 3.3.1, version of cxf-bc has already been 2009.01.

I think it will work.i will turn to 3.3.1.

Thank you again!!



Freeman Fang wrote:
> 
> Hi,
> 
> Can you explain how did you do this upgrade? Do you remove SMX_HOME  
> folder after upgrading?
> The default cxf bc version for smx 3.3 is 2008.01 but not 2008.01- 
> SNAPSHOT.
> Is it possible for you to use the latest released Smx 3.3.1?
> Freeman
> 
> On 2009-7-3, at 下午4:12, inter wrote:
> 
>>
>> I am using smx3.3.
>> The version of it's default cxf-bc is 2008.01-SNAPSHOT,
>> i upgraded it to 2009.02-SNAPSHOT.
>>
>> After that,I deployed the cxf-wsdl-first example to it,
>> i got flolowed errors:
>>
>> Exception in thread "Timer-2" java.lang.NoSuchMethodError:
>> org.apache.ws.commons.schema.XmlSchema.getSchemaDocument()Lorg/w3c/ 
>> dom/Document;
>> 	at  
>> org.apache.cxf.service.model.SchemaInfo.getElement(SchemaInfo.java: 
>> 109)
>> 	at
>> org 
>> .apache 
>> .cxf.wsdl11.ServiceWSDLBuilder.buildTypes(ServiceWSDLBuilder.java:267)
>> 	at
>> org 
>> .apache.cxf.wsdl11.ServiceWSDLBuilder.build(ServiceWSDLBuilder.java: 
>> 188)
>> 	at
>> org 
>> .apache.cxf.wsdl11.ServiceWSDLBuilder.build(ServiceWSDLBuilder.java: 
>> 148)
>> 	at  
>> org.apache.servicemix.cxfse.CxfSeEndpoint.start(CxfSeEndpoint.java: 
>> 436)
>> 	at
>> org 
>> .apache 
>> .servicemix.common.DefaultServiceUnit.start(DefaultServiceUnit.java: 
>> 78)
>> 	at
>> org 
>> .apache 
>> .servicemix 
>> .common.BaseServiceUnitManager.start(BaseServiceUnitManager.java:155)
>> 	at
>> org 
>> .apache 
>> .servicemix 
>> .jbi.framework.ServiceUnitLifeCycle.start(ServiceUnitLifeCycle.java: 
>> 103)
>> 	at
>> org 
>> .apache 
>> .servicemix 
>> .jbi 
>> .framework 
>> .ServiceAssemblyLifeCycle.start(ServiceAssemblyLifeCycle.java:132)
>> 	at
>> org 
>> .apache 
>> .servicemix 
>> .jbi.framework.DeploymentService.start(DeploymentService.java:378)
>> 	at
>> org 
>> .apache 
>> .servicemix 
>> .jbi 
>> .framework 
>> .AutoDeploymentService 
>> .updateServiceAssembly(AutoDeploymentService.java:355)
>> 	at
>> org 
>> .apache 
>> .servicemix 
>> .jbi 
>> .framework 
>> .AutoDeploymentService.updateArchive(AutoDeploymentService.java:256)
>> 	at
>> org 
>> .apache 
>> .servicemix 
>> .jbi 
>> .framework 
>> .AutoDeploymentService.monitorDirectory(AutoDeploymentService.java: 
>> 667)
>> 	at
>> org.apache.servicemix.jbi.framework.AutoDeploymentService.access 
>> $2(AutoDeploymentService.java:643)
>> 	at
>> org.apache.servicemix.jbi.framework.AutoDeploymentService 
>> $1.run(AutoDeploymentService.java:631)
>> 	at java.util.TimerThread.mainLoop(Timer.java:512)
>> 	at java.util.TimerThread.run(Timer.java:462)
>>
>> Should I do anything more after upgrading cxf-bc and se?
>> -- 
>> View this message in context:
>> http://www.nabble.com/problems-after-upgrading-cxf-bc-and-se-tp24319322p24319322.html
>> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>>
> 
> 
> -- 
> Freeman Fang
> ------------------------
> Open Source SOA: http://fusesource.com
> 
> 
> 

-- 
View this message in context: http://www.nabble.com/problems-after-upgrading-cxf-bc-and-se-tp24319322p24319593.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.


Re: problems after upgrading cxf-bc and se

Posted by Freeman Fang <fr...@gmail.com>.
Hi,

Can you explain how did you do this upgrade? Do you remove SMX_HOME  
folder after upgrading?
The default cxf bc version for smx 3.3 is 2008.01 but not 2008.01- 
SNAPSHOT.
Is it possible for you to use the latest released Smx 3.3.1?
Freeman

On 2009-7-3, at 下午4:12, inter wrote:

>
> I am using smx3.3.
> The version of it's default cxf-bc is 2008.01-SNAPSHOT,
> i upgraded it to 2009.02-SNAPSHOT.
>
> After that,I deployed the cxf-wsdl-first example to it,
> i got flolowed errors:
>
> Exception in thread "Timer-2" java.lang.NoSuchMethodError:
> org.apache.ws.commons.schema.XmlSchema.getSchemaDocument()Lorg/w3c/ 
> dom/Document;
> 	at  
> org.apache.cxf.service.model.SchemaInfo.getElement(SchemaInfo.java: 
> 109)
> 	at
> org 
> .apache 
> .cxf.wsdl11.ServiceWSDLBuilder.buildTypes(ServiceWSDLBuilder.java:267)
> 	at
> org 
> .apache.cxf.wsdl11.ServiceWSDLBuilder.build(ServiceWSDLBuilder.java: 
> 188)
> 	at
> org 
> .apache.cxf.wsdl11.ServiceWSDLBuilder.build(ServiceWSDLBuilder.java: 
> 148)
> 	at  
> org.apache.servicemix.cxfse.CxfSeEndpoint.start(CxfSeEndpoint.java: 
> 436)
> 	at
> org 
> .apache 
> .servicemix.common.DefaultServiceUnit.start(DefaultServiceUnit.java: 
> 78)
> 	at
> org 
> .apache 
> .servicemix 
> .common.BaseServiceUnitManager.start(BaseServiceUnitManager.java:155)
> 	at
> org 
> .apache 
> .servicemix 
> .jbi.framework.ServiceUnitLifeCycle.start(ServiceUnitLifeCycle.java: 
> 103)
> 	at
> org 
> .apache 
> .servicemix 
> .jbi 
> .framework 
> .ServiceAssemblyLifeCycle.start(ServiceAssemblyLifeCycle.java:132)
> 	at
> org 
> .apache 
> .servicemix 
> .jbi.framework.DeploymentService.start(DeploymentService.java:378)
> 	at
> org 
> .apache 
> .servicemix 
> .jbi 
> .framework 
> .AutoDeploymentService 
> .updateServiceAssembly(AutoDeploymentService.java:355)
> 	at
> org 
> .apache 
> .servicemix 
> .jbi 
> .framework 
> .AutoDeploymentService.updateArchive(AutoDeploymentService.java:256)
> 	at
> org 
> .apache 
> .servicemix 
> .jbi 
> .framework 
> .AutoDeploymentService.monitorDirectory(AutoDeploymentService.java: 
> 667)
> 	at
> org.apache.servicemix.jbi.framework.AutoDeploymentService.access 
> $2(AutoDeploymentService.java:643)
> 	at
> org.apache.servicemix.jbi.framework.AutoDeploymentService 
> $1.run(AutoDeploymentService.java:631)
> 	at java.util.TimerThread.mainLoop(Timer.java:512)
> 	at java.util.TimerThread.run(Timer.java:462)
>
> Should I do anything more after upgrading cxf-bc and se?
> -- 
> View this message in context: http://www.nabble.com/problems-after-upgrading-cxf-bc-and-se-tp24319322p24319322.html
> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>


-- 
Freeman Fang
------------------------
Open Source SOA: http://fusesource.com


Re: problems after upgrading cxf-bc and se

Posted by Freeman Fang <fr...@gmail.com>.
And the error actually comes from latest cxf component need higher  
XmlSchema version, so you also need upgrade your servicemix- 
shared*.zip at the same time.
Also the simple way is just use new released Smx3.3.1.
Freeman

On 2009-7-3, at 下午4:12, inter wrote:

>
> I am using smx3.3.
> The version of it's default cxf-bc is 2008.01-SNAPSHOT,
> i upgraded it to 2009.02-SNAPSHOT.
>
> After that,I deployed the cxf-wsdl-first example to it,
> i got flolowed errors:
>
> Exception in thread "Timer-2" java.lang.NoSuchMethodError:
> org.apache.ws.commons.schema.XmlSchema.getSchemaDocument()Lorg/w3c/ 
> dom/Document;
> 	at  
> org.apache.cxf.service.model.SchemaInfo.getElement(SchemaInfo.java: 
> 109)
> 	at
> org 
> .apache 
> .cxf.wsdl11.ServiceWSDLBuilder.buildTypes(ServiceWSDLBuilder.java:267)
> 	at
> org 
> .apache.cxf.wsdl11.ServiceWSDLBuilder.build(ServiceWSDLBuilder.java: 
> 188)
> 	at
> org 
> .apache.cxf.wsdl11.ServiceWSDLBuilder.build(ServiceWSDLBuilder.java: 
> 148)
> 	at  
> org.apache.servicemix.cxfse.CxfSeEndpoint.start(CxfSeEndpoint.java: 
> 436)
> 	at
> org 
> .apache 
> .servicemix.common.DefaultServiceUnit.start(DefaultServiceUnit.java: 
> 78)
> 	at
> org 
> .apache 
> .servicemix 
> .common.BaseServiceUnitManager.start(BaseServiceUnitManager.java:155)
> 	at
> org 
> .apache 
> .servicemix 
> .jbi.framework.ServiceUnitLifeCycle.start(ServiceUnitLifeCycle.java: 
> 103)
> 	at
> org 
> .apache 
> .servicemix 
> .jbi 
> .framework 
> .ServiceAssemblyLifeCycle.start(ServiceAssemblyLifeCycle.java:132)
> 	at
> org 
> .apache 
> .servicemix 
> .jbi.framework.DeploymentService.start(DeploymentService.java:378)
> 	at
> org 
> .apache 
> .servicemix 
> .jbi 
> .framework 
> .AutoDeploymentService 
> .updateServiceAssembly(AutoDeploymentService.java:355)
> 	at
> org 
> .apache 
> .servicemix 
> .jbi 
> .framework 
> .AutoDeploymentService.updateArchive(AutoDeploymentService.java:256)
> 	at
> org 
> .apache 
> .servicemix 
> .jbi 
> .framework 
> .AutoDeploymentService.monitorDirectory(AutoDeploymentService.java: 
> 667)
> 	at
> org.apache.servicemix.jbi.framework.AutoDeploymentService.access 
> $2(AutoDeploymentService.java:643)
> 	at
> org.apache.servicemix.jbi.framework.AutoDeploymentService 
> $1.run(AutoDeploymentService.java:631)
> 	at java.util.TimerThread.mainLoop(Timer.java:512)
> 	at java.util.TimerThread.run(Timer.java:462)
>
> Should I do anything more after upgrading cxf-bc and se?
> -- 
> View this message in context: http://www.nabble.com/problems-after-upgrading-cxf-bc-and-se-tp24319322p24319322.html
> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>


-- 
Freeman Fang
------------------------
Open Source SOA: http://fusesource.com