Title: RE: [jBoss-User] xml descriptor and resource bindings


> -----Message d'origine-----
> De : Stuart Barlow [mailto:[EMAIL PROTECTED]]
> Envoy� : mardi 22 ao�t 2000 15:53
> � : jBoss
> Objet : Re: [jBoss-User] xml descriptor and resource bindings
>
>
>
> Yup we go there in the end. jBoss was working fine all the while.
> :-)
Do you plan to doc this kind of integration in a JBoss user guide ?

>
> In TOPLink's JNDIConnector class you have to be careful of the
> cnstr that takes a String as this will by default build a
> CompositeName from your String. Instead there is another cnstr
> that takes a Name parameter. Here you can pass in the
> CompoundName yourself.
>
> So now we have an xa.DataSource defined using the Minerva class
> library in jBoss and TOPLink using it.
> Also TOPLink is using the jBoss TransactionManager for external
> transaction management.
>
>
> jBoss rules.
> Thanks for the help Rickard.
> Stuart Barlow.
>
> Rickard �berg wrote:
> >
> > Hm..
> >
> > Rickard �berg wrote:
> > > Stuart Barlow wrote:
> > > > So from this you can see the reason they get the InvalidName
> > > > exception is because they construct a CompositeName from
> > > > "java:comp/env/stuDB".
> > > >
> > > > Should they be constructing a CompondName?
> > >
> > > I think so, yes.
> >
> > Although the *really* portable way would be to use the string as-is.
> > I.e. ctx.lookup("java:comp/env/stuDB"), and let the
> namespace decide for
> > itself how to create Name objects.
> >
> > /Rickard
> >
> > --
> > Rickard �berg
> >
> > Email: [EMAIL PROTECTED]
> > http://www.telkel.com
> > http://www.jboss.org
> > http://www.dreambean.com
> >
> > --
> > --------------------------------------------------------------
> > To subscribe:        [EMAIL PROTECTED]
> > To unsubscribe:      [EMAIL PROTECTED]
> > Problems?:           [EMAIL PROTECTED]
>
>
> --
> --------------------------------------------------------------
> To subscribe:        [EMAIL PROTECTED]
> To unsubscribe:      [EMAIL PROTECTED]
> Problems?:           [EMAIL PROTECTED]
>

Reply via email to