[ http://jira.jboss.com/jira/browse/JBAS-804?page=history ]
Scott M Stark updated JBAS-804:
-------------------------------
type: Feature Request (was: Bug)
Description:
SourceForge Submitter: drmlipp .
EntityHandleImpl.getEJBObject maps all Exceptions to
java.rmi.ServerException. It must not do this as
ServerException has a very special meaning (see JDK API
doc).
As all exceptions are mapped to ServerExceptions, the
client cannot know if the RemoteException is temporary
(e.g. one node in a cluster failed) or permanent (e.g.
the object that is referred to in the handle does not
exist anymode). However, an EJB client must be able to
obtain this information in order to react
appropriately. E.g. the object not being found should
be mapped to a java.rmi.noSuchObjectException (this is
what we usually get when calling a method an a remote
interface that refers to an EJB that does not exist any
more).
- Michael
was:
SourceForge Submitter: drmlipp .
EntityHandleImpl.getEJBObject maps all Exceptions to
java.rmi.ServerException. It must not do this as
ServerException has a very special meaning (see JDK API
doc).
As all exceptions are mapped to ServerExceptions, the
client cannot know if the RemoteException is temporary
(e.g. one node in a cluster failed) or permanent (e.g.
the object that is referred to in the handle does not
exist anymode). However, an EJB client must be able to
obtain this information in order to react
appropriately. E.g. the object not being found should
be mapped to a java.rmi.noSuchObjectException (this is
what we usually get when calling a method an a remote
interface that refers to an EJB that does not exist any
more).
- Michael
Environment:
Priority: Minor (was: Critical)
Component: EJBs
No where in the spec is there a requirement for the type of mapping you are
asking for. Its an implementation detail as to whether the exception originated
on the server and was wrapped by a ServerException.
> ServerException thrown too often
> --------------------------------
>
> Key: JBAS-804
> URL: http://jira.jboss.com/jira/browse/JBAS-804
> Project: JBoss Application Server
> Type: Feature Request
> Components: EJBs
> Versions: JBossAS-3.2.6 Final
> Reporter: SourceForge User
> Assignee: Scott M Stark
> Priority: Minor
>
>
> SourceForge Submitter: drmlipp .
> EntityHandleImpl.getEJBObject maps all Exceptions to
> java.rmi.ServerException. It must not do this as
> ServerException has a very special meaning (see JDK API
> doc).
> As all exceptions are mapped to ServerExceptions, the
> client cannot know if the RemoteException is temporary
> (e.g. one node in a cluster failed) or permanent (e.g.
> the object that is referred to in the handle does not
> exist anymode). However, an EJB client must be able to
> obtain this information in order to react
> appropriately. E.g. the object not being found should
> be mapped to a java.rmi.noSuchObjectException (this is
> what we usually get when calling a method an a remote
> interface that refers to an EJB that does not exist any
> more).
> - Michael
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
JBoss-Development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-development
