On Wed, Jun 11, 2008 at 8:34 AM, ant elder <[EMAIL PROTECTED]> wrote:
> On Wed, Jun 11, 2008 at 8:29 AM, Simon Laws <[EMAIL PROTECTED]> > wrote: > > > On Wed, Jun 11, 2008 at 8:23 AM, ant elder <[EMAIL PROTECTED]> wrote: > > > > > On Wed, Jun 11, 2008 at 6:42 AM, Nishant Joshi < > [EMAIL PROTECTED]> > > > wrote: > > > > > > > Hi All, > > > > I can now run JMS client successfully with latest binding.jms, but > you > > > need > > > > to confirm following with WAS 6 before testing it.. this was done > with > > > the > > > > help of Ant... > > > > This investigation done on sample sample-helloworld-jms-webapp > > > > 1) see the link > > > > > > > > > > > > > > http://www-128.ibm.com/developerworks/forums/thread.jspa?messageID=13949798&tstart=0 > > > > 2) You need to add > > > > > > > > > > > > > > localhost:<SIB_ENDPOINT_ADDRESS>:BootstrapBasicMessaging,localhost:7276:BootstrapBasicMessaging > > > > in the property Provider endpoints of Connection Factory, You can > find > > it > > > > in > > > > the websphere admin console, under resourses - JMS click on your > > > connection > > > > factory > > > > Here <SIB_ENDPOINT_ADDRESS> is the port defined under websphere admin > > > > console and look in servers-application server, click on server1, and > > > then > > > > in the server1 panel there are two things under Communications in > ports > > > it > > > > should list SIB_ENDPOINT_ADDRESS > > > > here second entry of port 7276 is defaul to provide... > > > > 3) In this sample there is a property to set in the web.xml to say > > start > > > > when the server starts up not on the first web request this was not > > come > > > > with standard sample otherwise you need to call your service throgh > > > > hello.jsp and then you client would work woth it (jsp is come in the > > > sample > > > > sample-helloworld-jms-webapp) > > > > > > > > by using above steps i can now run my client successfully. > > > > > > > > Thanks Ant for all your help.. > > > > Please Ant correct me in this explanation. > > > > > > > > please let us know if anybody have any questions... :) > > > > > > > > -- > > > > Thanks > > > > Nishant Joshi > > > > > > > > > > That all sounds about right, the only thing I'd add is that there is > some > > > doc on the connection factory "provider endpoints" field at > > > > > > > > > http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.pmc.express.doc/sibjmsresources/SIBJMSConnectionFactory_DetailForm.html > > > > > > I've added a short section on using this WebSphere client for JMS to > the > > > binding.jms doc on the website, its very brief right now and just > refers > > to > > > this email thread, Nishant or anyone else - interested in adding more > > > detail > > > or expanding it out into a separate more detaailed how-to wiki page? > > > > > > ...ant > > > > > > ...ant > > > > > > > I'm seeing an NPE in the JMS itests on the line > > > > if > > > > > (props.get(Context.INITIAL_CONTEXT_FACTORY).equals("com.ibm.websphere.naming.WsnInitialContextFactory")) > > { > > > > Seems to be related to the changes here and could do with an "if null" > > check > > I guess. Is there a fix in hand for this or shall I make the change? > > > > Simon > > > I've just committed a fix. > > ...ant > Thanks Ant. Simon
