[ http://issues.apache.org/jira/browse/GERONIMO-2560?page=comments#action_12457975 ] David Jencks commented on GERONIMO-2560: ----------------------------------------
I learned a bit more xml today about xsi:type and substitution groups, some from http://davidbau.com/archives/2003/12/18/the_design_of_xmlbeans_part_3.html basically the XmlObject.add(XmlObject) methods only deal with inheritance in the schema, not substitution groups. This explains why the gbean is being added with the element name "service" rather than "gbean". The result is a valid document. We either need to support xsi:type more or find a way to get the gbean element name in here. > Realm added using SecurityRealm portlet does not work > ----------------------------------------------------- > > Key: GERONIMO-2560 > URL: http://issues.apache.org/jira/browse/GERONIMO-2560 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: console, security > Affects Versions: 1.2, 2.0 > Reporter: Vamsavardhana Reddy > Assigned To: Vamsavardhana Reddy > Priority: Critical > Fix For: 1.2, 2.0 > > > A new security realm added using SecurityRealm portlet does not get listed in > the portlet. There are no deployment errors. Also, if an application is > configured to authenticate against this realm, login is failing since the > realm could not be found. > The deployment plan for security realms generated in the console seems to use > a "service" tag in place of "gbean" tag. If the service tag is changed to > gbean tag, the realm is getting listed in the SecurityRealm portlet. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
