Hello,

I have fixed my problem by adding the necessary section to
mbeans-descriptors.xml for the DataSourceRealm. I basically coppied the
section for JDBC Realm and changed the values. Zipped it back into
catalina.jar where I got it from.

Surely if this is not fixed in Tocmat 4.1.31 it should be considered as a
fix necessary for 4.1.32 (when does the 4.1.x line end?).

For those who want to use this I have included the XML I used, remember this
has *not* been tested other than to watch it boot and note that there were
no errors and then run both the Admin Tool and use the DataSource.

STOP! Just used the DataSource and cannot login, I have thrown a couple of
hours at it and will have to revert to the old realm :-(

Unfortunately upgrading to version 5.0.28 is not an option for me.

Andoni.

  <mbean         name="DataSourceRealm"
            className="org.apache.catalina.mbeans.ClassNameMBean"
          description="Implementation of Realm that works with any JDBC
                        supported database and JNDI"
               domain="Catalina"
                group="Realm"
                 type="org.apache.catalina.realm.DataSourceRealm">

    <attribute   name="className"
          description="Fully qualified class name of the managed object"
                 type="java.lang.String"
            writeable="false"/>

    <attribute   name="debug"
          description="The debugging detail level for this component"
                 type="int"/>

    <attribute   name="dataSourceName"
          description="The JNDI Description of the connection to use."
                 type="java.lang.String"/>

    <attribute   name="roleNameCol"
          description="The column in the user role table that names a role"
                 type="java.lang.String"/>

    <attribute   name="userCredCol"
          description="The column in the user table that holds the user's
                        credentials"
                 type="java.lang.String"/>

    <attribute   name="userNameCol"
          description="The column in the user table that holds the user's
                        username"
                 type="java.lang.String"/>

    <attribute   name="userRoleTable"
          description="The table that holds the relation between user's and
                        roles"
                 type="java.lang.String"/>

    <attribute   name="userTable"
          description="The table that holds user data"
                 type="java.lang.String"/>

  </mbean>



----- Original Message ----- 
From: "Shapira, Yoav" <[EMAIL PROTECTED]>
To: "Tomcat Users List" <[EMAIL PROTECTED]>
Sent: Wednesday, October 13, 2004 1:52 PM
Subject: RE: DataSourceRealm vs. Administration Tool - A bug?


>
> Hi,
> If you get few responses to this question, I suggest trying 5.0.28 to
> see if the problem is still around in that version.
>
> Yoav Shapira http://www.yoavshapira.com
>
>
> >-----Original Message-----
> >From: Andoni [mailto:[EMAIL PROTECTED]
> >Sent: Wednesday, October 13, 2004 8:30 AM
> >To: Tomcat Users List
> >Subject: DataSourceRealm vs. Administration Tool - A bug?
> >
> >Hello,
> >
> >I have just installed Tomcat 4.1.24 and I have it nearly exactly the
> way I
> >want it now. I am doing my testing on Windows 2000 and Tomcat 4.1.27.
> >
> >The only other thing I want to implement is the DataSourceRealm. Here I
> am
> >having problems though as I have the Administration Tool set up and
> >therefore had to have the JMX MBeans listeners in server.xml enabled.
> These
> >would seem to conflict with the DataSourceRealm though as when I have
> both
> >in place I get the error:
> >
> >java.lang.Exception: ManagedBean is not found with DataSourceRealm
> >
> >When I remove either one the other works fine so I know the conflict is
> >here.
> >
> >Is this just something I have to live with? I read the release notes
> for
> >4.1.31 and they seem to suggest that this is not something that has
> been
> >fixed in a later release. Has it?
> >
> >My thanks as ever,
> >
> >Andoni
>
>
>
> This e-mail, including any attachments, is a confidential business
communication, and may contain information that is confidential, proprietary
and/or privileged.  This e-mail is intended only for the individual(s) to
whom it is addressed, and may not be saved, copied, printed, disclosed or
used by anyone else.  If you are not the(an) intended recipient, please
immediately delete this e-mail from your computer system and notify the
sender.  Thank you.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to