I think I remember this situation and it was not at all related to the BASE core, but to the web service api. Web service methods that doesn't return a value could not return an error message either. There is a ticket about this (http://base.thep.lu.se/ticket/862) but it should have been fixed in BASE 2.5 and there are not many changes to the web service code after this.
I don't know if your issue is related to this one, but your stacktrace is containing 'RPCInOnlyMessageReceiver' which indicates that the method doesn't return a value. As far as I know there should be no such methods remaining in BASE... so I am a bit confused about what is causing the error. Can you post some code that reproduces the problem? /Nicklas Olivier Lefevre wrote: > I noticed that not all PermissionDeniedException's thrown on > the server side (you can see them in the Tomcat log) are > relayed to the client side as an AxisFault. AFAICT this > affects all such exceptions thrown by Application. Other > instances of a PermissionDeniedException, e.g., when trying > to access an item, are normally relayed. > > In the log the difference between the two is that the "silent" > permission errors have an entry of the form: > > timestamp ERROR RPCInOnlyMessageReceiver:77 - Permission denied: msg > net.sf.basedb.core.PermissionDeniedException: Permission denied: msg > stack trace > timestamp ERROR AbstractMessageReceiver:101 - org.apache.axis2.AxisFault: > Permission denied: msg > > whereas those with are properly relayed as an AxisFault have an > entry of the form > > timestamp ERROR RPCMessageReceiver:153 - Permission denied: msg > java.lang.reflect.InvocationTargetException > first part of stack trace > Caused by: net.sf.basedb.core.PermissionDeniedException: Permission denied: > msg > second part of stack trace > > This is *very* annoying because, for instance, if you have an > invalid login call followed by a read call, your code will > proceed to the read call without having logged in, at which > point you will get a "Permission denied: Not allowed to read > xyz", but unless you read the Tomcat log you will not realize > that the root cause was not the read call but the failed login. > > What sorcery is this? Why aren't *all* errors on the server > side manifested as an AxisFault on the client side? Note that > this is with BASE 2.9.2 and thus with Axis 1.3, neither of > which is the current version but it is what I am stuck with. > > Thanks, > > -- O.L. > > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > The BASE general discussion mailing list > basedb-users@lists.sourceforge.net > unsubscribe: send a mail with subject "unsubscribe" to > basedb-users-requ...@lists.sourceforge.net ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ The BASE general discussion mailing list basedb-users@lists.sourceforge.net unsubscribe: send a mail with subject "unsubscribe" to basedb-users-requ...@lists.sourceforge.net
