thank you Howard!
Jessek wrote:
>
> Wasn't my idea, thank Howard for figuring it out. ;)
>
> On Fri, Feb 29, 2008 at 10:19 AM, Pai911 <[EMAIL PROTECTED]> wrote:
>>
>> For those who encountered this issue
>>
>> This issue ,as said by Jessek, is solved by "not" sharing Tapestry
>> related
>>
Wasn't my idea, thank Howard for figuring it out. ;)
On Fri, Feb 29, 2008 at 10:19 AM, Pai911 <[EMAIL PROTECTED]> wrote:
>
> For those who encountered this issue
>
> This issue ,as said by Jessek, is solved by "not" sharing Tapestry related
> library between multiple
>
> Tapestry applicatio
For those who encountered this issue
This issue ,as said by Jessek, is solved by "not" sharing Tapestry related
library between multiple
Tapestry application.
Thank you Jessek!
Jessek wrote:
>
> I think that Howard may have finally solved this mystery for us in
> this JIRA ticket https://i
I think that Howard may have finally solved this mystery for us in
this JIRA ticket https://issues.apache.org/jira/browse/TAPESTRY-2055 .
The summary of which is that it's an issue with how OGNL uses static
class state for certain things (like class resolvers), which may trip
applications up that
I forgot to mention that I am running "one web app" with two Tapestry
servlets
each with different path pattern
The dir structure is like this
tapestryadm.application
tapestryapplication.application
tapestryadm
--page
--component
--hivemodule.xml
tapestryapplication
--page
--co
