Re: [JBoss-dev] ordering proposal
Sorry for the late response, but this doesn't exist right now, but could be implemented to add jboss dependency managmenet to j2ee deployables. Probably just :SomeObjectName... --jason Bill Burke wrote: >Can you put a dependency tag in jboss.xml? What's the syntax? > >>-Original Message- >>From: Jason Dillon [mailto:[EMAIL PROTECTED]] >>Sent: Wednesday, March 13, 2002 5:53 PM >>To: Bill Burke >>Cc: marc fleury; Scott M Stark; Jboss-Development @ Lists . Sourceforge >>. Net >>Subject: Re: [JBoss-dev] ordering proposal >> >> >>A directory based short-term solution (which does not hint at any >>sysv-like functionality) is probably the easiest to implement and mange. >> >>It will however complicate the management of the system dramatically... >>actually any of the solutions/hacks which have been mentiond will only >>complicate. >> >>Take the N* prefix method, now the scanners need to make sure they sort >>by prefix, such that 05 comes becore 06 and so on. When two deployables >>share the same prefix and one depends on the other, then you must >>reorder. Depending on how complicated your deployment is, this could be >>a pain. >> >>For directories, if you start out with a small number, system, >>user-support, user (or whatever), then if a dependency between a >>component in user-support and user exists, where user-support c depends >>on user c, then you have to artificually create a third directory to >>resolve the conflict. >> >>So, as a user... where do I put my deployable? Does it matter that my >>deployable is of type x? >> >>Some users might like N*, some might like directories... the system >>should be able to handle both... lets not force one or the other. >> >>For the previous example, where beans loaded before the datasource, >>couldn't that be handled by putting a dependency tag in jboss.xml? Or >>is there more to the dependency problem than that? >> >>--jason >> >> >>Bill Burke wrote: >> >>>directory solution is better and easier to maintain IMHO than >>> >>the SXX stuff. >> >>>My gut feeling tells me that with the SXX solution you'll constantly be >>>changing filenames and will create headaches for everyone. Directoy >>>ordering and should be good enough for the implicit >>> >>and explicit >> >>>ordering you need, no? >>> >>>Bill >>> -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of marc fleury Sent: Wednesday, March 13, 2002 11:00 AM To: Scott M Stark; Jboss-Development @ Lists . Sourceforge . Net Subject: RE: [JBoss-dev] ordering proposal |-Original Message- |From: [EMAIL PROTECTED] |[mailto:[EMAIL PROTECTED]]On >>Behalf Of Scott >> |M Stark |Sent: Wednesday, March 13, 2002 8:00 AM |To: Jboss-Development @ Lists . Sourceforge . Net |Subject: Re: [JBoss-dev] ordering proposal | | |Or equivalently, mirror the deploy1, deploy2, ... etc structure in |the ear. | |Case 1: |ear/ |--deploy1/sar |--deploy1/war | |Case 2: |ear/ |--deploy1/war |--deploy2/sar yes, and i actually now prefer the explicit SXX solution for >>naming, doing >> away with rc.d structures. We just order by number SIMPLE, >>ultra SIMPLE >> in the abscence of numbering we deploy after the numbers. marcf | |Then you have the same ordering logic for the fixed directories and |application deployment units. | | |Scott Stark |Chief Technology Officer |JBoss Group, LLC | |- Original Message - |From: "Scott M Stark" <[EMAIL PROTECTED]> |To: "Jboss-Development @ Lists . Sourceforge . Net" |<[EMAIL PROTECTED]> |Sent: Wednesday, March 13, 2002 7:47 AM |Subject: Re: [JBoss-dev] ordering proposal | | |> |> - Original Message - |> From: "marc fleury" <[EMAIL PROTECTED]> |> To: "marc fleury" <[EMAIL PROTECTED]>; "David Jencks" |> <[EMAIL PROTECTED]> |> Cc: "Jboss-Development @ Lists . Sourceforge . Net" |> <[EMAIL PROTECTED]> |> Sent: Wednesday, March 13, 2002 5:42 AM |> Subject: RE: [JBoss-dev] ordering proposal |> |> |> > ok, |> > |> > so i will implement the following |> > |> > deploy directory remains there, you can drop anything in deploy. |> > |> > 3 rules: |> >> > jar/ |> > ---sar |> > ---war/ |> > --jar2 |> > 1- There is an ordering in deploy xml>sar>war>ear>jar or whatever i had |in |> > there before. |> > |> > 2-if you deploy a bean with dependencies, whatever they >>may be, i.e. >> |> > sar/ear/war/rar/jar containment is enough to order. The inner stuff is |> > deployed first |> > so | |> > |> > will result in the following order |> > jar2>sar>war>jar |> > |> > this is great, this is today
Re: [JBoss-dev] ordering proposal
> > >this is great, this is today in cvs, unless a certain someone removed this >as well. > =P >The problem is a painful russian doll structure. > >3- however there are 3 static directories deploy/first, deploy/second, >deploy/third, actually i could call them >deploy/deploy1, deploy/deploy2/deploy3... and allow for arbitrary numbers >but we would provide at least 3. >AND >if you drop something in deploy and deploy1 deploy2 for example > >deploy/sar >deploy1/jar >deploy2/war, sar1 >deploy3/ jar2, ear, xml > >you get > >deploy1-deploy2-deploy3-deploy with ordering from 2 and 1 above so > >jar, sar1, war, jar2, xml, ear, sar > So, if I have an ejb-jar which depends on some code deployed from an xml, which is all used by a service deployed by a sar... where do my files go? This may simplify the code which has to deal with depdenencies... by basically avoiding the problem... but it complicates the user configuration... >voila! no dependency explicitely set but a very simple way of putting stuff >in the right order. It will do the trick. I'll code it if a certain someone >doesn't. > With the recent mod to UDS this will work... just list new directory urls in jboss-service.xml. >rc1-rc6 has been in Unix for 20 years, so let's stop fucking around > Um... ya... well there have already been several others who have commented on this... lets not get confused over runlevels and Sn|Kn ordering... which are there only because the system does not have the capacity to define or ask the services started from the script what the dependecies are. The problem of solving the dependecies automatically inside of the server aren't really that huge... just a bit tricky here and there. We are almost there, with the depends element... but we need to finish off the job... by extending that to j2ee deployables (which can be done by adding support and config to jboss.xml) and by changing the system to wait for all dependencies to be meet before attempting to install any of the service into the spine. Perhaps dependecies should be rethought all together... not that I particularly want to spend any time there... but perhaps someone should. In the mean time I don't think we should move the complexity on to configuration/users. Short-term, sorting ala UDS for scanned directories is enabled. This should fix the issues we have seen... --jason ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Automated JBoss Testsuite Results: 17-March-2002
JBoss daily test results SUMMARY Number of tests run: 542 Successful tests: 525 Errors:10 Failures: 7 [time of test: 17 March 2002 5:38 GMT] [java.version: 1.3.1_02] [java.vendor: Sun Microsystems Inc.] [java.vm.version: 1.3.1_02-b02] [java.vm.name: Java HotSpot(TM) Server VM] [java.vm.info: mixed mode] [os.name: Linux] [os.arch: i386] [os.version: 2.4.9-31] See http://lubega.com for full details NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. Remember - if a test becomes broken after your changes - fix it or fix the test! DETAILS OF ERRORS [details not shown -as this makes the mail too big to reach the sf mailing list] PS BEFORE you commit, run the test suite! Its really is easy, just use the ant target 'run-basic-testsuite' from the build directory. To just run the unit tests (they are quite quick): In the testsuite directory, ./build.sh tests-unit You can run a single test case using: ./build.sh -Dtest=[XXXTestCase] one-test The XXXTestCase is the classname of the junit class to run. So, to run the EJBSpecUnitTestCase use: ./build.sh -Dtest=EJBSpecUnitTestCase one-test To run all tests within a package, use ./build.sh -Dtest=[package] test The package is name of the directory under the org/jboss/test directory that contains the tests to run. So, to run the unit tests in the org.jboss.test.security package use: ./build.sh -Dtest=security test Thanks for all your effort - we really do love you! ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Automated JBoss Testsuite Results: 17-March-2002
JBoss daily test results SUMMARY Number of tests run: 535 Successful tests: 517 Errors:11 Failures: 7 [time of test: 17 March 2002 4:37 GMT] [java.version: 1.3.1] [java.vendor: Sun Microsystems Inc.] [java.vm.version: 1.3.1-b24] [java.vm.name: Java HotSpot(TM) Server VM] [java.vm.info: mixed mode] [os.name: Linux] [os.arch: i386] [os.version: 2.4.9-31] See http://lubega.com for full details NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. Remember - if a test becomes broken after your changes - fix it or fix the test! DETAILS OF ERRORS [details not shown -as this makes the mail too big to reach the sf mailing list] PS BEFORE you commit, run the test suite! Its really is easy, just use the ant target 'run-basic-testsuite' from the build directory. To just run the unit tests (they are quite quick): In the testsuite directory, ./build.sh tests-unit You can run a single test case using: ./build.sh -Dtest=[XXXTestCase] one-test The XXXTestCase is the classname of the junit class to run. So, to run the EJBSpecUnitTestCase use: ./build.sh -Dtest=EJBSpecUnitTestCase one-test To run all tests within a package, use ./build.sh -Dtest=[package] test The package is name of the directory under the org/jboss/test directory that contains the tests to run. So, to run the unit tests in the org.jboss.test.security package use: ./build.sh -Dtest=security test Thanks for all your effort - we really do love you! ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Automated JBoss Testsuite Results: 17-March-2002
JBoss daily test results SUMMARY Number of tests run: 542 Successful tests: 525 Errors:10 Failures: 7 [time of test: 17 March 2002 3:15 GMT] [java.version: 1.3.1] [java.vendor: Blackdown Java-Linux Team] [java.vm.version: Blackdown-1.3.1-02a-FCS] [java.vm.name: Classic VM] [java.vm.info: green threads, nojit] [os.name: Linux] [os.arch: i386] [os.version: 2.4.9-31] See http://lubega.com for full details NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. Remember - if a test becomes broken after your changes - fix it or fix the test! DETAILS OF ERRORS [details not shown -as this makes the mail too big to reach the sf mailing list] PS BEFORE you commit, run the test suite! Its really is easy, just use the ant target 'run-basic-testsuite' from the build directory. To just run the unit tests (they are quite quick): In the testsuite directory, ./build.sh tests-unit You can run a single test case using: ./build.sh -Dtest=[XXXTestCase] one-test The XXXTestCase is the classname of the junit class to run. So, to run the EJBSpecUnitTestCase use: ./build.sh -Dtest=EJBSpecUnitTestCase one-test To run all tests within a package, use ./build.sh -Dtest=[package] test The package is name of the directory under the org/jboss/test directory that contains the tests to run. So, to run the unit tests in the org.jboss.test.security package use: ./build.sh -Dtest=security test Thanks for all your effort - we really do love you! ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Automated JBoss Testsuite Results: 17-March-2002
JBoss daily test results SUMMARY Number of tests run: 542 Successful tests: 525 Errors:10 Failures: 7 [time of test: 17 March 2002 2:5 GMT] [java.version: 1.3.1] [java.vendor: Blackdown Java-Linux Team] [java.vm.version: Blackdown-1.3.1_02a-FCS] [java.vm.name: Java HotSpot(TM) Client VM] [java.vm.info: mixed mode] [os.name: Linux] [os.arch: i386] [os.version: 2.4.9-31] See http://lubega.com for full details NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. Remember - if a test becomes broken after your changes - fix it or fix the test! DETAILS OF ERRORS [details not shown -as this makes the mail too big to reach the sf mailing list] PS BEFORE you commit, run the test suite! Its really is easy, just use the ant target 'run-basic-testsuite' from the build directory. To just run the unit tests (they are quite quick): In the testsuite directory, ./build.sh tests-unit You can run a single test case using: ./build.sh -Dtest=[XXXTestCase] one-test The XXXTestCase is the classname of the junit class to run. So, to run the EJBSpecUnitTestCase use: ./build.sh -Dtest=EJBSpecUnitTestCase one-test To run all tests within a package, use ./build.sh -Dtest=[package] test The package is name of the directory under the org/jboss/test directory that contains the tests to run. So, to run the unit tests in the org.jboss.test.security package use: ./build.sh -Dtest=security test Thanks for all your effort - we really do love you! ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Automated JBoss Testsuite Results: 17-March-2002
JBoss daily test results SUMMARY Number of tests run: 542 Successful tests: 524 Errors:10 Failures: 8 [time of test: 17 March 2002 1:21 GMT] [java.version: 1.3.0] [java.vendor: IBM Corporation] [java.vm.version: 1.3.0] [java.vm.name: Classic VM] [java.vm.info: J2RE 1.3.0 IBM build cx130-20020124 (JIT enabled: jitc)] [os.name: Linux] [os.arch: x86] [os.version: 2.4.9-31] See http://lubega.com for full details NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. Remember - if a test becomes broken after your changes - fix it or fix the test! DETAILS OF ERRORS [details not shown -as this makes the mail too big to reach the sf mailing list] PS BEFORE you commit, run the test suite! Its really is easy, just use the ant target 'run-basic-testsuite' from the build directory. To just run the unit tests (they are quite quick): In the testsuite directory, ./build.sh tests-unit You can run a single test case using: ./build.sh -Dtest=[XXXTestCase] one-test The XXXTestCase is the classname of the junit class to run. So, to run the EJBSpecUnitTestCase use: ./build.sh -Dtest=EJBSpecUnitTestCase one-test To run all tests within a package, use ./build.sh -Dtest=[package] test The package is name of the directory under the org/jboss/test directory that contains the tests to run. So, to run the unit tests in the org.jboss.test.security package use: ./build.sh -Dtest=security test Thanks for all your effort - we really do love you! ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Automated JBoss Testsuite Results: 17-March-2002
JBoss daily test results SUMMARY Number of tests run: 542 Successful tests: 523 Errors:11 Failures: 8 [time of test: 17 March 2002 0:36 GMT] [java.version: 1.3.0] [java.vendor: IBM Corporation] [java.vm.version: 1.3.0] [java.vm.name: Classic VM] [java.vm.info: J2RE 1.3.0 IBM build cx130-20010626 (JIT enabled: jitc)] [os.name: Linux] [os.arch: x86] [os.version: 2.4.9-31] See http://lubega.com for full details NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. Remember - if a test becomes broken after your changes - fix it or fix the test! DETAILS OF ERRORS [details not shown -as this makes the mail too big to reach the sf mailing list] PS BEFORE you commit, run the test suite! Its really is easy, just use the ant target 'run-basic-testsuite' from the build directory. To just run the unit tests (they are quite quick): In the testsuite directory, ./build.sh tests-unit You can run a single test case using: ./build.sh -Dtest=[XXXTestCase] one-test The XXXTestCase is the classname of the junit class to run. So, to run the EJBSpecUnitTestCase use: ./build.sh -Dtest=EJBSpecUnitTestCase one-test To run all tests within a package, use ./build.sh -Dtest=[package] test The package is name of the directory under the org/jboss/test directory that contains the tests to run. So, to run the unit tests in the org.jboss.test.security package use: ./build.sh -Dtest=security test Thanks for all your effort - we really do love you! ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-525412 ] EAR Deployment Problem with
Bugs item #525412, was opened at 2002-03-04 07:47 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=376685&aid=525412&group_id=22866 >Category: JBossServer Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 5 Submitted By: Peter Luttrell (objec) >Assigned to: Adrian Brock (ejort) Summary: EAR Deployment Problem with Initial Comment: According to the dtd for an ejb-jar, (http://java.sun.com/dtd/ejb-jar_2_0.dtd), the value of the element must be . or in another ejb-jar file in the same J2EE application unit. I take this to mean that you can use the name of a bean in another ejb-jar within an ear. In my attached example, the Titan.ear file contains 2 ejb jars: CabinEJB.jar and TravelAgentEJB.jar. In the deployment descriptor for TravelAgentEJB, I have an CabinEJB. "CabinEJB" is the name of the entity bean within CabinEJB.jar. If I deploy this ear on JBoss3.0.0beta, deployment fails because "CabinEJB" is not found. Based on my intrepetation of the spec, I expect it to deploy without a problem. Note that if I rearrange my deployment, such that both ejbs are in the same jar file with the same deployment descriptor, JBoss3.0.0beta deploys it perfectly. JBoss dist: JBoss3.0.0 + Tomcat 4.0.2 posted to sourceforge on 2002-02-22 OS: Redhat7.2 jdk: 1.3.1 To run the sample, which illistrates the problem: open up the build script and set your jboss install dir, then run the deploy-as-an-ear target. If you want to see it work as an ejb jar run deploy-as-a-single-jar target. Here's the first exception caused by this problem: ERROR [StatelessSessionContainer] Exception in service lifecycle operation: create org.jboss.deployment.DeploymentException: Bean CabinEJB not found within this applicaion. at org.jboss.ejb.Container.setupEnvironment(Continer.java:906) Note that the sample code is from Richard Monson-Haefel's book titled Enterprise JavaBeans. -- >Comment By: Adrian Brock (ejort) Date: 2002-03-16 20:36 Message: Logged In: YES user_id=9459 The ear (deployment) level list of containers has been lost during the modifications to include ejbs in sars at any level. The ejb-link is only checking for containers in the same jar. Regards, Adrian -- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=376685&aid=525412&group_id=22866 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] deploy: the votes are in
I thought this worked in alpha (can't remember having any problem with datasource and jars)? If all .sar's (datasources) are deployed before the .jar's, it will solve my problem. Are there any dependencies at deploy time between .jars with beans and ejb-jar.xmls? ejb-links? Isn't most dependencies dicovered when running the beans? (if not, this should be a issue for the 2.x-versions too). Does it take too much time too scan all xml-files in all .?ars first to find the right order? Also if we need to specify dependencies ourself, it is easier to specify in every bean what other ?jar it depends on instead of renumbering the order (renaming many files). Another idea could be to check the timestamps of the files and deploy them in the order they have been deployed the first time. This won't work if some modules is redeployed though. (This is just my opinions on this from a jboss user perspective) Marius On Sat, 2002-03-16 at 15:47, Peter Fagerlund wrote: > on 15-03-2 22.05, David Jencks at [EMAIL PROTECTED] wrote: > > > My opinion still is that handling this automatically is the best solution, > > by converting every kind of dependency into an mbean dependency. If we get > > people used to numbering their files, then they will have a delightful > > opportunity to number them in an order different from that required by an > > actual dependency analysis. > > Yes - automagic is simpler yet very much more complex - economical tho at a > higher initial price ... > > Could ANT genjar http://www.riggshill.com/projects/genjar/ help with > filtering classes in a dependency phase ? ... > > /peter_f > > > ___ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development signature.asc Description: This is a digitally signed message part
Re: [JBoss-dev] deploy: the votes are in
on 15-03-2 22.05, David Jencks at [EMAIL PROTECTED] wrote: > My opinion still is that handling this automatically is the best solution, > by converting every kind of dependency into an mbean dependency. If we get > people used to numbering their files, then they will have a delightful > opportunity to number them in an order different from that required by an > actual dependency analysis. Yes - automagic is simpler yet very much more complex - economical tho at a higher initial price ... Could ANT genjar http://www.riggshill.com/projects/genjar/ help with filtering classes in a dependency phase ? ... /peter_f ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Change Notes-530672 ] JBossMX 1.0 testing
Change Notes item #530672, was opened at 2002-03-16 12:50 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=381174&aid=530672&group_id=22866 Category: JBossMX Group: None Status: Open Priority: 5 Submitted By: Adrian Brock (ejort) Assigned to: Nobody/Anonymous (nobody) Summary: JBossMX 1.0 testing Initial Comment: RelMX_1_0_0_6 Unit tests for Relation service Unit tests for Queries Fixed problem MBeanRegistry sending notifications with the delegate object as source instead of the object name. Regards, Adrian -- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=381174&aid=530672&group_id=22866 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jmx/src/main/test/compliance/query QueryTestCase.java QuerySUITE.java BasicQueryExpTestCase.java
User: ejort
Date: 02/03/16 04:38:52
Modified:src/main/test/compliance/query Tag: BranchMX_1_0
QuerySUITE.java
Added: src/main/test/compliance/query Tag: BranchMX_1_0
QueryTestCase.java
Removed: src/main/test/compliance/query Tag: BranchMX_1_0
BasicQueryExpTestCase.java
Log:
Relations, Queries and MBeanRegistry synched with head
Revision ChangesPath
No revision
No revision
1.1.2.1 +1 -1 jmx/src/main/test/compliance/query/QuerySUITE.java
Index: QuerySUITE.java
===
RCS file: /cvsroot/jboss/jmx/src/main/test/compliance/query/QuerySUITE.java,v
retrieving revision 1.1
retrieving revision 1.1.2.1
diff -u -r1.1 -r1.1.2.1
--- QuerySUITE.java 22 Feb 2002 16:44:33 - 1.1
+++ QuerySUITE.java 16 Mar 2002 12:38:52 - 1.1.2.1
@@ -38,7 +38,7 @@
TestSuite suite = new TestSuite("Query tests");
suite.addTest(new TestSuite(QueryMBeansObjectNameOnlyTestCase.class));
-suite.addTest(new TestSuite(BasicQueryExpTestCase.class));
+suite.addTest(new TestSuite(QueryTestCase.class));
return suite;
}
No revision
No revision
1.1.2.1 +0 -0 jmx/src/main/test/compliance/query/QueryTestCase.java
Index: QueryTestCase.java
===
RCS file: /cvsroot/jboss/jmx/src/main/test/compliance/query/QueryTestCase.java,v
retrieving revision 1.1
retrieving revision 1.1.2.1
diff -u -r1.1 -r1.1.2.1
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jmx/src/main/javax/management AndQueryExp.java BetweenQueryExp.java BinaryComparisonQueryExp.java BinaryOpValueExp.java InQueryExp.java MBeanServerNotification.java MatchQueryExp.java NotQueryExp.java OrQueryExp.java
User: ejort
Date: 02/03/16 04:38:50
Modified:src/main/javax/management Tag: BranchMX_1_0 AndQueryExp.java
BetweenQueryExp.java BinaryComparisonQueryExp.java
BinaryOpValueExp.java InQueryExp.java
MBeanServerNotification.java MatchQueryExp.java
NotQueryExp.java OrQueryExp.java
Log:
Relations, Queries and MBeanRegistry synched with head
Revision ChangesPath
No revision
No revision
1.1.2.1 +8 -2 jmx/src/main/javax/management/AndQueryExp.java
Index: AndQueryExp.java
===
RCS file: /cvsroot/jboss/jmx/src/main/javax/management/AndQueryExp.java,v
retrieving revision 1.1
retrieving revision 1.1.2.1
diff -u -r1.1 -r1.1.2.1
--- AndQueryExp.java 22 Feb 2002 16:44:32 - 1.1
+++ AndQueryExp.java 16 Mar 2002 12:38:50 - 1.1.2.1
@@ -12,9 +12,15 @@
* An And Query Expression.
*
* Returns true only when both expressions are true.
+ *
+ * Revisions:
+ * 20020314 Adrian Brock:
+ *
+ * Fix the human readable expression
+ *
*
* @author mailto:[EMAIL PROTECTED]";>Adrian Brock.
- * @version $Revision: 1.1 $
+ * @version $Revision: 1.1.2.1 $
*/
/*package*/ class AndQueryExp
implements QueryExp
@@ -72,7 +78,7 @@
public String toString()
{
- return new String("(" +first.toString() + " && " + second.toString()) + ")";
+ return new String("(" +first.toString() + ") && (" + second.toString()) + ")";
}
// Protected ---
1.1.2.1 +9 -3 jmx/src/main/javax/management/BetweenQueryExp.java
Index: BetweenQueryExp.java
===
RCS file: /cvsroot/jboss/jmx/src/main/javax/management/BetweenQueryExp.java,v
retrieving revision 1.1
retrieving revision 1.1.2.1
diff -u -r1.1 -r1.1.2.1
--- BetweenQueryExp.java 22 Feb 2002 16:44:32 - 1.1
+++ BetweenQueryExp.java 16 Mar 2002 12:38:50 - 1.1.2.1
@@ -13,9 +13,15 @@
*
* Returns true only when the test expression is between the lower and
* upper bounds inclusive.
+ *
+ * Revisions:
+ * 20020314 Adrian Brock:
+ *
+ * Fix the human readable expression
+ *
*
* @author mailto:[EMAIL PROTECTED]";>Adrian Brock.
- * @version $Revision: 1.1 $
+ * @version $Revision: 1.1.2.1 $
*/
/*package*/ class BetweenQueryExp
implements QueryExp
@@ -108,8 +114,8 @@
public String toString()
{
- return new String("(" +lower.toString() + " <= " + test.toString() +
-" <= " + upper.toString()) + ")";
+ return new String("(" +lower.toString() + ") <= (" + test.toString() +
+") <= (" + upper.toString()) + ")";
}
// Protected ---
1.1.2.1 +34 -3 jmx/src/main/javax/management/BinaryComparisonQueryExp.java
Index: BinaryComparisonQueryExp.java
===
RCS file:
/cvsroot/jboss/jmx/src/main/javax/management/BinaryComparisonQueryExp.java,v
retrieving revision 1.1
retrieving revision 1.1.2.1
diff -u -r1.1 -r1.1.2.1
--- BinaryComparisonQueryExp.java 22 Feb 2002 16:44:32 - 1.1
+++ BinaryComparisonQueryExp.java 16 Mar 2002 12:38:50 - 1.1.2.1
@@ -7,10 +7,16 @@
package javax.management;
/**
- * A Binary Comparison query.
+ * A Binary Comparison query.
+ *
+ * Revisions:
+ * 20020314 Adrian Brock:
+ *
+ * Added human readable string representation.
+ *
*
* @author mailto:[EMAIL PROTECTED]";>Adrian Brock.
- * @version $Revision: 1.1 $
+ * @version $Revision: 1.1.2.1 $
*/
/*package*/ class BinaryComparisonQueryExp
extends QueryExpSupport
@@ -127,7 +133,32 @@
second.setMBeanServer(server);
}
- // Y overrides -
+ // Object overrides
+
+ public String toString()
+ {
+ StringBuffer buffer = new StringBuffer();
+ buffer.append("(");
+ buffer.append(first);
+ buffer.append(")");
+ switch (operation)
+ {
+ case Query.GT:
+ buffer.append(" > "); break;
+ case Query.GE:
+ buffer.append(" >= "); break;
+ case Query.LT:
+ buffer.append(" < "); break;
+ case Query.LE:
+ buffer.append(" <= "); break;
+ case Query.EQ:
+ buffer.append(" == ");
+ }
+ buffer.append("(");
+ buffer.append(second);
+ buffer.append(")");
+ return buffer.toString();
[JBoss-dev] CVS update: jmx/src/main/org/jboss/mx/server/registry BasicMBeanRegistry.java
User: ejort
Date: 02/03/16 04:38:52
Modified:src/main/org/jboss/mx/server/registry Tag: BranchMX_1_0
BasicMBeanRegistry.java
Log:
Relations, Queries and MBeanRegistry synched with head
Revision ChangesPath
No revision
No revision
1.9.2.2 +10 -5
jmx/src/main/org/jboss/mx/server/registry/BasicMBeanRegistry.java
Index: BasicMBeanRegistry.java
===
RCS file:
/cvsroot/jboss/jmx/src/main/org/jboss/mx/server/registry/BasicMBeanRegistry.java,v
retrieving revision 1.9.2.1
retrieving revision 1.9.2.2
diff -u -r1.9.2.1 -r1.9.2.2
--- BasicMBeanRegistry.java 13 Mar 2002 21:17:40 - 1.9.2.1
+++ BasicMBeanRegistry.java 16 Mar 2002 12:38:51 - 1.9.2.2
@@ -55,7 +55,7 @@
* @author mailto:[EMAIL PROTECTED]";>Juha Lindfors.
* @author mailto:[EMAIL PROTECTED]";>Trevor Squires.
* @author mailto:[EMAIL PROTECTED]";>Adrian Brock.
- * @version $Revision: 1.9.2.1 $
+ * @version $Revision: 1.9.2.2 $
*/
public class BasicMBeanRegistry
implements MBeanRegistry, BasicMBeanRegistryMBean
@@ -85,6 +85,11 @@
private MBeanServerDelegate delegate = null;
/**
+* The MBean server delegate's object name.
+*/
+ private ObjectName delegateName = null;
+
+ /**
* The loader repository for loading classes
*/
private LoaderRepository loaderRepository =
LoaderRepository.getDefaultLoaderRepository();
@@ -124,8 +129,8 @@
try
{
this.delegate = new MBeanServerDelegate();
- registerMBean(delegate, new ObjectName(MBEAN_SERVER_DELEGATE),
- null, JMI_DOMAIN);
+ this.delegateName = new ObjectName(MBEAN_SERVER_DELEGATE);
+ registerMBean(delegate, delegateName, null, JMI_DOMAIN);
}
catch (MalformedObjectNameException e)
{
@@ -257,7 +262,7 @@
delegate.sendNotification(
new MBeanServerNotification(
MBeanServerNotification.REGISTRATION_NOTIFICATION,
-delegate, registrationNotificationSequence++, regName));
+delegateName, registrationNotificationSequence++, regName));
return new ServerObjectInstance(regName,
entry.getResourceClassName(),
delegate.getMBeanServerId());
@@ -372,7 +377,7 @@
delegate.sendNotification(
new MBeanServerNotification(
MBeanServerNotification.UNREGISTRATION_NOTIFICATION,
-delegate,
+delegateName,
unregistrationNotificationSequence++,
name
)
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jmx/src/main/javax/management/relation RelationService.java RelationServiceMBean.java RelationTypeSupport.java Role.java RoleList.java RoleUnresolved.java RoleUnresolvedList.java RoleValidator.java
User: ejort
Date: 02/03/16 04:38:51
Modified:src/main/javax/management/relation Tag: BranchMX_1_0
RelationService.java RelationServiceMBean.java
RelationTypeSupport.java Role.java RoleList.java
RoleUnresolved.java RoleUnresolvedList.java
RoleValidator.java
Log:
Relations, Queries and MBeanRegistry synched with head
Revision ChangesPath
No revision
No revision
1.4.2.1 +110 -14 jmx/src/main/javax/management/relation/RelationService.java
Index: RelationService.java
===
RCS file:
/cvsroot/jboss/jmx/src/main/javax/management/relation/RelationService.java,v
retrieving revision 1.4
retrieving revision 1.4.2.1
diff -u -r1.4 -r1.4.2.1
--- RelationService.java 1 Mar 2002 19:25:57 - 1.4
+++ RelationService.java 16 Mar 2002 12:38:51 - 1.4.2.1
@@ -15,7 +15,9 @@
import java.util.Stack;
import javax.management.Attribute;
+import javax.management.AttributeNotFoundException;
import javax.management.InstanceNotFoundException;
+import javax.management.InvalidAttributeValueException;
import javax.management.MBeanException;
import javax.management.MBeanNotificationInfo;
import javax.management.MBeanRegistration;
@@ -32,10 +34,24 @@
/**
* Implements the management interface for a relation service.
*
+ * Revisions:
+ * 20020311 Adrian Brock:
+ *
+ * Fixed setRole for external MBean and exception handling
+ * EmptyStack exception in purging
+ * Unregistered mbeans should only contain relation mbeans
+ * Unregister notifications not working after change to MBean Filter
+ *
+ * 20020312 Adrian Brock:
+ *
+ * Fixed wrong exception types thrown and missing exceptions
+ * Allow null role list in createRelation
+ *
+ *
* @see RelationServiceMBean
*
* @author mailto:[EMAIL PROTECTED]";>Adrian Brock.
- * @version $Revision: 1.4 $
+ * @version $Revision: 1.4.2.1 $
*/
public class RelationService
extends NotificationBroadcasterSupport
@@ -130,12 +146,13 @@
throws IllegalArgumentException, NoSuchMethodException,
RelationServiceNotRegisteredException, InvalidRelationIdException,
InvalidRelationServiceException, RelationTypeNotFoundException,
- InvalidRoleValueException, RoleNotFoundException
+ InvalidRoleValueException, RoleNotFoundException,
+ InstanceNotFoundException
{
// Check we have a relation
-isActive();
if (relation == null)
throw new IllegalArgumentException("null relation");
+isActive();
// Get the information we need from the relation
ObjectName otherService = null;
@@ -153,6 +170,10 @@
roleList = (RoleList) server.invoke(relation, "retrieveAllRoles",
new Object[0], new String[0]);
}
+catch (InstanceNotFoundException e)
+{
+ throw e;
+}
catch (Exception e)
{
throw new NoSuchMethodException("Not a relation or not registered");
@@ -189,7 +210,7 @@
{
String name = relationType.getRelationTypeName();
if (typesByName.containsKey(name))
-throw new IllegalArgumentException("duplicate relation id");
+throw new InvalidRelationTypeException("duplicate relation id: " + name);
validateRelationType(relationType);
typesByName.put(name, relationType);
}
@@ -198,6 +219,9 @@
public Integer checkRoleReading(String roleName, String relationTypeName)
throws IllegalArgumentException, RelationTypeNotFoundException
{
+if (roleName == null)
+ throw new IllegalArgumentException("Null role name");
+
// Get the relation type
RelationType relationType = retrieveRelationTypeForName(relationTypeName);
@@ -224,6 +248,11 @@
Boolean initFlag)
throws IllegalArgumentException, RelationTypeNotFoundException
{
+if (role == null)
+ throw new IllegalArgumentException("Null role name");
+if (initFlag == null)
+ throw new IllegalArgumentException("Null init flag");
+
// Get the relation type
RelationType relationType = retrieveRelationTypeForName(relationTypeName);
@@ -254,7 +283,11 @@
RoleNotFoundException
{
// Take a copy of the role list
-RoleList copy = new RoleList(roleList);
+RoleList copy = null;
+if (roleList != null)
+ copy = new RoleList(roleList);
+else
+ copy = new RoleList();
// Create a relation
isActive();
@@ -284,7 +317,8 @@
synchronized (typesByName)
{
if (typesByName.containsKey(relationTypeName
[JBoss-dev] CVS update: jmx/src/main/test/compliance/query/support BooleanTest.java BooleanTestMBean.java NumberTest.java NumberTestMBean.java
User: ejort
Date: 02/03/16 04:38:52
Modified:src/main/test/compliance/query/support Tag: BranchMX_1_0
NumberTest.java NumberTestMBean.java
Added: src/main/test/compliance/query/support Tag: BranchMX_1_0
BooleanTest.java BooleanTestMBean.java
Log:
Relations, Queries and MBeanRegistry synched with head
Revision ChangesPath
No revision
No revision
1.1.2.1 +38 -3 jmx/src/main/test/compliance/query/support/NumberTest.java
Index: NumberTest.java
===
RCS file: /cvsroot/jboss/jmx/src/main/test/compliance/query/support/NumberTest.java,v
retrieving revision 1.1
retrieving revision 1.1.2.1
diff -u -r1.1 -r1.1.2.1
--- NumberTest.java 22 Feb 2002 16:44:33 - 1.1
+++ NumberTest.java 16 Mar 2002 12:38:52 - 1.1.2.1
@@ -9,19 +9,54 @@
public class NumberTest implements NumberTestMBean
{
- private int number = 0;
+ private Number number;
public NumberTest()
{
}
+ public NumberTest(double number)
+ {
+ this.number = new Double(number);
+ }
+
+ public NumberTest(Double number)
+ {
+ this.number = number;
+ }
+
+ public NumberTest(float number)
+ {
+ this.number = new Float(number);
+ }
+
+ public NumberTest(Float number)
+ {
+ this.number = number;
+ }
+
public NumberTest(int number)
{
+ this.number = new Integer(number);
+ }
+
+ public NumberTest(Integer number)
+ {
+ this.number = number;
+ }
+
+ public NumberTest(long number)
+ {
+ this.number = new Long(number);
+ }
+
+ public NumberTest(Long number)
+ {
this.number = number;
}
- public Integer getNumber()
+ public Number getNumber()
{
- return new Integer(number);
+ return number;
}
}
1.1.2.1 +1 -1 jmx/src/main/test/compliance/query/support/NumberTestMBean.java
Index: NumberTestMBean.java
===
RCS file:
/cvsroot/jboss/jmx/src/main/test/compliance/query/support/NumberTestMBean.java,v
retrieving revision 1.1
retrieving revision 1.1.2.1
diff -u -r1.1 -r1.1.2.1
--- NumberTestMBean.java 22 Feb 2002 16:44:33 - 1.1
+++ NumberTestMBean.java 16 Mar 2002 12:38:52 - 1.1.2.1
@@ -9,5 +9,5 @@
public interface NumberTestMBean
{
- Integer getNumber();
+ Number getNumber();
}
No revision
No revision
1.1.2.1 +0 -0 jmx/src/main/test/compliance/query/support/BooleanTest.java
Index: BooleanTest.java
===
RCS file:
/cvsroot/jboss/jmx/src/main/test/compliance/query/support/BooleanTest.java,v
retrieving revision 1.1
retrieving revision 1.1.2.1
diff -u -r1.1 -r1.1.2.1
1.1.2.1 +0 -0 jmx/src/main/test/compliance/query/support/BooleanTestMBean.java
Index: BooleanTestMBean.java
===
RCS file:
/cvsroot/jboss/jmx/src/main/test/compliance/query/support/BooleanTestMBean.java,v
retrieving revision 1.1
retrieving revision 1.1.2.1
diff -u -r1.1 -r1.1.2.1
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jmx/src/main/test/compliance/server MBeanServerTEST.java
User: ejort
Date: 02/03/16 04:38:53
Modified:src/main/test/compliance/server Tag: BranchMX_1_0
MBeanServerTEST.java
Log:
Relations, Queries and MBeanRegistry synched with head
Revision ChangesPath
No revision
No revision
1.6.2.3 +5 -1 jmx/src/main/test/compliance/server/MBeanServerTEST.java
Index: MBeanServerTEST.java
===
RCS file: /cvsroot/jboss/jmx/src/main/test/compliance/server/MBeanServerTEST.java,v
retrieving revision 1.6.2.2
retrieving revision 1.6.2.3
diff -u -r1.6.2.2 -r1.6.2.3
--- MBeanServerTEST.java 13 Mar 2002 21:18:49 - 1.6.2.2
+++ MBeanServerTEST.java 16 Mar 2002 12:38:53 - 1.6.2.3
@@ -52,7 +52,7 @@
* Tests the MBean server impl. through the MBeanServer interface.
*
* @author mailto:[EMAIL PROTECTED]";>Juha Lindfors.
- * @version $Revision: 1.6.2.2 $
+ * @version $Revision: 1.6.2.3 $
*
*/
public class MBeanServerTEST
@@ -1001,6 +1001,10 @@
// expected
assertTrue(!server.isRegistered(name));
assertTrue(e.getTargetException() instanceof java.lang.RuntimeException);
+ }
+ catch (RuntimeMBeanException e)
+ {
+ fail("FAILS IN RI: RuntimeMBeanException instead of
MBeanRegistrationException?");
}
}
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-530635 ] Lead developer needs some time off
Bugs item #530635, was opened at 2002-03-16 01:33 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=376685&aid=530635&group_id=22866 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Sorry Anonymous (concerneduser) Assigned to: Nobody/Anonymous (nobody) Summary: Lead developer needs some time off Initial Comment: Basically I'm concerned for Marc Fleury. The man doesn't seem to sleep at all, and it shows. The last month or so things have gone downhill fast, and I'm actually worried (yeah, seriously). Last weeks "suck my dick"-comment to some guy daring to ask for (*gasp*) an updated manual is just one example of what's happening. At least give him a week off after the London training. I think the quality of JBoss 3.0 will benefit from this. Good luck. -- Comment By: Nobody/Anonymous (nobody) Date: 2002-03-16 03:54 Message: Logged In: NO This problem will go away when I commit my unified developer changes. -- Comment By: Nobody/Anonymous (nobody) Date: 2002-03-16 03:03 Message: Logged In: NO Further analysis of this problem confirms that the "attitude module" needs to be realigned slightly towards the corporate to facilitate mainstream adoption (and thus success) of the project that so many have made such an investment in (both developers and consumers). -- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=376685&aid=530635&group_id=22866 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] RE: [JBoss-user] JBOSS 3.x FINAL
Comments like this jeopardize the investment of a bunch of hard-working JBoss developers and an even larger number of corporate developers that are attempting to server as evangelists for the product. James politely made perfectly valid comments about his experience and offered intelligent suggestions for the product. In the best interest of JBoss, he even offered to help. Marc, I know you and others are working extremely hard to make this a world-class product, and you're doing a great job. But a world-class product obviously has to have customers, and those customers deserve respect. Sincerely, Brian Sondergaard P.S. I'll buy you a pitcher (or two) next week in SF. - Original Message - From: "marc fleury" <[EMAIL PROTECTED]> To: "Trawick, James" <[EMAIL PROTECTED]>; "Jboss-Development@Lists. Sourceforge. Net" <[EMAIL PROTECTED]>; "Jboss-User@Lists. Sourceforge. Net" <[EMAIL PROTECTED]> Sent: Thursday, March 14, 2002 10:22 PM Subject: RE: [JBoss-dev] RE: [JBoss-user] JBOSS 3.x FINAL > mr trawick james, > > suck my dick > > marcf > > > |-Original Message- > |From: [EMAIL PROTECTED] > |[mailto:[EMAIL PROTECTED]]On Behalf Of > |Trawick, James > |Sent: Thursday, March 14, 2002 12:33 PM > |To: Jboss-Development@Lists. Sourceforge. Net; Jboss-User@Lists. > |Sourceforge. Net > |Subject: RE: [JBoss-dev] RE: [JBoss-user] JBOSS 3.x FINAL > | > | > |Not unfounded, personally proven. > | > |In any case there needs to be some sort of kickstart and executive summary > |for the new JBoss features. If it means that I'll finally get the answers > |I'm looking for without holding for three hours and/or putting up with the > |hellfire here, I'll be more than happy to help produce that. > | > |I was not aware that the docs for sale were actually available. My > |experience has been the exact opposite. On three separate occaisons over > |the past couple of months I've attempted to purchase the clustering > |documentation. Each time I received a message saying that there was a > |problem with their side of the transaction and a support rep would be in > |contact with me. Despite multiple attempts to open communications about > |these cases with Flashline, they have failed to do so. Emails apparently > |went to the bit bucket and their phone support reps have proven to be > |anywhere from rude to utterly incompetant. So for my purposes, the docs > |aren't real because for whatever reason I can't get to them despite my > |willingness to pay the mere $10 for quality documentation. At least they > |didn't charge me for it. > | > |chris > | > |-Original Message- > |From: Bill Burke [mailto:[EMAIL PROTECTED]] > |Sent: Thursday, March 14, 2002 3:10 PM > |To: Trawick, James > |Cc: Jboss-Development@Lists. Sourceforge. Net; Jboss-User@Lists. > |Sourceforge. Net > |Subject: RE: [JBoss-dev] RE: [JBoss-user] JBOSS 3.x FINAL > | > | > |Clustering docs are available for purchase. > | > |http://www.flashline.com/components/productsbyvendor.jsp?&vendorid= > |1376&affi > |liateid=260343 > | > |I've also written an article on "clustering" JBoss 2.4.x > | > |http://www.onjava.com/pub/a/onjava/2001/09/18/jboss.html > | > |Clustering features in JBoss beta: > |HA-JNDI, HA-RMI, EJBs(EB, SLSB, SFSB) Failover and load-balancing > | > |The code for HTTP Session Failover is in CVS, but is a work in progress. > |Ask Sacha and Julian how it's going. I don't work on this stuff. HTTP > |Session Failover will probably only be available for Jetty. > | > |I don't know what you're talking about when you say docs for sale aren't > |real, because we've already sold at least a 100 copies of the clustering > |docs. Sacha and I have gotten good feedback on these docs so your > |complaints are unfounded. > | > |> -Original Message- > |> From: [EMAIL PROTECTED] > |> [mailto:[EMAIL PROTECTED]]On Behalf Of > |> Trawick, James > |> Sent: Thursday, March 14, 2002 2:28 PM > |> To: 'David Ward' > |> Cc: 'marc fleury'; Jboss-Development@Lists. Sourceforge. Net; > |> Jboss-User@Lists. Sourceforge. Net > |> Subject: [JBoss-dev] RE: [JBoss-user] JBOSS 3.x FINAL > |> > |> > |> What I'm really interested in is the more corporate questions > |(we're still > |> battling for JBoss over Weblogic, and clustering is a real sore > |> point). How > |> does JBoss 3 clustering interact with web container clustering? > |> If they're > |> completely separate (which I'm pretty sure is the case, as it was > |> last time > |> I walked through the code), how can I put together a full clustered J2EE > |> stack with JBoss and (for example) Tomcat/Catalina? To what level does > |> JBoss provide high-availability? What are some failover scenarios? How > |> does one initiate a graceful failover for server maintenance? How > |> flexible/controllable is JBoss clustering in reality? > |> > | > |Failover scenarios? > |- failed network card > |- server crash > |- application crash > |- What else? > | > |Initiate graceful failover for Server maintain
[JBoss-dev] [ jboss-Bugs-530635 ] Lead developer needs some time off
Bugs item #530635, was opened at 2002-03-16 01:33 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=376685&aid=530635&group_id=22866 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Sorry Anonymous (concerneduser) Assigned to: Nobody/Anonymous (nobody) Summary: Lead developer needs some time off Initial Comment: Basically I'm concerned for Marc Fleury. The man doesn't seem to sleep at all, and it shows. The last month or so things have gone downhill fast, and I'm actually worried (yeah, seriously). Last weeks "suck my dick"-comment to some guy daring to ask for (*gasp*) an updated manual is just one example of what's happening. At least give him a week off after the London training. I think the quality of JBoss 3.0 will benefit from this. Good luck. -- Comment By: Nobody/Anonymous (nobody) Date: 2002-03-16 03:03 Message: Logged In: NO Further analysis of this problem confirms that the "attitude module" needs to be realigned slightly towards the corporate to facilitate mainstream adoption (and thus success) of the project that so many have made such an investment in (both developers and consumers). -- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=376685&aid=530635&group_id=22866 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] RE: [JBoss-user] JBOSS 3.x FINAL
Guys, I'm not sure why James is getting flamed to such an extent for mostly saying that the Flashline system is not working??? Whatever - I just tested it and it worked fine for me??!?!?!? James' suggestion about a summary of the new features and current state is not a bad one. but I guess that is being addressed by the wiki discussion (The webmacro wiki is good. Twiki used to crash a lot for me). Note that open an slather wiki site will get lots of contributions, but will not make great doco, plus it will get trashed at least once a month - from my experience of using wiki with Jetty. So I would say try to constrain what we use it for to what it is good at - recording current status and FAQs. People should still be writing doco. cheers marc fleury wrote: > mr trawick james, > > suck my dick > > marcf > > > |-Original Message- > |From: [EMAIL PROTECTED] > |[mailto:[EMAIL PROTECTED]]On Behalf Of > |Trawick, James > |Sent: Thursday, March 14, 2002 12:33 PM > |To: Jboss-Development@Lists. Sourceforge. Net; Jboss-User@Lists. > |Sourceforge. Net > |Subject: RE: [JBoss-dev] RE: [JBoss-user] JBOSS 3.x FINAL > | > | > |Not unfounded, personally proven. > | > |In any case there needs to be some sort of kickstart and executive summary > |for the new JBoss features. If it means that I'll finally get the answers > |I'm looking for without holding for three hours and/or putting up with the > |hellfire here, I'll be more than happy to help produce that. > | > |I was not aware that the docs for sale were actually available. My > |experience has been the exact opposite. On three separate occaisons over > |the past couple of months I've attempted to purchase the clustering > |documentation. Each time I received a message saying that there was a > |problem with their side of the transaction and a support rep would be in > |contact with me. Despite multiple attempts to open communications about > |these cases with Flashline, they have failed to do so. Emails apparently > |went to the bit bucket and their phone support reps have proven to be > |anywhere from rude to utterly incompetant. So for my purposes, the docs > |aren't real because for whatever reason I can't get to them despite my > |willingness to pay the mere $10 for quality documentation. At least they > |didn't charge me for it. > | > |chris > | > |-Original Message- > |From: Bill Burke [mailto:[EMAIL PROTECTED]] > |Sent: Thursday, March 14, 2002 3:10 PM > |To: Trawick, James > |Cc: Jboss-Development@Lists. Sourceforge. Net; Jboss-User@Lists. > |Sourceforge. Net > |Subject: RE: [JBoss-dev] RE: [JBoss-user] JBOSS 3.x FINAL > | > | > |Clustering docs are available for purchase. > | > |http://www.flashline.com/components/productsbyvendor.jsp?&vendorid= > |1376&affi > |liateid=260343 > | > |I've also written an article on "clustering" JBoss 2.4.x > | > |http://www.onjava.com/pub/a/onjava/2001/09/18/jboss.html > | > |Clustering features in JBoss beta: > |HA-JNDI, HA-RMI, EJBs(EB, SLSB, SFSB) Failover and load-balancing > | > |The code for HTTP Session Failover is in CVS, but is a work in progress. > |Ask Sacha and Julian how it's going. I don't work on this stuff. HTTP > |Session Failover will probably only be available for Jetty. > | > |I don't know what you're talking about when you say docs for sale aren't > |real, because we've already sold at least a 100 copies of the clustering > |docs. Sacha and I have gotten good feedback on these docs so your > |complaints are unfounded. > | > |> -Original Message- > |> From: [EMAIL PROTECTED] > |> [mailto:[EMAIL PROTECTED]]On Behalf Of > |> Trawick, James > |> Sent: Thursday, March 14, 2002 2:28 PM > |> To: 'David Ward' > |> Cc: 'marc fleury'; Jboss-Development@Lists. Sourceforge. Net; > |> Jboss-User@Lists. Sourceforge. Net > |> Subject: [JBoss-dev] RE: [JBoss-user] JBOSS 3.x FINAL > |> > |> > |> What I'm really interested in is the more corporate questions > |(we're still > |> battling for JBoss over Weblogic, and clustering is a real sore > |> point). How > |> does JBoss 3 clustering interact with web container clustering? > |> If they're > |> completely separate (which I'm pretty sure is the case, as it was > |> last time > |> I walked through the code), how can I put together a full clustered J2EE > |> stack with JBoss and (for example) Tomcat/Catalina? To what level does > |> JBoss provide high-availability? What are some failover scenarios? How > |> does one initiate a graceful failover for server maintenance? How > |> flexible/controllable is JBoss clustering in reality? > |> > | > |Failover scenarios? > |- failed network card > |- server crash > |- application crash > |- What else? > | > |Initiate graceful failover for Server maintainance? > |Just gracefully shutdown jboss. The Cluster dynamically figures out > |topology. Topology information is piggy-backed over invocation > |responses to > |client proxies when it changes. > | > |How flexible/controlla
[JBoss-dev] [ jboss-Bugs-530635 ] Lead developer needs some time off
Bugs item #530635, was opened at 2002-03-16 09:33 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=376685&aid=530635&group_id=22866 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Sorry Anonymous (concerneduser) Assigned to: Nobody/Anonymous (nobody) Summary: Lead developer needs some time off Initial Comment: Basically I'm concerned for Marc Fleury. The man doesn't seem to sleep at all, and it shows. The last month or so things have gone downhill fast, and I'm actually worried (yeah, seriously). Last weeks "suck my dick"-comment to some guy daring to ask for (*gasp*) an updated manual is just one example of what's happening. At least give him a week off after the London training. I think the quality of JBoss 3.0 will benefit from this. Good luck. -- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=376685&aid=530635&group_id=22866 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] RE: [JBoss-user] JBOSS 3.x FINAL
Does it really matter that the wiki be j2ee? What about one just based on servlets? I expect that we will want to run a Java based system too... though that is kind of a shame, since there are lots of PHP apps out there which could complement JBoss.org. Anyways, I just took a quick look at the different projects on sf.net which poped up with "java wiki"... probably dosen't matter too much which one it is. Based on activity alone it looks like we should choose in this order: 1) Java Wiki/Webtrans (96%) 2) Chiki Wiki (40%) 3) Very Quick Wiki (35%) --jason _ View thread online: http://main.jboss.org/thread.jsp?forum=66&thread=10925 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jboss-system/src/main/org/jboss/deployment/scanner URLDeploymentScanner.java
User: user57
Date: 02/03/16 00:40:44
Modified:src/main/org/jboss/deployment/scanner
URLDeploymentScanner.java
Log:
o Directory listings are now sorted as a shorterm fix for some deployment
dependency issues.
Revision ChangesPath
1.5 +26 -5
jboss-system/src/main/org/jboss/deployment/scanner/URLDeploymentScanner.java
Index: URLDeploymentScanner.java
===
RCS file:
/cvsroot/jboss/jboss-system/src/main/org/jboss/deployment/scanner/URLDeploymentScanner.java,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- URLDeploymentScanner.java 2 Mar 2002 09:59:12 - 1.4
+++ URLDeploymentScanner.java 16 Mar 2002 08:40:44 - 1.5
@@ -32,11 +32,13 @@
import org.jboss.util.NullArgumentException;
+import org.jboss.deployment.DeploymentSorter;
+
/**
* A URL-based deployment scanner. Supports local directory
* scanning for file-based urls.
*
- * @version $Revision: 1.4 $
+ * @version $Revision: 1.5 $
* @author mailto:[EMAIL PROTECTED]";>Jason Dillon
*/
public class URLDeploymentScanner
@@ -52,6 +54,9 @@
/** The server's home directory, for relative paths. */
protected File serverHome;
+ /** HACK to sort urls from a scaned directory. */
+ protected DeploymentSorter sorter = new DeploymentSorter();
+
public void setURLList(final List list)
{
if (list == null)
@@ -332,7 +337,7 @@
return deployedSet.contains(du);
}
- public void scan() throws Exception
+ public synchronized void scan() throws Exception
{
if (urlList == null)
throw new IllegalStateException("not initialized");
@@ -433,7 +438,7 @@
}
return;
}
-
+
// if it is not a directory, and it is not deployed then add it
if (!file.isDirectory()) {
// just a plain file which isn't deployed
@@ -446,7 +451,10 @@
if (files == null) {
throw new Exception("Null files returned from directory listing");
}
-
+
+ // list of urls to deploy
+ List list = new LinkedList();
+
for (int i = 0; i < files.length; i++)
{
if (files[i].isDirectory()) {
@@ -463,8 +471,21 @@
// It is a new file
url = files[i].toURL();
if (!isDeployed(url)) {
-deploy(new DeployedURL(url));
+list.add(url);
}
+ }
+
+ //
+ // HACK, sort the elements so dependencies have a better chance of working
+ //
+ list = sorter.sortURLs(list);
+
+ // deploy each url
+ Iterator iter = list.iterator();
+ while (iter.hasNext())
+ {
+ url = (URL)iter.next();
+ deploy(new DeployedURL(url));
}
}
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jboss-system/src/main/org/jboss/deployment DeploymentSorter.java
User: user57
Date: 02/03/16 00:40:44
Modified:src/main/org/jboss/deployment DeploymentSorter.java
Log:
o Directory listings are now sorted as a shorterm fix for some deployment
dependency issues.
Revision ChangesPath
1.3 +32 -1 jboss-system/src/main/org/jboss/deployment/DeploymentSorter.java
Index: DeploymentSorter.java
===
RCS file:
/cvsroot/jboss/jboss-system/src/main/org/jboss/deployment/DeploymentSorter.java,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- DeploymentSorter.java 2 Mar 2002 08:37:43 - 1.2
+++ DeploymentSorter.java 16 Mar 2002 08:40:43 - 1.3
@@ -15,12 +15,14 @@
import java.util.ArrayList;
import java.util.Iterator;
+import java.net.URL;
+
import org.jboss.util.NullArgumentException;
/**
* A helper class for sorting deployments.
*
- * @version $Revision: 1.2 $
+ * @version $Revision: 1.3 $
* @author mailto:[EMAIL PROTECTED]";>Jason Dillon
*/
public class DeploymentSorter
@@ -62,6 +64,35 @@
if (di.url.toString().endsWith(suffixOrder[i]))
{
list.add(di);
+ it.remove();
+}
+ }
+ }
+
+ // Unknown types deployed at the end
+ list.addAll(copy);
+
+ return list;
+ }
+
+ /**
+* Returns a sorted list given the list of urls based on {@link #suffixOrder}.
+*/
+ public List sortURLs(final List urls)
+ {
+ // sort a copy, so we don't kill the original!
+ ArrayList list = new ArrayList(urls.size());
+
+ Set copy = new HashSet(urls);
+ for (int i = 0 ; i < suffixOrder.length ; i++)
+ {
+ for (Iterator it = copy.iterator(); it.hasNext();)
+ {
+URL url = (URL)it.next();
+
+if (url.toString().endsWith(suffixOrder[i]))
+{
+ list.add(url);
it.remove();
}
}
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
