Well, I tried running TomCat on its own. There are several issues,
1. JNDI namespace integration
        This can be accomplished even in a stand-alone TomCat by properly
rewriting JbossWebXmlReader RequestInterceptor so that it contacts the
NameServer running on Computer1 and gets its InitialContext from
there. I've tried that and it did not fully for me, perhaps, my
implementation was flawed.

2. Accessing DataSources
        This is a JDBC issue. I was trying to split an EAR, so that it's
WAR component sits on one machine and EJBs on another. But I did not want
to do too many modifications to the source of the application (in fact,
none, except for minor deployment xml mods). The WAR I was using needs to
access DataSources (i.e. the database) so they have to be pre-configured.
It is impossible to access DataSource objects sitting on Computer1 from
Computer2 because those are VM-local (they sit in java:comp/env JNDI
context for that reason). So, I need to configure DataSources on
Computer2. The simplest way I was able to do it, is to start TomCat as
part of JBoss with DataSource setup in jboss.jcml


On Tue, 27 Feb 2001, Jay Walters wrote:

> Sorry to ask questions instead of give answers, but do you really need JBoss
> with Tomcat on the servlet machine? You could just run plain Tomcat there.
> 
> Cheers
> 
> -----Original Message-----
> From: Anatoly Akkerman [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, February 27, 2001 4:48 PM
> To: jboss-user mailing list; JBoss-Dev
> Subject: [jBoss-Dev] sharing JNDI namespace between 2 instances of JBoss
> 
> 
> 
> Hi,
> 
> I am trying to deploy an EAR piecewise on 2 separate instances of JBoss:
> WAR on one
> EJBs on another
> 
> In order to do that I've setup
> 
> Computer1
> JBoss w/o tomcat, EJBs are in the deploy
> NamingService running on port XXXX
> 
> Computer2
> JBoss with EmbeddedTomcat, WAR in the deploy directory
> jndi.properties java.naming.provider.url entry is set to Computer1:XXXX
> 
> Deployment succeeds and appropriate entries from the jboss-web.xml are
> processed and added into java:comp/env space for Computer2 JBoss. (I am
> printing out the listing for the whole Context on deployment)
> 
> But when the servlets try to resolve the java:comp/env entries for the
> beans that were added by JbossWebXmlReader, it throws a NamingException.
> 
> No message is provided with the NamingException, the only thing I was able
> to extract, is the message from the root cause exception:
> 
> "Type code out of range, is 125"
> 
> I suspect it has to do with the "java:comp/env" space issues, that these
> are local to the VM (?) while the InitialContext that the servlets are
> getting, belongs to the NamingService from Computer1. 
> 
> I am very new to JNDI, please, forgive me if I am not making sense.
> 
> -------------------------------------------------------------------------
> Anatoly Akkerman
> Computer Science Dept.
> Courant Institute of Mathematical Sciences, NYU
> 719 Broadway, #715                      Tel: 212 998-3525
> New York, NY 10003                      Fax: 212 995-4123
> -------------------------------------------------------------------------
> 
> 
> 


Reply via email to