[JBoss Seam] - Identity getPassword...
by garypinkham
There is probably a wonderful explanation for this but it's escaping me. Whenever I call indentity.getPassword from anywhere but the Authenticator bean I get a null. I'm brand new to seam (in case you couldn't tell) and am just experimenting with the basics. I used seam-gen to create a basic application and added a single action. In that new action I tried both Identity.instance().getPassword() and identity.getPassword() (with @In for Indentity). Both of them return null. Is that normal or have I done something wrong? Actually since I never changed any of the configs after running seam-gen I probably should say "Is there something I should do?"
Thanks in advance,
Gary
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059349#4059349
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4059349
17Â years, 5Â months
[Clustering/JBoss] - Re: HA-JNDI and JNDI for cluster access
by bstansberryï¼ jboss.com
There's a two stage process:
1) The code cycles through the list of URLs you provide, attempting to contact a server and download a naming proxy. At this point, providing mutliple URLs helps in case1, since if server1 is not available it can try server2, etc.
2) Once you contact a server, there's a big difference between regular JNDI and HA-JNDI. Now you have a proxy; it's the proxy that communicates with the server to do the lookup. Let's say that server1 was running. Step #1 iterates through the list in order, so server1 will provide the proxy.
a) With regular JNDI, the naming proxy you download will only know how to talk to the server it came from (server1). If server1 subsequently fails, the proxy can't recover; the exception propagates to your code. You can catch the exception, and do "context = new InitialContext(props)" again to recover, but you have to manage it.
b) With HA-JNDI, the naming proxy you download will have clustering logic and cluster topology info inside of it. It will know that server2 and server3 are all running. When you do a lookup it will load balance requests across them. If a call fails, it can transparently fail over to a different server.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059339#4059339
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4059339
17Â years, 5Â months