[JBoss-dev] Fwd: ests on different OS'es

2001-10-30 Thread Chris Kimpton

Hi Peter 

[I sent this to the list - hope you don't mind - just to mix in any
other ideas]

There was some talk about the compile farm a few months back... and I
tihnk it could be a way to go... We'd just need to see if we can
automate all the work - eg cronjobs/at-jobs to automate and getting
the stuff off the box, scp all the way to a public server.

Although the biggest problem I see is that they have no Windoze
servers - which I think is where we need regular testing.

I think the tinderbox ( http://mozilla.org/projects/tinderbox/ ) (or
similar) route seems the way to go - that is, a central server for
results and then various servers for generating/submitting results. 
It provides lots of info on when builds break and can highlight the
code that causes the break - from what I've read   ;-)

This should allow practically anyone to use their dev pc as a test
machine - after you run the tests, you can submit the results to the
central server (although I maybe asking too much from tinderbox
here...)

This is what I want to look at next.

Chris

--- Peter Fagerlund [EMAIL PROTECTED] wrote:
 Date: Mon, 29 Oct 2001 18:37:01 +0100
 Subject: ests on different OS'es
 From: Peter Fagerlund [EMAIL PROTECTED]
 To: Chris Kimpton [EMAIL PROTECTED]
 
 Chris,
 
 have You seen Guide to the SourceForge.net Compile Farm
 http://sourceforge.net/docman/display_doc.php?docid=762group_id=1
 
 Could We use that ? ... to also test on other plattforms and have
 an ant
 task auto uppload the results for presentation ??? ...
 
 What do u think ? ...
 
 /peter_f
 


=
Need somewhere to Live in London? - Then go to http://freeflats.com

__
Do You Yahoo!?
Make a great connection at Yahoo! Personals.
http://personals.yahoo.com

___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] Commiting minor changes to contrib/iiop

2001-10-30 Thread Francisco Reverbel

Ole,

I'm about to commit a few minor fixes to the contrib/iiop module (files
Attribute Analysis, ContainerAnalysis, and ExceptionAnalysis in package
org.jboss.iiop.rmi). Please let me know if you see something wrong in
these fixes.

Best regards,

Francisco



___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] CVS update: contrib/iiop/src/main/org/jboss/iiop/rmi AttributeAnalysis.java

2001-10-30 Thread Francisco Reverbel

  User: reverbel
  Date: 01/10/30 04:26:05

  Modified:iiop/src/main/org/jboss/iiop/rmi AttributeAnalysis.java
  Log:
  Converting to lower case the first character of an attribute name unless both
  the first and second characters are upper case.
  
  Revision  ChangesPath
  1.3   +10 -1 contrib/iiop/src/main/org/jboss/iiop/rmi/AttributeAnalysis.java
  
  Index: AttributeAnalysis.java
  ===
  RCS file: 
/cvsroot/jboss/contrib/iiop/src/main/org/jboss/iiop/rmi/AttributeAnalysis.java,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- AttributeAnalysis.java2001/08/08 20:19:39 1.2
  +++ AttributeAnalysis.java2001/10/30 12:26:05 1.3
  @@ -20,7 +20,7 @@
*  Specification, version 1.1 (01-06-07).
*  
*  @author a href=mailto:[EMAIL PROTECTED];Ole Husgaard/a
  - *  @version $Revision: 1.2 $
  + *  @version $Revision: 1.3 $
*/
   public class AttributeAnalysis
  extends AbstractAnalysis
  @@ -138,6 +138,15 @@
  void setIDLName(String idlName)
  {
 super.setIDLName(idlName);
  +
  +  // If the first char is an uppercase letter and the second char is not
  +  // an uppercase letter, then convert the first char to lowercase.
  +  if (idlName.charAt(0) = 0x41  idlName.charAt(0) = 0x5a 
  +(idlName.length() = 1
  +   || idlName.charAt(1)  0x41 || idlName.charAt(1)  0x5a)) {
  +  idlName = 
  + idlName.substring(0, 1).toLowerCase() + idlName.substring(1);
  +  }
   
 if (accessorAnalysis != null)
accessorAnalysis.setIDLName(_get_ + idlName);
  
  
  

___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] CVS update: contrib/iiop/src/main/org/jboss/iiop/rmi ContainerAnalysis.java

2001-10-30 Thread Francisco Reverbel

  User: reverbel
  Date: 01/10/30 04:34:58

  Modified:iiop/src/main/org/jboss/iiop/rmi ContainerAnalysis.java
  Log:
  Fixing minor bugs in toHexString() (a typo), analyzeMethods() (misplaced
  initialization of the mutators array), and fixupOverloadedOperationNames()
  (argument types are now separated by double underscores).
  
  Revision  ChangesPath
  1.4   +9 -5  contrib/iiop/src/main/org/jboss/iiop/rmi/ContainerAnalysis.java
  
  Index: ContainerAnalysis.java
  ===
  RCS file: 
/cvsroot/jboss/contrib/iiop/src/main/org/jboss/iiop/rmi/ContainerAnalysis.java,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- ContainerAnalysis.java2001/08/10 16:14:31 1.3
  +++ ContainerAnalysis.java2001/10/30 12:34:58 1.4
  @@ -42,7 +42,7 @@
*  Specification, version 1.1 (01-06-07).
*  
*  @author a href=mailto:[EMAIL PROTECTED];Ole Husgaard/a
  - *  @version $Revision: 1.3 $
  + *  @version $Revision: 1.4 $
*/
   public abstract class ContainerAnalysis
  extends ClassAnalysis
  @@ -270,7 +270,7 @@
 String s = Integer.toHexString(i).toUpperCase();

 if (s.length()  8)
  - return .substring(8 - s.length()) + s;
  + return .substring(0, 8 - s.length()) + s;
 else
return s;
  }
  @@ -282,7 +282,7 @@
 String s = Long.toHexString(l).toUpperCase();

 if (s.length()  16)
  - return .substring(16 - s.length()) + s;
  + return .substring(0, 16 - s.length()) + s;
 else
