[arquillian-issues] [JBoss JIRA] (ARQ-1346) cannot run ejb 3.x integrate test using arquillian-glassfish-managed-3.1

[Aslak Knutsen (JIRA)]

    [ https://issues.jboss.org/browse/ARQ-1346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779027#comment-12779027 ] 

Aslak Knutsen commented on ARQ-1346:
------------------------------------

The log says:  Method 'public abstract int org.jboss.ejb3.examples.ch04.firstejb.CalculatorCommonBusiness.add(int[])' must throw at least one exception of type java.rmi.RemoteException or one of its super-classes

If CalculatorCommonBusiness is a Remote interface then the behavior sounds like a validation of the EJB spec ??
                
> cannot run ejb 3.x integrate test using arquillian-glassfish-managed-3.1
> ------------------------------------------------------------------------
>
>                 Key: ARQ-1346
>                 URL: https://issues.jboss.org/browse/ARQ-1346
>             Project: Arquillian
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: GlassFish Containers
>    Affects Versions: 1.0.0.CR1
>         Environment: 1 Windows XP
> 2 Glassfish 3.1.2.2 or current v4 snapshot
>            Reporter: Tang Yong
>            Priority: Critical
>         Attachments: javaeewithgf.zip, javaeewithgf.zip, server.log
>
>
> Today, I trigger a problem[1] about arquillian glassfish integrated test
> again on Glassfish 3.1.2.2 or current Glassfish 4.0-SNAPSHOT.
> [1]:
> http://stackoverflow.com/questions/8677780/cannot-deploy-jar-file-with-ejb-to-glassfish-3-1-1
> The attachment(javaeewithgf.zip) is my modified sample based on
> "Enterprise JavaBeans 3.1, 6th Edition " using
> arquillian-glassfish-managed-3.1.
> And the attachment(server.log) is the result of running on current
> Glassfish 4.0-SNAPSHOT.
> The issue is very critical because test scene is very simple.
> I will upload the attachments.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira