Bill Barker wrote:
It certainly made Gump unhappy :).
Ooops, yes, it's going to be a problem. It's quite hard to build my
custom JAR :(
Rémy
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL P
- Original Message -
From: "Remy Maucherat" <[EMAIL PROTECTED]>
To: "Tomcat Developers List" <[EMAIL PROTECTED]>
Sent: Wednesday, August 11, 2004 11:04 AM
Subject: Re: [5.next] Progress, more ideas and native connector benchmarks
Some updates ...
Rem
Some updates ...
Remy Maucherat wrote:
* Default global and per-host configurations:
- conf///context.xml.default
- conf///web.xml.default
- conf/context.xml
- conf/web.xml
This will lead to the removal of the DefaultContext interface, since
this will fully replace the functionality (while being v
Shapira, Yoav wrote:
Hi,
You know, I've been meaning to address the "Undeploy considered dangerous" bugzilla item by adding a JavaScript confirmation dialog around the undeploy action in the HTML manager. Too bad I hadn't gotten around to it before your mishap ;(
I would have clicked "yes": I w
Research Informatics
>-Original Message-
>From: Remy Maucherat [mailto:[EMAIL PROTECTED]
>Sent: Wednesday, July 28, 2004 6:27 AM
>To: Tomcat Developers List
>Subject: Re: [5.next] Progress, more ideas and native connector benchmarks
>
>Remy Maucherat wrote:
>
>&g
Remy Maucherat wrote:
Bill Barker wrote:
- Remove Deployer and DefaultContext. The new stuff looks like a better
replacement.
I did that but didn't commit yet. The management side for the default
context would need to be redone (it's not very difficult, I think).
The clustering will need updates,
Bill Barker wrote:
I'll volunteer for the admin webapp stuff. I enjoy deleting stuff from
there ;-).
It's at the end of my list right now, so I wont't get there for a while.
I committed a few things:
- The new deployer is getting there. Missing is the support for the
manager webapp, but this wo
I'll volunteer for the admin webapp stuff. I enjoy deleting stuff from
there ;-).
- Original Message -
From: "Remy Maucherat" <[EMAIL PROTECTED]>
To: "Tomcat Developers List" <[EMAIL PROTECTED]>
Sent: Monday, July 26, 2004 9:27 AM
Subject: Re: [5.
I committed a few things:
- The new deployer is getting there. Missing is the support for the
manager webapp, but this won't be too hard to write.
- I redid partially the naming. Now the NamingResource object is the
main object, and Context is not polluted.
My list is:
- Update manager webapp, a
Remy Maucherat wrote:
Costin Manolache wrote:
Remy Maucherat wrote:
Costin Manolache wrote:
Both difference and similarity :-).
Eclipse ( osgi actually ) has a similar flat loader implementation,
but with finer control over what is exported/imported and pretty
strong versioning. In addition osgi
Costin Manolache wrote:
Remy Maucherat wrote:
Costin Manolache wrote:
Both difference and similarity :-).
Eclipse ( osgi actually ) has a similar flat loader implementation,
but with finer control over what is exported/imported and pretty
strong versioning. In addition osgi supports permissions o
Remy Maucherat wrote:
Costin Manolache wrote:
Both difference and similarity :-).
Eclipse ( osgi actually ) has a similar flat loader implementation,
but with finer control over what is exported/imported and pretty
strong versioning. In addition osgi supports permissions on importing
packages.
T
Costin Manolache wrote:
Both difference and similarity :-).
Eclipse ( osgi actually ) has a similar flat loader implementation,
but with finer control over what is exported/imported and pretty
strong versioning. In addition osgi supports permissions on importing
packages.
The reloading of module
Costin Manolache wrote:
Don't know what "dependency injection" is, but I hope the next spec
won't invent yet another way to do configuration.
Sorry for using hype words. I got contaminated, it can happen to
anyone. I'll try to shake it off now. I apologise to the community
for that, and I won't
Shapira, Yoav wrote:
* Default global and per-host configurations:
- conf///context.xml.default
- conf///web.xml.default
- conf/context.xml
- conf/web.xml
This will lead to the removal of the DefaultContext interface, since
this will fully replace the functionality (while being very simple to
imple
Remy Maucherat wrote:
Costin Manolache wrote:
Remy Maucherat wrote:
Costin Manolache wrote:
Quick question - did you had any discussion on class loaders for
5.next?
It's one area I'm playing with, I want to make sure I'm not going in
oposite direction :-)
I'll tweak the StandardCL to do a bit th
Costin Manolache wrote:
Remy Maucherat wrote:
Costin Manolache wrote:
Quick question - did you had any discussion on class loaders for
5.next?
It's one area I'm playing with, I want to make sure I'm not going in
oposite direction :-)
I'll tweak the StandardCL to do a bit the same as the WebappCL
THIS IS AN AUTOMATED RESPONSE FROM CDZONE
Thank you for contacting us.
If your enquiry is covered by the list below please visit
our web site at http://www.cdzone.co.uk/accounts where you can:
* Check your order status - we are unable to provide any more
detailed information about delivery
Remy Maucherat wrote:
Costin Manolache wrote:
Quick question - did you had any discussion on class loaders for 5.next?
It's one area I'm playing with, I want to make sure I'm not going in
oposite direction :-)
I'll tweak the StandardCL to do a bit the same as the WebappCL (ie, try
to make it fas
Costin Manolache wrote:
Quick question - did you had any discussion on class loaders for 5.next?
It's one area I'm playing with, I want to make sure I'm not going in
oposite direction :-)
I'll tweak the StandardCL to do a bit the same as the WebappCL (ie, try
to make it faster). I'll also remove
Shapira, Yoav wrote:
Hola,
* Redo naming resources configuration using setAllProperties rule to
make the XML less verbose.
Example:
type="com.mycompany.MyBean"
factory="org.apache.naming.factory.BeanFactory"
bar="23"/>
I personally really like this (and use setAllProper
Quick question - did you had any discussion on class loaders for 5.next?
It's one area I'm playing with, I want to make sure I'm not going in
oposite direction :-)
BTW - another feature idea would be to extend the JMX configuration into
the webapps, i.e. allow jmx apps to view and configure cont
Hola,
>* Redo naming resources configuration using setAllProperties rule to
>make the XML less verbose.
>Example:
> type="com.mycompany.MyBean"
>factory="org.apache.naming.factory.BeanFactory"
>bar="23"/>
I personally really like this (and use setAllProperties extensivel
23 matches
Mail list logo