OK,
It looks like I have been bludgeoned into seperating Jetty config and impl.
Just for the record, Jason, I still don't think you have taken in my
suggestion.
You seem to think that I am belligerently hanging onto the idea of
delivering Jetty in a single file, which needs unpacking,
I have suggested delivering the jetty-plugin UNPACKED numerous times (as
you will now find it if you build HEAD).
Unpacked means there is a deploy/jetty-plugin/*
I have not looked, but I was hoping to avoid this type of inconsitency in the
default release. Personally I think the unpacked
To recap:
deployment type | Advantages |Disadvantages
-
.sar archive | 1 file | Pain in the ass to configure
| digital signature |
|
Thanks for the recap, but it is in correct.
deployment type | Advantages |Disadvantages
---
- -
.sar archive | 1 file | Pain in the ass to configure
|
PROTECTED]; [EMAIL PROTECTED]; Jan Bartel; [EMAIL PROTECTED]
|Subject: Re: [JBoss-dev] Where should the Jasper jar live ?
|
|
|OK,
|
|It looks like I have been bludgeoned into seperating Jetty config and impl.
|
|Just for the record, Jason, I still don't think you have taken in my
|suggestion.
|
|You
, 2002 1:58 PM
|To: [EMAIL PROTECTED]
|Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; Jan Bartel; [EMAIL PROTECTED]
|Subject: Re: [JBoss-dev] Where should the Jasper jar live ?
|
|
|OK,
|
|It looks like I have been bludgeoned into seperating Jetty config and
| impl.
|
|Just for the record, Jason
|Really... how do you come to these conclusions?
if jetty is configured through jetty.xml then we need to use the directory
if jetty is configured through jboss-service.xml then we need to use a
jetty-service.xml
End of story.
what file are we talking about?
marcf
|To: [EMAIL PROTECTED]; lsanders
|Subject: Re: [JBoss-dev] Where should the Jasper jar live ?
|
|
|Thanks for the recap, but it is in correct.
|
| deployment type | Advantages |Disadvantages
So there are 3 different possible locations for the configuration of jetty?
How is this not complex to you?
--jason
On Monday 03 June 2002 03:25 pm, marc fleury wrote:
|Really... how do you come to these conclusions?
if jetty is configured through jetty.xml then we need to use the
|So there are 3 different possible locations for the configuration
|of jetty?
no
the configuration of jetty is done with jboss-service.xml
marcf
___
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28
Guys,
I've already said that I would alter Jetty's packaging for Jason.
Jason, where do you want Jetty's jars to go ?
I just tried them in lib/ with a jetty-service.xml in deploy/ - it
didn't work - I got a nice message telling me jetty-service.xml is being
deployed - then nothing (this is
-- jetty-service.xml
if no -- use diretory structure exploded
marcf
|-Original Message-
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of Jason
|Dillon
|Sent: Monday, June 03, 2002 3:16 PM
|To: [EMAIL PROTECTED]; lsanders
|Subject: Re: [JBoss-dev] Where should
digi sigs will not work when you need to change the config. it is only
useful
if you have static config and want to ensure that the contents do not
change.
the second you need to chagne the config, you must resign...
Right. The point is, it can be distributed with a signature, as long as
| |Subject: Re: [JBoss-dev] Where should the Jasper jar live ?
| |
| |
| |Thanks for the recap, but it is in correct.
| |
| | deployment type | Advantages |Disadvantages
| |
|
||--
| |-
| |
| |- -
| | .sar
the brain common sense and stop
feeling so lonely
marcf
| marcf
|
| |-Original Message-
| |From: [EMAIL PROTECTED]
| |[mailto:[EMAIL PROTECTED]]On Behalf Of
| | Jason Dillon
| |Sent: Monday, June 03, 2002 3:16 PM
| |To: [EMAIL PROTECTED]; lsanders
| |Subject: Re: [JBoss-dev] Where
'(\\.ear$ . archive-mode)
auto-mode-alist))
Share and Enjoy,
James
-Original Message-
From: David Jencks [mailto:[EMAIL PROTECTED]]
Sent: Friday, May 31, 2002 11:07 PM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-dev] Where should the Jasper jar live ?
I still like the sar concept.
I notice
|take all the
|
|resources out of their ears and deploy them in lib/, then
|
|just drop the
|
|dds into deploy/.
|
|Ok, so they can edit their descriptors - but it's not J2EE, is it ?
This is the future yes, for all the deployment types.
marcf
:[EMAIL PROTECTED]] On
Behalf Of Ignacio Coloma
Sent: Sunday, June 02, 2002 10:16 AM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-dev] Where should the Jasper jar live ?
Maybe having to install and learn to manage emacs and custom edit the
emacs config to modify the Jetty log system
Why have a sar of jars and a separate service.xml ? You might as well do
as Scott suggests and collapse all the jars into one. Besides, if a sar
is not deployable (because it has no dd) and therefore does not
encapsulate a JMX service - why call it a sar ?
A sar of jars is a convient
-mode-alist))
Share and Enjoy,
James
-Original Message-
From: David Jencks [mailto:[EMAIL PROTECTED]]
Sent: Friday, May 31, 2002 11:07 PM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-dev] Where should the Jasper jar live ?
I still like the sar concept.
I notice that emacs can
Jules, how about making the jetty-plugin.sar just contain the jars and have a
seperate jetty-service.xml?
--jason
On Friday 31 May 2002 04:31 pm, Jules Gosnell wrote:
Scott,
Would you mind if I moved the jasper.jar from lib/ to jetty-plugin.sar ?
I figure:
- jasper is an implementation
That is fine but why not just create a single jetty-service.jar that
includes all
Jetty specific files and have a seperate jetty-service.xml descriptor with
your
config that references the required jar:
server
classpath codebase=. archives=jetty-service.jar/
...
This is how I'm packaging the
I had a feeling I would never sneak this through without opening a can
of worms.
Jason,
Why have a sar of jars and a separate service.xml ? You might as well do
as Scott suggests and collapse all the jars into one. Besides, if a sar
is not deployable (because it has no dd) and therefore
The natural progression of all this separation of config and
implementation is that we will begin encouraging people to take all the
resources out of their ears and deploy them in lib/, then just drop the
dds into deploy/.
Ok, so they can edit their descriptors - but it's not J2EE, is it ?
Gosnell [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; Jan Bartel [EMAIL PROTECTED]; jason
[EMAIL PROTECTED]
Sent: Friday, May 31, 2002 5:59 PM
Subject: Re: [JBoss-dev] Where should the Jasper jar live ?
I had a feeling I would never sneak this through without opening a can
] Where should the Jasper jar live ?
I had a feeling I would never sneak this through without opening a can
of worms.
Jason,
Why have a sar of jars and a separate service.xml ? You might as well do
as Scott suggests and collapse all the jars into one. Besides, if a sar
is not deployable
Scott M Stark wrote:
Ultimately the configuration of every mbean is going to be seperate from
its implementation to support persistence of changes made through the
management interface.
So will this persistant configuration be laid over the static dd one, or
will it replace the dd ?
I still like the sar concept.
I notice that emacs can edit files in jars (such as ejb-jar.xml) and save
them back into the jar. Anyone know enough elisp to figure out how to make
it edit .sar, .ear, .war, etc the same way? (I presume it just means
recognizing the file format/extension as
Group, LLC
- Original Message -
From: Jules Gosnell [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; Jan Bartel [EMAIL PROTECTED]; jason
[EMAIL PROTECTED]
Sent: Friday, May 31, 2002 5:59 PM
Subject: Re: [JBoss-dev] Where should the Jasper jar live
dislcaimer, a few beers in me after the laker game...
The natural progression of all this separation of config and
implementation is that we will begin encouraging people to take all the
resources out of their ears and deploy them in lib/, then just drop the
dds into deploy/.
Who gives a
30 matches
Mail list logo
