Re: Exception in CustomerNotFoundFault - getFaultInfo()
I don't think it's actually a problem. The stack trace is an INFO level log to show on the server side that an exception was thrown. Most likely, if you changed the log level for org.apache.cxf.phase.PhaseInterceptorChain to warning or similar, it would go away. I think there was something logged someplace to remove the stack trace from that and just log the message. Not really sure though. Dan On Friday 14 December 2007, priya j wrote: > Hi, > > I follow the Customer Example in sample. when the customer object is > null it throw the CustomerNotFoundFault(details). > when i execute i get the following error, can you tell me where im > going wrong or is that anything else i need to add. > Please do help me, im new to web services. > Thanks inadvance. > > > ERROR > Dec 15, 2007 9:49:43 AM org.apache.cxf.phase.PhaseInterceptorChain > doIntercept > > INFO: Interceptor has thrown exception, unwinding now > > org.apache.cxf.interceptor.Fault > > at org.apache.cxf.service.invoker.AbstractInvoker.createFault( > > AbstractInvoker.java:107) > at org.apache.cxf.jaxws.JAXWSMethodInvoker.createFault( > > JAXWSMethodInvoker.java:76) > at org.apache.cxf.service.invoker.AbstractInvoker.invoke( > > AbstractInvoker.java:95) > at org.apache.cxf.jaxws.JAXWSMethodInvoker.invoke( > > JAXWSMethodInvoker.java:100) > at org.apache.cxf.service.invoker.AbstractInvoker.invoke( > > AbstractInvoker.java:68) > at org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run( > > ServiceInvokerInterceptor.java:56) > at org.apache.cxf.workqueue.SynchronousExecutor.execute( > > SynchronousExecutor.java:37) > at org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage( > > ServiceInvokerInterceptor.java:92) > at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept( > > PhaseInterceptorChain.java:207) > at org.apache.cxf.transport.ChainInitiationObserver.onMessage( > > ChainInitiationObserver.java:73) > at org.apache.cxf.transport.servlet.ServletDestination.doMessage( > > ServletDestination.java:79) > at > org.apache.cxf.transport.servlet.ServletController.invokeDestination( > > ServletController.java:256) > at org.apache.cxf.transport.servlet.ServletController.invoke( > > ServletController.java:123) > at org.apache.cxf.transport.servlet.AbstractCXFServlet.invoke( > > AbstractCXFServlet.java:170) > at org.apache.cxf.transport.servlet.AbstractCXFServlet.doGet( > > AbstractCXFServlet.java:152) > at javax.servlet.http.HttpServlet.service( > > HttpServlet.java:690) > at javax.servlet.http.HttpServlet.service( > > HttpServlet.java:803) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter( > > ApplicationFilterChain.java:290) > at org.apache.catalina.core.ApplicationFilterChain.doFilter( > > ApplicationFilterChain.java:206) > at org.apache.catalina.core.StandardWrapperValve.invoke( > > StandardWrapperValve.java:233) > at org.apache.catalina.core.StandardContextValve.invoke( > > StandardContextValve.java:175) > at org.apache.catalina.core.StandardHostValve.invoke( > > StandardHostValve.java:128) > at org.apache.catalina.valves.ErrorReportValve.invoke( > > ErrorReportValve.java:102) > at org.apache.catalina.core.StandardEngineValve.invoke( > > StandardEngineValve.java:109) > at org.apache.catalina.connector.CoyoteAdapter.service( > > CoyoteAdapter.java:263) > at org.apache.coyote.http11.Http11Processor.process( > > Http11Processor.java:844) > at > org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.proces >s( > > Http11Protocol.java:584) > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run( > > JIoEndpoint.java:447) > at java.lang.Thread.run(Unknown Source) > > Caused by: sg.sphsearch.sfe.webService.server.CustomerNotFoundFault > > at sg.sphsearch.sfe.webService.server.LwiWebService.getQueryResult( > > LwiWebService.java:75) > 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.apache.cxf.service.invoker.AbstractInvoker.performInvocation( > > AbstractInvoker.java:124) > at org.apache.cxf.service.invoker.AbstractInvoker.invoke( > > AbstractInvoker.java:82) > ... 26 more -- J. Daniel Kulp Principal Engineer, IONA [EMAIL PROTECTED] http://www.dankulp.com/blog
Exception in CustomerNotFoundFault - getFaultInfo()"
Hi, I follow the Customer Example in sample. when the customer object is null it throw the CustomerNotFoundFault(details). when i execute i get the following error, can you tell me where im going wrong or is that anything else i need to add. Please do help me, im new to web services. Thanks inadvance. ERROR Dec 15, 2007 9:49:43 AM org.apache.cxf.phase.PhaseInterceptorChain doIntercept INFO: Interceptor has thrown exception, unwinding now org.apache.cxf.interceptor.Fault at org.apache.cxf.service.invoker.AbstractInvoker.createFault( AbstractInvoker.java:107) at org.apache.cxf.jaxws.JAXWSMethodInvoker.createFault( JAXWSMethodInvoker.java:76) at org.apache.cxf.service.invoker.AbstractInvoker.invoke( AbstractInvoker.java:95) at org.apache.cxf.jaxws.JAXWSMethodInvoker.invoke( JAXWSMethodInvoker.java:100) at org.apache.cxf.service.invoker.AbstractInvoker.invoke( AbstractInvoker.java:68) at org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run( ServiceInvokerInterceptor.java:56) at org.apache.cxf.workqueue.SynchronousExecutor.execute( SynchronousExecutor.java:37) at org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage( ServiceInvokerInterceptor.java:92) at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept( PhaseInterceptorChain.java:207) at org.apache.cxf.transport.ChainInitiationObserver.onMessage( ChainInitiationObserver.java:73) at org.apache.cxf.transport.servlet.ServletDestination.doMessage( ServletDestination.java:79) at org.apache.cxf.transport.servlet.ServletController.invokeDestination( ServletController.java:256) at org.apache.cxf.transport.servlet.ServletController.invoke( ServletController.java:123) at org.apache.cxf.transport.servlet.AbstractCXFServlet.invoke( AbstractCXFServlet.java:170) at org.apache.cxf.transport.servlet.AbstractCXFServlet.doGet( AbstractCXFServlet.java:152) at javax.servlet.http.HttpServlet.service( HttpServlet.java:690) at javax.servlet.http.HttpServlet.service( HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter( ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter( ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke( StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke( StandardContextValve.java:175) at org.apache.catalina.core.StandardHostValve.invoke( StandardHostValve.java:128) at org.apache.catalina.valves.ErrorReportValve.invoke( ErrorReportValve.java:102) at org.apache.catalina.core.StandardEngineValve.invoke( StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service( CoyoteAdapter.java:263) at org.apache.coyote.http11.Http11Processor.process( Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process( Http11Protocol.java:584) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run( JIoEndpoint.java:447) at java.lang.Thread.run(Unknown Source) Caused by: sg.sphsearch.sfe.webService.server.CustomerNotFoundFault at sg.sphsearch.sfe.webService.server.LwiWebService.getQueryResult( LwiWebService.java:75) 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.apache.cxf.service.invoker.AbstractInvoker.performInvocation( AbstractInvoker.java:124) at org.apache.cxf.service.invoker.AbstractInvoker.invoke( AbstractInvoker.java:82) ... 26 more -- View this message in context: http://www.nabble.com/Exception-in-CustomerNotFoundFault---getFaultInfo%28%29%22-tp14343491p14343491.html Sent from the cxf-user mailing list archive at Nabble.com.
Exception in CustomerNotFoundFault - getFaultInfo()
Hi, I follow the Customer Example in sample. when the customer object is null it throw the CustomerNotFoundFault(details). when i execute i get the following error, can you tell me where im going wrong or is that anything else i need to add. Please do help me, im new to web services. Thanks inadvance. ERROR Dec 15, 2007 9:49:43 AM org.apache.cxf.phase.PhaseInterceptorChain doIntercept INFO: Interceptor has thrown exception, unwinding now org.apache.cxf.interceptor.Fault at org.apache.cxf.service.invoker.AbstractInvoker.createFault( AbstractInvoker.java:107) at org.apache.cxf.jaxws.JAXWSMethodInvoker.createFault( JAXWSMethodInvoker.java:76) at org.apache.cxf.service.invoker.AbstractInvoker.invoke( AbstractInvoker.java:95) at org.apache.cxf.jaxws.JAXWSMethodInvoker.invoke( JAXWSMethodInvoker.java:100) at org.apache.cxf.service.invoker.AbstractInvoker.invoke( AbstractInvoker.java:68) at org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run( ServiceInvokerInterceptor.java:56) at org.apache.cxf.workqueue.SynchronousExecutor.execute( SynchronousExecutor.java:37) at org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage( ServiceInvokerInterceptor.java:92) at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept( PhaseInterceptorChain.java:207) at org.apache.cxf.transport.ChainInitiationObserver.onMessage( ChainInitiationObserver.java:73) at org.apache.cxf.transport.servlet.ServletDestination.doMessage( ServletDestination.java:79) at org.apache.cxf.transport.servlet.ServletController.invokeDestination( ServletController.java:256) at org.apache.cxf.transport.servlet.ServletController.invoke( ServletController.java:123) at org.apache.cxf.transport.servlet.AbstractCXFServlet.invoke( AbstractCXFServlet.java:170) at org.apache.cxf.transport.servlet.AbstractCXFServlet.doGet( AbstractCXFServlet.java:152) at javax.servlet.http.HttpServlet.service( HttpServlet.java:690) at javax.servlet.http.HttpServlet.service( HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter( ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter( ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke( StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke( StandardContextValve.java:175) at org.apache.catalina.core.StandardHostValve.invoke( StandardHostValve.java:128) at org.apache.catalina.valves.ErrorReportValve.invoke( ErrorReportValve.java:102) at org.apache.catalina.core.StandardEngineValve.invoke( StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service( CoyoteAdapter.java:263) at org.apache.coyote.http11.Http11Processor.process( Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process( Http11Protocol.java:584) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run( JIoEndpoint.java:447) at java.lang.Thread.run(Unknown Source) Caused by: sg.sphsearch.sfe.webService.server.CustomerNotFoundFault at sg.sphsearch.sfe.webService.server.LwiWebService.getQueryResult( LwiWebService.java:75) 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.apache.cxf.service.invoker.AbstractInvoker.performInvocation( AbstractInvoker.java:124) at org.apache.cxf.service.invoker.AbstractInvoker.invoke( AbstractInvoker.java:82) ... 26 more -- View this message in context: http://www.nabble.com/Exception-in-CustomerNotFoundFault---getFaultInfo%28%29-tp14339904p14339904.html Sent from the cxf-user mailing list archive at Nabble.com.
Overloaded methods - XFire->CXF with Aegis
I have a WebService class that has a pair of overloaded methods.
One has two parameters - an object reference and a long value, returning an
array of objects. The other adds a third parameter, a String.
I'm using Spring and jaxws:endpoint tags to load the service, per many of
the examples on the CXF site, and most of this stuff works, but it appears
to be complaining about overloaded methods when I fire up Tomcat:
org.springframework.beans.factory.BeanCreationException: Error creating bean
with name 'TradingPartnershipService': Invocation of init method failed;
nested exception is java.lang.IllegalArgumentException: An operation with
name [{http://ws.catalog.inovis.com}getRetailersWithAccess] already exists
in this service
Caused by:
java.lang.IllegalArgumentException: An operation with name
[{http://ws.catalog.inovis.com}getRetailersWithAccess] already exists in
this service
at
org.apache.cxf.service.model.InterfaceInfo.addOperation(InterfaceInfo.java:71)
at
org.apache.cxf.service.factory.ReflectionServiceFactoryBean.createOperation(ReflectionServiceFactoryBean.java:454)
My interface defines these as follows:
public RetailerAccess[] getRetailersWithAccess(
@WebParam(name = "UserIdentifier", targetNamespace =
TNS)UserIdentifier userId,
@WebParam(name = "vendorAccountNumber", targetNamespace =
TNS)long vendorAccountId
);
public RetailerAccess[] getRetailersWithAccess(
@WebParam(name = "UserIdentifier", targetNamespace =
TNS)UserIdentifier userId,
@WebParam(name = "vendorAccountNumber", targetNamespace =
TNS)long vendorAccountId,
@WebParam(name = "selcode", targetNamespace = TNS)String selcode
) throws WebServiceException;
Is there some additional configuration I can do for CXF to handle these
overloads correctly? Or should I plan to rename one of them?
Thanks in advance.
--
View this message in context:
http://www.nabble.com/Overloaded-methods---XFire-%3ECXF-with-Aegis-tp14339900p14339900.html
Sent from the cxf-user mailing list archive at Nabble.com.
Re: Question about wsdl:import and xsd:extension
So, how do you reference xsds or wsdls from a wsdl that is being ran through
wsdl2java? I was looking at the cxf documentation and keep seem to figure
out the appropriate way unless they are in the same directory, which I
wouldn't want. I would prefer to have them referenced in their containing
jar file to make it easy to plug into servicemix.. but I can't seem to
figure this out or find good examples of how to use the catalog file, or
when it is appropriate to use it.
I'm still using cxf 2.0.2 btw since servicemix hasn't gotten to 2.0.3 ...
not sure if I should try to add it in myself to my deployment.
On Dec 11, 2007 4:40 PM, Daniel Kulp <[EMAIL PROTECTED]> wrote:
>
> Actually, I just read the original question... :-(
>
> If the location attribute on the import element is a full resolvable URL
> AND it's not remapped via a catalog, it should be left as is and not
> remapped to the internal wsdl/xsd serving code.If that's not what's
> happening, I'll definitely need to dig into some code some more to
> figure out why.
>
> If you look in WSDLQueryHandler (rt/core) in the updateSchemaImports
> method, if the location is a valid URL, we just let it be.
>
> Dan
>
>
> On Monday 10 December 2007, Silberman, Nathan wrote:
> > I'm using a 2.1 snapshot
> >
> > -Original Message-
> > From: Daniel Kulp [mailto:[EMAIL PROTECTED]
> > Sent: Monday, December 10, 2007 6:09 PM
> > To: cxf-user@incubator.apache.org
> > Cc: Silberman, Nathan
> > Subject: Re: Question about wsdl:import and xsd:extension
> >
> >
> > What version of CXF? There were some bugs in this area that were
> > fixed
> >
> > for 2.0.3.
> >
> > Dan
> >
> > On Monday 10 December 2007, Silberman, Nathan wrote:
> > > Glen,
> > >
> > > Thanks for the help. The problem I am encountering is that the
> > > ServletController seems unable to find the xsds in that directory.
> > > The
> > >
> > > ServletTransportFactory lists only my services in its destinations
> > > map.
> > >
> > > This code in the ServletController seems to not be able to find the
> > > xsd in the wsdl directory, I believe for the aformentioned reasons.
> > >
> > >try {
> > > EndpointInfo ei = new EndpointInfo();
> > > String address = request.getPathInfo() == null ? "" :
> > > request.getPathInfo();
> > >
> > > ei.setAddress(address);
> > > ServletDestination d =
> > > (ServletDestination)transport.getDestinationForPath(ei.getAddress())
> > >;
> > >
> > > if (d == null) {
> > > if (request.getRequestURI().endsWith("/services")
> > >
> > > || request.getRequestURI().endsWith("/services/"
> > > ||) StringUtils.isEmpty(request.getPathInfo())
> > > || "/".equals(request.getPathInfo())) {
> > >
> > > updateDests(request);
> > > generateServiceList(request, res);
> > >
> > > It seems to be looking for services only. Any thoughts?
> > >
> > > Nathan
> > >
> > >
> > >
> > > -Original Message-
> > > From: Glen Mazza [mailto:[EMAIL PROTECTED]
> > > Sent: Friday, December 07, 2007 1:28 PM
> > > To: cxf-user@incubator.apache.org
> > > Subject: RE: Question about wsdl:import and xsd:extension
> > >
> > > Am Freitag, den 07.12.2007, 11:02 -0500 schrieb Silberman, Nathan:
> > > > Does CXF have a standard file structure/method for where to place
> > > > the xsds if one abstracts out schemas to external files?
> > >
> > > The standard JAX-WS way I believe (from JSR 109) is that the wsdl
> > > and xsd's go into your WEB-INF/wsdl directory of the WAR supporting
> > > your web service.
> > >
> > > > Since the import I
> > > > have refers to a URI like:
> > > >
> > > > > > > location="http://mysite.com/schemas/myschema.xsd"/>
> > > >
> > > > I need to alter my web.xml to tell CXF not to route this request
> > > > to the CXFServlet and instead have a regular file serving servlet
> > > > that will server the XSD. Is there any other way to do this?
> > >
> > > Place the XSD's in the wsdl subdirectory as mentioned above? It
> > > should be accessible that way, just like the wsdl is when it is in
> > > that directory.
> > >
> > > Glen
> >
> > --
> > J. Daniel Kulp
> > Principal Engineer
> > IONA
> > P: 781-902-8727C: 508-380-7194
> > [EMAIL PROTECTED]
> > http://www.dankulp.com/blog
>
>
>
> --
> J. Daniel Kulp
> Principal Engineer
> IONA
> P: 781-902-8727C: 508-380-7194
> [EMAIL PROTECTED]
> http://www.dankulp.com/blog
>
Re: sample failure: restfull_http_binding
JSON isn't like XML. Its basically a serialized hashmap. It doesn't
allow multiple entries with the same "key". Which means there can only
ever be one acme.customer. Because of this, when there are multiple
acme.customers, we need to turn it into an array like in the sample you
attached.
Regards,
- Dan
YI (William) ZHU wrote:
Hi,
I found that there two issues in the CXF 2.0.2 sample
"restfull_http_binding":
1) the "test.html" page to test the "Jettison/CXF AJAX Demo" is not working,
I found that the javascript has problem.
2) if I change the "CustomerServiceImpl.java" file to let the web service to
return two customers, not the original 1 customer. Then following links
work fine:
http://localhost:8080/xml/customers
http://localhost:8080/xml/customers/123
http://localhost:8080/json/customers/123
but this link "http://localhost:8080/json/customers"; return:
{"acme.Customers":{"acme.customer":[{"acme.id":"789","acme.name":"William
Zhu"},{"acme.id":"123","acme.name":"Dan Diephouse"}]}}
I thought that's not correct, they should return two "acme.customer" items.
Can someone check the implementation of JSON on CXF is OK?
Thanks,
YI ZHU
--
Dan Diephouse
MuleSource
http://mulesource.com | http://netzooid.com/blog
Re: sample failure: restfull_http_binding
...continue...
should the return from JSON server be like:
{"acme.Customers":{"acme.customer":[{"acme.id":"789","acme.name":"William
Zhu"},{"acme.id":"123","acme.name":"Dan Diephouse"}]}}
or like this?
{"acme.Customers":{"acme.customer":{"acme.id":"789","acme.name":"William
Zhu"}},{"acme.customer":{"acme.id":"123","acme.name":"Dan Diephouse"}}}
I think that second one is correct. The first one is from server (JSON).
--
View this message in context:
http://www.nabble.com/sample-failure%3A-restfull_http_binding-tp14339771p14339790.html
Sent from the cxf-user mailing list archive at Nabble.com.
Re: sample failure: restfull_http_binding
I think these are logged as:
https://issues.apache.org/jira/browse/CXF-873
https://issues.apache.org/jira/browse/CXF-889
Patches are most welcome.
Dan
On Friday 14 December 2007, YI (William) ZHU wrote:
> Hi,
>
> I found that there two issues in the CXF 2.0.2 sample
> "restfull_http_binding":
>
> 1) the "test.html" page to test the "Jettison/CXF AJAX Demo" is not
> working, I found that the javascript has problem.
>
> 2) if I change the "CustomerServiceImpl.java" file to let the web
> service to return two customers, not the original 1 customer. Then
> following links work fine:
>http://localhost:8080/xml/customers
>http://localhost:8080/xml/customers/123
>http://localhost:8080/json/customers/123
>
> but this link "http://localhost:8080/json/customers"; return:
>
> {"acme.Customers":{"acme.customer":[{"acme.id":"789","acme.name":"Will
>iam Zhu"},{"acme.id":"123","acme.name":"Dan Diephouse"}]}}
>
> I thought that's not correct, they should return two "acme.customer"
> items.
>
> Can someone check the implementation of JSON on CXF is OK?
>
>
> Thanks,
> YI ZHU
--
J. Daniel Kulp
Principal Engineer, IONA
[EMAIL PROTECTED]
http://www.dankulp.com/blog
sample failure: restfull_http_binding
Hi,
I found that there two issues in the CXF 2.0.2 sample
"restfull_http_binding":
1) the "test.html" page to test the "Jettison/CXF AJAX Demo" is not working,
I found that the javascript has problem.
2) if I change the "CustomerServiceImpl.java" file to let the web service to
return two customers, not the original 1 customer. Then following links
work fine:
http://localhost:8080/xml/customers
http://localhost:8080/xml/customers/123
http://localhost:8080/json/customers/123
but this link "http://localhost:8080/json/customers"; return:
{"acme.Customers":{"acme.customer":[{"acme.id":"789","acme.name":"William
Zhu"},{"acme.id":"123","acme.name":"Dan Diephouse"}]}}
I thought that's not correct, they should return two "acme.customer" items.
Can someone check the implementation of JSON on CXF is OK?
Thanks,
YI ZHU
--
View this message in context:
http://www.nabble.com/sample-failure%3A-restfull_http_binding-tp14339771p14339771.html
Sent from the cxf-user mailing list archive at Nabble.com.
Re: Dispatch.invokeOneWay() over JMS transport
Just committed a fix for this. invokeOneWay was definitely not setting
the isOneWay flag on the Exchange. One line fix. :-)
I'll try and get new snapshots up this weekend.
Dan
On Wednesday 12 December 2007, Daniel Kulp wrote:
> Hmm... I wonder if this is related to:
>
> https://issues.apache.org/jira/browse/CXF-941
>
> I think the Dispatch.invokeOneWay stuff isn't letting the transport
> know not to expect a response.
>
> Dan
>
> On Wednesday 12 December 2007, Amah Ahite wrote:
> > Hi,
> > I am trying to configure CXF to redirect an asynchronous call
> > response to a queue an MDB listen on but it does not work as
> > expected. I started from the java_first_jaxws example code where I
> > change the server configuration as following :
> >
> >
> > > jndiConnectionFactoryName="ConnectionFactory"
> > jndiDestinationName="dynamicQueues/test.cxf.jmstransport.queue"
> > jndiReplyDestinationName="dynamicQueues/test.cxf.jmstransport.queue
> >.r eply" connectionUserName="testUser"
> > connectionPassword="testPassword"> > name="java.naming.factory.initial"
> > value="org.apache.activemq.jndi.ActiveMQInitialContextFactory"
> > />
> > > value="tcp://localhost:61616" />
> >
> >
> >
> >
> > and create a client that call the server using the Dispatch
> > interface:
> >
> >
> >
> > package test.client;
> > import java.io.StringReader;
> >
> > import javax.wsdl.extensions.soap12.SOAP12Binding;
> > import javax.xml.namespace.QName;
> > import javax.xml.transform.stream.StreamSource;
> > import javax.xml.ws.Dispatch;
> > import javax.xml.ws.Service;
> >
> > import org.apache.cxf.binding.soap.SoapBindingFactory;
> > import org.apache.cxf.helpers.IOUtils;
> > import org.apache.cxf.jaxws.support.BindingID;
> >
> > public class DispatchClientJMS {
> > public static void main(String[] args) throws Exception{
> > QName serviceName = new QName("http://service.test/";,
> > "HelloWorld"); Service s = Service.create(serviceName);
> >
> > QName portName = new QName("http://service.test/";,
> > "HelloWorldPort");
> > s.addPort(portName,SoapBindingFactory.SOAP_11_BINDING , "jms://");
> > Dispatch dispatch = s.createDispatch(portName,
> > StreamSource.class, Service.Mode.PAYLOAD);
> >
> > String req = " > xmlns:ns1='http://service.test/'>HI";
> > dispatch.invokeOneWay(new StreamSource(new StringReader(req)));
> > // StreamSource response = dispatch.invoke(new StreamSource(new
> > StringReader(req)));
> > System.out.println(IOUtils.toString(response.getInputStream()));
> > }
> > }
> >
> >
> >
> > The response is sent to the
> > dynamicQueues/test.cxf.jmstransport.queue.reply queue as expected
> > but the client does not return from
> > dispatch.invokeOneWay() method.
> >
> > Please could you tell me what I missing.
> >
> > Thanks you.
--
J. Daniel Kulp
Principal Engineer, IONA
[EMAIL PROTECTED]
http://www.dankulp.com/blog
Re: Upgrading from XFire to CXF
On Friday 14 December 2007, Bernd Schuller wrote: > that is absolutely great news, XmlBeans finally in the works! > > I'd be glad to provide some testing cycles. Is there > a good way to not have to compile *all* of CXF for this? > Sort of like a recommendation for a limited environment for > XmlBeans development? Well, you can always download the snapshot kits and just use them. I try to deploy new snapshots every couple of days. That said, if you checkout cxf from SVN, building the entire thing is fairly quick if you do "mvn install -Pfastinstall". (use the fastinstall profile we have)That skips all kinds of stuff like running tests, code styles and warning checks, etcOnce you do that once, you can then cd to the rt/databindings/xmlbeans dir and just run mvn from there as you work in there. Dan > > Thanks a lot , > Bernd. > > Daniel Kulp wrote: > > Ooo. Just the person I need to chat more with. > > :-) > > > > Seriously, I've started writing an XmlBeans databinding for CXF. > > It's on the 2.1 trunk right now. However, it's VERY limitted in > > what it can do right now. I'm by far NOT an XmlBeans expert (the > > first time I looked at XmlBeans was to start writing this data > > binding) so I'm not really sure what the expectation are around > > this. If you have some sample services/test cases I could throw at > > it, that would be great. > > > > THAT said, I don't think there is any way you are going to remove > > the JAXB runtime from CXF. CXF uses it internally for parsing all > > kinds of configuration things, wsdl extensions, etc... > > > > Dan > > > > On Thursday 13 December 2007, mraible wrote: > >> We are currently using XFire in the AppFuse project and it works > >> great. > >> > >> We are aware that Apache CXF is the next generation of XFire. > >> However, we've also optimized the XFire footprint[1] to be as small > >> as possible. Part of this optimization was removing JAXB 2 support > >> and using XMLBeans instead. The XFire Migrating Guide[2] says that > >> XMLBeans will be supported in CXF 2.1. > >> > >> What is the timeline for a 2.1 release? > >> > >> Thanks, > >> > >> Matt > >> > >> [1] http://issues.appfuse.org/browse/APF-797 > >> [2] http://cwiki.apache.org/CXF20DOC/xfire-migration-guide.html -- J. Daniel Kulp Principal Engineer, IONA [EMAIL PROTECTED] http://www.dankulp.com/blog
Re: Aegis Binding - Hello World example fails with SchemaFactoryFinder$ConfigurationError
Sounds like a JDK bug or something. I'm not really sure why.
Dan
On Thursday 13 December 2007, tcs wrote:
> I set the following system property:
> -Djavax.xml.validation.SchemaFactory:http://www.w3.org/2001/XMLSchema=
>com.sun.org.apache.xerces.internal.jaxp.validation.xs.SchemaFactoryImpl
>
> And was able to start the server. Shouldn't it default to this? Why
> does it default to:
> http\://www.w3.org/2001/XMLSchema=com.sun.org.apache.xerces.internal.j
>axp.validation.xs.SchemaFactoryImpl
>
> thanks
>
> tcs wrote:
> > I'm trying to write a simple web service using Aegis but am running
> > into some issues. When I try to start the server, I get the
> > following exception:
> >
> > INFO: Creating Service {http://demo/}HelloWorld from class
> > demo.HelloWorld JAXP: find
> > factoryId=javax.xml.validation.SchemaFactory:http://www.w3.org/2001/
> >XMLSchema Exception in thread "main"
> > javax.xml.validation.SchemaFactoryFinder$ConfigurationError:
> > Provider
> > http\://www.w3.org/2001/XMLSchema=com.sun.org.apache.xerces.internal
> >.jaxp.validation.xs.SchemaFactoryImpl not found
> > at javax.xml.validation.SchemaFactoryFinder.newInstance(Unknown
> > Source) at
> > javax.xml.validation.SchemaFactoryFinder.findJarServiceProvider(Unkn
> >own Source)
> > at javax.xml.validation.SchemaFactoryFinder.find(Unknown Source)
> > at javax.xml.validation.SchemaFactory.newInstance(Unknown Source)
> > at
> > org.apache.cxf.aegis.type.XMLTypeCreator.(XMLTypeCreator.jav
> >a:115) at java.lang.J9VMInternals.initializeImpl(Native Method)
> > at java.lang.J9VMInternals.initialize(J9VMInternals.java:177)
> > at
> > org.apache.cxf.aegis.type.DefaultTypeMappingRegistry.createRootTypeC
> >reator(DefaultTypeMappingRegistry.java:244) at
> > org.apache.cxf.aegis.type.DefaultTypeMappingRegistry.createTypeCreat
> >or(DefaultTypeMappingRegistry.java:228) at
> > org.apache.cxf.aegis.type.DefaultTypeMappingRegistry.createTypeMappi
> >ng(DefaultTypeMappingRegistry.java:209) at
> > org.apache.cxf.aegis.type.DefaultTypeMappingRegistry.createTypeMappi
> >ng(DefaultTypeMappingRegistry.java:202) at
> > org.apache.cxf.aegis.databinding.AegisDatabinding.initialize(AegisDa
> >tabinding.java:144) at
> > org.apache.cxf.service.factory.ReflectionServiceFactoryBean.buildSer
> >viceFromClass(ReflectionServiceFactoryBean.java:293) at
> > org.apache.cxf.service.factory.ReflectionServiceFactoryBean.initiali
> >zeServiceModel(ReflectionServiceFactoryBean.java:333) at
> > org.apache.cxf.service.factory.ReflectionServiceFactoryBean.create(R
> >eflectionServiceFactoryBean.java:151) at
> > org.apache.cxf.frontend.AbstractWSDLBasedEndpointFactory.createEndpo
> >int(AbstractWSDLBasedEndpointFactory.java:74) at
> > org.apache.cxf.frontend.ServerFactoryBean.create(ServerFactoryBean.j
> >ava:108) at test.StartServer.usingAegis(StartServer.java:48)
> > at test.StartServer.main(StartServer.java:18)
> >
> > I'm trying to start the server as follows:
> > HelloWorldImpl bean= new HelloWorldImpl ();
> > ServerFactoryBean svrFactory = new ServerFactoryBean();
> > svrFactory.setServiceClass(HelloWorldImpl.class);
> > svrFactory.setAddress(url);
> > svrFactory.setServiceBean(bean);
> > svrFactory.setDataBinding(new AegisDatabinding());
> > svrFactory.create();
--
J. Daniel Kulp
Principal Engineer, IONA
[EMAIL PROTECTED]
http://www.dankulp.com/blog
Re: array - difference between JAXB and Aegis Binding
Nope. Not right now. The aegis databinging is very "type" oriented in
that it generates a "type" for each field. It doesn't try to collapse
them down into elements with maxOccurs. I looked into it a bit when
fixing https://issues.apache.org/jira/browse/CXF-1116, but it didn't
look easy so I just stuck with the ArrayOf stuff.
Dan
On Thursday 13 December 2007, tcs wrote:
> Hi,
>
> I wrote a simple web service with two methods, one that would take an
> array and one that would return an array.
>
> public String[] getAbc() {
> String[] strs = new String[3];
> strs[0] = "a";
> strs[1] = "b";
> strs[2] = "c";
> return strs;
> }
>
> public String setAbc(String[] args) {
> return "done";
> }
>
> I noticed that with JAXB binding, the WSDL created does not have the
> wrapper 'ArrayOf...' element present.
>
> elementFormDefault="unqualified"
> targetNamespace="http://server.hw.demo/";
> xmlns:tns="http://server.hw.demo/";
> xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
>
>
>
>
> type="xsd:string"/>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> type="xsd:string"/>
>
>
>
>
>
>
> However with Aegis binding, the wrapper 'ArrayOf...' elements are
> present. elementFormDefault="qualified"
> targetNamespace="http://server.hw.demo/";>
>
>
> name="string" nillable="true" type="xsd:string"/>
>
>
>
>
>
>
> type="tns:ArrayOfString"/>
>
>
>
>
>
> type="xsd:string"/>
>
>
>
>
>
>
>
>
>
> type="tns:ArrayOfString"/>
>
>
>
>
>
> I'd like to use Aegis binding. But would like my WSDL to not have the
> wrapper 'ArrayOf...' elements. Is that possible?
>
> thanks,
>
> Just as an fyi.. this issue was discussed in this thread:
> http://www.nabble.com/JAX-WS-Array-Support-tt8483460.html#a8483460
--
J. Daniel Kulp
Principal Engineer, IONA
[EMAIL PROTECTED]
http://www.dankulp.com/blog
Re: add more attribute to my XML element
There are two ways to go about doing this: 1) JAXB code generation approach: To the type that is represented by the QueryResult, (and is passed into your server), add the required attributes as fields, annotate them such that they are attributes instead of elements, and done. 2) Interceptor approach: This isn't exactly easy. You would need to take the XmlStreamWriter, wrapper it with a new XmlStreamWriter, and the first time the writeStartElement is called, add the needed attributes. Dan On Thursday 13 December 2007, priya j wrote: > Hi, > I am using the CXF HTTP binding for my application. I want to add some > more attribute to my xml element. > > output is: > > > - http://webservice.com";> > - > > > > I need something like the following > > > - http://www.w3.org/2001/XMLSchema-instance"; > ="http://webservice.com"; type="web" totalResultsAvailable="9430" > totalResultsReturned="3" firstResultPosition="1" > > - > > > > > something like the dynamic generated values. > Can anyone help me on this. > Thanks inadvance -- J. Daniel Kulp Principal Engineer, IONA [EMAIL PROTECTED] http://www.dankulp.com/blog
Re: IllegalStateException: Current state not START_ELEMENT when using LocalTransportFactory for testing and supplying multiple parameters
No idea. Any chance you could send a test case? I just updated our
test case (DirectDispatchClientTest) to invoke a 2 param method and it
was fine.
That said, there have been a couple fixes to the LocalTransport on trunk.
Dan
On Friday 14 December 2007, Zarar Siddiqi wrote:
> When using AbstractCXFTest and using a LocalTransportFactory to run
> tests, one gets an IllegalStateException thrown from
> com.ctc.wstx.sr.BasicStreamReader Line 641:
>
> public String getAttributeValue(String nsURI, String localName) {
> if (mCurrToken != START_ELEMENT) {
> throw new
> IllegalStateException(ErrorConsts.ERR_STATE_NOT_STELEM);
> }
> return mAttrCollector.getValue(nsURI, localName);
> }
>
> All the web service methods with a single argument are working fine
> but if you have multiple arguments (in my case 2), then the if
> condition (mCurrToken != START_ELEMENT) is evaluated to false with
> the value of mCurrToken being 4 and START_ELEMENT being 1 (this is
> probably specific to my service method but maybe it happens every time
> you have two arguments, i don't know). The same service runs fine
> when deployed inside a container (i.e.: not using
> LocalTransportFactory).
>
> I was about to create a JIRA for this but thought I'd let the user
> list look at it first.
>
> Thanks,
> Zarar Siddiqi
--
J. Daniel Kulp
Principal Engineer, IONA
[EMAIL PROTECTED]
http://www.dankulp.com/blog
Re: Upgrading from XFire to CXF
I think having XmlBeans support would be great, but I'm confused by your footprint motivation. After a quick inspection, XmlBeans is ~2.7 times as big as Jaxb impl: [01:50:46] dain$ ls -lh ~/.m2/repository/com/sun/xml/bind/jaxb-impl/ 2.0.5/jaxb-impl-2.0.5.jar -rw-r--r-- 1 dain dain769K Jun 24 13:38 /Users/dain/.m2/ repository/com/sun/xml/bind/jaxb-impl/2.0.5/jaxb-impl-2.0.5.jar [10:41:51] dain$ ls -lh ~/.m2/repository/org/apache/xmlbeans/xmlbeans/ 2.3.0/xmlbeans-2.3.0.jar -rw-r--r-- 1 dain dain 2M Oct 19 22:16 /Users/dain/.m2/ repository/org/apache/xmlbeans/xmlbeans/2.3.0/xmlbeans-2.3.0.jar And since Java6 includes JaxB, overtime you will be able to drop that also. Anyway, I think having XmlBean support is cool... I'm just a bit confused about the footprint comment. -dain On Dec 13, 2007, at 8:19 AM, mraible wrote: We are currently using XFire in the AppFuse project and it works great. We are aware that Apache CXF is the next generation of XFire. However, we've also optimized the XFire footprint[1] to be as small as possible. Part of this optimization was removing JAXB 2 support and using XMLBeans instead. The XFire Migrating Guide[2] says that XMLBeans will be supported in CXF 2.1. What is the timeline for a 2.1 release? Thanks, Matt [1] http://issues.appfuse.org/browse/APF-797 [2] http://cwiki.apache.org/CXF20DOC/xfire-migration-guide.html -- View this message in context: http://www.nabble.com/Upgrading-from- XFire-to-CXF-tp14319236p14319236.html Sent from the cxf-user mailing list archive at Nabble.com.
Re: AegisDataBinding and Spring - Web Service fails to deploy
We would need the full log and/or the stuff in logs/localhost.*.log. There should be a stack trace or something above that error that would describe what the "failed due to previous errors" thing points at. Dan On Friday 14 December 2007, tcs wrote: > When I deploy my web service app that uses Spring on Tomcat, the web > app does not deploy and I see the following messsage : > > SEVERE: Error listenerStart > 14-Dec-2007 12:05:35 PM org.apache.catalina.core.StandardContext start > SEVERE: Context [/SampleWebService] startup failed due to previous > errors > > > My web.xml file is: > > > PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN" > "http://java.sun.com/dtd/web-app_2_3.dtd";> > > > > contextConfigLocation > WEB-INF/beans.xml > > > > > org.springframework.web.context.ContextLoaderListener > > > > > CXFServlet > CXF Servlet > > org.apache.cxf.transport.servlet.CXFServlet > > 1 > > > > CXFServlet > /* > > > > My beans.xml file is: > 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";> > > > > > >class="org.apache.cxf.aegis.databinding.AegisDatabinding" /> >class="org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean"> > > > >class="org.apache.cxf.jaxws.support.JaxWsServiceConfiguration"/> class="org.apache.cxf.aegis.databinding.AegisServiceConfiguration"/> >class="org.apache.cxf.service.factory.DefaultServiceConfiguration"/> > > > > > >address="/actService"> > > > > > -- J. Daniel Kulp Principal Engineer, IONA [EMAIL PROTECTED] http://www.dankulp.com/blog
Re: XML elements does not belong to the namespace
1) the endpoint interface - this is pretty much never going to work with
the simple frontend client without writing some custom subclass of
AbstractServiceConfiguration to map the arg0 names to the real names.
I wouldn't bother pursuing this one.
2) That error just means you specified the wrong qname for something.
The StartClient.java you sent has:
QName END_POINT_NAME = new
QName("http://service.webservice";, "ActServiceEndPoint");
However, the port name in the wsdl you sent is:
ActServicePortBinding
Dan
On Friday 14 December 2007, tcs wrote:
> I tried the 2.0.4 SNAPSHOT version with the SampleWebService server
> and client code that I sent to you.
>
> I replaced the older 'cxf-2.0.3-incubator.jar' in my web-service and
> web-service client classpath with the updated
> 'cxf-2.0.4-incubator-SNAPSHOT.jar'
>
> I deployed my webservice on tomcat. The behaviour is the same as the
> older version of CXF.
>
> I tested the client by building the ClientProxyFactoryBean using:
>
> 1) the endpoint interface
> The marshalled SOAP request contained the 'arg0' element which were
> not understood by the server. The server returned a fault.
>
> Exception in thread "main" org.apache.cxf.binding.soap.SoapFault:
> webservice.service.InvalidArgumentException: getActByPid(), method
> parameter 'theActPid' cannot be null
> at
> org.apache.cxf.binding.soap.interceptor.Soap11FaultInInterceptor.handl
>eMessage(Soap11FaultInInterceptor.java:70) at
> ...
>
> 2) the server WSDL url
> This exception is same as before.
>
> Exception in thread "main"
> org.apache.cxf.service.factory.ServiceConstructionException: Could not
> find portType named
> {http://service.webservice}ActServiceEndPointPortType at
> org.apache.cxf.service.factory.ReflectionServiceFactoryBean.getInterfa
>ceInfo(ReflectionServiceFactoryBean.java:442) at
> org.apache.cxf.service.factory.ReflectionServiceFactoryBean.initialize
>WSDLOperations(ReflectionServiceFactoryBean.java:450) at
> org.apache.cxf.service.factory.ReflectionServiceFactoryBean.buildServi
>ceFromWSDL(ReflectionServiceFactoryBean.java:274) at
> org.apache.cxf.service.factory.ReflectionServiceFactoryBean.initialize
>ServiceModel(ReflectionServiceFactoryBean.java:360) at
> org.apache.cxf.service.factory.ReflectionServiceFactoryBean.create(Ref
>lectionServiceFactoryBean.java:156) at
> org.apache.cxf.frontend.AbstractWSDLBasedEndpointFactory.createEndpoin
>t(AbstractWSDLBasedEndpointFactory.java:74) at
> org.apache.cxf.frontend.ClientFactoryBean.create(ClientFactoryBean.jav
>a:51) at
> org.apache.cxf.frontend.ClientProxyFactoryBean.create(ClientProxyFacto
>ryBean.java:92) at
> client.StartClient.useServerWsdl(StartClient.java:74)
> at client.StartClient.main(StartClient.java:25)
>
> dkulp wrote:
> > I'm deploying a new 2.0.4 snapshot now that SHOULD fix it. (I'd
> > appreciate it if that could be verified) We'll probably shoot for
> > a 2.0.4 release mid January sometime.
> >
> > Dan
> >
> > On Thursday 13 December 2007, tcs wrote:
> >> Thanks very much for looking into this.
> >>
> >> I'm working on fixing this now, but it's definitely a fairly large
> >> change Any ideas as to when this will be working?
> >>
> >> Knowing when this feature would be available will be me plan my
> >> projects.
> >>
> >> thanks!
> >
> > --
> > J. Daniel Kulp
> > Principal Engineer
> > IONA
> > P: 781-902-8727C: 508-380-7194
> > [EMAIL PROTECTED]
> > http://www.dankulp.com/blog
--
J. Daniel Kulp
Principal Engineer, IONA
[EMAIL PROTECTED]
http://www.dankulp.com/blog
AegisDataBinding and Spring - Web Service fails to deploy
When I deploy my web service app that uses Spring on Tomcat, the web app does not deploy and I see the following messsage : SEVERE: Error listenerStart 14-Dec-2007 12:05:35 PM org.apache.catalina.core.StandardContext start SEVERE: Context [/SampleWebService] startup failed due to previous errors My web.xml file is: http://java.sun.com/dtd/web-app_2_3.dtd";> contextConfigLocation WEB-INF/beans.xml org.springframework.web.context.ContextLoaderListener CXFServlet CXF Servlet org.apache.cxf.transport.servlet.CXFServlet 1 CXFServlet /* My beans.xml file is: 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";> -- View this message in context: http://www.nabble.com/AegisDataBinding-and-Spring---Web-Service-fails-to-deploy-tp14339694p14339694.html Sent from the cxf-user mailing list archive at Nabble.com.
IllegalStateException: Current state not START_ELEMENT when using LocalTransportFactory for testing and supplying multiple parameters
When using AbstractCXFTest and using a LocalTransportFactory to run tests,
one gets an IllegalStateException thrown from
com.ctc.wstx.sr.BasicStreamReader Line 641:
public String getAttributeValue(String nsURI, String localName) {
if (mCurrToken != START_ELEMENT) {
throw new
IllegalStateException(ErrorConsts.ERR_STATE_NOT_STELEM);
}
return mAttrCollector.getValue(nsURI, localName);
}
All the web service methods with a single argument are working fine but if
you have multiple arguments (in my case 2), then the if condition
(mCurrToken != START_ELEMENT) is evaluated to false with the value of
mCurrToken being 4 and START_ELEMENT being 1 (this is probably specific to
my service method but maybe it happens every time you have two arguments, i
don't know). The same service runs fine when deployed inside a container
(i.e.: not using LocalTransportFactory).
I was about to create a JIRA for this but thought I'd let the user list look
at it first.
Thanks,
Zarar Siddiqi
--
View this message in context:
http://www.nabble.com/IllegalStateException%3A-Current-state-not-START_ELEMENT-when-using-LocalTransportFactory-for-testing-and-supplying-multiple-parameters-tp14338780p14338780.html
Sent from the cxf-user mailing list archive at Nabble.com.
Re: XML elements does not belong to the namespace
I tried the 2.0.4 SNAPSHOT version with the SampleWebService server and
client code that I sent to you.
I replaced the older 'cxf-2.0.3-incubator.jar' in my web-service and
web-service client classpath with the updated
'cxf-2.0.4-incubator-SNAPSHOT.jar'
I deployed my webservice on tomcat. The behaviour is the same as the older
version of CXF.
I tested the client by building the ClientProxyFactoryBean using:
1) the endpoint interface
The marshalled SOAP request contained the 'arg0' element which were not
understood by the server. The server returned a fault.
Exception in thread "main" org.apache.cxf.binding.soap.SoapFault:
webservice.service.InvalidArgumentException: getActByPid(), method parameter
'theActPid' cannot be null
at
org.apache.cxf.binding.soap.interceptor.Soap11FaultInInterceptor.handleMessage(Soap11FaultInInterceptor.java:70)
at
...
2) the server WSDL url
This exception is same as before.
Exception in thread "main"
org.apache.cxf.service.factory.ServiceConstructionException: Could not find
portType named {http://service.webservice}ActServiceEndPointPortType
at
org.apache.cxf.service.factory.ReflectionServiceFactoryBean.getInterfaceInfo(ReflectionServiceFactoryBean.java:442)
at
org.apache.cxf.service.factory.ReflectionServiceFactoryBean.initializeWSDLOperations(ReflectionServiceFactoryBean.java:450)
at
org.apache.cxf.service.factory.ReflectionServiceFactoryBean.buildServiceFromWSDL(ReflectionServiceFactoryBean.java:274)
at
org.apache.cxf.service.factory.ReflectionServiceFactoryBean.initializeServiceModel(ReflectionServiceFactoryBean.java:360)
at
org.apache.cxf.service.factory.ReflectionServiceFactoryBean.create(ReflectionServiceFactoryBean.java:156)
at
org.apache.cxf.frontend.AbstractWSDLBasedEndpointFactory.createEndpoint(AbstractWSDLBasedEndpointFactory.java:74)
at
org.apache.cxf.frontend.ClientFactoryBean.create(ClientFactoryBean.java:51)
at
org.apache.cxf.frontend.ClientProxyFactoryBean.create(ClientProxyFactoryBean.java:92)
at client.StartClient.useServerWsdl(StartClient.java:74)
at client.StartClient.main(StartClient.java:25)
dkulp wrote:
>
>
> I'm deploying a new 2.0.4 snapshot now that SHOULD fix it. (I'd
> appreciate it if that could be verified) We'll probably shoot for a
> 2.0.4 release mid January sometime.
>
> Dan
>
> On Thursday 13 December 2007, tcs wrote:
>> Thanks very much for looking into this.
>>
>> I'm working on fixing this now, but it's definitely a fairly large
>> change Any ideas as to when this will be working?
>>
>> Knowing when this feature would be available will be me plan my
>> projects.
>>
>> thanks!
>
>
>
> --
> J. Daniel Kulp
> Principal Engineer
> IONA
> P: 781-902-8727C: 508-380-7194
> [EMAIL PROTECTED]
> http://www.dankulp.com/blog
>
>
--
View this message in context:
http://www.nabble.com/XML-elements-does-not-belong-to-the-namespace-tp14247019p14338029.html
Sent from the cxf-user mailing list archive at Nabble.com.
Re: My own TrustManager
I'm pretty sure we won't be able to do this declaratively, at least in the current code. You should have some avenues for doing this programmatically, however. On the client side, see the HTTPConduitTest [1] in the CXF systests. I'm a bit less certain about the server side, though it should be possible (this was an initial design requirement). If you can get your hands on the Destination, you can downcast it to a JettyHTTPDestination, and from there you should be able to get the JettyHTTPServerEngine, on which you can set a collection of TLS parameters. There are some caveats, of course. For one, you probably need to do this before publishing the endpoint -- you can't change TLS parameters on an already-open socket. Also, these are all internal types, which require a lot of casts down to implementation-specific types. So you have no guarantee that these types will be supported across changes to CXF. And this stuff is only relevant to using the Jetty HTTP stack on the server side. YMMV with the servlet stack, or anything else that comes down the pipe. Hope that helps. Let us know if this works. If it does, feel free to contribute a test! Thanks, -Fred [1] https://svn.apache.org/repos/asf/incubator/cxf/trunk/systests/src/ test/java/org/apache/cxf/systest/http/HTTPConduitTest.java On Dec 13, 2007, at 10:12 AM, Bc. Jiří Mikulášek wrote: Hi all, I need to add some spicific features to my SSL communictaion - so basically I would like to implement my own TrustManager. But when using CXF the code suplying TrustManagers is not under my control. Is there any way how to do it ofr CXF? thanks for any hints -- Jiri Mikulasek - Developer AURA, s.r.o. Uvoz 499/56; 602 00 Brno ISO 9001 certified company AQAP 2110 (ČOS 051622) tel./fax: +420 544 508 115 e-mail: [EMAIL PROTECTED] http://www.aura.cz -
Re: bug in sec:include / exclude ?
Interesting. I wonder if this is related to https://issues.apache.org/jira/browse/CXF-1222 Could I ask you to check your CPU utilization, while your server comes up? On Dec 14, 2007, at 1:48 AM, Bc. Jiří Mikulášek wrote: Hi all, I wonder this problem when testiong how to force the hanshake to one specific algorithm. The interesting thing is that on client site all works perfectly as expected. On the server site something must be wrong, because I still didn't catch the goal. To be more specific: Client configuration: SSL_RSA_WITH_NULL_SHA Server configuration below should work, but I get either connection timeout or outofmemory error. SSL_RSA_WITH_NULL_SHA the same results SSL_RSA_WITH_NULL_SHA On Friday 14 of December 2007 04:55:55 Fred Dushin wrote: That doesn't seem right. If the filters are not doing the right thing, then this is definitely a bug and should be filed. Are you sure that the configuration you are specifying is getting applied to the endpiont that's getting logged? I have not seen this behavior before, but I also don't know how well the feature is tested in the code. -Fred On Dec 13, 2007, at 8:47 AM, Bc. Jiří Mikulášek wrote: Hi, I am using 2.0.2 and found strange behaviour: example: .*_WITH_RC4_.* .*_RSA_WITH_NULL_SHA.* gives message: INFO: The cipher suites have been set to TLS_RSA_WITH_AES_128_CBC_SHA, . containing RSA_WITH_NULL_SHA and .*_RSA_WITH_NULL_SHA.* .*_WITH_RC4_.* gives the same but containing WITH_RC4 and not containing RSA_WITH_NULL_SHA is the message bad or the algorithm is bad? -- Jiri Mikulasek - Developer AURA, s.r.o. Uvoz 499/56; 602 00 Brno ISO 9001 certified company AQAP 2110 (ČOS 051622) tel./fax: +420 544 508 115 e-mail: [EMAIL PROTECTED] http://www.aura.cz - -- Jiri Mikulasek - Developer AURA, s.r.o. Uvoz 499/56; 602 00 Brno ISO 9001 certified company AQAP 2110 (ČOS 051622) tel./fax: +420 544 508 115 e-mail: [EMAIL PROTECTED] http://www.aura.cz -
Re: Upgrading from XFire to CXF
Hi Dan, that is absolutely great news, XmlBeans finally in the works! I'd be glad to provide some testing cycles. Is there a good way to not have to compile *all* of CXF for this? Sort of like a recommendation for a limited environment for XmlBeans development? Thanks a lot , Bernd. Daniel Kulp wrote: Ooo. Just the person I need to chat more with. :-) Seriously, I've started writing an XmlBeans databinding for CXF. It's on the 2.1 trunk right now. However, it's VERY limitted in what it can do right now. I'm by far NOT an XmlBeans expert (the first time I looked at XmlBeans was to start writing this data binding) so I'm not really sure what the expectation are around this. If you have some sample services/test cases I could throw at it, that would be great. THAT said, I don't think there is any way you are going to remove the JAXB runtime from CXF. CXF uses it internally for parsing all kinds of configuration things, wsdl extensions, etc... Dan On Thursday 13 December 2007, mraible wrote: We are currently using XFire in the AppFuse project and it works great. We are aware that Apache CXF is the next generation of XFire. However, we've also optimized the XFire footprint[1] to be as small as possible. Part of this optimization was removing JAXB 2 support and using XMLBeans instead. The XFire Migrating Guide[2] says that XMLBeans will be supported in CXF 2.1. What is the timeline for a 2.1 release? Thanks, Matt [1] http://issues.appfuse.org/browse/APF-797 [2] http://cwiki.apache.org/CXF20DOC/xfire-migration-guide.html -- Dr. Bernd Schuller | mail: [EMAIL PROTECTED] | phone: +49 2461 61-8736 (fax: -6656) Distributed Systems and Grid Computing | personal blog: Juelich Supercomputing Centre | http://www.jroller.com/page/gridhaus http://www.fz-juelich.de/jsc | --- --- Forschungszentrum Jülich GmbH 52425 Jülich Sitz der Gesellschaft: Jülich Eingetragen im Handelsregister des Amtsgerichts Düren Nr. HR B 3498 Vorsitzende des Aufsichtsrats: MinDirig'in Bärbel Brumme-Bothe Geschäftsführung: Prof. Dr. Achim Bachem (Vorsitzender), Dr. Ulrich Krafft (stellv. Vorsitzender), Dr. Sebastian M. Schmidt --- ---
Re: SOAP flow Compression?
I tried something: I commented everything done in the handleMessage() method of the intercepteur used by the client. And I still have an error: org.apache.cxf.binding.soap.SoapFault: "null" is not a valid SOAP version. And when I debug this part, when I check the message object, I have a soap version!!! I use soap 1.2 and I can verify it in the message object!!! I really don't understand... Tophebboy wrote: > > Yes, I'm using Eclipse STP and SOA tools. > When you generate the code from your wsdl, a web.xml and a cxf-servlet.xml > are generated in the same folder as the wsdl. The same process occurs when > you generates your war. And the generated files > always overwrite your files... > > > > Glen Mazza-2 wrote: >> >> Am Donnerstag, den 13.12.2007, 08:45 -0800 schrieb Tophebboy: >>> I already saw that...But I think I'm missing something...I read it twice >>> and >>> it still doesn't work!! >>> Anyway, I found a way of activating it copying the interceptor bean >>> definition in the cxf-servlet.xml file (I have to this after deploying >>> the >>> project because each time I create a war file, eclipse erases my >>> cxf-servlet.xml file to put the default one at its place). >> >> I still don't understand this. Why would Eclipse have a "default" >> cxf-servlet.xml file that it surreptitiously inserts in the WAR? That >> file is completely specific to CXF, most Eclipse committers have never >> even heard of that file. Are you using the Eclipse SOA Tools >> plugin--maybe *it* does something strange like this. >> >> >>> I also copied the >>> client xml file in my client app, naming it cxf.xml. >>> The problem is that when I try to call my web service from the client, I >>> have now this exception: >>> java.io.IOException: Not in GZIP format >>> It seems to occur in the client which is receiving a message. That's >>> weird >>> because the first step is to send a request to the server, isn't it? And >>> the >>> error occurs before the handleMessage method on the server is called... >>> I really don't understand what is going on...:-( >>> >>> >> >> The email I just sent a few minutes ago to Jan in Germany had links to a >> Ant- and Maven- based builds, neither of which touch your >> cxf-servlet.xml file and neither (at least in my case) caused these >> error messages to occur. You may wish to move from IDE-based creation >> of web services to Maven or Ant-based instead. >> >> Glen >> >> >> >> > > -- View this message in context: http://www.nabble.com/SOAP-flow-Compression--tp14299256p14332949.html Sent from the cxf-user mailing list archive at Nabble.com.
