Hi Sergey,

Thank you so much for your time. To answer your questions:

> 1. With JAX-RS involved, generated WSDL for a soap service is wrong

With JAX-RS alone, the WSDL for the SOAP service is wrong. I ended up mixing the annotations of JAX-RS and JAX-WS as previously posted in this thread.

Also, are there plans for auto-generation of WADL or WSDL2 for java-first ReST services?

> 2. Unmarshalling problem : does it happen as part of JAX-RS invocation ?
> If yes, what sort of problem it is ? do you get Account as null ?

It happens in the method invocation. I follow the directions stated in the user guide, but the method keeps reporting (via logs) that the object it received is null.

> 3. Service listings : do you still see the soap service listed ?

They share one servlet, so I assume there is only one list which would include both ReST and SOAP services. Am I wrong in this? It keeps on saying NPE somewhere in the Endpoint class. This has been reported here too:

http://www.nabble.com/Created%3A-%28CXF-1695%29-Service-listings-for-JAX-RS-endpoints-tt18363145.html#a18363145

Again, my thanks.

Sergey Beryozkin wrote:
Hi,

So, to summarize, currently you're seeing 2 problems :

1. With JAX-RS involved, generated WSDL for a soap service is wrong

2. Unmarshalling problem : does it happen as part of JAX-RS invocation ?
If yes, what sort of problem it is ? do you get Account as null ?

3. Service listings : do you still see the soap service listed ?

Cheers, Sergey


Hi all,

I tried mixing the annotations. as follows:

@Path("/")
@WebService(serviceName="AccountService")
public class AccountService {
   @PUT
   @Path("/Account")
   @WebMethod
   public long insert(
           @WebParam(name="account")
           Account account
           ) {
       logger.info("insert Received: " + account);
       return 0;
   }
}

@XmlRootElement(name="Account")
@XmlType(name="Account")
@XmlAccessorType(XmlAccessType.PROPERTY)
public class Account {
//properties goes here...
}

Things are working, though again, the service list is messed up. Down to the last stretch. As I have posted in http://www.nabble.com/-REST--HTTP-BINDING-Service-does-not-receive-Post-parameter-tt19986914.html#a19991022

There seems to be a problem with unmarshalling the object. I could be missing something with the xml so I am posting it here as well:

<Account xmlns="http://account.subscriber.ws.solegy.com/";>
<accountID>someVal</accountID>
<!-- other properties here-->
</Account>

I don't have a wsdl to verify things so I am pretty much lost. I have tried it as 'account' or wrapped with 'insert' tag to no avail. Would appreciate some help.

Thanks in advance.
------------------------------------------------------------------------


No virus found in this incoming message.
Checked by AVG - http://www.avg.com Version: 8.0.173 / Virus Database: 270.8.1/1727 - Release Date: 10/15/2008 8:02 PM

Reply via email to