The exception relates to Java 6 in conjunction with javassist, the library used
for runtime class transformation. You can get it to work with a few
workarounds, see this old thread:
http://markmail.org/message/dyvvplkjkbedzopw
Cheers,
Peter
--
If you are not an intended recipient of this e-ma
I wondering is that any company interested to outsource projects to us?
-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
Hi All,
I've been racking my brain all day on this one so I probally have tunnel
vision but I am getting a weird exception when trying to create a pageLink
on tomcat 5.5, jdk 1.6.06. Maybe someone has come across this already. I'm
really not sure if this is a tomcat issue, a tapestry issue or my
Sorry, I do not have to run the PageTest,but it fails in my running
application.
Howard Lewis Ship 写道:
> Sounds like a bug; even putting Tapestry into crippled mode (suppress
> redirects enabled) you should be able to return a page instance.
>
> Does this fail in your running app, or only inside
Em Sat, 27 Dec 2008 11:04:20 -0300, Tomas Kolda
escreveu:
I made a workaround through Servlet filter.
You could also use a Tapestry RequestFilter, avoiding a servlet filter and
having all the Tapestry infrastructure. :)
--
Thiago H. de Paula Figueiredo
Independent Java consultant, deve
I'm sorry that I'm hammering on this code, while it's still probably a
work in progress.. (always available through im)
but I commented out the spring ContextLoaderListener, moved the filter
up to be first, and this seems to initialize properly at least for Jetty
(within eclipse). The next is
but this seems really really flaky, undeterministic and appserver
dependent..
If you really want to create a SpringContext/TapestryIoC love child :)
could you create a new ContextLoaderListener to replace spring's that
does what you want?
So that both the SpringContext and TapestryIoC are lo
On Mon, Dec 29, 2008 at 4:09 PM, Fernando Padilla wrote:
> I was expecting you would be working on this feature, but I really don't
> want to change the way I instantiate my spring context..
>
> Could you hook in something that allows me to turn off this new feature and
> have it be perfectly back
Howard Lewis Ship wrote:
Looks reasonable to me; another alternative is to assign the id
parameter of the zone to a value you know will be unique on the client
side. Sometimes having Tapestry provide a dynamic client id is not the
best approach.
How could that be done inside a component? The "
Sounds like a bug; even putting Tapestry into crippled mode (suppress
redirects enabled) you should be able to return a page instance.
Does this fail in your running app, or only inside PageTester?
2008/12/26 d0ng :
> It send a redirect response in my test because of the default value of
>
> SUPP
Looks reasonable to me; another alternative is to assign the id
parameter of the zone to a value you know will be unique on the client
side. Sometimes having Tapestry provide a dynamic client id is not the
best approach.
On Mon, Dec 29, 2008 at 4:03 PM, Joachim Van der Auwera
wrote:
> I have foun
I was expecting you would be working on this feature, but I really don't
want to change the way I instantiate my spring context..
Could you hook in something that allows me to turn off this new feature
and have it be perfectly backward compatible? Or if it finds an already
instantiated Spring
We need to figure out the order that the filters are initialized, so
that the Tapestry filter can be initialized first. I think just
listing it first in the web.xml may do the trick.
On Mon, Dec 29, 2008 at 4:00 PM, Fernando Padilla wrote:
> I just tried it, and it won't work like that :(
>
> Li
I have found there is a problem when creating a component which includes
a zone and that zone is after the actionlink which is used to update it.
In that case, the existing zone's getClientId() cannot be used to fill
in the zone id as this is initialized in the beginRender and that has
not yet a
I just tried it, and it won't work like that :(
Like I said, I use spring outside of tapestry. So I need a valid
working spring context before the first request ever gets to tapestry
filter..
Here is my exception when I comment out the normal ContextLoaderListener..
[Console output redire
Also, code that expects the ContextLoaderListener will STILL work,
because Tapestry uses the same code, ContextLoader, that CLL does ...
just a little differently.
On Mon, Dec 29, 2008 at 3:40 PM, Fernando Padilla wrote:
> I just tried to run with the latest tapestry-trunk, and I get this
> reall
This is a change in behavior from Tapestry 5.0; it was necessary in
order to coordinate Spring and Tapestry IoC. It is necessary to let
Tapestry initialize Spring and use Tapestry-specific subclasses of
XmlWebApplicationContext and DefaultListableBeanFactory, to hook in
the logic that allows Sprin
I just tried to run with the latest tapestry-trunk, and I get this
really nasty exception :( :(
I initialize my own spring context with a ContextLoaderListener, because
I need spring outside of tapestry. Why is tapestry attempting to create
a context?
2008-12-29 15:18:27,363 [main] ERROR org
I just tried to run with the latest tapestry-trunk, and I get this
really nasty exception :( :(
I initialize my own spring context with a ContextLoaderListener, because
I need spring outside of tapestry. Why is tapestry attempting to create
a context?
2008-12-29 15:18:27,363 [main] ERROR
I'll look into it shortly. Probably just a problem with the ANTLR grammar.
On Mon, Dec 29, 2008 at 1:43 PM, Fernando Padilla wrote:
> https://issues.apache.org/jira/browse/TAP5-425
>
> In our code we used some single letter properties. This used to work in
> tapestry 5.0.15 or so.. but when we u
https://issues.apache.org/jira/browse/TAP5-425
In our code we used some single letter properties. This used to work in
tapestry 5.0.15 or so.. but when we upgraded to 5.1-SNAPSHOT, tapestry
now fails at runtime with a very weird execption. Any clues to get this
fixed in tapestry would be app
dumb question: how do you get the selected elements out of the and that
> should work, but unfortunately then you wont have the option of a
> java.util.list like you do with the pallet.
>
>
> - Original Message -
> From: "rs1050"
> To: users@tapestry.apache.org
> Sent: Monday, 17 Nove
In the autocomplete mixin, the full string which is returned is always
returned as value.
Is there a way to make a distinction between the value which should be
selected and the information which is displayed?
In the original library, you can contain additional information in a
"span" tag, a
It's probably not showing all of the information since you specified a
width of 60. Increase that to 200 or so. I put long entries in select
boxes all the time without problem in IE7.
Norman Franke
Answering Service for Directors, Inc.
www.myasd.com
On Dec 29, 2008, at 5:51 AM, christian bös
Hi Everyone,
I'm a new Tapestry user. I like tapestry it's very easy to build java
webapplications. But i have one little problem.
I have a select with option in there. the options are bigger than the select
itself.
Here is a little sample:
Test
This is a long Test, bla bla
this is
You may be looking for the onSelected event for the button.
> -Original Message-
> From: Issah Grusi [mailto:issah.gr...@yahoo.com]
> Sent: Sunday, December 28, 2008 22:18
> To: users@tapestry.apache.org
> Subject: onSubmitButton() method not running - Tapestry5
>
> Folks!
> I have a subm
Hi
This would be very handy for Trails.
On Mon, Dec 29, 2008 at 2:31 AM, Joakim Olsson wrote:
> Great, issue created (https://issues.apache.org/jira/browse/TAP5-424).
>
> Could I work around it in any way by contributing something to
> ComponentResources or something like that in my module-clas
Hi Everyone,
I'm a new Tapestry user. I like tapestry it's very easy to build java
webapplications. But i have one little problem.
I have a select with option in there. the options are bigger than the select
itself.
Here is a little sample:
Test
This is a long Test, bla bla
this is
28 matches
Mail list logo