return s;
  }
  @@ -398,10 +398,11 @@
 mutators = new int[methods.length];

 // Find read-write properties
  +  for (int i = 0; i  methods.length; ++i)
  + mutators[i] = -1; // no mutator here
 for (int i = 0; i  methods.length; ++i) {
   System.err.println(analyzeMethods(): method[+i+].getName()=\ +
  methods[i].getName() + \.);
  - mutators[i] = -1; // no mutator here
   
if (isAccessor(methods[i])  (m_flags[i]M_READ) == 0) {
   Class iReturn = methods[i].getReturnType();
  @@ -587,12 +588,15 @@
// Calculate new IDL name
ParameterAnalysis[] parms = oa.getParameters();
StringBuffer b = new StringBuffer(oa.getIDLName());
  - b.append('_');
  + if (parms.length == 0)
  +b.append(__);
for (int j = 0; j  parms.length; ++j) {
   String s = parms[j].getTypeIDLName();
   
   if (s.startsWith(::))
  s = s.substring(2);
  +
  +b.append('_');
   
   while (!.equals(s)) {
  int idx = s.indexOf(::);
  
  
  

___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] CVS update: contrib/iiop/src/main/org/jboss/iiop/rmi ExceptionAnalysis.java

2001-10-30 Thread Francisco Reverbel

  User: reverbel
  Date: 01/10/30 04:37:39

  Modified:iiop/src/main/org/jboss/iiop/rmi ExceptionAnalysis.java
  Log:
  Fixing a typo in the doAnalyze() method.
  
  Revision  ChangesPath
  1.3   +2 -2  contrib/iiop/src/main/org/jboss/iiop/rmi/ExceptionAnalysis.java
  
  Index: ExceptionAnalysis.java
  ===
  RCS file: 
/cvsroot/jboss/contrib/iiop/src/main/org/jboss/iiop/rmi/ExceptionAnalysis.java,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- ExceptionAnalysis.java2001/08/08 20:19:39 1.2
  +++ ExceptionAnalysis.java2001/10/30 12:37:39 1.3
  @@ -36,7 +36,7 @@
*  Specification, version 1.1 (01-06-07).
*  
*  @author a href=mailto:[EMAIL PROTECTED];Ole Husgaard/a
  - *  @version $Revision: 1.2 $
  + *  @version $Revision: 1.3 $
*/
   public class ExceptionAnalysis
  extends ValueAnalysis
  @@ -83,7 +83,7 @@
 String base = cls.getName();
 base = base.substring(base.lastIndexOf('.')+1);
 if (base.endsWith(Exception))
  - base = base.substring(0, base.length()-10);
  + base = base.substring(0, base.length()-9);
 base = Util.javaToIDLName(base + Ex);
   
 b.append(base).append(:1.0);
  
  
  

___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



RE: [JBoss-dev] Commiting minor changes to contrib/iiop

2001-10-30 Thread marc fleury

what do they do?
marcf

|-Original Message-
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of
|Francisco Reverbel
|Sent: Tuesday, October 30, 2001 7:19 AM
|To: [EMAIL PROTECTED]
|Subject: [JBoss-dev] Commiting minor changes to contrib/iiop
|
|
|Ole,
|
|I'm about to commit a few minor fixes to the contrib/iiop module (files
|Attribute Analysis, ContainerAnalysis, and ExceptionAnalysis in package
|org.jboss.iiop.rmi). Please let me know if you see something wrong in
|these fixes.
|
|Best regards,
|
|Francisco
|
|
|
|___
|Jboss-development mailing list
|[EMAIL PROTECTED]
|https://lists.sourceforge.net/lists/listinfo/jboss-development

___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] CVS update: contrib/iiop/src/main/org/jboss/ejb/plugins/iiop CDRStream.java

2001-10-30 Thread Francisco Reverbel

  User: reverbel
  Date: 01/10/30 06:15:24

  Modified:iiop/src/main/org/jboss/ejb/plugins/iiop CDRStream.java
  Log:
  Adding a PortableRemoteObject.narrow() call within the unmarshalling method for
  remote inferfaces (method read() of the inner class RemoteReader), to do stub
  downloading.
  
  Revision  ChangesPath
  1.3   +25 -14contrib/iiop/src/main/org/jboss/ejb/plugins/iiop/CDRStream.java
  
  Index: CDRStream.java
  ===
  RCS file: 
/cvsroot/jboss/contrib/iiop/src/main/org/jboss/ejb/plugins/iiop/CDRStream.java,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- CDRStream.java2001/08/28 22:07:53 1.2
  +++ CDRStream.java2001/10/30 14:15:24 1.3
  @@ -11,6 +11,7 @@
   import java.io.Serializable;
   import java.rmi.Remote;
   import javax.rmi.CORBA.Util;
  +import javax.rmi.PortableRemoteObject;
   import org.omg.CORBA_2_3.portable.InputStream;
   import org.omg.CORBA_2_3.portable.OutputStream;
   
  @@ -26,7 +27,7 @@
* defined by codeCDRStream/code.
*
* @author  a href=mailto:[EMAIL PROTECTED];Francisco Reverbel/a
  - * @version $Revision: 1.2 $
  + * @version $Revision: 1.3 $
*/
   public class CDRStream 
   {
  @@ -54,7 +55,7 @@
   * br
   * pre
   *java.lang.StringG (strinG)
  -*RMI/IDL remote interfaceR
  +*RMI/IDL remote interfaceR + interfaceName
   *RMI/IDL abstract interface  A
   *serializableE (sErializablE)
   *valuetype   L + className
  @@ -99,7 +100,7 @@
return G; // strinG
 }
 else if (RmiIdlUtil.isRMIIDLRemoteInterface(clz)) {
  - return R; // Remote interface
  + return R + clz.getName(); // Remote interface
 }
 else if (isAbstractInterface(clz)) {
return A; // Abstract interface
  @@ -165,7 +166,13 @@
 case 'O':
return ObjectReader.instance;
 case 'R':
  - return RemoteReader.instance;
  + try {
  +return new RemoteReader(cl.loadClass(s.substring(1)));
  + }
  + catch (ClassNotFoundException e) {
  +throw new RuntimeException(Error loading class  
  +   + s.substring(1) + :  + e);
  + }
 case 'S':
return ShortReader.instance;
 case 'V':
  @@ -268,7 +275,7 @@
return StringReader.instance;
 }
 else if (RmiIdlUtil.isRMIIDLRemoteInterface(clz)) {
  - return RemoteReader.instance;
  + return new RemoteReader(clz);
 }
 else if (isAbstractInterface(clz)) {
return AbstractInterfaceReader.instance;
  @@ -532,25 +539,30 @@
 
 public Object read(InputStream in)
 {
  - //return org.omg.CORBA.WStringValueHelper.read(in); 
  - return in.read_value(String.class);
  +  return in.read_value(String.class);
 }
  }
  
  /**
  -* Singleton class that unmarshals codejava.rmi.Remote/code objects
  -* from a CDR input stream.
  +* Class that unmarshals codejava.rmi.Remote/code objects from a CDR 
  +* input stream. A codeRemoteReader/code is specific for a given 
  +* remote interface, which is passed as a parameter to the 
  +* codeRemoteReader/code constructor.
   */
  private static final class RemoteReader
implements CDRStreamReader 
  {
  -  static final CDRStreamReader instance = new RemoteReader();
  +  private Class clz;
 
  -  private RemoteReader() { }
  +  RemoteReader(Class clz) {
  + this.clz = clz;
  +  }
 
 public Object read(InputStream in)
 {
  - return in.read_Object();
  +  // The narrow() call downloads the stub from the codebase embedded
  + // within the IOR of the unmarshalled object.
  + return PortableRemoteObject.narrow(in.read_Object(), clz);
 }
  }
   
  @@ -813,8 +825,7 @@
 
 public void write(OutputStream out, Object obj)
 {
  - //org.omg.CORBA.WStringValueHelper.write(out, (String)obj);
  - out.write_value((String)obj, String.class);
  +  out.write_value((String)obj, String.class);
 }
  }
   
  
  
  

