Nabble - cxf-user

Re: Bean as endpoint implementor

2009-12-22T18:17:59Z

Daniel - You are absolutely right. The most quick fix is to simply rename
endpoint bean.

<jaxws:endpoint id="myGlobManagerEndPoint"
implementor="#myGlobManager"
address="/myGlobManager"/>

It works great now! Thanks.

Bill

On Wed, Dec 23, 2009 at 1:51 AM, Daniel Kulp <dkulp@...> wrote:

>
>
> > <jaxws:endpoint id="myGlobManager"
> > implementor="#myGlobManager"
> > address="/myGlobManager"/>
>
> The implementor attribute is pointing at itself. The jaxws:endpoint bean
> is
> named myGlobManager and that's also the implementor? That's definitely
> not
> right.
>
> Most likely, you want something like:
>
> <bean id="myGlobManagerImpl" class="com.......MyGlobManagerImpl"/>
>
> <jaxws:endpoint id="myGlobManager"
> implementor="#myGlobManagerImpl"
> address="/myGlobManager"/>
>
> Due to your Autowired things, you may also need a TabManager bean and
> similar
> stuff defined in your beans.xml.
>
>
> Dan
>
>
>
>
>
> On Tue December 22 2009 12:35:08 pm Bill Li wrote:
> > Hi folks,
> >
> > I have a working project and would like to introduce web service
> > functionality here. I read around doc and successfully get a Foo service
> > running. My env is Spring 2.5, Jetty 6/Tomat 6. But when I try to export
> my
> > existing services, I continues hit spring exceptions. Let us come down to
> > code.
> >
> > Interface
> > ========
> > @WebService(name="myGlobManager", targetNamespace="http://cxf.apache.org
> ")
> > public interface MyGlobManager {
> > public MyGlob fetch();
> > }
> >
> > Impl
> > ========
> > @Service(value = "myGlobManager")
> > @WebService(endpointInterface="com.beelun.shoppro.service.MyGlobManager")
> > public class MyGlobManagerImpl extends GenericDaoHibernate<MyGlob, Long>
> > implements MyGlobManager {
> > // A cache for myGlob
> > private MyGlob myGlob = null;
> >
> > @Autowired
> > public MyGlobManagerImpl(SessionFactory sessionFactory) {
> > super(MyGlob.class, sessionFactory);
> > }
> >
> > @Autowired
> > TabManager tabManager;
> >
> > @Override
> > public MyGlob fetch() {...}
> >
> > Config file
> > =========
> > <beans xmlns="http://www.springframework.org/schema/beans"
> > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> > xmlns:jaxws="http://cxf.apache.org/jaxws"
> > xsi:schemaLocation="http://www.springframework.org/schema/beans
> >
> > http://www.springframework.org/schema/beans/spring-beans.xsd
> > http://cxf.apache.org/jaxws
> > http://cxf.apache.org/schemas/jaxws.xsd">
> >
> > <import resource="classpath:META-INF/cxf/cxf.xml" />
> > <import resource="classpath:META-INF/cxf/cxf-extension-soap.xml"/>
> > <import resource="classpath:META-INF/cxf/cxf-servlet.xml" />
> >
> > <jaxws:endpoint id="fooManager"
> >
> > implementor="com.beelun.shoppro.service.impl.FooManagerImpl"
> > address="/fooManager"/>
> >
> > <jaxws:endpoint id="myGlobManager"
> > implementor="#myGlobManager"
> > address="/myGlobManager"/>
> >
> > </beans>
> >
> > Exceptions
> > =============
> > 2009-12-23 01:12:25.099::WARN: Failed startup of context
> > org.mortbay.jetty.plugin.Jetty6PluginWebAppContext@1478e67f
> > {/,F:\shoppro\src\main\webapp}
> > org.springframework.beans.factory.BeanCreationException: Error creating
> > bean with name 'myGlobManager': Cannot resolve reference to bean
> > 'myGlobManager' while setting constructor argument; nested exception is
> > org.springframework.beans.factory.BeanCurrentlyInCreationException: Error
> > creating bean with name 'myGlobManager': Requested bean is currently in
> > creation: Is there an unresolvable circular reference?
> > at
> >
> org.springframework.beans.factory.support.BeanDefinitionValueResolver.resol
> > veReference(BeanDefinitionValueResolver.java:275) at
> >
> org.springframework.beans.factory.support.BeanDefinitionValueResolver.resol
> > veValueIfNecessary(BeanDefinitionValueResolver.java:104) ....
> >
> > Any idea?
> >
> > Thanks.
> >
>
> --
> Daniel Kulp
> dkulp@...
> http://www.dankulp.com/blog
>

--
Bill Li(李保存)
http://BaliOnWeb.com

RE: trouble running webservice on weblogic

2009-12-22T14:19:06Z

> -----Original Message-----
> From: Bill Smith [mailto:nedry@...]
> Sent: Tuesday, December 22, 2009 1:32 PM
> To: users@...
> Subject: trouble running webservice on weblogic
>
> I am trying to create a rather simple webservice on weblogic 10MP1.

You will very likely have to make sure that your application jars are
used instead of some that WebLogic uses natively. You do that with a
"weblogic-application.xml" file that specifies the
"prefer-application-packages" element.

trouble running webservice on weblogic

2009-12-22T13:32:27Z

I am trying to create a rather simple webservice on weblogic 10MP1.

I am getting the following stack trace, the scenario I am trying is below
the stacktrace Any help with any ideas on how to troubleshoot would be
appreciated.

java.lang.IllegalArgumentException: argument type mismatch
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.apache.cxf.databinding.AbstractWrapperHelper.createWrapperObject(AbstractWrapperHelper.java:99)
at
org.apache.cxf.jaxws.interceptors.WrapperClassOutInterceptor.handleMessage(WrapperClassOutInterceptor.java:103)
at
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:236)
at
org.apache.cxf.interceptor.OutgoingChainInterceptor.handleMessage(OutgoingChainInterceptor.java:76)
at
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:236)
at
org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:109)
at
org.apache.cxf.transport.servlet.ServletDestination.invoke(ServletDestination.java:98)
at
org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:394)
at
org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:170)
at
org.apache.cxf.transport.servlet.AbstractCXFServlet.invoke(AbstractCXFServlet.java:142)
at
org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:179)
at
org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:103)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at
org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:159)
at
weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:226)
at
weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124)
at
weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
at
weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
at
weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3395)
at
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at
weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2140)
at
weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2046)
at
weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1366)
at
weblogic.work.ExecuteRequestAdapter.execute(ExecuteRequestAdapter.java:21)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
Dec 22, 2009 9:12:24 PM org.apache.cxf.phase.PhaseInterceptorChain
doIntercept
WARNING: Interceptor has thrown exception, unwinding now
org.apache.cxf.interceptor.Fault
at
org.apache.cxf.databinding.AbstractWrapperHelper.createWrapperObject(AbstractWrapperHelper.java:107)
at
org.apache.cxf.jaxws.interceptors.WrapperClassOutInterceptor.handleMessage(WrapperClassOutInterceptor.java:103)
at
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:236)
at
org.apache.cxf.interceptor.OutgoingChainInterceptor.handleMessage(OutgoingChainInterceptor.java:76)
at
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:236)
at
org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:109)
at
org.apache.cxf.transport.servlet.ServletDestination.invoke(ServletDestination.java:98)
at
org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:394)
at
org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:170)
at
org.apache.cxf.transport.servlet.AbstractCXFServlet.invoke(AbstractCXFServlet.java:142)
at
org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:179)
at
org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:103)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at
org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:159)
at
weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:226)
at
weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124)
at
weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
at
weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
at
weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3395)
at
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at
weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2140)
at
weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2046)
at
weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1366)
at
weblogic.work.ExecuteRequestAdapter.execute(ExecuteRequestAdapter.java:21)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)

I am using cxf 2.2.5 with a very simple interface

