On Tue, 03 Jan 2012 16:33:59 -0200, felipexz wrote:
Yes of course I agree. But when you have Annotated fields, it can be
instatiated in other classes, can't be ?
Remember: instantiate a class = using the Java "new" operator.
How I would know that it's not already been instatiated ? That's a
On Tue, 03 Jan 2012 16:02:50 -0200, felipexz wrote:
Hi Sven.. I read it but the method on"Something" is a convention ?
Sorry but I'm new on Tapestry so I don't know.
Yes: http://tapestry.apache.org/component-events.html
I only found about the "onPrepare" in the wiki
http://wiki.apache.org/t
Yes of course I agree. But when you have Annotated fields, it can be
instatiated in other classes, can't be ?
How I would know that it's not already been instatiated ? That's an
annotated field.
I'm justing asking.. as I said I'm a newbie.
Best regards
--
View this message in context:
http://ta
The prefered convention in java : instantiate an class before work with it.
the documentation advise you only, where it make sense to do this job ;-)
with regards
Sven Homburg
Founder of the Chenille Kit Project
http://chenillekit.codehaus.org
2012/1/3 felipexz :
> Hi Sven.. I read it but the
Hi Sven.. I read it but the method on"Something" is a convention ?
Sorry but I'm new on Tapestry so I don't know.
I only found about the "onPrepare" in the wiki
http://wiki.apache.org/tapestry/Tapestry5HowToUseForms
So I think if its a convention ok, right. But if not I think it should be in
the
have a look at this page
http://tapestry.apache.org/forms-and-validation.html
""When rendering, the Form component emits two notifications: first,
"prepareForRender", then "prepare". These allow the Form's container
to setup any fields or properties that will be referenced in the form.
For exampl
Hi, now its working but I think you should add this "hint" in the
documentantion and at the Tutorial.
I know we need to initialize the class but where was my problem.
The working code is:
public class CreateMunicipio
{
@Property
@Persist
private Municipio municipio;
I Don't see you initializing the municipio variable anywhere in your code. You
need something like setupRender and initialize it via new if it is null.
On Jan 3, 2012, at 12:14 PM, felipexz wrote:
> I'm using Tomcat 7 and java 1.7.. its a problem ?
>
> --
> View this message in context:
>
I'm using Tomcat 7 and java 1.7.. its a problem ?
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Beaneditor-sending-null-object-tp5115312p5117434.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---
Hi, I think the problem is not about Persistence... the problem is municipio
is coming null.
Anyway I tryed with session.merge.. anyway it says idMunicipio cannot be
null.
Best regards
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Beaneditor-sending-null-object-tp511531
On Tue, 03 Jan 2012 14:50:03 -0200, felipexz wrote:
I tryed.. after the beaneditor submit it should persist my object.. but
it comes null.
And I get this error:
Caused by: org.hibernate.PersistentObjectException: detached entity
passed to persist: com.icms.feam.entities.Municipio
Use Ses
I tryed.. after the beaneditor submit it should persist my object.. but it
comes null.
And I get this error:
Caused by: org.hibernate.PersistentObjectException: detached entity passed
to persist: com.icms.feam.entities.Municipio
Best regards
--
View this message in context:
http://tapestry.104
On Tue, 03 Jan 2012 14:38:14 -0200, felipexz wrote:
Hi, thank you Thiago.. the code is this:
public class CreateMunicipio
{
@Property
private Municipio municipio;
When I try to run it.. my object municipio is null in
CreateMunicipio.class
why ? I'm filling it in my beane
Hi, thank you Thiago.. the code is this:
public class CreateMunicipio
{
@Property
private Municipio municipio;
@Inject
private Session session;
@CommitAfter
Object onSuccess()
{
session.persist(municipio);
On Tue, 03 Jan 2012 14:19:00 -0200, felipexz wrote:
I'm sorry but my questions are not cleary ?
Hi!
No, they weren't clear. Please post code and the full stack trace (if
any). Without them, we can only guess what's happening. ;)
No, tapestry-hibernate doesn't support Hibernate 4 yet, but
I'm sorry but my questions are not cleary ?
Best regards
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Beaneditor-sending-null-object-tp5115312p5117279.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---
gt; Best regards
>
> --
> View this message in context:
> http://tapestry.1045711.n5.nabble.com/Beaneditor-bug-null-property-error-tp5115312p5115312.html
> Sent from the Tapestry - User mailing list archive at Nabble.com.
>
> ---
Would it be a bug in the Beaneditor ? I didn't tryed in early
versions.. Im in 5.3.1
Tapestry 5.3 does support Hibernate 4.0 ?
Thank you
Best regards
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Beaneditor-bug-null-property-error-tp5115312p5115312.html
Sent from th
18 matches
Mail list logo
