Hi Scott

I found these during my code read through and investigation of current 
jboss.xml elements.

mdb-user, mdb-passwd and mdb-client-id and mdb-subscriptin-id are all 
loaded in MessageDrivenMetaData.

JMSContainerInvoker uses getUser() getClientID() etc to access them.

I've included these elements in the jboss_3_0.dtd i'm working on but 
haven't comitted to CVS yet.

Mike

At 16:20 31/01/2002, Scott M Stark wrote:

>I don't see any of the mdb-xxx fields you are talking about in the current
>code so these are all elements you added? I'm looking at version 1.42
>of the JMSContainerInvoker.java.
>
>What is needed is the names of the JMS properties from which the
>principal and credentials are obtained. The princpal name and
>credential value are not specified in the jboss.xml descriptor. Roles
>are also not defined in jboss.xml as they are a by-product of authenticating
>the obtained principal and credentials.
>
>----- Original Message -----
>From: "Dave Smith" <[EMAIL PROTECTED]>
>To: "Scott M Stark" <[EMAIL PROTECTED]>
>Cc: <[EMAIL PROTECTED]>
>Sent: Thursday, January 31, 2002 1:33 PM
>Subject: Re: [JBoss-dev] JAAS with MDB
>
>
> > Ok. I have a hacked up version of JMSContainerInvoker working. Now
> > currently we have mdb-user,mdb-password and mdb-subscription-id in the
> > jboss.xml. These are used for durable subscriptions and are referenced
> > in jbossmq-state.xml. Now should we add mdb-role and re-use this fields
> > or should we add new elements say mdb-principal mdb-credentials and
> > mdb-role?
> >
>
>
>
>_______________________________________________
>Jboss-development mailing list
>[EMAIL PROTECTED]
>https://lists.sourceforge.net/lists/listinfo/jboss-development


_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to