@WebService
public interface CaseService {

@WebResult(name="closeTicketResponse")
public String closeTicket(
@WebParam(name="ticketNumber") String ticketNumber
);

implementing class

@WebService(endpointInterface = "CaseService")
public class CaseServiceImpl implements CaseService {
public String closeTicket(String ticketNumber) {
return ticketNumber;
}

spring file

<beans xmlns="http://www.springframework.org/schema/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:cxf="http://cxf.apache.org/core"
xmlns:jaxrs="http://cxf.apache.org/jaxrs"
xmlns:jaxws="http://cxf.apache.org/jaxws"
xmlns:wsp="http://www.w3.org/2006/07/ws-policy"
xmlns:p="http://cxf.apache.org/policy"
xmlns:context="http://www.springframework.org/schema/context"
xsi:schemaLocation="http://www.springframework.org/schema/beans

http://www.springframework.org/schema/beans/spring-beans.xsd
http://cxf.apache.org/jaxrs
http://cxf.apache.org/schemas/jaxrs.xsd
http://cxf.apache.org/jaxws
http://cxf.apache.org/schemas/jaxws.xsd
http://cxf.apache.org/core
http://cxf.apache.org/schemas/core.xsd
http://www.w3.org/2006/07/ws-policy
http://www.w3.org/2006/11/ws-policy.xsd
http://cxf.apache.org/policy
http://cxf.apache.org/schemas/policy.xsd
http://www.springframework.org/schema/context

http://www.springframework.org/schema/context/spring-context-2.5.xsd">


<import resource="classpath:META-INF/cxf/cxf.xml"/>
<import
resource="classpath:META-INF/cxf/cxf-extension-jaxrs-binding.xml"/>
<import resource="classpath:META-INF/cxf/cxf-extension-xml.xml"/>
<import resource="classpath:META-INF/cxf/cxf-extension-soap.xml"/>
<import resource="classpath:META-INF/cxf/cxf-servlet.xml"/>
<import
resource="classpath:META-INF/cxf/cxf-extension-ws-security.xml"/>
<import resource="classpath:META-INF/cxf/cxf-extension-policy.xml"/>

<jaxws:endpoint
id="caseService"
implementor="CaseServiceImpl"
address="/CaseService" />

</beans>

RE: Inflexible fault interceptor chain?

2009-12-22T13:30:30Z

Hi All:

I am trying to build SVN 2.2.x (I just updated from SVN) to test a patch (I do not have a test yet) just to see what happens if SAAJOutInterceptor uses a W3CDOMStreamWriter even if the local variable is null. Since that caused a test to hang I thought I'd try to build an unchanged 2.2.6 as a baseline. I get the errors below when I run:

mvn clean install -Peverything

Does 2.2.x build ok for anyone out there?

Results :

Failed tests:
testExcludeNSWithPackageName(org.apache.cxf.tools.wsdlto.jaxws.CodeGenBugTest)
testBug305924ForNestedBinding(org.apache.cxf.tools.wsdlto.jaxws.CodeGenBugTest)
testParameterOrderNoOutputMessage(org.apache.cxf.tools.wsdlto.jaxws.CodeGenBugTest)
testParameterOrderDifferentNS(org.apache.cxf.tools.wsdlto.jaxws.CodeGenBugTest)

Tests in error:
testHelloWorldExternalBindingFile(org.apache.cxf.tools.wsdlto.jaxws.CodeGenOptionTest)
testFlagForGenStandAlone(org.apache.cxf.tools.wsdlto.jaxws.CodeGenOptionTest)
testFlagForGenAdditional(org.apache.cxf.tools.wsdlto.jaxws.CodeGenOptionTest)
testHeaderFromAnotherMessage1(org.apache.cxf.tools.wsdlto.jaxws.CodeGenTest)
testHeaderFromAnotherMessage2(org.apache.cxf.tools.wsdlto.jaxws.CodeGenTest)
testHeaderFromAnotherMessage3(org.apache.cxf.tools.wsdlto.jaxws.CodeGenTest)
testHeaderFromAnotherMessage4(org.apache.cxf.tools.wsdlto.jaxws.CodeGenTest)
testHeaderFromAnotherMessage5(org.apache.cxf.tools.wsdlto.jaxws.CodeGenTest)
testRPCLit(org.apache.cxf.tools.wsdlto.jaxws.CodeGenTest)
testAsyncMethod(org.apache.cxf.tools.wsdlto.jaxws.CodeGenTest)
testAsyncMethodNoService(org.apache.cxf.tools.wsdlto.jaxws.CodeGenTest)
testHelloWorldSoap12(org.apache.cxf.tools.wsdlto.jaxws.CodeGenTest)
testHelloWorld(org.apache.cxf.tools.wsdlto.jaxws.CodeGenTest)
testHelloWorldWithDummyPlugin(org.apache.cxf.tools.wsdlto.jaxws.CodeGenTest)
testDocLitHolder(org.apache.cxf.tools.wsdlto.jaxws.CodeGenTest)
testSchemaImport(org.apache.cxf.tools.wsdlto.jaxws.CodeGenTest)
testExceptionNameCollision(org.apache.cxf.tools.wsdlto.jaxws.CodeGenTest)
testAllNameCollision(org.apache.cxf.tools.wsdlto.jaxws.CodeGenTest)
testImportNameCollision(org.apache.cxf.tools.wsdlto.jaxws.CodeGenTest)
testSoapHeader(org.apache.cxf.tools.wsdlto.jaxws.CodeGenTest)
testHolderHeader(org.apache.cxf.tools.wsdlto.jaxws.CodeGenTest)
testWSAddress(org.apache.cxf.tools.wsdlto.jaxws.CodeGenTest)
testVoidInOutMethod(org.apache.cxf.tools.wsdlto.jaxws.CodeGenTest)
testWsdlImport(org.apache.cxf.tools.wsdlto.jaxws.CodeGenTest)
testWebFault(org.apache.cxf.tools.wsdlto.jaxws.CodeGenTest)
testMultiSchemaParsing(org.apache.cxf.tools.wsdlto.jaxws.CodeGenTest)
testDefaultParameterOrder(org.apache.cxf.tools.wsdlto.jaxws.CodeGenTest)
testSupportXMLBindingBare(org.apache.cxf.tools.wsdlto.jaxws.CodeGenTest)
testSupportXMLBindingWrapped(org.apache.cxf.tools.wsdlto.jaxws.CodeGenTest)
testRouterWSDL(org.apache.cxf.tools.wsdlto.jaxws.CodeGenTest)
testWSDLContainsJavaKeywords(org.apache.cxf.tools.wsdlto.jaxws.CodeGenTest)
testWSDLWithEnumType(org.apache.cxf.tools.wsdlto.jaxws.CodeGenTest)
testSWAMime(org.apache.cxf.tools.wsdlto.jaxws.CodeGenTest)
testRPCHeader(org.apache.cxf.tools.wsdlto.jaxws.CodeGenTest)
testRefTNS(org.apache.cxf.tools.wsdlto.jaxws.CodeGenTest)
testWebFaultAnnotaion(org.apache.cxf.tools.wsdlto.jaxws.CodeGenTest)
testGlobalBinding(org.apache.cxf.tools.wsdlto.jaxws.CodeGenTest)
testXmlSeeAlso(org.apache.cxf.tools.wsdlto.jaxws.CodeGenTest)
testWSAction(org.apache.cxf.tools.wsdlto.jaxws.CodeGenTest)
testHandlerAnnotation(org.apache.cxf.tools.wsdlto.jaxws.CodeGenTest)
testGenerateXmlListAnno(org.apache.cxf.tools.wsdlto.jaxws.CodeGenTest)
testWrapperWithWildcard(org.apache.cxf.tools.wsdlto.jaxws.CodeGenTest)
testCXF1950(org.apache.cxf.tools.wsdlto.jaxws.CodeGenTest)
testLogicalOnlyWSDL(org.apache.cxf.tools.wsdlto.jaxws.CodeGenBugTest)
testBug305729(org.apache.cxf.tools.wsdlto.jaxws.CodeGenBugTest)
testBug305773(org.apache.cxf.tools.wsdlto.jaxws.CodeGenBugTest)
testBug305700(org.apache.cxf.tools.wsdlto.jaxws.CodeGenBugTest)
testNamespacePackageMapping1(org.apache.cxf.tools.wsdlto.jaxws.CodeGenBugTest)
testNamespacePackageMapping2(org.apache.cxf.tools.wsdlto.jaxws.CodeGenBugTest)
testNamespacePackageMapping3(org.apache.cxf.tools.wsdlto.jaxws.CodeGenBugTest)
testBug305772(org.apache.cxf.tools.wsdlto.jaxws.CodeGenBugTest)
testCommandLine(org.apache.cxf.tools.wsdlto.jaxws.CodeGenBugTest)
testLocatorWithJaxbBinding(org.apache.cxf.tools.wsdlto.jaxws.CodeGenBugTest)
testWsdlNoService(org.apache.cxf.tools.wsdlto.jaxws.CodeGenBugTest)
testNoServiceImport(org.apache.cxf.tools.wsdlto.jaxws.CodeGenBugTest)
testServiceNS(org.apache.cxf.tools.wsdlto.jaxws.CodeGenBugTest)
testNoServiceNOPortType(org.apache.cxf.tools.wsdlto.jaxws.CodeGenBugTest)
testDefatultNsMap(org.apache.cxf.tools.wsdlto.jaxws.CodeGenBugTest)
testDefatultNsMapExclude(org.apache.cxf.tools.wsdlto.jaxws.CodeGenBugTest)
testHelloWorldExternalBindingFile(org.apache.cxf.tools.wsdlto.jaxws.CodeGenBugTest)
testWebResult(org.apache.cxf.tools.wsdlto.jaxws.CodeGenBugTest)
testCXF627(org.apache.cxf.tools.wsdlto.jaxws.CodeGenBugTest)
testRecursiveImport(org.apache.cxf.tools.wsdlto.jaxws.CodeGenBugTest)
testCXF804(org.apache.cxf.tools.wsdlto.jaxws.CodeGenBugTest)
testDefinieServiceName(org.apache.cxf.tools.wsdlto.jaxws.CodeGenBugTest)
testAntFile(org.apache.cxf.tools.wsdlto.jaxws.CodeGenBugTest)
testAsyncImplAndClient(org.apache.cxf.tools.wsdlto.jaxws.CodeGenBugTest)
testZeroInputOutOfBandHeader(org.apache.cxf.tools.wsdlto.jaxws.CodeGenBugTest)
testBindingForImportWSDL(org.apache.cxf.tools.wsdlto.jaxws.CodeGenBugTest)
testReuseJaxwsBindingFile(org.apache.cxf.tools.wsdlto.jaxws.CodeGenBugTest)
testBindingXPath(org.apache.cxf.tools.wsdlto.jaxws.CodeGenBugTest)
testJaxbCatalog(org.apache.cxf.tools.wsdlto.jaxws.CodeGenBugTest)
testCatalog2(org.apache.cxf.tools.wsdlto.jaxws.CodeGenBugTest)
testCatalog3(org.apache.cxf.tools.wsdlto.jaxws.CodeGenBugTest)
testServer(org.apache.cxf.tools.wsdlto.jaxws.CodeGenBugTest)
testTwoJaxwsBindingFile(org.apache.cxf.tools.wsdlto.jaxws.CodeGenBugTest)
testJaxwsBindingJavaDoc(org.apache.cxf.tools.wsdlto.jaxws.CodeGenBugTest)
testWSAActionAnno(org.apache.cxf.tools.wsdlto.jaxws.CodeGenBugTest)
testCXF964(org.apache.cxf.tools.wsdlto.jaxws.CodeGenBugTest)
testCXF1620(org.apache.cxf.tools.wsdlto.jaxws.CodeGenBugTest)
testCXF1048(org.apache.cxf.tools.wsdlto.jaxws.CodeGenBugTest)
testJaxbNpa(org.apache.cxf.tools.wsdlto.jaxb.JAXBCodeGenOptionTest)

Tests run: 124, Failures: 4, Errors: 82, Skipped: 1

> -----Original Message-----
> From: Daniel Kulp [mailto:dkulp@...]
> Sent: Tuesday, December 22, 2009 10:06
> To: users@...
> Cc: Gary Gregory
> Subject: Re: Inflexible fault interceptor chain?
>
>
> Can you create a small test case and attach to a jira?
>
> This definitely sounds like bug of some sort. When I redid the
> Provider
> based services, I noticed that strange code in the StaxOutInterceptor
> as well
> and tried to remove it. However, that broke some of the JAX-WS tck
> tests.
> I don't remember the exact reason. I think it has something to do
> with
> faults thrown from the logical or soap handlers on the outgoing chain
> needed
> some strange and wacky processing. Don't really remember.
>
> If we can get your test case, we may be able to get it to work better.
>
> That said, you could probably write your own interceptor (you seem to
> be good
> at that :-) that would run on the fault chain prior to the SAAJOut and
> have
> it remove the SAAJ model from the message. You may need to trace
> through a
> couple other interceptors (like SoapOutInterceptor) to see if other
> properties
> need to be removed/reset.
>
> Dan
>
>
> On Mon December 21 2009 8:12:50 pm Gary Gregory wrote:
> > Hello Dan and all,
> >
> > Ok, the SAAJOutInterceptor solution almost worked. The behavior I
> describe
> > below is the same in CXF 2.2.4 and 2.2.6-SNAPSHOT (as of Saturday's
> > build). I am not on 2.2.5 due to some bugs that are fixed in 2.2.6.
> The
> > debugging information I gathered for this message is with 2.2.4.
> >
> > I have two scenarios, one works and one does not with the
> > SAAJOutInterceptor solution.
> >
> > If a Fault is thrown by a custom interceptor at a certain point in
> the
> > output chain, the wrong SOAP XML is generated, specifically no SOAP
> fault
> > XML elements are generated. Let me start by showing what works and
> why
> > before showing what does not and why.
> >
> > In the first scenario, which works, a SoapFault is thrown by our
> provider's
> > invoke(SOAPMessage) method under certain conditions, basically if
> our
> > server detects certain errors. Our provider looks like this:
> >
> > @WebServiceProvider
> > @ServiceMode(value = Service.Mode.MESSAGE)
> > public static class LdeWebServiceProvider implements
> Provider<SOAPMessage>
> > { @Override
> > public SOAPMessage invoke(SOAPMessage soapRequest) {
> > ...
> > throw new SoapFault("Our message",
> > Soap11.getInstance().getReceiver()); }
> > }
> >
> > In SAAJOutInterceptor.handleMessage, the local variable saaj is null,
> so
> > the code path taken builds a SOAP message from scratch and plugs in
> a
> > W3CDOMStreamWriter. All of the interceptors then write to
> > W3CDOMStreamWriter instead of the default XMLStreamWriter which
> normally
> > caches and writes to the HTTP wire. The W3CDOMStreamWriter allows me
> to
> > transform the DOM before it gets on the wire. Great stuff, it works.
> >
> > In the second scenario, I test our output feature where in addition
> to an
> > optional transformation, we have custom interceptors to do optional
> XML
> > validation before and after the XML transformation. After our
> provider
> > successfully processed a message, the output chain processing kicks
> in and
> > looks like this:
> >
> > Chain org.apache.cxf.phase.PhaseInterceptorChain@c375934. Current
> flow:
> > setup [PolicyOutInterceptor]
> > pre-logical [SwAOutInterceptor, SoapHeaderOutFilterInterceptor]
> > post-logical [SoapPreProtocolOutInterceptor]
> > prepare-send [MessageSenderInterceptor, MessageModeOutInterceptor]
> > pre-stream [LoggingOutInterceptor, XmlDeclOutInterceptor*,
> > AttachmentOutInterceptor, StaxOutInterceptor] pre-protocol
> > [MessageModeOutInterceptorInternal, SAAJOutInterceptor,
> > SOAPHandlerInterceptor, OurWSS4JOutInterceptor] write
> [SoapOutInterceptor]
> > pre-marshal [LogicalHandlerOutInterceptor,
> ValidatingOutInterceptor*,
> > TransformOutInterceptor*, ValidatingOutInterceptor*] marshal
> > [BareOutInterceptor]
> > write-ending [SoapOutEndingInterceptor]
> > pre-protocol-ending [SAAJOutEndingInterceptor]
> > pre-stream-ending [StaxOutEndingInterceptor]
> > prepare-send-ending [MessageSenderEndingInterceptor]
> >
> > The interceptors marked with * are mine:
> > - XmlDeclOutInterceptor forces the XML declaration to be written.
> > - ValidatingOutInterceptor validates XML
> > - TransformOutInterceptor transforms XML
> > - ValidatingOutInterceptor validates XML
> >
> > The problem occurs if XML validation fails (the first validation in
> this
> > test).
> >
> > When the XML validation fails, an exception thrown, caught, and re-
> thrown
> > as a fault.
> >
> > At the start of fault processing, the chain when SAAJOutInterceptor
> is
> > called looks like this:
> >
> > Chain org.apache.cxf.phase.PhaseInterceptorChain@77c16c5f. Current
> flow:
> > setup [ServerPolicyOutFaultInterceptor]
> > prepare-send [MessageSenderInterceptor, Soap11FaultOutInterceptor]
> > pre-stream [LoggingOutInterceptor, XmlDeclOutInterceptor*,
> > StaxOutInterceptor] pre-protocol [WebFaultOutInterceptor,
> > SAAJOutInterceptor, SOAPHandlerFaultOutInterceptor] write
> > [SoapOutInterceptor]
> > pre-marshal [LogicalHandlerFaultOutInterceptor]
> > marshal [Soap11FaultOutInterceptorInternal]
> > pre-protocol-ending [TransformOutFaultInterceptor*]
> > prepare-send-ending [MessageSenderEndingInterceptor]
> >
> > The interceptors marked with * are mine:
> > - XmlDeclOutInterceptor forces the XML declaration to be written.
> > - TransformOutFaultInterceptor validates XML
> >
> > When I step through this SAAJOutInterceptor invocation, the saaj
> variable
> > is NOT null, so the code path taken is different from what I
> described
> > above. Instead of a W3CDOMStreamWriter, a dummy XMLStreamWriter is
> created
> > that throws away whatever is written to it:
> >
> > //as the SOAPMessage already has everything in place, we
> do not
> > need XMLStreamWriter to write //anything for us, so we just set
> > XMLStreamWriter's output to a dummy output stream. XMLStreamWriter
> > origWriter = message.getContent(XMLStreamWriter.class);
> > message.put(ORIGINAL_XML_WRITER, origWriter);
> >
> > XMLStreamWriter dummyWriter =
> > StaxUtils.createXMLStreamWriter(new OutputStream() { public void
> write(int
> > b) throws IOException {
> > }
> > public void write(byte b[], int off, int len)
> throws
> > IOException { }
> > });
> > message.setContent(XMLStreamWriter.class, dummyWriter);
> >
> > No wonder I get no SOAP fault information back, I get:
> >
> > <?xml version='1.0' encoding='ISO-8859-1'?>
> > <SOAP-ENV:Envelope
> > xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
> > xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <SOAP-
> ENV:Header
> > xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
> <ais:requestID
> >
> xmlns:ais="http://com.seagullsw.appinterface/AppInterfaceServer">{c0a80
> 102
> > -00ce16ad0000010e75da25398002}</ais:requestID> </SOAP-ENV:Header>
> > <SOAP-ENV:Body xmlns:SOAP-
> ENV="http://schemas.xmlsoap.org/soap/envelope/"
> > /> </SOAP-ENV:Envelope>
> >
> > Is this a bug? Why would there be a dummy writer put in place? Is
> there
> > another CXF way to do this?
> >
> > Thank you,
> > Gary
> >
> > > -----Original Message-----
> > > From: Gary Gregory
> > > Sent: Friday, December 18, 2009 18:11
> > > To: 'Daniel Kulp'; users@...
> > > Subject: RE: Inflexible fault interceptor chain?
> > >
> > > Ok, that worked!
> > >
> > > Thank you Dan,
> > > Gary
> > >
> > > > -----Original Message-----
> > > > From: Daniel Kulp [mailto:dkulp@...]
> > > > Sent: Friday, December 18, 2009 07:33
> > > > To: users@...
> > > > Cc: Gary Gregory; Lee Breisacher; Nikolay Glazyrin
> > > > Subject: Re: Inflexible fault interceptor chain?
> > > >
> > > >
> > > > Honestly, the EASIEST way to accomplish this, since you are using
> > >
> > > soap,
> > >
> > > > is to
> > > > add the SAAJOutInterceptor to the fault chain. Then, your
> > >
> > > interceptor
> > >
> > > > would
> > > > live right before it's "ending" interceptor and do:
> > > >
> > > > message.getContext(SOAPMessage.class)
> > > >
> > > > to get the SAAJ model out. Since the SAAJ model implements the
> DOM
> > > > interfaces, you can then feed that into an XSLT processor or
> similar
> > >
> > > to
> > >
> > > > transform it and then set a new version back with the setContent
> > >
> > > call.
> > >
> > > > Dan
> > > >
> > > > On Fri December 18 2009 4:13:29 am Gary Gregory wrote:
> > > > > Hi All:
> > > > >
> > > > > I need to apply an XSL transformation to messages coming out of
> CXF
> > > >
> > > > (our
> > > >
> > > > > users configure what the XSL looks like.) For a normal
> > >
> > > (successful)
> > >
> > > > > message, I have an interceptor (during Phase.PRE_MARSHAL) that
> > >
> > > uses
> > >
> > > > the
> > > >
> > > > > DOM aspect of a message. That works great. BTW, I get to the
> DOM
> > > >
> > > > like
> > > >
> > > > > this:
> > > > >
> > > > > Node node = (Node) message.getContent(List.class).get(0);
> > > > >
> > > > > That seems brittle, is there a safer way to get to an aspect of
> the
> > > >
> > > > message
> > > >
> > > > > I can feed to javax.xml.transform?
> > > > >
> > > > > The real issue comes with fault messages because the fault
> chain
> > >
> > > uses
> > >
> > > > an
> > >
> > >
> XMLStreamWriter<http://java.sun.com/javase/6/docs/api/javax/xml/stream/
> > >
> > > > XML
> > > >
> > > > > StreamWriter.html>. The fault chain looks like this:
> > > > >
> > > > > Chain org.apache.cxf.phase.PhaseInterceptorChain@3015b303.
> Current
> > > >
> > > > flow:
> > > > > setup [ServerPolicyOutFaultInterceptor]
> > > > > prepare-send [MessageSenderInterceptor,
> > >
> > > Soap11FaultOutInterceptor]
> > >
> > > > > pre-stream [LoggingOutInterceptor, XmlDeclOutInterceptor*,
> > > > > StaxOutInterceptor] pre-protocol [WebFaultOutInterceptor,
> > > > > SOAPHandlerFaultOutInterceptor] write [SoapOutInterceptor]
> > > > > pre-marshal [LogicalHandlerFaultOutInterceptor]
> > > > > marshal [Soap11FaultOutInterceptorInternal]
> > > > > pre-stream-ending [StaxOutEndingInterceptor,
> > > > > TransformOutFaultInterceptor*] prepare-send-ending
> > > > > [MessageSenderEndingInterceptor]
> > > > >
> > > > > FYI, the interceptors marked with * are our own:
> > > > >
> > > > > * XmlDeclOutInterceptor forces an XML declaration to be
> > > >
> > > > written.
> > > >
> > > > > * TransformOutFaultInterceptor is where I thought I
> could
> > > >
> > > > transform
> > > >
> > > > > the fault XML message.
> > > > >
> > > > > The
> > >
> > >
> XMLStreamWriter<http://java.sun.com/javase/6/docs/api/javax/xml/stream/
> > >
> > > > XML
> > > >
> > > > > StreamWriter.html> looks like this:
> > > > >
> > > > > [StreamWriter: class com.ctc.wstx.sw.SimpleNsStreamWriter,
> > >
> > > underlying
> > >
> > > > > outputter:
> > >
> > >
> com.ctc.wstx.sw.ISOLatin1XmlWriter@1125cf44<mailto:com.ctc.wstx.sw.ISOL
> > >
> > > > ati
> > > >
> > > > > n1XmlWriter@1125cf44>
> > > > >
> > > > > The com.ctc.wstx.sw.ISOLatin1XmlWriter wraps a
> > > > > org.apache.cxf.io.CachedOutputStream, which in turns wraps:
> > > > >
> > > > > * currentStream - LoadingByteArrayOutputStream
> > > > >
> > > > > * flowThroughStream -
> > > >
> > > > AbstractHTTPDestination$WrappedOutputStream
> > > >
> > > > > All of this to say that when the chain's interceptors are
> working
> > > >
> > > > with the
> > > >
> > > > > message's
> > >
> > >
> XMLStreamWriter<http://java.sun.com/javase/6/docs/api/javax/xml/stream/
> > >
> > > > XML
> > > >
> > > > > StreamWriter.html>, the bytes are cached and written to the
> wire.
> > >
> > > It
> > >
> > > > is not
> > > >
> > > > > possible to catch the fault XML message and change it.
> > > > >
> > > > > The only thing I've come up with but not implemented yet would
> be
> > >
> > > to
> > >
> > > > insert
> > > >
> > > > > an interceptor before the XML declaration is written and put
> the
> > >
> > >
> XMLStreamWriter<http://java.sun.com/javase/6/docs/api/javax/xml/stream/
> > >
> > > > XML
> > > >
> > > > > StreamWriter.html> into a temp spot in the message content map,
> > >
> > > then
> > >
> > > > put a
> > > >
> > > > > new
> > >
> > >
> XMLStreamWriter<http://java.sun.com/javase/6/docs/api/javax/xml/stream/
> > >
> > > > XML
> > > >
> > > > > StreamWriter.html> on a byte array in its place. A pre-stream-
> > >
> > > ending
> > >
> > > > > interceptor can take those bytes, apply XSL to them and then
> write
> > > >
> > > > them to
> > > >
> > > > > the original
> > >
> > >
> XMLStreamWriter<http://java.sun.com/javase/6/docs/api/javax/xml/stream/
> > >
> > > > XML
> > > >
> > > > > StreamWriter.html>, before putting the original
> > >
> > >
> XMLStreamWriter<http://java.sun.com/javase/6/docs/api/javax/xml/stream/
> > >
> > > > XML
> > > >
> > > > > StreamWriter.html> back in it original slot in the message
> content
> > > >
> > > > map.
> > > >
> > > > > That seems like big old hack.
> > > > >
> > > > > Any ideas on a cleaner solution?
> > > > >
> > > > > Thank you,
> > > > > Gary Gregory
> > > > > Seagull Software
> > > > > ggregory@...
> > > > > www.seagullsoftware.com
> > > >
> > > > --
> > > > Daniel Kulp
> > > > dkulp@...
> > > > http://www.dankulp.com/blog
> >
>
> --
> Daniel Kulp
> dkulp@...
> http://www.dankulp.com/blog

Re: Switching a client to produce a JMS Object Message?

2009-12-22T12:50:24Z

The answer is to simply set the messageType property to binary. I'll
blog my experience with an example when I get a chance.

Thanks!
James

On Tue, Dec 22, 2009 at 9:35 AM, James Carr <james.r.carr@...> wrote:

> Hi All,
>
> I have some existing services that were using CXF's SOAP over JMS
> protocol to send JMS messages to a topic... we've changed the homebrew
> infrastructure that listened to this topic with a more solid, open
> source solution. However, the replacement reads JmsMessages of type
> ObjectMessage rather than SOAP. The same values we used are used,
> except as StringProperties on the ObjectMessage.
>
> Is there someway to replace the message format of my CXF client
> service to produce ObjectMessages?
>
> Thanks,
> James
>

RE: Inflexible fault interceptor chain?

2009-12-22T10:52:36Z

I'll see if I can create a standalone test... in the meantime I am trying to see if my fix breaks 2.2.6-SNAPSHOT tests.

Gary

RE: [DOSGI] cxf 2.2.5 in the DOSGI 1.2 snapshot download?

2009-12-22T10:16:32Z

Injecting 2.2.5 into the multibundle seems to work fine, so no worries there.

On the downside,
-Dorg.apache.cxf.spring.validation.mode=VALIDATION_NONE
(the rationale for going to 2.2.5) still doesn't seem to have an effect.

My theory being schema validation on a machine not connected to the internet dramatically increases the startup time for cxf-dosgi-ri-dsw-cxf-1.1.jar (i.e. have to wait for all the timeouts).

Thanks,
Thom

-----Original Message-----
From: David Bosschaert [mailto:david.bosschaert@...]
Sent: Tuesday, December 22, 2009 9:19 AM
To: users@...
Subject: Re: [DOSGI] cxf 2.2.5 in the DOSGI 1.2 snapshot download?

Does the stack trace not appear with CXF 2.2.4 and DOSGi 1.1?

David

2009/12/22 Shulok, Thomas <thomas.shulok@...>:

> Hi David,
>
> Understood, that should work for me, but...injecting the cxf-bundle-minimal-2.2.5.jar into the 1.1 release generates the same stack trace as the 1.2 jar (both single bundle distros).
>
> Thanks,
> Thom
>
> -----Original Message-----
> From: David Bosschaert [mailto:david.bosschaert@...]
> Sent: Tuesday, December 22, 2009 7:23 AM
> To: users@...
> Subject: Re: [DOSGI] cxf 2.2.5 in the DOSGI 1.2 snapshot download?
>
> Hi Thomas,
>
> The 1.2-SNAPSHOT CXF-DOSGi trunk is under heavy refactoring at the moment, I'm happy to take a look at that stack trace once it's settled down, hopefully in a few weeks time. For now, please try if you can stick to the 1.1 release.
>
> From memory, I have seen stack traces like the one you're posting here. In some cases they did happen with the single-bundle distro but not with the multi-bundle distro. In some cases they have been harmless (just a validation error, but things continue to work).
>
> Best regards,
>
> David
>
> 2009/12/22 Shulok, Thomas <thomas.shulok@...>:
>> Thanks David. Will try out the next snapshot build.
>>
>> Yesterday, I did try what you suggested (today), but with the 1.2 snapshot, and I got the following...
>>
>> Thanks,
>> Thom
>>
>> Dec 21, 2009 2:14:38 PM org.apache.cxf.dosgi.dsw.OsgiUtils
>> readIntentMap
>> WARNING: Intent map load failed:
>> org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException:
>> Line 48 i n XML document from OSGi
>> resource[classpath:/OSGI-INF/cxf/intents/intent-map.xml
>> |bnd.id=2|bnd.sym=cxf-dosgi-ri-singlebundle-distribution] is invalid;
>> |nested exc
>> eption is org.xml.sax.SAXParseException: cvc-complex-type.2.4.c: The matching wi ldcard is strict, but no declaration can be found for element 'p:policies'.
>> at
>> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadB
>> eanDefinitions(XmlBeanDefinitionReader.java:404)
>> at
>> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBea
>> nDefinitions(XmlBeanDefinitionReader.java:342)
>> at
>> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBea
>> nDefinitions(XmlBeanDefinitionReader.java:310)
>> at
>> org.springframework.beans.factory.support.AbstractBeanDefinitionReade
>> r.loadBeanDefinitions(AbstractBeanDefinitionReader.java:143)
>> at
>> org.springframework.beans.factory.support.AbstractBeanDefinitionReade
>> r.loadBeanDefinitions(AbstractBeanDefinitionReader.java:178)
>> at
>> org.springframework.beans.factory.support.AbstractBeanDefinitionReade
>> r.loadBeanDefinitions(AbstractBeanDefinitionReader.java:149)
>> at
>> org.springframework.osgi.context.support.OsgiBundleXmlApplicationCont
>> ext.loadBeanDefinitions(OsgiBundleXmlApplicationContext.java:176)
>> at
>> org.springframework.osgi.context.support.OsgiBundleXmlApplicationCont
>> ext.loadBeanDefinitions(OsgiBundleXmlApplicationContext.java:142)
>> at
>> org.springframework.context.support.AbstractRefreshableApplicationCon
>> text.refreshBeanFactory(AbstractRefreshableApplicationContext.java:12
>> 3
>> )
>> at
>> org.springframework.context.support.AbstractApplicationContext.obtain
>> FreshBeanFactory(AbstractApplicationContext.java:422)
>> at
>> org.springframework.context.support.AbstractApplicationContext.refres
>> h(AbstractApplicationContext.java:352)
>> at
>> org.springframework.osgi.context.support.AbstractDelegatedExecutionAp
>> plicationContext.access$301(AbstractDelegatedExecutionApplicationCont
>> e
>> xt.java:69
>> )
>> at
>> org.springframework.osgi.context.support.AbstractDelegatedExecutionAp
>> plicationContext$1.run(AbstractDelegatedExecutionApplicationContext.j
>> a
>> va:186)
>> at
>> org.springframework.osgi.util.internal.PrivilegedUtils.executeWithCus
>> tomTCCL(PrivilegedUtils.java:85)
>> at
>> org.springframework.osgi.context.support.AbstractDelegatedExecutionAp
>> plicationContext.normalRefresh(AbstractDelegatedExecutionApplicationC
>> o
>> ntext.java
>> :182)
>> at
>> org.springframework.osgi.context.support.AbstractDelegatedExecutionAp
>> plicationContext$NoDependenciesWaitRefreshExecutor.refresh(AbstractDe
>> l
>> egatedExec
>> utionApplicationContext.java:89)
>> at
>> org.springframework.osgi.context.support.AbstractDelegatedExecutionAp
>> plicationContext.refresh(AbstractDelegatedExecutionApplicationContext.
>> java:175)
>> at
>> org.apache.cxf.dosgi.dsw.OsgiUtils.readIntentMap(OsgiUtils.java:401)
>> at
>> org.apache.cxf.dosgi.dsw.OsgiUtils.getIntentMap(OsgiUtils.java:376)
>> at
>> org.apache.cxf.dosgi.dsw.Activator.getIntentMap(Activator.java:96)
>> at
>> org.apache.cxf.dosgi.dsw.Activator.registerRemoteServiceAdminService(
>> Activator.java:78)
>> at org.apache.cxf.dosgi.dsw.Activator.start(Activator.java:55)
>> at
>> org.apache.cxf.dosgi.singlebundle.AggregatedActivator.startEmbeddedAc
>> tivators(AggregatedActivator.java:115)
>> at
>> org.apache.cxf.dosgi.singlebundle.AggregatedActivator.start(Aggregate
>> dActivator.java:46)
>> at
>> org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(Bund
>> leContextImpl.java:783)
>> at java.security.AccessController.doPrivileged(Native Method)
>> at
>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActiv
>> ator(BundleContextImpl.java:774)
>> at
>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(Bund
>> leContextImpl.java:755)
>> at
>> org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(Bundl
>> eHost.java:352)
>> at
>> org.eclipse.osgi.framework.internal.core.AbstractBundle.start(Abstrac
>> tBundle.java:280)
>> at
>> org.eclipse.osgi.framework.internal.core.AbstractBundle.start(Abstrac
>> tBundle.java:272)
>> at
>> org.eclipse.osgi.framework.internal.core.FrameworkCommandProvider._st
>> art(FrameworkCommandProvider.java:253)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown
>> Source)
>> at java.lang.reflect.Method.invoke(Unknown Source)
>> at org.eclipse.osgi.framework.internal.core.FrameworkCommandInterpreter.
>> execute(FrameworkCommandInterpreter.java:155)
>> at
>> org.eclipse.osgi.framework.internal.core.FrameworkConsole.docommand(F
>> rameworkConsole.java:303)
>> at
>> org.eclipse.osgi.framework.internal.core.FrameworkConsole.console(Fra
>> meworkConsole.java:288)
>> at
>> org.eclipse.osgi.framework.internal.core.FrameworkConsole.run(Framewo
>> rkConsole.java:224)
>> at java.lang.Thread.run(Unknown Source) Caused by: org.xml.sax.SAXParseException: cvc-complex-type.2.4.c: The matching w ildcard is strict, but no declaration can be found for element 'p:policies'.
>> at
>> com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAX
>> ParseException(Unknown Source)
>> at
>> com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.error(Unk
>> nown Source)
>> at
>> com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(
>> Unknown Source)
>> at
>> com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(
>> Unknown Source)
>> at
>> com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator$XSIErro
>> rReporter.reportError(Unknown Source)
>> at
>> com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.reportS
>> chemaError(Unknown Source)
>> at
>> com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.handleS
>> tartElement(Unknown Source)
>> at
>> com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.startEl
>> ement(Unknown Source)
>> at
>> com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scan
>> StartElement(Unknown Source)
>> at
>> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImp
>> l$FragmentContentDispatcher.dispatch(Unknown Source)
>> at
>> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImp
>> l.scanDocument(Unknown Source)
>> at
>> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(U
>> nknown Source)
>> at
>> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(U
>> nknown Source)
>> at
>> com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(Unknown So
>> urce)
>> at
>> com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(Unknown So
>> urce)
>> at
>> com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(Unk
>> nown Source)
>> at
>> org.springframework.beans.factory.xml.DefaultDocumentLoader.loadDocum
>> ent(DefaultDocumentLoader.java:75)
>> at
>> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadB
>> eanDefinitions(XmlBeanDefinitionReader.java:396)
>> ... 40 more
>> Dec 21, 2009 2:14:38 PM org.apache.cxf.dosgi.dsw.qos.IntentMap
>> setIntents
>> INFO: Injected intents: {}
>> java.lang.UnsupportedClassVersionError: Bad version number in .class
>> file
>> at java.lang.ClassLoader.defineClass1(Native Method)
>> at java.lang.ClassLoader.defineClass(Unknown Source)
>> at
>> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.defineClass(
>> DefaultClassLoader.java:183)
>> at
>> org.eclipse.osgi.baseadaptor.loader.ClasspathManager.defineClass(Clas
>> spathManager.java:576)
>> at
>> org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findClassImpl(Cl
>> asspathManager.java:546)
>> at
>> org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClassIm
>> pl(ClasspathManager.java:477)
>> at
>> org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass_L
>> ockClassLoader(ClasspathManager.java:465)
>> at
>> org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(C
>> lasspathManager.java:445)
>> at
>> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalCla
>> ss(DefaultClassLoader.java:211)
>> at
>> org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLo
>> ader.java:381)
>> at
>> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(Bundl
>> eLoader.java:457)
>> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.
>> java:410)
>> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.
>> java:398)
>> at
>> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(De
>> faultClassLoader.java:105)
>> at java.lang.ClassLoader.loadClass(Unknown Source)
>> at java.lang.ClassLoader.loadClassInternal(Unknown Source)
>> at java.lang.ClassLoader.defineClass1(Native Method)
>> at java.lang.ClassLoader.defineClass(Unknown Source)
>> at
>> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.defineClass(
>> DefaultClassLoader.java:183)
>> at
>> org.eclipse.osgi.baseadaptor.loader.ClasspathManager.defineClass(Clas
>> spathManager.java:576)
>> at
>> org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findClassImpl(Cl
>> asspathManager.java:546)
>> at
>> org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClassIm
>> pl(ClasspathManager.java:477)
>> at
>> org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass_L
>> ockClassLoader(ClasspathManager.java:465)
>> at
>> org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(C
>> lasspathManager.java:445)
>> at
>> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalCla
>> ss(DefaultClassLoader.java:211)
>> at
>> org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLo
>> ader.java:381)
>> at
>> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(Bundl
>> eLoader.java:457)
>> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.
>> java:410)
>> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.
>> java:398)
>> at
>> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(De
>> faultClassLoader.java:105)
>> at java.lang.ClassLoader.loadClass(Unknown Source)
>> at java.lang.ClassLoader.loadClassInternal(Unknown Source)
>> at
>> org.apache.cxf.dosgi.discovery.zookeeper.Activator.createZooKeeperDis
>> covery(Activator.java:112)
>> at
>> org.apache.cxf.dosgi.discovery.zookeeper.Activator.start(Activator.ja
>> va:46)
>> at
>> org.apache.cxf.dosgi.singlebundle.AggregatedActivator.startEmbeddedAc
>> tivators(AggregatedActivator.java:115)
>> at
>> org.apache.cxf.dosgi.singlebundle.AggregatedActivator.start(Aggregate
>> dActivator.java:46)
>> at
>> org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(Bund
>> leContextImpl.java:783)
>> at java.security.AccessController.doPrivileged(Native Method)
>> at
>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActiv
>> ator(BundleContextImpl.java:774)
>> at
>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(Bund
>> leContextImpl.java:755)
>> at
>> org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(Bundl
>> eHost.java:352)
>> at
>> org.eclipse.osgi.framework.internal.core.AbstractBundle.start(Abstrac
>> tBundle.java:280)
>> at
>> org.eclipse.osgi.framework.internal.core.AbstractBundle.start(Abstrac
>> tBundle.java:272)
>> at
>> org.eclipse.osgi.framework.internal.core.FrameworkCommandProvider._st
>> art(FrameworkCommandProvider.java:253)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown
>> Source)
>> at java.lang.reflect.Method.invoke(Unknown Source)
>> at org.eclipse.osgi.framework.internal.core.FrameworkCommandInterpreter.
>> execute(FrameworkCommandInterpreter.java:155)
>> at
>> org.eclipse.osgi.framework.internal.core.FrameworkConsole.docommand(F
>> rameworkConsole.java:303)
>> at
>> org.eclipse.osgi.framework.internal.core.FrameworkConsole.console(Fra
>> meworkConsole.java:288)
>> at
>> org.eclipse.osgi.framework.internal.core.FrameworkConsole.run(Framewo
>> rkConsole.java:224)
>> at java.lang.Thread.run(Unknown Source) Dec 21, 2009 2:14:38
>> PM org.apache.cxf.dosgi.topologymanager.Activator start
>> INFO: TopologyManager: start()
>> Dec 21, 2009 2:14:38 PM
>> org.apache.cxf.dosgi.topologymanager.RemoteServiceAdminL
>> ist$1 addingService
>> INFO: Adding RemoteServiceAdmin to list of admins Dec 21, 2009
>> 2:14:38 PM org.apache.cxf.dosgi.topologymanager.RemoteServiceAdminL
>> ist$1 addingService
>> INFO: enlisted RemoteEventAdmins: 0
>> Dec 21, 2009 2:14:38 PM
>> org.apache.cxf.dosgi.topologymanager.TopologyManager tri
>> ggerExportImportForRemoteSericeAdmin
>> INFO: TopologyManager: triggerExportImportForRemoteSericeAdmin()
>> Dec 21, 2009 2:14:38 PM
>> org.apache.cxf.dosgi.topologymanager.TopologyManagerImpo
>> rt triggerExportImportForRemoteSericeAdmin
>> SEVERE: NOT IMPLEMENTED !!!
>> Dec 21, 2009 2:14:38 PM
>> org.apache.cxf.dosgi.topologymanager.EndpointListenerImp
>> l getRegistrationProperties
>> INFO: EndpointListener: current filter: []
>>
>> -----Original Message-----
>> From: David Bosschaert [mailto:david.bosschaert@...]
>> Sent: Tuesday, December 22, 2009 6:27 AM
>> To: users@...
>> Subject: Re: [DOSGI] cxf 2.2.5 in the DOSGI 1.2 snapshot download?
>>
>> I've just updated CXF/DOSGi trunk to use CXF 2.2.5
>>
>> BTW you should be able to use CXF 2.2.5 with the DOSGI 1.1 release. In the multi bundle distro, just replace the cxf-bundle-minimal-2.2.5.jar with the 2.2.5 version. Haven't tried it but it should work...
>>
>> Cheers,
>>
>> David
>>
>> 2009/12/22 David Bosschaert <david.bosschaert@...>:
>>> Hi Thomas,
>>>
>>> Hmmm, I would think so, but the 1.1 release also has 2.2.4.
>>> I'll update the build system to pick up 2.2.5.
>>>
>>> BTW I *really* advise you to use the 1.1 release and not
>>> 1.2-SNAPSHOT at this moment in time as there is a lot of refactoring
>>> going on @ dosgi trunk [1]. So unless you like living on the edge I
>>> would go for the 1.1 release :)
>>>
>>> Cheers,
>>>
>>> David
>>>
>>> [1]
>>> http://old.nabble.com/Migrating-CXF-DOSGi-to-be-complaint-with-the-n
>>> e w -OSGi-Remote-Service--Admin-spec-td26645023.html
>>>
>>> 2009/12/21 Shulok, Thomas <thomas.shulok@...>:
>>>> Hi All,
>>>>
>>>> Just downloaded the lastest 1.2 snapshot, and it still has cxf-bundle-minimal-2.2.4.jar. Should this be 2.2.5 now?
>>>>
>>>> Thanks,
>>>> Thom
>>>>
>>>
>>
>

