[hibernate-issues] [Hibernate-JIRA] Commented: (EJB-402) Ejb3ConfigurationObjectFactory needs to use MarshalledValueInputStream

Galder Zamarreno (JIRA) noreply at atlassian.com
Thu Jan 8 03:54:39 EST 2009


    [ http://opensource.atlassian.com/projects/hibernate/browse/EJB-402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=32083#action_32083 ] 

Galder Zamarreno commented on EJB-402:
--------------------------------------

Yeah, a CNFE is raised when reading the configuration because the Entities that are reading
are deployed in an isolated deployment and when reading the configuration, the right 
classloader, the one associated with the thread is not set (MarshalledValueInputStream does this), 
hence it's not found.

I'm not sure whether you can easily find a solution that lives in HB and that works for all app 
servers. I know what works for JBoss AS and that solution imo, should live in the integration/ 
project in the same way that Arjuna put there the code that integrated Arjuna TM with AS:

http://lists.jboss.org/pipermail/jboss-development/2007-July/010319.html

One last thing, who and when are these EMF objects build? EM objects are build upon 
deployment of an archive containing a persistence unit.

> Ejb3ConfigurationObjectFactory needs to use MarshalledValueInputStream
> ----------------------------------------------------------------------
>
>                 Key: EJB-402
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-402
>             Project: Hibernate Entity Manager
>          Issue Type: Bug
>    Affects Versions: 3.2.1, 3.3.2.GA, 3.4.0.CR2
>            Reporter: Galder Zamarreno
>            Assignee: Galder Zamarreno
>             Fix For: 3.4.0.GA
>
>
> Ejb3ConfigurationObjectFactory should use MarshalledValueInputStream instead 
> of ObjectInputStream, otherwise looking up configuration from isolated deployments
> won't work correcly and you'll get ClassNotFoundExceptions.
> MarshalledValueInputStream is different from ObjectInputStream in that it uses the 
> thread context classloader to load classes rather than the system classloader.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the hibernate-issues mailing list