Arquillian
  1. Arquillian
  2. ARQ-1346

cannot run ejb 3.x integrate test using arquillian-glassfish-managed-3.1

    Details

    • Type: Bug Bug
    • Status: Open Open (View Workflow)
    • Priority: Critical Critical
    • Resolution: Unresolved
    • Affects Version/s: 1.0.0.CR1
    • Fix Version/s: None
    • Component/s: GlassFish Containers
    • Security Level: Public (Everyone can see)
    • Labels:
      None
    • Environment:
      1 Windows XP
      2 Glassfish 3.1.2.2 or current v4 snapshot
    • Estimated Difficulty:
      Medium
    • Similar Issues:
      Show 10 results 

      Description

      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.

      1. server.log
        42 kB
        Tang Yong

        Activity

        Hide
        Tang Yong
        added a comment -

        Now, the same exception also happened while using arquillian-glassfish-embedded-3.1.

        The issue is very fatal and please seeing whether being caused by arquillian glassfish container.

        I will upload a new sample with arquillian-glassfish-embedded-3.1.

        Show
        Tang Yong
        added a comment - Now, the same exception also happened while using arquillian-glassfish-embedded-3.1. The issue is very fatal and please seeing whether being caused by arquillian glassfish container. I will upload a new sample with arquillian-glassfish-embedded-3.1.
        Hide
        Aslak Knutsen
        added a comment -

        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 ??

        Show
        Aslak Knutsen
        added a comment - 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 ??
        Hide
        Andrew Rubinger
        added a comment -

        Remote interfaces are part of the EJB 2.x model, and must throw RemoteException on its business methods. This is separate from the @Remote annotation, which really defines a EJB 3.x "Remote Business" interface (confusing, I know). EJB 3.x remote business views do not throw RemoteException.

        Show
        Andrew Rubinger
        added a comment - Remote interfaces are part of the EJB 2.x model, and must throw RemoteException on its business methods. This is separate from the @Remote annotation, which really defines a EJB 3.x "Remote Business" interface (confusing, I know). EJB 3.x remote business views do not throw RemoteException.

          People

          • Assignee:
            Unassigned
            Reporter:
            Tang Yong
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated: