please NEVER post in html on this list.

Please repost in text so I can read what you have to say.

david jencks


On 2003.01.05 05:23:17 -0500 Brian Topping wrote:
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
> <HTML>
> <HEAD>
> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
> <META NAME="Generator" CONTENT="MS Exchange Server version 6.0.5762.3">
> <TITLE>References &amp; ObjectFactories</TITLE>
> </HEAD>
> <BODY>
> <!-- Converted from text/rtf format -->
> 
> <P><FONT SIZE=2 FACE="Arial">I've been wanting to expose the necessary
> objects for JaasSecurityManagerServiceMBean to be able to work in a
> standalone Tomcat for a couple of weeks now, and it's starting to make
> sense, but not entirely yet.&nbsp; My experience so far has been w/ web
> &amp; EJB, so this is a newbie question of sorts.</FONT></P>
> 
> <P><FONT SIZE=2 FACE="Arial">Scott's suggested that I generate remoted
> proxies for the AuthenticationManager and RealmMapping interfaces.&nbsp;
> I see where those fit just fine and could use them in the client once I
> can generate them.&nbsp; To get them, it seems like I have the option of
> getting them through an MBean or publishing them through JNDI.&nbsp;
> Here's what I've come up with in both cases:</FONT></P>
> 
> <P><FONT SIZE=2 FACE="Arial">* JNDI:&nbsp; I tried binding the
> javax.naming.Context that is created in
> JaasSecurityManagerService.startService() into the global JNDI
> space.&nbsp; When I try to use it, I'm able to look up the name in the
> context okay, but the object factory instantiation gets called on the
> client instead of the server.&nbsp; I'm guessing I'm not modifying the
> Reference properly such that JNDI calls the server-side object factory
> instead of serializing the Reference and sending it back, in which case
> the ObjectFactory on the client gets called, which is wrong.&nbsp; Using
> org.jnp.interfaces.NamingContext in the reference didn't seem to make a
> difference, I'm interested in the distinction between these two when
> making a reference.</FONT></P>
> 
> <P><FONT SIZE=2 FACE="Arial">* MBean:&nbsp; I've also tried adding a
> method to JaasSecurityManagerService that will return the correct
> SecurityDomainContext when given the Realm name.&nbsp; Returning the
> SecurityDomainContext isn't sufficient, it needs to be at least a remoted
> proxy.&nbsp; But it seems that the remoted SecurityDomainContext would
> have to be a factory in itself since it would then have to generate the
> RealmMapping and AuthenticationManager remote proxies.&nbsp; This doesn't
> smell right either.&nbsp; </FONT></P>
> 
> <P><FONT SIZE=2 FACE="Arial">I found the reference for <A
> 
>HREF="http://www.mail-archive.com/[email protected]/msg23231.html";>http://www.mail-archive.com/[email protected]/msg23231.html</A>,
> and this code is also in the latest reference manual.&nbsp; This tells me
> how to be a client to an MBean, and I know how to create one that is used
> from within the same JVM (using NonSerializableFactory).&nbsp; I
> understand the basic semantics behind References and ObjectFactories, but
> I have been unable to find an example of a server that creates remoted
> proxies.&nbsp; I suspect that I am looking at the problem wrong though,
> missing things simple, subtle or both.&nbsp; </FONT></P>
> 
> <P><FONT SIZE=2 FACE="Arial">Any thoughts are appreciated!!</FONT>
> </P>
> 
> <P><FONT SIZE=2 FACE="Arial">-b</FONT>
> </P>
> 
> </BODY>
> </HTML>
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-user
> 
> 


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to