|
I think my thread got a bit fragmented so I though I repost
my last question as a new thread: Hi
Scott (or anyone who knows), Just wondering if you can explain your suggestion
below a little bit. Perhaps
by supplying an example. I
appreciate your assistance. Best
Regards, Mike -----Original
Message----- From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
On Behalf Of Scott M Stark Sent:
To:
[EMAIL PROTECTED] Subject:
Re: [JBoss-user] JBoss
2.4.4/Tomcat 4x - How do I do Virtual Paths? You
can deploy a war that is a directory by adding the directory name to the AutoDeployer configuration. This
makes it difficult for designers. I like
to have an external area where designers can just throw in images on the dev
server without having to package them up. There
must be someway to create a virtual directory. Thanx for your reply. -----Original
Message----- From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
On Behalf Of Marius Kotsbak Sent:
To:
Mike Lecza Cc:
[EMAIL PROTECTED] Subject:
Re: [JBoss-user] JBoss
2.4.4/Tomcat 4x - How do I do Virtual Paths? On
Fri, 2002-04-05 at >
Sorry for the repost on this one, but someone must be using context >
paths with JBoss 2.4.4/Tomcat
4. Am I way off on this one? How can I >
set up an image path that is not within the webapp? I used to do this >
in the server.xml in tomcat
3x. > >
Below is the original post. > >
Thanx for reading.
Your help is most appreciated. > >
Regards. > >
================================================ > > >
I understand that 2.4.4 + Catalina doesn't support parsing the >
server.xml file. > >
I am trying to setup a Context path that would normally be in the > server.xml. From what I have read I am thinking I should
be able to do >
this in the jboss.jcml. I took a shot at getting it to work (cuz I >
don't see any dox on how-to). > >
Below is one of the things I tried. Can
someone confirm that this is >
possible and supply an example? > > > <mbean
code="org.jboss.web.catalina.EmbeddedCatalinaServiceSX" >
name="DefaultDomain:service=EmbeddedTomcat"> > <attribute
name="Port">80</attribute> > <attribute name="Config"> > <Context
path="/images" > docBase="/projects/XX/presentation/images" > crossContext="false" > debug="0" > reloadable="true"> > </Context> > </attribute> > </mbean> > >
> I don't think it should be supported, as it probably
is against the spec. When you deploy a webapp (.war)
or as a part of a .ear, it should not depend on
something in the filesystem outside the package.
Could you not just include the images in the .war? |
