[JBoss Seam] - seam-gen, javax.el.PropertyNotFoundException when running Se
by thoman23
Hello everybody,
I am brand new to Seam. I have been evaluating it for a few days, and I'm very excited by the possibilities. However, I keep running into an issue with seam-gen.
When I deploy a Seam example, like the seam-registration example, it works fine when I use the example build script "ant explode" or "ant deploy" targets. However, if I create an empty project using seam-gen, and then copy in the "src" and "view" files from the example to the seam-gen shell, I get the following error when clicking a command button in the application:
Exception during request processing:
Caused by javax.servlet.ServletException with message: "/register.xhtml @17,84 value="#{user.username}": Target Unreachable, identifier 'user' resolved to null"
Caused by javax.el.PropertyNotFoundException with message: "/register.xhtml @17,84 value="#{user.username}": Target Unreachable, identifier 'user' resolved to null"
This happens both with the command line seam-gen and the Eclipse seam tools plugin. I am sure others must run into this as well, but I can't find the exact resolution to the problem posted anywhere.
Can someone please help me get past this? I'd really like to use seam-gen more in my evaluation.
Thanks,
Anthony
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4110641#4110641
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4110641
18 years, 4 months
[JBoss Seam] - send mails on session destroy
by beligum
Hi all,
I'm trying to send some queued mails when the session end (sort of an auto-send outbox pattern). I've tried a lot of options, but I always encounter problems. What I have:
A stateless bean (tried it with a javabean too) emailManager that sends the messages (javabean that contains a Renderer and the Message to be sent).
A stateful session bean (application scope) that stores the message queue, and sends everything out when needed. The emailManager is injected here.
What I tried until now:
Put the "sendQueuedMessages" method in the @Destroy or @Remove or @PreDestroy method. This doesn't work, because all of my injected variables (in the SFSB) are nulled by the time this method is called.
Put it in a method with @Observer("org.jboss.seam.preDestroyContext.SESSION"). This works better, but when the renderer renders the email template (multiple recipients with <ui:repeat>), the variable of the ui:repeat is filled with null values, so no luck there too.
In general, it seems like some things are already destroyed before the method is finished. I tried to use Asynchronous methods too, but they complain about the fact that ApplicationFactory is't initialized.
Some advice?
bram
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4110629#4110629
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4110629
18 years, 4 months
[Messaging, JMS & JBossMQ] - Re: Higher JMSPriority not stepping in front of lower JMSPri
by seoeng
Ok, I think I have figured out what JBoss is doing. I am using 4.2.2GA.
Here is the new use case I used:
1. Send JMS Message with JMSPriority 4 to Queue
2. Send JMS Message with JMSPriority 4 to Queue
3. Send JMS Message with JMSPriority 4 to Queue
4. Send JMS Message with JMSPriority 7 to Queue
The MDB (Bean-Managed) is processing as follows:
1. Receives JMS Message #1, starts processing
2. Receives JMS Message #2, starts processing
3. Receives JMS Message #4, starts processing
4. Receives JMS Message #3, starts processing
NOTE: All messages are queued before MDB finishes #1.
What behavior is expected:
1. Receives JMS Message #1, starts processing
2. Receives JMS Message #4, starts processing
3. Receives JMS Message #2, starts processing
4. Receives JMS Message #3, starts processing
It appears that JBoss is queuing up a message before the MDB even processes it. So a higher priority message must wait what appears to be the invoker-proxy-binding's # of messages before it jumps in front.
This doesn't make sense to me, wouldn't you want a higher priority message to jump in front immediately? Is there a way around this, i.e. am I not setting the configuration correctly for my desired result?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4110626#4110626
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4110626
18 years, 4 months