Hi James,
I would be happy to contribute. Can you tell me where I should start
looking at ?
Cheers
Guillqume
On Dec 10, 2007 11:09 AM, James Mao [EMAIL PROTECTED] wrote:
I don't think that we have such an option, you can file a jira, patches
are always welcome ;)
Regards,
James
Hi,
Benjamin Coiffe,
Software Engineer
InforSense Ltd.
Colet Court
100 Hammersmith Road
London
W6 7JP
Email: [EMAIL PROTECTED]
Skype: benjamin.inforsense
-Original Message-
From: tog [mailto:[EMAIL PROTECTED]
Sent: Sun 12/9/2007 8:58 AM
To: cxf-user@incubator.apache.org
Subject: Re:
James, Jervis
Thanks for your help,
First I checked if my XML modified file were still well-formed :
actually they are well-formed...
Then I checked my Client code, but I had correctly updated the service
and port QName to reflect my changes.
I did not have the opportunity yet to use tcpmon
Hi all,
I'm trying to deploy a very simple REST Webservice, using two Get methods:
@WebService(name=GetWorkOrderServiceRest,
targetNamespace=http://webservice.api.wow;)
public class GetWorkOrderServiceRestImpl implements GetWorkOrderServiceRest
{
@Get
@HttpResource(location=/workorders)
public
FWIW I fixed the issue by replacing foobar.com with foobar.net
I must admit that I don't understand why it now works...
--
Eric Le Goff
I forgot to attach the wsdl...
Hi,
The Dymamic client factory fails to create a client for the WSDL I
have
attached to this email.
It is because of the complex type and the reference to a schema:
s:element name=GetMaterialDataResponse
s:complexType
s:sequence
It got removed. It is at the end of the email.
Thanks
Hi,
The Dymamic client factory fails to create a client for the WSDL I
have
attached to this email.
It is because of the complex type and the reference to a schema:
s:element name=GetMaterialDataResponse
s:complexType
Any thoughts?
--
View this message in context:
http://www.nabble.com/XML-elements-does-not-belong-to-the-namespace-tp14247019p14254461.html
Sent from the cxf-user mailing list archive at Nabble.com.
Nothing so far...
I'm feeling stupid right now. I think I will have to go back and learn more
about XML. Problem is, time is not something we can afford :/. Is there any
other way to make them Serializable (without, of course, having to write our
own solution to add that manually)?
Jim Ma-3
Hi ..
.. today I started migration of our product from XFire to CXF.
I fail on first step :-(
We use Jsr181HandlerMapping + XFireServletControllerAdapter in XFire.
I see this method as only true Spring integration. Spring handles URL
and XFIRE handles WS. Clear and smart.
In CFX I see
Currently there isn't Spring MVC support. We found that it wasn't
widely used and since we're always short on time we didn't focus our
limited resources on it. Not to say that we wouldn't support it - I
believe it could be done pretty easily with the ServletController class
which is very
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
I found the JIRA issue related to my problem:
https://issues.apache.org/jira/browse/CXF-897
I'm trying to follow the workarounds listed in the bug report.
a) I tried workaround #4, (i.e. renamed the argument in the implementation
class on the server to 'arg0') but unfortunately that didn't
Sad, but I will have to keep using Metro RI wsimport instead of CXF
wsdl2java.
daniel.mfreitas wrote:
Nothing so far...
I'm feeling stupid right now. I think I will have to go back and learn
more about XML. Problem is, time is not something we can afford :/. Is
there any other way to
Hello. My application is running ok, the only thing I would like to get rid
of is a stack trace that is printed on the server log every time a client
creates an instance of the service using the stubs created by reading the
wsdl.
The client stubs were created using Metro RI wsimport tool with
The ClientProxyFactoryBean has a
setServiceName(QName serviceName)
and
setEndpointName(QName endpointName)
calls.You would probably need to do a ?wsdl thing on the endpoint
once with your browser or similar to figure out what they are. Just
call those methods on the factory before
I was trying to configure JAX-WS Handler as part of spring configuration
file. I don't find any means to do that. Is it possible to register JAX-WS
Handler at deploy time instead of using @HandlerChain annotation. I don't
want every java class to declare this handler chain.
For example
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
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
There is a standard way to configure JAX-WS handlers using configuration files,
please refer to the jaxws_handlers demo
(jaxws_handlers\src\demo\handlers\common\demo_handlers.xml) shipped with CXF
distribution. The lifecycle of JAX-WS handlers has to be handled by JAX-WS
runtime, not by
Cannot spot any obvious error in your code. Could you copy me the log messages
when your server starts up, it should look like sth below:
2007-12-11 11:49:25 org.apache.cxf.service.factory.ReflectionServiceFactoryBean
buildServiceFromClass
INFO: Creating Service
21 matches
Mail list logo
