You are viewing a plain text version of this content. The canonical link for it is here.

Posted to user@commons.apache.org by "Mike Sparr - www.goomzee.com" <mi...@goomzee.com> on 2006/06/18 22:34:19 UTC

[SCXML] migration from old source to current - digest, exec, context handling

Rahul,

I pulled down the latest and attempting to migrate to new scxml baseline.
The following errors occurred with our implementation as they were based on
earlier version.  Only 5 errors referencing deprecated classes but curious
the best way to digest, etc. with current?  Errors are below.

Also, I used the following in console and source checked out and built just
fine.  Check out and build latest source (from console or DOS prompt -
assuming Subversion is installed):
============

cd /some/desired/directory
svn co http://svn.apache.org/repos/asf/jakarta/commons/proper/scxml/trunk
scxml
cd scxml
ant 

-------------

Errors based on deprecated class references:
==========

demo_jar:
    [mkdir] Created dir:
/Users/mike/Documents/dev/app/demoWorkspace/bin/demo
    [javac] Compiling 21 source files to
/Users/mike/Documents/dev/app/demoWorkspace/bin/demo
    [javac] 
/Users/mike/Documents/dev/app/demoWorkspace/src/com/demo/app/scxml/AppScxmlC
ontroller.java:15: cannot find symbol
    [javac] symbol  : class SCXMLDigester
    [javac] location: package org.apache.commons.scxml
    [javac] import org.apache.commons.scxml.SCXMLDigester;
    [javac]                                 ^
    [javac] 
/Users/mike/Documents/dev/app/demoWorkspace/src/com/demo/app/scxml/AppScxmlC
ontroller.java:87: cannot find symbol
    [javac] symbol  : method getRootContext()
    [javac] location: class org.apache.commons.scxml.model.SCXML
    [javac]             getExec(cb.getClientIdentifier()).getStateMachine()
    [javac]                    ^
    [javac] 
/Users/mike/Documents/dev/app/demoWorkspace/src/com/demo/app/scxml/AppScxmlC
ontroller.java:170: cannot find symbol
    [javac] symbol  : variable SCXMLDigester
    [javac] location: class com.demo.app.scxml.AppScxmlController
    [javac]                 scxml = SCXMLDigester.digest(scxml_url, new
DefaultHandler(),
    [javac]                         ^
    [javac] 
/Users/mike/Documents/dev/app/demoWorkspace/src/com/demo/app/scxml/AppScxmlC
ontroller.java:181: cannot find symbol
    [javac] symbol  : method
addListener(com.demo.app.scxml.AppScxmlListener)
    [javac] location: class org.apache.commons.scxml.model.SCXML
    [javac]             scxml.addListener(new AppScxmlListener());
    [javac]                  ^
    [javac] 
/Users/mike/Documents/dev/app/demoWorkspace/src/com/demo/app/scxml/AppScxmlD
ispatcher.java:141: cannot find symbol
    [javac] symbol  : method getRootContext()
    [javac] location: class org.apache.commons.scxml.model.SCXML
    [javac]        
exec.getStateMachine().getRootContext(),
    [javac]                                                     ^
    [javac] Note: Some input files use unchecked or unsafe operations.
    [javac] Note: Recompile with -Xlint:unchecked for details.
    [javac] 5 errors



---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org

Re: [SCXML] migration from old source to current - digest, exec, context handling

Posted by Rahul Akolkar <ra...@gmail.com>.

On 6/18/06, Mike Sparr - www.goomzee.com <mi...@goomzee.com> wrote:
> Hi Rahul,
>
> Thanks for the detailed response.  I found that the build succeeds but for
> some reason, I lose the target declaration of the send tag in ctx params
> (JEXL).  Still debugging.  With the JEXLEvaluator I get null response.  By
> replacing with the original  ELEvaluator I get text strings but no
> transform.
<snip/>

There are subtle differences you need to be aware of, especially in
the realm of Strings and String constants (note single quotes in JEXL
for String constants etc.) -- best way to understand that is probably
to compare and constrast the EL and JEXL microwave examples (long,
possibly fragmented, URLs):

http://svn.apache.org/repos/asf/jakarta/commons/proper/scxml/trunk/src/test/java/org/apache/commons/scxml/env/jsp/microwave-01.xml

vs.

http://svn.apache.org/repos/asf/jakarta/commons/proper/scxml/trunk/src/test/java/org/apache/commons/scxml/env/jexl/microwave-01.xml


>
> Do you recall any threads that gave FunctionMapper examples?
<snap/>

We discussed it before, but I don't recollect any code examples. In
any case, the EL FunctionMapper interface is simple, with one method:

Method resolveFunction(String prefix, String localName);

Impl looks like:

public Method resolveFunction(String prefix, String localName) {

   if (prefix != null
      && prefix.equals("foo")
      && localName.equals("bar")) {

        // return Method that you want to Map to
        // foo:bar(some arguments)
        // should be static method of some class
   }

   // and so on for other functions ...

   // finally, method not found?
   return null;
}

You will get ready-made impls for most String manipulation functions
out of the JSTL impl in use.


>
> I'll continue debugging to find out how to get everything working with new
> code-base and would appreciate any steer on making the above possible.
> Which Evaluator should I use (as I'm making changes now) Commons EL or JEXL.
>
<snip/>

EL, for reasons such as:

 * You are in a servlet container domain, EL is possibly all around
(and JEXL is possibly foreign)
 * You have an existing system that works with EL
 * String manipulation is easier with EL, IMO

-Rahul


> Cheers,
>
>
> Mike
>
<snap/>

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org

Re: [SCXML] migration from old source to current - digest, exec, context handling

Posted by Rahul Akolkar <ra...@gmail.com>.

On 6/19/06, Mike Sparr - www.goomzee.com <mi...@goomzee.com> wrote:
> :) Doh!  Nevermind.  I see you set the params BEFORE digestion.  That is
> resolved and thankfully I don't have to branch the library.  :)
>
<snip/>

Definitely a good thing, for both of us :-)


