The maven site generation on my CI machine (which is running Linux) works
well while using the tapestry-component-report plugin. If I try to stage the
site on my windows development machine I encounter the following error
during
mvn site:stage -DstagingDirectory=C:\fullsite
..
[INFO] Cobert
You might not even need any chenillekit on this. I use:
Sebastian Hennebrueder wrote:
>
> Scot Mcphee schrieb:
>> Hello
>>
>> Does any one have a short recipe how to use a checkbox in a grid
>> component?
>>
>> What I need to do is fairly simple - let the use select (for example)
>> t
still working too.
This solution is weblogic specific but there might be similar ways for
Glasfish or Websphere.
raucha wrote:
>
> I tried both suggestions without success. Adding the parameter to the JVM
> prevents weblogic from starting and changing the system property in the
> AppMo
t; wrote:
>
>> i had the same problem with websphere... i had to add following JVM
>> parameter
>> -Djavax.xml.stream.XMLInputFactory=com.ctc.wstx.stax.WstxInputFactory
>>
>> with another version i had to drop the stax2 jar into a shared folder
>> because the
>> classloader
After upgrading from 5.0.18 to 5.1.0.5 my application fails to start when
deployed on a weblogic server. I think this has to do with the usage of Stax
in the TemplateParser. I have tried to override the implementation in my
weblogic-application.xml with
javax.xml.stream.XMLInputFactory
com.
; httpSession manually
>
> see also
> http://tapestry-user.markmail.org/search/?q=session+peter#query:session%20peter+page:1+mid:3rnavgdfcjlbvagc+state:results
>
> i'm still not sure if it's a bug or feature
>
> g,
> kris
>
>
>
>
> raucha
I try to upgrade an application from 5.0.18 to 5.1.0.5. After invalidating
the Session for the user logout I get the included Exception. Everything
works fine with 5.0.18 and I checked hat I do not invalidate the HttpSession
but invalidate the Tapestry Session via the injected
org.apache.tapestry5
