You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tomee.apache.org by "David Blevins (JIRA)" <ji...@apache.org> on 2007/03/10 07:26:10 UTC

[jira] Created: (OPENEJB-536) Validate: AroundInvoke signature

Validate: AroundInvoke signature
--------------------------------

                 Key: OPENEJB-536
                 URL: https://issues.apache.org/jira/browse/OPENEJB-536
             Project: OpenEJB
          Issue Type: Sub-task
            Reporter: David Blevins




-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (OPENEJB-536) Validation: AroundInvoke signature

Posted by "David Blevins (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/OPENEJB-536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Blevins updated OPENEJB-536:
----------------------------------

    Summary: Validation: AroundInvoke signature  (was: Validate: AroundInvoke signature)

> Validation: AroundInvoke signature
> ----------------------------------
>
>                 Key: OPENEJB-536
>                 URL: https://issues.apache.org/jira/browse/OPENEJB-536
>             Project: OpenEJB
>          Issue Type: Sub-task
>          Components: ejb3 simplified
>            Reporter: David Blevins
>            Priority: Critical
>             Fix For: 3.0
>
>
> Object <METHOD>(InvocationContext) throws Exception
> It MUST have the return value object.  I can say from experience if this is not there you'll get some pretty strange null pointers from the JVM proxy.
> It also MUST have 'throws Exception' if it doesn't the app will not be able to throw any checked exceptions -- they will all count as system exceptions.
> And of course it MUST have InvocationContext.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (OPENEJB-536) Validate: AroundInvoke signature

Posted by "David Blevins (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/OPENEJB-536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Blevins updated OPENEJB-536:
----------------------------------

      Component/s: ejb3 simplified
    Fix Version/s: 3.0
         Priority: Critical  (was: Major)
      Description: 
Object <METHOD>(InvocationContext) throws Exception

It MUST have the return value object.  I can say from experience if this is not there you'll get some pretty strange null pointers from the JVM proxy.
It also MUST have 'throws Exception' if it doesn't the app will not be able to throw any checked exceptions -- they will all count as system exceptions.
And of course it MUST have InvocationContext.


> Validate: AroundInvoke signature
> --------------------------------
>
>                 Key: OPENEJB-536
>                 URL: https://issues.apache.org/jira/browse/OPENEJB-536
>             Project: OpenEJB
>          Issue Type: Sub-task
>          Components: ejb3 simplified
>            Reporter: David Blevins
>            Priority: Critical
>             Fix For: 3.0
>
>
> Object <METHOD>(InvocationContext) throws Exception
> It MUST have the return value object.  I can say from experience if this is not there you'll get some pretty strange null pointers from the JVM proxy.
> It also MUST have 'throws Exception' if it doesn't the app will not be able to throw any checked exceptions -- they will all count as system exceptions.
> And of course it MUST have InvocationContext.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.