[jbossws-dev] Why Hudson build fail for Native-Core-AS-5.0.0

[Richard Opalka]

Yes, it makes perfect sence.
According to 
http://fisheye.jboss.com/browse/JBossAS/trunk/server/src/etc/conf/default/bootstrap-beans.xml?r1=66628&r2=68825
where AOPClassLoaderScopingPolicy changed
from org.jboss.aop.asintegration.jboss4.RepositoryClassLoaderScopingPolicy
to org.jboss.aop.asintegration.jboss5.VFSClassLoaderScopingPolicy
This might be the problem.

Richard

Heiko Braun wrote:
> It's probably a scoping issue.
> The stax API uses a service loader to instantiate concrete
> implementations. When the API is loaded from somewhere higher in the
> classloader hierarchy the containing service loader cannot see the
> implementation further down. it uses parent delegation.
>
> /Heiko
>
>
> On Fri, 2008-01-11 at 10:49 +0100, Richard Opalka wrote:
>   
>> It's really strange because wstx.jar is in jbossws.sar module :-(
>> I didn't do any progress on that.
>>
>> Thomas, you reassigned JBWS-1930 to you, thanks for that ;-)
>> Could you take a look to this problem too, please?
>> I'm not able to solve it :-(
>>
>> Richard
>>
>> Richard Opalka wrote:
>>     
>>> Tests that fail are related to our policy implementation. This is the 
>>> exception on server side:
>>>
>>> Caused by: javax.xml.stream.FactoryConfigurationError: Provider 
>>> com.bea.xml.stream.XMLOutputFactoryBase not found
>>>        at 
>>> javax.xml.stream.FactoryFinder.newInstance(FactoryFinder.java:72)
>>>        at javax.xml.stream.FactoryFinder.find(FactoryFinder.java:176)
>>>        at javax.xml.stream.FactoryFinder.find(FactoryFinder.java:92)
>>>        at 
>>> javax.xml.stream.XMLOutputFactory.newInstance(XMLOutputFactory.java:98)
>>>        at 
>>> org.apache.ws.policy.util.StAXPolicyWriter.writePolicy(StAXPolicyWriter.java:54) 
>>>
>>>        at 
>>> org.jboss.ws.tools.wsdl.WSDLGenerator.addPolicyDefinition(WSDLGenerator.java:146) 
>>>
>>>        at 
>>> org.jboss.ws.tools.wsdl.WSDLGenerator.processEndpoint(WSDLGenerator.java:134) 
>>>
>>>        at 
>>> org.jboss.ws.tools.wsdl.WSDLGenerator.processService(WSDLGenerator.java:404) 
>>>
>>>        at 
>>> org.jboss.ws.tools.wsdl.WSDLGenerator.generate(WSDLGenerator.java:452)
>>>        at 
>>> org.jboss.ws.metadata.builder.jaxws.JAXWSWebServiceMetaDataBuilder.processOrGenerateWSDL(JAXWSWebServiceMetaDataBuilder.java:381) 
>>>
>>>        at 
>>> org.jboss.ws.metadata.builder.jaxws.JAXWSWebServiceMetaDataBuilder.buildWebServiceMetaData(JAXWSWebServiceMetaDataBuilder.java:158) 
>>>
>>>        at 
>>> org.jboss.ws.metadata.builder.jaxws.JAXWSServerMetaDataBuilder.setupProviderOrWebService(JAXWSServerMetaDataBuilder.java:52) 
>>>
>>>        at 
>>> org.jboss.ws.metadata.builder.jaxws.JAXWSMetaDataBuilderJSE.buildMetaData(JAXWSMetaDataBuilderJSE.java:63) 
>>>
>>>        at 
>>> org.jboss.wsf.stack.jbws.UnifiedMetaDataDeploymentAspect.create(UnifiedMetaDataDeploymentAspect.java:66) 
>>>
>>>        at 
>>> org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:115) 
>>>
>>>        at 
>>> org.jboss.wsf.container.jboss50.ArchiveDeployerHook.deploy(ArchiveDeployerHook.java:95) 
>>>
>>>        at 
>>> org.jboss.wsf.container.jboss50.AbstractWebServiceDeployer.internalDeploy(AbstractWebServiceDeployer.java:63) 
>>>
>>>        at 
>>> org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50) 
>>>
>>>        at 
>>> org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:169) 
>>>
>>>        ... 62 more
>>>
>>> According to FactoryFinder mechanism it seems there's wstx.jar missing 
>>> on the classpath.
>>> This jar defines javax.xml.stream.XMLOutputFactory service in its 
>>> META-INF/services directory.
>>> However because it is not on the classpath, stax-api.jar tries to load 
>>> the handcoded
>>> com.bea.xml.stream.XMLOutputFactoryBase provider instead.
>>>   I'll take care of that. Maybe solving of
>>>
>>> http://jira.jboss.org/jira/browse/JBWS-1930
>>>
>>> will solve the issue.
>>>
>>> Richard
>>>
>>>       
>>>> This commit belongs to: http://jira.jboss.org/jira/browse/JBAS-5119
>>>>         
>>>>> I reviewed all yesterday changes and discovered that the following 
>>>>> SVN commit
>>>>>
>>>>> http://fisheye.jboss.com/browse/JBossAS/trunk/server/src/etc/conf/default/bootstrap-beans.xml?r1=66628&r2=68825 
>>>>>
>>>>>
>>>>> breaks our test suite.
>>>>>
>>>>>           
>>>>         
>>> _______________________________________________
>>> jbossws-dev mailing list
>>> jbossws-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jbossws-dev
>>>       
>>     
>
>   


-- 
B.Sc. Richard Opalka
Senior Software Engineer
JBoss, a division of Red Hat

Mobile: +420 731 186 942
Mail: ropalka at redhat.com