Thanks, James. Yes, I'm using the -classdir to compile the generated
wrapper classes. I look forward to the new "java2ws" tool.
-Brett
On 7/31/07 1:17 AM, "James Mao" <[EMAIL PROTECTED]> wrote:
> Brett,
>>It also seems like I have to run java2wsdl twice, or I end up with BARE
>> type para
Brett,
It also seems like I have to run java2wsdl twice, or I end up with BARE
type parameters. The first time seems required to generate the wrapper
classes, and once they're compiled, the second time is required to generate
the WSDL. Is this correct behavior?
In wrapper style, java2wsdl
James,
It also seems like I have to run java2wsdl twice, or I end up with BARE
type parameters. The first time seems required to generate the wrapper
classes, and once they're compiled, the second time is required to generate
the WSDL. Is this correct behavior?
The first run of java2wsdl alwa
Brett,
Yes, There are two ways
Put the customization section into your schema in the wsdl,
or change it to an external style, and feed the 'binding file' to the
> wsdl2java -b $YOUR_BINDNIG_FILE
Let me know if it works for you
Cheers,
James
James,
Ok, it seems to be do
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 them
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 cxf-2.0.1-incubator-SNAPSHO
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
s
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
con
Modify the cxf-servlet.xml as the following
http://cxf.apache.org/bindings/xformat";>
http://apache.org/cxf/binding/http";>
Your impl should look like this
package demo.hw.server;
@javax.jws.WebService
public class GreeterImpl {
public String greetMe(String me) {
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
seem
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:
And you combine it with the transaction/AOP stuff from spring, Spring will
repla
OK, I see now that the trick to getting what I want to work involves
using the xformat:binding element in my wsdl:bindings.
Does this mean that I can't support both POX and SOAP using the same
@WebService impl?
Yes, you have to specify the @WebService and also @BindingType determine
the b
Yeap...that did itthankshave to remember to clean before
install.
On Jul 30, 2007, at 9:39 PM, Willem Jiang wrote:
Hi Mansour ,
I just built a kit with latest trunk code on windows box. I can't
reproduce your error.
If you build the kit from the trunk, please do the fellow things:
Well, in any case, I can confirm that in wrapped doc/lit, a return of
List doesn't work. I'm testing a fix now.
Dan
On Monday 30 July 2007 15:16, Benson Margulies wrote:
> Oops, wrong Dan. Dan D fixed a problem where two methods were
> returning two different java types that amounted to a li
Was just playing around with the hello_world_xml_bare, the
functionality is about what I want. But I'd like to be able to run it
in the servlet container, not using that Endpoint.publish stuff.
The xml binding do work in the servlet, in the demo, just do this in
case of tomcat on windows
Hi Mansour ,
I just built a kit with latest trunk code on windows box. I can't
reproduce your error.
If you build the kit from the trunk, please do the fellow things:
1. cd ${CXF}/trunk
2. svn up
3. mvn clean install
4. cd distribution
5. mvn clean install
Cheers,
Willem.
Mansour Raad wrote:
Thanks Julio. It worked and has eliminated the setter method from the WSDL
after adding this annotation. However, I see extra type (stringArray) in
WSDL schema section is getting added up automatically which is not present
in my service:
http://www.w3.org/2001/XMLSchema";
xmlns="http://jaxb.dev
Hi -
This problem is fix in the latest SNAPSHOT, I you don't want to
update yet add @WebMethod(exclude = true) annotation to any method in
your Impl that you don't want to expose in your WSDL.
On Jul 30, 2007, at 3:45 PM, gdprao wrote:
I have developed a service in CXF and my service imp
I answered my own question, and this might help someone else ...
Could some kind soul tell me how to modify this to use Aegis instead of
jaxb?
Also, has anyone got a recipe to get Eclipse and Spring to look at the
CXF included bean definitions?
Currently, I don't think there is a solution. The cxf dev team is looking
into the issue.
-bh
On 7/30/07, Zarar Siddiqi <[EMAIL PROTECTED]> wrote:
>
>
> 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,
>
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
I have developed a service in CXF and my service implementation class which
defines a setter injection method for Delegate which actually performs the
business logic.
After deploying the service, in the WSDL generated by CXF I see the schema
with elements for setServiceDelegate and
setServiceDele
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: Ben
Hmm List of Arrays. I'm sure I haven't tested that one.
Interesing. Definitely likely to be not working. :-(
Dan
On Monday 30 July 2007 14:58, Benson Margulies wrote:
> I think that this is occurring in the same thing I reported involving
> the array conflict. The use of the 'any'
I think that this is occurring in the same thing I reported involving
the array conflict. The use of the 'any' type is resulting in chaos, of
course.
WSDL shows:
From:
@WebMethod
public abstract List lookupBatch(String
indexid,
@WebParam(targetNamespace="urn:com.basistech.rnm.index"
)NameInd
What format do you need for a test case?
I have several spring files, but most are irrelevant - here's the other
essentials:
http://www.springframework.org/dtd/spring-beans.dtd";>
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 @Respon
OK, I see now that the trick to getting what I want to work involves
using the xformat:binding element in my wsdl:bindings.
Does this mean that I can't support both POX and SOAP using the same
@WebService impl?
On 7/30/07, Ray Krueger <[EMAIL PROTECTED]> wrote:
> Was just playing around with the
Was just playing around with the hello_world_xml_bare, the
functionality is about what I want. But I'd like to be able to run it
in the servlet container, not using that Endpoint.publish stuff.
I have a working jaxws endpoint, I would like CXF to handle an
incoming xml POST, unmarshall the payload
I've done some more digging on this and found that the shutdown method of
org.apache.cxf.transport.http_jetty.JettyHTTPServerEngine class does not appear
to ever be called. This means that the destroyForPort method is never called
which leaves Jetty's bounded thread pool running, selecting on th
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
[org.apache.cxf.transport.http_jetty.spring.Name
wsdl2java tools only support the jax-ws frontend, it does not support
the RESTful service, at moment, but we're working on it.
We have a XML binding in cxf, you can check out the samples
hello_world_xml_bare and hello_world_xml_wrapped,
Don't know if it's what you're looking for?
James
I'm
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:
>
>
>
>
>
>
>
> (if for some reason that
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 ma
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
Hello all,
I was previously using XFire and I am moving my application over to CXF. Right
now I am just prototyping some application features and I needed a quick
solution for remote administration. The simple frontend/embedded Jetty solution
was working really well for me with XFire, but I am
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 ap
Yes, I am specifying the following parameters as annotations on my
implementation:
name, serviceName, portName, targetNamespace, wsdlLocation, and
endpointInterface.
If no one sees anything immediately wrong with it, I can dig into the CXF code
to see what's going on-- I just thought I'd ask i
Thanks for the report. Fixed.
Cheers,
Jervis
-Original Message-
From: Mansour Raad [mailto:[EMAIL PROTECTED]
Sent: 2007?7?30? 18:24
To: cxf-user@incubator.apache.org
Subject: http rest sample does not compile
svn up the latest.
cd [install]/samples/restful_http_binding
ant server
I get
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 30
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 perfectl
Coming to think of this again, I found supporting Provider 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 were just being
svn up the latest.
cd [install]/samples/restful_http_binding
ant server
I get the following:
Buildfile: build.xml
maybe.generate.code:
compile:
[mkdir] Created dir: /Users/mansour/apache-cxf-2.1-incubator-
SNAPSHOT/samples/restful_http_binding/build/classes
[mkdir] Created dir: /Users/
Hi Michal,
The short answer is we do not support Provider right now in CXF,
I will discuss into details why we can not support Provider with
standard JAX-WS APIs in a following email. You mentioned CORBA binding is
working for you with the SEI style(client and server generated by wsdltojava),
oh, yeah! That´s the problem!.
I thought that the client can send a message to the detination queue, and
the message stay there forever (until another process read it).
Thank you for re-write the demo.
Juanjo.
On 7/30/07, Willem Jiang <[EMAIL PROTECTED]> wrote:
>
> Hi Juan,
>
> I just wrote a d
Thanks guys for your helpful replies. Isn't there any way how to solve my
problem using Interceptor? I'll try ServerFactoryBean as you mentioned.
Thanks
> Michal,
> Right now, we don't support any Provider (or Dispatch) that takes the raw
> CXF Message types. That's a good suggestion though.
Hi Ade,
Fixed the problem [1], you need the latest code, or wait until we
publish the 2.0.1
Let me, if there's any other problems, in jms case,
What you need is specify the transport as jms,
and you don't need to specify any other jms argument now, the default is
in 'queue' style.
Cheers,
J
Hi Juan,
I just wrote a demo with your scenario, both start server and client
with spring configure files. It works in my trunk.
So back to your question. You said
"It seems the communication between client and endpoint is ok over JMS,
but no messages in the queue. What is wrong?."
I guesse
49 matches
Mail list logo
