You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Ben Dotte <bd...@widen.com> on 2007/05/01 16:27:47 UTC
4.1.2 snapshot changes 4-20 to 4-30
Were there some sort of fundamental changes that happened between the
Tapestry 4.1.2 4-20 snapshot and the one from 4-30? I tried upgrading to
4-30 and I just seem to hit one error after another. The first problem
is an EventListener that used to work fine:
@EventListener(targets="sessionData", events="onclick")
public void sessionDataClicked(IRequestCycle cycle)
{
setShowSessionData(true);
cycle.getResponseBuilder().updateComponent("theSessionData");
}
The nested stack from that is:
Caused by: org.apache.hivemind.ApplicationRuntimeException: No component
found in tree for EventListener binding with a matching component id of
sessionData. [context:/WEB-INF/app/ErrorPage.html, line 1]
at
org.apache.tapestry.pageload.EventConnectionVisitor.visitComponent(Event
ConnectionVisitor.java:51)
at
$IComponentVisitor_11248054e16.visitComponent($IComponentVisitor_1124805
4e16.java)
at
$IComponentVisitor_11248054e17.visitComponent($IComponentVisitor_1124805
4e17.java)
at
org.apache.tapestry.pageload.ComponentTreeWalker.walkComponentTree(Compo
nentTreeWalker.java:45)
at
org.apache.tapestry.pageload.ComponentTreeWalker.walkComponentTree(Compo
nentTreeWalker.java:57)
at
org.apache.tapestry.pageload.PageLoader.loadPage(PageLoader.java:604)
at
$IPageLoader_11248054e04.loadPage($IPageLoader_11248054e04.java)
at
$IPageLoader_11248054e05.loadPage($IPageLoader_11248054e05.java)
at
org.apache.tapestry.pageload.PageSource.getPage(PageSource.java:119)
at
$IPageSource_11248054d1c.getPage($IPageSource_11248054d1c.java)
at
org.apache.tapestry.engine.RequestCycle.loadPage(RequestCycle.java:239)
at
org.apache.tapestry.engine.RequestCycle.getPage(RequestCycle.java:226)
at
org.apache.tapestry.error.ExceptionPresenterImpl.presentException(Except
ionPresenterImpl.java:42)
... 62 more
After I commented that out I got another error for a Script:
<span jwcid="@Script" script="/scripts/categoryHelper.script" />
Caused by: org.apache.tapestry.util.xml.DocumentParseException: Unable
to find resource classpath:/scripts/categoryHelper.script.
[classpath:/scripts/categoryHelper.script]
at
org.apache.tapestry.util.xml.RuleDirectedParser.parse(RuleDirectedParser
.java:125)
at
org.apache.tapestry.script.ScriptParser.parse(ScriptParser.java:112)
at
org.apache.tapestry.engine.DefaultScriptSource.parse(DefaultScriptSource
.java:88)
... 124 more
I saw a minor change in JIRA to the way scripts are found but I couldn't
see how it would relate to this in particular.
Thanks,
Ben
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
RE: 4.1.2 snapshot changes 4-20 to 4-30
Posted by Ben Dotte <bd...@widen.com>.
Thanks Jesse :) It's easier to work through the bugs when someone is
fixing them so rapidly!
-----Original Message-----
From: Jesse Kuhnert [mailto:jkuhnert@gmail.com]
Sent: Tuesday, May 01, 2007 5:20 PM
To: Tapestry users
Subject: Re: 4.1.2 snapshot changes 4-20 to 4-30
Cool. .It did actually affect the project I'm working on now so I can't
pretend it was entirely the result of this thread - but either way with
the
number of bug reports you've filed for ognl 2.7 I think all
current/potential tapestry 4.1.2 users should really be thanking you. ;)
I can't imagine how annoying it was being blocked by all of those
compilation errors, so at the very least you've earned having any
problems
you run into take higher priority than normal. Thanks! :)
On 5/1/07, Ben Dotte <bd...@widen.com> wrote:
>
> Thanks for looking into it so quickly.. I will try out the new
snapshot
> tomorrow.
>
> -----Original Message-----
> From: Jesse Kuhnert [mailto:jkuhnert@gmail.com]
> Sent: Tuesday, May 01, 2007 2:49 PM
> To: Tapestry users
> Subject: Re: 4.1.2 snapshot changes 4-20 to 4-30
>
> A fix is deploying now for the @EventListener related issue. (though
I'm
> unsure if it fixes it for Ben but we'll see)
>
> The script thing will have to happen later tonight.
>
> On 5/1/07, Jesse Kuhnert <jk...@gmail.com> wrote:
> >
> > Yeah I'm aware of the issue, think it's fixed locally but am still
> testing
> > the changes.
> >
> > On 5/1/07, Andreas Andreou < andyhot@di.uoa.gr> wrote:
> > >
> > > I think i've seen some similar issues in the latest snapshots...
> > >
> > > They indeed seem to be related to how components/pages are found,
> i'll
> > > try
> > > to have
> > > a clean example demonstrating this and register a JIRA.
> > >
> > > For now, try using:
> > >
> > > <dependency>
> > > <groupId>org.apache.tapestry</groupId>
> > > <artifactId>tapestry-framework</artifactId>
> > > <version>4.1.2-20070424.205219-56</version>
> > > </dependency>
> > >
> > >
> > >
> > > On 5/1/07, Ben Dotte <bd...@widen.com> wrote:
> > > >
> > > > I tried the snapshots from this morning but unfortunately I
still
> get
> > > > the same EventListener error. For the script error I tried
adding
> > > > context: to the path like this:
> > > >
> > > > <span jwcid="@Script"
> script="context:/scripts/categoryHelper.script"
> > > />
> > > >
> > > > But now the error I get for that is:
> > > >
> > > > Unable to parse script
> > > >
> > >
>
classpath:collective/ui/components/context:/scripts/categoryHelper.scrip
> > > > t.
> > > >
> > > > -----Original Message-----
> > > > From: Jesse Kuhnert [mailto:jkuhnert@gmail.com ]
> > > > Sent: Tuesday, May 01, 2007 9:33 AM
> > > > To: Tapestry users
> > > > Subject: Re: 4.1.2 snapshot changes 4-20 to 4-30
> > > >
> > > > There were two unrelated changes made. The @EventListener change
> > > > involved
> > > > some inevitable fundamental flaws that I think are all fully
> resolved
> > > as
> > > > of
> > > > this mornings deployment of snapshots.
> > > >
> > > > The script error is related to how the component specs are being
> > > > resolved,
> > > > I'll look into why this is messing up for you but am sure that
if
> you
> > > > add
> > > > either "context:" or "classpath:" in front of your string it
will
> work
> > > > correctly. (though I intended for it to work without them, so
it's
> a
> > > bug
> > > > if
> > > > it isn't working)
> > > >
> > > > On 5/1/07, Ben Dotte <bd...@widen.com> wrote:
> > > > >
> > > > > Were there some sort of fundamental changes that happened
> between
> > > the
> > > > > Tapestry 4.1.2 4-20 snapshot and the one from 4-30? I tried
> > > upgrading
> > > > to
> > > > > 4-30 and I just seem to hit one error after another. The first
> > > problem
> > > > > is an EventListener that used to work fine:
> > > > >
> > > > > @EventListener(targets="sessionData", events="onclick")
> > > > > public void sessionDataClicked(IRequestCycle cycle)
> > > > > {
> > > > > setShowSessionData(true);
> > > > > cycle.getResponseBuilder
> > > ().updateComponent("theSessionData");
> > > > > }
> > > > >
> > > > > The nested stack from that is:
> > > > >
> > > > > Caused by: org.apache.hivemind.ApplicationRuntimeException :
No
> > > > component
> > > > > found in tree for EventListener binding with a matching
> component id
> > > > of
> > > > > sessionData. [context:/WEB-INF/app/ErrorPage.html, line 1]
> > > > > at
> > > > >
> > > >
org.apache.tapestry.pageload.EventConnectionVisitor.visitComponent
> > > (Event
> > > > > ConnectionVisitor.java:51)
> > > > > at
> > > > >
> > > >
> > >
>
$IComponentVisitor_11248054e16.visitComponent($IComponentVisitor_1124805
> > > > > 4e16.java)
> > > > > at
> > > > >
> > > >
> > >
>
$IComponentVisitor_11248054e17.visitComponent($IComponentVisitor_1124805
> > > > > 4e17.java)
> > > > > at
> > > > >
> > > >
>
org.apache.tapestry.pageload.ComponentTreeWalker.walkComponentTree(Compo
> > > > > nentTreeWalker.java:45)
> > > > > at
> > > > >
> > > >
org.apache.tapestry.pageload.ComponentTreeWalker.walkComponentTree
> > > (Compo
> > > > > nentTreeWalker.java:57)
> > > > > at
> > > > >
org.apache.tapestry.pageload.PageLoader.loadPage(PageLoader.java
> > > :604)
> > > > > at
> > > > >
$IPageLoader_11248054e04.loadPage($IPageLoader_11248054e04.java)
> > > > > at
> > > > >
$IPageLoader_11248054e05.loadPage($IPageLoader_11248054e05.java)
> > > > > at
> > > > >
> org.apache.tapestry.pageload.PageSource.getPage(PageSource.java:119)
> > > > > at
> > > > >
$IPageSource_11248054d1c.getPage($IPageSource_11248054d1c.java)
> > > > > at
> > > > >
> > > >
org.apache.tapestry.engine.RequestCycle.loadPage(RequestCycle.java
> > > :239)
> > > > > at
> > > > >
> org.apache.tapestry.engine.RequestCycle.getPage(RequestCycle.java
> > > :226)
> > > > > at
> > > > >
> > > >
org.apache.tapestry.error.ExceptionPresenterImpl.presentException
> > > (Except
> > > > > ionPresenterImpl.java:42)
> > > > > ... 62 more
> > > > >
> > > > > After I commented that out I got another error for a Script:
> > > > >
> > > > > <span jwcid="@Script" script="/scripts/categoryHelper.script"
/>
> > > > >
> > > > > Caused by:
org.apache.tapestry.util.xml.DocumentParseException:
> > > Unable
> > > > > to find resource classpath:/scripts/categoryHelper.script.
> > > > > [classpath:/scripts/categoryHelper.script]
> > > > > at
> > > > >
> > > > org.apache.tapestry.util.xml.RuleDirectedParser.parse
> > > (RuleDirectedParser
> > > > > .java:125)
> > > > > at
> > > > >
> org.apache.tapestry.script.ScriptParser.parse(ScriptParser.java:112)
> > > > > at
> > > > >
> > > > org.apache.tapestry.engine.DefaultScriptSource.parse
> > > (DefaultScriptSource
> > > > > .java:88)
> > > > > ... 124 more
> > > > >
> > > > > I saw a minor change in JIRA to the way scripts are found but
I
> > > > couldn't
> > > > > see how it would relate to this in particular.
> > > > >
> > > > > Thanks,
> > > > > Ben
> > > > >
> > > > >
> > >
> ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > > > > For additional commands, e-mail:
users-help@tapestry.apache.org
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > Jesse Kuhnert
> > > > Tapestry/Dojo team member/developer
> > > >
> > > > Open source based consulting work centered around
> > > > dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
> > > >
> > > >
> ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > > > For additional commands, e-mail: users-help@tapestry.apache.org
> > > >
> > > >
> > > >
> > >
> > >
> > > --
> > > Andreas Andreou - andyhot@apache.org - http://andyhot.di.uoa.gr
> > > Tapestry / Tacos developer
> > > Open Source / JEE Consulting
> > >
> >
> >
> >
> > --
> > Jesse Kuhnert
> > Tapestry/Dojo team member/developer
> >
> > Open source based consulting work centered around
> > dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
> >
>
>
>
> --
> Jesse Kuhnert
> Tapestry/Dojo team member/developer
>
> Open source based consulting work centered around
> dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
--
Jesse Kuhnert
Tapestry/Dojo team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: 4.1.2 snapshot changes 4-20 to 4-30
Posted by Jesse Kuhnert <jk...@gmail.com>.
Cool. .It did actually affect the project I'm working on now so I can't
pretend it was entirely the result of this thread - but either way with the
number of bug reports you've filed for ognl 2.7 I think all
current/potential tapestry 4.1.2 users should really be thanking you. ;)
I can't imagine how annoying it was being blocked by all of those
compilation errors, so at the very least you've earned having any problems
you run into take higher priority than normal. Thanks! :)
On 5/1/07, Ben Dotte <bd...@widen.com> wrote:
>
> Thanks for looking into it so quickly.. I will try out the new snapshot
> tomorrow.
>
> -----Original Message-----
> From: Jesse Kuhnert [mailto:jkuhnert@gmail.com]
> Sent: Tuesday, May 01, 2007 2:49 PM
> To: Tapestry users
> Subject: Re: 4.1.2 snapshot changes 4-20 to 4-30
>
> A fix is deploying now for the @EventListener related issue. (though I'm
> unsure if it fixes it for Ben but we'll see)
>
> The script thing will have to happen later tonight.
>
> On 5/1/07, Jesse Kuhnert <jk...@gmail.com> wrote:
> >
> > Yeah I'm aware of the issue, think it's fixed locally but am still
> testing
> > the changes.
> >
> > On 5/1/07, Andreas Andreou < andyhot@di.uoa.gr> wrote:
> > >
> > > I think i've seen some similar issues in the latest snapshots...
> > >
> > > They indeed seem to be related to how components/pages are found,
> i'll
> > > try
> > > to have
> > > a clean example demonstrating this and register a JIRA.
> > >
> > > For now, try using:
> > >
> > > <dependency>
> > > <groupId>org.apache.tapestry</groupId>
> > > <artifactId>tapestry-framework</artifactId>
> > > <version>4.1.2-20070424.205219-56</version>
> > > </dependency>
> > >
> > >
> > >
> > > On 5/1/07, Ben Dotte <bd...@widen.com> wrote:
> > > >
> > > > I tried the snapshots from this morning but unfortunately I still
> get
> > > > the same EventListener error. For the script error I tried adding
> > > > context: to the path like this:
> > > >
> > > > <span jwcid="@Script"
> script="context:/scripts/categoryHelper.script"
> > > />
> > > >
> > > > But now the error I get for that is:
> > > >
> > > > Unable to parse script
> > > >
> > >
> classpath:collective/ui/components/context:/scripts/categoryHelper.scrip
> > > > t.
> > > >
> > > > -----Original Message-----
> > > > From: Jesse Kuhnert [mailto:jkuhnert@gmail.com ]
> > > > Sent: Tuesday, May 01, 2007 9:33 AM
> > > > To: Tapestry users
> > > > Subject: Re: 4.1.2 snapshot changes 4-20 to 4-30
> > > >
> > > > There were two unrelated changes made. The @EventListener change
> > > > involved
> > > > some inevitable fundamental flaws that I think are all fully
> resolved
> > > as
> > > > of
> > > > this mornings deployment of snapshots.
> > > >
> > > > The script error is related to how the component specs are being
> > > > resolved,
> > > > I'll look into why this is messing up for you but am sure that if
> you
> > > > add
> > > > either "context:" or "classpath:" in front of your string it will
> work
> > > > correctly. (though I intended for it to work without them, so it's
> a
> > > bug
> > > > if
> > > > it isn't working)
> > > >
> > > > On 5/1/07, Ben Dotte <bd...@widen.com> wrote:
> > > > >
> > > > > Were there some sort of fundamental changes that happened
> between
> > > the
> > > > > Tapestry 4.1.2 4-20 snapshot and the one from 4-30? I tried
> > > upgrading
> > > > to
> > > > > 4-30 and I just seem to hit one error after another. The first
> > > problem
> > > > > is an EventListener that used to work fine:
> > > > >
> > > > > @EventListener(targets="sessionData", events="onclick")
> > > > > public void sessionDataClicked(IRequestCycle cycle)
> > > > > {
> > > > > setShowSessionData(true);
> > > > > cycle.getResponseBuilder
> > > ().updateComponent("theSessionData");
> > > > > }
> > > > >
> > > > > The nested stack from that is:
> > > > >
> > > > > Caused by: org.apache.hivemind.ApplicationRuntimeException : No
> > > > component
> > > > > found in tree for EventListener binding with a matching
> component id
> > > > of
> > > > > sessionData. [context:/WEB-INF/app/ErrorPage.html, line 1]
> > > > > at
> > > > >
> > > > org.apache.tapestry.pageload.EventConnectionVisitor.visitComponent
> > > (Event
> > > > > ConnectionVisitor.java:51)
> > > > > at
> > > > >
> > > >
> > >
> $IComponentVisitor_11248054e16.visitComponent($IComponentVisitor_1124805
> > > > > 4e16.java)
> > > > > at
> > > > >
> > > >
> > >
> $IComponentVisitor_11248054e17.visitComponent($IComponentVisitor_1124805
> > > > > 4e17.java)
> > > > > at
> > > > >
> > > >
> org.apache.tapestry.pageload.ComponentTreeWalker.walkComponentTree(Compo
> > > > > nentTreeWalker.java:45)
> > > > > at
> > > > >
> > > > org.apache.tapestry.pageload.ComponentTreeWalker.walkComponentTree
> > > (Compo
> > > > > nentTreeWalker.java:57)
> > > > > at
> > > > > org.apache.tapestry.pageload.PageLoader.loadPage(PageLoader.java
> > > :604)
> > > > > at
> > > > > $IPageLoader_11248054e04.loadPage($IPageLoader_11248054e04.java)
> > > > > at
> > > > > $IPageLoader_11248054e05.loadPage($IPageLoader_11248054e05.java)
> > > > > at
> > > > >
> org.apache.tapestry.pageload.PageSource.getPage(PageSource.java:119)
> > > > > at
> > > > > $IPageSource_11248054d1c.getPage($IPageSource_11248054d1c.java)
> > > > > at
> > > > >
> > > > org.apache.tapestry.engine.RequestCycle.loadPage(RequestCycle.java
> > > :239)
> > > > > at
> > > > >
> org.apache.tapestry.engine.RequestCycle.getPage(RequestCycle.java
> > > :226)
> > > > > at
> > > > >
> > > > org.apache.tapestry.error.ExceptionPresenterImpl.presentException
> > > (Except
> > > > > ionPresenterImpl.java:42)
> > > > > ... 62 more
> > > > >
> > > > > After I commented that out I got another error for a Script:
> > > > >
> > > > > <span jwcid="@Script" script="/scripts/categoryHelper.script" />
> > > > >
> > > > > Caused by: org.apache.tapestry.util.xml.DocumentParseException:
> > > Unable
> > > > > to find resource classpath:/scripts/categoryHelper.script.
> > > > > [classpath:/scripts/categoryHelper.script]
> > > > > at
> > > > >
> > > > org.apache.tapestry.util.xml.RuleDirectedParser.parse
> > > (RuleDirectedParser
> > > > > .java:125)
> > > > > at
> > > > >
> org.apache.tapestry.script.ScriptParser.parse(ScriptParser.java:112)
> > > > > at
> > > > >
> > > > org.apache.tapestry.engine.DefaultScriptSource.parse
> > > (DefaultScriptSource
> > > > > .java:88)
> > > > > ... 124 more
> > > > >
> > > > > I saw a minor change in JIRA to the way scripts are found but I
> > > > couldn't
> > > > > see how it would relate to this in particular.
> > > > >
> > > > > Thanks,
> > > > > Ben
> > > > >
> > > > >
> > >
> ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > > > > For additional commands, e-mail: users-help@tapestry.apache.org
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > Jesse Kuhnert
> > > > Tapestry/Dojo team member/developer
> > > >
> > > > Open source based consulting work centered around
> > > > dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
> > > >
> > > >
> ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > > > For additional commands, e-mail: users-help@tapestry.apache.org
> > > >
> > > >
> > > >
> > >
> > >
> > > --
> > > Andreas Andreou - andyhot@apache.org - http://andyhot.di.uoa.gr
> > > Tapestry / Tacos developer
> > > Open Source / JEE Consulting
> > >
> >
> >
> >
> > --
> > Jesse Kuhnert
> > Tapestry/Dojo team member/developer
> >
> > Open source based consulting work centered around
> > dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
> >
>
>
>
> --
> Jesse Kuhnert
> Tapestry/Dojo team member/developer
>
> Open source based consulting work centered around
> dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
--
Jesse Kuhnert
Tapestry/Dojo team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
RE: 4.1.2 snapshot changes 4-20 to 4-30
Posted by Ben Dotte <bd...@widen.com>.
I think its finally working!
Thanks!!
-----Original Message-----
From: Jesse Kuhnert [mailto:jkuhnert@gmail.com]
Sent: Thursday, May 03, 2007 3:18 PM
To: Tapestry users
Subject: Re: 4.1.2 snapshot changes 4-20 to 4-30
Ok....It's deploying now.
On 5/3/07, Ben Dotte <bd...@widen.com> wrote:
>
> <snipped>
>
--
Jesse Kuhnert
Tapestry/Dojo team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: 4.1.2 snapshot changes 4-20 to 4-30
Posted by Jesse Kuhnert <jk...@gmail.com>.
Ok....It's deploying now.
On 5/3/07, Ben Dotte <bd...@widen.com> wrote:
>
> <snipped>
>
--
Jesse Kuhnert
Tapestry/Dojo team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
RE: 4.1.2 snapshot changes 4-20 to 4-30
Posted by Ben Dotte <bd...@widen.com>.
Seems to be fixed.. thanks!!
-----Original Message-----
From: Jesse Kuhnert [mailto:jkuhnert@gmail.com]
Sent: Monday, May 07, 2007 10:19 PM
To: Tapestry users
Subject: Re: 4.1.2 snapshot changes 4-20 to 4-30
I hope that app of yours is huge and unwieldy. ;)
there may be a fix out now.....I won't be using my "heavy dev" computer
tomorrow so if there's a problem starting tomorrow it won't be
resolvable
until at least tomorrow night..
On 5/7/07, Jesse Kuhnert <jk...@gmail.com> wrote:
>
> Ah...Ok. Thanks for the additional info.
>
> I think the new spec resource type change is here to stay, so it's
just
> matter of cleaning up whatever pieces used to work the old way. The
overall
> result being that Tapestry no longer ignores classpath resources
(except for
> assets / things it has always handled) in a way that makes any
resource
> resolution done globally work whether people stick things in the
classpath /
> context / mixture of the two.
>
> On 5/7/07, Ben Dotte <bd...@widen.com> wrote:
> >
> > Fair enough, it has to do with the way we handle client-specific
> > functionality. Eclipse copies everything, templates, .class files,
and
> > .properties files to the classpath that Jetty uses (for local
> > deployments). We have a separate process that builds the context for
us
> > that includes client-specific overrides of the templates and
.properties
> > files. So, one client might have a different version of
AssetEdit.html
> > than the default AssetEdit.html, for example, and we want that
> > client-specific version to get displayed. This is why it was a
problem
> > for us that Tapestry tried to search the classpath for templates
first
> > before checking the context.
> >
> > I realize this is very specific to our setup but since Tapestry used
to
> > check the context first for templates and .properties files anyway
it
> > hasn't been a problem up until these changes started taking place.
> >
> > -----Original Message-----
> > From: Jesse Kuhnert [mailto:jkuhnert@gmail.com]
> > Sent: Monday, May 07, 2007 5:10 PM
> > To: Tapestry users
> > Subject: Re: 4.1.2 snapshot changes 4-20 to 4-30
> >
> > Right....I get that it's looking in the classpath first - but why is
> > that a
> > problem ?
> >
> > On 5/7/07, Ben Dotte < bdotte@widen.com> wrote:
> > >
> > > As an example, we have a component
> > > collective.md.ui.components.AssetEdit. For the NLS keys on that
> > > component, we want Tapestry to look for AssetEdit.properties under
the
> > > context root/WEB-INF/app before it looks under the class path
> > > root/collective/md/ui/components. This is the behavior Tapestry
used
> > to
> > > have but now it looks on the classpath first.
> > >
> > > Thanks for taking a look.
> > >
> > > -----Original Message-----
> > > From: Jesse Kuhnert [mailto:jkuhnert@gmail.com]
> > > Sent: Monday, May 07, 2007 4:51 PM
> > > To: Tapestry users
> > > Subject: Re: 4.1.2 snapshot changes 4-20 to 4-30
> > >
> > > It's fine, report things as much as you like. Spec resolution
logic
> > has
> > > changed so it makes sense that there are side effects.
> > >
> > > What is the exact problem (expected vs. actual) happening now? I
know
> > > generally what you mean but properties get resolved by a
completely
> > > different service so the patterns are different.
> > >
> > > On 5/7/07, Ben Dotte <bd...@widen.com> wrote:
> > > >
> > > > Our templates are still getting resolved on WEB-INF/app just
fine,
> > but
> > > I
> > > > just found out we have a problem with NLS .properties files
getting
> > > > resolved that is the same as the template resolution problem.
> > > >
> > > > So it looks like Tapestry is now looking on the classpath first
for
> > > > .properties files whereas it used to look on the context first
> > > > (specifically for us this would also be WEB-INF/app). Would it
be
> > > > possible to change this back to look at the context first like
it
> > used
> > > > to?
> > > >
> > > > Sorry to bother with this yet again!
> > > >
> > > > Thanks,
> > > > Ben
> > > >
> > > >
> > > >
> > >
> > >
> > > --
> > > Jesse Kuhnert
> > > Tapestry/Dojo team member/developer
> > >
> > > Open source based consulting work centered around
> > > dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
> > >
> > >
---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > > For additional commands, e-mail: users-help@tapestry.apache.org
> > >
> > >
> >
> >
> > --
> > Jesse Kuhnert
> > Tapestry/Dojo team member/developer
> >
> > Open source based consulting work centered around
> > dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
> >
> >
---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: users-help@tapestry.apache.org
> >
> >
>
>
> --
> Jesse Kuhnert
> Tapestry/Dojo team member/developer
>
> Open source based consulting work centered around
> dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
>
--
Jesse Kuhnert
Tapestry/Dojo team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: 4.1.2 snapshot changes 4-20 to 4-30
Posted by Jesse Kuhnert <jk...@gmail.com>.
I hope that app of yours is huge and unwieldy. ;)
there may be a fix out now.....I won't be using my "heavy dev" computer
tomorrow so if there's a problem starting tomorrow it won't be resolvable
until at least tomorrow night..
On 5/7/07, Jesse Kuhnert <jk...@gmail.com> wrote:
>
> Ah...Ok. Thanks for the additional info.
>
> I think the new spec resource type change is here to stay, so it's just
> matter of cleaning up whatever pieces used to work the old way. The overall
> result being that Tapestry no longer ignores classpath resources (except for
> assets / things it has always handled) in a way that makes any resource
> resolution done globally work whether people stick things in the classpath /
> context / mixture of the two.
>
> On 5/7/07, Ben Dotte <bd...@widen.com> wrote:
> >
> > Fair enough, it has to do with the way we handle client-specific
> > functionality. Eclipse copies everything, templates, .class files, and
> > .properties files to the classpath that Jetty uses (for local
> > deployments). We have a separate process that builds the context for us
> > that includes client-specific overrides of the templates and .properties
> > files. So, one client might have a different version of AssetEdit.html
> > than the default AssetEdit.html, for example, and we want that
> > client-specific version to get displayed. This is why it was a problem
> > for us that Tapestry tried to search the classpath for templates first
> > before checking the context.
> >
> > I realize this is very specific to our setup but since Tapestry used to
> > check the context first for templates and .properties files anyway it
> > hasn't been a problem up until these changes started taking place.
> >
> > -----Original Message-----
> > From: Jesse Kuhnert [mailto:jkuhnert@gmail.com]
> > Sent: Monday, May 07, 2007 5:10 PM
> > To: Tapestry users
> > Subject: Re: 4.1.2 snapshot changes 4-20 to 4-30
> >
> > Right....I get that it's looking in the classpath first - but why is
> > that a
> > problem ?
> >
> > On 5/7/07, Ben Dotte < bdotte@widen.com> wrote:
> > >
> > > As an example, we have a component
> > > collective.md.ui.components.AssetEdit. For the NLS keys on that
> > > component, we want Tapestry to look for AssetEdit.properties under the
> > > context root/WEB-INF/app before it looks under the class path
> > > root/collective/md/ui/components. This is the behavior Tapestry used
> > to
> > > have but now it looks on the classpath first.
> > >
> > > Thanks for taking a look.
> > >
> > > -----Original Message-----
> > > From: Jesse Kuhnert [mailto:jkuhnert@gmail.com]
> > > Sent: Monday, May 07, 2007 4:51 PM
> > > To: Tapestry users
> > > Subject: Re: 4.1.2 snapshot changes 4-20 to 4-30
> > >
> > > It's fine, report things as much as you like. Spec resolution logic
> > has
> > > changed so it makes sense that there are side effects.
> > >
> > > What is the exact problem (expected vs. actual) happening now? I know
> > > generally what you mean but properties get resolved by a completely
> > > different service so the patterns are different.
> > >
> > > On 5/7/07, Ben Dotte <bd...@widen.com> wrote:
> > > >
> > > > Our templates are still getting resolved on WEB-INF/app just fine,
> > but
> > > I
> > > > just found out we have a problem with NLS .properties files getting
> > > > resolved that is the same as the template resolution problem.
> > > >
> > > > So it looks like Tapestry is now looking on the classpath first for
> > > > .properties files whereas it used to look on the context first
> > > > (specifically for us this would also be WEB-INF/app). Would it be
> > > > possible to change this back to look at the context first like it
> > used
> > > > to?
> > > >
> > > > Sorry to bother with this yet again!
> > > >
> > > > Thanks,
> > > > Ben
> > > >
> > > >
> > > >
> > >
> > >
> > > --
> > > Jesse Kuhnert
> > > Tapestry/Dojo team member/developer
> > >
> > > Open source based consulting work centered around
> > > dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > > For additional commands, e-mail: users-help@tapestry.apache.org
> > >
> > >
> >
> >
> > --
> > Jesse Kuhnert
> > Tapestry/Dojo team member/developer
> >
> > Open source based consulting work centered around
> > dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: users-help@tapestry.apache.org
> >
> >
>
>
> --
> Jesse Kuhnert
> Tapestry/Dojo team member/developer
>
> Open source based consulting work centered around
> dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
>
--
Jesse Kuhnert
Tapestry/Dojo team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
Re: 4.1.2 snapshot changes 4-20 to 4-30
Posted by Jesse Kuhnert <jk...@gmail.com>.
Ah...Ok. Thanks for the additional info.
I think the new spec resource type change is here to stay, so it's just
matter of cleaning up whatever pieces used to work the old way. The overall
result being that Tapestry no longer ignores classpath resources (except for
assets / things it has always handled) in a way that makes any resource
resolution done globally work whether people stick things in the classpath /
context / mixture of the two.
On 5/7/07, Ben Dotte <bd...@widen.com> wrote:
>
> Fair enough, it has to do with the way we handle client-specific
> functionality. Eclipse copies everything, templates, .class files, and
> .properties files to the classpath that Jetty uses (for local
> deployments). We have a separate process that builds the context for us
> that includes client-specific overrides of the templates and .properties
> files. So, one client might have a different version of AssetEdit.html
> than the default AssetEdit.html, for example, and we want that
> client-specific version to get displayed. This is why it was a problem
> for us that Tapestry tried to search the classpath for templates first
> before checking the context.
>
> I realize this is very specific to our setup but since Tapestry used to
> check the context first for templates and .properties files anyway it
> hasn't been a problem up until these changes started taking place.
>
> -----Original Message-----
> From: Jesse Kuhnert [mailto:jkuhnert@gmail.com]
> Sent: Monday, May 07, 2007 5:10 PM
> To: Tapestry users
> Subject: Re: 4.1.2 snapshot changes 4-20 to 4-30
>
> Right....I get that it's looking in the classpath first - but why is
> that a
> problem ?
>
> On 5/7/07, Ben Dotte <bd...@widen.com> wrote:
> >
> > As an example, we have a component
> > collective.md.ui.components.AssetEdit. For the NLS keys on that
> > component, we want Tapestry to look for AssetEdit.properties under the
> > context root/WEB-INF/app before it looks under the class path
> > root/collective/md/ui/components. This is the behavior Tapestry used
> to
> > have but now it looks on the classpath first.
> >
> > Thanks for taking a look.
> >
> > -----Original Message-----
> > From: Jesse Kuhnert [mailto:jkuhnert@gmail.com]
> > Sent: Monday, May 07, 2007 4:51 PM
> > To: Tapestry users
> > Subject: Re: 4.1.2 snapshot changes 4-20 to 4-30
> >
> > It's fine, report things as much as you like. Spec resolution logic
> has
> > changed so it makes sense that there are side effects.
> >
> > What is the exact problem (expected vs. actual) happening now? I know
> > generally what you mean but properties get resolved by a completely
> > different service so the patterns are different.
> >
> > On 5/7/07, Ben Dotte <bd...@widen.com> wrote:
> > >
> > > Our templates are still getting resolved on WEB-INF/app just fine,
> but
> > I
> > > just found out we have a problem with NLS .properties files getting
> > > resolved that is the same as the template resolution problem.
> > >
> > > So it looks like Tapestry is now looking on the classpath first for
> > > .properties files whereas it used to look on the context first
> > > (specifically for us this would also be WEB-INF/app). Would it be
> > > possible to change this back to look at the context first like it
> used
> > > to?
> > >
> > > Sorry to bother with this yet again!
> > >
> > > Thanks,
> > > Ben
> > >
> > >
> > >
> >
> >
> > --
> > Jesse Kuhnert
> > Tapestry/Dojo team member/developer
> >
> > Open source based consulting work centered around
> > dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: users-help@tapestry.apache.org
> >
> >
>
>
> --
> Jesse Kuhnert
> Tapestry/Dojo team member/developer
>
> Open source based consulting work centered around
> dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
--
Jesse Kuhnert
Tapestry/Dojo team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
RE: 4.1.2 snapshot changes 4-20 to 4-30
Posted by Ben Dotte <bd...@widen.com>.
Fair enough, it has to do with the way we handle client-specific
functionality. Eclipse copies everything, templates, .class files, and
.properties files to the classpath that Jetty uses (for local
deployments). We have a separate process that builds the context for us
that includes client-specific overrides of the templates and .properties
files. So, one client might have a different version of AssetEdit.html
than the default AssetEdit.html, for example, and we want that
client-specific version to get displayed. This is why it was a problem
for us that Tapestry tried to search the classpath for templates first
before checking the context.
I realize this is very specific to our setup but since Tapestry used to
check the context first for templates and .properties files anyway it
hasn't been a problem up until these changes started taking place.
-----Original Message-----
From: Jesse Kuhnert [mailto:jkuhnert@gmail.com]
Sent: Monday, May 07, 2007 5:10 PM
To: Tapestry users
Subject: Re: 4.1.2 snapshot changes 4-20 to 4-30
Right....I get that it's looking in the classpath first - but why is
that a
problem ?
On 5/7/07, Ben Dotte <bd...@widen.com> wrote:
>
> As an example, we have a component
> collective.md.ui.components.AssetEdit. For the NLS keys on that
> component, we want Tapestry to look for AssetEdit.properties under the
> context root/WEB-INF/app before it looks under the class path
> root/collective/md/ui/components. This is the behavior Tapestry used
to
> have but now it looks on the classpath first.
>
> Thanks for taking a look.
>
> -----Original Message-----
> From: Jesse Kuhnert [mailto:jkuhnert@gmail.com]
> Sent: Monday, May 07, 2007 4:51 PM
> To: Tapestry users
> Subject: Re: 4.1.2 snapshot changes 4-20 to 4-30
>
> It's fine, report things as much as you like. Spec resolution logic
has
> changed so it makes sense that there are side effects.
>
> What is the exact problem (expected vs. actual) happening now? I know
> generally what you mean but properties get resolved by a completely
> different service so the patterns are different.
>
> On 5/7/07, Ben Dotte <bd...@widen.com> wrote:
> >
> > Our templates are still getting resolved on WEB-INF/app just fine,
but
> I
> > just found out we have a problem with NLS .properties files getting
> > resolved that is the same as the template resolution problem.
> >
> > So it looks like Tapestry is now looking on the classpath first for
> > .properties files whereas it used to look on the context first
> > (specifically for us this would also be WEB-INF/app). Would it be
> > possible to change this back to look at the context first like it
used
> > to?
> >
> > Sorry to bother with this yet again!
> >
> > Thanks,
> > Ben
> >
> >
> >
>
>
> --
> Jesse Kuhnert
> Tapestry/Dojo team member/developer
>
> Open source based consulting work centered around
> dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
--
Jesse Kuhnert
Tapestry/Dojo team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: 4.1.2 snapshot changes 4-20 to 4-30
Posted by Jesse Kuhnert <jk...@gmail.com>.
Right....I get that it's looking in the classpath first - but why is that a
problem ?
On 5/7/07, Ben Dotte <bd...@widen.com> wrote:
>
> As an example, we have a component
> collective.md.ui.components.AssetEdit. For the NLS keys on that
> component, we want Tapestry to look for AssetEdit.properties under the
> context root/WEB-INF/app before it looks under the class path
> root/collective/md/ui/components. This is the behavior Tapestry used to
> have but now it looks on the classpath first.
>
> Thanks for taking a look.
>
> -----Original Message-----
> From: Jesse Kuhnert [mailto:jkuhnert@gmail.com]
> Sent: Monday, May 07, 2007 4:51 PM
> To: Tapestry users
> Subject: Re: 4.1.2 snapshot changes 4-20 to 4-30
>
> It's fine, report things as much as you like. Spec resolution logic has
> changed so it makes sense that there are side effects.
>
> What is the exact problem (expected vs. actual) happening now? I know
> generally what you mean but properties get resolved by a completely
> different service so the patterns are different.
>
> On 5/7/07, Ben Dotte <bd...@widen.com> wrote:
> >
> > Our templates are still getting resolved on WEB-INF/app just fine, but
> I
> > just found out we have a problem with NLS .properties files getting
> > resolved that is the same as the template resolution problem.
> >
> > So it looks like Tapestry is now looking on the classpath first for
> > .properties files whereas it used to look on the context first
> > (specifically for us this would also be WEB-INF/app). Would it be
> > possible to change this back to look at the context first like it used
> > to?
> >
> > Sorry to bother with this yet again!
> >
> > Thanks,
> > Ben
> >
> >
> >
>
>
> --
> Jesse Kuhnert
> Tapestry/Dojo team member/developer
>
> Open source based consulting work centered around
> dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
--
Jesse Kuhnert
Tapestry/Dojo team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
RE: 4.1.2 snapshot changes 4-20 to 4-30
Posted by Ben Dotte <bd...@widen.com>.
As an example, we have a component
collective.md.ui.components.AssetEdit. For the NLS keys on that
component, we want Tapestry to look for AssetEdit.properties under the
context root/WEB-INF/app before it looks under the class path
root/collective/md/ui/components. This is the behavior Tapestry used to
have but now it looks on the classpath first.
Thanks for taking a look.
-----Original Message-----
From: Jesse Kuhnert [mailto:jkuhnert@gmail.com]
Sent: Monday, May 07, 2007 4:51 PM
To: Tapestry users
Subject: Re: 4.1.2 snapshot changes 4-20 to 4-30
It's fine, report things as much as you like. Spec resolution logic has
changed so it makes sense that there are side effects.
What is the exact problem (expected vs. actual) happening now? I know
generally what you mean but properties get resolved by a completely
different service so the patterns are different.
On 5/7/07, Ben Dotte <bd...@widen.com> wrote:
>
> Our templates are still getting resolved on WEB-INF/app just fine, but
I
> just found out we have a problem with NLS .properties files getting
> resolved that is the same as the template resolution problem.
>
> So it looks like Tapestry is now looking on the classpath first for
> .properties files whereas it used to look on the context first
> (specifically for us this would also be WEB-INF/app). Would it be
> possible to change this back to look at the context first like it used
> to?
>
> Sorry to bother with this yet again!
>
> Thanks,
> Ben
>
>
>
--
Jesse Kuhnert
Tapestry/Dojo team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: 4.1.2 snapshot changes 4-20 to 4-30
Posted by Jesse Kuhnert <jk...@gmail.com>.
It's fine, report things as much as you like. Spec resolution logic has
changed so it makes sense that there are side effects.
What is the exact problem (expected vs. actual) happening now? I know
generally what you mean but properties get resolved by a completely
different service so the patterns are different.
On 5/7/07, Ben Dotte <bd...@widen.com> wrote:
>
> Our templates are still getting resolved on WEB-INF/app just fine, but I
> just found out we have a problem with NLS .properties files getting
> resolved that is the same as the template resolution problem.
>
> So it looks like Tapestry is now looking on the classpath first for
> .properties files whereas it used to look on the context first
> (specifically for us this would also be WEB-INF/app). Would it be
> possible to change this back to look at the context first like it used
> to?
>
> Sorry to bother with this yet again!
>
> Thanks,
> Ben
>
>
>
--
Jesse Kuhnert
Tapestry/Dojo team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
RE: 4.1.2 snapshot changes 4-20 to 4-30
Posted by Ben Dotte <bd...@widen.com>.
Our templates are still getting resolved on WEB-INF/app just fine, but I
just found out we have a problem with NLS .properties files getting
resolved that is the same as the template resolution problem.
So it looks like Tapestry is now looking on the classpath first for
.properties files whereas it used to look on the context first
(specifically for us this would also be WEB-INF/app). Would it be
possible to change this back to look at the context first like it used
to?
Sorry to bother with this yet again!
Thanks,
Ben
-----Original Message-----
From: Ben Dotte [mailto:bdotte@widen.com]
Sent: Thursday, May 03, 2007 3:01 PM
To: Tapestry users
Subject: RE: 4.1.2 snapshot changes 4-20 to 4-30
Ok, I hate to bring this up yet again but things still aren't working
the way they need to. Tapestry used to search the context for the
templates first, then it searched the classpath. Now it searches the
classpath first. Our templates technically get output to both places,
but the ones we need Tapestry to use are in WEB-INF/app. So I changed
our build process to no longer output templates to the classpath so it
would be forced to go to the context. Now pages render just fine from
the context but we get a huge pile of stack traces to the console as
documented on this case:
http://issues.apache.org/jira/browse/TAPESTRY-1437
If Tapestry just looked at the context first like it used to, everything
would work fine for us. Alternately, these stack traces really need to
be suppressed. I am talking 15,000 lines of stack traces just to get to
our home page. Ouch.
Thanks,
Ben
-----Original Message-----
From: Jesse Kuhnert [mailto:jkuhnert@gmail.com]
Sent: Thursday, May 03, 2007 1:37 PM
To: Tapestry users
Subject: Re: 4.1.2 snapshot changes 4-20 to 4-30
Sheww....Finally :)
Yeah I don't think the classpath search is going to be the most typical
type
either so it doesn't make sense to take the perf hit on resolving them
for
that. I'm not nearly done with these changes though ......Need to
re-factor
things so that only one service/object has knowledge of all the various
places to search / how / etc..
On 5/3/07, Ben Dotte <bd...@widen.com> wrote:
>
> Cool, it seems to be finding the component templates again like it
used
> to. The only difference is it used to search on the context first,
then
> the classpath.. but I'm not going to split hairs, works plenty good
for
> me.
>
> Thanks Jesse!
>
> -----Original Message-----
> From: Jesse Kuhnert [mailto:jkuhnert@gmail.com]
> Sent: Thursday, May 03, 2007 12:23 PM
> To: Tapestry users
> Subject: Re: 4.1.2 snapshot changes 4-20 to 4-30
>
> Ok that's making more sense now. I've made some changes and can no
> longer
> find any combination that breaks it. What a pita .....It should now
find
> them in
>
> -) classpath relative to component class
> -) relative to context root
> -) relative to context + WEB-INF root
> -) relative to context + WEB-INF + app name root
>
> Jar should be deployed by the time you read this email.
>
> On 5/3/07, Ben Dotte <bd...@widen.com> wrote:
> >
> > Yes, so an example would be WEB-INF/app/About.html. I'm a little
fuzzy
> > on the historical reason for this but it has certainly been a valid
> > choice since Tapestry 3 at least. I noticed
> > AbstractSpecificationResolver.java has two different methods,
> > getWebInfLocation() and getWebInfAppLocation(), the latter of which
is
> > documented with "Returns the location of the application-specific
> > subdirectory, under /WEB-INF/, in the servlet context."
> >
> > So presumably for us that application-specific subdirectory is app.
> > Perhaps that is because the <servlet-name> is defined as "app" for
us
> in
> > web.xml but I'm not 100% sure where that is coming from.
> >
> > Yes, our .application file is also in that directory.
> >
> > -----Original Message-----
> > From: Jesse Kuhnert [mailto:jkuhnert@gmail.com]
> > Sent: Thursday, May 03, 2007 11:41 AM
> > To: Tapestry users
> > Subject: Re: 4.1.2 snapshot changes 4-20 to 4-30
> >
> > Where/how does the "app" part come in? Is there literally a
directory
> > called
> > "app" where you have stuff, and if so is your .application file
there
> as
> > well?
> >
> > On 5/3/07, Ben Dotte <bd...@widen.com> wrote:
> > >
> > > The issue where component templates cannot be found in WEB-INF/app
> for
> > > specless apps. Yes, Marcus mentioned the same problem on
> TAPESTRY-1396
> > > yesterday. And yes, it is still a problem with the snapshot that
> just
> > > went out (tapestry-framework-4.1.2-20070503.160951-67.jar).
> > >
> > > To recreate, just put a component template with no spec under
> > > WEB-INF/app and Tapestry will be unable to find it on any of the
> > > post-4-30 snapshots.
> > >
> > > -----Original Message-----
> > > From: Jesse Kuhnert [mailto:jkuhnert@gmail.com]
> > > Sent: Thursday, May 03, 2007 11:13 AM
> > > To: Tapestry users
> > > Subject: Re: 4.1.2 snapshot changes 4-20 to 4-30
> > >
> > > Which issue is still a problem? Is it anything discussed in
> > > https://issues.apache.org/jira/browse/TAPESTRY-1396 ?
> > >
> > > Perhaps your failure is slightly different ? I may need more
> specific
> > > information (to re-create) . ...Either way an update just went out
a
> > few
> > > seconds ago. Maybe that fixed it.
> > >
> > > On 5/3/07, Ben Dotte <bd...@widen.com> wrote:
> > > >
> > > > It appears this is still a problem, even with the newest
snapshot
> > > > (tapestry-framework-4.1.2-20070503.050340-66.jar)
> > > > <snipped>
> > > >
> > >
> > >
> > >
> > > --
> > > Jesse Kuhnert
> > > Tapestry/Dojo team member/developer
> > >
> > > Open source based consulting work centered around
> > > dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
> > >
> > >
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > > For additional commands, e-mail: users-help@tapestry.apache.org
> > >
> > >
> >
> >
> > --
> > Jesse Kuhnert
> > Tapestry/Dojo team member/developer
> >
> > Open source based consulting work centered around
> > dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
> >
> >
---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: users-help@tapestry.apache.org
> >
> >
>
>
> --
> Jesse Kuhnert
> Tapestry/Dojo team member/developer
>
> Open source based consulting work centered around
> dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
--
Jesse Kuhnert
Tapestry/Dojo team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
RE: 4.1.2 snapshot changes 4-20 to 4-30
Posted by Ben Dotte <bd...@widen.com>.
Ok, I hate to bring this up yet again but things still aren't working
the way they need to. Tapestry used to search the context for the
templates first, then it searched the classpath. Now it searches the
classpath first. Our templates technically get output to both places,
but the ones we need Tapestry to use are in WEB-INF/app. So I changed
our build process to no longer output templates to the classpath so it
would be forced to go to the context. Now pages render just fine from
the context but we get a huge pile of stack traces to the console as
documented on this case:
http://issues.apache.org/jira/browse/TAPESTRY-1437
If Tapestry just looked at the context first like it used to, everything
would work fine for us. Alternately, these stack traces really need to
be suppressed. I am talking 15,000 lines of stack traces just to get to
our home page. Ouch.
Thanks,
Ben
-----Original Message-----
From: Jesse Kuhnert [mailto:jkuhnert@gmail.com]
Sent: Thursday, May 03, 2007 1:37 PM
To: Tapestry users
Subject: Re: 4.1.2 snapshot changes 4-20 to 4-30
Sheww....Finally :)
Yeah I don't think the classpath search is going to be the most typical
type
either so it doesn't make sense to take the perf hit on resolving them
for
that. I'm not nearly done with these changes though ......Need to
re-factor
things so that only one service/object has knowledge of all the various
places to search / how / etc..
On 5/3/07, Ben Dotte <bd...@widen.com> wrote:
>
> Cool, it seems to be finding the component templates again like it
used
> to. The only difference is it used to search on the context first,
then
> the classpath.. but I'm not going to split hairs, works plenty good
for
> me.
>
> Thanks Jesse!
>
> -----Original Message-----
> From: Jesse Kuhnert [mailto:jkuhnert@gmail.com]
> Sent: Thursday, May 03, 2007 12:23 PM
> To: Tapestry users
> Subject: Re: 4.1.2 snapshot changes 4-20 to 4-30
>
> Ok that's making more sense now. I've made some changes and can no
> longer
> find any combination that breaks it. What a pita .....It should now
find
> them in
>
> -) classpath relative to component class
> -) relative to context root
> -) relative to context + WEB-INF root
> -) relative to context + WEB-INF + app name root
>
> Jar should be deployed by the time you read this email.
>
> On 5/3/07, Ben Dotte <bd...@widen.com> wrote:
> >
> > Yes, so an example would be WEB-INF/app/About.html. I'm a little
fuzzy
> > on the historical reason for this but it has certainly been a valid
> > choice since Tapestry 3 at least. I noticed
> > AbstractSpecificationResolver.java has two different methods,
> > getWebInfLocation() and getWebInfAppLocation(), the latter of which
is
> > documented with "Returns the location of the application-specific
> > subdirectory, under /WEB-INF/, in the servlet context."
> >
> > So presumably for us that application-specific subdirectory is app.
> > Perhaps that is because the <servlet-name> is defined as "app" for
us
> in
> > web.xml but I'm not 100% sure where that is coming from.
> >
> > Yes, our .application file is also in that directory.
> >
> > -----Original Message-----
> > From: Jesse Kuhnert [mailto:jkuhnert@gmail.com]
> > Sent: Thursday, May 03, 2007 11:41 AM
> > To: Tapestry users
> > Subject: Re: 4.1.2 snapshot changes 4-20 to 4-30
> >
> > Where/how does the "app" part come in? Is there literally a
directory
> > called
> > "app" where you have stuff, and if so is your .application file
there
> as
> > well?
> >
> > On 5/3/07, Ben Dotte <bd...@widen.com> wrote:
> > >
> > > The issue where component templates cannot be found in WEB-INF/app
> for
> > > specless apps. Yes, Marcus mentioned the same problem on
> TAPESTRY-1396
> > > yesterday. And yes, it is still a problem with the snapshot that
> just
> > > went out (tapestry-framework-4.1.2-20070503.160951-67.jar).
> > >
> > > To recreate, just put a component template with no spec under
> > > WEB-INF/app and Tapestry will be unable to find it on any of the
> > > post-4-30 snapshots.
> > >
> > > -----Original Message-----
> > > From: Jesse Kuhnert [mailto:jkuhnert@gmail.com]
> > > Sent: Thursday, May 03, 2007 11:13 AM
> > > To: Tapestry users
> > > Subject: Re: 4.1.2 snapshot changes 4-20 to 4-30
> > >
> > > Which issue is still a problem? Is it anything discussed in
> > > https://issues.apache.org/jira/browse/TAPESTRY-1396 ?
> > >
> > > Perhaps your failure is slightly different ? I may need more
> specific
> > > information (to re-create) . ...Either way an update just went out
a
> > few
> > > seconds ago. Maybe that fixed it.
> > >
> > > On 5/3/07, Ben Dotte <bd...@widen.com> wrote:
> > > >
> > > > It appears this is still a problem, even with the newest
snapshot
> > > > (tapestry-framework-4.1.2-20070503.050340-66.jar)
> > > > <snipped>
> > > >
> > >
> > >
> > >
> > > --
> > > Jesse Kuhnert
> > > Tapestry/Dojo team member/developer
> > >
> > > Open source based consulting work centered around
> > > dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
> > >
> > >
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > > For additional commands, e-mail: users-help@tapestry.apache.org
> > >
> > >
> >
> >
> > --
> > Jesse Kuhnert
> > Tapestry/Dojo team member/developer
> >
> > Open source based consulting work centered around
> > dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
> >
> >
---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: users-help@tapestry.apache.org
> >
> >
>
>
> --
> Jesse Kuhnert
> Tapestry/Dojo team member/developer
>
> Open source based consulting work centered around
> dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
--
Jesse Kuhnert
Tapestry/Dojo team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: 4.1.2 snapshot changes 4-20 to 4-30
Posted by Jesse Kuhnert <jk...@gmail.com>.
Sheww....Finally :)
Yeah I don't think the classpath search is going to be the most typical type
either so it doesn't make sense to take the perf hit on resolving them for
that. I'm not nearly done with these changes though ......Need to re-factor
things so that only one service/object has knowledge of all the various
places to search / how / etc..
On 5/3/07, Ben Dotte <bd...@widen.com> wrote:
>
> Cool, it seems to be finding the component templates again like it used
> to. The only difference is it used to search on the context first, then
> the classpath.. but I'm not going to split hairs, works plenty good for
> me.
>
> Thanks Jesse!
>
> -----Original Message-----
> From: Jesse Kuhnert [mailto:jkuhnert@gmail.com]
> Sent: Thursday, May 03, 2007 12:23 PM
> To: Tapestry users
> Subject: Re: 4.1.2 snapshot changes 4-20 to 4-30
>
> Ok that's making more sense now. I've made some changes and can no
> longer
> find any combination that breaks it. What a pita .....It should now find
> them in
>
> -) classpath relative to component class
> -) relative to context root
> -) relative to context + WEB-INF root
> -) relative to context + WEB-INF + app name root
>
> Jar should be deployed by the time you read this email.
>
> On 5/3/07, Ben Dotte <bd...@widen.com> wrote:
> >
> > Yes, so an example would be WEB-INF/app/About.html. I'm a little fuzzy
> > on the historical reason for this but it has certainly been a valid
> > choice since Tapestry 3 at least. I noticed
> > AbstractSpecificationResolver.java has two different methods,
> > getWebInfLocation() and getWebInfAppLocation(), the latter of which is
> > documented with "Returns the location of the application-specific
> > subdirectory, under /WEB-INF/, in the servlet context."
> >
> > So presumably for us that application-specific subdirectory is app.
> > Perhaps that is because the <servlet-name> is defined as "app" for us
> in
> > web.xml but I'm not 100% sure where that is coming from.
> >
> > Yes, our .application file is also in that directory.
> >
> > -----Original Message-----
> > From: Jesse Kuhnert [mailto:jkuhnert@gmail.com]
> > Sent: Thursday, May 03, 2007 11:41 AM
> > To: Tapestry users
> > Subject: Re: 4.1.2 snapshot changes 4-20 to 4-30
> >
> > Where/how does the "app" part come in? Is there literally a directory
> > called
> > "app" where you have stuff, and if so is your .application file there
> as
> > well?
> >
> > On 5/3/07, Ben Dotte <bd...@widen.com> wrote:
> > >
> > > The issue where component templates cannot be found in WEB-INF/app
> for
> > > specless apps. Yes, Marcus mentioned the same problem on
> TAPESTRY-1396
> > > yesterday. And yes, it is still a problem with the snapshot that
> just
> > > went out (tapestry-framework-4.1.2-20070503.160951-67.jar).
> > >
> > > To recreate, just put a component template with no spec under
> > > WEB-INF/app and Tapestry will be unable to find it on any of the
> > > post-4-30 snapshots.
> > >
> > > -----Original Message-----
> > > From: Jesse Kuhnert [mailto:jkuhnert@gmail.com]
> > > Sent: Thursday, May 03, 2007 11:13 AM
> > > To: Tapestry users
> > > Subject: Re: 4.1.2 snapshot changes 4-20 to 4-30
> > >
> > > Which issue is still a problem? Is it anything discussed in
> > > https://issues.apache.org/jira/browse/TAPESTRY-1396 ?
> > >
> > > Perhaps your failure is slightly different ? I may need more
> specific
> > > information (to re-create) . ...Either way an update just went out a
> > few
> > > seconds ago. Maybe that fixed it.
> > >
> > > On 5/3/07, Ben Dotte <bd...@widen.com> wrote:
> > > >
> > > > It appears this is still a problem, even with the newest snapshot
> > > > (tapestry-framework-4.1.2-20070503.050340-66.jar)
> > > > <snipped>
> > > >
> > >
> > >
> > >
> > > --
> > > Jesse Kuhnert
> > > Tapestry/Dojo team member/developer
> > >
> > > Open source based consulting work centered around
> > > dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
> > >
> > >
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > > For additional commands, e-mail: users-help@tapestry.apache.org
> > >
> > >
> >
> >
> > --
> > Jesse Kuhnert
> > Tapestry/Dojo team member/developer
> >
> > Open source based consulting work centered around
> > dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: users-help@tapestry.apache.org
> >
> >
>
>
> --
> Jesse Kuhnert
> Tapestry/Dojo team member/developer
>
> Open source based consulting work centered around
> dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
--
Jesse Kuhnert
Tapestry/Dojo team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
RE: 4.1.2 snapshot changes 4-20 to 4-30
Posted by Ben Dotte <bd...@widen.com>.
Cool, it seems to be finding the component templates again like it used
to. The only difference is it used to search on the context first, then
the classpath.. but I'm not going to split hairs, works plenty good for
me.
Thanks Jesse!
-----Original Message-----
From: Jesse Kuhnert [mailto:jkuhnert@gmail.com]
Sent: Thursday, May 03, 2007 12:23 PM
To: Tapestry users
Subject: Re: 4.1.2 snapshot changes 4-20 to 4-30
Ok that's making more sense now. I've made some changes and can no
longer
find any combination that breaks it. What a pita .....It should now find
them in
-) classpath relative to component class
-) relative to context root
-) relative to context + WEB-INF root
-) relative to context + WEB-INF + app name root
Jar should be deployed by the time you read this email.
On 5/3/07, Ben Dotte <bd...@widen.com> wrote:
>
> Yes, so an example would be WEB-INF/app/About.html. I'm a little fuzzy
> on the historical reason for this but it has certainly been a valid
> choice since Tapestry 3 at least. I noticed
> AbstractSpecificationResolver.java has two different methods,
> getWebInfLocation() and getWebInfAppLocation(), the latter of which is
> documented with "Returns the location of the application-specific
> subdirectory, under /WEB-INF/, in the servlet context."
>
> So presumably for us that application-specific subdirectory is app.
> Perhaps that is because the <servlet-name> is defined as "app" for us
in
> web.xml but I'm not 100% sure where that is coming from.
>
> Yes, our .application file is also in that directory.
>
> -----Original Message-----
> From: Jesse Kuhnert [mailto:jkuhnert@gmail.com]
> Sent: Thursday, May 03, 2007 11:41 AM
> To: Tapestry users
> Subject: Re: 4.1.2 snapshot changes 4-20 to 4-30
>
> Where/how does the "app" part come in? Is there literally a directory
> called
> "app" where you have stuff, and if so is your .application file there
as
> well?
>
> On 5/3/07, Ben Dotte <bd...@widen.com> wrote:
> >
> > The issue where component templates cannot be found in WEB-INF/app
for
> > specless apps. Yes, Marcus mentioned the same problem on
TAPESTRY-1396
> > yesterday. And yes, it is still a problem with the snapshot that
just
> > went out (tapestry-framework-4.1.2-20070503.160951-67.jar).
> >
> > To recreate, just put a component template with no spec under
> > WEB-INF/app and Tapestry will be unable to find it on any of the
> > post-4-30 snapshots.
> >
> > -----Original Message-----
> > From: Jesse Kuhnert [mailto:jkuhnert@gmail.com]
> > Sent: Thursday, May 03, 2007 11:13 AM
> > To: Tapestry users
> > Subject: Re: 4.1.2 snapshot changes 4-20 to 4-30
> >
> > Which issue is still a problem? Is it anything discussed in
> > https://issues.apache.org/jira/browse/TAPESTRY-1396 ?
> >
> > Perhaps your failure is slightly different ? I may need more
specific
> > information (to re-create) . ...Either way an update just went out a
> few
> > seconds ago. Maybe that fixed it.
> >
> > On 5/3/07, Ben Dotte <bd...@widen.com> wrote:
> > >
> > > It appears this is still a problem, even with the newest snapshot
> > > (tapestry-framework-4.1.2-20070503.050340-66.jar)
> > > <snipped>
> > >
> >
> >
> >
> > --
> > Jesse Kuhnert
> > Tapestry/Dojo team member/developer
> >
> > Open source based consulting work centered around
> > dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
> >
> >
---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: users-help@tapestry.apache.org
> >
> >
>
>
> --
> Jesse Kuhnert
> Tapestry/Dojo team member/developer
>
> Open source based consulting work centered around
> dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
--
Jesse Kuhnert
Tapestry/Dojo team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: 4.1.2 snapshot changes 4-20 to 4-30
Posted by Jesse Kuhnert <jk...@gmail.com>.
Ok that's making more sense now. I've made some changes and can no longer
find any combination that breaks it. What a pita .....It should now find
them in
-) classpath relative to component class
-) relative to context root
-) relative to context + WEB-INF root
-) relative to context + WEB-INF + app name root
Jar should be deployed by the time you read this email.
On 5/3/07, Ben Dotte <bd...@widen.com> wrote:
>
> Yes, so an example would be WEB-INF/app/About.html. I'm a little fuzzy
> on the historical reason for this but it has certainly been a valid
> choice since Tapestry 3 at least. I noticed
> AbstractSpecificationResolver.java has two different methods,
> getWebInfLocation() and getWebInfAppLocation(), the latter of which is
> documented with "Returns the location of the application-specific
> subdirectory, under /WEB-INF/, in the servlet context."
>
> So presumably for us that application-specific subdirectory is app.
> Perhaps that is because the <servlet-name> is defined as "app" for us in
> web.xml but I'm not 100% sure where that is coming from.
>
> Yes, our .application file is also in that directory.
>
> -----Original Message-----
> From: Jesse Kuhnert [mailto:jkuhnert@gmail.com]
> Sent: Thursday, May 03, 2007 11:41 AM
> To: Tapestry users
> Subject: Re: 4.1.2 snapshot changes 4-20 to 4-30
>
> Where/how does the "app" part come in? Is there literally a directory
> called
> "app" where you have stuff, and if so is your .application file there as
> well?
>
> On 5/3/07, Ben Dotte <bd...@widen.com> wrote:
> >
> > The issue where component templates cannot be found in WEB-INF/app for
> > specless apps. Yes, Marcus mentioned the same problem on TAPESTRY-1396
> > yesterday. And yes, it is still a problem with the snapshot that just
> > went out (tapestry-framework-4.1.2-20070503.160951-67.jar).
> >
> > To recreate, just put a component template with no spec under
> > WEB-INF/app and Tapestry will be unable to find it on any of the
> > post-4-30 snapshots.
> >
> > -----Original Message-----
> > From: Jesse Kuhnert [mailto:jkuhnert@gmail.com]
> > Sent: Thursday, May 03, 2007 11:13 AM
> > To: Tapestry users
> > Subject: Re: 4.1.2 snapshot changes 4-20 to 4-30
> >
> > Which issue is still a problem? Is it anything discussed in
> > https://issues.apache.org/jira/browse/TAPESTRY-1396 ?
> >
> > Perhaps your failure is slightly different ? I may need more specific
> > information (to re-create) . ...Either way an update just went out a
> few
> > seconds ago. Maybe that fixed it.
> >
> > On 5/3/07, Ben Dotte <bd...@widen.com> wrote:
> > >
> > > It appears this is still a problem, even with the newest snapshot
> > > (tapestry-framework-4.1.2-20070503.050340-66.jar)
> > > <snipped>
> > >
> >
> >
> >
> > --
> > Jesse Kuhnert
> > Tapestry/Dojo team member/developer
> >
> > Open source based consulting work centered around
> > dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: users-help@tapestry.apache.org
> >
> >
>
>
> --
> Jesse Kuhnert
> Tapestry/Dojo team member/developer
>
> Open source based consulting work centered around
> dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
--
Jesse Kuhnert
Tapestry/Dojo team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
RE: 4.1.2 snapshot changes 4-20 to 4-30
Posted by Ben Dotte <bd...@widen.com>.
Yes, so an example would be WEB-INF/app/About.html. I'm a little fuzzy
on the historical reason for this but it has certainly been a valid
choice since Tapestry 3 at least. I noticed
AbstractSpecificationResolver.java has two different methods,
getWebInfLocation() and getWebInfAppLocation(), the latter of which is
documented with "Returns the location of the application-specific
subdirectory, under /WEB-INF/, in the servlet context."
So presumably for us that application-specific subdirectory is app.
Perhaps that is because the <servlet-name> is defined as "app" for us in
web.xml but I'm not 100% sure where that is coming from.
Yes, our .application file is also in that directory.
-----Original Message-----
From: Jesse Kuhnert [mailto:jkuhnert@gmail.com]
Sent: Thursday, May 03, 2007 11:41 AM
To: Tapestry users
Subject: Re: 4.1.2 snapshot changes 4-20 to 4-30
Where/how does the "app" part come in? Is there literally a directory
called
"app" where you have stuff, and if so is your .application file there as
well?
On 5/3/07, Ben Dotte <bd...@widen.com> wrote:
>
> The issue where component templates cannot be found in WEB-INF/app for
> specless apps. Yes, Marcus mentioned the same problem on TAPESTRY-1396
> yesterday. And yes, it is still a problem with the snapshot that just
> went out (tapestry-framework-4.1.2-20070503.160951-67.jar).
>
> To recreate, just put a component template with no spec under
> WEB-INF/app and Tapestry will be unable to find it on any of the
> post-4-30 snapshots.
>
> -----Original Message-----
> From: Jesse Kuhnert [mailto:jkuhnert@gmail.com]
> Sent: Thursday, May 03, 2007 11:13 AM
> To: Tapestry users
> Subject: Re: 4.1.2 snapshot changes 4-20 to 4-30
>
> Which issue is still a problem? Is it anything discussed in
> https://issues.apache.org/jira/browse/TAPESTRY-1396 ?
>
> Perhaps your failure is slightly different ? I may need more specific
> information (to re-create) . ...Either way an update just went out a
few
> seconds ago. Maybe that fixed it.
>
> On 5/3/07, Ben Dotte <bd...@widen.com> wrote:
> >
> > It appears this is still a problem, even with the newest snapshot
> > (tapestry-framework-4.1.2-20070503.050340-66.jar)
> > <snipped>
> >
>
>
>
> --
> Jesse Kuhnert
> Tapestry/Dojo team member/developer
>
> Open source based consulting work centered around
> dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
--
Jesse Kuhnert
Tapestry/Dojo team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: 4.1.2 snapshot changes 4-20 to 4-30
Posted by Jesse Kuhnert <jk...@gmail.com>.
Where/how does the "app" part come in? Is there literally a directory called
"app" where you have stuff, and if so is your .application file there as
well?
On 5/3/07, Ben Dotte <bd...@widen.com> wrote:
>
> The issue where component templates cannot be found in WEB-INF/app for
> specless apps. Yes, Marcus mentioned the same problem on TAPESTRY-1396
> yesterday. And yes, it is still a problem with the snapshot that just
> went out (tapestry-framework-4.1.2-20070503.160951-67.jar).
>
> To recreate, just put a component template with no spec under
> WEB-INF/app and Tapestry will be unable to find it on any of the
> post-4-30 snapshots.
>
> -----Original Message-----
> From: Jesse Kuhnert [mailto:jkuhnert@gmail.com]
> Sent: Thursday, May 03, 2007 11:13 AM
> To: Tapestry users
> Subject: Re: 4.1.2 snapshot changes 4-20 to 4-30
>
> Which issue is still a problem? Is it anything discussed in
> https://issues.apache.org/jira/browse/TAPESTRY-1396 ?
>
> Perhaps your failure is slightly different ? I may need more specific
> information (to re-create) . ...Either way an update just went out a few
> seconds ago. Maybe that fixed it.
>
> On 5/3/07, Ben Dotte <bd...@widen.com> wrote:
> >
> > It appears this is still a problem, even with the newest snapshot
> > (tapestry-framework-4.1.2-20070503.050340-66.jar)
> > <snipped>
> >
>
>
>
> --
> Jesse Kuhnert
> Tapestry/Dojo team member/developer
>
> Open source based consulting work centered around
> dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
--
Jesse Kuhnert
Tapestry/Dojo team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
RE: 4.1.2 snapshot changes 4-20 to 4-30
Posted by Ben Dotte <bd...@widen.com>.
The issue where component templates cannot be found in WEB-INF/app for
specless apps. Yes, Marcus mentioned the same problem on TAPESTRY-1396
yesterday. And yes, it is still a problem with the snapshot that just
went out (tapestry-framework-4.1.2-20070503.160951-67.jar).
To recreate, just put a component template with no spec under
WEB-INF/app and Tapestry will be unable to find it on any of the
post-4-30 snapshots.
-----Original Message-----
From: Jesse Kuhnert [mailto:jkuhnert@gmail.com]
Sent: Thursday, May 03, 2007 11:13 AM
To: Tapestry users
Subject: Re: 4.1.2 snapshot changes 4-20 to 4-30
Which issue is still a problem? Is it anything discussed in
https://issues.apache.org/jira/browse/TAPESTRY-1396 ?
Perhaps your failure is slightly different ? I may need more specific
information (to re-create) . ...Either way an update just went out a few
seconds ago. Maybe that fixed it.
On 5/3/07, Ben Dotte <bd...@widen.com> wrote:
>
> It appears this is still a problem, even with the newest snapshot
> (tapestry-framework-4.1.2-20070503.050340-66.jar)
> <snipped>
>
--
Jesse Kuhnert
Tapestry/Dojo team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: 4.1.2 snapshot changes 4-20 to 4-30
Posted by Jesse Kuhnert <jk...@gmail.com>.
Which issue is still a problem? Is it anything discussed in
https://issues.apache.org/jira/browse/TAPESTRY-1396 ?
Perhaps your failure is slightly different ? I may need more specific
information (to re-create) . ...Either way an update just went out a few
seconds ago. Maybe that fixed it.
On 5/3/07, Ben Dotte <bd...@widen.com> wrote:
>
> It appears this is still a problem, even with the newest snapshot
> (tapestry-framework-4.1.2-20070503.050340-66.jar)
> <snipped>
>
--
Jesse Kuhnert
Tapestry/Dojo team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
RE: 4.1.2 snapshot changes 4-20 to 4-30
Posted by Ben Dotte <bd...@widen.com>.
It appears this is still a problem, even with the newest snapshot
(tapestry-framework-4.1.2-20070503.050340-66.jar)
-----Original Message-----
From: Ben Dotte [mailto:bdotte@widen.com]
Sent: Wednesday, May 02, 2007 2:50 PM
To: Tapestry users
Subject: RE: 4.1.2 snapshot changes 4-20 to 4-30
Ok, looks like Marcus ran into the same problem:
https://issues.apache.org/jira/browse/TAPESTRY-1396
On a separate note I see OGNL Jira is sending out e-mails now.. awesome.
-----Original Message-----
From: Ben Dotte [mailto:bdotte@widen.com]
Sent: Wednesday, May 02, 2007 1:55 PM
To: Tapestry users
Subject: RE: 4.1.2 snapshot changes 4-20 to 4-30
Thanks. A good example that replicates our setup would be to have a
component (not page) template with no spec directly under WEB-INF/app.
It would probably also work to just put it directly into WEB-INF.
-----Original Message-----
From: Jesse Kuhnert [mailto:jkuhnert@gmail.com]
Sent: Wednesday, May 02, 2007 1:46 PM
To: Tapestry users
Subject: Re: 4.1.2 snapshot changes 4-20 to 4-30
Yes I think my intention/want now is to have everything "just work"
whether
you stick things in context or classpath (if possible, some things
aren't
because of restricted filesystem access ).
I'll look in to this later today, but to be sure I'm not
mis-interpreting
....A good example would be having a page with no spec + the html
template
just being under the web-inf folder right ?
On 5/2/07, Ben Dotte <bd...@widen.com> wrote:
>
> It looks like the newest snapshot does fix my EventListener and Script
> problems. However now I am seeing the problem Andreas mentioned, where
a
> component isn't being found where it used to get found.
>
> We are specless and our page/component templates are stored in
> WEB-INF/app. There was a change made to
> ComponentSpecificationResolverImpl.java between the current snapshot
and
> the one from 4-20 that seems to have caused this problem (in
> searchForComponentClass() line 252):
>
> Resource componentResource =
namespaceResource.getRelativeResource(type
> + ".jwc");
>
> // try classpath relative if namespace relative doesn't resolve
>
> if (componentResource.getResourceURL() == null) {
>
> Resource classResource = new ClasspathResource(_classResolver,
> componentClass.getName().replace('.', '/'));
> componentResource = classResource.getRelativeResource(type +
> ".jwc");
> }
>
> Since we don't have any .jwc files, componentResource.getResourceURL()
> always returns null and it then searches on the classpath instead. I
> tried putting the templates on the classpath and it finds them there,
> but that isn't how our build system is setup to work right now. If I
> comment out that if statement everything works fine again and the
> templates on WEB-INF/app are found.
>
> So, is this an intentional change, or should it be able to find
> templates in WEB-INF/app for specless apps?
>
> Thanks,
> Ben
>
> -----Original Message-----
> From: Ben Dotte [mailto:bdotte@widen.com]
> Sent: Tuesday, May 01, 2007 2:54 PM
> To: Tapestry users
> Subject: RE: 4.1.2 snapshot changes 4-20 to 4-30
>
> Thanks for looking into it so quickly.. I will try out the new
snapshot
> tomorrow.
>
> -----Original Message-----
> From: Jesse Kuhnert [mailto:jkuhnert@gmail.com]
> Sent: Tuesday, May 01, 2007 2:49 PM
> To: Tapestry users
> Subject: Re: 4.1.2 snapshot changes 4-20 to 4-30
>
> A fix is deploying now for the @EventListener related issue. (though
I'm
> unsure if it fixes it for Ben but we'll see)
>
> The script thing will have to happen later tonight.
>
> On 5/1/07, Jesse Kuhnert <jk...@gmail.com> wrote:
> >
> > Yeah I'm aware of the issue, think it's fixed locally but am still
> testing
> > the changes.
> >
> > On 5/1/07, Andreas Andreou < andyhot@di.uoa.gr> wrote:
> > >
> > > I think i've seen some similar issues in the latest snapshots...
> > >
> > > They indeed seem to be related to how components/pages are found,
> i'll
> > > try
> > > to have
> > > a clean example demonstrating this and register a JIRA.
> > >
> > > For now, try using:
> > >
> > > <dependency>
> > > <groupId>org.apache.tapestry</groupId>
> > > <artifactId>tapestry-framework</artifactId>
> > > <version>4.1.2-20070424.205219-56</version>
> > > </dependency>
> > >
> > >
> > >
> > > On 5/1/07, Ben Dotte <bd...@widen.com> wrote:
> > > >
> > > > I tried the snapshots from this morning but unfortunately I
still
> get
> > > > the same EventListener error. For the script error I tried
adding
> > > > context: to the path like this:
> > > >
> > > > <span jwcid="@Script"
> script="context:/scripts/categoryHelper.script"
> > > />
> > > >
> > > > But now the error I get for that is:
> > > >
> > > > Unable to parse script
> > > >
> > >
>
classpath:collective/ui/components/context:/scripts/categoryHelper.scrip
> > > > t.
> > > >
> > > > -----Original Message-----
> > > > From: Jesse Kuhnert [mailto:jkuhnert@gmail.com ]
> > > > Sent: Tuesday, May 01, 2007 9:33 AM
> > > > To: Tapestry users
> > > > Subject: Re: 4.1.2 snapshot changes 4-20 to 4-30
> > > >
> > > > There were two unrelated changes made. The @EventListener change
> > > > involved
> > > > some inevitable fundamental flaws that I think are all fully
> resolved
> > > as
> > > > of
> > > > this mornings deployment of snapshots.
> > > >
> > > > The script error is related to how the component specs are being
> > > > resolved,
> > > > I'll look into why this is messing up for you but am sure that
if
> you
> > > > add
> > > > either "context:" or "classpath:" in front of your string it
will
> work
> > > > correctly. (though I intended for it to work without them, so
it's
> a
> > > bug
> > > > if
> > > > it isn't working)
> > > >
> > > > On 5/1/07, Ben Dotte <bd...@widen.com> wrote:
> > > > >
> > > > > Were there some sort of fundamental changes that happened
> between
> > > the
> > > > > Tapestry 4.1.2 4-20 snapshot and the one from 4-30? I tried
> > > upgrading
> > > > to
> > > > > 4-30 and I just seem to hit one error after another. The first
> > > problem
> > > > > is an EventListener that used to work fine:
> > > > >
> > > > > @EventListener(targets="sessionData", events="onclick")
> > > > > public void sessionDataClicked(IRequestCycle cycle)
> > > > > {
> > > > > setShowSessionData(true);
> > > > > cycle.getResponseBuilder
> > > ().updateComponent("theSessionData");
> > > > > }
> > > > >
> > > > > The nested stack from that is:
> > > > >
> > > > > Caused by: org.apache.hivemind.ApplicationRuntimeException :
No
> > > > component
> > > > > found in tree for EventListener binding with a matching
> component id
> > > > of
> > > > > sessionData. [context:/WEB-INF/app/ErrorPage.html, line 1]
> > > > > at
> > > > >
> > > >
org.apache.tapestry.pageload.EventConnectionVisitor.visitComponent
> > > (Event
> > > > > ConnectionVisitor.java:51)
> > > > > at
> > > > >
> > > >
> > >
>
$IComponentVisitor_11248054e16.visitComponent($IComponentVisitor_1124805
> > > > > 4e16.java)
> > > > > at
> > > > >
> > > >
> > >
>
$IComponentVisitor_11248054e17.visitComponent($IComponentVisitor_1124805
> > > > > 4e17.java)
> > > > > at
> > > > >
> > > >
>
org.apache.tapestry.pageload.ComponentTreeWalker.walkComponentTree(Compo
> > > > > nentTreeWalker.java:45)
> > > > > at
> > > > >
> > > >
org.apache.tapestry.pageload.ComponentTreeWalker.walkComponentTree
> > > (Compo
> > > > > nentTreeWalker.java:57)
> > > > > at
> > > > >
org.apache.tapestry.pageload.PageLoader.loadPage(PageLoader.java
> > > :604)
> > > > > at
> > > > >
$IPageLoader_11248054e04.loadPage($IPageLoader_11248054e04.java)
> > > > > at
> > > > >
$IPageLoader_11248054e05.loadPage($IPageLoader_11248054e05.java)
> > > > > at
> > > > >
> org.apache.tapestry.pageload.PageSource.getPage(PageSource.java:119)
> > > > > at
> > > > >
$IPageSource_11248054d1c.getPage($IPageSource_11248054d1c.java)
> > > > > at
> > > > >
> > > >
org.apache.tapestry.engine.RequestCycle.loadPage(RequestCycle.java
> > > :239)
> > > > > at
> > > > >
> org.apache.tapestry.engine.RequestCycle.getPage(RequestCycle.java
> > > :226)
> > > > > at
> > > > >
> > > >
org.apache.tapestry.error.ExceptionPresenterImpl.presentException
> > > (Except
> > > > > ionPresenterImpl.java:42)
> > > > > ... 62 more
> > > > >
> > > > > After I commented that out I got another error for a Script:
> > > > >
> > > > > <span jwcid="@Script" script="/scripts/categoryHelper.script"
/>
> > > > >
> > > > > Caused by:
org.apache.tapestry.util.xml.DocumentParseException:
> > > Unable
> > > > > to find resource classpath:/scripts/categoryHelper.script.
> > > > > [classpath:/scripts/categoryHelper.script]
> > > > > at
> > > > >
> > > > org.apache.tapestry.util.xml.RuleDirectedParser.parse
> > > (RuleDirectedParser
> > > > > .java:125)
> > > > > at
> > > > >
> org.apache.tapestry.script.ScriptParser.parse(ScriptParser.java:112)
> > > > > at
> > > > >
> > > > org.apache.tapestry.engine.DefaultScriptSource.parse
> > > (DefaultScriptSource
> > > > > .java:88)
> > > > > ... 124 more
> > > > >
> > > > > I saw a minor change in JIRA to the way scripts are found but
I
> > > > couldn't
> > > > > see how it would relate to this in particular.
> > > > >
> > > > > Thanks,
> > > > > Ben
> > > > >
> > > > >
> > >
> ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > > > > For additional commands, e-mail:
users-help@tapestry.apache.org
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > Jesse Kuhnert
> > > > Tapestry/Dojo team member/developer
> > > >
> > > > Open source based consulting work centered around
> > > > dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
> > > >
> > > >
> ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > > > For additional commands, e-mail: users-help@tapestry.apache.org
> > > >
> > > >
> > > >
> > >
> > >
> > > --
> > > Andreas Andreou - andyhot@apache.org - http://andyhot.di.uoa.gr
> > > Tapestry / Tacos developer
> > > Open Source / JEE Consulting
> > >
> >
> >
> >
> > --
> > Jesse Kuhnert
> > Tapestry/Dojo team member/developer
> >
> > Open source based consulting work centered around
> > dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
> >
>
>
>
> --
> Jesse Kuhnert
> Tapestry/Dojo team member/developer
>
> Open source based consulting work centered around
> dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
--
Jesse Kuhnert
Tapestry/Dojo team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
RE: 4.1.2 snapshot changes 4-20 to 4-30
Posted by Ben Dotte <bd...@widen.com>.
Ok, looks like Marcus ran into the same problem:
https://issues.apache.org/jira/browse/TAPESTRY-1396
On a separate note I see OGNL Jira is sending out e-mails now.. awesome.
-----Original Message-----
From: Ben Dotte [mailto:bdotte@widen.com]
Sent: Wednesday, May 02, 2007 1:55 PM
To: Tapestry users
Subject: RE: 4.1.2 snapshot changes 4-20 to 4-30
Thanks. A good example that replicates our setup would be to have a
component (not page) template with no spec directly under WEB-INF/app.
It would probably also work to just put it directly into WEB-INF.
-----Original Message-----
From: Jesse Kuhnert [mailto:jkuhnert@gmail.com]
Sent: Wednesday, May 02, 2007 1:46 PM
To: Tapestry users
Subject: Re: 4.1.2 snapshot changes 4-20 to 4-30
Yes I think my intention/want now is to have everything "just work"
whether
you stick things in context or classpath (if possible, some things
aren't
because of restricted filesystem access ).
I'll look in to this later today, but to be sure I'm not
mis-interpreting
....A good example would be having a page with no spec + the html
template
just being under the web-inf folder right ?
On 5/2/07, Ben Dotte <bd...@widen.com> wrote:
>
> It looks like the newest snapshot does fix my EventListener and Script
> problems. However now I am seeing the problem Andreas mentioned, where
a
> component isn't being found where it used to get found.
>
> We are specless and our page/component templates are stored in
> WEB-INF/app. There was a change made to
> ComponentSpecificationResolverImpl.java between the current snapshot
and
> the one from 4-20 that seems to have caused this problem (in
> searchForComponentClass() line 252):
>
> Resource componentResource =
namespaceResource.getRelativeResource(type
> + ".jwc");
>
> // try classpath relative if namespace relative doesn't resolve
>
> if (componentResource.getResourceURL() == null) {
>
> Resource classResource = new ClasspathResource(_classResolver,
> componentClass.getName().replace('.', '/'));
> componentResource = classResource.getRelativeResource(type +
> ".jwc");
> }
>
> Since we don't have any .jwc files, componentResource.getResourceURL()
> always returns null and it then searches on the classpath instead. I
> tried putting the templates on the classpath and it finds them there,
> but that isn't how our build system is setup to work right now. If I
> comment out that if statement everything works fine again and the
> templates on WEB-INF/app are found.
>
> So, is this an intentional change, or should it be able to find
> templates in WEB-INF/app for specless apps?
>
> Thanks,
> Ben
>
> -----Original Message-----
> From: Ben Dotte [mailto:bdotte@widen.com]
> Sent: Tuesday, May 01, 2007 2:54 PM
> To: Tapestry users
> Subject: RE: 4.1.2 snapshot changes 4-20 to 4-30
>
> Thanks for looking into it so quickly.. I will try out the new
snapshot
> tomorrow.
>
> -----Original Message-----
> From: Jesse Kuhnert [mailto:jkuhnert@gmail.com]
> Sent: Tuesday, May 01, 2007 2:49 PM
> To: Tapestry users
> Subject: Re: 4.1.2 snapshot changes 4-20 to 4-30
>
> A fix is deploying now for the @EventListener related issue. (though
I'm
> unsure if it fixes it for Ben but we'll see)
>
> The script thing will have to happen later tonight.
>
> On 5/1/07, Jesse Kuhnert <jk...@gmail.com> wrote:
> >
> > Yeah I'm aware of the issue, think it's fixed locally but am still
> testing
> > the changes.
> >
> > On 5/1/07, Andreas Andreou < andyhot@di.uoa.gr> wrote:
> > >
> > > I think i've seen some similar issues in the latest snapshots...
> > >
> > > They indeed seem to be related to how components/pages are found,
> i'll
> > > try
> > > to have
> > > a clean example demonstrating this and register a JIRA.
> > >
> > > For now, try using:
> > >
> > > <dependency>
> > > <groupId>org.apache.tapestry</groupId>
> > > <artifactId>tapestry-framework</artifactId>
> > > <version>4.1.2-20070424.205219-56</version>
> > > </dependency>
> > >
> > >
> > >
> > > On 5/1/07, Ben Dotte <bd...@widen.com> wrote:
> > > >
> > > > I tried the snapshots from this morning but unfortunately I
still
> get
> > > > the same EventListener error. For the script error I tried
adding
> > > > context: to the path like this:
> > > >
> > > > <span jwcid="@Script"
> script="context:/scripts/categoryHelper.script"
> > > />
> > > >
> > > > But now the error I get for that is:
> > > >
> > > > Unable to parse script
> > > >
> > >
>
classpath:collective/ui/components/context:/scripts/categoryHelper.scrip
> > > > t.
> > > >
> > > > -----Original Message-----
> > > > From: Jesse Kuhnert [mailto:jkuhnert@gmail.com ]
> > > > Sent: Tuesday, May 01, 2007 9:33 AM
> > > > To: Tapestry users
> > > > Subject: Re: 4.1.2 snapshot changes 4-20 to 4-30
> > > >
> > > > There were two unrelated changes made. The @EventListener change
> > > > involved
> > > > some inevitable fundamental flaws that I think are all fully
> resolved
> > > as
> > > > of
> > > > this mornings deployment of snapshots.
> > > >
> > > > The script error is related to how the component specs are being
> > > > resolved,
> > > > I'll look into why this is messing up for you but am sure that
if
> you
> > > > add
> > > > either "context:" or "classpath:" in front of your string it
will
> work
> > > > correctly. (though I intended for it to work without them, so
it's
> a
> > > bug
> > > > if
> > > > it isn't working)
> > > >
> > > > On 5/1/07, Ben Dotte <bd...@widen.com> wrote:
> > > > >
> > > > > Were there some sort of fundamental changes that happened
> between
> > > the
> > > > > Tapestry 4.1.2 4-20 snapshot and the one from 4-30? I tried
> > > upgrading
> > > > to
> > > > > 4-30 and I just seem to hit one error after another. The first
> > > problem
> > > > > is an EventListener that used to work fine:
> > > > >
> > > > > @EventListener(targets="sessionData", events="onclick")
> > > > > public void sessionDataClicked(IRequestCycle cycle)
> > > > > {
> > > > > setShowSessionData(true);
> > > > > cycle.getResponseBuilder
> > > ().updateComponent("theSessionData");
> > > > > }
> > > > >
> > > > > The nested stack from that is:
> > > > >
> > > > > Caused by: org.apache.hivemind.ApplicationRuntimeException :
No
> > > > component
> > > > > found in tree for EventListener binding with a matching
> component id
> > > > of
> > > > > sessionData. [context:/WEB-INF/app/ErrorPage.html, line 1]
> > > > > at
> > > > >
> > > >
org.apache.tapestry.pageload.EventConnectionVisitor.visitComponent
> > > (Event
> > > > > ConnectionVisitor.java:51)
> > > > > at
> > > > >
> > > >
> > >
>
$IComponentVisitor_11248054e16.visitComponent($IComponentVisitor_1124805
> > > > > 4e16.java)
> > > > > at
> > > > >
> > > >
> > >
>
$IComponentVisitor_11248054e17.visitComponent($IComponentVisitor_1124805
> > > > > 4e17.java)
> > > > > at
> > > > >
> > > >
>
org.apache.tapestry.pageload.ComponentTreeWalker.walkComponentTree(Compo
> > > > > nentTreeWalker.java:45)
> > > > > at
> > > > >
> > > >
org.apache.tapestry.pageload.ComponentTreeWalker.walkComponentTree
> > > (Compo
> > > > > nentTreeWalker.java:57)
> > > > > at
> > > > >
org.apache.tapestry.pageload.PageLoader.loadPage(PageLoader.java
> > > :604)
> > > > > at
> > > > >
$IPageLoader_11248054e04.loadPage($IPageLoader_11248054e04.java)
> > > > > at
> > > > >
$IPageLoader_11248054e05.loadPage($IPageLoader_11248054e05.java)
> > > > > at
> > > > >
> org.apache.tapestry.pageload.PageSource.getPage(PageSource.java:119)
> > > > > at
> > > > >
$IPageSource_11248054d1c.getPage($IPageSource_11248054d1c.java)
> > > > > at
> > > > >
> > > >
org.apache.tapestry.engine.RequestCycle.loadPage(RequestCycle.java
> > > :239)
> > > > > at
> > > > >
> org.apache.tapestry.engine.RequestCycle.getPage(RequestCycle.java
> > > :226)
> > > > > at
> > > > >
> > > >
org.apache.tapestry.error.ExceptionPresenterImpl.presentException
> > > (Except
> > > > > ionPresenterImpl.java:42)
> > > > > ... 62 more
> > > > >
> > > > > After I commented that out I got another error for a Script:
> > > > >
> > > > > <span jwcid="@Script" script="/scripts/categoryHelper.script"
/>
> > > > >
> > > > > Caused by:
org.apache.tapestry.util.xml.DocumentParseException:
> > > Unable
> > > > > to find resource classpath:/scripts/categoryHelper.script.
> > > > > [classpath:/scripts/categoryHelper.script]
> > > > > at
> > > > >
> > > > org.apache.tapestry.util.xml.RuleDirectedParser.parse
> > > (RuleDirectedParser
> > > > > .java:125)
> > > > > at
> > > > >
> org.apache.tapestry.script.ScriptParser.parse(ScriptParser.java:112)
> > > > > at
> > > > >
> > > > org.apache.tapestry.engine.DefaultScriptSource.parse
> > > (DefaultScriptSource
> > > > > .java:88)
> > > > > ... 124 more
> > > > >
> > > > > I saw a minor change in JIRA to the way scripts are found but
I
> > > > couldn't
> > > > > see how it would relate to this in particular.
> > > > >
> > > > > Thanks,
> > > > > Ben
> > > > >
> > > > >
> > >
> ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > > > > For additional commands, e-mail:
users-help@tapestry.apache.org
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > Jesse Kuhnert
> > > > Tapestry/Dojo team member/developer
> > > >
> > > > Open source based consulting work centered around
> > > > dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
> > > >
> > > >
> ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > > > For additional commands, e-mail: users-help@tapestry.apache.org
> > > >
> > > >
> > > >
> > >
> > >
> > > --
> > > Andreas Andreou - andyhot@apache.org - http://andyhot.di.uoa.gr
> > > Tapestry / Tacos developer
> > > Open Source / JEE Consulting
> > >
> >
> >
> >
> > --
> > Jesse Kuhnert
> > Tapestry/Dojo team member/developer
> >
> > Open source based consulting work centered around
> > dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
> >
>
>
>
> --
> Jesse Kuhnert
> Tapestry/Dojo team member/developer
>
> Open source based consulting work centered around
> dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
--
Jesse Kuhnert
Tapestry/Dojo team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
RE: 4.1.2 snapshot changes 4-20 to 4-30
Posted by Ben Dotte <bd...@widen.com>.
Thanks. A good example that replicates our setup would be to have a
component (not page) template with no spec directly under WEB-INF/app.
It would probably also work to just put it directly into WEB-INF.
-----Original Message-----
From: Jesse Kuhnert [mailto:jkuhnert@gmail.com]
Sent: Wednesday, May 02, 2007 1:46 PM
To: Tapestry users
Subject: Re: 4.1.2 snapshot changes 4-20 to 4-30
Yes I think my intention/want now is to have everything "just work"
whether
you stick things in context or classpath (if possible, some things
aren't
because of restricted filesystem access ).
I'll look in to this later today, but to be sure I'm not
mis-interpreting
....A good example would be having a page with no spec + the html
template
just being under the web-inf folder right ?
On 5/2/07, Ben Dotte <bd...@widen.com> wrote:
>
> It looks like the newest snapshot does fix my EventListener and Script
> problems. However now I am seeing the problem Andreas mentioned, where
a
> component isn't being found where it used to get found.
>
> We are specless and our page/component templates are stored in
> WEB-INF/app. There was a change made to
> ComponentSpecificationResolverImpl.java between the current snapshot
and
> the one from 4-20 that seems to have caused this problem (in
> searchForComponentClass() line 252):
>
> Resource componentResource =
namespaceResource.getRelativeResource(type
> + ".jwc");
>
> // try classpath relative if namespace relative doesn't resolve
>
> if (componentResource.getResourceURL() == null) {
>
> Resource classResource = new ClasspathResource(_classResolver,
> componentClass.getName().replace('.', '/'));
> componentResource = classResource.getRelativeResource(type +
> ".jwc");
> }
>
> Since we don't have any .jwc files, componentResource.getResourceURL()
> always returns null and it then searches on the classpath instead. I
> tried putting the templates on the classpath and it finds them there,
> but that isn't how our build system is setup to work right now. If I
> comment out that if statement everything works fine again and the
> templates on WEB-INF/app are found.
>
> So, is this an intentional change, or should it be able to find
> templates in WEB-INF/app for specless apps?
>
> Thanks,
> Ben
>
> -----Original Message-----
> From: Ben Dotte [mailto:bdotte@widen.com]
> Sent: Tuesday, May 01, 2007 2:54 PM
> To: Tapestry users
> Subject: RE: 4.1.2 snapshot changes 4-20 to 4-30
>
> Thanks for looking into it so quickly.. I will try out the new
snapshot
> tomorrow.
>
> -----Original Message-----
> From: Jesse Kuhnert [mailto:jkuhnert@gmail.com]
> Sent: Tuesday, May 01, 2007 2:49 PM
> To: Tapestry users
> Subject: Re: 4.1.2 snapshot changes 4-20 to 4-30
>
> A fix is deploying now for the @EventListener related issue. (though
I'm
> unsure if it fixes it for Ben but we'll see)
>
> The script thing will have to happen later tonight.
>
> On 5/1/07, Jesse Kuhnert <jk...@gmail.com> wrote:
> >
> > Yeah I'm aware of the issue, think it's fixed locally but am still
> testing
> > the changes.
> >
> > On 5/1/07, Andreas Andreou < andyhot@di.uoa.gr> wrote:
> > >
> > > I think i've seen some similar issues in the latest snapshots...
> > >
> > > They indeed seem to be related to how components/pages are found,
> i'll
> > > try
> > > to have
> > > a clean example demonstrating this and register a JIRA.
> > >
> > > For now, try using:
> > >
> > > <dependency>
> > > <groupId>org.apache.tapestry</groupId>
> > > <artifactId>tapestry-framework</artifactId>
> > > <version>4.1.2-20070424.205219-56</version>
> > > </dependency>
> > >
> > >
> > >
> > > On 5/1/07, Ben Dotte <bd...@widen.com> wrote:
> > > >
> > > > I tried the snapshots from this morning but unfortunately I
still
> get
> > > > the same EventListener error. For the script error I tried
adding
> > > > context: to the path like this:
> > > >
> > > > <span jwcid="@Script"
> script="context:/scripts/categoryHelper.script"
> > > />
> > > >
> > > > But now the error I get for that is:
> > > >
> > > > Unable to parse script
> > > >
> > >
>
classpath:collective/ui/components/context:/scripts/categoryHelper.scrip
> > > > t.
> > > >
> > > > -----Original Message-----
> > > > From: Jesse Kuhnert [mailto:jkuhnert@gmail.com ]
> > > > Sent: Tuesday, May 01, 2007 9:33 AM
> > > > To: Tapestry users
> > > > Subject: Re: 4.1.2 snapshot changes 4-20 to 4-30
> > > >
> > > > There were two unrelated changes made. The @EventListener change
> > > > involved
> > > > some inevitable fundamental flaws that I think are all fully
> resolved
> > > as
> > > > of
> > > > this mornings deployment of snapshots.
> > > >
> > > > The script error is related to how the component specs are being
> > > > resolved,
> > > > I'll look into why this is messing up for you but am sure that
if
> you
> > > > add
> > > > either "context:" or "classpath:" in front of your string it
will
> work
> > > > correctly. (though I intended for it to work without them, so
it's
> a
> > > bug
> > > > if
> > > > it isn't working)
> > > >
> > > > On 5/1/07, Ben Dotte <bd...@widen.com> wrote:
> > > > >
> > > > > Were there some sort of fundamental changes that happened
> between
> > > the
> > > > > Tapestry 4.1.2 4-20 snapshot and the one from 4-30? I tried
> > > upgrading
> > > > to
> > > > > 4-30 and I just seem to hit one error after another. The first
> > > problem
> > > > > is an EventListener that used to work fine:
> > > > >
> > > > > @EventListener(targets="sessionData", events="onclick")
> > > > > public void sessionDataClicked(IRequestCycle cycle)
> > > > > {
> > > > > setShowSessionData(true);
> > > > > cycle.getResponseBuilder
> > > ().updateComponent("theSessionData");
> > > > > }
> > > > >
> > > > > The nested stack from that is:
> > > > >
> > > > > Caused by: org.apache.hivemind.ApplicationRuntimeException :
No
> > > > component
> > > > > found in tree for EventListener binding with a matching
> component id
> > > > of
> > > > > sessionData. [context:/WEB-INF/app/ErrorPage.html, line 1]
> > > > > at
> > > > >
> > > >
org.apache.tapestry.pageload.EventConnectionVisitor.visitComponent
> > > (Event
> > > > > ConnectionVisitor.java:51)
> > > > > at
> > > > >
> > > >
> > >
>
$IComponentVisitor_11248054e16.visitComponent($IComponentVisitor_1124805
> > > > > 4e16.java)
> > > > > at
> > > > >
> > > >
> > >
>
$IComponentVisitor_11248054e17.visitComponent($IComponentVisitor_1124805
> > > > > 4e17.java)
> > > > > at
> > > > >
> > > >
>
org.apache.tapestry.pageload.ComponentTreeWalker.walkComponentTree(Compo
> > > > > nentTreeWalker.java:45)
> > > > > at
> > > > >
> > > >
org.apache.tapestry.pageload.ComponentTreeWalker.walkComponentTree
> > > (Compo
> > > > > nentTreeWalker.java:57)
> > > > > at
> > > > >
org.apache.tapestry.pageload.PageLoader.loadPage(PageLoader.java
> > > :604)
> > > > > at
> > > > >
$IPageLoader_11248054e04.loadPage($IPageLoader_11248054e04.java)
> > > > > at
> > > > >
$IPageLoader_11248054e05.loadPage($IPageLoader_11248054e05.java)
> > > > > at
> > > > >
> org.apache.tapestry.pageload.PageSource.getPage(PageSource.java:119)
> > > > > at
> > > > >
$IPageSource_11248054d1c.getPage($IPageSource_11248054d1c.java)
> > > > > at
> > > > >
> > > >
org.apache.tapestry.engine.RequestCycle.loadPage(RequestCycle.java
> > > :239)
> > > > > at
> > > > >
> org.apache.tapestry.engine.RequestCycle.getPage(RequestCycle.java
> > > :226)
> > > > > at
> > > > >
> > > >
org.apache.tapestry.error.ExceptionPresenterImpl.presentException
> > > (Except
> > > > > ionPresenterImpl.java:42)
> > > > > ... 62 more
> > > > >
> > > > > After I commented that out I got another error for a Script:
> > > > >
> > > > > <span jwcid="@Script" script="/scripts/categoryHelper.script"
/>
> > > > >
> > > > > Caused by:
org.apache.tapestry.util.xml.DocumentParseException:
> > > Unable
> > > > > to find resource classpath:/scripts/categoryHelper.script.
> > > > > [classpath:/scripts/categoryHelper.script]
> > > > > at
> > > > >
> > > > org.apache.tapestry.util.xml.RuleDirectedParser.parse
> > > (RuleDirectedParser
> > > > > .java:125)
> > > > > at
> > > > >
> org.apache.tapestry.script.ScriptParser.parse(ScriptParser.java:112)
> > > > > at
> > > > >
> > > > org.apache.tapestry.engine.DefaultScriptSource.parse
> > > (DefaultScriptSource
> > > > > .java:88)
> > > > > ... 124 more
> > > > >
> > > > > I saw a minor change in JIRA to the way scripts are found but
I
> > > > couldn't
> > > > > see how it would relate to this in particular.
> > > > >
> > > > > Thanks,
> > > > > Ben
> > > > >
> > > > >
> > >
> ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > > > > For additional commands, e-mail:
users-help@tapestry.apache.org
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > Jesse Kuhnert
> > > > Tapestry/Dojo team member/developer
> > > >
> > > > Open source based consulting work centered around
> > > > dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
> > > >
> > > >
> ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > > > For additional commands, e-mail: users-help@tapestry.apache.org
> > > >
> > > >
> > > >
> > >
> > >
> > > --
> > > Andreas Andreou - andyhot@apache.org - http://andyhot.di.uoa.gr
> > > Tapestry / Tacos developer
> > > Open Source / JEE Consulting
> > >
> >
> >
> >
> > --
> > Jesse Kuhnert
> > Tapestry/Dojo team member/developer
> >
> > Open source based consulting work centered around
> > dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
> >
>
>
>
> --
> Jesse Kuhnert
> Tapestry/Dojo team member/developer
>
> Open source based consulting work centered around
> dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
--
Jesse Kuhnert
Tapestry/Dojo team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: 4.1.2 snapshot changes 4-20 to 4-30
Posted by Jesse Kuhnert <jk...@gmail.com>.
Yes I think my intention/want now is to have everything "just work" whether
you stick things in context or classpath (if possible, some things aren't
because of restricted filesystem access ).
I'll look in to this later today, but to be sure I'm not mis-interpreting
....A good example would be having a page with no spec + the html template
just being under the web-inf folder right ?
On 5/2/07, Ben Dotte <bd...@widen.com> wrote:
>
> It looks like the newest snapshot does fix my EventListener and Script
> problems. However now I am seeing the problem Andreas mentioned, where a
> component isn't being found where it used to get found.
>
> We are specless and our page/component templates are stored in
> WEB-INF/app. There was a change made to
> ComponentSpecificationResolverImpl.java between the current snapshot and
> the one from 4-20 that seems to have caused this problem (in
> searchForComponentClass() line 252):
>
> Resource componentResource = namespaceResource.getRelativeResource(type
> + ".jwc");
>
> // try classpath relative if namespace relative doesn't resolve
>
> if (componentResource.getResourceURL() == null) {
>
> Resource classResource = new ClasspathResource(_classResolver,
> componentClass.getName().replace('.', '/'));
> componentResource = classResource.getRelativeResource(type +
> ".jwc");
> }
>
> Since we don't have any .jwc files, componentResource.getResourceURL()
> always returns null and it then searches on the classpath instead. I
> tried putting the templates on the classpath and it finds them there,
> but that isn't how our build system is setup to work right now. If I
> comment out that if statement everything works fine again and the
> templates on WEB-INF/app are found.
>
> So, is this an intentional change, or should it be able to find
> templates in WEB-INF/app for specless apps?
>
> Thanks,
> Ben
>
> -----Original Message-----
> From: Ben Dotte [mailto:bdotte@widen.com]
> Sent: Tuesday, May 01, 2007 2:54 PM
> To: Tapestry users
> Subject: RE: 4.1.2 snapshot changes 4-20 to 4-30
>
> Thanks for looking into it so quickly.. I will try out the new snapshot
> tomorrow.
>
> -----Original Message-----
> From: Jesse Kuhnert [mailto:jkuhnert@gmail.com]
> Sent: Tuesday, May 01, 2007 2:49 PM
> To: Tapestry users
> Subject: Re: 4.1.2 snapshot changes 4-20 to 4-30
>
> A fix is deploying now for the @EventListener related issue. (though I'm
> unsure if it fixes it for Ben but we'll see)
>
> The script thing will have to happen later tonight.
>
> On 5/1/07, Jesse Kuhnert <jk...@gmail.com> wrote:
> >
> > Yeah I'm aware of the issue, think it's fixed locally but am still
> testing
> > the changes.
> >
> > On 5/1/07, Andreas Andreou < andyhot@di.uoa.gr> wrote:
> > >
> > > I think i've seen some similar issues in the latest snapshots...
> > >
> > > They indeed seem to be related to how components/pages are found,
> i'll
> > > try
> > > to have
> > > a clean example demonstrating this and register a JIRA.
> > >
> > > For now, try using:
> > >
> > > <dependency>
> > > <groupId>org.apache.tapestry</groupId>
> > > <artifactId>tapestry-framework</artifactId>
> > > <version>4.1.2-20070424.205219-56</version>
> > > </dependency>
> > >
> > >
> > >
> > > On 5/1/07, Ben Dotte <bd...@widen.com> wrote:
> > > >
> > > > I tried the snapshots from this morning but unfortunately I still
> get
> > > > the same EventListener error. For the script error I tried adding
> > > > context: to the path like this:
> > > >
> > > > <span jwcid="@Script"
> script="context:/scripts/categoryHelper.script"
> > > />
> > > >
> > > > But now the error I get for that is:
> > > >
> > > > Unable to parse script
> > > >
> > >
> classpath:collective/ui/components/context:/scripts/categoryHelper.scrip
> > > > t.
> > > >
> > > > -----Original Message-----
> > > > From: Jesse Kuhnert [mailto:jkuhnert@gmail.com ]
> > > > Sent: Tuesday, May 01, 2007 9:33 AM
> > > > To: Tapestry users
> > > > Subject: Re: 4.1.2 snapshot changes 4-20 to 4-30
> > > >
> > > > There were two unrelated changes made. The @EventListener change
> > > > involved
> > > > some inevitable fundamental flaws that I think are all fully
> resolved
> > > as
> > > > of
> > > > this mornings deployment of snapshots.
> > > >
> > > > The script error is related to how the component specs are being
> > > > resolved,
> > > > I'll look into why this is messing up for you but am sure that if
> you
> > > > add
> > > > either "context:" or "classpath:" in front of your string it will
> work
> > > > correctly. (though I intended for it to work without them, so it's
> a
> > > bug
> > > > if
> > > > it isn't working)
> > > >
> > > > On 5/1/07, Ben Dotte <bd...@widen.com> wrote:
> > > > >
> > > > > Were there some sort of fundamental changes that happened
> between
> > > the
> > > > > Tapestry 4.1.2 4-20 snapshot and the one from 4-30? I tried
> > > upgrading
> > > > to
> > > > > 4-30 and I just seem to hit one error after another. The first
> > > problem
> > > > > is an EventListener that used to work fine:
> > > > >
> > > > > @EventListener(targets="sessionData", events="onclick")
> > > > > public void sessionDataClicked(IRequestCycle cycle)
> > > > > {
> > > > > setShowSessionData(true);
> > > > > cycle.getResponseBuilder
> > > ().updateComponent("theSessionData");
> > > > > }
> > > > >
> > > > > The nested stack from that is:
> > > > >
> > > > > Caused by: org.apache.hivemind.ApplicationRuntimeException : No
> > > > component
> > > > > found in tree for EventListener binding with a matching
> component id
> > > > of
> > > > > sessionData. [context:/WEB-INF/app/ErrorPage.html, line 1]
> > > > > at
> > > > >
> > > > org.apache.tapestry.pageload.EventConnectionVisitor.visitComponent
> > > (Event
> > > > > ConnectionVisitor.java:51)
> > > > > at
> > > > >
> > > >
> > >
> $IComponentVisitor_11248054e16.visitComponent($IComponentVisitor_1124805
> > > > > 4e16.java)
> > > > > at
> > > > >
> > > >
> > >
> $IComponentVisitor_11248054e17.visitComponent($IComponentVisitor_1124805
> > > > > 4e17.java)
> > > > > at
> > > > >
> > > >
> org.apache.tapestry.pageload.ComponentTreeWalker.walkComponentTree(Compo
> > > > > nentTreeWalker.java:45)
> > > > > at
> > > > >
> > > > org.apache.tapestry.pageload.ComponentTreeWalker.walkComponentTree
> > > (Compo
> > > > > nentTreeWalker.java:57)
> > > > > at
> > > > > org.apache.tapestry.pageload.PageLoader.loadPage(PageLoader.java
> > > :604)
> > > > > at
> > > > > $IPageLoader_11248054e04.loadPage($IPageLoader_11248054e04.java)
> > > > > at
> > > > > $IPageLoader_11248054e05.loadPage($IPageLoader_11248054e05.java)
> > > > > at
> > > > >
> org.apache.tapestry.pageload.PageSource.getPage(PageSource.java:119)
> > > > > at
> > > > > $IPageSource_11248054d1c.getPage($IPageSource_11248054d1c.java)
> > > > > at
> > > > >
> > > > org.apache.tapestry.engine.RequestCycle.loadPage(RequestCycle.java
> > > :239)
> > > > > at
> > > > >
> org.apache.tapestry.engine.RequestCycle.getPage(RequestCycle.java
> > > :226)
> > > > > at
> > > > >
> > > > org.apache.tapestry.error.ExceptionPresenterImpl.presentException
> > > (Except
> > > > > ionPresenterImpl.java:42)
> > > > > ... 62 more
> > > > >
> > > > > After I commented that out I got another error for a Script:
> > > > >
> > > > > <span jwcid="@Script" script="/scripts/categoryHelper.script" />
> > > > >
> > > > > Caused by: org.apache.tapestry.util.xml.DocumentParseException:
> > > Unable
> > > > > to find resource classpath:/scripts/categoryHelper.script.
> > > > > [classpath:/scripts/categoryHelper.script]
> > > > > at
> > > > >
> > > > org.apache.tapestry.util.xml.RuleDirectedParser.parse
> > > (RuleDirectedParser
> > > > > .java:125)
> > > > > at
> > > > >
> org.apache.tapestry.script.ScriptParser.parse(ScriptParser.java:112)
> > > > > at
> > > > >
> > > > org.apache.tapestry.engine.DefaultScriptSource.parse
> > > (DefaultScriptSource
> > > > > .java:88)
> > > > > ... 124 more
> > > > >
> > > > > I saw a minor change in JIRA to the way scripts are found but I
> > > > couldn't
> > > > > see how it would relate to this in particular.
> > > > >
> > > > > Thanks,
> > > > > Ben
> > > > >
> > > > >
> > >
> ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > > > > For additional commands, e-mail: users-help@tapestry.apache.org
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > Jesse Kuhnert
> > > > Tapestry/Dojo team member/developer
> > > >
> > > > Open source based consulting work centered around
> > > > dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
> > > >
> > > >
> ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > > > For additional commands, e-mail: users-help@tapestry.apache.org
> > > >
> > > >
> > > >
> > >
> > >
> > > --
> > > Andreas Andreou - andyhot@apache.org - http://andyhot.di.uoa.gr
> > > Tapestry / Tacos developer
> > > Open Source / JEE Consulting
> > >
> >
> >
> >
> > --
> > Jesse Kuhnert
> > Tapestry/Dojo team member/developer
> >
> > Open source based consulting work centered around
> > dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
> >
>
>
>
> --
> Jesse Kuhnert
> Tapestry/Dojo team member/developer
>
> Open source based consulting work centered around
> dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
--
Jesse Kuhnert
Tapestry/Dojo team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
RE: 4.1.2 snapshot changes 4-20 to 4-30
Posted by Ben Dotte <bd...@widen.com>.
It looks like the newest snapshot does fix my EventListener and Script
problems. However now I am seeing the problem Andreas mentioned, where a
component isn't being found where it used to get found.
We are specless and our page/component templates are stored in
WEB-INF/app. There was a change made to
ComponentSpecificationResolverImpl.java between the current snapshot and
the one from 4-20 that seems to have caused this problem (in
searchForComponentClass() line 252):
Resource componentResource = namespaceResource.getRelativeResource(type
+ ".jwc");
// try classpath relative if namespace relative doesn't resolve
if (componentResource.getResourceURL() == null) {
Resource classResource = new ClasspathResource(_classResolver,
componentClass.getName().replace('.', '/'));
componentResource = classResource.getRelativeResource(type +
".jwc");
}
Since we don't have any .jwc files, componentResource.getResourceURL()
always returns null and it then searches on the classpath instead. I
tried putting the templates on the classpath and it finds them there,
but that isn't how our build system is setup to work right now. If I
comment out that if statement everything works fine again and the
templates on WEB-INF/app are found.
So, is this an intentional change, or should it be able to find
templates in WEB-INF/app for specless apps?
Thanks,
Ben
-----Original Message-----
From: Ben Dotte [mailto:bdotte@widen.com]
Sent: Tuesday, May 01, 2007 2:54 PM
To: Tapestry users
Subject: RE: 4.1.2 snapshot changes 4-20 to 4-30
Thanks for looking into it so quickly.. I will try out the new snapshot
tomorrow.
-----Original Message-----
From: Jesse Kuhnert [mailto:jkuhnert@gmail.com]
Sent: Tuesday, May 01, 2007 2:49 PM
To: Tapestry users
Subject: Re: 4.1.2 snapshot changes 4-20 to 4-30
A fix is deploying now for the @EventListener related issue. (though I'm
unsure if it fixes it for Ben but we'll see)
The script thing will have to happen later tonight.
On 5/1/07, Jesse Kuhnert <jk...@gmail.com> wrote:
>
> Yeah I'm aware of the issue, think it's fixed locally but am still
testing
> the changes.
>
> On 5/1/07, Andreas Andreou < andyhot@di.uoa.gr> wrote:
> >
> > I think i've seen some similar issues in the latest snapshots...
> >
> > They indeed seem to be related to how components/pages are found,
i'll
> > try
> > to have
> > a clean example demonstrating this and register a JIRA.
> >
> > For now, try using:
> >
> > <dependency>
> > <groupId>org.apache.tapestry</groupId>
> > <artifactId>tapestry-framework</artifactId>
> > <version>4.1.2-20070424.205219-56</version>
> > </dependency>
> >
> >
> >
> > On 5/1/07, Ben Dotte <bd...@widen.com> wrote:
> > >
> > > I tried the snapshots from this morning but unfortunately I still
get
> > > the same EventListener error. For the script error I tried adding
> > > context: to the path like this:
> > >
> > > <span jwcid="@Script"
script="context:/scripts/categoryHelper.script"
> > />
> > >
> > > But now the error I get for that is:
> > >
> > > Unable to parse script
> > >
> >
classpath:collective/ui/components/context:/scripts/categoryHelper.scrip
> > > t.
> > >
> > > -----Original Message-----
> > > From: Jesse Kuhnert [mailto:jkuhnert@gmail.com ]
> > > Sent: Tuesday, May 01, 2007 9:33 AM
> > > To: Tapestry users
> > > Subject: Re: 4.1.2 snapshot changes 4-20 to 4-30
> > >
> > > There were two unrelated changes made. The @EventListener change
> > > involved
> > > some inevitable fundamental flaws that I think are all fully
resolved
> > as
> > > of
> > > this mornings deployment of snapshots.
> > >
> > > The script error is related to how the component specs are being
> > > resolved,
> > > I'll look into why this is messing up for you but am sure that if
you
> > > add
> > > either "context:" or "classpath:" in front of your string it will
work
> > > correctly. (though I intended for it to work without them, so it's
a
> > bug
> > > if
> > > it isn't working)
> > >
> > > On 5/1/07, Ben Dotte <bd...@widen.com> wrote:
> > > >
> > > > Were there some sort of fundamental changes that happened
between
> > the
> > > > Tapestry 4.1.2 4-20 snapshot and the one from 4-30? I tried
> > upgrading
> > > to
> > > > 4-30 and I just seem to hit one error after another. The first
> > problem
> > > > is an EventListener that used to work fine:
> > > >
> > > > @EventListener(targets="sessionData", events="onclick")
> > > > public void sessionDataClicked(IRequestCycle cycle)
> > > > {
> > > > setShowSessionData(true);
> > > > cycle.getResponseBuilder
> > ().updateComponent("theSessionData");
> > > > }
> > > >
> > > > The nested stack from that is:
> > > >
> > > > Caused by: org.apache.hivemind.ApplicationRuntimeException : No
> > > component
> > > > found in tree for EventListener binding with a matching
component id
> > > of
> > > > sessionData. [context:/WEB-INF/app/ErrorPage.html, line 1]
> > > > at
> > > >
> > > org.apache.tapestry.pageload.EventConnectionVisitor.visitComponent
> > (Event
> > > > ConnectionVisitor.java:51)
> > > > at
> > > >
> > >
> >
$IComponentVisitor_11248054e16.visitComponent($IComponentVisitor_1124805
> > > > 4e16.java)
> > > > at
> > > >
> > >
> >
$IComponentVisitor_11248054e17.visitComponent($IComponentVisitor_1124805
> > > > 4e17.java)
> > > > at
> > > >
> > >
org.apache.tapestry.pageload.ComponentTreeWalker.walkComponentTree(Compo
> > > > nentTreeWalker.java:45)
> > > > at
> > > >
> > > org.apache.tapestry.pageload.ComponentTreeWalker.walkComponentTree
> > (Compo
> > > > nentTreeWalker.java:57)
> > > > at
> > > > org.apache.tapestry.pageload.PageLoader.loadPage(PageLoader.java
> > :604)
> > > > at
> > > > $IPageLoader_11248054e04.loadPage($IPageLoader_11248054e04.java)
> > > > at
> > > > $IPageLoader_11248054e05.loadPage($IPageLoader_11248054e05.java)
> > > > at
> > > >
org.apache.tapestry.pageload.PageSource.getPage(PageSource.java:119)
> > > > at
> > > > $IPageSource_11248054d1c.getPage($IPageSource_11248054d1c.java)
> > > > at
> > > >
> > > org.apache.tapestry.engine.RequestCycle.loadPage(RequestCycle.java
> > :239)
> > > > at
> > > >
org.apache.tapestry.engine.RequestCycle.getPage(RequestCycle.java
> > :226)
> > > > at
> > > >
> > > org.apache.tapestry.error.ExceptionPresenterImpl.presentException
> > (Except
> > > > ionPresenterImpl.java:42)
> > > > ... 62 more
> > > >
> > > > After I commented that out I got another error for a Script:
> > > >
> > > > <span jwcid="@Script" script="/scripts/categoryHelper.script" />
> > > >
> > > > Caused by: org.apache.tapestry.util.xml.DocumentParseException:
> > Unable
> > > > to find resource classpath:/scripts/categoryHelper.script.
> > > > [classpath:/scripts/categoryHelper.script]
> > > > at
> > > >
> > > org.apache.tapestry.util.xml.RuleDirectedParser.parse
> > (RuleDirectedParser
> > > > .java:125)
> > > > at
> > > >
org.apache.tapestry.script.ScriptParser.parse(ScriptParser.java:112)
> > > > at
> > > >
> > > org.apache.tapestry.engine.DefaultScriptSource.parse
> > (DefaultScriptSource
> > > > .java:88)
> > > > ... 124 more
> > > >
> > > > I saw a minor change in JIRA to the way scripts are found but I
> > > couldn't
> > > > see how it would relate to this in particular.
> > > >
> > > > Thanks,
> > > > Ben
> > > >
> > > >
> >
---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > > > For additional commands, e-mail: users-help@tapestry.apache.org
> > > >
> > > >
> > >
> > >
> > > --
> > > Jesse Kuhnert
> > > Tapestry/Dojo team member/developer
> > >
> > > Open source based consulting work centered around
> > > dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
> > >
> > >
---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > > For additional commands, e-mail: users-help@tapestry.apache.org
> > >
> > >
> > >
> >
> >
> > --
> > Andreas Andreou - andyhot@apache.org - http://andyhot.di.uoa.gr
> > Tapestry / Tacos developer
> > Open Source / JEE Consulting
> >
>
>
>
> --
> Jesse Kuhnert
> Tapestry/Dojo team member/developer
>
> Open source based consulting work centered around
> dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
>
--
Jesse Kuhnert
Tapestry/Dojo team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
RE: 4.1.2 snapshot changes 4-20 to 4-30
Posted by Ben Dotte <bd...@widen.com>.
Thanks for looking into it so quickly.. I will try out the new snapshot
tomorrow.
-----Original Message-----
From: Jesse Kuhnert [mailto:jkuhnert@gmail.com]
Sent: Tuesday, May 01, 2007 2:49 PM
To: Tapestry users
Subject: Re: 4.1.2 snapshot changes 4-20 to 4-30
A fix is deploying now for the @EventListener related issue. (though I'm
unsure if it fixes it for Ben but we'll see)
The script thing will have to happen later tonight.
On 5/1/07, Jesse Kuhnert <jk...@gmail.com> wrote:
>
> Yeah I'm aware of the issue, think it's fixed locally but am still
testing
> the changes.
>
> On 5/1/07, Andreas Andreou < andyhot@di.uoa.gr> wrote:
> >
> > I think i've seen some similar issues in the latest snapshots...
> >
> > They indeed seem to be related to how components/pages are found,
i'll
> > try
> > to have
> > a clean example demonstrating this and register a JIRA.
> >
> > For now, try using:
> >
> > <dependency>
> > <groupId>org.apache.tapestry</groupId>
> > <artifactId>tapestry-framework</artifactId>
> > <version>4.1.2-20070424.205219-56</version>
> > </dependency>
> >
> >
> >
> > On 5/1/07, Ben Dotte <bd...@widen.com> wrote:
> > >
> > > I tried the snapshots from this morning but unfortunately I still
get
> > > the same EventListener error. For the script error I tried adding
> > > context: to the path like this:
> > >
> > > <span jwcid="@Script"
script="context:/scripts/categoryHelper.script"
> > />
> > >
> > > But now the error I get for that is:
> > >
> > > Unable to parse script
> > >
> >
classpath:collective/ui/components/context:/scripts/categoryHelper.scrip
> > > t.
> > >
> > > -----Original Message-----
> > > From: Jesse Kuhnert [mailto:jkuhnert@gmail.com ]
> > > Sent: Tuesday, May 01, 2007 9:33 AM
> > > To: Tapestry users
> > > Subject: Re: 4.1.2 snapshot changes 4-20 to 4-30
> > >
> > > There were two unrelated changes made. The @EventListener change
> > > involved
> > > some inevitable fundamental flaws that I think are all fully
resolved
> > as
> > > of
> > > this mornings deployment of snapshots.
> > >
> > > The script error is related to how the component specs are being
> > > resolved,
> > > I'll look into why this is messing up for you but am sure that if
you
> > > add
> > > either "context:" or "classpath:" in front of your string it will
work
> > > correctly. (though I intended for it to work without them, so it's
a
> > bug
> > > if
> > > it isn't working)
> > >
> > > On 5/1/07, Ben Dotte <bd...@widen.com> wrote:
> > > >
> > > > Were there some sort of fundamental changes that happened
between
> > the
> > > > Tapestry 4.1.2 4-20 snapshot and the one from 4-30? I tried
> > upgrading
> > > to
> > > > 4-30 and I just seem to hit one error after another. The first
> > problem
> > > > is an EventListener that used to work fine:
> > > >
> > > > @EventListener(targets="sessionData", events="onclick")
> > > > public void sessionDataClicked(IRequestCycle cycle)
> > > > {
> > > > setShowSessionData(true);
> > > > cycle.getResponseBuilder
> > ().updateComponent("theSessionData");
> > > > }
> > > >
> > > > The nested stack from that is:
> > > >
> > > > Caused by: org.apache.hivemind.ApplicationRuntimeException : No
> > > component
> > > > found in tree for EventListener binding with a matching
component id
> > > of
> > > > sessionData. [context:/WEB-INF/app/ErrorPage.html, line 1]
> > > > at
> > > >
> > > org.apache.tapestry.pageload.EventConnectionVisitor.visitComponent
> > (Event
> > > > ConnectionVisitor.java:51)
> > > > at
> > > >
> > >
> >
$IComponentVisitor_11248054e16.visitComponent($IComponentVisitor_1124805
> > > > 4e16.java)
> > > > at
> > > >
> > >
> >
$IComponentVisitor_11248054e17.visitComponent($IComponentVisitor_1124805
> > > > 4e17.java)
> > > > at
> > > >
> > >
org.apache.tapestry.pageload.ComponentTreeWalker.walkComponentTree(Compo
> > > > nentTreeWalker.java:45)
> > > > at
> > > >
> > > org.apache.tapestry.pageload.ComponentTreeWalker.walkComponentTree
> > (Compo
> > > > nentTreeWalker.java:57)
> > > > at
> > > > org.apache.tapestry.pageload.PageLoader.loadPage(PageLoader.java
> > :604)
> > > > at
> > > > $IPageLoader_11248054e04.loadPage($IPageLoader_11248054e04.java)
> > > > at
> > > > $IPageLoader_11248054e05.loadPage($IPageLoader_11248054e05.java)
> > > > at
> > > >
org.apache.tapestry.pageload.PageSource.getPage(PageSource.java:119)
> > > > at
> > > > $IPageSource_11248054d1c.getPage($IPageSource_11248054d1c.java)
> > > > at
> > > >
> > > org.apache.tapestry.engine.RequestCycle.loadPage(RequestCycle.java
> > :239)
> > > > at
> > > >
org.apache.tapestry.engine.RequestCycle.getPage(RequestCycle.java
> > :226)
> > > > at
> > > >
> > > org.apache.tapestry.error.ExceptionPresenterImpl.presentException
> > (Except
> > > > ionPresenterImpl.java:42)
> > > > ... 62 more
> > > >
> > > > After I commented that out I got another error for a Script:
> > > >
> > > > <span jwcid="@Script" script="/scripts/categoryHelper.script" />
> > > >
> > > > Caused by: org.apache.tapestry.util.xml.DocumentParseException:
> > Unable
> > > > to find resource classpath:/scripts/categoryHelper.script.
> > > > [classpath:/scripts/categoryHelper.script]
> > > > at
> > > >
> > > org.apache.tapestry.util.xml.RuleDirectedParser.parse
> > (RuleDirectedParser
> > > > .java:125)
> > > > at
> > > >
org.apache.tapestry.script.ScriptParser.parse(ScriptParser.java:112)
> > > > at
> > > >
> > > org.apache.tapestry.engine.DefaultScriptSource.parse
> > (DefaultScriptSource
> > > > .java:88)
> > > > ... 124 more
> > > >
> > > > I saw a minor change in JIRA to the way scripts are found but I
> > > couldn't
> > > > see how it would relate to this in particular.
> > > >
> > > > Thanks,
> > > > Ben
> > > >
> > > >
> >
---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > > > For additional commands, e-mail: users-help@tapestry.apache.org
> > > >
> > > >
> > >
> > >
> > > --
> > > Jesse Kuhnert
> > > Tapestry/Dojo team member/developer
> > >
> > > Open source based consulting work centered around
> > > dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
> > >
> > >
---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > > For additional commands, e-mail: users-help@tapestry.apache.org
> > >
> > >
> > >
> >
> >
> > --
> > Andreas Andreou - andyhot@apache.org - http://andyhot.di.uoa.gr
> > Tapestry / Tacos developer
> > Open Source / JEE Consulting
> >
>
>
>
> --
> Jesse Kuhnert
> Tapestry/Dojo team member/developer
>
> Open source based consulting work centered around
> dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
>
--
Jesse Kuhnert
Tapestry/Dojo team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: 4.1.2 snapshot changes 4-20 to 4-30
Posted by Jesse Kuhnert <jk...@gmail.com>.
A fix is deploying now for the @EventListener related issue. (though I'm
unsure if it fixes it for Ben but we'll see)
The script thing will have to happen later tonight.
On 5/1/07, Jesse Kuhnert <jk...@gmail.com> wrote:
>
> Yeah I'm aware of the issue, think it's fixed locally but am still testing
> the changes.
>
> On 5/1/07, Andreas Andreou < andyhot@di.uoa.gr> wrote:
> >
> > I think i've seen some similar issues in the latest snapshots...
> >
> > They indeed seem to be related to how components/pages are found, i'll
> > try
> > to have
> > a clean example demonstrating this and register a JIRA.
> >
> > For now, try using:
> >
> > <dependency>
> > <groupId>org.apache.tapestry</groupId>
> > <artifactId>tapestry-framework</artifactId>
> > <version>4.1.2-20070424.205219-56</version>
> > </dependency>
> >
> >
> >
> > On 5/1/07, Ben Dotte <bd...@widen.com> wrote:
> > >
> > > I tried the snapshots from this morning but unfortunately I still get
> > > the same EventListener error. For the script error I tried adding
> > > context: to the path like this:
> > >
> > > <span jwcid="@Script" script="context:/scripts/categoryHelper.script"
> > />
> > >
> > > But now the error I get for that is:
> > >
> > > Unable to parse script
> > >
> > classpath:collective/ui/components/context:/scripts/categoryHelper.scrip
> > > t.
> > >
> > > -----Original Message-----
> > > From: Jesse Kuhnert [mailto:jkuhnert@gmail.com ]
> > > Sent: Tuesday, May 01, 2007 9:33 AM
> > > To: Tapestry users
> > > Subject: Re: 4.1.2 snapshot changes 4-20 to 4-30
> > >
> > > There were two unrelated changes made. The @EventListener change
> > > involved
> > > some inevitable fundamental flaws that I think are all fully resolved
> > as
> > > of
> > > this mornings deployment of snapshots.
> > >
> > > The script error is related to how the component specs are being
> > > resolved,
> > > I'll look into why this is messing up for you but am sure that if you
> > > add
> > > either "context:" or "classpath:" in front of your string it will work
> > > correctly. (though I intended for it to work without them, so it's a
> > bug
> > > if
> > > it isn't working)
> > >
> > > On 5/1/07, Ben Dotte <bd...@widen.com> wrote:
> > > >
> > > > Were there some sort of fundamental changes that happened between
> > the
> > > > Tapestry 4.1.2 4-20 snapshot and the one from 4-30? I tried
> > upgrading
> > > to
> > > > 4-30 and I just seem to hit one error after another. The first
> > problem
> > > > is an EventListener that used to work fine:
> > > >
> > > > @EventListener(targets="sessionData", events="onclick")
> > > > public void sessionDataClicked(IRequestCycle cycle)
> > > > {
> > > > setShowSessionData(true);
> > > > cycle.getResponseBuilder
> > ().updateComponent("theSessionData");
> > > > }
> > > >
> > > > The nested stack from that is:
> > > >
> > > > Caused by: org.apache.hivemind.ApplicationRuntimeException : No
> > > component
> > > > found in tree for EventListener binding with a matching component id
> > > of
> > > > sessionData. [context:/WEB-INF/app/ErrorPage.html, line 1]
> > > > at
> > > >
> > > org.apache.tapestry.pageload.EventConnectionVisitor.visitComponent
> > (Event
> > > > ConnectionVisitor.java:51)
> > > > at
> > > >
> > >
> > $IComponentVisitor_11248054e16.visitComponent($IComponentVisitor_1124805
> > > > 4e16.java)
> > > > at
> > > >
> > >
> > $IComponentVisitor_11248054e17.visitComponent($IComponentVisitor_1124805
> > > > 4e17.java)
> > > > at
> > > >
> > > org.apache.tapestry.pageload.ComponentTreeWalker.walkComponentTree(Compo
> > > > nentTreeWalker.java:45)
> > > > at
> > > >
> > > org.apache.tapestry.pageload.ComponentTreeWalker.walkComponentTree
> > (Compo
> > > > nentTreeWalker.java:57)
> > > > at
> > > > org.apache.tapestry.pageload.PageLoader.loadPage(PageLoader.java
> > :604)
> > > > at
> > > > $IPageLoader_11248054e04.loadPage($IPageLoader_11248054e04.java)
> > > > at
> > > > $IPageLoader_11248054e05.loadPage($IPageLoader_11248054e05.java)
> > > > at
> > > > org.apache.tapestry.pageload.PageSource.getPage(PageSource.java:119)
> > > > at
> > > > $IPageSource_11248054d1c.getPage($IPageSource_11248054d1c.java)
> > > > at
> > > >
> > > org.apache.tapestry.engine.RequestCycle.loadPage(RequestCycle.java
> > :239)
> > > > at
> > > > org.apache.tapestry.engine.RequestCycle.getPage(RequestCycle.java
> > :226)
> > > > at
> > > >
> > > org.apache.tapestry.error.ExceptionPresenterImpl.presentException
> > (Except
> > > > ionPresenterImpl.java:42)
> > > > ... 62 more
> > > >
> > > > After I commented that out I got another error for a Script:
> > > >
> > > > <span jwcid="@Script" script="/scripts/categoryHelper.script" />
> > > >
> > > > Caused by: org.apache.tapestry.util.xml.DocumentParseException:
> > Unable
> > > > to find resource classpath:/scripts/categoryHelper.script.
> > > > [classpath:/scripts/categoryHelper.script]
> > > > at
> > > >
> > > org.apache.tapestry.util.xml.RuleDirectedParser.parse
> > (RuleDirectedParser
> > > > .java:125)
> > > > at
> > > > org.apache.tapestry.script.ScriptParser.parse(ScriptParser.java:112)
> > > > at
> > > >
> > > org.apache.tapestry.engine.DefaultScriptSource.parse
> > (DefaultScriptSource
> > > > .java:88)
> > > > ... 124 more
> > > >
> > > > I saw a minor change in JIRA to the way scripts are found but I
> > > couldn't
> > > > see how it would relate to this in particular.
> > > >
> > > > Thanks,
> > > > Ben
> > > >
> > > >
> > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > > > For additional commands, e-mail: users-help@tapestry.apache.org
> > > >
> > > >
> > >
> > >
> > > --
> > > Jesse Kuhnert
> > > Tapestry/Dojo team member/developer
> > >
> > > Open source based consulting work centered around
> > > dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > > For additional commands, e-mail: users-help@tapestry.apache.org
> > >
> > >
> > >
> >
> >
> > --
> > Andreas Andreou - andyhot@apache.org - http://andyhot.di.uoa.gr
> > Tapestry / Tacos developer
> > Open Source / JEE Consulting
> >
>
>
>
> --
> Jesse Kuhnert
> Tapestry/Dojo team member/developer
>
> Open source based consulting work centered around
> dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
>
--
Jesse Kuhnert
Tapestry/Dojo team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
Re: 4.1.2 snapshot changes 4-20 to 4-30
Posted by Jesse Kuhnert <jk...@gmail.com>.
Yeah I'm aware of the issue, think it's fixed locally but am still testing
the changes.
On 5/1/07, Andreas Andreou <an...@di.uoa.gr> wrote:
>
> I think i've seen some similar issues in the latest snapshots...
>
> They indeed seem to be related to how components/pages are found, i'll try
> to have
> a clean example demonstrating this and register a JIRA.
>
> For now, try using:
>
> <dependency>
> <groupId>org.apache.tapestry</groupId>
> <artifactId>tapestry-framework</artifactId>
> <version>4.1.2-20070424.205219-56</version>
> </dependency>
>
>
>
> On 5/1/07, Ben Dotte <bd...@widen.com> wrote:
> >
> > I tried the snapshots from this morning but unfortunately I still get
> > the same EventListener error. For the script error I tried adding
> > context: to the path like this:
> >
> > <span jwcid="@Script" script="context:/scripts/categoryHelper.script" />
> >
> > But now the error I get for that is:
> >
> > Unable to parse script
> > classpath:collective/ui/components/context:/scripts/categoryHelper.scrip
> > t.
> >
> > -----Original Message-----
> > From: Jesse Kuhnert [mailto:jkuhnert@gmail.com]
> > Sent: Tuesday, May 01, 2007 9:33 AM
> > To: Tapestry users
> > Subject: Re: 4.1.2 snapshot changes 4-20 to 4-30
> >
> > There were two unrelated changes made. The @EventListener change
> > involved
> > some inevitable fundamental flaws that I think are all fully resolved as
> > of
> > this mornings deployment of snapshots.
> >
> > The script error is related to how the component specs are being
> > resolved,
> > I'll look into why this is messing up for you but am sure that if you
> > add
> > either "context:" or "classpath:" in front of your string it will work
> > correctly. (though I intended for it to work without them, so it's a bug
> > if
> > it isn't working)
> >
> > On 5/1/07, Ben Dotte <bd...@widen.com> wrote:
> > >
> > > Were there some sort of fundamental changes that happened between the
> > > Tapestry 4.1.2 4-20 snapshot and the one from 4-30? I tried upgrading
> > to
> > > 4-30 and I just seem to hit one error after another. The first problem
> > > is an EventListener that used to work fine:
> > >
> > > @EventListener(targets="sessionData", events="onclick")
> > > public void sessionDataClicked(IRequestCycle cycle)
> > > {
> > > setShowSessionData(true);
> > > cycle.getResponseBuilder().updateComponent("theSessionData");
> > > }
> > >
> > > The nested stack from that is:
> > >
> > > Caused by: org.apache.hivemind.ApplicationRuntimeException: No
> > component
> > > found in tree for EventListener binding with a matching component id
> > of
> > > sessionData. [context:/WEB-INF/app/ErrorPage.html, line 1]
> > > at
> > >
> > org.apache.tapestry.pageload.EventConnectionVisitor.visitComponent(Event
> > > ConnectionVisitor.java:51)
> > > at
> > >
> > $IComponentVisitor_11248054e16.visitComponent($IComponentVisitor_1124805
> > > 4e16.java)
> > > at
> > >
> > $IComponentVisitor_11248054e17.visitComponent($IComponentVisitor_1124805
> > > 4e17.java)
> > > at
> > >
> > org.apache.tapestry.pageload.ComponentTreeWalker.walkComponentTree(Compo
> > > nentTreeWalker.java:45)
> > > at
> > >
> > org.apache.tapestry.pageload.ComponentTreeWalker.walkComponentTree(Compo
> > > nentTreeWalker.java:57)
> > > at
> > > org.apache.tapestry.pageload.PageLoader.loadPage(PageLoader.java:604)
> > > at
> > > $IPageLoader_11248054e04.loadPage($IPageLoader_11248054e04.java)
> > > at
> > > $IPageLoader_11248054e05.loadPage($IPageLoader_11248054e05.java)
> > > at
> > > org.apache.tapestry.pageload.PageSource.getPage(PageSource.java:119)
> > > at
> > > $IPageSource_11248054d1c.getPage($IPageSource_11248054d1c.java)
> > > at
> > >
> > org.apache.tapestry.engine.RequestCycle.loadPage(RequestCycle.java:239)
> > > at
> > > org.apache.tapestry.engine.RequestCycle.getPage(RequestCycle.java:226)
> > > at
> > >
> > org.apache.tapestry.error.ExceptionPresenterImpl.presentException(Except
> > > ionPresenterImpl.java:42)
> > > ... 62 more
> > >
> > > After I commented that out I got another error for a Script:
> > >
> > > <span jwcid="@Script" script="/scripts/categoryHelper.script" />
> > >
> > > Caused by: org.apache.tapestry.util.xml.DocumentParseException: Unable
> > > to find resource classpath:/scripts/categoryHelper.script.
> > > [classpath:/scripts/categoryHelper.script]
> > > at
> > >
> > org.apache.tapestry.util.xml.RuleDirectedParser.parse(RuleDirectedParser
> > > .java:125)
> > > at
> > > org.apache.tapestry.script.ScriptParser.parse(ScriptParser.java:112)
> > > at
> > >
> > org.apache.tapestry.engine.DefaultScriptSource.parse(DefaultScriptSource
> > > .java:88)
> > > ... 124 more
> > >
> > > I saw a minor change in JIRA to the way scripts are found but I
> > couldn't
> > > see how it would relate to this in particular.
> > >
> > > Thanks,
> > > Ben
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > > For additional commands, e-mail: users-help@tapestry.apache.org
> > >
> > >
> >
> >
> > --
> > Jesse Kuhnert
> > Tapestry/Dojo team member/developer
> >
> > Open source based consulting work centered around
> > dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: users-help@tapestry.apache.org
> >
> >
> >
>
>
> --
> Andreas Andreou - andyhot@apache.org - http://andyhot.di.uoa.gr
> Tapestry / Tacos developer
> Open Source / JEE Consulting
>
--
Jesse Kuhnert
Tapestry/Dojo team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
Re: 4.1.2 snapshot changes 4-20 to 4-30
Posted by Andreas Andreou <an...@di.uoa.gr>.
I think i've seen some similar issues in the latest snapshots...
They indeed seem to be related to how components/pages are found, i'll try
to have
a clean example demonstrating this and register a JIRA.
For now, try using:
<dependency>
<groupId>org.apache.tapestry</groupId>
<artifactId>tapestry-framework</artifactId>
<version>4.1.2-20070424.205219-56</version>
</dependency>
On 5/1/07, Ben Dotte <bd...@widen.com> wrote:
>
> I tried the snapshots from this morning but unfortunately I still get
> the same EventListener error. For the script error I tried adding
> context: to the path like this:
>
> <span jwcid="@Script" script="context:/scripts/categoryHelper.script" />
>
> But now the error I get for that is:
>
> Unable to parse script
> classpath:collective/ui/components/context:/scripts/categoryHelper.scrip
> t.
>
> -----Original Message-----
> From: Jesse Kuhnert [mailto:jkuhnert@gmail.com]
> Sent: Tuesday, May 01, 2007 9:33 AM
> To: Tapestry users
> Subject: Re: 4.1.2 snapshot changes 4-20 to 4-30
>
> There were two unrelated changes made. The @EventListener change
> involved
> some inevitable fundamental flaws that I think are all fully resolved as
> of
> this mornings deployment of snapshots.
>
> The script error is related to how the component specs are being
> resolved,
> I'll look into why this is messing up for you but am sure that if you
> add
> either "context:" or "classpath:" in front of your string it will work
> correctly. (though I intended for it to work without them, so it's a bug
> if
> it isn't working)
>
> On 5/1/07, Ben Dotte <bd...@widen.com> wrote:
> >
> > Were there some sort of fundamental changes that happened between the
> > Tapestry 4.1.2 4-20 snapshot and the one from 4-30? I tried upgrading
> to
> > 4-30 and I just seem to hit one error after another. The first problem
> > is an EventListener that used to work fine:
> >
> > @EventListener(targets="sessionData", events="onclick")
> > public void sessionDataClicked(IRequestCycle cycle)
> > {
> > setShowSessionData(true);
> > cycle.getResponseBuilder().updateComponent("theSessionData");
> > }
> >
> > The nested stack from that is:
> >
> > Caused by: org.apache.hivemind.ApplicationRuntimeException: No
> component
> > found in tree for EventListener binding with a matching component id
> of
> > sessionData. [context:/WEB-INF/app/ErrorPage.html, line 1]
> > at
> >
> org.apache.tapestry.pageload.EventConnectionVisitor.visitComponent(Event
> > ConnectionVisitor.java:51)
> > at
> >
> $IComponentVisitor_11248054e16.visitComponent($IComponentVisitor_1124805
> > 4e16.java)
> > at
> >
> $IComponentVisitor_11248054e17.visitComponent($IComponentVisitor_1124805
> > 4e17.java)
> > at
> >
> org.apache.tapestry.pageload.ComponentTreeWalker.walkComponentTree(Compo
> > nentTreeWalker.java:45)
> > at
> >
> org.apache.tapestry.pageload.ComponentTreeWalker.walkComponentTree(Compo
> > nentTreeWalker.java:57)
> > at
> > org.apache.tapestry.pageload.PageLoader.loadPage(PageLoader.java:604)
> > at
> > $IPageLoader_11248054e04.loadPage($IPageLoader_11248054e04.java)
> > at
> > $IPageLoader_11248054e05.loadPage($IPageLoader_11248054e05.java)
> > at
> > org.apache.tapestry.pageload.PageSource.getPage(PageSource.java:119)
> > at
> > $IPageSource_11248054d1c.getPage($IPageSource_11248054d1c.java)
> > at
> >
> org.apache.tapestry.engine.RequestCycle.loadPage(RequestCycle.java:239)
> > at
> > org.apache.tapestry.engine.RequestCycle.getPage(RequestCycle.java:226)
> > at
> >
> org.apache.tapestry.error.ExceptionPresenterImpl.presentException(Except
> > ionPresenterImpl.java:42)
> > ... 62 more
> >
> > After I commented that out I got another error for a Script:
> >
> > <span jwcid="@Script" script="/scripts/categoryHelper.script" />
> >
> > Caused by: org.apache.tapestry.util.xml.DocumentParseException: Unable
> > to find resource classpath:/scripts/categoryHelper.script.
> > [classpath:/scripts/categoryHelper.script]
> > at
> >
> org.apache.tapestry.util.xml.RuleDirectedParser.parse(RuleDirectedParser
> > .java:125)
> > at
> > org.apache.tapestry.script.ScriptParser.parse(ScriptParser.java:112)
> > at
> >
> org.apache.tapestry.engine.DefaultScriptSource.parse(DefaultScriptSource
> > .java:88)
> > ... 124 more
> >
> > I saw a minor change in JIRA to the way scripts are found but I
> couldn't
> > see how it would relate to this in particular.
> >
> > Thanks,
> > Ben
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: users-help@tapestry.apache.org
> >
> >
>
>
> --
> Jesse Kuhnert
> Tapestry/Dojo team member/developer
>
> Open source based consulting work centered around
> dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
>
--
Andreas Andreou - andyhot@apache.org - http://andyhot.di.uoa.gr
Tapestry / Tacos developer
Open Source / JEE Consulting
RE: 4.1.2 snapshot changes 4-20 to 4-30
Posted by Ben Dotte <bd...@widen.com>.
I tried the snapshots from this morning but unfortunately I still get
the same EventListener error. For the script error I tried adding
context: to the path like this:
<span jwcid="@Script" script="context:/scripts/categoryHelper.script" />
But now the error I get for that is:
Unable to parse script
classpath:collective/ui/components/context:/scripts/categoryHelper.scrip
t.
-----Original Message-----
From: Jesse Kuhnert [mailto:jkuhnert@gmail.com]
Sent: Tuesday, May 01, 2007 9:33 AM
To: Tapestry users
Subject: Re: 4.1.2 snapshot changes 4-20 to 4-30
There were two unrelated changes made. The @EventListener change
involved
some inevitable fundamental flaws that I think are all fully resolved as
of
this mornings deployment of snapshots.
The script error is related to how the component specs are being
resolved,
I'll look into why this is messing up for you but am sure that if you
add
either "context:" or "classpath:" in front of your string it will work
correctly. (though I intended for it to work without them, so it's a bug
if
it isn't working)
On 5/1/07, Ben Dotte <bd...@widen.com> wrote:
>
> Were there some sort of fundamental changes that happened between the
> Tapestry 4.1.2 4-20 snapshot and the one from 4-30? I tried upgrading
to
> 4-30 and I just seem to hit one error after another. The first problem
> is an EventListener that used to work fine:
>
> @EventListener(targets="sessionData", events="onclick")
> public void sessionDataClicked(IRequestCycle cycle)
> {
> setShowSessionData(true);
> cycle.getResponseBuilder().updateComponent("theSessionData");
> }
>
> The nested stack from that is:
>
> Caused by: org.apache.hivemind.ApplicationRuntimeException: No
component
> found in tree for EventListener binding with a matching component id
of
> sessionData. [context:/WEB-INF/app/ErrorPage.html, line 1]
> at
>
org.apache.tapestry.pageload.EventConnectionVisitor.visitComponent(Event
> ConnectionVisitor.java:51)
> at
>
$IComponentVisitor_11248054e16.visitComponent($IComponentVisitor_1124805
> 4e16.java)
> at
>
$IComponentVisitor_11248054e17.visitComponent($IComponentVisitor_1124805
> 4e17.java)
> at
>
org.apache.tapestry.pageload.ComponentTreeWalker.walkComponentTree(Compo
> nentTreeWalker.java:45)
> at
>
org.apache.tapestry.pageload.ComponentTreeWalker.walkComponentTree(Compo
> nentTreeWalker.java:57)
> at
> org.apache.tapestry.pageload.PageLoader.loadPage(PageLoader.java:604)
> at
> $IPageLoader_11248054e04.loadPage($IPageLoader_11248054e04.java)
> at
> $IPageLoader_11248054e05.loadPage($IPageLoader_11248054e05.java)
> at
> org.apache.tapestry.pageload.PageSource.getPage(PageSource.java:119)
> at
> $IPageSource_11248054d1c.getPage($IPageSource_11248054d1c.java)
> at
>
org.apache.tapestry.engine.RequestCycle.loadPage(RequestCycle.java:239)
> at
> org.apache.tapestry.engine.RequestCycle.getPage(RequestCycle.java:226)
> at
>
org.apache.tapestry.error.ExceptionPresenterImpl.presentException(Except
> ionPresenterImpl.java:42)
> ... 62 more
>
> After I commented that out I got another error for a Script:
>
> <span jwcid="@Script" script="/scripts/categoryHelper.script" />
>
> Caused by: org.apache.tapestry.util.xml.DocumentParseException: Unable
> to find resource classpath:/scripts/categoryHelper.script.
> [classpath:/scripts/categoryHelper.script]
> at
>
org.apache.tapestry.util.xml.RuleDirectedParser.parse(RuleDirectedParser
> .java:125)
> at
> org.apache.tapestry.script.ScriptParser.parse(ScriptParser.java:112)
> at
>
org.apache.tapestry.engine.DefaultScriptSource.parse(DefaultScriptSource
> .java:88)
> ... 124 more
>
> I saw a minor change in JIRA to the way scripts are found but I
couldn't
> see how it would relate to this in particular.
>
> Thanks,
> Ben
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
--
Jesse Kuhnert
Tapestry/Dojo team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: 4.1.2 snapshot changes 4-20 to 4-30
Posted by Jesse Kuhnert <jk...@gmail.com>.
There were two unrelated changes made. The @EventListener change involved
some inevitable fundamental flaws that I think are all fully resolved as of
this mornings deployment of snapshots.
The script error is related to how the component specs are being resolved,
I'll look into why this is messing up for you but am sure that if you add
either "context:" or "classpath:" in front of your string it will work
correctly. (though I intended for it to work without them, so it's a bug if
it isn't working)
On 5/1/07, Ben Dotte <bd...@widen.com> wrote:
>
> Were there some sort of fundamental changes that happened between the
> Tapestry 4.1.2 4-20 snapshot and the one from 4-30? I tried upgrading to
> 4-30 and I just seem to hit one error after another. The first problem
> is an EventListener that used to work fine:
>
> @EventListener(targets="sessionData", events="onclick")
> public void sessionDataClicked(IRequestCycle cycle)
> {
> setShowSessionData(true);
> cycle.getResponseBuilder().updateComponent("theSessionData");
> }
>
> The nested stack from that is:
>
> Caused by: org.apache.hivemind.ApplicationRuntimeException: No component
> found in tree for EventListener binding with a matching component id of
> sessionData. [context:/WEB-INF/app/ErrorPage.html, line 1]
> at
> org.apache.tapestry.pageload.EventConnectionVisitor.visitComponent(Event
> ConnectionVisitor.java:51)
> at
> $IComponentVisitor_11248054e16.visitComponent($IComponentVisitor_1124805
> 4e16.java)
> at
> $IComponentVisitor_11248054e17.visitComponent($IComponentVisitor_1124805
> 4e17.java)
> at
> org.apache.tapestry.pageload.ComponentTreeWalker.walkComponentTree(Compo
> nentTreeWalker.java:45)
> at
> org.apache.tapestry.pageload.ComponentTreeWalker.walkComponentTree(Compo
> nentTreeWalker.java:57)
> at
> org.apache.tapestry.pageload.PageLoader.loadPage(PageLoader.java:604)
> at
> $IPageLoader_11248054e04.loadPage($IPageLoader_11248054e04.java)
> at
> $IPageLoader_11248054e05.loadPage($IPageLoader_11248054e05.java)
> at
> org.apache.tapestry.pageload.PageSource.getPage(PageSource.java:119)
> at
> $IPageSource_11248054d1c.getPage($IPageSource_11248054d1c.java)
> at
> org.apache.tapestry.engine.RequestCycle.loadPage(RequestCycle.java:239)
> at
> org.apache.tapestry.engine.RequestCycle.getPage(RequestCycle.java:226)
> at
> org.apache.tapestry.error.ExceptionPresenterImpl.presentException(Except
> ionPresenterImpl.java:42)
> ... 62 more
>
> After I commented that out I got another error for a Script:
>
> <span jwcid="@Script" script="/scripts/categoryHelper.script" />
>
> Caused by: org.apache.tapestry.util.xml.DocumentParseException: Unable
> to find resource classpath:/scripts/categoryHelper.script.
> [classpath:/scripts/categoryHelper.script]
> at
> org.apache.tapestry.util.xml.RuleDirectedParser.parse(RuleDirectedParser
> .java:125)
> at
> org.apache.tapestry.script.ScriptParser.parse(ScriptParser.java:112)
> at
> org.apache.tapestry.engine.DefaultScriptSource.parse(DefaultScriptSource
> .java:88)
> ... 124 more
>
> I saw a minor change in JIRA to the way scripts are found but I couldn't
> see how it would relate to this in particular.
>
> Thanks,
> Ben
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
--
Jesse Kuhnert
Tapestry/Dojo team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com