> Regarding the EL issue, yes I stuck with EL instead of JEXL (reverted
> rather).  I need to look at JSTL as you recommended to handle string
> functions.  Yes, the cb is in the context and EL works in controller but
> after updating code, it doesn't evaluate in Dispatcher?
>
> I didn't get that resolved but going to add some more debug.outs to find out
> what's happening with the context.  As I stated before, the controller
> places the executor in a store (bridge) after instantiation and the cb in
> context stores the handle (getClientIdentifier) so it can be retrieved.
> Everything worked fine until update so there must be some minor change I'm
> not seeing.
>
<snap/>

I haven't grasped the details of your code, so its hard for me to say
what is amiss. If you can localize what bit is failing, we can
possibly get further.


> I did notice that when updating /lib/ with the dependent jars a few things
> broke so I reverted back to prior versions [digester, beanutils, logging,
> el, etc.].  Just trying to get it stable again before plugging in new
> functionality and staying as close to spec as possible (hence updating
> library).
>
<snip/>

If you remember, what updates broke what part of the library? Would be
good to know. [scxml] Commons dependencies are pretty much the newest
versions (though I suspect it will be possible to use many lower
versions, ofcourse that can only be evaluated on a case-by-case basis
-- the perils of versioned dependencies et al).


> I'll keep digging - if I find out what it was I can let you know.  If
> anything, early adopters can have a migration path to new version.  :)
>
<snap/>

Yes, thats important. Please note that my replies will be very slow
over the next three weeks, but that is because of some high amount of
travel, rather than anything else.

-Rahul


> Best,
>
> Mike
>
<snip/>

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org

Re: [SCXML] add custom FunctionMapper to EL for string manipulation functions

Posted by Rahul Akolkar <ra...@gmail.com>.

On 6/21/06, Mike Sparr - www.goomzee.com <mi...@goomzee.com> wrote:
> Does anyone have example usage of ELEvaluator(FunctionMapper)?  I downloaded
> JSTL 1.1 and going through library but few examples on how to implement.
>
> Goal is to add some more functions with EL (like substringAfter,
> substringBefore, tokenize(var,delim), etc.).
>
<snip/>

See roughly halfway through this post from last week:

http://marc.theaimsgroup.com/?l=jakarta-commons-user&m=115074442229754&w=2

What worked, what didn't? I'd have written out a complete example if I
had more time today.


> Also, the commons ELEvaluator references deprecated FunctionMapper as noted
> in Sun's documentation:
>
> " Please note that as of JSP 2.1, all classes and interfaces that were in
> package javax.servlet.jsp.el have been deprecated in favor of the new
> unified Expression Language APIs (javax.el). See the Expression Language
> specification document for more details.
>
> While a JSP container must still support the deprecated APIs defined in
> javax.servlet.jsp.el, developers should only rely on the new javax.el APIs
> for new development work. "
>
<snap/>

Yes, JSP 2.0 EL (the one in the [scxml] examples) and JSP > 2.0
(unified) EL has numerous changes. To use unified EL in SCXML
documents, the appropriate Context and Evaluator implementation will
probably need to be authored, but thats only relevant if your web-app
is already using 2.1.

-Rahul


> ====
>
> Ideal functionality when scripting SCXML doc:
>
> <var name="foo" expr="First Last Email"/>
> <var name='fooTokens' expr='${tokenize(foo," ")}'/>
>
> <first-name>${foo[0]}</first-name>
> <last-name>${foo[1]}</last-name>
> <email>${foo[2]}</email>
>
> ====
>
> OR, when using VXML 2.0 builtin grammar for currency, when user says
> "dollars" the value passed is prefixed with USD (e.g. "20 dollars" is passed
> as "USD20").  It would be helpful to have some string manipulation functions
> like substringAfter("USD20","USD") to parse out the 20.
>
> ====
>
> If anyone knows how to add the FunctionMappers or best way to implement the
> above 2 cases minimum, I'm all ears.  :)
>
> Tx,
>
> Mike
>

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org