Re: Inflexible fault interceptor chain?

2009-12-22T10:05:37Z

Can you create a small test case and attach to a jira?

This definitely sounds like bug of some sort. When I redid the Provider
based services, I noticed that strange code in the StaxOutInterceptor as well
and tried to remove it. However, that broke some of the JAX-WS tck tests.
I don't remember the exact reason. I think it has something to do with
faults thrown from the logical or soap handlers on the outgoing chain needed
some strange and wacky processing. Don't really remember.

If we can get your test case, we may be able to get it to work better.

That said, you could probably write your own interceptor (you seem to be good
at that :-) that would run on the fault chain prior to the SAAJOut and have
it remove the SAAJ model from the message. You may need to trace through a
couple other interceptors (like SoapOutInterceptor) to see if other properties
need to be removed/reset.

Dan

On Mon December 21 2009 8:12:50 pm Gary Gregory wrote:

> Hello Dan and all,
>
> Ok, the SAAJOutInterceptor solution almost worked. The behavior I describe
> below is the same in CXF 2.2.4 and 2.2.6-SNAPSHOT (as of Saturday's
> build). I am not on 2.2.5 due to some bugs that are fixed in 2.2.6. The
> debugging information I gathered for this message is with 2.2.4.
>
> I have two scenarios, one works and one does not with the
> SAAJOutInterceptor solution.
>
> If a Fault is thrown by a custom interceptor at a certain point in the
> output chain, the wrong SOAP XML is generated, specifically no SOAP fault
> XML elements are generated. Let me start by showing what works and why
> before showing what does not and why.
>
> In the first scenario, which works, a SoapFault is thrown by our provider's
> invoke(SOAPMessage) method under certain conditions, basically if our
> server detects certain errors. Our provider looks like this:
>
> @WebServiceProvider
> @ServiceMode(value = Service.Mode.MESSAGE)
> public static class LdeWebServiceProvider implements Provider<SOAPMessage>
> { @Override
> public SOAPMessage invoke(SOAPMessage soapRequest) {
> ...
> throw new SoapFault("Our message",
> Soap11.getInstance().getReceiver()); }
> }
>
> In SAAJOutInterceptor.handleMessage, the local variable saaj is null, so
> the code path taken builds a SOAP message from scratch and plugs in a
> W3CDOMStreamWriter. All of the interceptors then write to
> W3CDOMStreamWriter instead of the default XMLStreamWriter which normally
> caches and writes to the HTTP wire. The W3CDOMStreamWriter allows me to
> transform the DOM before it gets on the wire. Great stuff, it works.
>
> In the second scenario, I test our output feature where in addition to an
> optional transformation, we have custom interceptors to do optional XML
> validation before and after the XML transformation. After our provider
> successfully processed a message, the output chain processing kicks in and
> looks like this:
>
> Chain org.apache.cxf.phase.PhaseInterceptorChain@c375934. Current flow:
> setup [PolicyOutInterceptor]
> pre-logical [SwAOutInterceptor, SoapHeaderOutFilterInterceptor]
> post-logical [SoapPreProtocolOutInterceptor]
> prepare-send [MessageSenderInterceptor, MessageModeOutInterceptor]
> pre-stream [LoggingOutInterceptor, XmlDeclOutInterceptor*,
> AttachmentOutInterceptor, StaxOutInterceptor] pre-protocol
> [MessageModeOutInterceptorInternal, SAAJOutInterceptor,
> SOAPHandlerInterceptor, OurWSS4JOutInterceptor] write [SoapOutInterceptor]
> pre-marshal [LogicalHandlerOutInterceptor, ValidatingOutInterceptor*,
> TransformOutInterceptor*, ValidatingOutInterceptor*] marshal
> [BareOutInterceptor]
> write-ending [SoapOutEndingInterceptor]
> pre-protocol-ending [SAAJOutEndingInterceptor]
> pre-stream-ending [StaxOutEndingInterceptor]
> prepare-send-ending [MessageSenderEndingInterceptor]
>
> The interceptors marked with * are mine:
> - XmlDeclOutInterceptor forces the XML declaration to be written.
> - ValidatingOutInterceptor validates XML
> - TransformOutInterceptor transforms XML
> - ValidatingOutInterceptor validates XML
>
> The problem occurs if XML validation fails (the first validation in this
> test).
>
> When the XML validation fails, an exception thrown, caught, and re-thrown
> as a fault.
>
> At the start of fault processing, the chain when SAAJOutInterceptor is
> called looks like this:
>
> Chain org.apache.cxf.phase.PhaseInterceptorChain@77c16c5f. Current flow:
> setup [ServerPolicyOutFaultInterceptor]
> prepare-send [MessageSenderInterceptor, Soap11FaultOutInterceptor]
> pre-stream [LoggingOutInterceptor, XmlDeclOutInterceptor*,
> StaxOutInterceptor] pre-protocol [WebFaultOutInterceptor,
> SAAJOutInterceptor, SOAPHandlerFaultOutInterceptor] write
> [SoapOutInterceptor]
> pre-marshal [LogicalHandlerFaultOutInterceptor]
> marshal [Soap11FaultOutInterceptorInternal]
> pre-protocol-ending [TransformOutFaultInterceptor*]
> prepare-send-ending [MessageSenderEndingInterceptor]
>
> The interceptors marked with * are mine:
> - XmlDeclOutInterceptor forces the XML declaration to be written.
> - TransformOutFaultInterceptor validates XML
>
> When I step through this SAAJOutInterceptor invocation, the saaj variable
> is NOT null, so the code path taken is different from what I described
> above. Instead of a W3CDOMStreamWriter, a dummy XMLStreamWriter is created
> that throws away whatever is written to it:
>
> //as the SOAPMessage already has everything in place, we do not
> need XMLStreamWriter to write //anything for us, so we just set
> XMLStreamWriter's output to a dummy output stream. XMLStreamWriter
> origWriter = message.getContent(XMLStreamWriter.class);
> message.put(ORIGINAL_XML_WRITER, origWriter);
>
> XMLStreamWriter dummyWriter =
> StaxUtils.createXMLStreamWriter(new OutputStream() { public void write(int
> b) throws IOException {
> }
> public void write(byte b[], int off, int len) throws
> IOException { }
> });
> message.setContent(XMLStreamWriter.class, dummyWriter);
>
> No wonder I get no SOAP fault information back, I get:
>
> <?xml version='1.0' encoding='ISO-8859-1'?>
> <SOAP-ENV:Envelope
> xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
> xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <SOAP-ENV:Header
> xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"> <ais:requestID
> xmlns:ais="http://com.seagullsw.appinterface/AppInterfaceServer">{c0a80102
> -00ce16ad0000010e75da25398002}</ais:requestID> </SOAP-ENV:Header>
> <SOAP-ENV:Body xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
> /> </SOAP-ENV:Envelope>
>
> Is this a bug? Why would there be a dummy writer put in place? Is there
> another CXF way to do this?
>
> Thank you,
> Gary
>
> > -----Original Message-----
> > From: Gary Gregory
> > Sent: Friday, December 18, 2009 18:11
> > To: 'Daniel Kulp'; users@...
> > Subject: RE: Inflexible fault interceptor chain?
> >
> > Ok, that worked!
> >
> > Thank you Dan,
> > Gary
> >
> > > -----Original Message-----
> > > From: Daniel Kulp [mailto:dkulp@...]
> > > Sent: Friday, December 18, 2009 07:33
> > > To: users@...
> > > Cc: Gary Gregory; Lee Breisacher; Nikolay Glazyrin
> > > Subject: Re: Inflexible fault interceptor chain?
> > >
> > >
> > > Honestly, the EASIEST way to accomplish this, since you are using
> >
> > soap,
> >
> > > is to
> > > add the SAAJOutInterceptor to the fault chain. Then, your
> >
> > interceptor
> >
> > > would
> > > live right before it's "ending" interceptor and do:
> > >
> > > message.getContext(SOAPMessage.class)
> > >
> > > to get the SAAJ model out. Since the SAAJ model implements the DOM
> > > interfaces, you can then feed that into an XSLT processor or similar
> >
> > to
> >
> > > transform it and then set a new version back with the setContent
> >
> > call.
> >
> > > Dan
> > >
> > > On Fri December 18 2009 4:13:29 am Gary Gregory wrote:
> > > > Hi All:
> > > >
> > > > I need to apply an XSL transformation to messages coming out of CXF
> > >
> > > (our
> > >
> > > > users configure what the XSL looks like.) For a normal
> >
> > (successful)
> >
> > > > message, I have an interceptor (during Phase.PRE_MARSHAL) that
> >
> > uses
> >
> > > the
> > >
> > > > DOM aspect of a message. That works great. BTW, I get to the DOM
> > >
> > > like
> > >
> > > > this:
> > > >
> > > > Node node = (Node) message.getContent(List.class).get(0);
> > > >
> > > > That seems brittle, is there a safer way to get to an aspect of the
> > >
> > > message
> > >
> > > > I can feed to javax.xml.transform?
> > > >
> > > > The real issue comes with fault messages because the fault chain
> >
> > uses
> >
> > > an
> >
> > XMLStreamWriter<http://java.sun.com/javase/6/docs/api/javax/xml/stream/
> >
> > > XML
> > >
> > > > StreamWriter.html>. The fault chain looks like this:
> > > >
> > > > Chain org.apache.cxf.phase.PhaseInterceptorChain@3015b303. Current
> > >
> > > flow:
> > > > setup [ServerPolicyOutFaultInterceptor]
> > > > prepare-send [MessageSenderInterceptor,
> >
> > Soap11FaultOutInterceptor]
> >
> > > > pre-stream [LoggingOutInterceptor, XmlDeclOutInterceptor*,
> > > > StaxOutInterceptor] pre-protocol [WebFaultOutInterceptor,
> > > > SOAPHandlerFaultOutInterceptor] write [SoapOutInterceptor]
> > > > pre-marshal [LogicalHandlerFaultOutInterceptor]
> > > > marshal [Soap11FaultOutInterceptorInternal]
> > > > pre-stream-ending [StaxOutEndingInterceptor,
> > > > TransformOutFaultInterceptor*] prepare-send-ending
> > > > [MessageSenderEndingInterceptor]
> > > >
> > > > FYI, the interceptors marked with * are our own:
> > > >
> > > > * XmlDeclOutInterceptor forces an XML declaration to be
> > >
> > > written.
> > >
> > > > * TransformOutFaultInterceptor is where I thought I could
> > >
> > > transform
> > >
> > > > the fault XML message.
> > > >
> > > > The
> >
> > XMLStreamWriter<http://java.sun.com/javase/6/docs/api/javax/xml/stream/
> >
> > > XML
> > >
> > > > StreamWriter.html> looks like this:
> > > >
> > > > [StreamWriter: class com.ctc.wstx.sw.SimpleNsStreamWriter,
> >
> > underlying
> >
> > > > outputter:
> >
> > com.ctc.wstx.sw.ISOLatin1XmlWriter@1125cf44<mailto:com.ctc.wstx.sw.ISOL
> >
> > > ati
> > >
> > > > n1XmlWriter@1125cf44>
> > > >
> > > > The com.ctc.wstx.sw.ISOLatin1XmlWriter wraps a
> > > > org.apache.cxf.io.CachedOutputStream, which in turns wraps:
> > > >
> > > > * currentStream - LoadingByteArrayOutputStream
> > > >
> > > > * flowThroughStream -
> > >
> > > AbstractHTTPDestination$WrappedOutputStream
> > >
> > > > All of this to say that when the chain's interceptors are working
> > >
> > > with the
> > >
> > > > message's
> >
> > XMLStreamWriter<http://java.sun.com/javase/6/docs/api/javax/xml/stream/
> >
> > > XML
> > >
> > > > StreamWriter.html>, the bytes are cached and written to the wire.
> >
> > It
> >
> > > is not
> > >
> > > > possible to catch the fault XML message and change it.
> > > >
> > > > The only thing I've come up with but not implemented yet would be
> >
> > to
> >
> > > insert
> > >
> > > > an interceptor before the XML declaration is written and put the
> >
> > XMLStreamWriter<http://java.sun.com/javase/6/docs/api/javax/xml/stream/
> >
> > > XML
> > >
> > > > StreamWriter.html> into a temp spot in the message content map,
> >
> > then
> >
> > > put a
> > >
> > > > new
> >
> > XMLStreamWriter<http://java.sun.com/javase/6/docs/api/javax/xml/stream/
> >
> > > XML
> > >
> > > > StreamWriter.html> on a byte array in its place. A pre-stream-
> >
> > ending
> >
> > > > interceptor can take those bytes, apply XSL to them and then write
> > >
> > > them to
> > >
> > > > the original
> >
> > XMLStreamWriter<http://java.sun.com/javase/6/docs/api/javax/xml/stream/
> >
> > > XML
> > >
> > > > StreamWriter.html>, before putting the original
> >
> > XMLStreamWriter<http://java.sun.com/javase/6/docs/api/javax/xml/stream/
> >
> > > XML
> > >
> > > > StreamWriter.html> back in it original slot in the message content
> > >
> > > map.
> > >
> > > > That seems like big old hack.
> > > >
> > > > Any ideas on a cleaner solution?
> > > >
> > > > Thank you,
> > > > Gary Gregory
> > > > Seagull Software
> > > > ggregory@...
> > > > www.seagullsoftware.com
> > >
> > > --
> > > Daniel Kulp
> > > dkulp@...
> > > http://www.dankulp.com/blog
>

--
Daniel Kulp
dkulp@...
http://www.dankulp.com/blog

Re: Field Decrypts but does not unmarshall

2009-12-22T10:01:02Z

On Mon December 21 2009 4:31:54 pm Howard Points wrote:
> I have a field in an inbound request that is encrypted via WS-Security. I
> can step into the wss4j code and see the field is being decrypted properly,
> but the field is null when it gets into my endpoint impl. I am thinking
> that something is going wrong during the unmarshalling. The field of
> concern type is an xsd:any. I am using CxF 2.2.5. I set a breakpoint in
> SoapHeaderInterceptor and stepped through it, but did not see any problems.
> Is there a better place to set a breakpoint to debug this?

Hmm... you are probably down deep in JAXB at this point. Not sure how to
debug this. I guess my immediate suggestion would be to turn on schema
validation and seeing if that spits an error out.

Dan

>
> Does anyone know what's going wrong?
>
> Thanks,
> Howard
>

--
Daniel Kulp
dkulp@...
http://www.dankulp.com/blog

Re: Bean as endpoint implementor

2009-12-22T09:51:49Z

> <jaxws:endpoint id="myGlobManager"
> implementor="#myGlobManager"
> address="/myGlobManager"/>

The implementor attribute is pointing at itself. The jaxws:endpoint bean is
named myGlobManager and that's also the implementor? That's definitely not
right.

Most likely, you want something like:

<bean id="myGlobManagerImpl" class="com.......MyGlobManagerImpl"/>

<jaxws:endpoint id="myGlobManager"
implementor="#myGlobManagerImpl"
address="/myGlobManager"/>

Due to your Autowired things, you may also need a TabManager bean and similar
stuff defined in your beans.xml.

Dan

On Tue December 22 2009 12:35:08 pm Bill Li wrote:

> Hi folks,
>
> I have a working project and would like to introduce web service
> functionality here. I read around doc and successfully get a Foo service
> running. My env is Spring 2.5, Jetty 6/Tomat 6. But when I try to export my
> existing services, I continues hit spring exceptions. Let us come down to
> code.
>
> Interface
> ========
> @WebService(name="myGlobManager", targetNamespace="http://cxf.apache.org")
> public interface MyGlobManager {
> public MyGlob fetch();
> }
>
> Impl
> ========
> @Service(value = "myGlobManager")
> @WebService(endpointInterface="com.beelun.shoppro.service.MyGlobManager")
> public class MyGlobManagerImpl extends GenericDaoHibernate<MyGlob, Long>
> implements MyGlobManager {
> // A cache for myGlob
> private MyGlob myGlob = null;
>
> @Autowired
> public MyGlobManagerImpl(SessionFactory sessionFactory) {
> super(MyGlob.class, sessionFactory);
> }
>
> @Autowired
> TabManager tabManager;
>
> @Override
> public MyGlob fetch() {...}
>
> Config file
> =========
> <beans xmlns="http://www.springframework.org/schema/beans"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xmlns:jaxws="http://cxf.apache.org/jaxws"
> xsi:schemaLocation="http://www.springframework.org/schema/beans
>
> http://www.springframework.org/schema/beans/spring-beans.xsd
> http://cxf.apache.org/jaxws
> http://cxf.apache.org/schemas/jaxws.xsd">
>
> <import resource="classpath:META-INF/cxf/cxf.xml" />
> <import resource="classpath:META-INF/cxf/cxf-extension-soap.xml"/>
> <import resource="classpath:META-INF/cxf/cxf-servlet.xml" />
>
> <jaxws:endpoint id="fooManager"
>
> implementor="com.beelun.shoppro.service.impl.FooManagerImpl"
> address="/fooManager"/>
>
> <jaxws:endpoint id="myGlobManager"
> implementor="#myGlobManager"
> address="/myGlobManager"/>
>
> </beans>
>
> Exceptions
> =============
> 2009-12-23 01:12:25.099::WARN: Failed startup of context
> org.mortbay.jetty.plugin.Jetty6PluginWebAppContext@1478e67f
> {/,F:\shoppro\src\main\webapp}
> org.springframework.beans.factory.BeanCreationException: Error creating
> bean with name 'myGlobManager': Cannot resolve reference to bean
> 'myGlobManager' while setting constructor argument; nested exception is
> org.springframework.beans.factory.BeanCurrentlyInCreationException: Error
> creating bean with name 'myGlobManager': Requested bean is currently in
> creation: Is there an unresolvable circular reference?
> at
> org.springframework.beans.factory.support.BeanDefinitionValueResolver.resol
> veReference(BeanDefinitionValueResolver.java:275) at
> org.springframework.beans.factory.support.BeanDefinitionValueResolver.resol
> veValueIfNecessary(BeanDefinitionValueResolver.java:104) ....
>
> Any idea?
>
> Thanks.
>

--
Daniel Kulp
dkulp@...
http://www.dankulp.com/blog

RE: [DOSGI] cxf 2.2.5 in the DOSGI 1.2 snapshot download?

2009-12-22T09:38:40Z

Right, 2.2.4 works fine. Up til now, this has all been with single bundle though, currently working on getting the multi bundle up. Will let you know.

Thanks,
Thom

-----Original Message-----
From: David Bosschaert [mailto:david.bosschaert@...]
Sent: Tuesday, December 22, 2009 9:19 AM
To: users@...
Subject: Re: [DOSGI] cxf 2.2.5 in the DOSGI 1.2 snapshot download?

Does the stack trace not appear with CXF 2.2.4 and DOSGi 1.1?

David

2009/12/22 Shulok, Thomas <thomas.shulok@...>:

Bean as endpoint implementor

2009-12-22T09:35:08Z

Hi folks,

I have a working project and would like to introduce web service
functionality here. I read around doc and successfully get a Foo service
running. My env is Spring 2.5, Jetty 6/Tomat 6. But when I try to export my
existing services, I continues hit spring exceptions. Let us come down to
code.

Interface
========
@WebService(name="myGlobManager", targetNamespace="http://cxf.apache.org")
public interface MyGlobManager {
public MyGlob fetch();
}

Impl
========
@Service(value = "myGlobManager")
@WebService(endpointInterface="com.beelun.shoppro.service.MyGlobManager")
public class MyGlobManagerImpl extends GenericDaoHibernate<MyGlob, Long>
implements MyGlobManager {
// A cache for myGlob
private MyGlob myGlob = null;

@Autowired
public MyGlobManagerImpl(SessionFactory sessionFactory) {
super(MyGlob.class, sessionFactory);
}

@Autowired
TabManager tabManager;

@Override
public MyGlob fetch() {...}

Config file
=========
<beans xmlns="http://www.springframework.org/schema/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:jaxws="http://cxf.apache.org/jaxws"
xsi:schemaLocation="http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans.xsd
http://cxf.apache.org/jaxws
http://cxf.apache.org/schemas/jaxws.xsd">

<import resource="classpath:META-INF/cxf/cxf.xml" />
<import resource="classpath:META-INF/cxf/cxf-extension-soap.xml"/>
<import resource="classpath:META-INF/cxf/cxf-servlet.xml" />

<jaxws:endpoint id="fooManager"

implementor="com.beelun.shoppro.service.impl.FooManagerImpl"
address="/fooManager"/>

<jaxws:endpoint id="myGlobManager"
implementor="#myGlobManager"
address="/myGlobManager"/>

</beans>

Exceptions
=============
2009-12-23 01:12:25.099::WARN: Failed startup of context
org.mortbay.jetty.plugin.Jetty6PluginWebAppContext@1478e67f
{/,F:\shoppro\src\main\webapp}
org.springframework.beans.factory.BeanCreationException: Error creating bean
with name 'myGlobManager': Cannot resolve reference to bean 'myGlobManager'
while setting constructor argument; nested exception is
org.springframework.beans.factory.BeanCurrentlyInCreationException: Error
creating bean with name 'myGlobManager': Requested bean is currently in
creation: Is there an unresolvable circular reference?
at
org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:275)
at
org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:104)
....

Any idea?

Thanks.

--
Bill Li
http://BaliOnWeb.com

WSDLQueryException thrown when calling Webservice locally on same machine

2009-12-22T09:31:11Z

I had an issue a couple of years ago we still haven't resolved. Here is that ticket:

http://old.nabble.com/I-have-the-TRaX,-can-you-help--td16455965.html

I've since upgraded to CXF 2.2.5 and the TRAX is no longer getting thrown but this is:

11:12:24,949 ERROR [STDERR] Dec 22, 2009 11:12:24 AM org.apache.cxf.transport.servlet.ServletController invoke
WARNING: org.apache.cxf.transport.http.WSDLQueryHandler Exception caught writing response.
org.apache.cxf.transport.http.WSDLQueryException: Exception occurred while trying to process http://x.x.x.x:8080/WebApp/TestService?wsdl
at org.apache.cxf.transport.http.WSDLQueryHandler.writeResponse(WSDLQueryHandler.java:228)
at org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:156)
at org.apache.cxf.transport.servlet.AbstractCXFServlet.invoke(AbstractCXFServlet.java:142)
at org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:179)
at org.apache.cxf.transport.servlet.AbstractHTTPServlet.doGet(AbstractHTTPServlet.java:108)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:690)
at org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:159)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446)
at java.lang.Thread.run(Thread.java:619)
Caused by: com.ctc.wstx.exc.WstxIOException: null
at com.ctc.wstx.sw.BaseStreamWriter.finishDocument(BaseStreamWriter.java:1692)
at com.ctc.wstx.sw.BaseStreamWriter.writeEndDocument(BaseStreamWriter.java:585)
at org.apache.cxf.staxutils.StaxUtils.writeDocument(StaxUtils.java:575)
at org.apache.cxf.staxutils.StaxUtils.writeDocument(StaxUtils.java:557)
at org.apache.cxf.staxutils.StaxUtils.writeNode(StaxUtils.java:727)
at org.apache.cxf.transport.http.WSDLQueryHandler.writeResponse(WSDLQueryHandler.java:223)
... 24 more
Caused by: ClientAbortException: java.net.SocketException: Connection reset by peer: socket write error
at org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:319)
at org.apache.catalina.connector.OutputBuffer.flush(OutputBuffer.java:288)
at org.apache.catalina.connector.CoyoteOutputStream.flush(CoyoteOutputStream.java:98)
at com.ctc.wstx.io.UTF8Writer.flush(UTF8Writer.java:99)
at com.ctc.wstx.sw.BufferingXmlWriter.flush(BufferingXmlWriter.java:214)
at com.ctc.wstx.sw.BufferingXmlWriter.close(BufferingXmlWriter.java:194)
at com.ctc.wstx.sw.BaseStreamWriter.finishDocument(BaseStreamWriter.java:1690)
... 29 more
Caused by: java.net.SocketException: Connection reset by peer: socket write error
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
at org.apache.coyote.http11.InternalOutputBuffer.realWriteBytes(InternalOutputBuffer.java:737)
at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:434)
at org.apache.coyote.http11.InternalOutputBuffer.flush(InternalOutputBuffer.java:299)
at org.apache.coyote.http11.Http11Processor.action(Http11Processor.java:963)
at org.apache.coyote.Response.action(Response.java:183)
at org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:314)
... 35 more
11:12:24,961 ERROR [[CXFServlet]] Servlet.service() for servlet CXFServlet threw exception
java.net.SocketException: Connection reset by peer: socket write error
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
at org.apache.coyote.http11.InternalOutputBuffer.realWriteBytes(InternalOutputBuffer.java:737)
at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:434)
at org.apache.coyote.http11.InternalOutputBuffer.flush(InternalOutputBuffer.java:299)
at org.apache.coyote.http11.Http11Processor.action(Http11Processor.java:963)
at org.apache.coyote.Response.action(Response.java:183)
at org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:314)
at org.apache.catalina.connector.OutputBuffer.flush(OutputBuffer.java:288)
at org.apache.catalina.connector.CoyoteOutputStream.flush(CoyoteOutputStream.java:98)
at com.ctc.wstx.io.UTF8Writer.flush(UTF8Writer.java:99)
at com.ctc.wstx.sw.BufferingXmlWriter.flush(BufferingXmlWriter.java:214)
at com.ctc.wstx.sw.BufferingXmlWriter.close(BufferingXmlWriter.java:194)
at com.ctc.wstx.sw.BaseStreamWriter.finishDocument(BaseStreamWriter.java:1690)
at com.ctc.wstx.sw.BaseStreamWriter.writeEndDocument(BaseStreamWriter.java:585)
at org.apache.cxf.staxutils.StaxUtils.writeDocument(StaxUtils.java:575)
at org.apache.cxf.staxutils.StaxUtils.writeDocument(StaxUtils.java:557)
at org.apache.cxf.staxutils.StaxUtils.writeNode(StaxUtils.java:727)
at org.apache.cxf.transport.http.WSDLQueryHandler.writeResponse(WSDLQueryHandler.java:223)
at org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:156)
at org.apache.cxf.transport.servlet.AbstractCXFServlet.invoke(AbstractCXFServlet.java:142)
at org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:179)
at org.apache.cxf.transport.servlet.AbstractHTTPServlet.doGet(AbstractHTTPServlet.java:108)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:690)
at org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:159)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446)
at java.lang.Thread.run(Thread.java:619)

