Re: JavaRpc code modularity

Hi Andreas,

my plan is (some parts already done):
- DONE: refactored the org.json.* classes to package
org.qooxdoo.rpc.json because the version used in JavaRpc is not the
original org.json version and may conflict with these (e.g. they do not
know "JsonException")
- DONE: created org.qooxdoo.rpc.AbstractRpcHandler which contains all
JsonRPC specific code from RpcServlet but absolutely no dependencies to
javax.Servlet.*
- TODO: Use commons-logging
- TODO: Update javadoc
- DONE: added support for enums
  - serialization: js object attributes "name"=enum.name(),
"ordinal"=enum.oridinal(), "string",enum.toString()
  - deserialization: Integer -> ordinal, other -> name

I'm also going to create an interface for a service resolver class that
finds a service (by name) plus finds matching methods. One
implementation will behave exactly as yours: get the class from
classpath (acepting only classes that implement RemoreService) and
lookup methods that throws RemoteExceptions. This will ensure 100%
backward compatibility. Another implementation will use annotations. For
this i'm going to use webservice annotations so that such a service can
be used both as (SOAP) webservice plus as Json service.

I'll keep you up to date with my changes.

Regards, Michael.


------------------------------------------------------------------------------
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel