[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-633) remoting extension in handling exceptions on client side
6:09 a.m.
remoting extension in handling exceptions on client side
--------------------------------------------------------
Key: JBSEAM-633
URL: http://jira.jboss.com/jira/browse/JBSEAM-633
Project: JBoss Seam
Issue Type: Patch
Components: Remoting
Affects Versions: 1.1.0.GA
Reporter: Nico Gau
Priority: Optional
Hi all,
I don't really know what JIRA is by the way, so hopefully nobody is upset by this
post. I first mailed Gavin but he told me I should put it in JIRA.
I currently work on a project which uses Seam Remoting directly and I didn't find a
neat way in handling errors on the client side as Exceptions are not propagated to it.
Therefore I changed Seam to transmit all exceptions which can be handled in the javascript
part via another callback. E.g.:
Seam.Component.getInstance('userManager').currentUser(function(user) {
alert("user: " + user);
},
function(ex) {
alert("exception occured: " + ex.getMessage());
});
As the exception handler is optional, the change would not brake any client code. If you
are interested in the change, you can reach me at heinzbeinz AT googlemail.com
--
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:54 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Assigned: (JBSEAM-633) remoting extension in handling exceptions on client side
[ http://jira.jboss.com/jira/browse/JBSEAM-633?page=all ]
Shane Bryzak reassigned JBSEAM-633:
-----------------------------------
Assignee: Shane Bryzak
remoting extension in handling exceptions on client side
--------------------------------------------------------
Key: JBSEAM-633
URL: http://jira.jboss.com/jira/browse/JBSEAM-633
Project: JBoss Seam
Issue Type: Patch
Components: Remoting
Affects Versions: 1.1.0.GA
Reporter: Nico Gau
Assigned To: Shane Bryzak
Priority: Optional
Hi all,
I don't really know what JIRA is by the way, so hopefully nobody is upset by this
post. I first mailed Gavin but he told me I should put it in JIRA.
I currently work on a project which uses Seam Remoting directly and I didn't find a
neat way in handling errors on the client side as Exceptions are not propagated to it.
Therefore I changed Seam to transmit all exceptions which can be handled in the javascript
part via another callback. E.g.:
Seam.Component.getInstance('userManager').currentUser(function(user) {
alert("user: " + user);
},
function(ex) {
alert("exception occured: " + ex.getMessage());
});
As the exception handler is optional, the change would not brake any client code. If you
are interested in the change, you can reach me at heinzbeinz AT googlemail.com
--
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:54 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-633) remoting extension in handling exceptions on client side
[ http://jira.jboss.com/jira/browse/JBSEAM-633?page=comments#action_12349585 ]
Shane Bryzak commented on JBSEAM-633:
-------------------------------------
I previously had plans to do something about this (see forum post
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=84894) but never got
round to it. I'll take a look at this as a matter of priority after the next
release.
remoting extension in handling exceptions on client side
--------------------------------------------------------
Key: JBSEAM-633
URL: http://jira.jboss.com/jira/browse/JBSEAM-633
Project: JBoss Seam
Issue Type: Patch
Components: Remoting
Affects Versions: 1.1.0.GA
Reporter: Nico Gau
Assigned To: Shane Bryzak
Priority: Optional
Hi all,
I don't really know what JIRA is by the way, so hopefully nobody is upset by this
post. I first mailed Gavin but he told me I should put it in JIRA.
I currently work on a project which uses Seam Remoting directly and I didn't find a
neat way in handling errors on the client side as Exceptions are not propagated to it.
Therefore I changed Seam to transmit all exceptions which can be handled in the javascript
part via another callback. E.g.:
Seam.Component.getInstance('userManager').currentUser(function(user) {
alert("user: " + user);
},
function(ex) {
alert("exception occured: " + ex.getMessage());
});
As the exception handler is optional, the change would not brake any client code. If you
are interested in the change, you can reach me at heinzbeinz AT googlemail.com
--
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:49 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-633) remoting extension in handling exceptions on client side
[ http://jira.jboss.com/jira/browse/JBSEAM-633?page=comments#action_12349588 ]
Nico Gau commented on JBSEAM-633:
---------------------------------
I already implemented that feature, also (as you stated in your forum post), I also
thought it's not useful to transmit the stack trace. So only the message part (and of
course if you overloaded the Exception class all of child class members) are transmitted.
To register exception handlers in a way you stated in the post, only the javascript part
must slightly be changed.
I first thought of way like this:
if Seam.Component.getInstance(..).$FUNC$ assigns no handler in the call then
Seam.Component.getInstance(...) is looked up, if there is a handler, if not Seam.Component
can have a default handler (this is we're someone may install a handler which notifies
that there was a unhandled exception).
I can send you the source code of the remoting part of Seam if you like to.
remoting extension in handling exceptions on client side
--------------------------------------------------------
Key: JBSEAM-633
URL: http://jira.jboss.com/jira/browse/JBSEAM-633
Project: JBoss Seam
Issue Type: Patch
Components: Remoting
Affects Versions: 1.1.0.GA
Reporter: Nico Gau
Assigned To: Shane Bryzak
Priority: Optional
Hi all,
I don't really know what JIRA is by the way, so hopefully nobody is upset by this
post. I first mailed Gavin but he told me I should put it in JIRA.
I currently work on a project which uses Seam Remoting directly and I didn't find a
neat way in handling errors on the client side as Exceptions are not propagated to it.
Therefore I changed Seam to transmit all exceptions which can be handled in the javascript
part via another callback. E.g.:
Seam.Component.getInstance('userManager').currentUser(function(user) {
alert("user: " + user);
},
function(ex) {
alert("exception occured: " + ex.getMessage());
});
As the exception handler is optional, the change would not brake any client code. If you
are interested in the change, you can reach me at heinzbeinz AT googlemail.com
--
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:39 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-633) remoting extension in handling exceptions on client side
[ http://jira.jboss.com/jira/browse/JBSEAM-633?page=comments#action_12350601 ]
Simon Tian commented on JBSEAM-633:
-----------------------------------
Upon Shane's suggestion at
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=98782, I'd like to
detail the remoting exception handling requests:
1. If it is session timed out, there always miss components or values and thus causing
exception during remote call, in this case it'd be better to redirect to a login page
or a similar page so that a new session will start.
2. If it is a real runtime exception, say connetion broken, it'd better to redirect to
another page so that the user can notify the administrator to do something.
remoting extension in handling exceptions on client side
--------------------------------------------------------
Key: JBSEAM-633
URL: http://jira.jboss.com/jira/browse/JBSEAM-633
Project: JBoss Seam
Issue Type: Patch
Components: Remoting
Affects Versions: 1.1.0.GA
Reporter: Nico Gau
Assigned To: Shane Bryzak
Priority: Optional
Hi all,
I don't really know what JIRA is by the way, so hopefully nobody is upset by this
post. I first mailed Gavin but he told me I should put it in JIRA.
I currently work on a project which uses Seam Remoting directly and I didn't find a
neat way in handling errors on the client side as Exceptions are not propagated to it.
Therefore I changed Seam to transmit all exceptions which can be handled in the javascript
part via another callback. E.g.:
Seam.Component.getInstance('userManager').currentUser(function(user) {
alert("user: " + user);
},
function(ex) {
alert("exception occured: " + ex.getMessage());
});
As the exception handler is optional, the change would not brake any client code. If you
are interested in the change, you can reach me at heinzbeinz AT googlemail.com
--
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:05 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-633) remoting extension in handling exceptions on client side
[ http://jira.jboss.com/jira/browse/JBSEAM-633?page=comments#action_12350674 ]
Nico Gau commented on JBSEAM-633:
---------------------------------
Hi,
I needed the exception stuff for handling self thrown exceptions. E.g. if you have a
backend function
@WebRemote
void dummy() throws MyException1, MyException2
{
if(...)
throw new MyException1(...);
if(...)
throw new MyException2(...);
...
}
then you can throw Exceptions in there and these Exceptions are transmitted to the client
which can handle it. Currently you need to have a return value which represents the error
so you can handle it.
remoting extension in handling exceptions on client side
--------------------------------------------------------
Key: JBSEAM-633
URL: http://jira.jboss.com/jira/browse/JBSEAM-633
Project: JBoss Seam
Issue Type: Patch
Components: Remoting
Affects Versions: 1.1.0.GA
Reporter: Nico Gau
Assigned To: Shane Bryzak
Priority: Optional
Hi all,
I don't really know what JIRA is by the way, so hopefully nobody is upset by this
post. I first mailed Gavin but he told me I should put it in JIRA.
I currently work on a project which uses Seam Remoting directly and I didn't find a
neat way in handling errors on the client side as Exceptions are not propagated to it.
Therefore I changed Seam to transmit all exceptions which can be handled in the javascript
part via another callback. E.g.:
Seam.Component.getInstance('userManager').currentUser(function(user) {
alert("user: " + user);
},
function(ex) {
alert("exception occured: " + ex.getMessage());
});
As the exception handler is optional, the change would not brake any client code. If you
are interested in the change, you can reach me at heinzbeinz AT googlemail.com
--
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:07 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-633) remoting extension in handling exceptions on client side
[ http://jira.jboss.com/jira/browse/JBSEAM-633?page=comments#action_12390102 ]
Shane Bryzak commented on JBSEAM-633:
-------------------------------------
We also need to handle 404 NOT FOUND errors and the like.
remoting extension in handling exceptions on client side
--------------------------------------------------------
Key: JBSEAM-633
URL: http://jira.jboss.com/jira/browse/JBSEAM-633
Project: JBoss Seam
Issue Type: Patch
Components: Remoting
Affects Versions: 1.1.0.GA
Reporter: Nico Gau
Assigned To: Shane Bryzak
Priority: Optional
Hi all,
I don't really know what JIRA is by the way, so hopefully nobody is upset by this
post. I first mailed Gavin but he told me I should put it in JIRA.
I currently work on a project which uses Seam Remoting directly and I didn't find a
neat way in handling errors on the client side as Exceptions are not propagated to it.
Therefore I changed Seam to transmit all exceptions which can be handled in the javascript
part via another callback. E.g.:
Seam.Component.getInstance('userManager').currentUser(function(user) {
alert("user: " + user);
},
function(ex) {
alert("exception occured: " + ex.getMessage());
});
As the exception handler is optional, the change would not brake any client code. If you
are interested in the change, you can reach me at heinzbeinz AT googlemail.com
--
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:53 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-633) remoting extension in handling exceptions on client side
[ http://jira.jboss.com/jira/browse/JBSEAM-633?page=all ]
Pete Muir updated JBSEAM-633:
-----------------------------
Component/s: Exception Handling
remoting extension in handling exceptions on client side
--------------------------------------------------------
Key: JBSEAM-633
URL: http://jira.jboss.com/jira/browse/JBSEAM-633
Project: JBoss Seam
Issue Type: Patch
Components: Remoting, Exception Handling
Affects Versions: 1.1.0.GA
Reporter: Nico Gau
Assigned To: Shane Bryzak
Priority: Optional
Hi all,
I don't really know what JIRA is by the way, so hopefully nobody is upset by this
post. I first mailed Gavin but he told me I should put it in JIRA.
I currently work on a project which uses Seam Remoting directly and I didn't find a
neat way in handling errors on the client side as Exceptions are not propagated to it.
Therefore I changed Seam to transmit all exceptions which can be handled in the javascript
part via another callback. E.g.:
Seam.Component.getInstance('userManager').currentUser(function(user) {
alert("user: " + user);
},
function(ex) {
alert("exception occured: " + ex.getMessage());
});
As the exception handler is optional, the change would not brake any client code. If you
are interested in the change, you can reach me at heinzbeinz AT googlemail.com
--
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:09 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-633) remoting extension in handling exceptions on client side
[
https://jira.jboss.org/jira/browse/JBSEAM-633?page=com.atlassian.jira.plu...
]
Francisco Jose Peredo Noguez commented on JBSEAM-633:
-----------------------------------------------------
I think this should be implemented as originally requested, and leave extensions like
extra-internationalization support, 404 NOT FOUND errors, redirection on remoting
failure, etc for much later:
http://www.seamframework.org/Community/SeamRemotingNoExceptionsSupport#co...
remoting extension in handling exceptions on client side
--------------------------------------------------------
Key: JBSEAM-633
URL: https://jira.jboss.org/jira/browse/JBSEAM-633
Project: Seam
Issue Type: Patch
Components: Exception Handling, Remoting
Affects Versions: 1.1.0.GA
Reporter: Nico Gau
Assignee: Shane Bryzak
Priority: Optional
Hi all,
I don't really know what JIRA is by the way, so hopefully nobody is upset by this
post. I first mailed Gavin but he told me I should put it in JIRA.
I currently work on a project which uses Seam Remoting directly and I didn't find a
neat way in handling errors on the client side as Exceptions are not propagated to it.
Therefore I changed Seam to transmit all exceptions which can be handled in the javascript
part via another callback. E.g.:
Seam.Component.getInstance('userManager').currentUser(function(user) {
alert("user: " + user);
},
function(ex) {
alert("exception occured: " + ex.getMessage());
});
As the exception handler is optional, the change would not brake any client code. If you
are interested in the change, you can reach me at heinzbeinz AT googlemail.com
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:37 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-633) remoting extension in handling exceptions on client side
[
https://jira.jboss.org/jira/browse/JBSEAM-633?page=com.atlassian.jira.plu...
]
Shane Bryzak updated JBSEAM-633:
--------------------------------
Fix Version/s: 2.1.0.GA
remoting extension in handling exceptions on client side
--------------------------------------------------------
Key: JBSEAM-633
URL: https://jira.jboss.org/jira/browse/JBSEAM-633
Project: Seam
Issue Type: Patch
Components: Exception Handling, Remoting
Affects Versions: 1.1.0.GA
Reporter: Nico Gau
Assignee: Shane Bryzak
Priority: Optional
Fix For: 2.1.0.GA
Hi all,
I don't really know what JIRA is by the way, so hopefully nobody is upset by this
post. I first mailed Gavin but he told me I should put it in JIRA.
I currently work on a project which uses Seam Remoting directly and I didn't find a
neat way in handling errors on the client side as Exceptions are not propagated to it.
Therefore I changed Seam to transmit all exceptions which can be handled in the javascript
part via another callback. E.g.:
Seam.Component.getInstance('userManager').currentUser(function(user) {
alert("user: " + user);
},
function(ex) {
alert("exception occured: " + ex.getMessage());
});
As the exception handler is optional, the change would not brake any client code. If you
are interested in the change, you can reach me at heinzbeinz AT googlemail.com
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:03 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-633) remoting extension in handling exceptions on client side
[
https://jira.jboss.org/jira/browse/JBSEAM-633?page=com.atlassian.jira.plu...
]
Pete Muir updated JBSEAM-633:
-----------------------------
Issue Type: Feature Request (was: Patch)
Fix Version/s: 2.1.1.CR1
(was: 2.1.0.GA)
remoting extension in handling exceptions on client side
--------------------------------------------------------
Key: JBSEAM-633
URL: https://jira.jboss.org/jira/browse/JBSEAM-633
Project: Seam
Issue Type: Feature Request
Components: Exception Handling, Remoting
Affects Versions: 1.1.0.GA
Reporter: Nico Gau
Assignee: Shane Bryzak
Priority: Optional
Fix For: 2.1.1.CR1
Hi all,
I don't really know what JIRA is by the way, so hopefully nobody is upset by this
post. I first mailed Gavin but he told me I should put it in JIRA.
I currently work on a project which uses Seam Remoting directly and I didn't find a
neat way in handling errors on the client side as Exceptions are not propagated to it.
Therefore I changed Seam to transmit all exceptions which can be handled in the javascript
part via another callback. E.g.:
Seam.Component.getInstance('userManager').currentUser(function(user) {
alert("user: " + user);
},
function(ex) {
alert("exception occured: " + ex.getMessage());
});
As the exception handler is optional, the change would not brake any client code. If you
are interested in the change, you can reach me at heinzbeinz AT googlemail.com
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:59 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-633) remoting extension in handling exceptions on client side
[
https://jira.jboss.org/jira/browse/JBSEAM-633?page=com.atlassian.jira.plu...
]
Shane Bryzak closed JBSEAM-633.
-------------------------------
Resolution: Done
I've now implemented basic exception handling features in Seam Remoting, I'll
update the documentation shortly.
remoting extension in handling exceptions on client side
--------------------------------------------------------
Key: JBSEAM-633
URL: https://jira.jboss.org/jira/browse/JBSEAM-633
Project: Seam
Issue Type: Feature Request
Components: Exception Handling, Remoting
Affects Versions: 1.1.0.GA
Reporter: Nico Gau
Assignee: Shane Bryzak
Priority: Optional
Fix For: 2.1.1.CR1
Hi all,
I don't really know what JIRA is by the way, so hopefully nobody is upset by this
post. I first mailed Gavin but he told me I should put it in JIRA.
I currently work on a project which uses Seam Remoting directly and I didn't find a
neat way in handling errors on the client side as Exceptions are not propagated to it.
Therefore I changed Seam to transmit all exceptions which can be handled in the javascript
part via another callback. E.g.:
Seam.Component.getInstance('userManager').currentUser(function(user) {
alert("user: " + user);
},
function(ex) {
alert("exception occured: " + ex.getMessage());
});
As the exception handler is optional, the change would not brake any client code. If you
are interested in the change, you can reach me at heinzbeinz AT googlemail.com
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:12 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-633) remoting extension in handling exceptions on client side
[
https://jira.jboss.org/jira/browse/JBSEAM-633?page=com.atlassian.jira.plu...
]
manuel kallenbach commented on JBSEAM-633:
------------------------------------------
Thanks for implementing this.
However, there is one thing I think that's not working properly.
If you start a batch of remote calls and specify only an exception handler for each but
the last call (callback is null for the first calls), the callback of the last call in the
batch won't be called.
I hope you could understand that. My english is not the best ;-)
remoting extension in handling exceptions on client side
--------------------------------------------------------
Key: JBSEAM-633
URL: https://jira.jboss.org/jira/browse/JBSEAM-633
Project: Seam
Issue Type: Feature Request
Components: Exception Handling, Remoting
Affects Versions: 1.1.0.GA
Reporter: Nico Gau
Assignee: Shane Bryzak
Priority: Optional
Fix For: 2.1.1.CR1
Hi all,
I don't really know what JIRA is by the way, so hopefully nobody is upset by this
post. I first mailed Gavin but he told me I should put it in JIRA.
I currently work on a project which uses Seam Remoting directly and I didn't find a
neat way in handling errors on the client side as Exceptions are not propagated to it.
Therefore I changed Seam to transmit all exceptions which can be handled in the javascript
part via another callback. E.g.:
Seam.Component.getInstance('userManager').currentUser(function(user) {
alert("user: " + user);
},
function(ex) {
alert("exception occured: " + ex.getMessage());
});
As the exception handler is optional, the change would not brake any client code. If you
are interested in the change, you can reach me at heinzbeinz AT googlemail.com
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5602
days inactive
6354
days old
12 comments
7 participants
participants (7)
-
Francisco Jose Peredo Noguez (JIRA) -
manuel kallenbach (JIRA)
-
Nico Gau (JIRA) -
Pete Muir (JIRA)
-
Shane Bryzak (JIRA)
-
Shane Bryzak (JIRA)
-
Simon Tian (JIRA)