The weird thing it only gets thrown when calling it from my app when the app is on the same machine as the application server which is providing the service. It seems that any time a service call is made, this stack gets thrown. Here is what I get in the log from my app:

Dec 22, 2009 11:11:08 AM org.springframework.context.support.AbstractApplicationContext prepareRefresh
INFO: Refreshing org.apache.cxf.bus.spring.BusApplicationContext@e92aef: display name [org.apache.cxf.bus.spring.BusApplicationContext@e92aef]; startup date [Tue Dec 22 11:11:08 CST 2009]; root of context hierarchy
Dec 22, 2009 11:11:08 AM org.springframework.beans.factory.support.DefaultListableBeanFactory registerBeanDefinition
INFO: Overriding bean definition for bean 'org.apache.cxf.transport.http.policy.HTTPClientAssertionBuilder': replacing [Generic bean: class [org.apache.cxf.transport.http.policy.HTTPClientAssertionBuilder]; scope=singleton; abstract=false; lazyInit=false; autowireMode=0; dependencyCheck=0; autowireCandidate=true; primary=false; factoryBeanName=null; factoryMethodName=null; initMethodName=null; destroyMethodName=null; defined in URL [bundleresource://96.fwk15926420:2/META-INF/cxf/cxf-extension-http.fixml]] with [Generic bean: class [org.apache.cxf.transport.http.policy.HTTPClientAssertionBuilder]; scope=singleton; abstract=false; lazyInit=false; autowireMode=0; dependencyCheck=0; autowireCandidate=true; primary=false; factoryBeanName=null; factoryMethodName=null; initMethodName=null; destroyMethodName=null; defined in URL [bundleresource://96.fwk15926420:2/META-INF/cxf/cxf-extension-http.fixml]]
Dec 22, 2009 11:11:08 AM org.springframework.beans.factory.support.DefaultListableBeanFactory registerBeanDefinition
INFO: Overriding bean definition for bean 'org.apache.cxf.transport.http.policy.HTTPServerAssertionBuilder': replacing [Generic bean: class [org.apache.cxf.transport.http.policy.HTTPServerAssertionBuilder]; scope=singleton; abstract=false; lazyInit=false; autowireMode=0; dependencyCheck=0; autowireCandidate=true; primary=false; factoryBeanName=null; factoryMethodName=null; initMethodName=null; destroyMethodName=null; defined in URL [bundleresource://96.fwk15926420:2/META-INF/cxf/cxf-extension-http.fixml]] with [Generic bean: class [org.apache.cxf.transport.http.policy.HTTPServerAssertionBuilder]; scope=singleton; abstract=false; lazyInit=false; autowireMode=0; dependencyCheck=0; autowireCandidate=true; primary=false; factoryBeanName=null; factoryMethodName=null; initMethodName=null; destroyMethodName=null; defined in URL [bundleresource://96.fwk15926420:2/META-INF/cxf/cxf-extension-http.fixml]]
Dec 22, 2009 11:11:08 AM org.springframework.beans.factory.support.DefaultListableBeanFactory registerBeanDefinition
INFO: Overriding bean definition for bean 'org.apache.cxf.transport.http.policy.NoOpPolicyInterceptorProvider': replacing [Generic bean: class [org.apache.cxf.transport.http.policy.NoOpPolicyInterceptorProvider]; scope=singleton; abstract=false; lazyInit=false; autowireMode=0; dependencyCheck=0; autowireCandidate=true; primary=false; factoryBeanName=null; factoryMethodName=null; initMethodName=null; destroyMethodName=null; defined in URL [bundleresource://96.fwk15926420:2/META-INF/cxf/cxf-extension-http.fixml]] with [Generic bean: class [org.apache.cxf.transport.http.policy.NoOpPolicyInterceptorProvider]; scope=singleton; abstract=false; lazyInit=false; autowireMode=0; dependencyCheck=0; autowireCandidate=true; primary=false; factoryBeanName=null; factoryMethodName=null; initMethodName=null; destroyMethodName=null; defined in URL [bundleresource://96.fwk15926420:2/META-INF/cxf/cxf-extension-http.fixml]]
Dec 22, 2009 11:11:08 AM org.springframework.beans.factory.support.DefaultListableBeanFactory registerBeanDefinition
INFO: Overriding bean definition for bean 'org.apache.cxf.transport.http.ClientOnlyHTTPTransportFactory': replacing [Generic bean: class [org.apache.cxf.transport.http.ClientOnlyHTTPTransportFactory]; scope=singleton; abstract=false; lazyInit=true; autowireMode=0; dependencyCheck=0; autowireCandidate=true; primary=false; factoryBeanName=null; factoryMethodName=null; initMethodName=null; destroyMethodName=null; defined in URL [bundleresource://96.fwk15926420:2/META-INF/cxf/cxf-extension-http.fixml]] with [Generic bean: class [org.apache.cxf.transport.http.ClientOnlyHTTPTransportFactory]; scope=singleton; abstract=false; lazyInit=true; autowireMode=0; dependencyCheck=0; autowireCandidate=true; primary=false; factoryBeanName=null; factoryMethodName=null; initMethodName=null; destroyMethodName=null; defined in URL [bundleresource://96.fwk15926420:2/META-INF/cxf/cxf-extension-http.fixml]]
Dec 22, 2009 11:11:08 AM org.springframework.context.support.AbstractApplicationContext obtainFreshBeanFactory
INFO: Bean factory for application context [org.apache.cxf.bus.spring.BusApplicationContext@e92aef]: org.springframework.beans.factory.support.DefaultListableBeanFactory@1580d5e
Dec 22, 2009 11:11:09 AM org.springframework.beans.factory.support.DefaultListableBeanFactory preInstantiateSingletons
INFO: Pre-instantiating singletons in org.springframework.beans.factory.support.DefaultListableBeanFactory@1580d5e: defining beans [cxf,org.apache.cxf.bus.spring.BusApplicationListener,org.apache.cxf.bus.spring.BusWiringBeanFactoryPostProcessor,org.apache.cxf.bus.spring.Jsr250BeanPostProcessor,org.apache.cxf.bus.spring.BusExtensionPostProcessor,org.apache.cxf.resource.ResourceManager,org.apache.cxf.configuration.Configurer,org.apache.cxf.binding.BindingFactoryManager,org.apache.cxf.transport.DestinationFactoryManager,org.apache.cxf.transport.ConduitInitiatorManager,org.apache.cxf.wsdl.WSDLManager,org.apache.cxf.phase.PhaseManager,org.apache.cxf.workqueue.WorkQueueManager,org.apache.cxf.buslifecycle.BusLifeCycleManager,org.apache.cxf.endpoint.ServerRegistry,org.apache.cxf.endpoint.ServerLifeCycleManager,org.apache.cxf.endpoint.ClientLifeCycleManager,org.apache.cxf.transports.http.QueryHandlerRegistry,org.apache.cxf.endpoint.EndpointResolverRegistry,org.apache.cxf.headers.HeaderManager,org.apache.cxf.catalog.OASISCatalogManager,org.apache.cxf.endpoint.ServiceContractResolverRegistry,org.apache.cxf.binding.corba.CorbaBindingFactory,org.apache.cxf.binding.corba.wsdl.WSDLExtensionRegister#0,org.apache.cxf.jaxws.context.WebServiceContextResourceResolver,org.apache.cxf.jaxws.context.WebServiceContextImpl,org.apache.cxf.binding.soap.SoapBindingFactory,org.apache.cxf.binding.soap.SoapTransportFactory,org.apache.cxf.binding.soap.customEditorConfigurer,org.apache.cxf.binding.xml.XMLBindingFactory,org.apache.cxf.ws.addressing.policy.AddressingAssertionBuilder,org.apache.cxf.ws.addressing.policy.AddressingPolicyInterceptorProvider,org.apache.cxf.ws.addressing.policy.UsingAddressingAssertionBuilder,org.apache.cxf.javascript.JavascriptQueryHandlerRegistry,org.apache.cxf.transport.local.LocalTransportFactory,org.apache.cxf.transport.http.policy.HTTPClientAssertionBuilder,org.apache.cxf.transport.http.policy.HTTPServerAssertionBuilder,org.apache.cxf.transport.http.policy.NoOpPolicyInterceptorProvider,org.apache.cxf.transport.http.ClientOnlyHTTPTransportFactory,org.apache.cxf.management.InstrumentationManager,org.apache.cxf.transport.http_jetty.JettyHTTPTransportFactory,org.apache.cxf.transport.jms.JMSTransportFactory,org.apache.cxf.binding.object.ObjectBindingFactory,org.apache.cxf.binding.http.HttpBindingFactory,org.apache.cxf.jaxrs.JAXRSBindingFactory,org.apache.cxf.ws.security.policy.WSSecurityPolicyLoader,org.apache.cxf.ws.policy.AssertionBuilderRegistry,org.apache.cxf.ws.policy.PolicyInterceptorProviderRegistry,org.apache.cxf.ws.policy.attachment.external.DomainExpressionBuilderRegistry,org.apache.cxf.ws.policy.attachment.external.EndpointReferenceDomainExpressionBuilder,org.apache.cxf.ws.policy.PolicyBuilder,org.apache.cxf.ws.policy.PolicyEngine,org.apache.cxf.ws.policy.attachment.wsdl11.Wsdl11AttachmentPolicyProvider,org.apache.cxf.ws.policy.attachment.ServiceModelPolicyProvider,org.apache.cxf.ws.policy.mtom.MTOMAssertionBuilder,org.apache.cxf.ws.policy.mtom.MTOMPolicyInterceptorProvider,org.apache.cxf.ws.rm.RMManager,org.apache.cxf.ws.rm.policy.RMPolicyInterceptorProvider,org.apache.cxf.ws.rm.RMAssertionBuilder]; root of factory hierarchy
Dec 22, 2009 11:11:16 AM org.apache.cxf.configuration.spring.ConfigurerImpl getBeanName
INFO: Could not determine bean name for instance of class org.apache.cxf.jaxws.JaxWsClientFactoryBean.
Dec 22, 2009 11:11:16 AM org.apache.cxf.service.factory.ReflectionServiceFactoryBean buildServiceFromWSDL
INFO: Creating Service {http://<target namespace>/}TestServiceProviderService from WSDL: http://x.x.x.x:8080/WebApp/TestService?wsdl

Any ideas? It's as if the local call performs a client abort and then the server catchs it. Just very interesting I don't get this error when using my client app on a remote machine.

Re: [DOSGI] cxf 2.2.5 in the DOSGI 1.2 snapshot download?

2009-12-22T09:18:36Z

Does the stack trace not appear with CXF 2.2.4 and DOSGi 1.1?

David

2009/12/22 Shulok, Thomas <thomas.shulok@...>:

> Hi David,
>
> Understood, that should work for me, but...injecting the cxf-bundle-minimal-2.2.5.jar into the 1.1 release generates the same stack trace as the 1.2 jar (both single bundle distros).
>
> Thanks,
> Thom
>
> -----Original Message-----
> From: David Bosschaert [mailto:david.bosschaert@...]
> Sent: Tuesday, December 22, 2009 7:23 AM
> To: users@...
> Subject: Re: [DOSGI] cxf 2.2.5 in the DOSGI 1.2 snapshot download?
>
> Hi Thomas,
>
> The 1.2-SNAPSHOT CXF-DOSGi trunk is under heavy refactoring at the moment, I'm happy to take a look at that stack trace once it's settled down, hopefully in a few weeks time. For now, please try if you can stick to the 1.1 release.
>
> From memory, I have seen stack traces like the one you're posting here. In some cases they did happen with the single-bundle distro but not with the multi-bundle distro. In some cases they have been harmless (just a validation error, but things continue to work).
>
> Best regards,
>
> David
>
> 2009/12/22 Shulok, Thomas <thomas.shulok@...>:
>> Thanks David. Will try out the next snapshot build.
>>
>> Yesterday, I did try what you suggested (today), but with the 1.2 snapshot, and I got the following...
>>
>> Thanks,
>> Thom
>>
>> Dec 21, 2009 2:14:38 PM org.apache.cxf.dosgi.dsw.OsgiUtils
>> readIntentMap
>> WARNING: Intent map load failed:
>> org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException:
>> Line 48 i n XML document from OSGi
>> resource[classpath:/OSGI-INF/cxf/intents/intent-map.xml
>> |bnd.id=2|bnd.sym=cxf-dosgi-ri-singlebundle-distribution] is invalid;
>> |nested exc
>> eption is org.xml.sax.SAXParseException: cvc-complex-type.2.4.c: The matching wi ldcard is strict, but no declaration can be found for element 'p:policies'.
>> at
>> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadB
>> eanDefinitions(XmlBeanDefinitionReader.java:404)
>> at
>> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBea
>> nDefinitions(XmlBeanDefinitionReader.java:342)
>> at
>> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBea
>> nDefinitions(XmlBeanDefinitionReader.java:310)
>> at
>> org.springframework.beans.factory.support.AbstractBeanDefinitionReade
>> r.loadBeanDefinitions(AbstractBeanDefinitionReader.java:143)
>> at
>> org.springframework.beans.factory.support.AbstractBeanDefinitionReade
>> r.loadBeanDefinitions(AbstractBeanDefinitionReader.java:178)
>> at
>> org.springframework.beans.factory.support.AbstractBeanDefinitionReade
>> r.loadBeanDefinitions(AbstractBeanDefinitionReader.java:149)
>> at
>> org.springframework.osgi.context.support.OsgiBundleXmlApplicationCont
>> ext.loadBeanDefinitions(OsgiBundleXmlApplicationContext.java:176)
>> at
>> org.springframework.osgi.context.support.OsgiBundleXmlApplicationCont
>> ext.loadBeanDefinitions(OsgiBundleXmlApplicationContext.java:142)
>> at
>> org.springframework.context.support.AbstractRefreshableApplicationCon
>> text.refreshBeanFactory(AbstractRefreshableApplicationContext.java:123
>> )
>> at
>> org.springframework.context.support.AbstractApplicationContext.obtain
>> FreshBeanFactory(AbstractApplicationContext.java:422)
>> at
>> org.springframework.context.support.AbstractApplicationContext.refres
>> h(AbstractApplicationContext.java:352)
>> at
>> org.springframework.osgi.context.support.AbstractDelegatedExecutionAp
>> plicationContext.access$301(AbstractDelegatedExecutionApplicationConte
>> xt.java:69
>> )
>> at
>> org.springframework.osgi.context.support.AbstractDelegatedExecutionAp
>> plicationContext$1.run(AbstractDelegatedExecutionApplicationContext.ja
>> va:186)
>> at
>> org.springframework.osgi.util.internal.PrivilegedUtils.executeWithCus
>> tomTCCL(PrivilegedUtils.java:85)
>> at
>> org.springframework.osgi.context.support.AbstractDelegatedExecutionAp
>> plicationContext.normalRefresh(AbstractDelegatedExecutionApplicationCo
>> ntext.java
>> :182)
>> at
>> org.springframework.osgi.context.support.AbstractDelegatedExecutionAp
>> plicationContext$NoDependenciesWaitRefreshExecutor.refresh(AbstractDel
>> egatedExec
>> utionApplicationContext.java:89)
>> at
>> org.springframework.osgi.context.support.AbstractDelegatedExecutionAp
>> plicationContext.refresh(AbstractDelegatedExecutionApplicationContext.
>> java:175)
>> at
>> org.apache.cxf.dosgi.dsw.OsgiUtils.readIntentMap(OsgiUtils.java:401)
>> at
>> org.apache.cxf.dosgi.dsw.OsgiUtils.getIntentMap(OsgiUtils.java:376)
>> at
>> org.apache.cxf.dosgi.dsw.Activator.getIntentMap(Activator.java:96)
>> at
>> org.apache.cxf.dosgi.dsw.Activator.registerRemoteServiceAdminService(
>> Activator.java:78)
>> at org.apache.cxf.dosgi.dsw.Activator.start(Activator.java:55)
>> at
>> org.apache.cxf.dosgi.singlebundle.AggregatedActivator.startEmbeddedAc
>> tivators(AggregatedActivator.java:115)
>> at
>> org.apache.cxf.dosgi.singlebundle.AggregatedActivator.start(Aggregate
>> dActivator.java:46)
>> at
>> org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(Bund
>> leContextImpl.java:783)
>> at java.security.AccessController.doPrivileged(Native Method)
>> at
>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActiv
>> ator(BundleContextImpl.java:774)
>> at
>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(Bund
>> leContextImpl.java:755)
>> at
>> org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(Bundl
>> eHost.java:352)
>> at
>> org.eclipse.osgi.framework.internal.core.AbstractBundle.start(Abstrac
>> tBundle.java:280)
>> at
>> org.eclipse.osgi.framework.internal.core.AbstractBundle.start(Abstrac
>> tBundle.java:272)
>> at
>> org.eclipse.osgi.framework.internal.core.FrameworkCommandProvider._st
>> art(FrameworkCommandProvider.java:253)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown
>> Source)
>> at java.lang.reflect.Method.invoke(Unknown Source)
>> at org.eclipse.osgi.framework.internal.core.FrameworkCommandInterpreter.
>> execute(FrameworkCommandInterpreter.java:155)
>> at
>> org.eclipse.osgi.framework.internal.core.FrameworkConsole.docommand(F
>> rameworkConsole.java:303)
>> at
>> org.eclipse.osgi.framework.internal.core.FrameworkConsole.console(Fra
>> meworkConsole.java:288)
>> at
>> org.eclipse.osgi.framework.internal.core.FrameworkConsole.run(Framewo
>> rkConsole.java:224)
>> at java.lang.Thread.run(Unknown Source) Caused by: org.xml.sax.SAXParseException: cvc-complex-type.2.4.c: The matching w ildcard is strict, but no declaration can be found for element 'p:policies'.
>> at
>> com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAX
>> ParseException(Unknown Source)
>> at
>> com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.error(Unk
>> nown Source)
>> at
>> com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(
>> Unknown Source)
>> at
>> com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(
>> Unknown Source)
>> at
>> com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator$XSIErro
>> rReporter.reportError(Unknown Source)
>> at
>> com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.reportS
>> chemaError(Unknown Source)
>> at
>> com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.handleS
>> tartElement(Unknown Source)
>> at
>> com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.startEl
>> ement(Unknown Source)
>> at
>> com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scan
>> StartElement(Unknown Source)
>> at
>> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImp
>> l$FragmentContentDispatcher.dispatch(Unknown Source)
>> at
>> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImp
>> l.scanDocument(Unknown Source)
>> at
>> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(U
>> nknown Source)
>> at
>> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(U
>> nknown Source)
>> at
>> com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(Unknown So
>> urce)
>> at
>> com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(Unknown So
>> urce)
>> at
>> com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(Unk
>> nown Source)
>> at
>> org.springframework.beans.factory.xml.DefaultDocumentLoader.loadDocum
>> ent(DefaultDocumentLoader.java:75)
>> at
>> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadB
>> eanDefinitions(XmlBeanDefinitionReader.java:396)
>> ... 40 more
>> Dec 21, 2009 2:14:38 PM org.apache.cxf.dosgi.dsw.qos.IntentMap
>> setIntents
>> INFO: Injected intents: {}
>> java.lang.UnsupportedClassVersionError: Bad version number in .class
>> file
>> at java.lang.ClassLoader.defineClass1(Native Method)
>> at java.lang.ClassLoader.defineClass(Unknown Source)
>> at
>> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.defineClass(
>> DefaultClassLoader.java:183)
>> at
>> org.eclipse.osgi.baseadaptor.loader.ClasspathManager.defineClass(Clas
>> spathManager.java:576)
>> at
>> org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findClassImpl(Cl
>> asspathManager.java:546)
>> at
>> org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClassIm
>> pl(ClasspathManager.java:477)
>> at
>> org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass_L
>> ockClassLoader(ClasspathManager.java:465)
>> at
>> org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(C
>> lasspathManager.java:445)
>> at
>> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalCla
>> ss(DefaultClassLoader.java:211)
>> at
>> org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLo
>> ader.java:381)
>> at
>> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(Bundl
>> eLoader.java:457)
>> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.
>> java:410)
>> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.
>> java:398)
>> at
>> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(De
>> faultClassLoader.java:105)
>> at java.lang.ClassLoader.loadClass(Unknown Source)
>> at java.lang.ClassLoader.loadClassInternal(Unknown Source)
>> at java.lang.ClassLoader.defineClass1(Native Method)
>> at java.lang.ClassLoader.defineClass(Unknown Source)
>> at
>> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.defineClass(
>> DefaultClassLoader.java:183)
>> at
>> org.eclipse.osgi.baseadaptor.loader.ClasspathManager.defineClass(Clas
>> spathManager.java:576)
>> at
>> org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findClassImpl(Cl
>> asspathManager.java:546)
>> at
>> org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClassIm
>> pl(ClasspathManager.java:477)
>> at
>> org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass_L
>> ockClassLoader(ClasspathManager.java:465)
>> at
>> org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(C
>> lasspathManager.java:445)
>> at
>> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalCla
>> ss(DefaultClassLoader.java:211)
>> at
>> org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLo
>> ader.java:381)
>> at
>> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(Bundl
>> eLoader.java:457)
>> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.
>> java:410)
>> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.
>> java:398)
>> at
>> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(De
>> faultClassLoader.java:105)
>> at java.lang.ClassLoader.loadClass(Unknown Source)
>> at java.lang.ClassLoader.loadClassInternal(Unknown Source)
>> at
>> org.apache.cxf.dosgi.discovery.zookeeper.Activator.createZooKeeperDis
>> covery(Activator.java:112)
>> at
>> org.apache.cxf.dosgi.discovery.zookeeper.Activator.start(Activator.ja
>> va:46)
>> at
>> org.apache.cxf.dosgi.singlebundle.AggregatedActivator.startEmbeddedAc
>> tivators(AggregatedActivator.java:115)
>> at
>> org.apache.cxf.dosgi.singlebundle.AggregatedActivator.start(Aggregate
>> dActivator.java:46)
>> at
>> org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(Bund
>> leContextImpl.java:783)
>> at java.security.AccessController.doPrivileged(Native Method)
>> at
>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActiv
>> ator(BundleContextImpl.java:774)
>> at
>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(Bund
>> leContextImpl.java:755)
>> at
>> org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(Bundl
>> eHost.java:352)
>> at
>> org.eclipse.osgi.framework.internal.core.AbstractBundle.start(Abstrac
>> tBundle.java:280)
>> at
>> org.eclipse.osgi.framework.internal.core.AbstractBundle.start(Abstrac
>> tBundle.java:272)
>> at
>> org.eclipse.osgi.framework.internal.core.FrameworkCommandProvider._st
>> art(FrameworkCommandProvider.java:253)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown
>> Source)
>> at java.lang.reflect.Method.invoke(Unknown Source)
>> at org.eclipse.osgi.framework.internal.core.FrameworkCommandInterpreter.
>> execute(FrameworkCommandInterpreter.java:155)
>> at
>> org.eclipse.osgi.framework.internal.core.FrameworkConsole.docommand(F
>> rameworkConsole.java:303)
>> at
>> org.eclipse.osgi.framework.internal.core.FrameworkConsole.console(Fra
>> meworkConsole.java:288)
>> at
>> org.eclipse.osgi.framework.internal.core.FrameworkConsole.run(Framewo
>> rkConsole.java:224)
>> at java.lang.Thread.run(Unknown Source) Dec 21, 2009 2:14:38 PM
>> org.apache.cxf.dosgi.topologymanager.Activator start
>> INFO: TopologyManager: start()
>> Dec 21, 2009 2:14:38 PM
>> org.apache.cxf.dosgi.topologymanager.RemoteServiceAdminL
>> ist$1 addingService
>> INFO: Adding RemoteServiceAdmin to list of admins Dec 21, 2009 2:14:38
>> PM org.apache.cxf.dosgi.topologymanager.RemoteServiceAdminL
>> ist$1 addingService
>> INFO: enlisted RemoteEventAdmins: 0
>> Dec 21, 2009 2:14:38 PM
>> org.apache.cxf.dosgi.topologymanager.TopologyManager tri
>> ggerExportImportForRemoteSericeAdmin
>> INFO: TopologyManager: triggerExportImportForRemoteSericeAdmin()
>> Dec 21, 2009 2:14:38 PM
>> org.apache.cxf.dosgi.topologymanager.TopologyManagerImpo
>> rt triggerExportImportForRemoteSericeAdmin
>> SEVERE: NOT IMPLEMENTED !!!
>> Dec 21, 2009 2:14:38 PM
>> org.apache.cxf.dosgi.topologymanager.EndpointListenerImp
>> l getRegistrationProperties
>> INFO: EndpointListener: current filter: []
>>
>> -----Original Message-----
>> From: David Bosschaert [mailto:david.bosschaert@...]
>> Sent: Tuesday, December 22, 2009 6:27 AM
>> To: users@...
>> Subject: Re: [DOSGI] cxf 2.2.5 in the DOSGI 1.2 snapshot download?
>>
>> I've just updated CXF/DOSGi trunk to use CXF 2.2.5
>>
>> BTW you should be able to use CXF 2.2.5 with the DOSGI 1.1 release. In the multi bundle distro, just replace the cxf-bundle-minimal-2.2.5.jar with the 2.2.5 version. Haven't tried it but it should work...
>>
>> Cheers,
>>
>> David
>>
>> 2009/12/22 David Bosschaert <david.bosschaert@...>:
>>> Hi Thomas,
>>>
>>> Hmmm, I would think so, but the 1.1 release also has 2.2.4.
>>> I'll update the build system to pick up 2.2.5.
>>>
>>> BTW I *really* advise you to use the 1.1 release and not 1.2-SNAPSHOT
>>> at this moment in time as there is a lot of refactoring going on @
>>> dosgi trunk [1]. So unless you like living on the edge I would go for
>>> the 1.1 release :)
>>>
>>> Cheers,
>>>
>>> David
>>>
>>> [1]
>>> http://old.nabble.com/Migrating-CXF-DOSGi-to-be-complaint-with-the-ne
>>> w -OSGi-Remote-Service--Admin-spec-td26645023.html
>>>
>>> 2009/12/21 Shulok, Thomas <thomas.shulok@...>:
>>>> Hi All,
>>>>
>>>> Just downloaded the lastest 1.2 snapshot, and it still has cxf-bundle-minimal-2.2.4.jar. Should this be 2.2.5 now?
>>>>
>>>> Thanks,
>>>> Thom
>>>>
>>>
>>
>

Re: jms-spec-demo example in apache-cxf-2.3.0-SNAPSHOT: No DestinationFactory was found ....

2009-12-22T09:12:31Z

The samples, since we don't rebuild them and deploy them and such as part of
the release process, use a version for cxf of
"<cxf.version>[2,)</cxf.version>" and also don't include the snapshot repos by
default.

Can you try running with:

mvn -Pserver,snapshots -Dcxf.version=2.3.0-SNAPSHOT

That should force it into using the latest 2.3.0-SNAPSHOTs and provide the
repo for it to use. Most likely, with just "mvn -Pserver", it's grabbing
2.2.5 from central and using that.

Dan

On Tue December 22 2009 9:11:07 am Nguyen Tien Luong wrote:

> Hi,
>
> I'm trying to run jms-spec-demo example in the snapshot version of CXF
> (apache-cxf-2.3.0-SNAPSHOT-src)
> I used maven for building.
>
> mvn install (this will build the demo) <--- It's OK
> In separate command windows/shells:
> mvn -Pjms.broker <--- It's OK
> mvn -Pserver <--- error raises here
>
>
> __________________________________________________________
> [ERROR] BUILD ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] An exception occured while executing the Java class. null
> No DestinationFactory was found for the namespace
> http://www.w3.org/2008/07/soap/bindings/JMS/. [INFO]
> ------------------------------------------------------------------------
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: An exception
> occured while executing the Java class. null at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLi
> fecycleExecutor.java:583) at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecyc
> le(DefaultLifecycleExecutor.java:499) at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLif
> ecycleExecutor.java:478) at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFa
> ilures(DefaultLifecycleExecutor.java:330) at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(De
> faultLifecycleExecutor.java:291) at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecyc
> leExecutor.java:142) at
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at
> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at
> org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:
> 39) at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorIm
> pl.java:25) at java.lang.reflect.Method.invoke(Method.java:585)
> at
> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at
> org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at
> org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by:
> org.apache.maven.plugin.MojoExecutionException: An exception occured while
> executing the Java class. null at
> org.codehaus.mojo.exec.ExecJavaMojo.execute(ExecJavaMojo.java:338) at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMana
> ger.java:451) at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLi
> fecycleExecutor.java:558) ... 16 more
> Caused by: java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:
> 39) at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorIm
> pl.java:25) at java.lang.reflect.Method.invoke(Method.java:585)
> at org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:283)
> at java.lang.Thread.run(Thread.java:595)
> Caused by: javax.xml.ws.WebServiceException:
> org.apache.cxf.service.factory.ServiceConstructionException at
> org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:275) at
> org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:209) at
> org.apache.cxf.jaxws.spi.ProviderImpl.createAndPublishEndpoint(ProviderImp
> l.java:84) at javax.xml.ws.Endpoint.publish(Endpoint.java:47)
> at demo.jms_greeter.server.Server.<init>(Server.java:32)
> at demo.jms_greeter.server.Server.main(Server.java:37)
> ... 6 more
> Caused by: org.apache.cxf.service.factory.ServiceConstructionException
> at
> org.apache.cxf.frontend.ServerFactoryBean.create(ServerFactoryBean.java:12
> 5) at
> org.apache.cxf.jaxws.JaxWsServerFactoryBean.create(JaxWsServerFactoryBean.
> java:167) at
> org.apache.cxf.jaxws.EndpointImpl.getServer(EndpointImpl.java:346) at
> org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:259) ... 11
> more
> Caused by: org.apache.cxf.BusException: No DestinationFactory was found for
> the namespace http://www.w3.org/2008/07/soap/bindings/JMS/. at
> org..apache.cxf.transport.DestinationFactoryManagerImpl.getDestinationFact
> ory(DestinationFactoryManagerImpl.java:115) at
> org.apache.cxf.endpoint.ServerImpl.initDestination(ServerImpl.java:85) at
> org.apache.cxf.endpoint.ServerImpl.<init>(ServerImpl.java:69) at
> org.apache.cxf.frontend.ServerFactoryBean.create(ServerFactoryBean.java:10
> 6) ... 14 more
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 12 seconds
> [INFO] Finished at: Tue Dec 22 14:50:07 CET 2009
> [INFO] Final Memory: 38M/64M
> [INFO]
> ------------------------------------------------------------------------
> __________________________________________________________
>
>
> Because the SOAP over JMS specification feature described here is a new
> feature under development for CXF 2.3, so I don't know this error relates
> to the snapshot version or it's my configuration that cause this thing.
>
> Any help is appriciated
>
> Thanks
> =========================================================================
> NGUYEN Tien Luong | M2PGI - UFRIMAG
> 13 Rue Blanche MONIER | Tel :
> 06.45.42.46.33 38000 GRENOBLE |
> http://tienluong.info
>

