RE: [JBoss-dev] DependencyManager & jboss.dependencies
why don't you figure it out? let us know if it is depracated... marc |-Original Message- |From: [EMAIL PROTECTED] |[mailto:[EMAIL PROTECTED]]On Behalf Of Jason |Dillon |Sent: Friday, April 13, 2001 7:24 PM |To: [EMAIL PROTECTED] |Subject: [JBoss-dev] DependencyManager & jboss.dependencies | | |Is this used anywhere? I could not find anything that read from |'jboss.dependencies' and it looks like the only place where the class is |even imported is in org.jboss.Main (though it is not instantiated). | |Just curious if this is just legacy or still needs to be hooked up. | |--jason | | |___ |Jboss-development mailing list |[EMAIL PROTECTED] |http://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] DependencyManager & jboss.dependencies
No more poor doco excuses: http://www.jboss.org/documentation/HTML/ch02s03.html On 2001.04.13 19:23 marc fleury wrote: > why don't you figure it out? > > let us know if it is depracated... > marc > > > |-Original Message- > |From: [EMAIL PROTECTED] > |[mailto:[EMAIL PROTECTED]]On Behalf Of Jason > |Dillon > |Sent: Friday, April 13, 2001 7:24 PM > |To: [EMAIL PROTECTED] > |Subject: [JBoss-dev] DependencyManager & jboss.dependencies > | > | > |Is this used anywhere? I could not find anything that read from > |'jboss.dependencies' and it looks like the only place where the class is > |even imported is in org.jboss.Main (though it is not instantiated). > | > |Just curious if this is just legacy or still needs to be hooked up. > | > |--jason > | > | > |___ > |Jboss-development mailing list > |[EMAIL PROTECTED] > |http://lists.sourceforge.net/lists/listinfo/jboss-development > > ___ > Jboss-development mailing list > [EMAIL PROTECTED] > http://lists.sourceforge.net/lists/listinfo/jboss-development > ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] DependencyManager & jboss.dependencies
I'm pretty sure it is... but do take a look, just to make sure :) -- Juha At 19:23 13.4.2001 -0400, you wrote: >why don't you figure it out? > >let us know if it is depracated... >marc > > >|-Original Message- >|From: [EMAIL PROTECTED] >|[mailto:[EMAIL PROTECTED]]On Behalf Of Jason >|Dillon >|Sent: Friday, April 13, 2001 7:24 PM >|To: [EMAIL PROTECTED] >|Subject: [JBoss-dev] DependencyManager & jboss.dependencies >| >| >|Is this used anywhere? I could not find anything that read from >|'jboss.dependencies' and it looks like the only place where the class is >|even imported is in org.jboss.Main (though it is not instantiated). >| >|Just curious if this is just legacy or still needs to be hooked up. >| >|--jason >| >| >|___ >|Jboss-development mailing list >|[EMAIL PROTECTED] >|http://lists.sourceforge.net/lists/listinfo/jboss-development > >___ >Jboss-development mailing list >[EMAIL PROTECTED] >http://lists.sourceforge.net/lists/listinfo/jboss-development > ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] DependencyManager & jboss.dependencies
>From my investigation I would say that it is not being used anywhere inside of the jboss project. If this is true, it might be a good idea to at least remove the jboss.dependencies from the conf/default directory so that it does not confuse anyone. I think that the DependencyManager is a good one, so I would not be so quick to suggest that it be removed. --jason On Fri, 13 Apr 2001, marc fleury wrote: > why don't you figure it out? > > let us know if it is depracated... > marc > > > |-Original Message- > |From: [EMAIL PROTECTED] > |[mailto:[EMAIL PROTECTED]]On Behalf Of Jason > |Dillon > |Sent: Friday, April 13, 2001 7:24 PM > |To: [EMAIL PROTECTED] > |Subject: [JBoss-dev] DependencyManager & jboss.dependencies > | > | > |Is this used anywhere? I could not find anything that read from > |'jboss.dependencies' and it looks like the only place where the class is > |even imported is in org.jboss.Main (though it is not instantiated). > | > |Just curious if this is just legacy or still needs to be hooked up. > | > |--jason > | > | > |___ > |Jboss-development mailing list > |[EMAIL PROTECTED] > |http://lists.sourceforge.net/lists/listinfo/jboss-development > > ___ > Jboss-development mailing list > [EMAIL PROTECTED] > http://lists.sourceforge.net/lists/listinfo/jboss-development > ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] DependencyManager & jboss.dependencies
It's not used anywhere. Since most mbeans are loaded in order from jboss.jcml, the DependencyManager is not needed. Am I wrong? Bill -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of marc fleury Sent: Friday, April 13, 2001 7:23 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] DependencyManager & jboss.dependencies why don't you figure it out? let us know if it is depracated... marc |-Original Message- |From: [EMAIL PROTECTED] |[mailto:[EMAIL PROTECTED]]On Behalf Of Jason |Dillon |Sent: Friday, April 13, 2001 7:24 PM |To: [EMAIL PROTECTED] |Subject: [JBoss-dev] DependencyManager & jboss.dependencies | | |Is this used anywhere? I could not find anything that read from |'jboss.dependencies' and it looks like the only place where the class is |even imported is in org.jboss.Main (though it is not instantiated). | |Just curious if this is just legacy or still needs to be hooked up. | |--jason | | |___ |Jboss-development mailing list |[EMAIL PROTECTED] |http://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] DependencyManager & jboss.dependencies
> > I think that the DependencyManager is a good one, so I would not be so > quick to suggest that it be removed. > Oh you dont want to start a war againsee dev archives. Yes it is not bad but I would say it is too explicit and verbose and doesn't do runtime dependencies. It would be nice to try to develop some solution using relations from jmx but it is currently not possible, it will be soon. http://archives.java.sun.com/cgi-bin/wa?A1=ind0104&L=jmx-forum Vladimir > --jason > > > On Fri, 13 Apr 2001, marc fleury wrote: > > > why don't you figure it out? > > > > let us know if it is depracated... > > marc > > > > > > |-Original Message- > > |From: [EMAIL PROTECTED] > > |[mailto:[EMAIL PROTECTED]]On Behalf Of > Jason > > |Dillon > > |Sent: Friday, April 13, 2001 7:24 PM > > |To: [EMAIL PROTECTED] > > |Subject: [JBoss-dev] DependencyManager & jboss.dependencies > > | > > | > > |Is this used anywhere? I could not find anything that read from > > |'jboss.dependencies' and it looks like the only place where the class > is > > |even imported is in org.jboss.Main (though it is not instantiated). > > | > > |Just curious if this is just legacy or still needs to be hooked up. > > | > > |--jason > > | > > | > > |___ > > |Jboss-development mailing list > > |[EMAIL PROTECTED] > > |http://lists.sourceforge.net/lists/listinfo/jboss-development > > > > ___ > > Jboss-development mailing list > > [EMAIL PROTECTED] > > http://lists.sourceforge.net/lists/listinfo/jboss-development > > > > > ___ > Jboss-development mailing list > [EMAIL PROTECTED] > http://lists.sourceforge.net/lists/listinfo/jboss-development > ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] DependencyManager & jboss.dependencies
> Oh you dont want to start a war againsee dev archives. Yes it is not I sure don't. --jason ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] DependencyManager & jboss.dependencies
|>From my investigation I would say that it is not being used anywhere |inside of the jboss project. If this is true, it might be a good |idea to at |least remove the jboss.dependencies from the conf/default directory so that |it does not confuse anyone. correct, |I think that the DependencyManager is a good one, so I would not |be so quick |to suggest that it be removed. it was not a good one, remove it, we need to simplify simplify simplify marc |http://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] DependencyManager & jboss.dependencies
DependencyManager and jboss.dependencies have been removed. I also updated Main to remove the import of DependencyManager. I verified that the system builds correctly and runs with no other modifications too. --jason On Sat, 14 Apr 2001, marc fleury wrote: > |>From my investigation I would say that it is not being used anywhere > |inside of the jboss project. If this is true, it might be a good > |idea to at > |least remove the jboss.dependencies from the conf/default directory so that > |it does not confuse anyone. > > correct, > > |I think that the DependencyManager is a good one, so I would not > |be so quick > |to suggest that it be removed. > > it was not a good one, remove it, we need to simplify simplify simplify > > marc > |http://lists.sourceforge.net/lists/listinfo/jboss-development > > > ___ > Jboss-development mailing list > [EMAIL PROTECTED] > http://lists.sourceforge.net/lists/listinfo/jboss-development > ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] DependencyManager & jboss.dependencies
Wanna take a look at the OpenJMS stuff too? :) It takes a meg in our package, and seems unnecessary as we use JBossMQ for MDB. The old log4j might be a good candidate for removal as well. -- Juha At 14:17 14.4.2001 -0700, you wrote: >DependencyManager and jboss.dependencies have been removed. I also >updated Main to remove the import of DependencyManager. I verified that >the system builds correctly and runs with no other modifications too. > >--jason > >On Sat, 14 Apr 2001, marc fleury wrote: > >> |>From my investigation I would say that it is not being used anywhere >> |inside of the jboss project. If this is true, it might be a good >> |idea to at >> |least remove the jboss.dependencies from the conf/default directory so that >> |it does not confuse anyone. >> >> correct, >> >> |I think that the DependencyManager is a good one, so I would not >> |be so quick >> |to suggest that it be removed. >> >> it was not a good one, remove it, we need to simplify simplify simplify >> >> marc >> |http://lists.sourceforge.net/lists/listinfo/jboss-development >> >> >> ___ >> Jboss-development mailing list >> [EMAIL PROTECTED] >> http://lists.sourceforge.net/lists/listinfo/jboss-development >> > > >___ >Jboss-development mailing list >[EMAIL PROTECTED] >http://lists.sourceforge.net/lists/listinfo/jboss-development > ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] DependencyManager & jboss.dependencies
Ok, it looks like the OpenJMS is only referenced directly in these
files:
o src/main/org/jboss/jms/asf/OpenJMSServerSessionPoolFactory.java:
import org.exolab.jms.client.OpenJMSServerSessionPool;
import org.exolab.jms.client.JmsServerSessionPool;
org.exolab.core.logger.LoggerIfc logger =
org.exolab.core.logger.LoggerFactory.create(null, null);
org.exolab.core.logger.LogEventType event =
org.exolab.core.logger.LogEventType.getLogEventType("debug");
o src/main/org/jboss/jms/jndi/OpenJMSProvider.java:
public static final String INITIAL_CONTEXT_FACTORY =
"org.exolab.jms.jndi.rmi.RmiJndiInitialContextFactory";
private static final String HOST_PROP_NAME="org.exolab.jms.jndi.Host";
private static final String
PORT_PROP_NAME="org.exolab.jms.jndi.PortNumber";
o src/main/org/jboss/ejb/plugins/jms/JMSContainerInvoker.java:
public String getType() { return "org.exolab.castor.jdo.DataObjects";
//import org.exolab.jms.jndi.JndiConstants;
import org.exolab.jms.client.JmsServerSessionPool;
---
The last of which imports an OpenJMS class, but does not make use of it.
Except for JMSContainerInvoker, these classes are not referenced anywhere
else in the system either.
I can understand wanting to clean up unused sources and thirdparty
libraries, but I am wondering what if someone wanted to make use of
OpenJMS? These classes seem like a good candidate for an external plugin
module, but I am not really sure what the precedent is for that.
It would be nice to have a 'plugin' module, which could some child
modules, one for 'openjms'. Perhaps that is what the 'contrib' module is
for?
With the above OpenJMS specific classes removed and these library files:
o src/lib/openjms-client-patched-0.5.1.jar
o src/lib/openjms-patched-0.5.1.jar
o src/lib/openjms-pool.jar
o src/lib/openjms-rmi-patched-0.5.1.jar
I was able to build and execute the default configuration with no errors.
So any ideas on what I should do? Should I proceed and commit these
changes, thus removing OpenJMS support from JBoss, or should I attempt to
preserve these classes in an external project for those who still use
OpenJMS?
I have not investigated the log4j bits yet, are there classes as well as
library files for that too?
--jason
On Sun, 15 Apr 2001, Juha Lindfors wrote:
>
> Wanna take a look at the OpenJMS stuff too? :)
>
> It takes a meg in our package, and seems unnecessary as we use JBossMQ for
> MDB.
> The old log4j might be a good candidate for removal as well.
>
> -- Juha
>
> At 14:17 14.4.2001 -0700, you wrote:
> >DependencyManager and jboss.dependencies have been removed. I also
> >updated Main to remove the import of DependencyManager. I verified that
> >the system builds correctly and runs with no other modifications too.
> >
> >--jason
> >
> >On Sat, 14 Apr 2001, marc fleury wrote:
> >
> >> |>From my investigation I would say that it is not being used anywhere
> >> |inside of the jboss project. If this is true, it might be a good
> >> |idea to at
> >> |least remove the jboss.dependencies from the conf/default directory so
> that
> >> |it does not confuse anyone.
> >>
> >> correct,
> >>
> >> |I think that the DependencyManager is a good one, so I would not
> >> |be so quick
> >> |to suggest that it be removed.
> >>
> >> it was not a good one, remove it, we need to simplify simplify simplify
> >>
> >> marc
> >> |http://lists.sourceforge.net/lists/listinfo/jboss-development
> >>
> >>
> >> ___
> >> Jboss-development mailing list
> >> [EMAIL PROTECTED]
> >> http://lists.sourceforge.net/lists/listinfo/jboss-development
> >>
> >
> >
> >___
> >Jboss-development mailing list
> >[EMAIL PROTECTED]
> >http://lists.sourceforge.net/lists/listinfo/jboss-development
> >
>
> ___
> Jboss-development mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-development
>
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] DependencyManager & jboss.dependencies
Factoring out the openjms stuff from the server to a contrib module seems
like a good idea to me. Ping Peter Antman for comments/help (the email is
at SF) before commiting. Also run mdb tests from test module.
the log4j should be as easy as removing the log4j-old.jar from the cvs,
don't remove any classes, log4j is being used
-- Juha
At 16:31 14.4.2001 -0700, you wrote:
>Ok, it looks like the OpenJMS is only referenced directly in these
>files:
>
> o src/main/org/jboss/jms/asf/OpenJMSServerSessionPoolFactory.java:
>
> import org.exolab.jms.client.OpenJMSServerSessionPool;
> import org.exolab.jms.client.JmsServerSessionPool;
>org.exolab.core.logger.LoggerIfc logger =
> org.exolab.core.logger.LoggerFactory.create(null, null);
>org.exolab.core.logger.LogEventType event =
> org.exolab.core.logger.LogEventType.getLogEventType("debug");
>
> o src/main/org/jboss/jms/jndi/OpenJMSProvider.java:
>
>public static final String INITIAL_CONTEXT_FACTORY =
> "org.exolab.jms.jndi.rmi.RmiJndiInitialContextFactory";
>private static final String HOST_PROP_NAME="org.exolab.jms.jndi.Host";
>private static final String
> PORT_PROP_NAME="org.exolab.jms.jndi.PortNumber";
>
> o src/main/org/jboss/ejb/plugins/jms/JMSContainerInvoker.java:
>
>public String getType() { return "org.exolab.castor.jdo.DataObjects";
>
> //import org.exolab.jms.jndi.JndiConstants;
> import org.exolab.jms.client.JmsServerSessionPool;
>
>---
>
>The last of which imports an OpenJMS class, but does not make use of it.
>Except for JMSContainerInvoker, these classes are not referenced anywhere
>else in the system either.
>
>I can understand wanting to clean up unused sources and thirdparty
>libraries, but I am wondering what if someone wanted to make use of
>OpenJMS? These classes seem like a good candidate for an external plugin
>module, but I am not really sure what the precedent is for that.
>
>It would be nice to have a 'plugin' module, which could some child
>modules, one for 'openjms'. Perhaps that is what the 'contrib' module is
>for?
>
>With the above OpenJMS specific classes removed and these library files:
>
> o src/lib/openjms-client-patched-0.5.1.jar
> o src/lib/openjms-patched-0.5.1.jar
> o src/lib/openjms-pool.jar
> o src/lib/openjms-rmi-patched-0.5.1.jar
>
>I was able to build and execute the default configuration with no errors.
>
>So any ideas on what I should do? Should I proceed and commit these
>changes, thus removing OpenJMS support from JBoss, or should I attempt to
>preserve these classes in an external project for those who still use
>OpenJMS?
>
>I have not investigated the log4j bits yet, are there classes as well as
>library files for that too?
>
>--jason
>
>On Sun, 15 Apr 2001, Juha Lindfors wrote:
>
>>
>> Wanna take a look at the OpenJMS stuff too? :)
>>
>> It takes a meg in our package, and seems unnecessary as we use JBossMQ for
>> MDB.
>> The old log4j might be a good candidate for removal as well.
>>
>> -- Juha
>>
>> At 14:17 14.4.2001 -0700, you wrote:
>> >DependencyManager and jboss.dependencies have been removed. I also
>> >updated Main to remove the import of DependencyManager. I verified that
>> >the system builds correctly and runs with no other modifications too.
>> >
>> >--jason
>> >
>> >On Sat, 14 Apr 2001, marc fleury wrote:
>> >
>> >> |>From my investigation I would say that it is not being used anywhere
>> >> |inside of the jboss project. If this is true, it might be a good
>> >> |idea to at
>> >> |least remove the jboss.dependencies from the conf/default directory so
>> that
>> >> |it does not confuse anyone.
>> >>
>> >> correct,
>> >>
>> >> |I think that the DependencyManager is a good one, so I would not
>> >> |be so quick
>> >> |to suggest that it be removed.
>> >>
>> >> it was not a good one, remove it, we need to simplify simplify simplify
>> >>
>> >> marc
>> >> |http://lists.sourceforge.net/lists/listinfo/jboss-development
>> >>
>> >>
>> >> ___
>> >> Jboss-development mailing list
>> >> [EMAIL PROTECTED]
>> >> http://lists.sourceforge.net/lists/listinfo/jboss-development
>> >>
>> >
>> >
>> >___
>> >Jboss-development mailing list
>> >[EMAIL PROTECTED]
>> >http://lists.sourceforge.net/lists/listinfo/jboss-development
>> >
>>
>> ___
>> Jboss-development mailing list
>> [EMAIL PROTECTED]
>> http://lists.sourceforge.net/lists/listinfo/jboss-development
>>
>
>
>___
>Jboss-development mailing list
>[EMAIL PROTECTED]
>http://lists.sourceforge.net/lists/listinfo/jboss-development
>
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] DependencyManager & jboss.dependencies
Just to clarify, I should talk to Peter about adding a openjms contrib
module. And for the tests, this is from the jbosstest module... perhaps
the bin/mdbtest.sh script? Is there more documentation on this anywhere?
--jason
On Sun, 15 Apr 2001, Juha Lindfors wrote:
>
> Factoring out the openjms stuff from the server to a contrib module seems
> like a good idea to me. Ping Peter Antman for comments/help (the email is
> at SF) before commiting. Also run mdb tests from test module.
>
> the log4j should be as easy as removing the log4j-old.jar from the cvs,
> don't remove any classes, log4j is being used
>
> -- Juha
>
>
> At 16:31 14.4.2001 -0700, you wrote:
> >Ok, it looks like the OpenJMS is only referenced directly in these
> >files:
> >
> > o src/main/org/jboss/jms/asf/OpenJMSServerSessionPoolFactory.java:
> >
> > import org.exolab.jms.client.OpenJMSServerSessionPool;
> > import org.exolab.jms.client.JmsServerSessionPool;
> >org.exolab.core.logger.LoggerIfc logger =
> > org.exolab.core.logger.LoggerFactory.create(null, null);
> >org.exolab.core.logger.LogEventType event =
> > org.exolab.core.logger.LogEventType.getLogEventType("debug");
> >
> > o src/main/org/jboss/jms/jndi/OpenJMSProvider.java:
> >
> >public static final String INITIAL_CONTEXT_FACTORY =
> > "org.exolab.jms.jndi.rmi.RmiJndiInitialContextFactory";
> >private static final String HOST_PROP_NAME="org.exolab.jms.jndi.Host";
> >private static final String
> > PORT_PROP_NAME="org.exolab.jms.jndi.PortNumber";
> >
> > o src/main/org/jboss/ejb/plugins/jms/JMSContainerInvoker.java:
> >
> >public String getType() { return "org.exolab.castor.jdo.DataObjects";
> >
> > //import org.exolab.jms.jndi.JndiConstants;
> > import org.exolab.jms.client.JmsServerSessionPool;
> >
> >---
> >
> >The last of which imports an OpenJMS class, but does not make use of it.
> >Except for JMSContainerInvoker, these classes are not referenced anywhere
> >else in the system either.
> >
> >I can understand wanting to clean up unused sources and thirdparty
> >libraries, but I am wondering what if someone wanted to make use of
> >OpenJMS? These classes seem like a good candidate for an external plugin
> >module, but I am not really sure what the precedent is for that.
> >
> >It would be nice to have a 'plugin' module, which could some child
> >modules, one for 'openjms'. Perhaps that is what the 'contrib' module is
> >for?
> >
> >With the above OpenJMS specific classes removed and these library files:
> >
> > o src/lib/openjms-client-patched-0.5.1.jar
> > o src/lib/openjms-patched-0.5.1.jar
> > o src/lib/openjms-pool.jar
> > o src/lib/openjms-rmi-patched-0.5.1.jar
> >
> >I was able to build and execute the default configuration with no errors.
> >
> >So any ideas on what I should do? Should I proceed and commit these
> >changes, thus removing OpenJMS support from JBoss, or should I attempt to
> >preserve these classes in an external project for those who still use
> >OpenJMS?
> >
> >I have not investigated the log4j bits yet, are there classes as well as
> >library files for that too?
> >
> >--jason
> >
> >On Sun, 15 Apr 2001, Juha Lindfors wrote:
> >
> >>
> >> Wanna take a look at the OpenJMS stuff too? :)
> >>
> >> It takes a meg in our package, and seems unnecessary as we use JBossMQ for
> >> MDB.
> >> The old log4j might be a good candidate for removal as well.
> >>
> >> -- Juha
> >>
> >> At 14:17 14.4.2001 -0700, you wrote:
> >> >DependencyManager and jboss.dependencies have been removed. I also
> >> >updated Main to remove the import of DependencyManager. I verified that
> >> >the system builds correctly and runs with no other modifications too.
> >> >
> >> >--jason
> >> >
> >> >On Sat, 14 Apr 2001, marc fleury wrote:
> >> >
> >> >> |>From my investigation I would say that it is not being used anywhere
> >> >> |inside of the jboss project. If this is true, it might be a good
> >> >> |idea to at
> >> >> |least remove the jboss.dependencies from the conf/default directory so
> >> that
> >> >> |it does not confuse anyone.
> >> >>
> >> >> correct,
> >> >>
> >> >> |I think that the DependencyManager is a good one, so I would not
> >> >> |be so quick
> >> >> |to suggest that it be removed.
> >> >>
> >> >> it was not a good one, remove it, we need to simplify simplify simplify
> >> >>
> >> >> marc
> >> >> |http://lists.sourceforge.net/lists/listinfo/jboss-development
> >> >>
> >> >>
> >> >> ___
> >> >> Jboss-development mailing list
> >> >> [EMAIL PROTECTED]
> >> >> http://lists.sourceforge.net/lists/listinfo/jboss-development
> >> >>
> >> >
> >> >
> >> >___
> >> >Jboss-development mailing list
> >> >[EMAIL PROTECTED]
> >> >http://lists.sourceforge.net/lists/listinfo/jboss-development
> >> >
> >>
> >> ___
> >> Jboss-development mailing list
> >> [EMAIL PROTECTED]
> >> http://l
RE: [JBoss-dev] DependencyManager & jboss.dependencies
Hi, On Sat, 14 Apr 2001, Jason Dillon wrote: > Just to clarify, I should talk to Peter about adding a openjms contrib > module. Yes, he knows the code. > And for the tests, this is from the jbosstest module... perhaps > the bin/mdbtest.sh script? Yep. > Is there more documentation on this anywhere? No, just the source I think. -- Juha ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] DependencyManager & jboss.dependencies
I think that I have finished moving the openjms specific fluff outside of the main jboss module. I was able to run the mdbtest.sh script against the JBossMQ provider, though I have not even tried to test the OpenJMS provider classes. They are mostly unmodified, so I would expect them to continue working as before. Is there any documentation that might need to be updated that is OpenJMS specific? I can not seem to recall anywhere in the online docs where any OpenJMS provider classes were mentioned explicitly, but I can't recall at the moment. The changes to the jboss module are mostly removed files, and I have verified that the current config works and runs the mdbtest.sh with no errors. Any preferences on how to continue? My bias would be to commit these changes soon, so I can move on to other bits. This will effect OpenJMS users, so we should probably add that to a release note also. --jason > On Sat, 14 Apr 2001, Jason Dillon wrote: > > > Just to clarify, I should talk to Peter about adding a openjms contrib > > module. > > Yes, he knows the code. > > > And for the tests, this is from the jbosstest module... perhaps > > the bin/mdbtest.sh script? > > Yep. > > > Is there more documentation on this anywhere? > > No, just the source I think. > > -- Juha > > > > ___ > Jboss-development mailing list > [EMAIL PROTECTED] > http://lists.sourceforge.net/lists/listinfo/jboss-development > ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] DependencyManager & jboss.dependencies
Hi, On Mon, 16 Apr 2001, Jason Dillon wrote: > Any preferences on how to continue? My bias would be to commit these > changes soon, so I can move on to other bits. This will effect OpenJMS > users, so we should probably add that to a release note also. yeah I think you can commit it.. if people don't appreciate the changes, they will send angry emails to you about it, at which point you can consider undoing your changes.. :) anyway, I don't think there are that many JBoss/OpenJMS users out there and the code will still be available in the contrib/ module -- Juha ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] DependencyManager & jboss.dependencies
It looks like log4j-old.jar (which contains classes in org.log4j) is not being referenced by any files in the jboss or contrib/log4j modules (except log4j-old.jar). So, it is *probably* safe to remove this file. --jason On Sun, 15 Apr 2001, Juha Lindfors wrote: > > Wanna take a look at the OpenJMS stuff too? :) > > It takes a meg in our package, and seems unnecessary as we use JBossMQ for > MDB. > The old log4j might be a good candidate for removal as well. > > -- Juha > > At 14:17 14.4.2001 -0700, you wrote: > >DependencyManager and jboss.dependencies have been removed. I also > >updated Main to remove the import of DependencyManager. I verified that > >the system builds correctly and runs with no other modifications too. > > > >--jason > > > >On Sat, 14 Apr 2001, marc fleury wrote: > > > >> |>From my investigation I would say that it is not being used anywhere > >> |inside of the jboss project. If this is true, it might be a good > >> |idea to at > >> |least remove the jboss.dependencies from the conf/default directory so > that > >> |it does not confuse anyone. > >> > >> correct, > >> > >> |I think that the DependencyManager is a good one, so I would not > >> |be so quick > >> |to suggest that it be removed. > >> > >> it was not a good one, remove it, we need to simplify simplify simplify > >> > >> marc > >> |http://lists.sourceforge.net/lists/listinfo/jboss-development > >> > >> > >> ___ > >> Jboss-development mailing list > >> [EMAIL PROTECTED] > >> http://lists.sourceforge.net/lists/listinfo/jboss-development > >> > > > > > >___ > >Jboss-development mailing list > >[EMAIL PROTECTED] > >http://lists.sourceforge.net/lists/listinfo/jboss-development > > > > ___ > Jboss-development mailing list > [EMAIL PROTECTED] > http://lists.sourceforge.net/lists/listinfo/jboss-development > ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
