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

[Emmanuel Bernard (JIRA)]

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

Emmanuel Bernard commented on EJB-402:
--------------------------------------

galder

The problem is that Ejb3ConfigurationObjectFactory currently uses ObjectInputStream to read the Ejb3Configuration from JNDI. If the deployment is isolated, reading this configuration fails because it tries to resolve classes that are isolated.

I don't know, you created Ejb3ConfigurationObjectFactory in the 1st place so you should know why you did that:

9/6/06 "EJB-160 make Ejb3Configuration and AnnotationConfiguration serializable and allow JNDI reference"

I don't know SessionFactoryObjectFactory enough to be able to say whether the configuration could be retrieved in the same way or not but SessionFactoryObjectFactory looks more recent and does not require the use of an OIS or MVIS so that's probably a better way of getting the required configuration object from JNDI rather than introducing a dependency on AS.



> 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