get back.
-Tom
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Behalf Of Jason
Dillon
Sent: Saturday, March 08, 2003 4:30 PM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-dev] Naming a core module?
This is fine until the naming service is rewritten and starts to make
use
Officer
JBoss Group, LLC
- Original Message -
From: Tom Elrod [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Saturday, March 08, 2003 11:02 PM
Subject: RE: [JBoss-dev] Naming a core module?
I agree that it doesn't make sense to have naming in core. Actually noted
Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Scott M Stark
Sent: Sunday, March 09, 2003 11:16 AM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-dev] Naming a core module?
The only protocols that can be included in the core are those natively
supported by the VM. I
- Original Message -
From: Jeff Haynie [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Sunday, March 09, 2003 8:35 AM
Subject: RE: [JBoss-dev] Naming a core module?
There's a difference between build-time dependencies and run-time
dependencies.
To build the SOAP
On Sunday, March 9, 2003, at 10:35 AM, Jeff Haynie wrote:
If different protocols are desired beyond that and we support them, you
can just add the dependent JARs and they become available.
I think this is what you want ...
I think this is a bad idea. If I want a specific connector available
on
.
-Tom
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Behalf Of Dain
Sundstrom
Sent: Sunday, March 09, 2003 6:23 PM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-dev] Naming a core module?
On Sunday, March 9, 2003, at 10:35 AM, Jeff Haynie wrote:
If different
When did naming become a core module? Appears that a remoting test
depends upon it. Is this what we really want? The core is now
dependent on naming to build... naming is a service, not part of the
core system. Any way we can fix this so the dependencies are not whack?
--jason
: [JBoss-dev] Naming a core module?
When did naming become a core module? Appears that a remoting test
depends upon it. Is this what we really want? The core is now
dependent on naming to build... naming is a service, not part of the
core system. Any way we can fix this so the dependencies
detector into
remoting, but just for source build dependencies only.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Jason Dillon
Sent: Saturday, March 08, 2003 4:12 PM
To: [EMAIL PROTECTED]
Subject: [JBoss-dev] Naming a core module?
When did naming become
, March 08, 2003 4:30 PM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-dev] Naming a core module?
This is fine until the naming service is rewritten and starts to make
use of functionality from system or other core modules. Best
to avoid
these sorts of complications.
--jason
On Sunday
10 matches
Mail list logo