--
Daniel Kulp
dkulp@...
http://www.dankulp.com/blog

RE: [DOSGI] cxf 2.2.5 in the DOSGI 1.2 snapshot download?

2009-12-22T08:54:00Z

Hi David,

Understood, that should work for me, but...injecting the cxf-bundle-minimal-2.2.5.jar into the 1.1 release generates the same stack trace as the 1.2 jar (both single bundle distros).

Thanks,
Thom

-----Original Message-----
From: David Bosschaert [mailto:david.bosschaert@...]
Sent: Tuesday, December 22, 2009 7:23 AM
To: users@...
Subject: Re: [DOSGI] cxf 2.2.5 in the DOSGI 1.2 snapshot download?

Hi Thomas,

The 1.2-SNAPSHOT CXF-DOSGi trunk is under heavy refactoring at the moment, I'm happy to take a look at that stack trace once it's settled down, hopefully in a few weeks time. For now, please try if you can stick to the 1.1 release.

From memory, I have seen stack traces like the one you're posting here. In some cases they did happen with the single-bundle distro but not with the multi-bundle distro. In some cases they have been harmless (just a validation error, but things continue to work).

Best regards,

David

2009/12/22 Shulok, Thomas <thomas.shulok@...>:

> Thanks David. Will try out the next snapshot build.
>
> Yesterday, I did try what you suggested (today), but with the 1.2 snapshot, and I got the following...
>
> Thanks,
> Thom
>
> Dec 21, 2009 2:14:38 PM org.apache.cxf.dosgi.dsw.OsgiUtils
> readIntentMap
> WARNING: Intent map load failed:
> org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException:
> Line 48 i n XML document from OSGi
> resource[classpath:/OSGI-INF/cxf/intents/intent-map.xml
> |bnd.id=2|bnd.sym=cxf-dosgi-ri-singlebundle-distribution] is invalid;
> |nested exc
> eption is org.xml.sax.SAXParseException: cvc-complex-type.2.4.c: The matching wi ldcard is strict, but no declaration can be found for element 'p:policies'.
> at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadB
> eanDefinitions(XmlBeanDefinitionReader.java:404)
> at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBea
> nDefinitions(XmlBeanDefinitionReader.java:342)
> at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBea
> nDefinitions(XmlBeanDefinitionReader.java:310)
> at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReade
> r.loadBeanDefinitions(AbstractBeanDefinitionReader.java:143)
> at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReade
> r.loadBeanDefinitions(AbstractBeanDefinitionReader.java:178)
> at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReade
> r.loadBeanDefinitions(AbstractBeanDefinitionReader.java:149)
> at
> org.springframework.osgi.context.support.OsgiBundleXmlApplicationCont
> ext.loadBeanDefinitions(OsgiBundleXmlApplicationContext.java:176)
> at
> org.springframework.osgi.context.support.OsgiBundleXmlApplicationCont
> ext.loadBeanDefinitions(OsgiBundleXmlApplicationContext.java:142)
> at
> org.springframework.context.support.AbstractRefreshableApplicationCon
> text.refreshBeanFactory(AbstractRefreshableApplicationContext.java:123
> )
> at
> org.springframework.context.support.AbstractApplicationContext.obtain
> FreshBeanFactory(AbstractApplicationContext.java:422)
> at
> org.springframework.context.support.AbstractApplicationContext.refres
> h(AbstractApplicationContext.java:352)
> at
> org.springframework.osgi.context.support.AbstractDelegatedExecutionAp
> plicationContext.access$301(AbstractDelegatedExecutionApplicationConte
> xt.java:69
> )
> at
> org.springframework.osgi.context.support.AbstractDelegatedExecutionAp
> plicationContext$1.run(AbstractDelegatedExecutionApplicationContext.ja
> va:186)
> at
> org.springframework.osgi.util.internal.PrivilegedUtils.executeWithCus
> tomTCCL(PrivilegedUtils.java:85)
> at
> org.springframework.osgi.context.support.AbstractDelegatedExecutionAp
> plicationContext.normalRefresh(AbstractDelegatedExecutionApplicationCo
> ntext.java
> :182)
> at
> org.springframework.osgi.context.support.AbstractDelegatedExecutionAp
> plicationContext$NoDependenciesWaitRefreshExecutor.refresh(AbstractDel
> egatedExec
> utionApplicationContext.java:89)
> at
> org.springframework.osgi.context.support.AbstractDelegatedExecutionAp
> plicationContext.refresh(AbstractDelegatedExecutionApplicationContext.
> java:175)
> at
> org.apache.cxf.dosgi.dsw.OsgiUtils.readIntentMap(OsgiUtils.java:401)
> at
> org.apache.cxf.dosgi.dsw.OsgiUtils.getIntentMap(OsgiUtils.java:376)
> at
> org.apache.cxf.dosgi.dsw.Activator.getIntentMap(Activator.java:96)
> at
> org.apache.cxf.dosgi.dsw.Activator.registerRemoteServiceAdminService(
> Activator.java:78)
> at org.apache.cxf.dosgi.dsw.Activator.start(Activator.java:55)
> at
> org.apache.cxf.dosgi.singlebundle.AggregatedActivator.startEmbeddedAc
> tivators(AggregatedActivator.java:115)
> at
> org.apache.cxf.dosgi.singlebundle.AggregatedActivator.start(Aggregate
> dActivator.java:46)
> at
> org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(Bund
> leContextImpl.java:783)
> at java.security.AccessController.doPrivileged(Native Method)
> at
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActiv
> ator(BundleContextImpl.java:774)
> at
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(Bund
> leContextImpl.java:755)
> at
> org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(Bundl
> eHost.java:352)
> at
> org.eclipse.osgi.framework.internal.core.AbstractBundle.start(Abstrac
> tBundle.java:280)
> at
> org.eclipse.osgi.framework.internal.core.AbstractBundle.start(Abstrac
> tBundle.java:272)
> at
> org.eclipse.osgi.framework.internal.core.FrameworkCommandProvider._st
> art(FrameworkCommandProvider.java:253)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown
> Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at org.eclipse.osgi.framework.internal.core.FrameworkCommandInterpreter.
> execute(FrameworkCommandInterpreter.java:155)
> at
> org.eclipse.osgi.framework.internal.core.FrameworkConsole.docommand(F
> rameworkConsole.java:303)
> at
> org.eclipse.osgi.framework.internal.core.FrameworkConsole.console(Fra
> meworkConsole.java:288)
> at
> org.eclipse.osgi.framework.internal.core.FrameworkConsole.run(Framewo
> rkConsole.java:224)
> at java.lang.Thread.run(Unknown Source) Caused by: org.xml.sax.SAXParseException: cvc-complex-type.2.4.c: The matching w ildcard is strict, but no declaration can be found for element 'p:policies'.
> at
> com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAX
> ParseException(Unknown Source)
> at
> com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.error(Unk
> nown Source)
> at
> com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(
> Unknown Source)
> at
> com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(
> Unknown Source)
> at
> com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator$XSIErro
> rReporter.reportError(Unknown Source)
> at
> com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.reportS
> chemaError(Unknown Source)
> at
> com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.handleS
> tartElement(Unknown Source)
> at
> com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.startEl
> ement(Unknown Source)
> at
> com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scan
> StartElement(Unknown Source)
> at
> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImp
> l$FragmentContentDispatcher.dispatch(Unknown Source)
> at
> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImp
> l.scanDocument(Unknown Source)
> at
> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(U
> nknown Source)
> at
> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(U
> nknown Source)
> at
> com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(Unknown So
> urce)
> at
> com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(Unknown So
> urce)
> at
> com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(Unk
> nown Source)
> at
> org.springframework.beans.factory.xml.DefaultDocumentLoader.loadDocum
> ent(DefaultDocumentLoader.java:75)
> at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadB
> eanDefinitions(XmlBeanDefinitionReader.java:396)
> ... 40 more
> Dec 21, 2009 2:14:38 PM org.apache.cxf.dosgi.dsw.qos.IntentMap
> setIntents
> INFO: Injected intents: {}
> java.lang.UnsupportedClassVersionError: Bad version number in .class
> file
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClass(Unknown Source)
> at
> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.defineClass(
> DefaultClassLoader.java:183)
> at
> org.eclipse.osgi.baseadaptor.loader.ClasspathManager.defineClass(Clas
> spathManager.java:576)
> at
> org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findClassImpl(Cl
> asspathManager.java:546)
> at
> org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClassIm
> pl(ClasspathManager.java:477)
> at
> org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass_L
> ockClassLoader(ClasspathManager.java:465)
> at
> org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(C
> lasspathManager.java:445)
> at
> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalCla
> ss(DefaultClassLoader.java:211)
> at
> org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLo
> ader.java:381)
> at
> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(Bundl
> eLoader.java:457)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.
> java:410)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.
> java:398)
> at
> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(De
> faultClassLoader.java:105)
> at java.lang.ClassLoader.loadClass(Unknown Source)
> at java.lang.ClassLoader.loadClassInternal(Unknown Source)
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClass(Unknown Source)
> at
> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.defineClass(
> DefaultClassLoader.java:183)
> at
> org.eclipse.osgi.baseadaptor.loader.ClasspathManager.defineClass(Clas
> spathManager.java:576)
> at
> org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findClassImpl(Cl
> asspathManager.java:546)
> at
> org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClassIm
> pl(ClasspathManager.java:477)
> at
> org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass_L
> ockClassLoader(ClasspathManager.java:465)
> at
> org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(C
> lasspathManager.java:445)
> at
> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalCla
> ss(DefaultClassLoader.java:211)
> at
> org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLo
> ader.java:381)
> at
> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(Bundl
> eLoader.java:457)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.
> java:410)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.
> java:398)
> at
> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(De
> faultClassLoader.java:105)
> at java.lang.ClassLoader.loadClass(Unknown Source)
> at java.lang.ClassLoader.loadClassInternal(Unknown Source)
> at
> org.apache.cxf.dosgi.discovery.zookeeper.Activator.createZooKeeperDis
> covery(Activator.java:112)
> at
> org.apache.cxf.dosgi.discovery.zookeeper.Activator.start(Activator.ja
> va:46)
> at
> org.apache.cxf.dosgi.singlebundle.AggregatedActivator.startEmbeddedAc
> tivators(AggregatedActivator.java:115)
> at
> org.apache.cxf.dosgi.singlebundle.AggregatedActivator.start(Aggregate
> dActivator.java:46)
> at
> org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(Bund
> leContextImpl.java:783)
> at java.security.AccessController.doPrivileged(Native Method)
> at
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActiv
> ator(BundleContextImpl.java:774)
> at
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(Bund
> leContextImpl.java:755)
> at
> org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(Bundl
> eHost.java:352)
> at
> org.eclipse.osgi.framework.internal.core.AbstractBundle.start(Abstrac
> tBundle.java:280)
> at
> org.eclipse.osgi.framework.internal.core.AbstractBundle.start(Abstrac
> tBundle.java:272)
> at
> org.eclipse.osgi.framework.internal.core.FrameworkCommandProvider._st
> art(FrameworkCommandProvider.java:253)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown
> Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at org.eclipse.osgi.framework.internal.core.FrameworkCommandInterpreter.
> execute(FrameworkCommandInterpreter.java:155)
> at
> org.eclipse.osgi.framework.internal.core.FrameworkConsole.docommand(F
> rameworkConsole.java:303)
> at
> org.eclipse.osgi.framework.internal.core.FrameworkConsole.console(Fra
> meworkConsole.java:288)
> at
> org.eclipse.osgi.framework.internal.core.FrameworkConsole.run(Framewo
> rkConsole.java:224)
> at java.lang.Thread.run(Unknown Source) Dec 21, 2009 2:14:38 PM
> org.apache.cxf.dosgi.topologymanager.Activator start
> INFO: TopologyManager: start()
> Dec 21, 2009 2:14:38 PM
> org.apache.cxf.dosgi.topologymanager.RemoteServiceAdminL
> ist$1 addingService
> INFO: Adding RemoteServiceAdmin to list of admins Dec 21, 2009 2:14:38
> PM org.apache.cxf.dosgi.topologymanager.RemoteServiceAdminL
> ist$1 addingService
> INFO: enlisted RemoteEventAdmins: 0
> Dec 21, 2009 2:14:38 PM
> org.apache.cxf.dosgi.topologymanager.TopologyManager tri
> ggerExportImportForRemoteSericeAdmin
> INFO: TopologyManager: triggerExportImportForRemoteSericeAdmin()
> Dec 21, 2009 2:14:38 PM
> org.apache.cxf.dosgi.topologymanager.TopologyManagerImpo
> rt triggerExportImportForRemoteSericeAdmin
> SEVERE: NOT IMPLEMENTED !!!
> Dec 21, 2009 2:14:38 PM
> org.apache.cxf.dosgi.topologymanager.EndpointListenerImp
> l getRegistrationProperties
> INFO: EndpointListener: current filter: []
>
> -----Original Message-----
> From: David Bosschaert [mailto:david.bosschaert@...]
> Sent: Tuesday, December 22, 2009 6:27 AM
> To: users@...
> Subject: Re: [DOSGI] cxf 2.2.5 in the DOSGI 1.2 snapshot download?
>
> I've just updated CXF/DOSGi trunk to use CXF 2.2.5
>
> BTW you should be able to use CXF 2.2.5 with the DOSGI 1.1 release. In the multi bundle distro, just replace the cxf-bundle-minimal-2.2.5.jar with the 2.2.5 version. Haven't tried it but it should work...
>
> Cheers,
>
> David
>
> 2009/12/22 David Bosschaert <david.bosschaert@...>:
>> Hi Thomas,
>>
>> Hmmm, I would think so, but the 1.1 release also has 2.2.4.
>> I'll update the build system to pick up 2.2.5.
>>
>> BTW I *really* advise you to use the 1.1 release and not 1.2-SNAPSHOT
>> at this moment in time as there is a lot of refactoring going on @
>> dosgi trunk [1]. So unless you like living on the edge I would go for
>> the 1.1 release :)
>>
>> Cheers,
>>
>> David
>>
>> [1]
>> http://old.nabble.com/Migrating-CXF-DOSGi-to-be-complaint-with-the-ne
>> w -OSGi-Remote-Service--Admin-spec-td26645023.html
>>
>> 2009/12/21 Shulok, Thomas <thomas.shulok@...>:
>>> Hi All,
>>>
>>> Just downloaded the lastest 1.2 snapshot, and it still has cxf-bundle-minimal-2.2.4.jar. Should this be 2.2.5 now?
>>>
>>> Thanks,
>>> Thom
>>>
>>
>