___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



RE: [JBoss-dev] Fwd: ests on different OS'es

2001-10-30 Thread marc fleury

Sounds great actually, having the automated tests is an important thing for
the next fase of dev.  In fact even just the compile farm with Linux but
triggered when there are tag updates would be an important thing for us not
to miss obvious problems in the tests.

marcf

|-Original Message-
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of Chris
|Kimpton
|Sent: Tuesday, October 30, 2001 5:01 AM
|To: [EMAIL PROTECTED]
|Subject: [JBoss-dev] Fwd: ests on different OS'es
|
|
|Hi Peter
|
|[I sent this to the list - hope you don't mind - just to mix in any
|other ideas]
|
|There was some talk about the compile farm a few months back... and I
|tihnk it could be a way to go... We'd just need to see if we can
|automate all the work - eg cronjobs/at-jobs to automate and getting
|the stuff off the box, scp all the way to a public server.
|
|Although the biggest problem I see is that they have no Windoze
|servers - which I think is where we need regular testing.
|
|I think the tinderbox ( http://mozilla.org/projects/tinderbox/ ) (or
|similar) route seems the way to go - that is, a central server for
|results and then various servers for generating/submitting results.
|It provides lots of info on when builds break and can highlight the
|code that causes the break - from what I've read   ;-)
|
|This should allow practically anyone to use their dev pc as a test
|machine - after you run the tests, you can submit the results to the
|central server (although I maybe asking too much from tinderbox
|here...)
|
|This is what I want to look at next.
|
|Chris
|
|--- Peter Fagerlund [EMAIL PROTECTED] wrote:
| Date: Mon, 29 Oct 2001 18:37:01 +0100
| Subject: ests on different OS'es
| From: Peter Fagerlund [EMAIL PROTECTED]
| To: Chris Kimpton [EMAIL PROTECTED]
|
| Chris,
|
| have You seen Guide to the SourceForge.net Compile Farm
| http://sourceforge.net/docman/display_doc.php?docid=762group_id=1
|
| Could We use that ? ... to also test on other plattforms and have
| an ant
| task auto uppload the results for presentation ??? ...
|
| What do u think ? ...
|
| /peter_f
|
|
|
|=
|Need somewhere to Live in London? - Then go to http://freeflats.com
|
|__
|Do You Yahoo!?
|Make a great connection at Yahoo! Personals.
|http://personals.yahoo.com
|
|___
|Jboss-development mailing list
|[EMAIL PROTECTED]
|https://lists.sourceforge.net/lists/listinfo/jboss-development


___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



RE: [JBoss-dev] Commiting minor changes to contrib/iiop

2001-10-30 Thread Francisco Reverbel

Hi,

On Tue, 30 Oct 2001, marc fleury wrote:

 what do they do?
 marcf

Just minor bug fixes. They should fix:

 - a silly problem with attribute names (The first character of an
   attribute name should be converted to lowercase unless both the first
   and the second characters are upper case. I mean, FooAttr becomes
   fooAttr, but FOOAttr remains FOOAttr.)

 - a bug in the mangling of overloaded operation names (argument types
   should be separated by double underscores)

 - an ArrayIndexOutOfBoundsException in ContainerAnalysis (within
   analyzeMethods()) caused by a misplaced initialization of array of
   indices.

 - a couple of typos in arguments to substring() calls.

The log messages are: 

  Modified:iiop/src/main/org/jboss/iiop/rmi AttributeAnalysis.java
  Log:
  Converting to lower case the first character of an attribute name
  unless both the first and second characters are upper case.

  Modified:iiop/src/main/org/jboss/iiop/rmi ContainerAnalysis.java
  Log:
  Fixing minor bugs in toHexString() (a typo), analyzeMethods() (misplaced
  initialization of the mutators array), and
  fixupOverloadedOperationNames() (argument types are now separated by
  double underscores). 
  
  Modified:iiop/src/main/org/jboss/iiop/rmi ExceptionAnalysis.java
  Log:
  Fixing a typo in the doAnalyze() method.

Best regards,

Francisco  

 
 |-Original Message-
 |From: [EMAIL PROTECTED]
 |[mailto:[EMAIL PROTECTED]]On Behalf Of
 |Francisco Reverbel
 |Sent: Tuesday, October 30, 2001 7:19 AM
 |To: [EMAIL PROTECTED]
 |Subject: [JBoss-dev] Commiting minor changes to contrib/iiop
 |
 |
 |Ole,
 |
 |I'm about to commit a few minor fixes to the contrib/iiop module (files
 |Attribute Analysis, ContainerAnalysis, and ExceptionAnalysis in package
 |org.jboss.iiop.rmi). Please let me know if you see something wrong in
 |these fixes.
 |
 |Best regards,
 |
 |Francisco
 |
 |
 |
 |___
 |Jboss-development mailing list
 |[EMAIL PROTECTED]
 |https://lists.sourceforge.net/lists/listinfo/jboss-development
 


___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



RE: [JBoss-dev] Fwd: ests on different OS'es

2001-10-30 Thread Julian Gosnell

I looked at Tinderbox a while ago and decided I could
do better in Java.

I started cobbling together something with SOAP
services and JBoss - J[ava] D[istributed] B[uild]
S[ystem].

Something like this.

You tell a Slave where it's master is.

The Slave starts up and registers it's availability
with the Master.

The Master may make requests to a Slave containing ant
buildfiles. (these can contain ftp, unzip, cvs etc
commands) and targets.

The Slave returns a log and a status.

The Master watches an e.g. CVS repository and
schedules builds on Slaves of various architectures.

The Master is even able to upgrade the development
platform on a Slave by sending it a buildfile which
does this.

The Master remembers the architecture and components
available on each Slave.

The Master can produce nice reports, like Tinderbox,
showing the state of various builds at various times.

.

Tinderbox is a mish-mash of scripts. Each node in the
cluster needs to be individually configured...

JDBS is much more dynamic and would make a nice base
for a compile farm for someone like SourceForge. You
just run up a Slave at night and contribute your
processor to the farm.

I had plans to get it going and persuade JBoss to run
it up somewhere. Plans are easy, but there is never
enough time.

If anyone is really keen, I could mail you the
source. ( I never wrote the buildfiles, scheduler
or reporting).

I was going to mention it to Chris but


