Win a copy of Re-engineering Legacy Software this week in the Refactoring forum
or Docker in Action in the Agile forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Service.getPort(Class)

 
vikas jain
Ranch Hand
Posts: 37
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
If we have more than one bindings ( document/literal and RPC/literal) for a single portType.

Then by using the method Service.getPort(Class), is it possible to get a stub that is for a particular message/mode. And if yes where we keep that mapping.

also, what is the use of <port-comonent-ref> element. Is this useful only when the J2EE web service is deployed in the same J2EE application.
 
Peer Reynders
Bartender
Posts: 2968
6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
This material is only relevant if you are accessing a web service through a dynamic proxy (RMH p338), rather than a static stub or DII.

With a dynamic proxy there is no <service-interface> inside <service-ref> (dynamic proxies implement javax.xml.rpc.Service) which would also define the endpoint interface - so <service-endpoint-interface> is defined inside <port-component-ref> for dynamic proxies. If your application accesses multiple web service endpoints then the endpoint interface is the only distinguishing feature between them - so when you use java.rmi.Remote javax.xml.rpc.Service.getPort(Class) you have to specify the interface to be implemented which in turn identifies the web service endpoint.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic