On Wed, 14 Nov 2012 13:17:34 -0200, o3005659 wrote:
I know how to handle forms, and I know how to setup java server, I just
wasn't sure does Tap requires some magic spell or something like that.
That's quite different from what you asked: "How can I make contact form
in Tapestry using Javax
just having a laugh... no harshness intended ;)
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Javax-mail-in-Tapestry-tp5718005p5718011.html
Sent from the Tapestry - Dev mailing list archive at Nabble.com.
I know how to handle forms, and I know how to setup java server, I just
wasn't sure does Tap requires some magic spell or something like that. BTW,
your answer was crystal and clear. :) Agree this shouldn't be among Dev Q.
if you know how to change it, go ahead.
--
View this message in context:
Firstly, you've asked this question on the tapestry-dev list when you should
have posted it on tapestry-users.
Secondly, you have asked two questions:
1. How do I handle a form in tapestry?
2. How do I send a mail using javax mail
Answers:
1. http://tapestry.apache.org/forms-and-validation.html
2
I put this on the users group recently to complete a thread, it belongs here
really I suppose.
The problem manifests when multiple PUs are defined in persistence.xml and then
referred to in classes using the @PersistenceContext(unitName= annotation. As
it is in 5.3.6 the first EntityManager wir
How can I make contact form in Tapestry using Javax mail? Or should you
suggest me some better mail service for my Tapestry app if there is some
available? I would like to hear your opinion about it.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Javax-mail-in-Tapestry-t
Good catch, will look at it.
On 14.11.2012 12:37, Bob Harner wrote:
> If considering API changes, it might also be worthwhile to consider
> Howard's ancient https://issues.apache.org/jira/browse/TAP5-336 ("The
> Cookies service interface could be simplified using a builder pattern"). If
> not wort
On Wed, Nov 14, 2012 at 12:37 PM, Bob Harner wrote:
> If considering API changes, it might also be worthwhile to consider
> Howard's ancient https://issues.apache.org/jira/browse/TAP5-336 ("The
> Cookies service interface could be simplified using a builder pattern"). If
> not worthwhile now, the
If considering API changes, it might also be worthwhile to consider
Howard's ancient https://issues.apache.org/jira/browse/TAP5-336 ("The
Cookies service interface could be simplified using a builder pattern"). If
not worthwhile now, then TAP5-336 should probably be closed.
On Tue, Nov 13, 2012 a
I haven't tried injecting 2 different EntityManager instances into pages so
cannot comment on that. I only refer to DAOs in my pages and these contain the
multiple PersistenceContext annotations.
It looks like the behaviour is different for page injection vs injecting into
service classes?
--
10 matches
Mail list logo