geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hiroko Takamiya (JIRA)" <>
Subject [jira] [Created] (GERONIMO-6435) Invalid method interface: MessageEndpoint
Date Thu, 07 Feb 2013 15:33:12 GMT
Hiroko Takamiya created GERONIMO-6435:

             Summary: Invalid method interface: MessageEndpoint   
                 Key: GERONIMO-6435
             Project: Geronimo
          Issue Type: Bug
      Security Level: public (Regular issues)
          Components: javaee6
    Affects Versions: 3.0-beta-1
         Environment: EJB
            Reporter: Hiroko Takamiya
            Priority: Minor

Our customer is getting following error ("Invalid method interface: MessageEndpoint") when
running their EJB 3.1 beans. 

--Error message---------
[12/18/12 15:13:08:638 CET] 00000030 SecurityColla 3   Authorization     
failed accessing EJB    java.lang.IllegalArgumentException:     
Invalid method interface: MessageEndpoint                              
at                                                       $MethodSpec.checkMethodInterface(                                            
at                                                          $MethodSpec.<init>(EJBMethodPermi 

Fortunately, interface list is extensible by adding property org.apache.
security.jacc.EJBMethodPermission.methodInterfaces to JVM. And this
solution works, although it is quite dirty.                        

Looking at EJB 3.1 spec below, "MessageEndpoint" is newly added interface.

I have looked at apache geronimo download page but no luck finding the interface in the latest

--- details on what I looked for --                               
..and clicked on the latest release available                           
"Apache Geronimo v3.0.0 - Released July 13, 2012"                       
..and downloaded "Certified Java EE 6 Full Profile Releases"            
...and looked into following class                          

Please kindly look at adding this one interface to the file. 

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:

View raw message