So when I actually include tapestry-jquery things blow up when the servlet
container is initialized (I use an embedded jetty). This is with Tapestry 5.3
and using the mvn dependency described on the tapestry-jquery website. Any
ideas what I did wrong?
java.lang.NoClassDefFoundError:
org/apache/tapestry5/upload/services/UploadedFile
at java.lang.Class.getDeclaredConstructors0(Native Method)
at java.lang.Class.privateGetDeclaredConstructors(Class.java:2389)
at java.lang.Class.getConstructors(Class.java:1459)
at
org.apache.tapestry5.ioc.internal.util.InternalUtils.findAutobuildConstructor(InternalUtils.java:623)
at
org.apache.tapestry5.ioc.internal.ServiceBinderImpl.createStandardConstructorBasedObjectCreatorSource(ServiceBinderImpl.java:143)
at
org.apache.tapestry5.ioc.internal.ServiceBinderImpl.createObjectCreatorSourceFromImplementationClass(ServiceBinderImpl.java:128)
at
org.apache.tapestry5.ioc.internal.ServiceBinderImpl.flush(ServiceBinderImpl.java:95)
at
org.apache.tapestry5.ioc.internal.ServiceBinderImpl.finish(ServiceBinderImpl.java:83)
at
org.apache.tapestry5.ioc.internal.DefaultModuleDefImpl.bind(DefaultModuleDefImpl.java:539)
at
org.apache.tapestry5.ioc.internal.DefaultModuleDefImpl.<init>(DefaultModuleDefImpl.java:123)
at
org.apache.tapestry5.ioc.RegistryBuilder.add(RegistryBuilder.java:131)
at
org.apache.tapestry5.ioc.RegistryBuilder.add(RegistryBuilder.java:159)
at
org.apache.tapestry5.ioc.IOCUtilities.addModulesInList(IOCUtilities.java:137)
at
org.apache.tapestry5.ioc.IOCUtilities.addModulesInManifest(IOCUtilities.java:107)
at
org.apache.tapestry5.ioc.IOCUtilities.addDefaultModules(IOCUtilities.java:77)
at
org.apache.tapestry5.internal.TapestryAppInitializer.<init>(TapestryAppInitializer.java:124)
at org.apache.tapestry5.TapestryFilter.init(TapestryFilter.java:103)
at org.mortbay.jetty.servlet.FilterHolder.doStart(FilterHolder.java:97)
at
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at
org.mortbay.jetty.servlet.ServletHandler.initialize(ServletHandler.java:662)
at org.mortbay.jetty.servlet.Context.startContext(Context.java:140)
at
org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1250)
at
org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:517)
at
org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:467)
at
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at
org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:152)
at
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at
org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130)
at org.mortbay.jetty.Server.doStart(Server.java:224)
at
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
On Dec 2, 2011, at 1:48 PM, François Facon wrote:
> Hi Chris,
>
> Tapestry Ensure Backwards Compatibility on server side and also on client
> side.
> As mention by Thiago, you can use both prototype an jQuery with Tapestry.
> in Tapestry-jquery we use jQuery plugin structure to make sure $ is safe.
>
> see
> https://github.com/got5/tapestry5-jquery/blob/master/src/main/resources/org/got5/tapestry5/jquery/assets/mixins/button/button.js
> for example with agnostic structure introduce in 5.3.
>
> When we have to use both jQuery an Prototype on our projects we set
> configuration.add(JQuerySymbolConstants.SUPPRESS_PROTOTYPE, "false");
> jQuery is then used only inside jQuery Plugin.
>
> François
>
>
> 2011/12/2 Thiago H. de Paula Figueiredo <thiag...@gmail.com>:
>> On Fri, 02 Dec 2011 18:52:49 -0200, Chris Collins <chris...@me.com> wrote:
>>
>>> jquery and prototype living together in perfect harmony
>>> ==========================================
>>> I am working on a project where I am looking at a number of open source
>>> javascript libraries. Some depend on jQuery and some depend on prototype. I
>>> apologize for my ignorance here but it seems the fundamental issue is one of
>>> namespace primarily around "$". I know you can run jQuery in compatible
>>> mode but wouldn't this mean that any js library I used that depended on
>>> jQuery would need to be hacked up carefully to substitute all $() with
>>> jQuery(…)?
>>
>>
>> In theory, all jQuery plugins should *not* use $() and use $jQuery instead:
>> http://docs.jquery.com/Plugins/Authoring.
>>
>> --
>> Thiago H. de Paula Figueiredo
>> Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and
>> instructor
>> Owner, Ars Machina Tecnologia da Informação Ltda.
>> http://www.arsmachina.com.br
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
>> For additional commands, e-mail: users-h...@tapestry.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