Jules



 --- marc fleury [EMAIL PROTECTED] wrote: 
Sounds great actually, having the automated tests is
 an important thing for
 the next fase of dev.  In fact even just the compile
 farm with Linux but
 triggered when there are tag updates would be an
 important thing for us not
 to miss obvious problems in the tests.
 
 marcf
 
 |-Original Message-
 |From: [EMAIL PROTECTED]

|[mailto:[EMAIL PROTECTED]]On
 Behalf Of Chris
 |Kimpton
 |Sent: Tuesday, October 30, 2001 5:01 AM
 |To: [EMAIL PROTECTED]
 |Subject: [JBoss-dev] Fwd: ests on different OS'es
 |
 |
 |Hi Peter
 |
 |[I sent this to the list - hope you don't mind -
 just to mix in any
 |other ideas]
 |
 |There was some talk about the compile farm a few
 months back... and I
 |tihnk it could be a way to go... We'd just need to
 see if we can
 |automate all the work - eg cronjobs/at-jobs to
 automate and getting
 |the stuff off the box, scp all the way to a public
 server.
 |
 |Although the biggest problem I see is that they
 have no Windoze
 |servers - which I think is where we need regular
 testing.
 |
 |I think the tinderbox (
 http://mozilla.org/projects/tinderbox/ ) (or
 |similar) route seems the way to go - that is, a
 central server for
 |results and then various servers for
 generating/submitting results.
 |It provides lots of info on when builds break and
 can highlight the
 |code that causes the break - from what I've
 read   ;-)
 |
 |This should allow practically anyone to use their
 dev pc as a test
 |machine - after you run the tests, you can submit
 the results to the
 |central server (although I maybe asking too much
 from tinderbox
 |here...)
 |
 |This is what I want to look at next.
 |
 |Chris
 |
 |--- Peter Fagerlund [EMAIL PROTECTED] wrote:
 | Date: Mon, 29 Oct 2001 18:37:01 +0100
 | Subject: ests on different OS'es
 | From: Peter Fagerlund [EMAIL PROTECTED]
 | To: Chris Kimpton [EMAIL PROTECTED]
 |
 | Chris,
 |
 | have You seen Guide to the SourceForge.net
 Compile Farm
 |

http://sourceforge.net/docman/display_doc.php?docid=762group_id=1
 |
 | Could We use that ? ... to also test on other
 plattforms and have
 | an ant
 | task auto uppload the results for presentation
 ??? ...
 |
 | What do u think ? ...
 |
 | /peter_f
 |
 |
 |
 |=
 |Need somewhere to Live in London? - Then go to
 http://freeflats.com
 |
 |__
 |Do You Yahoo!?
 |Make a great connection at Yahoo! Personals.
 |http://personals.yahoo.com
 |
 |___
 |Jboss-development mailing list
 |[EMAIL PROTECTED]

|https://lists.sourceforge.net/lists/listinfo/jboss-development
 
 
 ___
 Jboss-development mailing list
 [EMAIL PROTECTED]

https://lists.sourceforge.net/lists/listinfo/jboss-development 


Nokia Game is on again. 
Go to http://uk.yahoo.com/nokiagame/ and join the new
all media adventure before November 3rd.

___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



RE: [JBoss-dev] Fwd: ests on different OS'es

2001-10-30 Thread marc fleury


then what are  you waiting for julian? you did this whole thing in your
corner?

why?

put it out already gad damn it

marcf
|-Original Message-
|From: Julian Gosnell [mailto:[EMAIL PROTECTED]]
|Sent: Tuesday, October 30, 2001 11:53 AM
|To: marc fleury; Chris Kimpton; [EMAIL PROTECTED]
|Subject: RE: [JBoss-dev] Fwd: ests on different OS'es
|
|
|I looked at Tinderbox a while ago and decided I could
|do better in Java.
|
|I started cobbling together something with SOAP
|services and JBoss - J[ava] D[istributed] B[uild]
|S[ystem].
|
|Something like this.
|
|You tell a Slave where it's master is.
|
|The Slave starts up and registers it's availability
|with the Master.
|
|The Master may make requests to a Slave containing ant
|buildfiles. (these can contain ftp, unzip, cvs etc
|commands) and targets.
|
|The Slave returns a log and a status.
|
|The Master watches an e.g. CVS repository and
|schedules builds on Slaves of various architectures.
|
|The Master is even able to upgrade the development
|platform on a Slave by sending it a buildfile which
|does this.
|
|The Master remembers the architecture and components
|available on each Slave.
|
|The Master can produce nice reports, like Tinderbox,
|showing the state of various builds at various times.
|
|.
|
|Tinderbox is a mish-mash of scripts. Each node in the
|cluster needs to be individually configured...
|
|JDBS is much more dynamic and would make a nice base
|for a compile farm for someone like SourceForge. You
|just run up a Slave at night and contribute your
|processor to the farm.
|
|I had plans to get it going and persuade JBoss to run
|it up somewhere. Plans are easy, but there is never
|enough time.
|
|If anyone is really keen, I could mail you the
|source. ( I never wrote the buildfiles, scheduler
|or reporting).
|
|I was going to mention it to Chris but
|
|
|Jules
|
|
|
| --- marc fleury [EMAIL PROTECTED] wrote: 
|Sounds great actually, having the automated tests is
| an important thing for
| the next fase of dev.  In fact even just the compile
| farm with Linux but
| triggered when there are tag updates would be an
| important thing for us not
| to miss obvious problems in the tests.
|
| marcf
|
| |-Original Message-
| |From: [EMAIL PROTECTED]
|
||[mailto:[EMAIL PROTECTED]]On
| Behalf Of Chris
| |Kimpton
| |Sent: Tuesday, October 30, 2001 5:01 AM
| |To: [EMAIL PROTECTED]
| |Subject: [JBoss-dev] Fwd: ests on different OS'es
| |
| |
| |Hi Peter
| |
| |[I sent this to the list - hope you don't mind -
| just to mix in any
| |other ideas]
| |
| |There was some talk about the compile farm a few
| months back... and I
| |tihnk it could be a way to go... We'd just need to
| see if we can
| |automate all the work - eg cronjobs/at-jobs to
| automate and getting
| |the stuff off the box, scp all the way to a public
| server.
| |
| |Although the biggest problem I see is that they
| have no Windoze
| |servers - which I think is where we need regular
| testing.
| |
| |I think the tinderbox (
| http://mozilla.org/projects/tinderbox/ ) (or
| |similar) route seems the way to go - that is, a
| central server for
| |results and then various servers for
| generating/submitting results.
| |It provides lots of info on when builds break and
| can highlight the
| |code that causes the break - from what I've
| read   ;-)
| |
| |This should allow practically anyone to use their
| dev pc as a test
| |machine - after you run the tests, you can submit
| the results to the
| |central server (although I maybe asking too much
| from tinderbox
| |here...)
| |
| |This is what I want to look at next.
| |
| |Chris
| |
| |--- Peter Fagerlund [EMAIL PROTECTED] wrote:
| | Date: Mon, 29 Oct 2001 18:37:01 +0100
| | Subject: ests on different OS'es
| | From: Peter Fagerlund [EMAIL PROTECTED]
| | To: Chris Kimpton [EMAIL PROTECTED]
| |
| | Chris,
| |
| | have You seen Guide to the SourceForge.net
| Compile Farm
| |
|
|http://sourceforge.net/docman/display_doc.php?docid=762group_id=1
| |
| | Could We use that ? ... to also test on other
| plattforms and have
| | an ant
| | task auto uppload the results for presentation
| ??? ...
| |
| | What do u think ? ...
| |
| | /peter_f
| |
| |
| |
| |=
| |Need somewhere to Live in London? - Then go to
| http://freeflats.com
| |
| |__
| |Do You Yahoo!?
| |Make a great connection at Yahoo! Personals.
| |http://personals.yahoo.com
| |
| |___
| |Jboss-development mailing list
| |[EMAIL PROTECTED]
|
||https://lists.sourceforge.net/lists/listinfo/jboss-development
|
|
| ___
| Jboss-development mailing list
| [EMAIL PROTECTED]
|
|https://lists.sourceforge.net/lists/listinfo/jboss-development
|
|
|Nokia Game is on again.
|Go to http://uk.yahoo.com/nokiagame/ and join the new
|all media adventure before November 3rd.



