I am using spring 1.2.8 with IBM websphere 6.0.2.11.
Up until now we were using a normal client, and the spring was helping us locating the ejb using a jnditemplate as follows:
this worked well using our localhost sever (test enviroment), and a "real" server on a remote computer.Code:<bean id="jndiTemplate" class="org.springframework.jndi.JndiTemplate"> <property name="environment"> <props> <prop key="java.naming.factory.initial"> com.ibm.websphere.naming.WsnInitialContextFactory </prop> <prop key="java.naming.provider.url"> iiop://ourhostname:2809 </prop> --> </props> </property> </bean> <bean id="ourEJB" class="org.springframework.ejb.access.SimpleRemoteStatelessSessionProxyFactoryBean"> <property name="jndiName" value="ejb/OurEJB" /> <property name="businessInterface" value="com.OurInterface" /> <property name="jndiTemplate" ref="jndiTemplate" /> </bean>
We are not trying to change into a WSA Application Client, because we were told that it will do better in working with a cluster. We've tried adding the -CCproviderURL="corbaloc:iiop:firsthost:2809,:secon dhost:2809" to the launchclient.bat command, but we are not sure how to tell spring to use these urls inside the jndiTemplate.
We've tried just commenting the previous (older) url, and also just removing the template all together, but nothing seems to work, and we can't locate the ejb using spring, like we used to.
Is there some way to just put both urls inside the jndi-template (and optinally, stop using the Application Client project type)? And if not, how can we tell spring to look for the initial context using the two urls we provide at the lunchclient.bat command line?
Thanks for the help


Reply With Quote