Switching a client to produce a JMS Object Message?

2009-12-22T07:35:20Z

Hi All,

I have some existing services that were using CXF's SOAP over JMS
protocol to send JMS messages to a topic... we've changed the homebrew
infrastructure that listened to this topic with a more solid, open
source solution. However, the replacement reads JmsMessages of type
ObjectMessage rather than SOAP. The same values we used are used,
except as StringProperties on the ObjectMessage.

Is there someway to replace the message format of my CXF client
service to produce ObjectMessages?

Thanks,
James

Re: JAXRSOutInterceptor - 346 - No message body writer has been found for response class Incidents.

2009-12-22T07:30:47Z

Many thanks,

I have verified the first solution proposed and everything works fine after adding in the MANIFEST file of the bundle containing the JAXB annoted classed these imports :

javax.xml.bind;version=2.1.0;resolution:=optional,
javax.xml.bind.annotation;version=2.1.0;resolution:=optional,
com.sun.xml.bind.v2.runtime.reflect;version=0.0.0;resolution:=optional

Thanks for the quick answer ;-)

Regards,

Charles

Sergey Beryozkin-2 wrote:

Hi

We have talked with Charles on Gmail and identified that the issue was to do with the CXF JAXB provider not seeing JAXB annotations,
due to the fact the JAXB-annotated classes have been moved to another OSGI bundle.
Two possible solutions :
- update the bundle containing the JAXRS service class to import a javax.xml.bind.annotation package
- configure CXF JAXBElementProvider to marshall away without @XMLRootElement being available, as described here
http://cwiki.apache.org/CXF20DOC/jax-rs.html#JAX-RS-HandlingJAXBbeanswithoutXmlRootElementannotations

Charles suggested to update JAXBElementProvider so that it logs/reprots why a given element is seen as not readable/writable,
something I will do shortly...

thanks, Sergey

>
> Hi,
>
> I have designed a project running on Apache Felix Karaf 1.2.0 and using the
> following components :
> - Apache CXF : 2.2.5
> - Camel-cxf : 2.2.0-SNAPSHOT
>
> This project consists in 4 different bundles :
> - REST service
> - Model
> - DAO
> - Route
>
> All the required packages are imported/exported accordingly.
>
> Surprisingly, when I try to do a GET, I receive the following warning
> without any error in the log except that the response send to the browser is
> "No message body reader has been found for request class ReportIncident":
>
> 14:30:38,271 | WARN | 74@qtp-8345336-0 | JAXRSUtils |
> pache.cxf.jaxrs.utils.JAXRSUtils 973 | No message body reader has been
> found for request class ReportIncident, ContentType :
> application/xml;charset=UTF-8.
>
> In debug mode, I have see that the instance MessageBodyReader is null at the
> line 950 of the code
>
> @SuppressWarnings("unchecked")
> private static <T> Object readFromMessageBody(Class<T> targetTypeClass,
> Type parameterType,
> Annotation[]
> parameterAnnotations,
> InputStream is,
> MediaType contentType,
> List<MediaType>
> consumeTypes,
> Message m) {
>
> List<MediaType> types = JAXRSUtils.intersectMimeTypes(consumeTypes,
> contentType);
>
> MessageBodyReader provider = null;
> for (MediaType type : types) {
> provider = ProviderFactory.getInstance(m)
> .createMessageBodyReader(targetTypeClass,
> parameterType,
> parameterAnnotations,
> type,
> m);
>
>
>
> Where is the issue ?
>
> Regards,
>
>
>
> -----
> Charles Moulliard
> SOA Architect
>
> My Blog : http://cmoulliard.blogspot.com/ http://cmoulliard.blogspot.com/
> --
> View this message in context:
> http://old.nabble.com/JAXRSOutInterceptor---346---No-message-body-writer-has-been-found-for-response-class-Incidents.-tp26888538p26888538.html
> Sent from the cxf-user mailing list archive at Nabble.com.
>

Charles Moulliard
SOA Architect

My Blog : http://cmoulliard.blogspot.com/

Re: problem while posting JSON text to RESTService

2009-12-22T07:27:50Z

Hi

I think this entry is confusing Jettison on the read side :

> <entry key="http://www.w3.org/2001/XMLSchema-instance" value=""/>

and you probably do not need it on the write side either, instead, just set a boolean "writeXsiType"
to false if you do not need the hierarchy info to go on the wire

let us know please if it helps
Cheers, Sergey

> Hi All,
>
>
>
> I have problem while posting JSON text to RESTService. The service is
> failing with Exception
>
> JAXBException occurred : unexpected element (uri:"
> http://www.w3.org/2001/XMLSchema-instance", local:"Customer"). Expected
> elements are <{}Customer>. unexpected element (uri:"
> http://www.w3.org/2001/XMLSchema-instance", local:"Customer"). Expected
> elements are <{}Customer>.
>
> I believe this the problem with namespace. Pleas suggest me a solution
>
>
>
>
>
> JSON Text
>
> -----------------
>
> {"Customer":{"id":123,"name":"Balaji"}}
>
>
>
>
>
> Customer Service
>
> ------------------
>
> @Path("/customerservice/")
>
> public class CustomerService {
>
> @POST
>
> @Path("/customers/")
>
> public Response addCustomer(Customer customer) {
>
> System.out.println("----invoking addCustomer, Customer name is: " +
> customer.getName());
>
> customer.setId(++currentId);
>
>
>
> customers.put(customer.getId(), customer);
>
>
>
> return Response.ok(customer).build();
>
> }
>
> }
>
>
>
> Spring-config.xml
>
> --------------
>
> <util:map id="jsonNamespaceMap" map-class="java.util.Hashtable">
>
> <entry key="http://www.w3.org/2001/XMLSchema-instance" value=""/>
>
> </util:map>
>
>
>
> <jaxrs:serviceBeans>
>
> <ref bean="customerService"/>
>
> </jaxrs:serviceBeans>
>
>
> Thanks
>
> Balaji
>

Re: [DOSGI] cxf 2.2.5 in the DOSGI 1.2 snapshot download?

2009-12-22T07:23:03Z

Hi Thomas,

The 1.2-SNAPSHOT CXF-DOSGi trunk is under heavy refactoring at the
moment, I'm happy to take a look at that stack trace once it's settled
down, hopefully in a few weeks time. For now, please try if you can
stick to the 1.1 release.

From memory, I have seen stack traces like the one you're posting
here. In some cases they did happen with the single-bundle distro but
not with the multi-bundle distro. In some cases they have been
harmless (just a validation error, but things continue to work).

Best regards,

David

2009/12/22 Shulok, Thomas <thomas.shulok@...>:

> Thanks David. Will try out the next snapshot build.
>
> Yesterday, I did try what you suggested (today), but with the 1.2 snapshot, and I got the following...
>
> Thanks,
> Thom
>
> Dec 21, 2009 2:14:38 PM org.apache.cxf.dosgi.dsw.OsgiUtils readIntentMap
> WARNING: Intent map load failed:
> org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException: Line 48 i n XML document from OSGi resource[classpath:/OSGI-INF/cxf/intents/intent-map.xml
> |bnd.id=2|bnd.sym=cxf-dosgi-ri-singlebundle-distribution] is invalid;
> |nested exc
> eption is org.xml.sax.SAXParseException: cvc-complex-type.2.4.c: The matching wi ldcard is strict, but no declaration can be found for element 'p:policies'.
> at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadB
> eanDefinitions(XmlBeanDefinitionReader.java:404)
> at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBea
> nDefinitions(XmlBeanDefinitionReader.java:342)
> at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBea
> nDefinitions(XmlBeanDefinitionReader.java:310)
> at org.springframework.beans.factory.support.AbstractBeanDefinitionReade
> r.loadBeanDefinitions(AbstractBeanDefinitionReader.java:143)
> at org.springframework.beans.factory.support.AbstractBeanDefinitionReade
> r.loadBeanDefinitions(AbstractBeanDefinitionReader.java:178)
> at org.springframework.beans.factory.support.AbstractBeanDefinitionReade
> r.loadBeanDefinitions(AbstractBeanDefinitionReader.java:149)
> at org.springframework.osgi.context.support.OsgiBundleXmlApplicationCont
> ext.loadBeanDefinitions(OsgiBundleXmlApplicationContext.java:176)
> at org.springframework.osgi.context.support.OsgiBundleXmlApplicationCont
> ext.loadBeanDefinitions(OsgiBundleXmlApplicationContext.java:142)
> at org.springframework.context.support.AbstractRefreshableApplicationCon
> text.refreshBeanFactory(AbstractRefreshableApplicationContext.java:123)
> at org.springframework.context.support.AbstractApplicationContext.obtain
> FreshBeanFactory(AbstractApplicationContext.java:422)
> at org.springframework.context.support.AbstractApplicationContext.refres
> h(AbstractApplicationContext.java:352)
> at org.springframework.osgi.context.support.AbstractDelegatedExecutionAp
> plicationContext.access$301(AbstractDelegatedExecutionApplicationContext.java:69
> )
> at org.springframework.osgi.context.support.AbstractDelegatedExecutionAp
> plicationContext$1.run(AbstractDelegatedExecutionApplicationContext.java:186)
> at org.springframework.osgi.util.internal.PrivilegedUtils.executeWithCus
> tomTCCL(PrivilegedUtils.java:85)
> at org.springframework.osgi.context.support.AbstractDelegatedExecutionAp
> plicationContext.normalRefresh(AbstractDelegatedExecutionApplicationContext.java
> :182)
> at org.springframework.osgi.context.support.AbstractDelegatedExecutionAp
> plicationContext$NoDependenciesWaitRefreshExecutor.refresh(AbstractDelegatedExec
> utionApplicationContext.java:89)
> at org.springframework.osgi.context.support.AbstractDelegatedExecutionAp
> plicationContext.refresh(AbstractDelegatedExecutionApplicationContext.java:175)
> at org.apache.cxf.dosgi.dsw.OsgiUtils.readIntentMap(OsgiUtils.java:401)
> at org.apache.cxf.dosgi.dsw.OsgiUtils.getIntentMap(OsgiUtils.java:376)
> at org.apache.cxf.dosgi.dsw.Activator.getIntentMap(Activator.java:96)
> at org.apache.cxf.dosgi.dsw.Activator.registerRemoteServiceAdminService(
> Activator.java:78)
> at org.apache.cxf.dosgi.dsw.Activator.start(Activator.java:55)
> at org.apache.cxf.dosgi.singlebundle.AggregatedActivator.startEmbeddedAc
> tivators(AggregatedActivator.java:115)
> at org.apache.cxf.dosgi.singlebundle.AggregatedActivator.start(Aggregate
> dActivator.java:46)
> at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(Bund
> leContextImpl.java:783)
> at java.security.AccessController.doPrivileged(Native Method)
> at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActiv
> ator(BundleContextImpl.java:774)
> at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(Bund
> leContextImpl.java:755)
> at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(Bundl
> eHost.java:352)
> at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(Abstrac
> tBundle.java:280)
> at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(Abstrac
> tBundle.java:272)
> at org.eclipse.osgi.framework.internal.core.FrameworkCommandProvider._st
> art(FrameworkCommandProvider.java:253)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at org.eclipse.osgi.framework.internal.core.FrameworkCommandInterpreter.
> execute(FrameworkCommandInterpreter.java:155)
> at org.eclipse.osgi.framework.internal.core.FrameworkConsole.docommand(F
> rameworkConsole.java:303)
> at org.eclipse.osgi.framework.internal.core.FrameworkConsole.console(Fra
> meworkConsole.java:288)
> at org.eclipse.osgi.framework.internal.core.FrameworkConsole.run(Framewo
> rkConsole.java:224)
> at java.lang.Thread.run(Unknown Source) Caused by: org.xml.sax.SAXParseException: cvc-complex-type.2.4.c: The matching w ildcard is strict, but no declaration can be found for element 'p:policies'.
> at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAX
> ParseException(Unknown Source)
> at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.error(Unk
> nown Source)
> at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(
> Unknown Source)
> at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(
> Unknown Source)
> at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator$XSIErro
> rReporter.reportError(Unknown Source)
> at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.reportS
> chemaError(Unknown Source)
> at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.handleS
> tartElement(Unknown Source)
> at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.startEl
> ement(Unknown Source)
> at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scan
> StartElement(Unknown Source)
> at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImp
> l$FragmentContentDispatcher.dispatch(Unknown Source)
> at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImp
> l.scanDocument(Unknown Source)
> at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(U
> nknown Source)
> at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(U
> nknown Source)
> at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(Unknown So
> urce)
> at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(Unknown So
> urce)
> at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(Unk
> nown Source)
> at org.springframework.beans.factory.xml.DefaultDocumentLoader.loadDocum
> ent(DefaultDocumentLoader.java:75)
> at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadB
> eanDefinitions(XmlBeanDefinitionReader.java:396)
> ... 40 more
> Dec 21, 2009 2:14:38 PM org.apache.cxf.dosgi.dsw.qos.IntentMap setIntents
> INFO: Injected intents: {}
> java.lang.UnsupportedClassVersionError: Bad version number in .class file
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClass(Unknown Source)
> at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.defineClass(
> DefaultClassLoader.java:183)
> at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.defineClass(Clas
> spathManager.java:576)
> at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findClassImpl(Cl
> asspathManager.java:546)
> at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClassIm
> pl(ClasspathManager.java:477)
> at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass_L
> ockClassLoader(ClasspathManager.java:465)
> at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(C
> lasspathManager.java:445)
> at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalCla
> ss(DefaultClassLoader.java:211)
> at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLo
> ader.java:381)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(Bundl
> eLoader.java:457)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.
> java:410)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.
> java:398)
> at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(De
> faultClassLoader.java:105)
> at java.lang.ClassLoader.loadClass(Unknown Source)
> at java.lang.ClassLoader.loadClassInternal(Unknown Source)
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClass(Unknown Source)
> at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.defineClass(
> DefaultClassLoader.java:183)
> at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.defineClass(Clas
> spathManager.java:576)
> at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findClassImpl(Cl
> asspathManager.java:546)
> at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClassIm
> pl(ClasspathManager.java:477)
> at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass_L
> ockClassLoader(ClasspathManager.java:465)
> at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(C
> lasspathManager.java:445)
> at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalCla
> ss(DefaultClassLoader.java:211)
> at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLo
> ader.java:381)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(Bundl
> eLoader.java:457)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.
> java:410)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.
> java:398)
> at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(De
> faultClassLoader.java:105)
> at java.lang.ClassLoader.loadClass(Unknown Source)
> at java.lang.ClassLoader.loadClassInternal(Unknown Source)
> at org.apache.cxf.dosgi.discovery.zookeeper.Activator.createZooKeeperDis
> covery(Activator.java:112)
> at org.apache.cxf.dosgi.discovery.zookeeper.Activator.start(Activator.ja
> va:46)
> at org.apache.cxf.dosgi.singlebundle.AggregatedActivator.startEmbeddedAc
> tivators(AggregatedActivator.java:115)
> at org.apache.cxf.dosgi.singlebundle.AggregatedActivator.start(Aggregate
> dActivator.java:46)
> at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(Bund
> leContextImpl.java:783)
> at java.security.AccessController.doPrivileged(Native Method)
> at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActiv
> ator(BundleContextImpl.java:774)
> at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(Bund
> leContextImpl.java:755)
> at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(Bundl
> eHost.java:352)
> at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(Abstrac
> tBundle.java:280)
> at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(Abstrac
> tBundle.java:272)
> at org.eclipse.osgi.framework.internal.core.FrameworkCommandProvider._st
> art(FrameworkCommandProvider.java:253)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at org.eclipse.osgi.framework.internal.core.FrameworkCommandInterpreter.
> execute(FrameworkCommandInterpreter.java:155)
> at org.eclipse.osgi.framework.internal.core.FrameworkConsole.docommand(F
> rameworkConsole.java:303)
> at org.eclipse.osgi.framework.internal.core.FrameworkConsole.console(Fra
> meworkConsole.java:288)
> at org.eclipse.osgi.framework.internal.core.FrameworkConsole.run(Framewo
> rkConsole.java:224)
> at java.lang.Thread.run(Unknown Source) Dec 21, 2009 2:14:38 PM org.apache.cxf.dosgi.topologymanager.Activator start
> INFO: TopologyManager: start()
> Dec 21, 2009 2:14:38 PM org.apache.cxf.dosgi.topologymanager.RemoteServiceAdminL
> ist$1 addingService
> INFO: Adding RemoteServiceAdmin to list of admins Dec 21, 2009 2:14:38 PM org.apache.cxf.dosgi.topologymanager.RemoteServiceAdminL
> ist$1 addingService
> INFO: enlisted RemoteEventAdmins: 0
> Dec 21, 2009 2:14:38 PM org.apache.cxf.dosgi.topologymanager.TopologyManager tri ggerExportImportForRemoteSericeAdmin
> INFO: TopologyManager: triggerExportImportForRemoteSericeAdmin()
> Dec 21, 2009 2:14:38 PM org.apache.cxf.dosgi.topologymanager.TopologyManagerImpo
> rt triggerExportImportForRemoteSericeAdmin
> SEVERE: NOT IMPLEMENTED !!!
> Dec 21, 2009 2:14:38 PM org.apache.cxf.dosgi.topologymanager.EndpointListenerImp
> l getRegistrationProperties
> INFO: EndpointListener: current filter: []
>
> -----Original Message-----
> From: David Bosschaert [mailto:david.bosschaert@...]
> Sent: Tuesday, December 22, 2009 6:27 AM
> To: users@...
> Subject: Re: [DOSGI] cxf 2.2.5 in the DOSGI 1.2 snapshot download?
>
> I've just updated CXF/DOSGi trunk to use CXF 2.2.5
>
> BTW you should be able to use CXF 2.2.5 with the DOSGI 1.1 release. In the multi bundle distro, just replace the cxf-bundle-minimal-2.2.5.jar with the 2.2.5 version. Haven't tried it but it should work...
>
> Cheers,
>
> David
>
> 2009/12/22 David Bosschaert <david.bosschaert@...>:
>> Hi Thomas,
>>
>> Hmmm, I would think so, but the 1.1 release also has 2.2.4.
>> I'll update the build system to pick up 2.2.5.
>>
>> BTW I *really* advise you to use the 1.1 release and not 1.2-SNAPSHOT
>> at this moment in time as there is a lot of refactoring going on @
>> dosgi trunk [1]. So unless you like living on the edge I would go for
>> the 1.1 release :)
>>
>> Cheers,
>>
>> David
>>
>> [1]
>> http://old.nabble.com/Migrating-CXF-DOSGi-to-be-complaint-with-the-new
>> -OSGi-Remote-Service--Admin-spec-td26645023.html
>>
>> 2009/12/21 Shulok, Thomas <thomas.shulok@...>:
>>> Hi All,
>>>
>>> Just downloaded the lastest 1.2 snapshot, and it still has cxf-bundle-minimal-2.2.4.jar. Should this be 2.2.5 now?
>>>
>>> Thanks,
>>> Thom
>>>
>>
>

