Don,
You're right about there being only a two-way split. I've looked in
the archives and found as long ago as 2002 Howard described "invisible
instrumentation" as being "a term for how Tapestry HTML templates
maintain WYSIWYG editor compatibility". So, as you say, my 2nd and
3rd style
Well, Insert is a terrible name :-)
There's already OutputText (for formatted output). Perhaps FormatText
would have been a better name in retrospect.
On Fri, Jun 27, 2008 at 10:06 AM, Don Ryan <[EMAIL PROTECTED]> wrote:
>
> On 26 Jun 2008, at 20:28, Howard Lewis Ship wrote:
>
>> There's some ga
Hi, is there a T4 to T5 migration guide out there? Any links would be
helpfull.
Thanks.
..kace
--
View this message in context:
http://www.nabble.com/T4-to-T5-migration-guide-tp18162390p18162390.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
On 26 Jun 2008, at 20:28, Howard Lewis Ship wrote:
There's some gaps waiting to be filled (not abandoned, just
prioritized a bit lower than more urgent bug fixes).
That's great to hear. Thanks.
If you want to use T4 style, how about:
public class Output {
@Parameter (required=true)
On 26 Jun 2008, at 23:31, Geoff Callender wrote:
Are you sure? What about...
A
The core Output component in T5 has a required format parameter, so
the above will throw an exception. The Output component is useful for
things like dates and interpolating values into messages, but a
sligh
Workaround: put a
In fact I think I am confronted with two different issues :
1 - @Persist behavior
When I use a @Persist, I am aware that the object will only be kept in
'memory' between two request on the same page / component. So in my head I
thought that it was always the same object (the same instance of the
What happens if you then declare:
@ApplicationState
private SomeIntf a;
with no name, and you have two objects of the same type declared
elsewhere, with different names? Which object should "a" be resolved to?
Arguably, if it can't be resolved, tapestry would need to throw an
exception. Fine.
Ideally, we'd be able to recover the generics information, but the
Java implementation of generics makes that very hard to accomplish.
Type erasure and all that.
I think the approach of creating sub-interfaces to "nail down" the
generic types is the best approach.
On Fri, Jun 27, 2008 at 7:08 AM,
This would be tricky, the information is somewhat compartmentalized
and the other problem is how to communicate the Event object to the
event handler method. We could change Event to expose the source
Component ... we could also change the EventWorker logic to see if the
sole parameter to an event
void onPrepare() { user = new UserImpl(); }
On Fri, Jun 27, 2008 at 8:02 AM, Kheldar666 <[EMAIL PROTECTED]> wrote:
>
> Yes, I know how to instantiate an Object in a onSetupRender phase for
> instance.
>
> But in the case of the BeanEditForm, the problem occurs when submitting.
> Maybe the BeanEdit
@Component(parameters={"onClick=message:key-name"})
But then your message would have to contain the javascript (as it
would for DH below).
But you could tweak DH's suggestion slightly:
@Component(parameters = {"onClick=confirmMessage"})
...
public String getConfirmMessage() {
return Stri
Is there any way to get the component that fired an event? I looked at the
documentation and the sources trying to find out, but no success.
IMHO it would be very intesresting for mixins. I have just wrote one that
uses Hibernate Validator to handle the form validation event automatically
a
Yes, I know how to instantiate an Object in a onSetupRender phase for
instance.
But in the case of the BeanEditForm, the problem occurs when submitting.
Maybe the BeanEditForm, on Submit, tries to create a new User before copying
all datas from the Form to the user's properties ?
So I think I do
Hello all,
I declared an ASO like that
@ApplicationState
private SomeIntf a ;
It works very well, and I can find this object across all my pages. But
then I declared another one :
@ApplicationState
private SomeIntf b ;
Following the way Java deals with templates, T5 considers that those tw
Em Fri, 27 Jun 2008 04:21:47 -0300, Francois Armand <[EMAIL PROTECTED]>
escreveu:
I faced exactly the same problem when I was playing with a personnal
beaneditor : at the end, the only solution I found was to copy&paste the
beanEditor class, change visibility to protected and add one or two
Hi,
This is version 5.0.13, and I turned off the auto commit,
false
Howard Lewis Ship wrote:
>
> Dependends on the version of Tapestry. Earlier versions included an
> automatic commit.
>
> On Thu, Jun 26, 2008 at 7:44 PM, Angelo Chen <[EMAIL PROTECTED]>
> wrote:
>>
>> Hi,
>>
>> As what I un
Dependends on the version of Tapestry. Earlier versions included an
automatic commit.
On Thu, Jun 26, 2008 at 7:44 PM, Angelo Chen <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> As what I understand now that transaction has to be committed to persist the
> objects, following is a diapatcher, there is no
There currently isn't a *global* mechanism to map an interface to a
class so that BeanEditForm can instantiate it for you.
Instead, you can add an event handler to your page for the prepare
event. This method is responsible for preparing the page for either
rendering a form, or submitting a form.
a possible solution is:
add to your application module class
public static void bind(ServiceBinder binder)
{
binder.bind(User.class, UserImpl.class);
}
2008/6/27 Kheldar666 <[EMAIL PROTECTED]>:
>
> Hello,
>
> When i use Tapestry, almost my Bean are Interfaces (ex : UserImpl
> implements
hi,
there was a conversation recently on this mailinglist.
please take a look at
http://tapestry-user.markmail.org/search/?q=#query:+page:11+mid:whqzqhu6pjvyjhca+state:results
g,
kris
"Marcelo Lotif" <[EMAIL PROTECTED]>
27.06.2008 13:30
Bitte antworten an
"Tapestry users"
An
"Tapestry u
Hello,
When i use Tapestry, almost my Bean are Interfaces (ex : UserImpl implements
User ). That causes me a problem sometimes, specially when using
BeanEditForm (ex : with @Parameter private User _user ).
When I submit the form after editing a User, I have this error :
Exception instantiating
I'm having a similar issue, with the @IncludeStylesheetLibrary. This
annotation inserts the script tag at the end of the page, but i need
to put it at the beginning...
There's any solution or at least a workaround for this?
On Fri, Jun 27, 2008 at 8:10 AM, lebenski <[EMAIL PROTECTED]> wrote:
>
>
Hi
This has been an issue for a while now - we're using prototype etc. to
manipulate elements in some of our pages but can't access it due to it being
loaded at the end of the page.
I have read on these forums before that javascript should be loaded at the
end of the page to increase load spee
hi, i'm curious how you handle situation when ajax request is being sent but
page fragment cannot be rendererd because it depends on session which has
expired in a meantime.
here is typical request flow in my application:
* users clicks actionLink linked with some zone
* acegi detects no creden
1. @Component(parameters = {"onClick=confirmMessage"})
public String getConfirmMessage() {
return messsage.get("key-name");
}
Just refer that, I haven't tried for it yet.
2. Or you can define your own binding prefix.
Thanks!
DH
- Original Message -
From: "滕训华" <[EMAIL PROTECTED]>
To
Thiago H. de Paula Figueiredo wrote:
[...]
Question to Howard: instead of having package visibility, could the
core components have methods with protected visibility? And could
their fields hava protected getters, so component subclasses can
access superclass' parameter values? Or the current
27 matches
Mail list logo