[Messaging, JMS & JBossMQ] - Re: UsingWebSphereMQSeriesWithJBossASPart4
by rosama77
Yeah, I already see that (after a lot of hours spending, not so very clear for me), but later return to test the scenarios 1 and 2, from the demo application, and finally get to worked with scenarios 2, defining some environment entries in the EJB, and following the steps very carefull.
Where can I post a problem with the same version for jboss 3.2.5 but referring to LDAP, because never sucessfull to connect, I don't know if the standard of LDAP tree, or just not working, this was using JAAS and some security-domains, but never sucessfull (logs telling that never connects to LDAP server, do I have to defined a admin user in order to connect in configurations files?).
Someone that has a good article about this, also we get supported from you guys, but from USA, they aparently said never worked, but I have my doubts. What do you think Adrian?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4073248#4073248
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4073248
18Â years, 10Â months
[JBoss Seam] - Re: Login Redirection not propagating GET parameters
by milli
"pete.muir(a)jboss.org" wrote : No. They are not semantically identical. @RequestParameter is simply for injecting a request parameter, page parameters have a deeper effect on your app (parameter propagation, setting values on your model, application of converters).
I understand with page definition you can do more than a simple @RequestParameter injection.
Let's forget about propagating parameters values for a while. But when it comes to just passing GET parameters(to the backing bean component) shouldn't they be having the same behaviour?
Here is what I found out.
When you have the parameter defined in pages.xml, here is the flow of the backing bean component:
* Seam calls @Create method first
* It then calls setters on the parameters to initialize the values
With @RequestParameter, the behaviour is
* Seam injects parameter values first (No need to have setters)
* It then calls the @Create method
Is this the intended behaviour? May be there was a reason to design this way which I don't get it.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4073234#4073234
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4073234
18Â years, 10Â months