Win a copy of Design for the Mind this week in the Design forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

EJB3 WSException: Cannot obtain java type mapping

 
sthalle
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
My webservice client cannot execute a method on the server ?
Got:
client.AuctionWSClient
Starting Auction WebService Client
Creating a service Using:
http://127.0.0.1:8080/auction-auction-ejb/AuctionWebServiceBean?wsdl
and {http://webservice.auction.be/}AuctionWebServiceBeanService
Exception in thread "main" org.jboss.ws.WSException: Cannot obtain java type mapping for: {http://webservice.auction.be/}item
at org.jboss.ws.metadata.builder.jaxrpc.JAXRPCMetaDataBuilder.buildInputParameter(JAXRPCMetaDataBuilder.java:266)

(Generated)WSDL-Extract:
<definitions name="AuctionWebServiceBeanService" targetNamespace="http://webservice.auction.be/">
<types><xs:schema targetNamespace="http://webservice.auction.be/" version="1.0">
<xs:complexType name="user">
<xs:sequence>
<xs:element maxOccurs="unbounded" minOccurs="0" name="bids" nillable="true" type="tns:bid"/>
<xs:element minOccurs="0" name="email" type="xs:string"/>
<xs:element maxOccurs="unbounded" minOccurs="0" name="items" nillable="true" type="tns:item"/>
</xs:sequence>
</xs:complexType>...............
<xs:complexType name="item">
<xs:sequence>
<xs:element maxOccurs="unbounded" minOccurs="0" name="bids" nillable="true" type="tns:bid"/>
<xs:element minOccurs="0" name="description" type="xs:string"/>
<xs:element minOccurs="0" name="seller" type="tns:user"/>
</xs:sequence>
</xs:complexType>
</xs:schema>..................................

Interface AuctionWebService:
@WebService
@SOAPBinding(style = Style.RPC)
public interface AuctionWebService extends Remote {
@WebResult(name="user")User
createUser(@WebParam String email);

I have another webservice "echo" which works, but which don't use java beans as parameters or return type. The client path seems to be ok (I think). Added @WebResult and @WebParam, but this did not change anything. Deployment on JBoss gives no errors...

If anyone has an idea ?
Thanks.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic