Petition, idea or something
Hi, i am a relative inexperienced developer. I have worked with a couple of presentation frameworks and there is a feature i would really like to have, that no framework i know has. Here the thing: sometimes i do not like to have getters and setters for all my classes because of my domain modeling. And also do not like to define a bean on the web tier for each class i want to create from the UI and then populate or create a model object from it (i think sometimes this is useful, but many times it is duplicated work). So what i would really like is to somehow define on the html pages, that certain parameters are part of the constructor of certain class. I just want you to know that i have no idea if this is possible, just would like to have it as a developer using a web framework. A very rough example would be something like this: So in my dreams :) this would do something like this: * Get the item class. * create a new instance (newItem) of that class using a constructor and using the first textfield as the first parameter. * invoke newItem.setValue1(...) or set via reflection the value defined on the second textfield. I know that there are lots of holes on this idea, but basically i think the idea is not very complicated. Maybe there is already a nice and simple solution to this, and i am not familiar with it. If not, i would like to know how hard would it be to implement, maybe i will give it a shot. Thanks for your time. Best regards. Manuel.
Re: Overriding default validation messages
Its ok, i did the same thing (exactly the same question), that how i know about the wiki now. :) On Wed, May 21, 2008 at 5:22 PM, Toby Hobson <[EMAIL PROTECTED]> wrote: > Sorry ... I should have looked at the wiki first > > Thanks Manuel > > Tob > > - Original Message ---- > From: Manuel Corrales <[EMAIL PROTECTED]> > To: Tapestry users ; Toby Hobson < > [EMAIL PROTECTED]> > Sent: Wednesday, 21 May, 2008 9:19:48 PM > Subject: Re: Overriding default validation messages > > I think this is the best way (if not the only) > > > http://wiki.apache.org/tapestry/Tapestry5HowToOverrideTheDefaultErrorMessageBanner > > Regards. > > On Wed, May 21, 2008 at 5:10 PM, Toby Hobson <[EMAIL PROTECTED]> > wrote: > > > Hi > > > > How do I change the default validation message for a validator i.e. I > want > > to change the message from "you must supply a value for is" to "x is > > required". I know how to do it for each property i.e. > > email-required-message=x but I'd like to change the default > > > > Thanks! > > > > Toby > > > > > > > >
Re: Overriding default validation messages
I think this is the best way (if not the only) http://wiki.apache.org/tapestry/Tapestry5HowToOverrideTheDefaultErrorMessageBanner Regards. On Wed, May 21, 2008 at 5:10 PM, Toby Hobson <[EMAIL PROTECTED]> wrote: > Hi > > How do I change the default validation message for a validator i.e. I want > to change the message from "you must supply a value for is" to "x is > required". I know how to do it for each property i.e. > email-required-message=x but I'd like to change the default > > Thanks! > > Toby > >
Re: Autocomplete component
Ok, thanks! On Tue, May 20, 2008 at 8:25 PM, Josh Canfield <[EMAIL PROTECTED]> wrote: > The Autocomplete calls toString on each of the objects that you > return, and that is the value that is set into your input box. > > You can check out the source for the component it's pretty short. > > http://tapestry.apache.org/tapestry5/apidocs/src-html/org/apache/tapestry/corelib/mixins/Autocomplete.html > > If you want more complex data to be displayed then you can extend the > class and implement the generateResponseMarkup method. As of 5.0.11 > extending the client side behavior when the user chooses a value is > not possible, as far as I could find. > > > Josh > > On Tue, May 20, 2008 at 4:06 PM, Manuel Corrales > <[EMAIL PROTECTED]> wrote: > > Hi, i have s doubt about autocomplete component. According to the > > documentation, you can return a list of any objects on the > > onProvideCompletions, my question is, when i choose a value, this value > is > > going to be the object from that list? or just a string and i have to > make a > > match beetwen the string and the real object? > > > > Thanks very much! > > > > > > -- > -- > TheDailyTube.com. Sign up and get the best new videos on the internet > delivered fresh to your inbox. > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Autocomplete component
Hi, i have s doubt about autocomplete component. According to the documentation, you can return a list of any objects on the onProvideCompletions, my question is, when i choose a value, this value is going to be the object from that list? or just a string and i have to make a match beetwen the string and the real object? Thanks very much!
Form with errors
Hi, i have a left menu with a link (Add new Item). When i press the link, i go to a form to create a new Item. If i have some server side validation error, the error messages are shown on the screen, but the issue is that if i press the Add new Item from the left menu, the form does not clean itself, i mean the errors are still there and the form have the values i was entering. Is this the right behavior? How can i do to get a new clean form each time i press the link? Thanks in advance!
Re: Little confused
Hi Filip, i have no @Property annotation on my Tapestry version. What
version are you using?
On Sat, May 17, 2008 at 7:55 PM, Filip S. Adamsen <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I've found the following pattern to work very well - at least I use it
> everywhere on several sites in production with no problems. :)
>
> @Property
> private Item item;
>
> // I have a form in my template with t:id="add"
> void onPrepareFromAdd() {
>if (null == item) item = new Item();
> }
>
> void onSuccessFromAdd() {
>// go about my business with the item
>...
>// I'd normally return here, but since you need
>// something done in onSubmit...
> }
>
> Object onSubmitFromAdd() {
>// do what you need to do
>return ...;
> }
>
> I sometimes persist the item if needed.
>
> Hope this helps.
>
> -Filip
>
>
> On 2008-05-17 16:01, Manuel Corrales wrote:
>
>> Hi, here is my problem. I have a bean on my java page, but i am not using
>> the beaneditorform component to create a new one. Acording to Alexander
>> book, the beaneditorform component can handle the initialization of the
>> bean, so you dont have to create one. As i am not using this component,
>> should i define the bean with a sentence like this:
>>
>> private Matafuego matafuego = new Matafuego();
>>
>> or should i create the new instance on the onActivate method?
>>
>> I tryied the first approach, but the bean is always the same (i guess
>> because of the page pooling mechanism). What is the right approach to
>> this?
>>
>> Thanks very much.
>>
>>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
Re: Little confused
Well, i think i am really screwing thnigs up. Very sorry for abusing of your
time, i have almost everything working ok. Thanks for your time!
On Sat, May 17, 2008 at 2:57 PM, Manuel Corrales <[EMAIL PROTECTED]>
wrote:
> Ok, me bothering again. Now when i have a validation error that was checked
> on the server side, the form is completely wiped out. Thats the normal
> behavior?
>
>
> On Sat, May 17, 2008 at 2:49 PM, Manuel Corrales <[EMAIL PROTECTED]>
> wrote:
>
>> Sorry, my mistake. The same code i posted but without initializing the
>> matafuego variable is working now. I still dont completely understand why
>> tapestry is not cleaning my matafuego variable.
>>
>> Thanks very much for your help!
>>
>>
>> On Sat, May 17, 2008 at 2:39 PM, Manuel Corrales <
>> [EMAIL PROTECTED]> wrote:
>>
>>> Ok, thanks. Probably this is some stupid begginer mistake, but i cant
>>> make this work. My class is this:
>>>
>>> public class NuevoMatafuego {
>>>
>>> private Matafuego matafuego = new Matafuego();
>>> @Inject
>>> private Messages messages;
>>> @Component
>>> private Form nuevoMatafuegoForm;
>>> @Component(id = "nroAparato")
>>> private TextField nroAparato;
>>>
>>> public SelectModel getTiposDeMatafuego() {
>>> return new EnumSelectModel(TipoMatafuego.class, messages);
>>> }
>>>
>>> public Matafuego getMatafuego() {
>>> return matafuego;
>>> }
>>>
>>> public void setMatafuego(Matafuego matafuego) {
>>> this.matafuego = matafuego;
>>> }
>>>
>>> void onActivate() {
>>> if (matafuego == null) {
>>> matafuego = new Matafuego();
>>> }
>>> }
>>>
>>> @OnEvent(value = "submit", component = "nuevoMatafuegoForm")
>>> Object onSubmitNuevoMatafuegoForm() {
>>> MatafuegoFacade facade = new MatafuegoFacade();
>>> try {
>>> facade.guardarMatafuego(matafuego);
>>> matafuego = null;
>>> return MainMatafuegos.class;
>>> } catch ( ConstraintViolationException e) {
>>> nuevoMatafuegoForm.recordError(nroAparato,
>>> messages.get("matafuegoDuplicado"));
>>> return this;
>>> }
>>> }
>>>
>>> }
>>>
>>>
>>> As you can see, the matafuego instance is not @Persist, so i really do
>>> not undestand why is not being cleared. Also if instead of doing Matafuego
>>> matafuego = new Matafuego(); on the declaration, i dont initialize it, then
>>> when i try to save it, it is null in the onSubmit method.
>>>
>>> Any suggestion?
>>>
>>>
>>> On Sat, May 17, 2008 at 1:51 PM, Kevin Menard <[EMAIL PROTECTED]>
>>> wrote:
>>>
>>>> It doesn't really matter where you clear it. Just clear it when you're
>>>> done
>>>> with it. As for the lifecycle question, you have to clear it because
>>>> you
>>>> @Persisted it. If you didn't @Persist it, you wouldn't have to clear
>>>> it,
>>>> but you'd likely lose your data when working with the form, depending on
>>>> your workflow.
>>>>
>>>> This should work fine. I do it all the time.
>>>>
>>>> --
>>>> Kevin
>>>>
>>>>
>>>> On 5/17/08 12:34 PM, "Manuel Corrales" <[EMAIL PROTECTED]>
>>>> wrote:
>>>>
>>>> > Hi Ned, the onSuccess methos is executed before the onSubmit, so that
>>>> would
>>>> > not work for me because i am doing the model logic on the onSubmit. I
>>>> tryed
>>>> > setting my variable in null after executing my businnes logic, but i
>>>> still
>>>> > have the same issue. My private variable should not be cleaned by
>>>> Tapestry
>>>> > pooling mechanism?
>>>> >
>>>> > The only thing i can think to fix this, is to set my variable to null
>>>> after
>>>> > the bussines logic, and then on the onACtivate method check if its
>>>> null, the
>>>> > i create a new one, if its not null then i do nothing.
>>>> >
>>>> > Thanks, and still waiting for an elegant solution to this ;)
>>>> > **
>>>>
>>>>
>>>> -
>>>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>>>> For additional commands, e-mail: [EMAIL PROTECTED]
>>>>
>>>>
>>>
>>
>
Re: Little confused
Ok, me bothering again. Now when i have a validation error that was checked
on the server side, the form is completely wiped out. Thats the normal
behavior?
On Sat, May 17, 2008 at 2:49 PM, Manuel Corrales <[EMAIL PROTECTED]>
wrote:
> Sorry, my mistake. The same code i posted but without initializing the
> matafuego variable is working now. I still dont completely understand why
> tapestry is not cleaning my matafuego variable.
>
> Thanks very much for your help!
>
>
> On Sat, May 17, 2008 at 2:39 PM, Manuel Corrales <[EMAIL PROTECTED]>
> wrote:
>
>> Ok, thanks. Probably this is some stupid begginer mistake, but i cant make
>> this work. My class is this:
>>
>> public class NuevoMatafuego {
>>
>> private Matafuego matafuego = new Matafuego();
>> @Inject
>> private Messages messages;
>> @Component
>> private Form nuevoMatafuegoForm;
>> @Component(id = "nroAparato")
>> private TextField nroAparato;
>>
>> public SelectModel getTiposDeMatafuego() {
>> return new EnumSelectModel(TipoMatafuego.class, messages);
>> }
>>
>> public Matafuego getMatafuego() {
>> return matafuego;
>> }
>>
>> public void setMatafuego(Matafuego matafuego) {
>> this.matafuego = matafuego;
>> }
>>
>> void onActivate() {
>> if (matafuego == null) {
>> matafuego = new Matafuego();
>> }
>> }
>>
>> @OnEvent(value = "submit", component = "nuevoMatafuegoForm")
>> Object onSubmitNuevoMatafuegoForm() {
>> MatafuegoFacade facade = new MatafuegoFacade();
>> try {
>> facade.guardarMatafuego(matafuego);
>> matafuego = null;
>> return MainMatafuegos.class;
>> } catch ( ConstraintViolationException e) {
>> nuevoMatafuegoForm.recordError(nroAparato,
>> messages.get("matafuegoDuplicado"));
>> return this;
>> }
>> }
>>
>> }
>>
>>
>> As you can see, the matafuego instance is not @Persist, so i really do not
>> undestand why is not being cleared. Also if instead of doing Matafuego
>> matafuego = new Matafuego(); on the declaration, i dont initialize it, then
>> when i try to save it, it is null in the onSubmit method.
>>
>> Any suggestion?
>>
>>
>> On Sat, May 17, 2008 at 1:51 PM, Kevin Menard <[EMAIL PROTECTED]>
>> wrote:
>>
>>> It doesn't really matter where you clear it. Just clear it when you're
>>> done
>>> with it. As for the lifecycle question, you have to clear it because you
>>> @Persisted it. If you didn't @Persist it, you wouldn't have to clear it,
>>> but you'd likely lose your data when working with the form, depending on
>>> your workflow.
>>>
>>> This should work fine. I do it all the time.
>>>
>>> --
>>> Kevin
>>>
>>>
>>> On 5/17/08 12:34 PM, "Manuel Corrales" <[EMAIL PROTECTED]> wrote:
>>>
>>> > Hi Ned, the onSuccess methos is executed before the onSubmit, so that
>>> would
>>> > not work for me because i am doing the model logic on the onSubmit. I
>>> tryed
>>> > setting my variable in null after executing my businnes logic, but i
>>> still
>>> > have the same issue. My private variable should not be cleaned by
>>> Tapestry
>>> > pooling mechanism?
>>> >
>>> > The only thing i can think to fix this, is to set my variable to null
>>> after
>>> > the bussines logic, and then on the onACtivate method check if its
>>> null, the
>>> > i create a new one, if its not null then i do nothing.
>>> >
>>> > Thanks, and still waiting for an elegant solution to this ;)
>>> > **
>>>
>>>
>>> -
>>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>>> For additional commands, e-mail: [EMAIL PROTECTED]
>>>
>>>
>>
>
Re: Little confused
Sorry, my mistake. The same code i posted but without initializing the
matafuego variable is working now. I still dont completely understand why
tapestry is not cleaning my matafuego variable.
Thanks very much for your help!
On Sat, May 17, 2008 at 2:39 PM, Manuel Corrales <[EMAIL PROTECTED]>
wrote:
> Ok, thanks. Probably this is some stupid begginer mistake, but i cant make
> this work. My class is this:
>
> public class NuevoMatafuego {
>
> private Matafuego matafuego = new Matafuego();
> @Inject
> private Messages messages;
> @Component
> private Form nuevoMatafuegoForm;
> @Component(id = "nroAparato")
> private TextField nroAparato;
>
> public SelectModel getTiposDeMatafuego() {
> return new EnumSelectModel(TipoMatafuego.class, messages);
> }
>
> public Matafuego getMatafuego() {
> return matafuego;
> }
>
> public void setMatafuego(Matafuego matafuego) {
> this.matafuego = matafuego;
> }
>
> void onActivate() {
> if (matafuego == null) {
> matafuego = new Matafuego();
> }
> }
>
> @OnEvent(value = "submit", component = "nuevoMatafuegoForm")
> Object onSubmitNuevoMatafuegoForm() {
> MatafuegoFacade facade = new MatafuegoFacade();
> try {
> facade.guardarMatafuego(matafuego);
> matafuego = null;
> return MainMatafuegos.class;
> } catch ( ConstraintViolationException e) {
> nuevoMatafuegoForm.recordError(nroAparato,
> messages.get("matafuegoDuplicado"));
> return this;
> }
> }
>
> }
>
>
> As you can see, the matafuego instance is not @Persist, so i really do not
> undestand why is not being cleared. Also if instead of doing Matafuego
> matafuego = new Matafuego(); on the declaration, i dont initialize it, then
> when i try to save it, it is null in the onSubmit method.
>
> Any suggestion?
>
>
> On Sat, May 17, 2008 at 1:51 PM, Kevin Menard <[EMAIL PROTECTED]>
> wrote:
>
>> It doesn't really matter where you clear it. Just clear it when you're
>> done
>> with it. As for the lifecycle question, you have to clear it because you
>> @Persisted it. If you didn't @Persist it, you wouldn't have to clear it,
>> but you'd likely lose your data when working with the form, depending on
>> your workflow.
>>
>> This should work fine. I do it all the time.
>>
>> --
>> Kevin
>>
>>
>> On 5/17/08 12:34 PM, "Manuel Corrales" <[EMAIL PROTECTED]> wrote:
>>
>> > Hi Ned, the onSuccess methos is executed before the onSubmit, so that
>> would
>> > not work for me because i am doing the model logic on the onSubmit. I
>> tryed
>> > setting my variable in null after executing my businnes logic, but i
>> still
>> > have the same issue. My private variable should not be cleaned by
>> Tapestry
>> > pooling mechanism?
>> >
>> > The only thing i can think to fix this, is to set my variable to null
>> after
>> > the bussines logic, and then on the onACtivate method check if its null,
>> the
>> > i create a new one, if its not null then i do nothing.
>> >
>> > Thanks, and still waiting for an elegant solution to this ;)
>> > **
>>
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
Re: Little confused
Ok, thanks. Probably this is some stupid begginer mistake, but i cant make
this work. My class is this:
public class NuevoMatafuego {
private Matafuego matafuego = new Matafuego();
@Inject
private Messages messages;
@Component
private Form nuevoMatafuegoForm;
@Component(id = "nroAparato")
private TextField nroAparato;
public SelectModel getTiposDeMatafuego() {
return new EnumSelectModel(TipoMatafuego.class, messages);
}
public Matafuego getMatafuego() {
return matafuego;
}
public void setMatafuego(Matafuego matafuego) {
this.matafuego = matafuego;
}
void onActivate() {
if (matafuego == null) {
matafuego = new Matafuego();
}
}
@OnEvent(value = "submit", component = "nuevoMatafuegoForm")
Object onSubmitNuevoMatafuegoForm() {
MatafuegoFacade facade = new MatafuegoFacade();
try {
facade.guardarMatafuego(matafuego);
matafuego = null;
return MainMatafuegos.class;
} catch ( ConstraintViolationException e) {
nuevoMatafuegoForm.recordError(nroAparato,
messages.get("matafuegoDuplicado"));
return this;
}
}
}
As you can see, the matafuego instance is not @Persist, so i really do not
undestand why is not being cleared. Also if instead of doing Matafuego
matafuego = new Matafuego(); on the declaration, i dont initialize it, then
when i try to save it, it is null in the onSubmit method.
Any suggestion?
On Sat, May 17, 2008 at 1:51 PM, Kevin Menard <[EMAIL PROTECTED]> wrote:
> It doesn't really matter where you clear it. Just clear it when you're
> done
> with it. As for the lifecycle question, you have to clear it because you
> @Persisted it. If you didn't @Persist it, you wouldn't have to clear it,
> but you'd likely lose your data when working with the form, depending on
> your workflow.
>
> This should work fine. I do it all the time.
>
> --
> Kevin
>
>
> On 5/17/08 12:34 PM, "Manuel Corrales" <[EMAIL PROTECTED]> wrote:
>
> > Hi Ned, the onSuccess methos is executed before the onSubmit, so that
> would
> > not work for me because i am doing the model logic on the onSubmit. I
> tryed
> > setting my variable in null after executing my businnes logic, but i
> still
> > have the same issue. My private variable should not be cleaned by
> Tapestry
> > pooling mechanism?
> >
> > The only thing i can think to fix this, is to set my variable to null
> after
> > the bussines logic, and then on the onACtivate method check if its null,
> the
> > i create a new one, if its not null then i do nothing.
> >
> > Thanks, and still waiting for an elegant solution to this ;)
> > **
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
Re: Little confused
Hi Ned, the onSuccess methos is executed before the onSubmit, so that would
not work for me because i am doing the model logic on the onSubmit. I tryed
setting my variable in null after executing my businnes logic, but i still
have the same issue. My private variable should not be cleaned by Tapestry
pooling mechanism?
The only thing i can think to fix this, is to set my variable to null after
the bussines logic, and then on the onACtivate method check if its null, the
i create a new one, if its not null then i do nothing.
Thanks, and still waiting for an elegant solution to this ;)
**
On Sat, May 17, 2008 at 12:12 PM, Ned Jackson Lovely <[EMAIL PROTECTED]> wrote:
> Set your private variable to null in your onSuccess function.
>
> On 5/17/08, Manuel Corrales <[EMAIL PROTECTED]> wrote:
> > Thanks for your answer, but i still have the same issue. Maybe i am not
> > explaining the problem ok. I have a page with a link, when i press the
> link
> > the application goes to the new Matafuego page, where i am using a "hand
> > made form" (i mean not using beaneditorform tag). The first time i do
> this,
> > everything works fine, i complete the date press Save and the application
> > redirects to the main page again. But the second time i press the link to
> > add a new Matafuego, the form has the data i complete on the first one.
> The
> > behavior i am looking here, is that each time i access the form, i create
> a
> > new Matafuego, i mean a clean form and a new Matafuego instance.
> >
> > Thanks in advance.
> >
> > On Sat, May 17, 2008 at 11:54 AM, Kevin Menard <[EMAIL PROTECTED]>
> > wrote:
> >
> >> I would probably use a lazy getter with a @Persist attached to the
> field.
> >>
> >> Something like:
> >>
> >> @Persist
> >> private Matafuego matafuego;
> >>
> >> public Metafuego getMetafuego()
> >> {
> >> if (null == metafuego)
> >> {
> >> metafuego = new Metafuego();
> >> }
> >>
> >> return metafuego;
> >> }
> >>
> >> The page instance is guaranteed to be accessed by only a single thread
> at
> >> a
> >> time, so that should be safe for you.
> >>
> >> --
> >> Kevin
> >>
> >>
> >> On 5/17/08 10:01 AM, "Manuel Corrales" <[EMAIL PROTECTED]>
> wrote:
> >>
> >> > Hi, here is my problem. I have a bean on my java page, but i am not
> >> > using
> >> > the beaneditorform component to create a new one. Acording to
> Alexander
> >> > book, the beaneditorform component can handle the initialization of
> the
> >> > bean, so you dont have to create one. As i am not using this
> component,
> >> > should i define the bean with a sentence like this:
> >> >
> >> > private Matafuego matafuego = new Matafuego();
> >> >
> >> > or should i create the new instance on the onActivate method?
> >> >
> >> > I tryied the first approach, but the bean is always the same (i guess
> >> > because of the page pooling mechanism). What is the right approach to
> >> this?
> >> >
> >> > Thanks very much.
> >>
> >>
> >> -
> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
> >> For additional commands, e-mail: [EMAIL PROTECTED]
> >>
> >>
> >
>
>
> --
> njl
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
Re: Little confused
Thanks for your answer, but i still have the same issue. Maybe i am not
explaining the problem ok. I have a page with a link, when i press the link
the application goes to the new Matafuego page, where i am using a "hand
made form" (i mean not using beaneditorform tag). The first time i do this,
everything works fine, i complete the date press Save and the application
redirects to the main page again. But the second time i press the link to
add a new Matafuego, the form has the data i complete on the first one. The
behavior i am looking here, is that each time i access the form, i create a
new Matafuego, i mean a clean form and a new Matafuego instance.
Thanks in advance.
On Sat, May 17, 2008 at 11:54 AM, Kevin Menard <[EMAIL PROTECTED]>
wrote:
> I would probably use a lazy getter with a @Persist attached to the field.
>
> Something like:
>
> @Persist
> private Matafuego matafuego;
>
> public Metafuego getMetafuego()
> {
> if (null == metafuego)
> {
> metafuego = new Metafuego();
> }
>
> return metafuego;
> }
>
> The page instance is guaranteed to be accessed by only a single thread at a
> time, so that should be safe for you.
>
> --
> Kevin
>
>
> On 5/17/08 10:01 AM, "Manuel Corrales" <[EMAIL PROTECTED]> wrote:
>
> > Hi, here is my problem. I have a bean on my java page, but i am not using
> > the beaneditorform component to create a new one. Acording to Alexander
> > book, the beaneditorform component can handle the initialization of the
> > bean, so you dont have to create one. As i am not using this component,
> > should i define the bean with a sentence like this:
> >
> > private Matafuego matafuego = new Matafuego();
> >
> > or should i create the new instance on the onActivate method?
> >
> > I tryied the first approach, but the bean is always the same (i guess
> > because of the page pooling mechanism). What is the right approach to
> this?
> >
> > Thanks very much.
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
Little confused
Hi, here is my problem. I have a bean on my java page, but i am not using the beaneditorform component to create a new one. Acording to Alexander book, the beaneditorform component can handle the initialization of the bean, so you dont have to create one. As i am not using this component, should i define the bean with a sentence like this: private Matafuego matafuego = new Matafuego(); or should i create the new instance on the onActivate method? I tryied the first approach, but the bean is always the same (i guess because of the page pooling mechanism). What is the right approach to this? Thanks very much.
Re: Localization of default messages
Thank you very much! On Tue, Apr 29, 2008 at 9:11 AM, Michael Gerzabek <[EMAIL PROTECTED]> wrote: > Manuel, > > you simply put > org.apache.tapestry.corelib.components.Errors_es.properties (I suppose) in > your resources. If you use the maven archetype this should be > PROJECT_HOME/src/main/resources > > > Manuel Corrales schrieb: > > Hi, i was checking the documentation but was not able to find how can i > > do > > to change the default messages. For instance, when you use a beanform or > > a > > t:errors, you get a default heading text saying something like: "You > > should > > fix the next errors" :P or when you insert a non parseable date on a > > DateField you get also an implicit validation error. How can i changes > > this > > texts, so my application is completely localized? > > > > Best regards and thanks in advance! > > > > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Localization of default messages
Hi, i was checking the documentation but was not able to find how can i do to change the default messages. For instance, when you use a beanform or a t:errors, you get a default heading text saying something like: "You should fix the next errors" :P or when you insert a non parseable date on a DateField you get also an implicit validation error. How can i changes this texts, so my application is completely localized? Best regards and thanks in advance!
Re: CSS styles override
Thanks! On Tue, Apr 29, 2008 at 5:52 AM, Christian Köberl < [EMAIL PROTECTED]> wrote: > > > Manuel Corrales-2 wrote: > > > > I wonder if there is any way of skip the default style or if there is > > a reset style, because i am finding not to easy to override the default > > style, so i think it would be great to have some way of disable it or at > > least provide some reset css style. > > > See configuration symbol "tapestry.default-stylesheet" in > http://tapestry.apache.org/tapestry5/tapestry-core/guide/conf.html > > Cheers, > Chris > > -- > View this message in context: > http://www.nabble.com/CSS-styles-override-tp16941288p16955742.html > Sent from the Tapestry - User mailing list archive at Nabble.com. > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Re: multiple context values
I think you can separate the values with commas like this: t:context="p.productId, p.categoryId" Good luck! On Mon, Apr 28, 2008 at 12:53 PM, Leon Derks <[EMAIL PROTECTED]> wrote: > How can I add multiple context values to an actionlink? > > For example a productId and a categoryId? > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Re: CSS styles override
I am attaching the style i am using a sample page and a screenshot of the
problem (of the page i attach). This is just a prototype, but illustrates
the problem. As you can see, the labels of the form are placed below, just
when the left menu ends. How can i fix this?
Best regards and thanks in advance!!
On Mon, Apr 28, 2008 at 12:21 PM, Manuel Corrales <[EMAIL PROTECTED]>
wrote:
> Hi, i am starting a fresh project and after reading the tutorial and a
> trying Tapestry 5 i am loving it. It is a fantastic framework, and works
> like a charm!!!
> I am having only one issue, i would like to fix. I am having some weird
> behavior, trying to adapt my page style along with the default tapestry
> style. I wonder if there is any way of skip the default style or if there is
> a reset style, because i am finding not to easy to override the default
> style, so i think it would be great to have some way of disable it or at
> least provide some reset css style.
>
> Again, i am in love with this framework and will be using it on my
> projects from now on.
> Congratulations and keep the great work.
>
> Best regards.
>
> Manuel.
>
body {
line-height: 1;
color: black;
background: white;
}
ol, ul {
list-style: none;
}
/* tables still need 'cellspacing="0"' in the markup */
table {
border-collapse: separate;
border-spacing: 0;
}
caption, th, td {
text-align: left;
font-weight: normal;
}
blockquote:before, blockquote:after,
q:before, q:after {
content: "";
}
blockquote, q {
quotes: "" "";
}
/***
* TITLE: Common Stylesheet for Blue Haze *
* URI : http://www.oswd.org/design/xxx/bluehaze/bluehaze.css *
* MODIF: 2003-01-05 1608 +0800*
***/
/* ## Browser-specific Styles ## */
/* For IE & Mozilla-based browsers: */
.LHS {
margin-left: 2.5mm;
float: left;
clear: left;
}
.RHS {
margin-right: 2.5mm;
float: right;
clear: right;
}
/* For Mozilla-based (CSS2-fully complaint) browsers only: */
[class~="LHS"] {
margin-left: 5mm;
}
[class~="RHS"] {
margin-right: 5mm;
}
/* ## Body Text ## */
body {
background-color: white;
color: black;
font-family: verdana, tahoma, helvetica, arial, sans-serif;
font-size: 95%;
margin: 0;
background-repeat: no-repeat;
background-attachment: scroll;
}
h1, h2, h3 {
font-family: "trebuchet ms", tahoma, sans-serif;
}
h1 {
font-weight: bold;
font-size: 150%;
border-bottom-style: solid;
border-bottom-width: 1px;
padding-bottom: 0.5ex;
}
img {
border: none;
}
q {
font-family: tahoma, verdana, helvetica, arial, sans-serif;
font-weight: bold;
border-style: dotted;
border-width: 2px;
margin: 0 1em 1ex 1em;
padding: 0.5ex 0.5ex 0.5ex 1ex;
width: 9em;
float: left;
}
acronym {
border-bottom-style: dotted;
border-bottom-width: 1px;
cursor: help;
}
code {
font-family: "lucida console", monospace;
font-size: 90%;
}
dt {
font-weight: bold;
}
dd {
padding-bottom: 1.5em;
}
#bodyText {
text-align: justify;
line-height: 1.5em;
margin: 10mm 5mm 0 14em;
padding: 0 1em 1ex 1em;
}
#bodyText p {
padding-bottom: 2ex;
}
#bodyText a {
text-decoration: none;
border-bottom-style: solid;
border-bottom-width: 1px;
}
#bodyText a:hover {
border-bottom: none;
}
#bodyText .topOfPage {
font-size: 90%;
font-weight: bold;
font-variant: small-caps;
text-decoration: none;
border: none;
padding-left: 1ex;
padding-right: 1ex;
float: right;
}
.smallCaps {
font-variant: small-caps;
}
/* ## Header ## */
#header {
border-bottom-style: solid;
border-bottom-width: 2px;
height: 7.5em;
margin-bottom: 5mm;
padding: 0 2.5mm 0 5mm;
background-repeat: no-repeat;
}
.headerTitle {
font-size: 300%;
font-weight: bold;
line-height: 2em;
}
.menuBar {
float: left;
}
.locBar {
float: right;
}
.menuBar *, .locBar * {
text-decoration: none;
font-weight: bold;
padding-right: 1ex;
}
.menuBar a:hover, .locBar a:hover {
text-decoration: underline;
}
/* ## Side Box ## */
.sideBox {
border-style: solid none solid none;
border-width: 2px 0 2px 0;
width: 11em;
margin-top: 5mm;
}
.sideBox div {
font-weight: bold;
border-bottom-style: dashed;
border-bottom-width: 1px;
padding: 0.5ex 0.5em 0.5ex 0.75em;
}
.sideBox a, .sideBox a:hover, .sideBox span {
color: black;
text-decoration: none;
line-height: 1.25em;
display: block;
padding: 1.25ex 0.5em 1.25ex 0.75em;
}
.sideBox .thisPage {
font-weight: bold;
}
/* ## Footer ## */
#footer {
padding-top: 0.75ex;
padding-bottom: 0.75ex;
clear: left;
}
#footer div {
font-size: 8
CSS styles override
Hi, i am starting a fresh project and after reading the tutorial and a trying Tapestry 5 i am loving it. It is a fantastic framework, and works like a charm!!! I am having only one issue, i would like to fix. I am having some weird behavior, trying to adapt my page style along with the default tapestry style. I wonder if there is any way of skip the default style or if there is a reset style, because i am finding not to easy to override the default style, so i think it would be great to have some way of disable it or at least provide some reset css style. Again, i am in love with this framework and will be using it on my projects from now on. Congratulations and keep the great work. Best regards. Manuel.
