Coming to think of this again, I found supporting ProviderCorbaMessage isn't
that difficult as I originally thought. We have some manual checks of binding
type in DispatchInDatabindingInterceptor\DispatchOutDatabindingInterceptor,
such as if (binding == soapbinding) then blabla. Actually we
I'm loving CXF right now by the way, so thanks for that :)
I'd like to be able to send my current WSDL types over the wire
without soap envelopes as plain-old-xml via http POST operations.
I started with a WSDL and a pair of Request/Response type objects...
Running wsdl2java generates a
Hi Jervis, it really sounds great, cxf would be more flexible then. Thank you
for your replies. So do you plan adding support of that to cxf? And would it be
possible to know when? :-)
Cheers,
Michael
-Original Message-
From: Liu, Jervis [mailto:[EMAIL PROTECTED]
Sent: Monday, July
Hi Ray, What do you mean by not do the auto-magical xml stuff that CXF seems
to support now in the REST support? Do you mean you want to access the raw xml
message payload instead of marshalling the xml into objects? If this is the
case, you probably want to use the JAX-WS Provider/Dispatch
Yes, that is exactly what I mean.
Though I'd rather not deal with the payload directly. I'd like for CXF
to handle the marshaling and unmarshaling still.
On 7/30/07, Liu, Jervis [EMAIL PROTECTED] wrote:
Hi Ray, What do you mean by not do the auto-magical xml stuff that CXF
seems to support now
Sorry...
More specifically, I'd lile to use the Impl, Request, and Response
classes that the wsdl2java toll generated.
On 7/30/07, Ray Krueger [EMAIL PROTECTED] wrote:
Yes, that is exactly what I mean.
Though I'd rather not deal with the payload directly. I'd like for CXF
to handle the
That did it. Thanks Dan
On 7/29/07, Dan Diephouse [EMAIL PROTECTED] wrote:
No, that wouldn't cause the problem.
The JaxWsServiceConfiguration isn't enough. We still need the
defaultServiceConfiguration in there. Can you try something like:
list
bean
OK, now it compiles, but now I get the following warning:
server:
[java] Jul 30, 2007 9:32:53 AM
org.springframework.beans.factory.xml.DefaultNamespaceHandlerResolver
initHandlerMappings
[java] WARNING: Ignoring namespace handler
Hi Brad,
Any chance you could at least attach your complete spring configuration? I
think the config you outlined should work, but I would like to see more. Of
course a test case would be welcome too :-)
- Dan
On 7/27/07, Brad Harper [EMAIL PROTECTED] wrote:
The snapshot and adding
What format do you need for a test case?
I have several spring files, but most are irrelevant - here's the other
essentials:
?xml version=1.0 encoding=UTF-8?
!DOCTYPE beans PUBLIC -//SPRING//DTD BEAN//EN
http://www.springframework.org/dtd/spring-beans.dtd;
beans
bean id=dataSource
Oops, wrong Dan. Dan D fixed a problem where two methods were returning
two different java types that amounted to a list of the same thing.
-Original Message-
From: Daniel Kulp [mailto:[EMAIL PROTECTED]
Sent: Monday, July 30, 2007 3:15 PM
To: cxf-user@incubator.apache.org
Cc: Benson
Hi,
I'm in the exact same situation. Do you mind sharing your solution? I'm
also using AOP and Spring in the same manner.
Thanks,
Zarar
Michael Lake-5 wrote:
Brad -
I'm also using spring aop for transactions and method interceptors on my
endpoint interface.
instead of using the
OK Brad sent me a config sample offline, but I wanted to respond here so it
would be properly archived. In essence, when you have a config like this:
jaxws:endpoint
id=testService
address=/testService
jaxws:implementor
ref bean=myTestService /
Hi,
I¹ve got a service that I¹m trying to implement and am having an issue.
Actually, I¹m converting from Axis (1.x), and I¹m using code first
development. In Axis I had a service interface defined from which I would
generate WSDL, and then from the WSDL generate client stubs. Luckily, this
Modify the cxf-servlet.xml as the following
jaxws:endpoint
id=hello_world_xml
implementor=demo.hw.server.GreeterImpl
address=/xml
bindingUri=http://cxf.apache.org/bindings/xformat;
/jaxws:endpoint
jaxws:endpoint
id=hello_world_soap
Dan,
A java.lang.reflect.Proxy can only be constructed from interfaces, and
those interfaces are available via reflection. As noted in the JavaDoc:
Since a proxy class implements all of the interfaces specified at its
creation, invoking getInterfaces on its Class object will return an array
Hi all,
I'm getting a marshalling error for when using java.util.Map.
It is works fine for java.util.Collection and I didn't even have to add a
JAXB annotation to return the type for Collection.
I am using Spring2.0.4 libs as per your examples.
I am using cxf Version
James,
Ok, it seems to be doing almost what I need. I still get the warnings
during java2wsdl because java2wsdl is looking for the wrapper bean classes
but they don't exist yet! _It_ is the tool that creates them. Anyway, if I
allow it to create them (after all of the warnings) and compile
Brett,
Yes, There are two ways
Put the customization section into your schema in the wsdl,
xsd:annotation
xsd:appinfo
jxb:globalBindings collectionType=indexed/
/xsd:appinfo
/xsd:annotation
or change it to an external style, and feed the 'binding file' to the
wsdl2java -b
19 matches
Mail list logo
