3:19 p.m.
Hi!
I'm wondering a couple things here:
1) Is there something like jboss-web.xml as far as configuring context
paths and whatnot? I don't recall seeing anything like that when I
was looking at the DTD for jboss-deployment-structure.xml, though it
seems a logical place, so I wouldn't be surprised if I missed it.
2) Are we at a point where I can add a context for serving static
content from some arbitrary location on disk? If so, I'm thinking it
ties in with #1, so maybe this is more like one and a half questions.
:Den
--
We must welcome the future, remembering that soon it will be the past;
and we must respect the past, remembering that it was once all that
was humanly possible.
George Santayana
3:29 p.m.
See this branch: https://github.com/wolfc/jboss-as/tree/JBAS-9020
On 04/28/2011 10:19 PM, denstar wrote:
Hi!
I'm wondering a couple things here:
1) Is there something like jboss-web.xml as far as configuring context
paths and whatnot? I don't recall seeing anything like that when I
was looking at the DTD for jboss-deployment-structure.xml, though it
seems a logical place, so I wouldn't be surprised if I missed it.
https://github.com/wolfc/jboss-as/blob/JBAS-9020/welcome/src/main/webapp/...
2) Are we at a point where I can add a context for serving static
content from some arbitrary location on disk? If so, I'm thinking it
ties in with #1, so maybe this is more like one and a half questions.
https://github.com/wolfc/jboss-as/blob/JBAS-9020/build/src/main/resources...
:Den
You can either use relative-to or path will be interpreted as an
absolute path.
Carlo
5:14 p.m.
On Thu, 2011-04-28 at 22:29 +0200, Carlo de Wolf wrote:
See this branch: https://github.com/wolfc/jboss-as/tree/JBAS-9020
Ok, some things need to be fixed. You should not add the JSP for 404 (it
probably has a XSS problem because of the request URI being sent back;
any access would also create a session, thus using resources). If you
must have an error page, I'd recommend a dumb 404.html. Less fancy but
safer.
On 04/28/2011 10:19 PM, denstar wrote:
> Hi!
>
> I'm wondering a couple things here:
>
> 1) Is there something like jboss-web.xml as far as configuring context
> paths and whatnot? I don't recall seeing anything like that when I
> was looking at the DTD for jboss-deployment-structure.xml, though it
> seems a logical place, so I wouldn't be surprised if I missed it.
https://github.com/wolfc/jboss-as/blob/JBAS-9020/welcome/src/main/webapp/...
> 2) Are we at a point where I can add a context for serving static
> content from some arbitrary location on disk? If so, I'm thinking it
> ties in with #1, so maybe this is more like one and a half questions.
https://github.com/wolfc/jboss-as/blob/JBAS-9020/build/src/main/resources...
> :Den
>
You can either use relative-to or path will be interpreted as an
absolute path.
Ok.
--
Remy Maucherat <rmaucher(a)redhat.com>
Red Hat Inc
8:19 a.m.
On 04/29/2011 12:14 AM, Remy Maucherat wrote:
On Thu, 2011-04-28 at 22:29 +0200, Carlo de Wolf wrote:
> See this branch: https://github.com/wolfc/jboss-as/tree/JBAS-9020
Ok, some things need to be fixed. You should not add the JSP for 404 (it
probably has a XSS problem because of the request URI being sent back;
any access would also create a session, thus using resources). If you
must have an error page, I'd recommend a dumb 404.html. Less fancy but
safer.
Please add comments regarding the welcome app to
https://issues.jboss.org/browse/AS7-522.
I'm not a web-wizard, so I'm not going to try and do fancy (or unfancy)
stuff. :-)
Carlo
> On 04/28/2011 10:19 PM, denstar wrote:
>> Hi!
>>
>> I'm wondering a couple things here:
>>
>> 1) Is there something like jboss-web.xml as far as configuring context
>> paths and whatnot? I don't recall seeing anything like that when I
>> was looking at the DTD for jboss-deployment-structure.xml, though it
>> seems a logical place, so I wouldn't be surprised if I missed it.
>
https://github.com/wolfc/jboss-as/blob/JBAS-9020/welcome/src/main/webapp/...
>
>> 2) Are we at a point where I can add a context for serving static
>> content from some arbitrary location on disk? If so, I'm thinking it
>> ties in with #1, so maybe this is more like one and a half questions.
>
https://github.com/wolfc/jboss-as/blob/JBAS-9020/build/src/main/resources...
>
>> :Den
>>
> You can either use relative-to or path will be interpreted as an
> absolute path.
Ok.
5:28 p.m.
On Thu, Apr 28, 2011 at 2:29 PM, Carlo de Wolf wrote:
See this branch: https://github.com/wolfc/jboss-as/tree/JBAS-9020
Heh. The welcome.jar is born! Nice.
On 04/28/2011 10:19 PM, denstar wrote:
>
> Hi!
>
> I'm wondering a couple things here:
>
> 1) Is there something like jboss-web.xml as far as configuring context
> paths and whatnot? I don't recall seeing anything like that when I
> was looking at the DTD for jboss-deployment-structure.xml, though it
> seems a logical place, so I wouldn't be surprised if I missed it.
https://github.com/wolfc/jboss-as/blob/JBAS-9020/welcome/src/main/webapp/...
Sweet! I apparently had just had a brain fart, as I was like "why
isn't this working?!?!" only to realize when I /really/ looked at it,
I was using context.xml. D'oh. Thanks!
> 2) Are we at a point where I can add a context for serving
static
> content from some arbitrary location on disk? If so, I'm thinking it
> ties in with #1, so maybe this is more like one and a half questions.
https://github.com/wolfc/jboss-as/blob/JBAS-9020/build/src/main/resources...
I love being able to specify the absolute-ness of the paths! Better
than some kind of special token to differentiate between file system
roots and deployment-relative.
I'm not sure how I'd leverage this to get what I was talking about
though. I don't see the sub-deployment elements in the XSD, so I'm
not sure what options there are. I think I'm looking at domain,
whereas this would be in jboss-deployment-scanner.xsd probably? Is
there a central place for XSDs?
Maybe some spin on:
<fs-archive path="/some/place/else/images.jar"/>
For something like:
<fs path="/some/place/else/images.jar" contextpath="/images"/>
?
(side note: I feel silly asking anything, when the source code is
available. There is no question I can't answer myself.)
(eventually)
:)
Thank you Carlo!
:Denny
--
When men and women agree, it is only in their conclusions; their
reasons are always different.
George Santayana
8:29 a.m.
Yes, we call this overlays. It is currently not yet implemented.
It'll become something like:
<deployment name="foo.war" runtime-name="foo.war">
<fs-exploded path="deployments/foo.war"
relative-to="jboss.home"/>
<fs-exploded root="/images"
path="/some/place/else/images"/>
</deployment>
The actual xml might still change a bit..
Carlo
On 04/29/2011 12:30 AM, denstar wrote:
On Thu, Apr 28, 2011 at 4:28 PM, denstar wrote:
...
> <fs path="/some/place/else/images.jar"
contextpath="/images"/>
Obviously I meant "/some/place/else/images", else I would have left
the -archive on the fs bit. =)p
:Den
8:41 a.m.
On Fri, 2011-04-29 at 15:29 +0200, Carlo de Wolf wrote:
Yes, we call this overlays. It is currently not yet implemented.
No, don't call this an overlay, the name is used by Servlet 3, so it
would cause confusion.
It'll become something like:
<deployment name="foo.war" runtime-name="foo.war">
<fs-exploded path="deployments/foo.war"
relative-to="jboss.home"/>
<fs-exploded root="/images"
path="/some/place/else/images"/>
</deployment>
The actual xml might still change a bit..
Is that transparent through VFS ? If it's not, then I don't like
kludges.
--
Remy Maucherat <rmaucher(a)redhat.com>
Red Hat Inc
9:26 a.m.
On 04/29/2011 08:41 AM, Remy Maucherat wrote:
On Fri, 2011-04-29 at 15:29 +0200, Carlo de Wolf wrote:
> Yes, we call this overlays. It is currently not yet implemented.
No, don't call this an overlay, the name is used by Servlet 3, so it
would cause confusion.
> It'll become something like:
>
> <deployment name="foo.war" runtime-name="foo.war">
> <fs-exploded path="deployments/foo.war"
relative-to="jboss.home"/>
> <fs-exploded root="/images"
path="/some/place/else/images"/>
> </deployment>
>
>
> The actual xml might still change a bit..
Is that transparent through VFS ? If it's not, then I don't like
kludges.
Yes it is. Also I don't like the term "overlay" either! The XML looks
OK to me though.
--
- DML
1:59 p.m.
On Fri, Apr 29, 2011 at 7:29 AM, Carlo de Wolf wrote:
Yes, we call this overlays. It is currently not yet implemented.
Cool, I gathered as much when I tossed the new XSD in. =)
It'll become something like:
<deployment name="foo.war" runtime-name="foo.war">
<fs-exploded path="deployments/foo.war"
relative-to="jboss.home"/>
<fs-exploded root="/images"
path="/some/place/else/images"/>
</deployment>
The actual xml might still change a bit..
Looks dandy to me.
Naming stuff can suck. "overlay", "path", "root"... terms
are
overloaded. Bah.
Would context-path be in there too?
What about "resource map", "resource structure" or some such instead
of "overlay"? "deployment resource"? hrm. Trying to remember what
I
read on that "overlay" ticket. Will the fs-* element be appearing
other places besides the deployment element?
Anyways, it's looking good, and thanks for the heads up!
:Denny
--
Being is. Being is in-itself. Being is what it is.
Jean-Paul Sartre
6:01 p.m.
The relevant xsd is at
https://github.com/wolfc/jboss-as/blob/JBAS-9020/controller/src/main/reso...
On 4/28/11 5:28 PM, denstar wrote:
On Thu, Apr 28, 2011 at 2:29 PM, Carlo de Wolf wrote:
> See this branch: https://github.com/wolfc/jboss-as/tree/JBAS-9020
Heh. The welcome.jar is born! Nice.
> On 04/28/2011 10:19 PM, denstar wrote:
>>
>> Hi!
>>
>> I'm wondering a couple things here:
>>
>> 1) Is there something like jboss-web.xml as far as configuring context
>> paths and whatnot? I don't recall seeing anything like that when I
>> was looking at the DTD for jboss-deployment-structure.xml, though it
>> seems a logical place, so I wouldn't be surprised if I missed it.
>
>
https://github.com/wolfc/jboss-as/blob/JBAS-9020/welcome/src/main/webapp/...
Sweet! I apparently had just had a brain fart, as I was like "why
isn't this working?!?!" only to realize when I /really/ looked at it,
I was using context.xml. D'oh. Thanks!
>> 2) Are we at a point where I can add a context for serving static
>> content from some arbitrary location on disk? If so, I'm thinking it
>> ties in with #1, so maybe this is more like one and a half questions.
>
>
https://github.com/wolfc/jboss-as/blob/JBAS-9020/build/src/main/resources...
I love being able to specify the absolute-ness of the paths! Better
than some kind of special token to differentiate between file system
roots and deployment-relative.
I'm not sure how I'd leverage this to get what I was talking about
though. I don't see the sub-deployment elements in the XSD, so I'm
not sure what options there are. I think I'm looking at domain,
whereas this would be in jboss-deployment-scanner.xsd probably? Is
there a central place for XSDs?
Maybe some spin on:
<fs-archive path="/some/place/else/images.jar"/>
For something like:
<fs path="/some/place/else/images.jar" contextpath="/images"/>
?
(side note: I feel silly asking anything, when the source code is
available. There is no question I can't answer myself.)
(eventually)
:)
Thank you Carlo!
:Denny
--
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat
6:22 p.m.
On Thu, Apr 28, 2011 at 5:01 PM, Brian Stansberry wrote:
The relevant xsd is at
https://github.com/wolfc/jboss-as/blob/JBAS-9020/controller/src/main/reso...
Awesome! Thanks! The one you'd sent me before didn't have as much,
this is muy bueno.
I'll be blogging a good bit of what I've asked about/been doing. Not
quite the same as contributing code, but maybe it'll help the cause a
smidge'.
Mostly I want to help folks like me, who are /just dangerous enough/
(to malform a phrase). =)
:Denny
--
Acting is happy agony.
Jean-Paul Sartre
5021
days inactive
5022
days old
11 comments
5 participants
participants (5)
-
Brian Stansberry -
Carlo de Wolf -
David M. Lloyd -
denstar -
Remy Maucherat