I notice Implementation web have a similar issue as described in TUSCANY-2837, where it provides JSON-RPC functionality from inside it's own module. Should we use this same extension mechanism to make things more flexible and working in a consistent way ?
On Fri, Mar 27, 2009 at 1:38 AM, Luciano Resende <[email protected]> wrote: > I have committed the following changes related to TUSCANY-2837 : > - Added extension points to Implementation Widget (core-web) > - Updated ATOM (binding-atom-js) and JSON-RPC (binding-atom-js) > bindings using these extensions to provide Javascript Proxies > - Updated sample apps with new required dependencies > > Note that with these changes, applications that use Widget will need > to add new dependencies in order to the client js be generated > properly : > > <dependency> > <groupId>org.apache.tuscany.sca</groupId> > <artifactId>tuscany-binding-atom-js</artifactId> > <version>1.5-SNAPSHOT</version> > <scope>runtime</scope> > </dependency> > > <dependency> > <groupId>org.apache.tuscany.sca</groupId> > <artifactId>tuscany-binding-jsonrpc-js</artifactId> > <version>1.5-SNAPSHOT</version> > <scope>runtime</scope> > </dependency> > > Please let me know if you have comments or if you find any issues in this > area. > > > -- > Luciano Resende > http://people.apache.org/~lresende > http://lresende.blogspot.com/ > -- Luciano Resende Apache Tuscany, Apache PhotArk http://people.apache.org/~lresende http://lresende.blogspot.com/