RE: [DOSGI] cxf 2.2.5 in the DOSGI 1.2 snapshot download?

2009-12-22T07:13:23Z

Hi David,

Thanks for the tip. The fix I want is for

(CXF-2039) -Dorg.apache.cxf.spring.validation.mode=VALIDATION_NONE has no effect, so if I can just plug 2.2.5 into 1.1 that's fine with me (pending resolution of stack trace I just sent in response to your suggestion :-)

Thanks,
Thom

-----Original Message-----
From: David Bosschaert [mailto:david.bosschaert@...]
Sent: Tuesday, December 22, 2009 1:37 AM
To: users@...
Subject: Re: [DOSGI] cxf 2.2.5 in the DOSGI 1.2 snapshot download?

Hi Thomas,

Hmmm, I would think so, but the 1.1 release also has 2.2.4.
I'll update the build system to pick up 2.2.5.

BTW I *really* advise you to use the 1.1 release and not 1.2-SNAPSHOT at this moment in time as there is a lot of refactoring going on @ dosgi trunk [1]. So unless you like living on the edge I would go for the 1.1 release :)

Cheers,

David

[1] http://old.nabble.com/Migrating-CXF-DOSGi-to-be-complaint-with-the-new-OSGi-Remote-Service--Admin-spec-td26645023.html

2009/12/21 Shulok, Thomas <thomas.shulok@...>:
> Hi All,
>
> Just downloaded the lastest 1.2 snapshot, and it still has cxf-bundle-minimal-2.2.4.jar. Should this be 2.2.5 now?
>
> Thanks,
> Thom
>

Re: JAXRSOutInterceptor - 346 - No message body writer has been found for response class Incidents.

2009-12-22T07:12:38Z

Hi

We have talked with Charles on Gmail and identified that the issue was to do with the CXF JAXB provider not seeing JAXB annotations,
due to the fact the JAXB-annotated classes have been moved to another OSGI bundle.
Two possible solutions :
- update the bundle containing the JAXRS service class to import a javax.xml.bind.annotation package
- configure CXF JAXBElementProvider to marshall away without @XMLRootElement being available, as described here
http://cwiki.apache.org/CXF20DOC/jax-rs.html#JAX-RS-HandlingJAXBbeanswithoutXmlRootElementannotations

Charles suggested to update JAXBElementProvider so that it logs/reprots why a given element is seen as not readable/writable,
something I will do shortly...

thanks, Sergey

>
> Hi,
>
> I have designed a project running on Apache Felix Karaf 1.2.0 and using the
> following components :
> - Apache CXF : 2.2.5
> - Camel-cxf : 2.2.0-SNAPSHOT
>
> This project consists in 4 different bundles :
> - REST service
> - Model
> - DAO
> - Route
>
> All the required packages are imported/exported accordingly.
>
> Surprisingly, when I try to do a GET, I receive the following warning
> without any error in the log except that the response send to the browser is
> "No message body reader has been found for request class ReportIncident":
>
> 14:30:38,271 | WARN | 74@qtp-8345336-0 | JAXRSUtils |
> pache.cxf.jaxrs.utils.JAXRSUtils 973 | No message body reader has been
> found for request class ReportIncident, ContentType :
> application/xml;charset=UTF-8.
>
> In debug mode, I have see that the instance MessageBodyReader is null at the
> line 950 of the code
>
> @SuppressWarnings("unchecked")
> private static <T> Object readFromMessageBody(Class<T> targetTypeClass,
> Type parameterType,
> Annotation[]
> parameterAnnotations,
> InputStream is,
> MediaType contentType,
> List<MediaType>
> consumeTypes,
> Message m) {
>
> List<MediaType> types = JAXRSUtils.intersectMimeTypes(consumeTypes,
> contentType);
>
> MessageBodyReader provider = null;
> for (MediaType type : types) {
> provider = ProviderFactory.getInstance(m)
> .createMessageBodyReader(targetTypeClass,
> parameterType,
> parameterAnnotations,
> type,
> m);
>
>
>
> Where is the issue ?
>
> Regards,
>
>
>
> -----
> Charles Moulliard
> SOA Architect
>
> My Blog : http://cmoulliard.blogspot.com/ http://cmoulliard.blogspot.com/
> --
> View this message in context:
> http://old.nabble.com/JAXRSOutInterceptor---346---No-message-body-writer-has-been-found-for-response-class-Incidents.-tp26888538p26888538.html
> Sent from the cxf-user mailing list archive at Nabble.com.
>

RE: [DOSGI] cxf 2.2.5 in the DOSGI 1.2 snapshot download?

2009-12-22T07:10:02Z

Thanks David. Will try out the next snapshot build.

Yesterday, I did try what you suggested (today), but with the 1.2 snapshot, and I got the following...

Thanks,
Thom

Dec 21, 2009 2:14:38 PM org.apache.cxf.dosgi.dsw.OsgiUtils readIntentMap
WARNING: Intent map load failed:
org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException: Line 48 i n XML document from OSGi resource[classpath:/OSGI-INF/cxf/intents/intent-map.xml
|bnd.id=2|bnd.sym=cxf-dosgi-ri-singlebundle-distribution] is invalid;
|nested exc
eption is org.xml.sax.SAXParseException: cvc-complex-type.2.4.c: The matching wi ldcard is strict, but no declaration can be found for element 'p:policies'.
at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadB
eanDefinitions(XmlBeanDefinitionReader.java:404)
at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBea
nDefinitions(XmlBeanDefinitionReader.java:342)
at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBea
nDefinitions(XmlBeanDefinitionReader.java:310)
at org.springframework.beans.factory.support.AbstractBeanDefinitionReade
r.loadBeanDefinitions(AbstractBeanDefinitionReader.java:143)
at org.springframework.beans.factory.support.AbstractBeanDefinitionReade
r.loadBeanDefinitions(AbstractBeanDefinitionReader.java:178)
at org.springframework.beans.factory.support.AbstractBeanDefinitionReade
r.loadBeanDefinitions(AbstractBeanDefinitionReader.java:149)
at org.springframework.osgi.context.support.OsgiBundleXmlApplicationCont
ext.loadBeanDefinitions(OsgiBundleXmlApplicationContext.java:176)
at org.springframework.osgi.context.support.OsgiBundleXmlApplicationCont
ext.loadBeanDefinitions(OsgiBundleXmlApplicationContext.java:142)
at org.springframework.context.support.AbstractRefreshableApplicationCon
text.refreshBeanFactory(AbstractRefreshableApplicationContext.java:123)
at org.springframework.context.support.AbstractApplicationContext.obtain
FreshBeanFactory(AbstractApplicationContext.java:422)
at org.springframework.context.support.AbstractApplicationContext.refres
h(AbstractApplicationContext.java:352)
at org.springframework.osgi.context.support.AbstractDelegatedExecutionAp
plicationContext.access$301(AbstractDelegatedExecutionApplicationContext.java:69
)
at org.springframework.osgi.context.support.AbstractDelegatedExecutionAp
plicationContext$1.run(AbstractDelegatedExecutionApplicationContext.java:186)
at org.springframework.osgi.util.internal.PrivilegedUtils.executeWithCus
tomTCCL(PrivilegedUtils.java:85)
at org.springframework.osgi.context.support.AbstractDelegatedExecutionAp
plicationContext.normalRefresh(AbstractDelegatedExecutionApplicationContext.java
:182)
at org.springframework.osgi.context.support.AbstractDelegatedExecutionAp
plicationContext$NoDependenciesWaitRefreshExecutor.refresh(AbstractDelegatedExec
utionApplicationContext.java:89)
at org.springframework.osgi.context.support.AbstractDelegatedExecutionAp
plicationContext.refresh(AbstractDelegatedExecutionApplicationContext.java:175)
at org.apache.cxf.dosgi.dsw.OsgiUtils.readIntentMap(OsgiUtils.java:401)
at org.apache.cxf.dosgi.dsw.OsgiUtils.getIntentMap(OsgiUtils.java:376)
at org.apache.cxf.dosgi.dsw.Activator.getIntentMap(Activator.java:96)
at org.apache.cxf.dosgi.dsw.Activator.registerRemoteServiceAdminService(
Activator.java:78)
at org.apache.cxf.dosgi.dsw.Activator.start(Activator.java:55)
at org.apache.cxf.dosgi.singlebundle.AggregatedActivator.startEmbeddedAc
tivators(AggregatedActivator.java:115)
at org.apache.cxf.dosgi.singlebundle.AggregatedActivator.start(Aggregate
dActivator.java:46)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(Bund
leContextImpl.java:783)
at java.security.AccessController.doPrivileged(Native Method)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActiv
ator(BundleContextImpl.java:774)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(Bund
leContextImpl.java:755)
at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(Bundl
eHost.java:352)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(Abstrac
tBundle.java:280)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(Abstrac
tBundle.java:272)
at org.eclipse.osgi.framework.internal.core.FrameworkCommandProvider._st
art(FrameworkCommandProvider.java:253)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.osgi.framework.internal.core.FrameworkCommandInterpreter.
execute(FrameworkCommandInterpreter.java:155)
at org.eclipse.osgi.framework.internal.core.FrameworkConsole.docommand(F
rameworkConsole.java:303)
at org.eclipse.osgi.framework.internal.core.FrameworkConsole.console(Fra
meworkConsole.java:288)
at org.eclipse.osgi.framework.internal.core.FrameworkConsole.run(Framewo
rkConsole.java:224)
at java.lang.Thread.run(Unknown Source) Caused by: org.xml.sax.SAXParseException: cvc-complex-type.2.4.c: The matching w ildcard is strict, but no declaration can be found for element 'p:policies'.
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAX
ParseException(Unknown Source)
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.error(Unk
nown Source)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(
Unknown Source)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(
Unknown Source)
at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator$XSIErro
rReporter.reportError(Unknown Source)
at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.reportS
chemaError(Unknown Source)
at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.handleS
tartElement(Unknown Source)
at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.startEl
ement(Unknown Source)
at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scan
StartElement(Unknown Source)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImp
l$FragmentContentDispatcher.dispatch(Unknown Source)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImp
l.scanDocument(Unknown Source)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(U
nknown Source)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(U
nknown Source)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(Unknown So
urce)
at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(Unknown So
urce)
at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(Unk
nown Source)
at org.springframework.beans.factory.xml.DefaultDocumentLoader.loadDocum
ent(DefaultDocumentLoader.java:75)
at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadB
eanDefinitions(XmlBeanDefinitionReader.java:396)
... 40 more
Dec 21, 2009 2:14:38 PM org.apache.cxf.dosgi.dsw.qos.IntentMap setIntents
INFO: Injected intents: {}
java.lang.UnsupportedClassVersionError: Bad version number in .class file
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(Unknown Source)
at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.defineClass(
DefaultClassLoader.java:183)
at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.defineClass(Clas
spathManager.java:576)
at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findClassImpl(Cl
asspathManager.java:546)
at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClassIm
pl(ClasspathManager.java:477)
at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass_L
ockClassLoader(ClasspathManager.java:465)
at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(C
lasspathManager.java:445)
at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalCla
ss(DefaultClassLoader.java:211)
at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLo
ader.java:381)
at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(Bundl
eLoader.java:457)
at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.
java:410)
at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.
java:398)
at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(De
faultClassLoader.java:105)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClassInternal(Unknown Source)
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(Unknown Source)
at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.defineClass(
DefaultClassLoader.java:183)
at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.defineClass(Clas
spathManager.java:576)
at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findClassImpl(Cl
asspathManager.java:546)
at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClassIm
pl(ClasspathManager.java:477)
at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass_L
ockClassLoader(ClasspathManager.java:465)
at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(C
lasspathManager.java:445)
at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalCla
ss(DefaultClassLoader.java:211)
at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLo
ader.java:381)
at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(Bundl
eLoader.java:457)
at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.
java:410)
at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.
java:398)
at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(De
faultClassLoader.java:105)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClassInternal(Unknown Source)
at org.apache.cxf.dosgi.discovery.zookeeper.Activator.createZooKeeperDis
covery(Activator.java:112)
at org.apache.cxf.dosgi.discovery.zookeeper.Activator.start(Activator.ja
va:46)
at org.apache.cxf.dosgi.singlebundle.AggregatedActivator.startEmbeddedAc
tivators(AggregatedActivator.java:115)
at org.apache.cxf.dosgi.singlebundle.AggregatedActivator.start(Aggregate
dActivator.java:46)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(Bund
leContextImpl.java:783)
at java.security.AccessController.doPrivileged(Native Method)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActiv
ator(BundleContextImpl.java:774)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(Bund
leContextImpl.java:755)
at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(Bundl
eHost.java:352)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(Abstrac
tBundle.java:280)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(Abstrac
tBundle.java:272)
at org.eclipse.osgi.framework.internal.core.FrameworkCommandProvider._st
art(FrameworkCommandProvider.java:253)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.osgi.framework.internal.core.FrameworkCommandInterpreter.
execute(FrameworkCommandInterpreter.java:155)
at org.eclipse.osgi.framework.internal.core.FrameworkConsole.docommand(F
rameworkConsole.java:303)
at org.eclipse.osgi.framework.internal.core.FrameworkConsole.console(Fra
meworkConsole.java:288)
at org.eclipse.osgi.framework.internal.core.FrameworkConsole.run(Framewo
rkConsole.java:224)
at java.lang.Thread.run(Unknown Source) Dec 21, 2009 2:14:38 PM org.apache.cxf.dosgi.topologymanager.Activator start
INFO: TopologyManager: start()
Dec 21, 2009 2:14:38 PM org.apache.cxf.dosgi.topologymanager.RemoteServiceAdminL
ist$1 addingService
INFO: Adding RemoteServiceAdmin to list of admins Dec 21, 2009 2:14:38 PM org.apache.cxf.dosgi.topologymanager.RemoteServiceAdminL
ist$1 addingService
INFO: enlisted RemoteEventAdmins: 0
Dec 21, 2009 2:14:38 PM org.apache.cxf.dosgi.topologymanager.TopologyManager tri ggerExportImportForRemoteSericeAdmin
INFO: TopologyManager: triggerExportImportForRemoteSericeAdmin()
Dec 21, 2009 2:14:38 PM org.apache.cxf.dosgi.topologymanager.TopologyManagerImpo
rt triggerExportImportForRemoteSericeAdmin
SEVERE: NOT IMPLEMENTED !!!
Dec 21, 2009 2:14:38 PM org.apache.cxf.dosgi.topologymanager.EndpointListenerImp
l getRegistrationProperties
INFO: EndpointListener: current filter: []

-----Original Message-----
From: David Bosschaert [mailto:david.bosschaert@...]
Sent: Tuesday, December 22, 2009 6:27 AM
To: users@...
Subject: Re: [DOSGI] cxf 2.2.5 in the DOSGI 1.2 snapshot download?

I've just updated CXF/DOSGi trunk to use CXF 2.2.5

BTW you should be able to use CXF 2.2.5 with the DOSGI 1.1 release. In the multi bundle distro, just replace the cxf-bundle-minimal-2.2.5.jar with the 2.2.5 version. Haven't tried it but it should work...

Cheers,

David

2009/12/22 David Bosschaert <david.bosschaert@...>:

> Hi Thomas,
>
> Hmmm, I would think so, but the 1.1 release also has 2.2.4.
> I'll update the build system to pick up 2.2.5.
>
> BTW I *really* advise you to use the 1.1 release and not 1.2-SNAPSHOT
> at this moment in time as there is a lot of refactoring going on @
> dosgi trunk [1]. So unless you like living on the edge I would go for
> the 1.1 release :)
>
> Cheers,
>
> David
>
> [1]
> http://old.nabble.com/Migrating-CXF-DOSGi-to-be-complaint-with-the-new
> -OSGi-Remote-Service--Admin-spec-td26645023.html
>
> 2009/12/21 Shulok, Thomas <thomas.shulok@...>:
>> Hi All,
>>
>> Just downloaded the lastest 1.2 snapshot, and it still has cxf-bundle-minimal-2.2.4.jar. Should this be 2.2.5 now?
>>
>> Thanks,
>> Thom
>>
>

Re: [DOSGI] cxf 2.2.5 in the DOSGI 1.2 snapshot download?

2009-12-22T06:27:27Z

I've just updated CXF/DOSGi trunk to use CXF 2.2.5

BTW you should be able to use CXF 2.2.5 with the DOSGI 1.1 release. In
the multi bundle distro, just replace the cxf-bundle-minimal-2.2.5.jar
with the 2.2.5 version. Haven't tried it but it should work...

Cheers,

David

2009/12/22 David Bosschaert <david.bosschaert@...>:

> Hi Thomas,
>
> Hmmm, I would think so, but the 1.1 release also has 2.2.4.
> I'll update the build system to pick up 2.2.5.
>
> BTW I *really* advise you to use the 1.1 release and not 1.2-SNAPSHOT
> at this moment in time as there is a lot of refactoring going on @
> dosgi trunk [1]. So unless you like living on the edge I would go for
> the 1.1 release :)
>
> Cheers,
>
> David
>
> [1] http://old.nabble.com/Migrating-CXF-DOSGi-to-be-complaint-with-the-new-OSGi-Remote-Service--Admin-spec-td26645023.html
>
> 2009/12/21 Shulok, Thomas <thomas.shulok@...>:
>> Hi All,
>>
>> Just downloaded the lastest 1.2 snapshot, and it still has cxf-bundle-minimal-2.2.4.jar. Should this be 2.2.5 now?
>>
>> Thanks,
>> Thom
>>
>

jms-spec-demo example in apache-cxf-2.3.0-SNAPSHOT: No DestinationFactory was found ....

2009-12-22T06:11:07Z

Hi,

I'm trying to run jms-spec-demo example in the snapshot version of CXF (apache-cxf-2.3.0-SNAPSHOT-src)

I used maven for building.

    mvn install (this will build the demo) <--- It's OK
        In separate command windows/shells:
    mvn -Pjms.broker <--- It's OK
    mvn -Pserver <--- error raises here

__________________________________________________________
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] An exception occured while executing the Java class. null
No DestinationFactory was found for the namespace http://www.w3.org/2008/07/soap/bindings/JMS/.
[INFO] ------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: An exception occured while executing the Java class. null
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:583)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
        at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
        at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
        at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoExecutionException: An exception occured while executing the Java class. null
        at org.codehaus.mojo.exec.ExecJavaMojo.execute(ExecJavaMojo.java:338)
        at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
        ... 16 more
Caused by: java.lang.reflect.InvocationTargetException
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:283)
        at java.lang.Thread.run(Thread.java:595)
Caused by: javax.xml.ws.WebServiceException: org.apache.cxf.service.factory.ServiceConstructionException
        at org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:275)
        at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:209)
        at org.apache.cxf.jaxws.spi.ProviderImpl.createAndPublishEndpoint(ProviderImpl.java:84)
        at javax.xml.ws.Endpoint.publish(Endpoint.java:47)
        at demo.jms_greeter.server.Server.<init>(Server.java:32)
        at demo.jms_greeter.server.Server.main(Server.java:37)
        ... 6 more
Caused by: org.apache.cxf.service.factory.ServiceConstructionException
        at org.apache.cxf.frontend.ServerFactoryBean.create(ServerFactoryBean.java:125)
        at org.apache.cxf.jaxws.JaxWsServerFactoryBean.create(JaxWsServerFactoryBean.java:167)
        at org.apache.cxf.jaxws.EndpointImpl.getServer(EndpointImpl.java:346)
        at org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:259)
        ... 11 more
Caused by: org.apache.cxf.BusException: No DestinationFactory was found for the namespace http://www.w3.org/2008/07/soap/bindings/JMS/.
        at org..apache.cxf.transport.DestinationFactoryManagerImpl.getDestinationFactory(DestinationFactoryManagerImpl.java:115)
        at org.apache.cxf.endpoint.ServerImpl.initDestination(ServerImpl.java:85)
        at org.apache.cxf.endpoint.ServerImpl.<init>(ServerImpl.java:69)
        at org.apache.cxf.frontend.ServerFactoryBean.create(ServerFactoryBean.java:106)
        ... 14 more
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 12 seconds
[INFO] Finished at: Tue Dec 22 14:50:07 CET 2009
[INFO] Final Memory: 38M/64M
[INFO] ------------------------------------------------------------------------
__________________________________________________________

Because the SOAP over JMS specification feature described here is a new feature under development for CXF 2.3, so I don't know this error relates to the snapshot version or it's my configuration that cause this thing.

Any help is appriciated

Thanks
=========================================================================
NGUYEN Tien Luong      |                  M2PGI - UFRIMAG
13 Rue Blanche MONIER    |           Tel : 06.45.42.46.33
38000 GRENOBLE       |              http://tienluong.info

problem while posting JSON text to RESTService

2009-12-22T05:43:05Z

Hi All,

I have problem while posting JSON text to RESTService. The service is
failing with Exception

