I would love to do things that way. Here lies my problem. I have a stateful service. The service needs to keep a TCP connection open to an external resource. Everytime I get a connection from the pool, it must be exactly the same one I used before for this session. I tried to play around with the BySubject and ByApplication settings but found it easier to just open a connection at the beginning and close it on remove.
If there are better ways to do this I am all ears.
thanks for the help.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4055284#4055284
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4055284
I'm trying to consume a .NET web service from an EJB3 Stateless session bean (using JBoss 5 beta 2). I used wsconsume to generate all the client classes; it seemed to work without any problems. However, when I deploy my app (as an ear) and try to call the bean which invokes the web service (using the generated classes), I get the following warning (multiple times):
anonymous wrote :
| [WSDLDefinitions] Multiple WSDL bindings referrence the same interface: {http://com/werner/multimiler/web}PCMilerSoap
|
Has anyone encountered this before? How can I fix the issue?
Any help would be very much appreciated.
Thanks,
Tim
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4055278#4055278
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4055278