geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From j...@codehaus.org
Subject [jira] Closed: (GERONIMO-138) Security-related changes improving EJB deployment
Date Sat, 03 Jan 2004 01:24:44 GMT
Message:

   The following issue has been closed.

   Resolver: David Jencks
       Date: Fri, 2 Jan 2004 7:24 PM

I've applied the parts I agree with, mostly the null check on the security element.  I do
not agree that the class-space element should be optional.  For the most part I prefer the
original formatting.
---------------------------------------------------------------------
View the issue:

  http://jira.codehaus.org/secure/ViewIssue.jspa?key=GERONIMO-138


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: GERONIMO-138
    Summary: Security-related changes improving EJB deployment
       Type: Improvement

     Status: Closed
   Priority: Minor
 Resolution: FIXED

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: Apache Geronimo
 Components: 
             core

   Assignee: David Jencks
   Reporter: Jacek Laskowski

    Created: Wed, 31 Dec 2003 6:45 AM
    Updated: Fri, 2 Jan 2004 7:24 PM

Description:
Hi,

Attached are the changes required to deploy EJBs with no end user intervention. They're strictly
related to Security module. (I hope Alan will come back to work soon and apply the patch so
I don't have to change anything at Wiki :-))

The changes are:
  o add JAAC provider property
  o additional null checks consistent with geronimo-ejb-jar.xsd
  o remove requirements to add empty <security/> element to /META-INF/geronimo-ejb-jar.xml
  o organizing imports
  o formating code after the changes

Also it's necessary to apply GERONIMO-137 as LoaderUtil is very forgiving about null's.

Upon applying the patch, session beans are deploying very nicely :-)


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


Mime
View raw message