JAXBException occurred : unexpected element (uri:"
http://www.w3.org/2001/XMLSchema-instance", local:"Customer"). Expected
elements are <{}Customer>. unexpected element (uri:"
http://www.w3.org/2001/XMLSchema-instance", local:"Customer"). Expected
elements are <{}Customer>.

I believe this the problem with namespace. Pleas suggest me a solution

JSON Text

-----------------

{"Customer":{"id":123,"name":"Balaji"}}

Customer Service

------------------

@Path("/customerservice/")

public class CustomerService {

@POST

@Path("/customers/")

public Response addCustomer(Customer customer) {

System.out.println("----invoking addCustomer, Customer name is: " +
customer.getName());

customer.setId(++currentId);

customers.put(customer.getId(), customer);

return Response.ok(customer).build();

}

}

Spring-config.xml

--------------

<util:map id="jsonNamespaceMap" map-class="java.util.Hashtable">

<entry key="http://www.w3.org/2001/XMLSchema-instance" value=""/>

</util:map>

<jaxrs:serviceBeans>

<ref bean="customerService"/>

</jaxrs:serviceBeans>

Thanks

Balaji

JAXRSOutInterceptor - 346 - No message body writer has been found for response class Incidents.

2009-12-22T05:42:29Z

Hi,

I have designed a project running on Apache Felix Karaf 1.2.0 and using the following components :
- Apache CXF : 2.2.5
- Camel-cxf : 2.2.0-SNAPSHOT

This project consists in 4 different bundles :
- REST service
- Model
- DAO
- Route

All the required packages are imported/exported accordingly.

Surprisingly, when I try to do a GET, I receive the following warning without any error in the log except that the response send to the browser is "No message body reader has been found for request class ReportIncident":

14:30:38,271 | WARN | 74@qtp-8345336-0 | JAXRSUtils | pache.cxf.jaxrs.utils.JAXRSUtils 973 | No message body reader has been found for request class ReportIncident, ContentType : application/xml;charset=UTF-8.

In debug mode, I have see that the instance MessageBodyReader is null at the line 950 of the code

@SuppressWarnings("unchecked")
private static <T> Object readFromMessageBody(Class<T> targetTypeClass,
Type parameterType,
Annotation[] parameterAnnotations,
InputStream is,
MediaType contentType,
List<MediaType> consumeTypes,
Message m) {

List<MediaType> types = JAXRSUtils.intersectMimeTypes(consumeTypes, contentType);

MessageBodyReader provider = null;
for (MediaType type : types) {
provider = ProviderFactory.getInstance(m)
.createMessageBodyReader(targetTypeClass,
parameterType,
parameterAnnotations,
type,
m);

Where is the issue ?

Regards,

Charles Moulliard
SOA Architect

My Blog : http://cmoulliard.blogspot.com/

Re: [DOSGI] cxf 2.2.5 in the DOSGI 1.2 snapshot download?

2009-12-22T01:37:07Z

Hi Thomas,

Hmmm, I would think so, but the 1.1 release also has 2.2.4.
I'll update the build system to pick up 2.2.5.

BTW I *really* advise you to use the 1.1 release and not 1.2-SNAPSHOT
at this moment in time as there is a lot of refactoring going on @
dosgi trunk [1]. So unless you like living on the edge I would go for
the 1.1 release :)

Cheers,

David

[1] http://old.nabble.com/Migrating-CXF-DOSGi-to-be-complaint-with-the-new-OSGi-Remote-Service--Admin-spec-td26645023.html

2009/12/21 Shulok, Thomas <thomas.shulok@...>:
> Hi All,
>
> Just downloaded the lastest 1.2 snapshot, and it still has cxf-bundle-minimal-2.2.4.jar. Should this be 2.2.5 now?
>
> Thanks,
> Thom
>

Re: sending attachments using JaxWsProxyFactoryBean and ClientProxy

2009-12-21T19:24:50Z

Hi Dan.

I tried your code snippet, but attachments still don't get sent. I checked my byte[] attachment param, and it's not null.

Any suggestions?

Many thanks.
Kin

dkulp wrote:

> void bindAttachmentsToSoapRequest(Object proxyObject, byte[]
> attachments) {
> //...
>
> final Client client = ClientProxy.getClient(proxyObject);
>
> client.getEndpoint().put(MessageContext.OUTBOUND_MESSAGE_ATTACHMENTS,
> new DataHandler(new
> ByteArrayDataSource(attachments, "content/type")));
> }

That definitely won't work. I think the best way to get this to work is:
import org.apache.cxf.attachment.AttachmentImpl;
import org.apache.cxf.message.Attachment;
import org.apache.cxf.message.Message;

Collection<Attachment> atts = new ArrayList<Attachment>();
atts.add(new AttachmentImpl("myId", new DataHandler(new
ByteArrayDataSource(attachments, "content/type"));

((BindingProvider)proxyObject).getRequestContext().put(
Message.ATTACHMENTS,
atts);

Dan

On Fri December 18 2009 12:29:38 am erskine.dedios wrote:
> Hi.
>
> I'm very new to cxf, could you help me sort this out? I am able to send a
> soap message successfully, but attachments don't seem to get sent.
>
> Below is a snippet of my code. ..
>
> JaxWsProxyFactoryBean proxyFactory = new
> JaxWsProxyFactoryBean();
> proxyFactory.setServiceClass(SendMessage.class);
>
> proxyFactory.setAddress("http://nelson:8089/mockSendMessageBinding");
> remoteSendMessageService = (SendMessage) proxyFactory.create();
>
> bindAttachmentsToSoapRequest(remoteSendMessageService,
> attachments);
>
> remoteSendMessageService.sendMessage(destinationList,
> origin,
> subject);
>
>
> //...
>
> void bindAttachmentsToSoapRequest(Object proxyObject, byte[]
> attachments) {
> //...
>
> final Client client = ClientProxy.getClient(proxyObject);
>
> client.getEndpoint().put(MessageContext.OUTBOUND_MESSAGE_ATTACHMENTS,
> new DataHandler(new
> ByteArrayDataSource(attachments, "content/type")));
> }
>
> I use soapui to receive my soap messages.
>
>
>
> Thanks.
> Kin
>

--
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog

RE: Inflexible fault interceptor chain?

2009-12-21T17:12:50Z

Hello Dan and all,

Ok, the SAAJOutInterceptor solution almost worked. The behavior I describe below is the same in CXF 2.2.4 and 2.2.6-SNAPSHOT (as of Saturday's build). I am not on 2.2.5 due to some bugs that are fixed in 2.2.6. The debugging information I gathered for this message is with 2.2.4.

I have two scenarios, one works and one does not with the SAAJOutInterceptor solution.

If a Fault is thrown by a custom interceptor at a certain point in the output chain, the wrong SOAP XML is generated, specifically no SOAP fault XML elements are generated. Let me start by showing what works and why before showing what does not and why.

In the first scenario, which works, a SoapFault is thrown by our provider's invoke(SOAPMessage) method under certain conditions, basically if our server detects certain errors. Our provider looks like this:

@WebServiceProvider
@ServiceMode(value = Service.Mode.MESSAGE)
public static class LdeWebServiceProvider implements Provider<SOAPMessage> {
@Override
public SOAPMessage invoke(SOAPMessage soapRequest) {
...
throw new SoapFault("Our message", Soap11.getInstance().getReceiver());
}
}

In SAAJOutInterceptor.handleMessage, the local variable saaj is null, so the code path taken builds a SOAP message from scratch and plugs in a W3CDOMStreamWriter. All of the interceptors then write to W3CDOMStreamWriter instead of the default XMLStreamWriter which normally caches and writes to the HTTP wire. The W3CDOMStreamWriter allows me to transform the DOM before it gets on the wire. Great stuff, it works.

In the second scenario, I test our output feature where in addition to an optional transformation, we have custom interceptors to do optional XML validation before and after the XML transformation. After our provider successfully processed a message, the output chain processing kicks in and looks like this:

Chain org.apache.cxf.phase.PhaseInterceptorChain@c375934. Current flow:
setup [PolicyOutInterceptor]
pre-logical [SwAOutInterceptor, SoapHeaderOutFilterInterceptor]
post-logical [SoapPreProtocolOutInterceptor]
prepare-send [MessageSenderInterceptor, MessageModeOutInterceptor]
pre-stream [LoggingOutInterceptor, XmlDeclOutInterceptor*, AttachmentOutInterceptor, StaxOutInterceptor]
pre-protocol [MessageModeOutInterceptorInternal, SAAJOutInterceptor, SOAPHandlerInterceptor, OurWSS4JOutInterceptor]
write [SoapOutInterceptor]
pre-marshal [LogicalHandlerOutInterceptor, ValidatingOutInterceptor*, TransformOutInterceptor*, ValidatingOutInterceptor*]
marshal [BareOutInterceptor]
write-ending [SoapOutEndingInterceptor]
pre-protocol-ending [SAAJOutEndingInterceptor]
pre-stream-ending [StaxOutEndingInterceptor]
prepare-send-ending [MessageSenderEndingInterceptor]

The interceptors marked with * are mine:
- XmlDeclOutInterceptor forces the XML declaration to be written.
- ValidatingOutInterceptor validates XML
- TransformOutInterceptor transforms XML
- ValidatingOutInterceptor validates XML

The problem occurs if XML validation fails (the first validation in this test).

When the XML validation fails, an exception thrown, caught, and re-thrown as a fault.

At the start of fault processing, the chain when SAAJOutInterceptor is called looks like this:

Chain org.apache.cxf.phase.PhaseInterceptorChain@77c16c5f. Current flow:
setup [ServerPolicyOutFaultInterceptor]
prepare-send [MessageSenderInterceptor, Soap11FaultOutInterceptor]
pre-stream [LoggingOutInterceptor, XmlDeclOutInterceptor*, StaxOutInterceptor]
pre-protocol [WebFaultOutInterceptor, SAAJOutInterceptor, SOAPHandlerFaultOutInterceptor]
write [SoapOutInterceptor]
pre-marshal [LogicalHandlerFaultOutInterceptor]
marshal [Soap11FaultOutInterceptorInternal]
pre-protocol-ending [TransformOutFaultInterceptor*]
prepare-send-ending [MessageSenderEndingInterceptor]

The interceptors marked with * are mine:
- XmlDeclOutInterceptor forces the XML declaration to be written.
- TransformOutFaultInterceptor validates XML

When I step through this SAAJOutInterceptor invocation, the saaj variable is NOT null, so the code path taken is different from what I described above. Instead of a W3CDOMStreamWriter, a dummy XMLStreamWriter is created that throws away whatever is written to it:

//as the SOAPMessage already has everything in place, we do not need XMLStreamWriter to write
//anything for us, so we just set XMLStreamWriter's output to a dummy output stream.
XMLStreamWriter origWriter = message.getContent(XMLStreamWriter.class);
message.put(ORIGINAL_XML_WRITER, origWriter);

XMLStreamWriter dummyWriter = StaxUtils.createXMLStreamWriter(new OutputStream() {
public void write(int b) throws IOException {
}
public void write(byte b[], int off, int len) throws IOException {
}
});
message.setContent(XMLStreamWriter.class, dummyWriter);

No wonder I get no SOAP fault information back, I get:

<?xml version='1.0' encoding='ISO-8859-1'?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Header xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<ais:requestID xmlns:ais="http://com.seagullsw.appinterface/AppInterfaceServer">{c0a80102-00ce16ad0000010e75da25398002}</ais:requestID>
</SOAP-ENV:Header>
<SOAP-ENV:Body xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" />
</SOAP-ENV:Envelope>

Is this a bug? Why would there be a dummy writer put in place? Is there another CXF way to do this?

Thank you,
Gary

> -----Original Message-----
> From: Gary Gregory
> Sent: Friday, December 18, 2009 18:11
> To: 'Daniel Kulp'; users@...
> Subject: RE: Inflexible fault interceptor chain?
>
> Ok, that worked!
>
> Thank you Dan,
> Gary
>
> > -----Original Message-----
> > From: Daniel Kulp [mailto:dkulp@...]
> > Sent: Friday, December 18, 2009 07:33
> > To: users@...
> > Cc: Gary Gregory; Lee Breisacher; Nikolay Glazyrin
> > Subject: Re: Inflexible fault interceptor chain?
> >
> >
> > Honestly, the EASIEST way to accomplish this, since you are using
> soap,
> > is to
> > add the SAAJOutInterceptor to the fault chain. Then, your
> interceptor
> > would
> > live right before it's "ending" interceptor and do:
> >
> > message.getContext(SOAPMessage.class)
> >
> > to get the SAAJ model out. Since the SAAJ model implements the DOM
> > interfaces, you can then feed that into an XSLT processor or similar
> to
> > transform it and then set a new version back with the setContent
> call.
> >
> >
> > Dan
> >
> >
> > On Fri December 18 2009 4:13:29 am Gary Gregory wrote:
> > > Hi All:
> > >
> > > I need to apply an XSL transformation to messages coming out of CXF
> > (our
> > > users configure what the XSL looks like.) For a normal
> (successful)
> > > message, I have an interceptor (during Phase.PRE_MARSHAL) that
> uses
> > the
> > > DOM aspect of a message. That works great. BTW, I get to the DOM
> > like
> > > this:
> > >
> > > Node node = (Node) message.getContent(List.class).get(0);
> > >
> > > That seems brittle, is there a safer way to get to an aspect of the
> > message
> > > I can feed to javax.xml.transform?
> > >
> > > The real issue comes with fault messages because the fault chain
> uses
> > an
> > >
> >
> XMLStreamWriter<http://java.sun.com/javase/6/docs/api/javax/xml/stream/
> > XML
> > > StreamWriter.html>. The fault chain looks like this:
> > >
> > > Chain org.apache.cxf.phase.PhaseInterceptorChain@3015b303. Current
> > flow:
> > > setup [ServerPolicyOutFaultInterceptor]
> > > prepare-send [MessageSenderInterceptor,
> Soap11FaultOutInterceptor]
> > > pre-stream [LoggingOutInterceptor, XmlDeclOutInterceptor*,
> > > StaxOutInterceptor] pre-protocol [WebFaultOutInterceptor,
> > > SOAPHandlerFaultOutInterceptor] write [SoapOutInterceptor]
> > > pre-marshal [LogicalHandlerFaultOutInterceptor]
> > > marshal [Soap11FaultOutInterceptorInternal]
> > > pre-stream-ending [StaxOutEndingInterceptor,
> > > TransformOutFaultInterceptor*] prepare-send-ending
> > > [MessageSenderEndingInterceptor]
> > >
> > > FYI, the interceptors marked with * are our own:
> > >
> > > * XmlDeclOutInterceptor forces an XML declaration to be
> > written.
> > >
> > > * TransformOutFaultInterceptor is where I thought I could
> > transform
> > > the fault XML message.
> > >
> > > The
> > >
> >
> XMLStreamWriter<http://java.sun.com/javase/6/docs/api/javax/xml/stream/
> > XML
> > > StreamWriter.html> looks like this:
> > >
> > > [StreamWriter: class com.ctc.wstx.sw.SimpleNsStreamWriter,
> underlying
> > > outputter:
> > >
> >
> com.ctc.wstx.sw.ISOLatin1XmlWriter@1125cf44<mailto:com.ctc.wstx.sw.ISOL
> > ati
> > > n1XmlWriter@1125cf44>
> > >
> > > The com.ctc.wstx.sw.ISOLatin1XmlWriter wraps a
> > > org.apache.cxf.io.CachedOutputStream, which in turns wraps:
> > >
> > > * currentStream - LoadingByteArrayOutputStream
> > >
> > > * flowThroughStream -
> > AbstractHTTPDestination$WrappedOutputStream
> > >
> > > All of this to say that when the chain's interceptors are working
> > with the
> > > message's
> > >
> >
> XMLStreamWriter<http://java.sun.com/javase/6/docs/api/javax/xml/stream/
> > XML
> > > StreamWriter.html>, the bytes are cached and written to the wire.
> It
> > is not
> > > possible to catch the fault XML message and change it.
> > >
> > > The only thing I've come up with but not implemented yet would be
> to
> > insert
> > > an interceptor before the XML declaration is written and put the
> > >
> >
> XMLStreamWriter<http://java.sun.com/javase/6/docs/api/javax/xml/stream/
> > XML
> > > StreamWriter.html> into a temp spot in the message content map,
> then
> > put a
> > > new
> > >
> >
> XMLStreamWriter<http://java.sun.com/javase/6/docs/api/javax/xml/stream/
> > XML
> > > StreamWriter.html> on a byte array in its place. A pre-stream-
> ending
> > > interceptor can take those bytes, apply XSL to them and then write
> > them to
> > > the original
> > >
> >
> XMLStreamWriter<http://java.sun.com/javase/6/docs/api/javax/xml/stream/
> > XML
> > > StreamWriter.html>, before putting the original
> > >
> >
> XMLStreamWriter<http://java.sun.com/javase/6/docs/api/javax/xml/stream/
> > XML
> > > StreamWriter.html> back in it original slot in the message content
> > map.
> > >
> > > That seems like big old hack.
> > >
> > > Any ideas on a cleaner solution?
> > >
> > > Thank you,
> > > Gary Gregory
> > > Seagull Software
> > > ggregory@...
> > > www.seagullsoftware.com
> > >
> >
> > --
> > Daniel Kulp
> > dkulp@...
> > http://www.dankulp.com/blog

default namespace not specified from xjc output when no package-info.java

2009-12-21T16:39:25Z

cxf-2.2.3; jaxb 2.1.3; java 1.6

Was trying to see where the parameter name was being lost and the differences in wsdl for different the different xml parameters (element vs type).

So created a simple xsd:

<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" >

<xsd:element name="e2" type="t2">

</xsd:element>

<xsd:complexType name="t2">

<xsd:sequence>

<xsd:element name="Child"/>

</xsd:sequence>

</xsd:complexType>

</xsd:schema>

And a simple ws to access the xjc generated classes:

package test.ws.services;

…

@WebService

public class SampleXJCWS {

@Oneway

public void doE2(T2 el) {

System.out.println("DoE2 = " + el);

}

…

}

The captured wsdl, was invalid, xerces "Namespace URI {} not available in schema ws.samplexjc.wsdl":

<wsdl:definitions name="SampleXJCWSService" targetNamespace="http://services.ws.test/"

xmlns:ns1="http://schemas.xmlsoap.org/wsdl/soap/http"

xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://services.ws.test/"

xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/

xmlns:xsd="http://www.w3.org/2001/XMLSchema">

<wsdl:types>

<xs:schema elementFormDefault="unqualified" targetNamespace="http://services.ws.test/" version="1.0"

xmlns:tns="http://services.ws.test/" xmlns:xs=http://www.w3.org/2001/XMLSchema>

…

<xs:complexType name="doE2">

<xs:sequence>

<xs:element minOccurs="0" name="arg0" type="t2"/>

</xs:sequence>

</xs:complexType>

…

<xs:schema targetNamespace="http://services.ws.test/" version="1.0" xmlns:xs="http://www.w3.org/2001/XMLSchema">

…

<xs:complexType name="t2">

<xs:sequence>

<xs:element name="Child" type="xs:anyType"/>

</xs:sequence>

</xs:complexType>

…

</wsdl:definitions>

This can be corrected by adding an xmlns=http://services.ws.test/ to both schema declarations. It is not a problem if a package-info class exists.

Re: CXF SSL and Configuration

2009-12-21T13:40:21Z

On Mon December 21 2009 1:13:28 pm blitzer wrote:
> I removed everything but <http-conf:tlsClientParameters
> secureSocketProtocol="SSL"/>
> And it now works. What causes this to work?

Basically, at one point a few versions ago, for any https stuff, we REQUIRED
the tlsClientParameters to be configured. If you used an https URL without
it, we'd throw an exception. As you discovered, configuring the TLS stuff
can be a bit complex so we added the ability for https URL's to work if the
tlsClientParameters setting isn't configured by fully delegating to the JRE
for security/https stuff. However, if tlsClientParameters is configured, we
can no longer delegate to the JRE and use the configured information. Thus,
once you deleted the configuration, the JRE is used and it should work for
you.

Dan

>
> blitzer wrote:
> > So, in short I have a small configuration issue. With one line of code in
> > an axis client I can use a url against a web service that is https. All
> > i have to do is set
> > System.setProperty("javax.net.ssl.truststore",storeLocation) and my
> > client works.
> >
> > With CXF it seems there is much more to it. I have tried many many things
> > from lots of searches.
> >
> > I have tried a conduit that looks like this
> > Configuration A:
> > <http-conf:conduit name="*.http-conduit">
> >
> > <http-conf:client ProxyServer="aProxy"
> > ProxyServerPort="80" AllowChunking="false" />
> >
> > <http-conf:tlsClientParameters disableCNCheck="true"
> > secureSocketProtocol="SSL">
> > <conf-sec:trustManagers>
> > <conf-sec:certStore
> > file="E://PLAYGROUND//blitz//cert//store"/>
> > </conf-sec:trustManagers>
> > </http-conf:tlsClientParameters>
> >
> > <http-conf:authorization>
> > <conf-sec:UserName>User</conf-sec:UserName>
> > <conf-sec:Password>pass</conf-sec:Password>
> > </http-conf:authorization>
> >
> > </http-conf:conduit>
> >
> > And one that looks like this:
> > Configuration B:
> > <http-conf:conduit name="*.http-conduit">
> >
> > <http-conf:client ProxyServer="aProxy"
> > ProxyServerPort="80" AllowChunking="false" />
> >
> > <http-conf:tlsClientParameters disableCNCheck="true"
> > secureSocketProtocol="SSL">
> > <conf-sec:trustManagers>
> > <conf-sec:keyStore type="JKS" password="password"
> > file="E:/PLAYGROUND/blitz/cert/store"/>
> > </conf-sec:trustManagers>
> > </http-conf:tlsClientParameters>
> >
> > <http-conf:authorization>
> > <conf-sec:UserName>User</conf-sec:UserName>
> > <conf-sec:Password>pass</conf-sec:Password>
> > </http-conf:authorization>
> >
> > </http-conf:conduit>
> >
> > I am not a cert, keystore expert by any means and I am confused on which
> > configuration I should be using. My use case is using cxf to call a
> > third party https service. I pulled the cert from their site and
> > performed a keytool import on it to get the store. All the proxy and
> > basic auth stuff works like a charm. When I try to use ssl however I
> > cannot get a single configuration to work. I am sure that this works but
> > online everyone that has solved this issue has a different way of doing
> > so.
> >
> > With Configuration A I get an error about my DerInputStream being too
> > large.
> > With Configuration B I get an error that there is no trusted
> > certification found. Also with this configuration I debugged the
> > HttpConduit object and in the tlsClientParameters I can see the store in
> > all its glory with all the correct configurations that are in the
> > configuration xml file.
> >
> > I want cxf to make this project a success. Any ideas on what I am doing
> > wrong?
> > Thanks
>

--
Daniel Kulp
dkulp@...
http://www.dankulp.com/blog

[DOSGI] cxf 2.2.5 in the DOSGI 1.2 snapshot download?

2009-12-21T13:38:01Z

Hi All,

Just downloaded the lastest 1.2 snapshot, and it still has cxf-bundle-minimal-2.2.4.jar. Should this be 2.2.5 now?

Thanks,
Thom

Field Decrypts but does not unmarshall

2009-12-21T13:31:54Z

I have a field in an inbound request that is encrypted via WS-Security. I can step into the wss4j code and see the field is being decrypted properly, but the field is null when it gets into my endpoint impl. I am thinking that something is going wrong during the unmarshalling. The field of concern type is an xsd:any. I am using CxF 2.2.5. I set a breakpoint in SoapHeaderInterceptor and stepped through it, but did not see any problems. Is there a better place to set a breakpoint to debug this?

Does anyone know what's going wrong?

Thanks,
Howard

RE: Start time of cxf

2009-12-21T11:09:53Z

Hi All,

I've been seeing the same thing, especially on machines that are not connected to the outside world (as might be expected). Is there any suggestion for a workaround here?

Thanks,
Thom

-----Original Message-----
From: Daniel Kulp [mailto:dkulp@...]
Sent: Monday, November 02, 2009 7:10 AM
To: users@...
Cc: florian.grunow@...
Subject: Re: Start time of cxf

It's definitely trying to download something schema related:

The last line in the stack with CXF is:
at org.apache.cxf.dosgi.dsw.OsgiUtils.readIntentMap(OsgiUtils.java:422)

Thus, it's something in the intent map. Looking at it:
org.springframework.beans.factory.xml.DefaultDocumentLoader.loadDocument(DefaultDocumentLoader.java:75)
org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:396)

Those two lines are while parsing the Spring beans files. It's loading the
XML and trying to validate the beans files. Thus, this is down in Spring
someplace.

Dan

On Mon November 2 2009 7:22:09 am florian.grunow@... wrote:

> Hi there!
>
> Daniel Kulp <dkulp@...> wrote on 30.10.2009 17:45:29:
> > Can you "kill -3" the container during this and see the stack trace?
> > I'm
> >
> > wondering if it's downloading a schema off the internet or something.
>
> I attached the dump when running kill -3 during cxf startup.
>
> Any ideas?
>
> How long does it take on your machines?
>
> Cheers,
>
> Florian
>
>
>
> InterComponentWare AG:
> Vorstand: Dr. Lutz Kleinholz (Vors.), Dr. Georg Ralle, Jörg Stadler /
> Aufsichtsratsvors.: Prof. Dr. Christof Hettich Firmensitz: 69190
> Walldorf, Industriestraße 41 / AG Mannheim HRB 351761 / USt.-IdNr.:
> DE 198388516 =
>

--
Daniel Kulp
dkulp@...
http://www.dankulp.com/blog