You are viewing a plain text version of this content. The canonical link for it is here.
Posted to bsf-dev@jakarta.apache.org by Stefan Bodewig <bo...@apache.org> on 2003/09/08 14:15:42 UTC
New rhino incompatibility ahead
Hi,
since the migration of the cvs server, Gump nag mails no longer reach
this list - I guess they are sitting in the moderation queue (if you
need a backup moderator, let me know, I'm can easily handle a few
extra spam messages 8-).
Since about a week a change in Rhino is causing problems, see
<http://cvs.apache.org/builds/gump/2003-09-06/jakarta-bsf.html>.
Looks as if the String-arg constructor has been removed.
I have no idea whether it has been deprecated already and whether a
suitable replacement exists.
Cheers
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: bsf-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: bsf-dev-help@jakarta.apache.org
Re: New rhino incompatibility ahead
Posted by Chuck Murcko <ch...@topsail.org>.
The list is configured to allow these messages to arrive now.
Chuck
On Sep 8, 2003, at 7:50 AM, Igor Bukanov wrote:
> Stefan Bodewig wrote:
>> Hi,
>> since the migration of the cvs server, Gump nag mails no longer reach
>> this list - I guess they are sitting in the moderation queue (if you
>> need a backup moderator, let me know, I'm can easily handle a few
>> extra spam messages 8-).
>> Since about a week a change in Rhino is causing problems, see
>> <http://cvs.apache.org/builds/gump/2003-09-06/jakarta-bsf.html>.
>> Looks as if the String-arg constructor has been removed.
>> I have no idea whether it has been deprecated already and whether a
>> suitable replacement exists.
>
> Here is the error output:
>
> [javac]
> /home/rubys/jakarta/jakarta-bsf/src/org/apache/bsf/engines/javascript/
> JavaScriptEngine.java:119: cannot resolve symbol
> [javac] symbol : constructor JavaScriptException (java.lang.String)
> [javac] location: class org.mozilla.javascript.JavaScriptException
> [javac] throw new JavaScriptException("function " + method + " not
> found.");
>
> In Rhino JavaScriptException is intended to represent exceptions
> thrown explicitly by JS throw statement. To indicate runtime errors in
> Java code related to JS implementation EvaluatorException should be
> used and the update code will look:
>
> throw new EvaluatorException("function " + method + " not found.");
>
> This form of EvaluatorException was present in Rhino since the first
> public release.
>
> For compatibility the old form of JavaScriptException(Object) will be
> restored but it would be nice if BSF would be updated to use the
> proper exception class.
>
> Regards, Igor
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: bsf-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: bsf-dev-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: bsf-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: bsf-dev-help@jakarta.apache.org
Re: New rhino incompatibility ahead
Posted by Igor Bukanov <ig...@fastmail.fm>.
Stefan Bodewig wrote:
> Hi,
>
> since the migration of the cvs server, Gump nag mails no longer reach
> this list - I guess they are sitting in the moderation queue (if you
> need a backup moderator, let me know, I'm can easily handle a few
> extra spam messages 8-).
>
> Since about a week a change in Rhino is causing problems, see
> <http://cvs.apache.org/builds/gump/2003-09-06/jakarta-bsf.html>.
> Looks as if the String-arg constructor has been removed.
>
> I have no idea whether it has been deprecated already and whether a
> suitable replacement exists.
Here is the error output:
[javac]
/home/rubys/jakarta/jakarta-bsf/src/org/apache/bsf/engines/javascript/JavaScriptEngine.java:119:
cannot resolve symbol
[javac] symbol : constructor JavaScriptException (java.lang.String)
[javac] location: class org.mozilla.javascript.JavaScriptException
[javac] throw new JavaScriptException("function " + method + " not
found.");
In Rhino JavaScriptException is intended to represent exceptions thrown
explicitly by JS throw statement. To indicate runtime errors in Java
code related to JS implementation EvaluatorException should be used and
the update code will look:
throw new EvaluatorException("function " + method + " not found.");
This form of EvaluatorException was present in Rhino since the first
public release.
For compatibility the old form of JavaScriptException(Object) will be
restored but it would be nice if BSF would be updated to use the proper
exception class.
Regards, Igor
---------------------------------------------------------------------
To unsubscribe, e-mail: bsf-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: bsf-dev-help@jakarta.apache.org