The following comment has been added to this issue:

     Author: James Carman
    Created: Thu, 2 Sep 2004 10:13 AM
       Body:
>From the EJB 2.1 specification...

"The enterprise bean must not attempt to create a class loader; obtain the 
current class loader; set the context class loader; set security manager; 
create a new security manager; stop the JVM; or change the input, output, and 
error streams."

I didn't see anything in the Servlet 2.4 spec that raised any eyebrows, but 
someone else might want to give it a look-see. 
---------------------------------------------------------------------
View this comment:
  http://issues.apache.org/jira/browse/HIVEMIND-49?page=comments#action_39526

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/HIVEMIND-49

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HIVEMIND-49
    Summary: RegistryShutdownListener not found
       Type: Bug

     Status: Open
   Priority: Blocker

    Project: HiveMind
 Components: 
             framework
   Versions:
             1.0

   Assignee: Howard M. Lewis Ship
   Reporter: Naresh Sikha

    Created: Wed, 1 Sep 2004 11:55 AM
    Updated: Thu, 2 Sep 2004 10:13 AM
Environment: Tomcat 5.0.28, Windows XP, J2SDK1.4.2

Description:
My environement fails to start up as RegistryShutdownListener cannot be found.

This may be off base since I haven't fully grasped the architecture of 
o.a.h.service.impl.ClassFactoryClassLoader, but I think this is because 
o.a.h.service.impl.ClassFactoryClassLoader doesn't allow visibility into the 
current thread context class loader (it doesn't get constructed with a parent).

So whenever ClassFab created classes attempt to resolve classes their 
dependencies fail to get found.

I'm attaching a test case .war file runnable in Tomcat 5.0 that fails at the 
url /HiveMindWeb/test. The source code is WEB-INF/classes/test/TestServlet.java

I'm also attaching the log file with the error.

My local Ant build of Hivemind succeeded without error so I belive this to be 
an integration bug.

Thanks.


---------------------------------------------------------------------
JIRA INFORMATION:
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

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


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

Reply via email to