[ http://jira.jboss.com/jira/browse/JBAS-1286?page=history ]
     
Adrian Brock reopened JBAS-1286:
--------------------------------


> EJB3 .ear file and hot deploy of .war file cause java.lang.ClassCastException
> -----------------------------------------------------------------------------
>
>          Key: JBAS-1286
>          URL: http://jira.jboss.com/jira/browse/JBAS-1286
>      Project: JBoss Application Server
>         Type: Bug
>     Versions: JBossAS-4.0.1RC1
>  Environment: Linux, 2.6.9 kernel. jdk build 1.5.0-b64. JBoss 4.0.1RC1. EJB 
> Preview 2.
>     Reporter: Frank Merenda
>     Assignee: Scott M Stark
>     Priority: Minor

>
>
> If I have a EJB 3 SLSB deployed in an .ear file, and I create a separate .war 
> file (not in the ear file) to access that SLSB it works fine upon server 
> startup. If I touch the .ear file everything still works fine. If I touch the 
> .war file, I get a ClassCastException:
> java.lang.ClassCastException: $Proxy76
>         at 
> org.jboss.jbossnetwork.pushportal.business.ApplicationFacade.login(ApplicationFacade.java:23)
>         at ....
> I am referencing the SLSB from the war file with the following code:
>   InitialContext ctx = new InitialContext();
>   Login login = (Login) ctx.lookup(LoginRemote.class.getName());
> It is blowing up on the second line.
> This is repeatable 100% of the time. If I restart the app server it works 
> correctly again. If I just re-touch both the .ear and the .war I will still 
> get the CCE.
> I was not sure if this goes into the EJB3 or the JBoss AS project. There were 
> other ClassCastExceptions in the AS project, so I put it in here.
> I've attached the .war and .ear file. You can deploy them in JBoss 4.0.1RC2 
> with EJB3 set up. (update if no attachment, email me at [EMAIL PROTECTED] and 
> I will send them. I don't see an attach on the bug request). I will try to 
> add it after I file the bug.  
> Steps to repeat:
> 1) deploy war and ear files.
> 2) go to http://localhost:8080/jbosspush/login.html
> 3) type in any 4 letters for the username and password. You are sent to the 
> main page.
> 4) touch jboss-4.0.1RC1/server/all/deploy/jbosspush.war. Wait for hot deploy.
> 5) go to http://localhost:8080/jbosspush/login.html
> 6) type in any 4 letters for the username and password. You are sent to 
> placeholder error page. Trace is in the log.
> 7) restart jboss server
> 8) repeat steps 1-3. Everything works.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
JBoss-Development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to