Re: [JBoss-dev] Fwd: ests on different OS'es

2001-10-30 Thread Peter Fagerlund

Check it in ( as a proj? - Scott ?) - I myself (robot) need repair -- but
will with Chris 'es  direction, try to, take Us, soweherere close to desiree
! ... I really got a surge bu.m..p...e when Julian told Us how ...

Avanti

/peter_f

PS : ests should read as Tests : DS (T = now = yes;)

on 1-10-30 18.41, marc fleury at [EMAIL PROTECTED] wrote:

 
 then what are  you waiting for julian? you did this whole thing in your
 corner?
 
 why?
 
 put it out already gad damn it
 
 marcf
 |-Original Message-
 |From: Julian Gosnell [mailto:[EMAIL PROTECTED]]
 |Sent: Tuesday, October 30, 2001 11:53 AM
 |To: marc fleury; Chris Kimpton; [EMAIL PROTECTED]
 |Subject: RE: [JBoss-dev] Fwd: ests on different OS'es
 |
 |
 |I looked at Tinderbox a while ago and decided I could
 |do better in Java.
 |
 |I started cobbling together something with SOAP
 |services and JBoss - J[ava] D[istributed] B[uild]
 |S[ystem].
 |
 |Something like this.
 |
 |You tell a Slave where it's master is.
 |
 |The Slave starts up and registers it's availability
 |with the Master.
 |
 |The Master may make requests to a Slave containing ant
 |buildfiles. (these can contain ftp, unzip, cvs etc
 |commands) and targets.
 |
 |The Slave returns a log and a status.
 |
 |The Master watches an e.g. CVS repository and
 |schedules builds on Slaves of various architectures.
 |
 |The Master is even able to upgrade the development
 |platform on a Slave by sending it a buildfile which
 |does this.
 |
 |The Master remembers the architecture and components
 |available on each Slave.
 |
 |The Master can produce nice reports, like Tinderbox,
 |showing the state of various builds at various times.
 |
 |.
 |
 |Tinderbox is a mish-mash of scripts. Each node in the
 |cluster needs to be individually configured...
 |
 |JDBS is much more dynamic and would make a nice base
 |for a compile farm for someone like SourceForge. You
 |just run up a Slave at night and contribute your
 |processor to the farm.
 |
 |I had plans to get it going and persuade JBoss to run
 |it up somewhere. Plans are easy, but there is never
 |enough time.
 |
 |If anyone is really keen, I could mail you the
 |source. ( I never wrote the buildfiles, scheduler
 |or reporting).
 |
 |I was going to mention it to Chris but
 |
 |
 |Jules
 |
 |
 |
 | --- marc fleury [EMAIL PROTECTED] wrote: 
 |Sounds great actually, having the automated tests is
 | an important thing for
 | the next fase of dev.  In fact even just the compile
 | farm with Linux but
 | triggered when there are tag updates would be an
 | important thing for us not
 | to miss obvious problems in the tests.
 |
 | marcf
 |
 | |-Original Message-
 | |From: [EMAIL PROTECTED]
 |
 ||[mailto:[EMAIL PROTECTED]]On
 | Behalf Of Chris
 | |Kimpton
 | |Sent: Tuesday, October 30, 2001 5:01 AM
 | |To: [EMAIL PROTECTED]
 | |Subject: [JBoss-dev] Fwd: ests on different OS'es
 | |
 | |
 | |Hi Peter
 | |
 | |[I sent this to the list - hope you don't mind -
 | just to mix in any
 | |other ideas]
 | |
 | |There was some talk about the compile farm a few
 | months back... and I
 | |tihnk it could be a way to go... We'd just need to
 | see if we can
 | |automate all the work - eg cronjobs/at-jobs to
 | automate and getting
 | |the stuff off the box, scp all the way to a public
 | server.
 | |
 | |Although the biggest problem I see is that they
 | have no Windoze
 | |servers - which I think is where we need regular
 | testing.
 | |
 | |I think the tinderbox (
 | http://mozilla.org/projects/tinderbox/ ) (or
 | |similar) route seems the way to go - that is, a
 | central server for
 | |results and then various servers for
 | generating/submitting results.
 | |It provides lots of info on when builds break and
 | can highlight the
 | |code that causes the break - from what I've
 | read   ;-)
 | |
 | |This should allow practically anyone to use their
 | dev pc as a test
 | |machine - after you run the tests, you can submit
 | the results to the
 | |central server (although I maybe asking too much
 | from tinderbox
 | |here...)
 | |
 | |This is what I want to look at next.
 | |
 | |Chris
 | |
 | |--- Peter Fagerlund [EMAIL PROTECTED] wrote:
 | | Date: Mon, 29 Oct 2001 18:37:01 +0100
 | | Subject: ests on different OS'es
 | | From: Peter Fagerlund [EMAIL PROTECTED]
 | | To: Chris Kimpton [EMAIL PROTECTED]
 | |
 | | Chris,
 | |
 | | have You seen Guide to the SourceForge.net
 | Compile Farm
 | |
 |
 |http://sourceforge.net/docman/display_doc.php?docid=762group_id=1
 | |
 | | Could We use that ? ... to also test on other
 | plattforms and have
 | | an ant
 | | task auto uppload the results for presentation
 | ??? ...
 | |
 | | What do u think ? ...
 | |
 | | /peter_f
 | |
 | |
 | |
 | |=
 | |Need somewhere to Live in London? - Then go to
 | http://freeflats.com
 | |
 | |__
 | |Do You Yahoo!?
 | |Make a great connection at Yahoo! Personals.
 | |http://personals.yahoo.com
 | |
 | 

