RE: [JBoss-dev] Re: How about a JBoss-2.6 release?
FWIW, I noticed that the service provider spec defines that the config files live in a sub director "services" under META-INF Ie if services.xml is the services config file, shouldn't it be located as follows: META-INF/services/services.xml or was the services.xml file intended as an xml replacement for the contents of the services directory> Cheers, Simon.
Re: [JBoss-dev] Re: How about a JBoss-2.6 release?
marc fleury wrote: > sure thing! why don't you submit that :) you are about to lose your rw > passwd for inactivity in JBoss, you know we have the 3mo rules of > contribution for active developers. I know, and it would be kinda sad to loose the rw 8-) /R -- Rickard Öberg Software Development Specialist xlurc - Xpedio Linköping Ubiquitous Research Center Author of "Mastering RMI" Email: [EMAIL PROTECTED] ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Re: How about a JBoss-2.6 release?
|More clear? sure thing! why don't you submit that :) you are about to lose your rw passwd for inactivity in JBoss, you know we have the 3mo rules of contribution for active developers. marcf | |/Rickard | |-- |Rickard Öberg |Software Development Specialist |xlurc - Xpedio Linköping Ubiquitous Research Center |Author of "Mastering RMI" |Email: [EMAIL PROTECTED] | |___ |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] Re: How about a JBoss-2.6 release?
marc fleury wrote: > |Now, couple that with a Jini-based deploy interface and you have > |something really interesting. > > what do you mean, expand Well, it's how the actual deployment step is done, i.e. getting the JAR to the server. With Jini there are two ways: 1. Use pull: each server has a Jini service that "listens" for available JAR's from a central repository, which is found form the LUS (Jini LookUpService, similar to JNDI but more dynamic). When a JAR is added, it is downloaded and deployed. 2. Use push: each server has a Jini service that one can call deploy(URL) on. The deployer tool can find the servers by looking them up in the LUS. 1. is good because you just say "here are the JAR's to be used for this cluster", i.e. put them in the central repository and let the servers find them by looking them up. Whenever you start a new server it will load them automatically, i.e. you don't have to deploy them manually. 2. is good because you get immediate response whether the deployment succeeded or failed, and you have more control over when the actual deployment is done. Both are useful, and they're not exclusive, i.e. both can be used at the same time. More clear? /Rickard -- Rickard Öberg Software Development Specialist xlurc - Xpedio Linköping Ubiquitous Research Center Author of "Mastering RMI" Email: [EMAIL PROTECTED] ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Re: How about a JBoss-2.6 release?
|If you do, please look at the "Service provider" API in the JAR |specification: |http://java.sun.com/j2se/1.3/docs/guide/jar/jar.html#Service%20Provider I will look at this, |Not quite sure how to use it, but something like calling the file |META-INF/services.xml would probably be a good idea. this is how i call it already. |Now, couple that with a Jini-based deploy interface and you have |something really interesting. what do you mean, expand marcf ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Re: How about a JBoss-2.6 release?
marc fleury wrote: > > |Does this include what we loosely called .sar deployment (i.e. Jar file > |with MBeans and jboss.cfml/services.xml in it)? That would be so cool. > |:-) > > yep. If you do, please look at the "Service provider" API in the JAR specification: http://java.sun.com/j2se/1.3/docs/guide/jar/jar.html#Service%20Provider Not quite sure how to use it, but something like calling the file META-INF/services.xml would probably be a good idea. > You took the infrastructure so far with the MLet but making the stuff really > hot deploy is really a pain, the MLets don't work. I now understand why you > took the december "argument" on our research so personally, you had in fact > ran into these problems during the JMX design. > > You should have corrected me when I said we would not use this EVER in our > codebase ;-) it's the building block. I should have known, research is > never "intellectual curiosity" but almost always finds implementations in > places we expect it least. Ah well, it's on track now at least :-) > You will see, I will try to commit very very soon (I know I have been saying > so for the past 2 weeks) but the MLet stuff is replaced by a > ServiceClassLoader tightly coupled with the MBean/url approach... I think > you will like it, if you understood Dr Jung's work (did you?) Sounds very very nice :-) > A simple work. I take what you had pionneered to its real final form and > its logical conclusion. The microkernel stuff is real and solid imho, even > if it doesn't look like much, it is, I like to believe, ground breaking > work. Yes, agree. Now, couple that with a Jini-based deploy interface and you have something really interesting. /Rickard -- Rickard Öberg Software Development Specialist xlurc - Xpedio Linköping Ubiquitous Research Center Author of "Mastering RMI" Email: [EMAIL PROTECTED] ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Re: How about a JBoss-2.6 release?
versions are misleading. RH is the ongoing cvs HEAD effort, today called 2.5, the CMP stuff is almost finished by Dain, the MQ stuff has really matured to a point where it is production quality thanks to David and hiram, the iiop stuff is getting there thanks to ole and francisco, the http stack is going to be jetty integrated at the core thanks to Julian (soon), the clustering Bill/Sacha, microkernel-jmx-sar with Scott/me/juha (working on book), new build etc etc... so 3.0 is not something we bring out of nowhere after 3 month of tower development it is already happening in the commits under your noses. 3.0 will be all these features STABILIZED, so the version that is coming out soon is the BETA, in fact it will be an ALPHA. clear? marcf |-Original Message- |From: [EMAIL PROTECTED] |[mailto:[EMAIL PROTECTED]]On Behalf Of |Hunter Hillegas |Sent: Wednesday, August 22, 2001 1:42 PM |To: JBoss Dev |Subject: Re: [JBoss-dev] Re: How about a JBoss-2.6 release? | | |Do you mean beta versions or a production quality release? | |Either way, I had no idea it was that far along! That's great! | |Hunter | |> From: "marc fleury" <[EMAIL PROTECTED]> |> Reply-To: [EMAIL PROTECTED] |> Date: Wed, 22 Aug 2001 13:15:40 -0400 |> To: <[EMAIL PROTECTED]> |> Subject: RE: [JBoss-dev] Re: How about a JBoss-2.6 release? |> |> 3.0 is coming out soon, probably by the end of the week/month. | | |___ |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] Re: How about a JBoss-2.6 release?
|Does this include what we loosely called .sar deployment (i.e. Jar file |with MBeans and jboss.cfml/services.xml in it)? That would be so cool. |:-) yep. You took the infrastructure so far with the MLet but making the stuff really hot deploy is really a pain, the MLets don't work. I now understand why you took the december "argument" on our research so personally, you had in fact ran into these problems during the JMX design. You should have corrected me when I said we would not use this EVER in our codebase ;-) it's the building block. I should have known, research is never "intellectual curiosity" but almost always finds implementations in places we expect it least. You will see, I will try to commit very very soon (I know I have been saying so for the past 2 weeks) but the MLet stuff is replaced by a ServiceClassLoader tightly coupled with the MBean/url approach... I think you will like it, if you understood Dr Jung's work (did you?) Re Rabbit Hole, I am now running out of time and need to commit. What I am going to commit is basically the microkernel approach to the JMX stuff, a working URL based deployment (real http farm installs) and the sar hotdeploy approach to the server. SPINE (GPA) + SERVICES = JBOSS. A simple work. I take what you had pionneered to its real final form and its logical conclusion. The microkernel stuff is real and solid imho, even if it doesn't look like much, it is, I like to believe, ground breaking work. marcf ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Re: How about a JBoss-2.6 release?
marc fleury wrote: > 2.4 is going to be the stable one but 3.0 is 2.4 with new features (IIOP, > qualityMQ, CMP, cluster, Microkernel, http based install) Does this include what we loosely called .sar deployment (i.e. Jar file with MBeans and jboss.cfml/services.xml in it)? That would be so cool. :-) BTW, in my current project we have dropped EJB's in favor of MBeans + Jini. So, the EAR hot deployment is not so interesting, but .sar hot deployment would be :-) /Rickard -- Rickard Öberg Software Development Specialist xlurc - Xpedio Linköping Ubiquitous Research Center Author of "Mastering RMI" Email: [EMAIL PROTECTED] ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Re: How about a JBoss-2.6 release?
Do you mean beta versions or a production quality release? Either way, I had no idea it was that far along! That's great! Hunter > From: "marc fleury" <[EMAIL PROTECTED]> > Reply-To: [EMAIL PROTECTED] > Date: Wed, 22 Aug 2001 13:15:40 -0400 > To: <[EMAIL PROTECTED]> > Subject: RE: [JBoss-dev] Re: How about a JBoss-2.6 release? > > 3.0 is coming out soon, probably by the end of the week/month. ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Re: How about a JBoss-2.6 release?
Jason, I totally agree with my partner :) 2.4 is going to be the stable one but 3.0 is 2.4 with new features (IIOP, qualityMQ, CMP, cluster, Microkernel, http based install) etc etc... making a 2.6 version will not bring much if we put all these features. 2.6 will need to be a maintenance release of 2.4 when 3.0 is out. We want a very stable version and that means no new features in there, 2.4 is the word. 3.0 is coming out soon, probably by the end of the week/month. marcf |-Original Message- |From: [EMAIL PROTECTED] |[mailto:[EMAIL PROTECTED]]On Behalf Of Scott |M Stark |Sent: Wednesday, August 22, 2001 11:07 AM |To: [EMAIL PROTECTED] |Subject: [JBoss-dev] Re: How about a JBoss-2.6 release? | | |Every 3-4 months is the release cycle. It will be 6-8 weeks before the next |release branch is made so wether this is 2.6 or 3.0 depends on what gets |put in. | |- Original Message - |From: "Jason Dillon" <[EMAIL PROTECTED]> |To: <[EMAIL PROTECTED]>; "marc fleury" <[EMAIL PROTECTED]> |Cc: <[EMAIL PROTECTED]> |Sent: Wednesday, August 22, 2001 12:20 AM |Subject: How about a JBoss-2.6 release? | | |> Today I finally was able to stabalize my app with the HEAD |branch (which I |> have been trying todo for the past few months). I still have to do much |QA |> before I am willing to take this to production. I expect a few minor |snags, |> but nothing major *fingers crossed*. |> |> Any ways, I think that with all of the JBossMQ, entity locking & logging |> changes that it might be the most stable JBoss ever (well at least more |> stable than the version I have used). |> |> I am not sure what you are planning for a release schedule. I remember |> something a while back about some number of months, but I can not recall |> what they were at the moment. |> |> How about a 3-6 month schedule, which moves based on feature completion, |> would work out the best. But that is just a wild guess backed by a |> little preference. |> |> On an unrelated note, I should have time this week to improve the build |> system docs as win32 build scripts. I would still like to create a |> http://jboss.org/developers/ area to drop all this (plus more) into. |> Probably move cvs stuff there too. |> |> Is this going to be ok? |> |> Hopefully I can also get to the manual & testsuite modules too, so that |> everything is integrated. |> |> --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-dev] Re: How about a JBoss-2.6 release?
Every 3-4 months is the release cycle. It will be 6-8 weeks before the next release branch is made so wether this is 2.6 or 3.0 depends on what gets put in. - Original Message - From: "Jason Dillon" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]>; "marc fleury" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Wednesday, August 22, 2001 12:20 AM Subject: How about a JBoss-2.6 release? > Today I finally was able to stabalize my app with the HEAD branch (which I > have been trying todo for the past few months). I still have to do much QA > before I am willing to take this to production. I expect a few minor snags, > but nothing major *fingers crossed*. > > Any ways, I think that with all of the JBossMQ, entity locking & logging > changes that it might be the most stable JBoss ever (well at least more > stable than the version I have used). > > I am not sure what you are planning for a release schedule. I remember > something a while back about some number of months, but I can not recall > what they were at the moment. > > How about a 3-6 month schedule, which moves based on feature completion, > would work out the best. But that is just a wild guess backed by a > little preference. > > On an unrelated note, I should have time this week to improve the build > system docs as win32 build scripts. I would still like to create a > http://jboss.org/developers/ area to drop all this (plus more) into. > Probably move cvs stuff there too. > > Is this going to be ok? > > Hopefully I can also get to the manual & testsuite modules too, so that > everything is integrated. > > --jason > > ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
