I just tested sending a mail from an asynchronous method (using JSF RI 1.2_03).
1 - I rebuilt Seam from CVS
2 - tested the following method, which worked
| public void newMessage(ContactMessage message) {
| try {
| renderer.render(/mails/contact.xhtml);
|
I've put a fix for 1.2 RI into CVS. Please test
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4026961#4026961
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4026961
___
jboss-user
I can do it mid of next week. I'm out for few days. I will post my results.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4026986#4026986
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4026986
Hi Peter!
anonymous wrote : The fix won't work with JSF 1.2
Any idea when it'll work with JSF 1.2 RI? Seam mail with facelets templating
looks so promising but it's pretty much useless for me at this time because I
always send mails asynchronously.
tazman
View the original post :
I'll try to get the fix into 1.2.1
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4025048#4025048
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4025048
___
jboss-user mailing list
Btw, the best way to get a fix done sooner is to vote for it in JIRA!
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4025050#4025050
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4025050
I checked it with myfaces, still there is a problem, I posted stack trace in
JIRA issue.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4023969#4023969
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4023969
I'm getting this same stacktrace (NPE in FaceletsRenderer). I'm trying to use
Quartz to send an email at a scheduled time. The method kicks-off when it
should, but the rendering fails:
| java.lang.NullPointerException
| at
By the way, I'm using Tomcat with Embedded EJB and Seam 1.1.6.
My apologies if asking when a Jira ticket will be resolved is Taboo. I'm
really impressed with Seam and the responsiveness of the developers on this
forum...please don't hate me. :-)
View the original post :
There is currently a fix (which I haven't tested properly, so it would be great
if you could, and put any problems on the JIRA issue) which will be in today's
release. Hopefully I'll close the issue next week sometime (its currently my
number 2 priority)
View the original post :
I will build seam source from CVS and will try to test it today. I will post my
results on JIRA.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4023174#4023174
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4023174
The fix won't work with JSF 1.2
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4023175#4023175
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4023175
___
jboss-user mailing list
Yes unfortunetly it doesn't work with JSF 1.2, I will try to switch tomorrow to
myfaces and test it in thi environment.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4023326#4023326
Reply to the post :
Issue is posted: http://jira.jboss.com/jira/browse/JBSEAM-892
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4020102#4020102
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4020102
Sorry I was out yestarday and I didn't have access to my dev environment where
I have this problem. Unfortunetly the stack trace is super short and maybe it
will tell you more then me:
anonymous wrote :
| 15:02:31,623 ERROR [TimerImpl] Error invoking ejbTimeout:
javax.ejb.EJBTransacti
|
It looks to me like ejb3 is swallowing the stack trace (it has an annoying
habit of doing this in async stuff). We need the stack of the original
exception (wrap your code in a try-catch and use e.printStackTrace()).
View the original post :
I got it:
anonymous wrote :
| 18:04:44,723 ERROR [STDERR] java.lang.NullPointerException
| 18:04:44,723 ERROR [STDERR] at
org.jboss.seam.ui.facelet.FaceletsRenderer.wr
| apResponseWriter(FaceletsRenderer.java:95)
| 18:04:44,723 ERROR [STDERR] at
I just checked also one thing. I removed from my mail template all referances
to my components. Now it is completely static template with hardcoded
receipient, subject and body. Unfortunelty I get same error when rendering - I
guess this proves that my problem is not about properly scoped
Please create an issue in JIRA, this is clearly a bug.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4019493#4019493
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4019493
___
I guess I wasn't clear in my previous posts. This is exactly what I'm doing, I
tried to stick it in to all possible contexts that are available throug
Contexts class. Everytime I get NPE when running Renderer.render() method and I
understand that this is because my objects are not found in
Post the stack trace.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4018893#4018893
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4018893
___
jboss-user mailing list
No, an NPE inside Seam (rather than your own code) sounds more like a bug in
Seam.
But you havn't posted this stack trace, which makes it super-difficult to help
you.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4019070#4019070
Reply to the post :
Async methods are processed in their own conversation context (this is to
ensure that conversations are always single-threaded). Try passing the stuff
you need as parameters to the async method.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4018531#4018531
I'm already passing my objects as parameters to asynch method and it works
great. The problem begins when I want to render mail using Renderer.render
method because my objects are not within conversation context of renderer. And
in my email template I need to access my user object to get his
So stick em in the conversation or event context before calling render(). ie.
Contexts.getEventContext().set(...).
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4018664#4018664
Reply to the post :
25 matches
Mail list logo