[JBoss-dev] CVS update: thirdparty/exolab/tyrex/lib tyrex.jar

2001-10-30 Thread Scott M Stark

  User: starksm 
  Date: 01/10/30 17:01:31

  Modified:exolab/tyrex/lib tyrex.jar
  Log:
  Update to the tyrex-0.9.8.5 jar
  
  Revision  ChangesPath
  1.2   +791 -1147 thirdparty/exolab/tyrex/lib/tyrex.jar
  
Binary file
  
  

___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] CVS update: thirdparty/gnu/regexp/lib gnu-regexp.jar

2001-10-30 Thread Scott M Stark

  User: starksm 
  Date: 01/10/30 17:02:11

  Modified:gnu/regexp/lib gnu-regexp.jar
  Log:
  Update to the gnu.regexp-1.1.4 jar
  
  Revision  ChangesPath
  1.2   +113 -73   thirdparty/gnu/regexp/lib/gnu-regexp.jar
  
Binary file
  
  

___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] CVS update: thirdparty/sun/jaxp/lib xalan.jar

2001-10-30 Thread Scott M Stark

  User: starksm 
  Date: 01/10/30 17:04:23

  Modified:sun/jaxp/lib xalan.jar
  Log:
  Update to the xalan-j_2_2_D11 jar
  
  Revision  ChangesPath
  1.2   +3403 -3099thirdparty/sun/jaxp/lib/xalan.jar
  
Binary file
  
  

___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



RE: [JBoss-dev] Automated JBoss Testsuite Results

2001-10-30 Thread marc fleury


OK let's make this work bit by bit

|Number of tests run:   130
|
|
|
|Successful tests:  121
|
|Errors:4
|
|Failures:  5
|
|
|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 easy, just run the
|target 'run-basic-testsuite' from the main build.xml.

yeah IS THERE A WAY TO RUN THIS WITHOUT THE BUILD (man...)

I *just* want to run the freaking testbean stuff just to make sure the JMX
detaching doesn't break the functionality and right now I am getting an
headache just looking at the build xml files from Jason :(

|PPS Come on people - there were a few days back in July 2001 when
|we had ZERO tests failing!

Yeah we will get back there eventually, will take some effort.

marcf


___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] CVS update: jbossmq/src/main/org/jboss/mq/server MessageCache.java

2001-10-30 Thread Scott M Stark

  User: starksm 
  Date: 01/10/30 17:51:10

  Modified:src/main/org/jboss/mq/server MessageCache.java
  Log:
  Use the ServiceMBeanSupport.log to for logging and change the
  debug msgs to trace to avoid the excessive logging to server.log
  
  Revision  ChangesPath
  1.3   +173 -133  jbossmq/src/main/org/jboss/mq/server/MessageCache.java
  
  Index: MessageCache.java
  ===
  RCS file: /cvsroot/jboss/jbossmq/src/main/org/jboss/mq/server/MessageCache.java,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- MessageCache.java 2001/10/28 04:07:36 1.2
  +++ MessageCache.java 2001/10/31 01:51:10 1.3
  @@ -23,342 +23,380 @@
* later.
*
* @author a href=mailto:[EMAIL PROTECTED];Hiram Chirino/a
  - * @version$Revision: 1.2 $
  + * @version$Revision: 1.3 $
*/
  -public class MessageCache extends ServiceMBeanSupport implements MessageCacheMBean, 
