You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by ant elder <an...@gmail.com> on 2010/10/24 10:15:19 UTC
What are the *-dojo modules for?
I'm trying to understand what it is the real purpose of all the
Tuscany dojo modules:
tuscany-binding-atom-js-dojo
tuscany-binding-jsonrpc-js-dojo
tuscany-implementation-widget-runtime-dojo
tuscany-web-javascript-dojo
Can anyone help with some details?
...ant
Re: What are the *-dojo modules for?
Posted by ant elder <an...@gmail.com>.
On Sun, Oct 24, 2010 at 9:15 AM, ant elder <an...@gmail.com> wrote:
> I'm trying to understand what it is the real purpose of all the
> Tuscany dojo modules:
>
> tuscany-binding-atom-js-dojo
> tuscany-binding-jsonrpc-js-dojo
> tuscany-implementation-widget-runtime-dojo
> tuscany-web-javascript-dojo
>
> Can anyone help with some details?
>
> ...ant
>
and also tuscany-binding-rest-js-dojo
...ant
Re: What are the *-dojo modules for?
Posted by Simon Laws <si...@googlemail.com>.
>
> We only register the listener servlet on the module activator, and I
> believe it's just using the default http port configured/used in the
> host (e.g host-tomcat )
>
>
> [1] https://svn.apache.org/repos/asf/tuscany/sca-java-1.x/trunk/modules/web-javascript-dojo/src/main/java/org/apache/tuscany/sca/web/javascript/dojo/DojoModuleActivator.java
>
>
>
> --
> Luciano Resende
> http://people.apache.org/~lresende
> http://twitter.com/lresende1975
> http://lresende.blogspot.com/
>
That does seem to be the case. I'm going to raise a JIRA against this
as this seems to cause problems when you deploy to a container at
anything other than the default port. It's also a tad confusing the
way that multiple things can get registered against the root context
in the webapp case and overwrite one another with no warning.
Simon
--
Apache Tuscany committer: tuscany.apache.org
Co-author of a book about Tuscany and SCA: tuscanyinaction.com
Re: What are the *-dojo modules for?
Posted by Luciano Resende <lu...@gmail.com>.
On Fri, Nov 5, 2010 at 6:23 AM, Simon Laws <si...@googlemail.com> wrote:
> On Sun, Oct 24, 2010 at 5:06 PM, Luciano Resende <lu...@gmail.com> wrote:
>> On Sun, Oct 24, 2010 at 8:40 AM, ant elder <an...@gmail.com> wrote:
>>> On Sun, Oct 24, 2010 at 4:30 PM, Luciano Resende <lu...@gmail.com> wrote:
>>>> On Sun, Oct 24, 2010 at 4:17 AM, Simon Nash <na...@apache.org> wrote:
>>>>> ant elder wrote:
>>>>>>
>>>>>> I'm trying to understand what it is the real purpose of all the
>>>>>> Tuscany dojo modules:
>>>>>>
>>>>>> tuscany-binding-atom-js-dojo
>>>>>> tuscany-binding-jsonrpc-js-dojo
>>>>>> tuscany-implementation-widget-runtime-dojo
>>>>>> tuscany-web-javascript-dojo
>>>>>>
>>>>>> Can anyone help with some details?
>>>>>>
>>>>>> ...ant
>>>>>>
>>>>>>
>>>>> These are used by the store-dojo sample. If you look at the store.html file
>>>>> within that sample you will find some Javascript references to dojo things.
>>>>> There are also a few differences in the Javascript code when compared with
>>>>> the same code in the store sample. This might provide some clues :-)
>>>>>
>>>>> Simon
>>>>>
>>>>>
>>>>
>>>> These modules provide support for "Javascript Proxies" for
>>>> Implementation widget. They are based on Dojo Javascript Framework.
>>>>
>>>
>>> So they're only used with implementation.widget?
>>>
>>> ...ant
>>>
>>
>> Yes, and some of they are optional depending on the binding you are
>> using in conjunction with implementation.widget.
>>
>> --
>> Luciano Resende
>> http://people.apache.org/~lresende
>> http://twitter.com/lresende1975
>> http://lresende.blogspot.com/
>>
>
> As an aside, what controls what port these dojo resources are exposed
> on. I'm looking at a user issue and as far as I can tell I've set
> everything to work of 8085, bindings, wsdl etc. but these still come
> out on 8080, e.g.
>
> INFO: Added Servlet mapping: http://IBM-7A66AA9141B:8080/MyStore/dojo
> 05-Nov-2010 09:41:34 org.apache.tuscany.sca.host.webapp.WebAppServletHost addSer
> vletMapping
> INFO: Added Servlet mapping: http://IBM-7A66AA9141B:8080/MyStore/dojo/*
> 05-Nov-2010 09:41:34 org.apache.tuscany.sca.host.webapp.WebAppServletHost addSer
> vletMapping
> INFO: Added Servlet mapping: http://IBM-7A66AA9141B:8080/MyStore/tuscany
> 05-Nov-2010 09:41:34 org.apache.tuscany.sca.host.webapp.WebAppServletHost addSer
> vletMapping
> INFO: Added Servlet mapping: http://IBM-7A66AA9141B:8080/MyStore/tuscany/*
> 05-Nov-2010 09:41:34 org.apache.tuscany.sca.web.javascript.dojo.DojoWidgetJavasc
> riptProvider start
> INFO: Registered Dojo and Tuscany Dojo extensions (counter=1)
> 05-Nov-2010 09:41:36 org.apache.tuscany.sca.host.webapp.WebAppServletHost addSer
> vletMapping
> INFO: Added Servlet mapping: http://localhost:8085/MyStore/CatalogService
> 05-Nov-2010 09:41:36 org.apache.tuscany.sca.core.assembly.impl.EndpointRegistryI
> mpl addEndpoint
> INFO: Add endpoint - (@25330548)Endpoint: URI = Store#service-binding(CatalogSe
> rvice/catalogWS)
> 05-Nov-2010 09:41:36 org.apache.tuscany.sca.host.webapp.WebAppServletHost addSer
> vletMapping
> INFO: Added Servlet mapping: http://localhost:8085/MyStore/CatalogServiceJSONRPC
> /*
> 05-Nov-2010 09:41:36 org.apache.tuscany.sca.core.assembly.impl.EndpointRegistryI
> mpl addEndpoint
>
> I can't make them come up on anything but 8080 even if I specify a
> service binding for the impl.widget component.
>
We only register the listener servlet on the module activator, and I
believe it's just using the default http port configured/used in the
host (e.g host-tomcat )
[1] https://svn.apache.org/repos/asf/tuscany/sca-java-1.x/trunk/modules/web-javascript-dojo/src/main/java/org/apache/tuscany/sca/web/javascript/dojo/DojoModuleActivator.java
--
Luciano Resende
http://people.apache.org/~lresende
http://twitter.com/lresende1975
http://lresende.blogspot.com/
Re: What are the *-dojo modules for?
Posted by Simon Laws <si...@googlemail.com>.
On Sun, Oct 24, 2010 at 5:06 PM, Luciano Resende <lu...@gmail.com> wrote:
> On Sun, Oct 24, 2010 at 8:40 AM, ant elder <an...@gmail.com> wrote:
>> On Sun, Oct 24, 2010 at 4:30 PM, Luciano Resende <lu...@gmail.com> wrote:
>>> On Sun, Oct 24, 2010 at 4:17 AM, Simon Nash <na...@apache.org> wrote:
>>>> ant elder wrote:
>>>>>
>>>>> I'm trying to understand what it is the real purpose of all the
>>>>> Tuscany dojo modules:
>>>>>
>>>>> tuscany-binding-atom-js-dojo
>>>>> tuscany-binding-jsonrpc-js-dojo
>>>>> tuscany-implementation-widget-runtime-dojo
>>>>> tuscany-web-javascript-dojo
>>>>>
>>>>> Can anyone help with some details?
>>>>>
>>>>> ...ant
>>>>>
>>>>>
>>>> These are used by the store-dojo sample. If you look at the store.html file
>>>> within that sample you will find some Javascript references to dojo things.
>>>> There are also a few differences in the Javascript code when compared with
>>>> the same code in the store sample. This might provide some clues :-)
>>>>
>>>> Simon
>>>>
>>>>
>>>
>>> These modules provide support for "Javascript Proxies" for
>>> Implementation widget. They are based on Dojo Javascript Framework.
>>>
>>
>> So they're only used with implementation.widget?
>>
>> ...ant
>>
>
> Yes, and some of they are optional depending on the binding you are
> using in conjunction with implementation.widget.
>
> --
> Luciano Resende
> http://people.apache.org/~lresende
> http://twitter.com/lresende1975
> http://lresende.blogspot.com/
>
As an aside, what controls what port these dojo resources are exposed
on. I'm looking at a user issue and as far as I can tell I've set
everything to work of 8085, bindings, wsdl etc. but these still come
out on 8080, e.g.
INFO: Added Servlet mapping: http://IBM-7A66AA9141B:8080/MyStore/dojo
05-Nov-2010 09:41:34 org.apache.tuscany.sca.host.webapp.WebAppServletHost addSer
vletMapping
INFO: Added Servlet mapping: http://IBM-7A66AA9141B:8080/MyStore/dojo/*
05-Nov-2010 09:41:34 org.apache.tuscany.sca.host.webapp.WebAppServletHost addSer
vletMapping
INFO: Added Servlet mapping: http://IBM-7A66AA9141B:8080/MyStore/tuscany
05-Nov-2010 09:41:34 org.apache.tuscany.sca.host.webapp.WebAppServletHost addSer
vletMapping
INFO: Added Servlet mapping: http://IBM-7A66AA9141B:8080/MyStore/tuscany/*
05-Nov-2010 09:41:34 org.apache.tuscany.sca.web.javascript.dojo.DojoWidgetJavasc
riptProvider start
INFO: Registered Dojo and Tuscany Dojo extensions (counter=1)
05-Nov-2010 09:41:36 org.apache.tuscany.sca.host.webapp.WebAppServletHost addSer
vletMapping
INFO: Added Servlet mapping: http://localhost:8085/MyStore/CatalogService
05-Nov-2010 09:41:36 org.apache.tuscany.sca.core.assembly.impl.EndpointRegistryI
mpl addEndpoint
INFO: Add endpoint - (@25330548)Endpoint: URI = Store#service-binding(CatalogSe
rvice/catalogWS)
05-Nov-2010 09:41:36 org.apache.tuscany.sca.host.webapp.WebAppServletHost addSer
vletMapping
INFO: Added Servlet mapping: http://localhost:8085/MyStore/CatalogServiceJSONRPC
/*
05-Nov-2010 09:41:36 org.apache.tuscany.sca.core.assembly.impl.EndpointRegistryI
mpl addEndpoint
I can't make them come up on anything but 8080 even if I specify a
service binding for the impl.widget component.
Simon
--
Apache Tuscany committer: tuscany.apache.org
Co-author of a book about Tuscany and SCA: tuscanyinaction.com
Re: What are the *-dojo modules for?
Posted by ant elder <an...@gmail.com>.
On Thu, Nov 11, 2010 at 7:16 AM, Luciano Resende <lu...@gmail.com> wrote:
> On Wed, Nov 10, 2010 at 12:49 AM, Simon Nash <na...@apache.org> wrote:
>> ant elder wrote:
>>>
>>> On Sun, Oct 24, 2010 at 5:06 PM, Luciano Resende <lu...@gmail.com>
>>> wrote:
>>>>
>>>> On Sun, Oct 24, 2010 at 8:40 AM, ant elder <an...@gmail.com> wrote:
>>>>>
>>>>> On Sun, Oct 24, 2010 at 4:30 PM, Luciano Resende <lu...@gmail.com>
>>>>> wrote:
>>>>>>
>>>>>> On Sun, Oct 24, 2010 at 4:17 AM, Simon Nash <na...@apache.org> wrote:
>>>>>>>
>>>>>>> ant elder wrote:
>>>>>>>>
>>>>>>>> I'm trying to understand what it is the real purpose of all the
>>>>>>>> Tuscany dojo modules:
>>>>>>>>
>>>>>>>> tuscany-binding-atom-js-dojo
>>>>>>>> tuscany-binding-jsonrpc-js-dojo
>>>>>>>> tuscany-implementation-widget-runtime-dojo
>>>>>>>> tuscany-web-javascript-dojo
>>>>>>>>
>>>>>>>> Can anyone help with some details?
>>>>>>>>
>>>>>>>> ...ant
>>>>>>>>
>>>>>>>>
>>>>>>> These are used by the store-dojo sample. If you look at the
>>>>>>> store.html file
>>>>>>> within that sample you will find some Javascript references to dojo
>>>>>>> things.
>>>>>>> There are also a few differences in the Javascript code when compared
>>>>>>> with
>>>>>>> the same code in the store sample. This might provide some clues :-)
>>>>>>>
>>>>>>> Simon
>>>>>>>
>>>>>>>
>>>>>> These modules provide support for "Javascript Proxies" for
>>>>>> Implementation widget. They are based on Dojo Javascript Framework.
>>>>>>
>>>>> So they're only used with implementation.widget?
>>>>>
>>>>> ...ant
>>>>>
>>>> Yes, and some of they are optional depending on the binding you are
>>>> using in conjunction with implementation.widget.
>>>>
>>>
>>> Now that this thread has come up again it reminds me i'd asked about
>>> them. if they're for implementation.widget could we have widget in the
>>> module name to make that more clear? And now that we have the base +
>>> extension approach and these don't drag in extra dependencies wouldn't
>>> it be possible to just have them part of the widget runtime module so
>>> there are no extra modules at all?
>>>
>>> ...ant
>>>
>>>
>> I'll toss in another suggestion. Instead of parallel sets of these
>> 4 modules (one that uses dojo and one that doesn't), could the dojo and
>> non-dojo flavours of each module be combined, with runtime code in the
>> module to select which flavour should be used?
>>
>> Simon
>>
>>
>
> The issue here is with regards to embedders, which will use some of
> these mmodules but not all. If we combine them, this is not going to
> be possible anymore. If we make the choice via runtime, particularly
> in 2.x, this will have implications on the embedders, so I'd ask them
> first.
>
> I'll take a look in 2.x and figure out if there is a better layout for
> these modules, as they shouldn't have big implications on embedders
> (AFAIK)
>
I don't understand why this has impact on embedders, can you explain
you concerns in more detail?
I can't see any scenarios where people or environments will be
adversely impacted if there are a few classes that are not used in a
particular configuration. There might be an issue if those extra
classes drag in extra 3rd party dependencies so in those cases we need
to make sure things run ok without the extra dependencies. In this
case though there are no extra dependencies over whats in the
base-runtime so its fine.
The flip side of this is that by merging the modules it makes it
vastly simpler to use as you just need the single runtime jar and no
worrying about what there for of if you need things like
tuscany-web-javascript, tuscany-web-javascript-dojo,
tuscany-implementation-widget-runtime-dojo etc.
For 2.0 I think we need to make sure all the extensions have a default
configuration that works ok for most situations with just the
extension's single runtime jar.
...ant
Re: What are the *-dojo modules for?
Posted by Luciano Resende <lu...@gmail.com>.
On Wed, Nov 10, 2010 at 12:49 AM, Simon Nash <na...@apache.org> wrote:
> ant elder wrote:
>>
>> On Sun, Oct 24, 2010 at 5:06 PM, Luciano Resende <lu...@gmail.com>
>> wrote:
>>>
>>> On Sun, Oct 24, 2010 at 8:40 AM, ant elder <an...@gmail.com> wrote:
>>>>
>>>> On Sun, Oct 24, 2010 at 4:30 PM, Luciano Resende <lu...@gmail.com>
>>>> wrote:
>>>>>
>>>>> On Sun, Oct 24, 2010 at 4:17 AM, Simon Nash <na...@apache.org> wrote:
>>>>>>
>>>>>> ant elder wrote:
>>>>>>>
>>>>>>> I'm trying to understand what it is the real purpose of all the
>>>>>>> Tuscany dojo modules:
>>>>>>>
>>>>>>> tuscany-binding-atom-js-dojo
>>>>>>> tuscany-binding-jsonrpc-js-dojo
>>>>>>> tuscany-implementation-widget-runtime-dojo
>>>>>>> tuscany-web-javascript-dojo
>>>>>>>
>>>>>>> Can anyone help with some details?
>>>>>>>
>>>>>>> ...ant
>>>>>>>
>>>>>>>
>>>>>> These are used by the store-dojo sample. If you look at the
>>>>>> store.html file
>>>>>> within that sample you will find some Javascript references to dojo
>>>>>> things.
>>>>>> There are also a few differences in the Javascript code when compared
>>>>>> with
>>>>>> the same code in the store sample. This might provide some clues :-)
>>>>>>
>>>>>> Simon
>>>>>>
>>>>>>
>>>>> These modules provide support for "Javascript Proxies" for
>>>>> Implementation widget. They are based on Dojo Javascript Framework.
>>>>>
>>>> So they're only used with implementation.widget?
>>>>
>>>> ...ant
>>>>
>>> Yes, and some of they are optional depending on the binding you are
>>> using in conjunction with implementation.widget.
>>>
>>
>> Now that this thread has come up again it reminds me i'd asked about
>> them. if they're for implementation.widget could we have widget in the
>> module name to make that more clear? And now that we have the base +
>> extension approach and these don't drag in extra dependencies wouldn't
>> it be possible to just have them part of the widget runtime module so
>> there are no extra modules at all?
>>
>> ...ant
>>
>>
> I'll toss in another suggestion. Instead of parallel sets of these
> 4 modules (one that uses dojo and one that doesn't), could the dojo and
> non-dojo flavours of each module be combined, with runtime code in the
> module to select which flavour should be used?
>
> Simon
>
>
The issue here is with regards to embedders, which will use some of
these mmodules but not all. If we combine them, this is not going to
be possible anymore. If we make the choice via runtime, particularly
in 2.x, this will have implications on the embedders, so I'd ask them
first.
I'll take a look in 2.x and figure out if there is a better layout for
these modules, as they shouldn't have big implications on embedders
(AFAIK)
--
Luciano Resende
http://people.apache.org/~lresende
http://twitter.com/lresende1975
http://lresende.blogspot.com/
Re: What are the *-dojo modules for?
Posted by Simon Nash <na...@apache.org>.
ant elder wrote:
> On Sun, Oct 24, 2010 at 5:06 PM, Luciano Resende <lu...@gmail.com> wrote:
>> On Sun, Oct 24, 2010 at 8:40 AM, ant elder <an...@gmail.com> wrote:
>>> On Sun, Oct 24, 2010 at 4:30 PM, Luciano Resende <lu...@gmail.com> wrote:
>>>> On Sun, Oct 24, 2010 at 4:17 AM, Simon Nash <na...@apache.org> wrote:
>>>>> ant elder wrote:
>>>>>> I'm trying to understand what it is the real purpose of all the
>>>>>> Tuscany dojo modules:
>>>>>>
>>>>>> tuscany-binding-atom-js-dojo
>>>>>> tuscany-binding-jsonrpc-js-dojo
>>>>>> tuscany-implementation-widget-runtime-dojo
>>>>>> tuscany-web-javascript-dojo
>>>>>>
>>>>>> Can anyone help with some details?
>>>>>>
>>>>>> ...ant
>>>>>>
>>>>>>
>>>>> These are used by the store-dojo sample. If you look at the store.html file
>>>>> within that sample you will find some Javascript references to dojo things.
>>>>> There are also a few differences in the Javascript code when compared with
>>>>> the same code in the store sample. This might provide some clues :-)
>>>>>
>>>>> Simon
>>>>>
>>>>>
>>>> These modules provide support for "Javascript Proxies" for
>>>> Implementation widget. They are based on Dojo Javascript Framework.
>>>>
>>> So they're only used with implementation.widget?
>>>
>>> ...ant
>>>
>> Yes, and some of they are optional depending on the binding you are
>> using in conjunction with implementation.widget.
>>
>
> Now that this thread has come up again it reminds me i'd asked about
> them. if they're for implementation.widget could we have widget in the
> module name to make that more clear? And now that we have the base +
> extension approach and these don't drag in extra dependencies wouldn't
> it be possible to just have them part of the widget runtime module so
> there are no extra modules at all?
>
> ...ant
>
>
I'll toss in another suggestion. Instead of parallel sets of these
4 modules (one that uses dojo and one that doesn't), could the dojo and
non-dojo flavours of each module be combined, with runtime code in the
module to select which flavour should be used?
Simon
Re: What are the *-dojo modules for?
Posted by ant elder <an...@apache.org>.
On Sun, Oct 24, 2010 at 5:06 PM, Luciano Resende <lu...@gmail.com> wrote:
> On Sun, Oct 24, 2010 at 8:40 AM, ant elder <an...@gmail.com> wrote:
>> On Sun, Oct 24, 2010 at 4:30 PM, Luciano Resende <lu...@gmail.com> wrote:
>>> On Sun, Oct 24, 2010 at 4:17 AM, Simon Nash <na...@apache.org> wrote:
>>>> ant elder wrote:
>>>>>
>>>>> I'm trying to understand what it is the real purpose of all the
>>>>> Tuscany dojo modules:
>>>>>
>>>>> tuscany-binding-atom-js-dojo
>>>>> tuscany-binding-jsonrpc-js-dojo
>>>>> tuscany-implementation-widget-runtime-dojo
>>>>> tuscany-web-javascript-dojo
>>>>>
>>>>> Can anyone help with some details?
>>>>>
>>>>> ...ant
>>>>>
>>>>>
>>>> These are used by the store-dojo sample. If you look at the store.html file
>>>> within that sample you will find some Javascript references to dojo things.
>>>> There are also a few differences in the Javascript code when compared with
>>>> the same code in the store sample. This might provide some clues :-)
>>>>
>>>> Simon
>>>>
>>>>
>>>
>>> These modules provide support for "Javascript Proxies" for
>>> Implementation widget. They are based on Dojo Javascript Framework.
>>>
>>
>> So they're only used with implementation.widget?
>>
>> ...ant
>>
>
> Yes, and some of they are optional depending on the binding you are
> using in conjunction with implementation.widget.
>
Now that this thread has come up again it reminds me i'd asked about
them. if they're for implementation.widget could we have widget in the
module name to make that more clear? And now that we have the base +
extension approach and these don't drag in extra dependencies wouldn't
it be possible to just have them part of the widget runtime module so
there are no extra modules at all?
...ant
Re: What are the *-dojo modules for?
Posted by Luciano Resende <lu...@gmail.com>.
On Sun, Oct 24, 2010 at 8:40 AM, ant elder <an...@gmail.com> wrote:
> On Sun, Oct 24, 2010 at 4:30 PM, Luciano Resende <lu...@gmail.com> wrote:
>> On Sun, Oct 24, 2010 at 4:17 AM, Simon Nash <na...@apache.org> wrote:
>>> ant elder wrote:
>>>>
>>>> I'm trying to understand what it is the real purpose of all the
>>>> Tuscany dojo modules:
>>>>
>>>> tuscany-binding-atom-js-dojo
>>>> tuscany-binding-jsonrpc-js-dojo
>>>> tuscany-implementation-widget-runtime-dojo
>>>> tuscany-web-javascript-dojo
>>>>
>>>> Can anyone help with some details?
>>>>
>>>> ...ant
>>>>
>>>>
>>> These are used by the store-dojo sample. If you look at the store.html file
>>> within that sample you will find some Javascript references to dojo things.
>>> There are also a few differences in the Javascript code when compared with
>>> the same code in the store sample. This might provide some clues :-)
>>>
>>> Simon
>>>
>>>
>>
>> These modules provide support for "Javascript Proxies" for
>> Implementation widget. They are based on Dojo Javascript Framework.
>>
>
> So they're only used with implementation.widget?
>
> ...ant
>
Yes, and some of they are optional depending on the binding you are
using in conjunction with implementation.widget.
--
Luciano Resende
http://people.apache.org/~lresende
http://twitter.com/lresende1975
http://lresende.blogspot.com/
Re: What are the *-dojo modules for?
Posted by ant elder <an...@gmail.com>.
On Sun, Oct 24, 2010 at 4:30 PM, Luciano Resende <lu...@gmail.com> wrote:
> On Sun, Oct 24, 2010 at 4:17 AM, Simon Nash <na...@apache.org> wrote:
>> ant elder wrote:
>>>
>>> I'm trying to understand what it is the real purpose of all the
>>> Tuscany dojo modules:
>>>
>>> tuscany-binding-atom-js-dojo
>>> tuscany-binding-jsonrpc-js-dojo
>>> tuscany-implementation-widget-runtime-dojo
>>> tuscany-web-javascript-dojo
>>>
>>> Can anyone help with some details?
>>>
>>> ...ant
>>>
>>>
>> These are used by the store-dojo sample. If you look at the store.html file
>> within that sample you will find some Javascript references to dojo things.
>> There are also a few differences in the Javascript code when compared with
>> the same code in the store sample. This might provide some clues :-)
>>
>> Simon
>>
>>
>
> These modules provide support for "Javascript Proxies" for
> Implementation widget. They are based on Dojo Javascript Framework.
>
So they're only used with implementation.widget?
...ant
Re: What are the *-dojo modules for?
Posted by Luciano Resende <lu...@gmail.com>.
On Sun, Oct 24, 2010 at 4:17 AM, Simon Nash <na...@apache.org> wrote:
> ant elder wrote:
>>
>> I'm trying to understand what it is the real purpose of all the
>> Tuscany dojo modules:
>>
>> tuscany-binding-atom-js-dojo
>> tuscany-binding-jsonrpc-js-dojo
>> tuscany-implementation-widget-runtime-dojo
>> tuscany-web-javascript-dojo
>>
>> Can anyone help with some details?
>>
>> ...ant
>>
>>
> These are used by the store-dojo sample. If you look at the store.html file
> within that sample you will find some Javascript references to dojo things.
> There are also a few differences in the Javascript code when compared with
> the same code in the store sample. This might provide some clues :-)
>
> Simon
>
>
These modules provide support for "Javascript Proxies" for
Implementation widget. They are based on Dojo Javascript Framework.
--
Luciano Resende
http://people.apache.org/~lresende
http://twitter.com/lresende1975
http://lresende.blogspot.com/
Re: What are the *-dojo modules for?
Posted by Simon Nash <na...@apache.org>.
ant elder wrote:
> I'm trying to understand what it is the real purpose of all the
> Tuscany dojo modules:
>
> tuscany-binding-atom-js-dojo
> tuscany-binding-jsonrpc-js-dojo
> tuscany-implementation-widget-runtime-dojo
> tuscany-web-javascript-dojo
>
> Can anyone help with some details?
>
> ...ant
>
>
These are used by the store-dojo sample. If you look at the store.html file
within that sample you will find some Javascript references to dojo things.
There are also a few differences in the Javascript code when compared with
the same code in the store sample. This might provide some clues :-)
Simon