geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jarek Gawor (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (GERONIMO-6435) Invalid method interface: MessageEndpoint
Date Fri, 22 Feb 2013 02:50:12 GMT

     [ https://issues.apache.org/jira/browse/GERONIMO-6435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jarek Gawor resolved GERONIMO-6435.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 3.0.1
         Assignee: Jarek Gawor

I updated the Geronimo server code (j2ee-server module specifically) to set the additional
EJB 3.1 method interfaces (Timer and MessageEndpoint) via JACC API extensibility mechanism.
Changes committed in revision 1448884.

                
> Invalid method interface: MessageEndpoint   
> --------------------------------------------
>
>                 Key: GERONIMO-6435
>                 URL: https://issues.apache.org/jira/browse/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
>            Assignee: Jarek Gawor
>            Priority: Minor
>              Labels: newbie
>             Fix For: 3.0.1
>
>
> 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                                                                
> javax.security.jacc.EJBMethodPermission$MethodSpec.checkMethodInterface( 
> EJBMethodPermission.java:303)                                            
> at                                                                   
> javax.security.jacc.EJBMethodPermission$MethodSpec.<init>(EJBMethodPermi 
> ssion.java:183) 
> ....
> ----------------------            
> 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. 
> http://download.oracle.com/otndocs/jcp/ejb-3.1-mrel-full-oth-JSpec/
> I have looked at apache geronimo download page but no luck finding the interface in the
latest downloads.
> --- details on what I looked for --
> http://geronimo.apache.org/downloads.html                               
>                                                                         
> ..and clicked on the latest release available                           
> "Apache Geronimo v3.0.0 - Released July 13, 2012"                       
>   (http://geronimo.apache.org/apache-geronimo-v300-release.html)        
> ..and downloaded "Certified Java EE 6 Full Profile Releases"            
> ...and looked into following class                          
> geronimo-tomcat7-javaee6-3.0.0\repository\org\apache\                   
> geronimo\specs\geronimo-jacc_1.4_spec\1.0\javax\security\               
> jacc\EJBMethodPermission.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: http://www.atlassian.com/software/jira

Mime
View raw message