MBeanRegistration, Runnable {
  -
  -   org.apache.log4j.Category cat = 
org.apache.log4j.Category.getInstance(MessageCache.class);
  -
  +public class MessageCache extends ServiceMBeanSupport implements MessageCacheMBean, 
MBeanRegistration, Runnable
  +{
  // The cached messages are orded in a LRU linked list
  private LinkedList lruCache = new LinkedList();
  -
  -   // Provides a Unique ID to MessageHanles 
  +   
  +   // Provides a Unique ID to MessageHanles
  private long messageCounter = 0;
  int cacheHits = 0;
  int cacheMisses = 0;
  -
  +   
  private File dataFile;
  private String dataDirectory;
  private Thread referenceSoftner;
  -
  +   
  private long highMemoryMark = 1024L * 1000 * 16;
  private long maxMemoryMark = 1024L * 1000 * 32;
  public static final long ONE_MEGABYTE = 1024L * 1000;
  -
  +   
  int softRefCacheSize = 0;
  int totalCacheSize = 0;
  -
  +   
  // Used to get notified when message are being deleted by GC
  ReferenceQueue referenceQueue = new ReferenceQueue();
  -
  +   
  /**
   * Adds a message to the cache
   */
  -   public MessageReference add(SpyMessage message) throws javax.jms.JMSException {
  -  cat.debug(add lock aquire);
  -  synchronized (this) {
  +   public MessageReference add(SpyMessage message) throws javax.jms.JMSException
  +   {
  +  log.trace(add lock aquire);
  +  synchronized (this)
  +  {
MessageReference mh = new MessageReference(this, new 
Long(messageCounter++), message);
lruCache.addLast(mh);
totalCacheSize++;
validateSoftReferenceDepth();
  -
  - cat.debug(add lock release);
  + 
  + log.trace(add lock release);
return mh;
 }
  }
  -
  +   
  /**
   * removes a message from the cache
   */
  -   public void remove(MessageReference mr) throws JMSException {
  -  cat.debug(remove lock aquire);
  -  synchronized (this) {
  +   public void remove(MessageReference mr) throws JMSException
  +   {
  +  log.trace(remove lock aquire);
  +  synchronized (this)
  +  {
mr.clear();
lruCache.remove(mr);
totalCacheSize--;
  - cat.debug(remove lock release);
  + log.trace(remove lock release);
 }
  }
  -
  +   
  /**
   * The strategy is that we keep the most recently used messages as
  -* Hard references.  Then we make the older ones soft references.  Making 
  +* Hard references.  Then we make the older ones soft references.  Making
   * something a soft reference stores it to disk so we need to avoid making
   * soft references if we can avoid it.  But once it is made a soft reference does
   * not mean that it is removed from memory.  Depending on how agressive the JVM's
   * GC is, it may stay around long enough for it to be used by a client doing a 
read,
   * saving us read from the file system.  If memory gets tight the GC will remove
  -* the soft references.  What we want to do is make sure there are at least some 
  +* the soft references.  What we want to do is make sure there are at least some
   * soft references available so that the GC can reclaim memory.
   * @see Runnable#run()
   */
  -   public void run() {
  -  try {
  - while (true) {
  -cat.debug(Waiting for a reference to get GCed.);
  +   public void run()
  +   {
  +  try
  +  {
  + while (true)
  + {
  +log.trace(Waiting for a reference to get GCed.);
   // Get the next soft reference that was canned by the GC
  -
  +
   Reference r = referenceQueue.remove(1000);
  -if (r != null) {
  +if (r != null)
  +{
  softRefCacheSize--;
  // the GC will free a set of messages together, so we poll them
  // all 

Re: [JBoss-dev] Automated JBoss Testsuite Results

2001-10-30 Thread David Jencks

In the testsuite directory, 
./build.sh tests-unit

The build scripts aren't quite as complicated as they look at first ;-)

david jencks

On 2001.10.30 20:48:49 -0500 marc fleury wrote:
 
 OK let's make this work bit by bit
 
 |Number of tests run:   130
 |
 |
 |
 |Successful tests:  121
 |
 |Errors:4
 |
 |Failures:  5
 |
 |
 |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 easy, just run the
 |target 'run-basic-testsuite' from the main build.xml.
 
 yeah IS THERE A WAY TO RUN THIS WITHOUT THE BUILD (man...)
 
 I *just* want to run the freaking testbean stuff just to make sure the
 JMX
 detaching doesn't break the functionality and right now I am getting an
 headache just looking at the build xml files from Jason :(
 
 |PPS Come on people - there were a few days back in July 2001 when
 |we had ZERO tests failing!
 
 Yeah we will get back there eventually, will take some effort.
 
 marcf
 
 
 ___
 Jboss-development mailing list
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/jboss-development
 
 

___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] CVS update: jboss/src/main/org/jboss/ejb/plugins/lock QueuedPessimisticEJBLock.java

2001-10-30 Thread marc fleury

  User: mnf999  
  Date: 01/10/30 18:37:56

  Modified:src/main/org/jboss/ejb/plugins/lock
QueuedPessimisticEJBLock.java
  Log:
  Some Fixmes in the code, we are in a serious need of a cleanup imho...
  
  this code is starting to look green around the edge, a serious sign of decay
  
  Revision  ChangesPath
  1.5   +4 -1  
jboss/src/main/org/jboss/ejb/plugins/lock/QueuedPessimisticEJBLock.java
  
  Index: QueuedPessimisticEJBLock.java
  ===
  RCS file: 
/cvsroot/jboss/jboss/src/main/org/jboss/ejb/plugins/lock/QueuedPessimisticEJBLock.java,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- QueuedPessimisticEJBLock.java 2001/09/11 18:35:01 1.4
  +++ QueuedPessimisticEJBLock.java 2001/10/31 02:37:56 1.5
  @@ -38,10 +38,13 @@
* When the reference count goes to 0, the lock is released from the
* id - lock mapping.
*
  + * FIXME marcf: we should get solid numbers on this locking, bench in multi-thread 
environments
  + * We need someone with serious SUN hardware to run this lock into the ground
  + *
* @author a href=[EMAIL PROTECTED]Marc Fleury/a
* @author a href=[EMAIL PROTECTED]Bill Burke/a
*
  - * @version $Revision: 1.4 $
  + * @version $Revision: 1.5 $
*
* pbRevisions:/bbr
* pb2001/08/03: billb/b
  
  
  

___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] CVS update: jboss/src/main/org/jboss/ejb ContainerFactory.java

2001-10-30 Thread marc fleury

  User: mnf999  
  Date: 01/10/30 18:37:55

  Modified:src/main/org/jboss/ejb ContainerFactory.java
  Log:
  Some Fixmes in the code, we are in a serious need of a cleanup imho...
  
  this code is starting to look green around the edge, a serious sign of decay
  
  Revision  ChangesPath
  1.95  +8 -1  jboss/src/main/org/jboss/ejb/ContainerFactory.java
  
  Index: ContainerFactory.java
  ===
  RCS file: /cvsroot/jboss/jboss/src/main/org/jboss/ejb/ContainerFactory.java,v
  retrieving revision 1.94
  retrieving revision 1.95
  diff -u -r1.94 -r1.95
  --- ContainerFactory.java 2001/09/15 00:18:40 1.94
  +++ ContainerFactory.java 2001/10/31 02:37:55 1.95
  @@ -68,7 +68,7 @@
   * @author a href=mailto:[EMAIL PROTECTED];Peter Antman/a.
   * @author a href=mailto:[EMAIL PROTECTED];Scott Stark/a
   * @author a href=mailto:[EMAIL PROTECTED];Sacha Labourey/a
  -* @version $Revision: 1.94 $
  +* @version $Revision: 1.95 $
   */
   public class ContainerFactory
  extends ServiceMBeanSupport
  @@ -424,6 +424,8 @@
 // this one dont has the contextclassloader as parent
 // in case of the contextclassloader has a ejb package in its
 // classpath the metadata of this package would be used.
  +  // marcf: fine, just make sure that the rest of the code doesn't use this 
localCL for classes
  +  // otherwise you are going to get runtime classcasts.
 ClassLoader localCl = new URLClassLoader( new URL[]{ url } );
 efm.setClassLoader( localCl );
   
  @@ -793,6 +795,10 @@
   * add the indicated interceptors to the container depending on the container
   * transcation type and metricsEnabled flag.
   *
  +* FIXME marcf: frankly the transaction type stuff makes no sense to me, we have 
externalized
  +* the container stack construction in jbossxml and I don't see why or why there 
would be a 
  +* type missmatch on the transaction
  +* 
   * @param container   the container instance to setup.
   * @param transType   one of the BMT, CMT or ANY constants.
   * @param element the container-interceptors element from the
  @@ -816,6 +822,7 @@
/* Check that the interceptor is configured for the transaction mode of 
the bean
   by comparing its 'transaction' attribute to the string representation
   of transType
  +FIXME: marcf, WHY???
*/
String transAttr = ielement.getAttribute(transaction);
if( transAttr == null || transAttr.length() == 0 )
  
  
  

___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] CVS update: jboss/src/main/org/jboss/system URLClassLoader.java

2001-10-30 Thread Scott M Stark

  User: starksm 
  Date: 01/10/30 19:09:37

  Modified:src/main/org/jboss/system URLClassLoader.java
  Log:
  Add the URLs to the toString() format
  
  Revision  ChangesPath
  1.6   +52 -25jboss/src/main/org/jboss/system/URLClassLoader.java
  
  Index: URLClassLoader.java
  ===
  RCS file: /cvsroot/jboss/jboss/src/main/org/jboss/system/URLClassLoader.java,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -r1.5 -r1.6
  --- URLClassLoader.java   2001/10/09 19:36:57 1.5
  +++ URLClassLoader.java   2001/10/31 03:09:37 1.6
  @@ -30,7 +30,7 @@
*
* @author a href=[EMAIL PROTECTED]Marc Fleury/a
* @author a href=[EMAIL PROTECTED]Christoph G. Jung/a
  - * @version $Revision: 1.5 $
  + * @version $Revision: 1.6 $
* 
* pb20010830 marc fleury:/b
* ul
  @@ -64,18 +64,22 @@
* @param String application
* @param ClassLoader parent
*/
  -/*public URLClassLoader( String pUrl )
  +   /*public URLClassLoader( String pUrl )
  {
 super( new URL[] {} );
  -  try {
  +  try
  +  {
URL lUrl = new URL( pUrl );
addURL( lUrl );
this.keyUrl = lUrl;
 }
  -  catch( Exception e ) {
  +  catch( Exception e )
  +  {
System.out.println([GPA] WARNING: URL +keyUrl+ is not valid);
 }
  -  try {
  +
  +  try
  +  {

//url.openStream();

  @@ -90,26 +94,25 @@
 { 
System.out.println([GPA] WARNING: URL +keyUrl+ could not be opened);
 }
  -  }*/
  - 
  +   }*/
  +
  /**
   * One url per SCL
   *
   * @param String application
   * @param ClassLoader parent
   */
  - 
  public URLClassLoader(URL[] urls, URL keyUrl)
  {
  - 
 super(urls);
  - 
 this.keyUrl = keyUrl;
  - 
  -  try {
  +
  +  try
  +  {
 //url.openStream();

  - if (libraries == null) {
  + if (libraries == null)
  + {
   libraries = ServiceLibraries.getLibraries();
}

  @@ -123,12 +126,14 @@
// be queried
libraries.addClassLoader(this);
 }
  -  catch(Exception e) { 
  +  catch(Exception e)
  +  { 
System.out.println([GPA] WARNING: URL +keyUrl+ could not be opened);
 }
  }
   
  -   public URL getKeyURL() {
  +   public URL getKeyURL()
  +   {
 return keyUrl;
  }

  @@ -163,36 +168,47 @@
 return super.loadClass(name, resolve);
  }

  -   public URL getResource(String name) {
  -  if (name.endsWith(CHANGEME)) {
  +   public URL getResource(String name)
  +   {
  +  if (name.endsWith(CHANGEME))
  +  {
System.out.println(UCL GETRESOURCE +name+  in UCL  +
   this.hashCode());
 }
 
 URL resource = super.getResource(name);

  -  if (resource == null) {
  +  if (resource == null)
  +  {
resource = libraries.getResource(name, this);
 }

  -  if (resource == null) {
  +  if (resource == null)
  +  {
System.out.println(Did not find the UCL resource +name);
 }
 return resource;
  }

  -   public URL getResourceLocally(String name) {
  +   public URL getResourceLocally(String name)
  +   {
 return super.getResource(name);
  }

  -   public InputStream getResourceAsStream(String name) {
  -  try {
  +   public InputStream getResourceAsStream(String name)
  +   {
  +  try
  +  {
URL resourceUrl = getResource(name);

  - if (resourceUrl != null) {
  + if (resourceUrl != null)
  + {
   return resourceUrl.openStream();
}
  -  } catch (Exception ignore) {}
  +  }
  +  catch (Exception ignore)
  +  {
  +  }
 
 return null;
  }
  @@ -213,6 +229,17 @@
   
  public String toString()
  {
  -  return JBoss URLClassloader: keyURL :  + getKeyURL() + , URLS:  + 
getURLs();
  +  StringBuffer tmp = new StringBuffer(JBoss URLClassloader: keyURL : );
  +  tmp.append(getKeyURL());
  +  tmp.append(, URLS: );
  +  URL[] urls = getURLs();
  +  tmp.append('[');
  +  for(int u = 0; u  urls.length; u ++)
  +  {
  + tmp.append(urls[u]);
  + tmp.append(',');
  +  }
  +  tmp.append(']');
  +  return tmp.toString();
  }
   }
  
  
  

___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] Automated JBoss Testsuite Results

2001-10-30 Thread chris



JBoss daily test results

SUMMARY

Number of tests run:   140



Successful tests:  129

Errors:5

Failures:  6





[time of test: 31 October 2001 3:18 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-6]

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.

It is assumed that whoever makes change(s) to jboss that 
break the test will be fixing the test or jboss, as appropriate!





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 easy, just run the target 
'run-basic-testsuite' from the main build.xml.

PPS Come on people - there were a few days back in July 2001 when we had ZERO tests 
failing!

Oh, and thanks - remember we love you too!



___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] Automated JBoss Testsuite Results

2001-10-30 Thread chris



JBoss daily test results

SUMMARY

Number of tests run:   140



Successful tests:  131

Errors:4

Failures:  5





[time of test: 31 October 2001 4:8 GMT]
[java.version: 1.3.1]
[java.vendor: Blackdown Java-Linux Team]
[java.vm.version: Blackdown-1.3.1-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-6]

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.

It is assumed that whoever makes change(s) to jboss that 
break the test will be fixing the test or jboss, as appropriate!





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 easy, just run the target 
'run-basic-testsuite' from the main build.xml.

PPS Come on people - there were a few days back in July 2001 when we had ZERO tests 
failing!

Oh, and thanks - remember we love you too!



___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] Automated JBoss Testsuite Results

2001-10-30 Thread chris



JBoss daily test results

SUMMARY

Number of tests run:   130



Successful tests:  121

Errors:4

Failures:  5





[time of test: 31 October 2001 5:28 GMT]
[java.version: 1.3.1]
[java.vendor: Blackdown Java-Linux Team]
[java.vm.version: Blackdown-1.3.1-FCS]
[java.vm.name: Classic VM]
[java.vm.info: green threads, nojit]
[os.name: Linux]
[os.arch: i386]
[os.version: 2.4.9-6]

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.

It is assumed that whoever makes change(s) to jboss that 
break the test will be fixing the test or jboss, as appropriate!





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 easy, just run the target 
'run-basic-testsuite' from the main build.xml.

PPS Come on people - there were a few days back in July 2001 when we had ZERO tests 
failing!

Oh, and thanks - remember we love you too!



___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] CVS update: contrib/varia/src/resources - New directory

2001-10-30 Thread Scott M Stark

  User: starksm 
  Date: 01/10/30 21:40:26

  contrib/varia/src/resources - New directory

___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] CVS update: contrib/varia/src/resources/boot - New directory

2001-10-30 Thread Scott M Stark

  User: starksm 
  Date: 01/10/30 21:40:33

  contrib/varia/src/resources/boot - New directory

___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] CVS update: contrib/varia/src/main/org/jboss/boot/servlets - New directory

2001-10-30 Thread Scott M Stark

  User: starksm 
  Date: 01/10/30 21:42:57

  contrib/varia/src/main/org/jboss/boot/servlets - New directory

___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development