Using a J2EE webservices client to talk to .NET would work like this: 1. You create a J2EE application client deployment ( this is deployed on the server).
2. You create a standalone client. This is a normal java program which is the true client. 3. On startup, the standalon client app then does a jndi lookup to retreive the meta information from the jboss instance. (This meta information is contained in the J2EE application client deployment) 4. The standalone client will then install handlers that are specified in the meta information. 5. The standalone client issues a webservice request to the .NET service. Currently the standalone client and the jboss instance containing the J2EE application client must be on the same system, but we are planning on removing this restriction. -Jason View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3884036#3884036 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3884036 ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
