date:20020323

[JBoss-dev] [ jboss-Bugs-532734 ] Ineffective SQL-code generated

2002-03-23 Thread noreply


Bugs item #532734, was opened at 2002-03-20 22:17
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detailatid=376685aid=532734group_id=22866

Category: JBossCMP
Group: v3.0 Rabbit Hole
Status: Open
Resolution: None
Priority: 5
Submitted By: Marius Kotsbak (mkotsbak)
Assigned to: Dain Sundstrom (dsundstrom)
Summary: Ineffective SQL-code generated

Initial Comment:
I found this in the log. It seems like it is generating
ineffective sql. Wouldn't it be more effective (easier
for postgresql to parse) by using  possibleValueID IN
(3,5,6,9, etc) for example?

It also seems to read repeatly from the base a entity
bean marked as read only, time-out=0, and read-ahead.
(it shows generated sql of it several times)

2002-03-20 20:11:28,480 DEBUG
[org.jboss.ejb.plugins.cmp.jdbc.JDBCLoadEntityCommand.PossibleValue]
Executing SQL: SELECT possibleValueID,stringValue,
priority FROM PossibleValue WHERE (possibleValueID=?)
OR (poss
ibleValueID=?) OR (possibleValueID=?) OR
(possibleValueID=?) OR (possibleValueID=?) OR
(possibleValueID=?) OR (possibleValueID=?) OR
(possibleValueID=?) OR (possibleValueID=?) OR
(possibleValueID=?) OR (possibleV
alueID=?) OR (possibleValueID=?) OR (possibleValueID=?)
OR (possibleValueID=?) OR (possibleValueID=?) OR
(possibleValueID=?) OR (possibleValueID=?) OR
(possibleValueID=?) OR (possibleValueID=?) OR
(possibleValueI
D=?) OR (possibleValueID=?) OR (possibleValueID=?) OR
(possibleValueID=?) OR (possibleValueID=?) OR
(possibleValueID=?) OR (possibleValueID=?) OR
(possibleValueID=?) OR (possibleValueID=?) OR
(possibleValueID=?) 
OR (possibleValueID=?) OR (possibleValueID=?) OR
(possibleValueID=?) OR (possibleValueID=?) OR
(possibleValueID=?) OR (possibleValueID=?) OR
(possibleValueID=?) OR (possibleValueID=?) OR
(possibleValueID=?) OR (p
ossibleValueID=?) OR (possibleValueID=?) OR
(possibleValueID=?) OR (possibleValueID=?) OR
(possibleValueID=?) OR (possibleValueID=?) OR
(possibleValueID=?) OR (possibleValueID=?) OR
(possibleValueID=?) OR (possib
leValueID=?) OR (possibleValueID=?) OR
(possibleValueID=?) OR (possibleValueID=?) OR
(possibleValueID=?) OR (possibleValueID=?) OR
(possibleValueID=?) OR (possibleValueID=?) OR
(possibleValueID=?) OR (possibleVal
ueID=?)

--

Comment By: Marius Kotsbak (mkotsbak)
Date: 2002-03-23 11:10

Message:
Logged In: YES 
user_id=366650

What happens when there is more then one pk column?
Do you ask me? In my example, it is just one long PK
column (CMP-beans). I don't think I am using pk-objects in
this part either.

To me it looks like jboss is doing some sort of manual
joining too (wich postgres supports presumably much faster).
If I had written the sql statements for my example, I
wouldn't have needed any IN(2,4,6 etc), just JOINing. Also
this part of my application is slow, even if I try to tune
it with on-load, on-find.

Please don't adjust bug priorities.
I'm sorry. Didn't know I was allowed to do it

--

Comment By: Dain Sundstrom (dsundstrom)
Date: 2002-03-22 22:44

Message:
Logged In: YES 
user_id=251431

What happens when there is more then one pk column?

Please don't adjust bug priorities.

--

You can respond by visiting: 
http://sourceforge.net/tracker/?func=detailatid=376685aid=532734group_id=22866

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

Re: [JBoss-dev] CVS locks?

2002-03-23 Thread Adrian Brock


Hi Jason,

Sorry for the delay. If I'd just hung around 15 mins :-)

The full path is
/cvsroot/jboss/contrib/jetty/src/main/org/mortbay/jetty/jmx

The locks are held by anoncvs_jboss and maximal

Regards,
Adrian

 Can you tell me what the full paths are that are
 locked.
 
 --jason
 
 
 Adrian Brock wrote:
 
 Hi,
 
 Is there a problem with locks in cvs? Or is this
 deliberate?
 
 I'm trying to tag cvs before committing the jbossmx
 integration in case there's a problem.
 
 I've got two people locking jetty/jmx, one is
 anoncvs.
 They've had the lock for over an hour.
 
 Anyway, I'm going to get a couple of hours sleep
 before
 trying again.
 
 Regards,
 Adrian
 _
 ___
 View thread online:
 http://main.jboss.org/thread.jsp?forum=66thread=11429
 
 ___
 Jboss-development mailing list
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/jboss-de
 elopment
 
 
 
 
 ___
 Jboss-development mailing list
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/jboss-dev
 lopment


_
View thread online: http://main.jboss.org/thread.jsp?forum=66thread=11429

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

Re: [JBoss-dev] Forums::FAQ is a mess

2002-03-23 Thread Peter Fagerlund


on 23-03-2 03.23, Jason Dillon at [EMAIL PROTECTED] wrote:

 I was just looking through this, answered a couple, but damn this is a
 mess... not really what I expected to find under a FAQ listing... its
 half FAQ-like entries and then half lame user questions...

I deployed a big fat war called cocoon on Jetty-JBoss and in the process I
am reading the cocoon list's - yesterday they are discussing the possiblity
to sifter throught the mail list's and auto extract content into a faq
rendered throught cocoon.

I am thinking a small wiki like thing for each topic(wiki mom) and one big
wiki like thing collecting and displaying the small ones ... Trad faq
needs alot of maintanace a wiki like soloution also needs alot of work but
are much more Live to edit ... the link generation has its merits ...
forum is good and can only get better in tandem with a WikedBoss ... and
then to draw knowledge to compile a faq from the WikedBoss would be a
possibility ...

/peter_f


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

RE: [jetty-discuss] [Fwd: [JBoss-dev] Authentication with Jetty]

2002-03-23 Thread Ignacio Coloma


Jan how I love you.

That fixed it. I was trying to write a repro case as Scott asked, but
haven't been able to get the same behaviour. I prepared a servlet that was
registered in jbosstest-web and reproduced my situation but I wasn't able to
get my same bug.

Your fix worked, instead. Thanks a lot.

 -Mensaje original-
 De: Jan Bartel [mailto:[EMAIL PROTECTED]]
 Enviado el: viernes, 22 de marzo de 2002 10:36
 Para: [EMAIL PROTECTED];
 [EMAIL PROTECTED]
 Asunto: Re: [jetty-discuss] [Fwd: [JBoss-dev] Authentication with Jetty]


 OK chaps, I'm going to have a shot at providing a solution to this.

 I think what is happening is that Jetty is only setting the Principal
 to null after it is finished handling a request, rather than both the
 Principal *and* the Credential. Therefore, when no user has been
 authenticated, both Principal and Credential will be null. However,
 after a user has been authenticated, there will be a thread with a null
 Principal but a still set Credential.

 Now I haven't fully traced back the intricacies of the security code,
 but I notice that there are a few tests like:
 if (username == null  password == null)
  use the unauthenticatedIdentity;

 I am assuming that maybe the username and password are obtained from the
 thread's SecurityAssociation.getPrincipal() and
 SecurityAssociation.getPassword().

 So, in short I've made sure we null out *both*
 SecurityAssociation.Principal and SecurityAssociation.Credential.

 Update your tree to get the new
 $JBOSSHOME/jetty/src/main/org/jboss/jetty/Jetty.java.

 If that doesn't fix it, then I definitely give up :-)

 Jan

 Scott M Stark wrote:

 I'm not following what you meant in your original post about
 I get an exception one of each 3 times...
 
 Hit refresh - ok
 Hit refresh - ok
 Hit refresh - Error 500
 
 The error is thrown on any non-authenticated browser when there is an
 authenticated one open. If you don't authenticate anyone (if you only
 
  browse
 
 the public zone) there is no error.
 
 
  That should not happen. Is the servlet accessing the ejb deployed in
  both the protected and unprotected areas? Try to reproduce the issue
  with a variation of the jbosstest-web.ear.
 
 
 MyAuthEntry {
 org.jboss.security.auth.spi.DatabaseServerLoginModule required
 dsJndiName=java:/CanplasticaDS
 principalsQuery=SELECT PASSWORD AS Password FROM USUARIO
 WHERE ID=?
 rolesQuery=SELECT ROLE AS Role, 'Roles' AS RoleGroup FROM
 ROLE WHERE
 USU_ID = ?
 unauthenticatedIdentity=nobody --
 ;
 };
 
 Also the nobody user has a principal record, because if not it
 also wasn't
 allowed to access the app.
 
  That should work then.
 
 
 
  ___
  Jboss-development mailing list
  [EMAIL PROTECTED]
  https://lists.sourceforge.net/lists/listinfo/jboss-development
 



  Yahoo! Groups Sponsor -~--
 Tiny Wireless Camera under $80!
 Order Now! FREE VCR Commander!
 Click Here - Only 1 Day Left!
 http://us.click.yahoo.com/nuyOHD/7.PDAA/yigFAA/CefplB/TM
 -~-

 For the latest information about Jetty, please see
http://jetty.mortbay.org

To alter your subscription to this list goto
http://groups.yahoo.com/group/jetty-discuss

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/





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

Re: [JBoss-dev] CVS locks?

2002-03-23 Thread Adrian Brock


IANACVSE - I am not a CVS expert :-)

It is correct that I can tag later if I keep
CVS snapshots before and after my commit?

Regards,
Adrian

 Hi Jason,
 
 Sorry for the delay. If I'd just hung around 15 mins
 :-)
 
 The full path is
 /cvsroot/jboss/contrib/jetty/src/main/org/mortbay/jett
 /jmx
 
 The locks are held by anoncvs_jboss and maximal
 
 Regards,
 Adrian
 
  Can you tell me what the full paths are that are
  locked.
  
  --jason
  
  
  Adrian Brock wrote:
  
  Hi,
  
  Is there a problem with locks in cvs? Or is this
  deliberate?
  
  I'm trying to tag cvs before committing the
 jbossmx
  integration in case there's a problem.
  
  I've got two people locking jetty/jmx, one is
  anoncvs.
  They've had the lock for over an hour.
  
  Anyway, I'm going to get a couple of hours sleep
  before
  trying again.
  
  Regards,
  Adrian
 
 _
 
  ___
  View thread online:
 
 http://main.jboss.org/thread.jsp?forum=66thread=11429
 
  
  ___
  Jboss-development mailing list
  [EMAIL PROTECTED]
 
 https://lists.sourceforge.net/lists/listinfo/jboss-de
 
  elopment
  
  
  
  
  ___
  Jboss-development mailing list
  [EMAIL PROTECTED]
 
 https://lists.sourceforge.net/lists/listinfo/jboss-dev
 
  lopment
 


_
View thread online: http://main.jboss.org/thread.jsp?forum=66thread=11429

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

Re: [JBoss-dev] CVS locks?

2002-03-23 Thread Scott M Stark


No. You can tag latter by date or version. Tagging
does not work on the working directory so you can't
just tag your local copy.


Scott Stark
Chief Technology Officer
JBoss Group, LLC

- Original Message -
From: Adrian Brock [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Saturday, March 23, 2002 8:34 AM
Subject: Re: [JBoss-dev] CVS locks?


 IANACVSE - I am not a CVS expert :-)

 It is correct that I can tag later if I keep
 CVS snapshots before and after my commit?

 Regards,
 Adrian

  Hi Jason,
 
  Sorry for the delay. If I'd just hung around 15 mins
  :-)
 
  The full path is
  /cvsroot/jboss/contrib/jetty/src/main/org/mortbay/jett
  /jmx
 
  The locks are held by anoncvs_jboss and maximal
 
  Regards,
  Adrian
 
   Can you tell me what the full paths are that are
   locked.
  
   --jason
  
  
   Adrian Brock wrote:
  
   Hi,
   
   Is there a problem with locks in cvs? Or is this
   deliberate?
   
   I'm trying to tag cvs before committing the
  jbossmx
   integration in case there's a problem.
   
   I've got two people locking jetty/jmx, one is
   anoncvs.
   They've had the lock for over an hour.
   
   Anyway, I'm going to get a couple of hours sleep
   before
   trying again.
   
   Regards,
   Adrian
  
  _
 
   ___
   View thread online:
  
  http://main.jboss.org/thread.jsp?forum=66thread=11429
 
   
   ___
   Jboss-development mailing list
   [EMAIL PROTECTED]
  
  https://lists.sourceforge.net/lists/listinfo/jboss-de
 
   elopment
   
  
  
  
   ___
   Jboss-development mailing list
   [EMAIL PROTECTED]
  
  https://lists.sourceforge.net/lists/listinfo/jboss-dev
 
   lopment
 


 _
 View thread online: http://main.jboss.org/thread.jsp?forum=66thread=11429

 ___
 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] CVS locks?

2002-03-23 Thread Adrian Brock


Thanks Scott,

I'll wait for the locks to go away.

Regards,
Adrian

 No. You can tag latter by date or version. Tagging
 does not work on the working directory so you can't
 just tag your local copy.
 
 
 Scott Stark
 Chief Technology Officer
 JBoss Group, LLC
 
 - Original Message -
 From: Adrian Brock [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Sent: Saturday, March 23, 2002 8:34 AM
 Subject: Re: [JBoss-dev] CVS locks?
 
 
  IANACVSE - I am not a CVS expert :-)
 
  It is correct that I can tag later if I keep
  CVS snapshots before and after my commit?
 
  Regards,
  Adrian
 
   Hi Jason,
  
   Sorry for the delay. If I'd just hung around 15
 mins
   :-)
  
   The full path is
  
 /cvsroot/jboss/contrib/jetty/src/main/org/mortbay/jett
   /jmx
  
   The locks are held by anoncvs_jboss and maximal
  
   Regards,
   Adrian
  
Can you tell me what the full paths are that
 are
locked.
   
--jason
   
   
Adrian Brock wrote:
   
Hi,

Is there a problem with locks in cvs? Or is
 this
deliberate?

I'm trying to tag cvs before committing the
   jbossmx
integration in case there's a problem.

I've got two people locking jetty/jmx, one is
anoncvs.
They've had the lock for over an hour.

Anyway, I'm going to get a couple of hours
 sleep
before
trying again.

Regards,
Adrian
   
  
 _
  
___
View thread online:
   
  
 http://main.jboss.org/thread.jsp?forum=66thread=11429
  

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

   
   
   
___
Jboss-development mailing list
[EMAIL PROTECTED]
   
  
 https://lists.sourceforge.net/lists/listinfo/jboss-dev
  
lopment
  
 
 
 
 __
 __
  View thread online:
 http://main.jboss.org/thread.jsp?forum=66thread=11429
 
  ___
  Jboss-development mailing list
  [EMAIL PROTECTED]
 
 https://lists.sourceforge.net/lists/listinfo/jboss-dev
 lopment
 
 
 
 ___
 Jboss-development mailing list
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/jboss-dev
 lopment


_
View thread online: http://main.jboss.org/thread.jsp?forum=66thread=11429

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

Re: [JBoss-dev] Forums::FAQ is a mess

2002-03-23 Thread Luke Taylor


Jason Dillon wrote:
 I was just looking through this, answered a couple, but damn this is a 
 mess... not really what I expected to find under a FAQ listing... its 
 half FAQ-like entries and then half lame user questions...
 
 =(
 

There's no real information structure to a FAQ forum, so I can't see it 
working. I was planning on doing some more work on the FAQ which is part 
of the online manual build, though doesn't get displayed.

I think ultimately the traditional approach is the best way. A wiki is a 
good but will still get cluttered with lots of opinions rather than 
definite answers. It's good to have a source of concise, accurate 
answers, or pointers to the relevant chapters of the manuals/books.

I'll look at getting it into shape again once I've finished the current 
stuff I'm working on... probably start of April sometime.

Luke.



-- 
  Luke Taylor.  Monkey Machine Ltd.
  PGP Key ID: 0x57E9523Chttp://www.mkeym.com




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

Re: [JBoss-dev] CVS locks?

2002-03-23 Thread Adrian Brock


I've got just over 40 source modifications.

Is it acceptable to tag individually using a
non Rel_3_* tag?

I can do the tagging by hand on individual sources.

Alternatively, I could just commit the changes.
There are already java 1.4 users using jbossmx with
jboss3 to solve the jsr77 problem, but these probably
aren't live users using it in anger.

Regards,
Adrian


 Thanks Scott,
 
 I'll wait for the locks to go away.
 
 Regards,
 Adrian
 
  No. You can tag latter by date or version. Tagging
  does not work on the working directory so you
 can't
  just tag your local copy.
  
  
  Scott Stark
  Chief Technology Officer
  JBoss Group, LLC
  
  - Original Message -
  From: Adrian Brock [EMAIL PROTECTED]
  To: [EMAIL PROTECTED]
  Sent: Saturday, March 23, 2002 8:34 AM
  Subject: Re: [JBoss-dev] CVS locks?
  
  
   IANACVSE - I am not a CVS expert :-)
  
   It is correct that I can tag later if I keep
   CVS snapshots before and after my commit?
  
   Regards,
   Adrian
  
Hi Jason,
   
Sorry for the delay. If I'd just hung around
 15
  mins
:-)
   
The full path is
   
 
 /cvsroot/jboss/contrib/jetty/src/main/org/mortbay/jett
 
/jmx
   
The locks are held by anoncvs_jboss and
 maximal
   
Regards,
Adrian
   
 Can you tell me what the full paths are that
  are
 locked.

 --jason


 Adrian Brock wrote:

 Hi,
 
 Is there a problem with locks in cvs? Or is
  this
 deliberate?
 
 I'm trying to tag cvs before committing the
jbossmx
 integration in case there's a problem.
 
 I've got two people locking jetty/jmx, one
 is
 anoncvs.
 They've had the lock for over an hour.
 
 Anyway, I'm going to get a couple of hours
  sleep
 before
 trying again.
 
 Regards,
 Adrian

   
 
 _
 
   
 ___
 View thread online:

   
 
 http://main.jboss.org/thread.jsp?forum=66thread=11429
 
   
 

  ___
 Jboss-development mailing list
 [EMAIL PROTECTED]

   
 
 https://lists.sourceforge.net/lists/listinfo/jboss-de
 
   
 elopment
 




 ___
 Jboss-development mailing list
 [EMAIL PROTECTED]

   
 
 https://lists.sourceforge.net/lists/listinfo/jboss-dev
 
   
 lopment
   
  
  
  
 
 __
 
  __
   View thread online:
 
 http://main.jboss.org/thread.jsp?forum=66thread=11429
 
  
   ___
   Jboss-development mailing list
   [EMAIL PROTECTED]
  
 
 https://lists.sourceforge.net/lists/listinfo/jboss-dev
 
  lopment
  
  
  
  ___
  Jboss-development mailing list
  [EMAIL PROTECTED]
 
 https://lists.sourceforge.net/lists/listinfo/jboss-dev
 
  lopment
 


_
View thread online: http://main.jboss.org/thread.jsp?forum=66thread=11429

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

Re: [JBoss-dev] CVS locks?

2002-03-23 Thread Scott M Stark


What is the purpose of the tag your trying to apply? If
your trying to define snaphosts before and after a move
to the JBossMX JMX implementation this can be done
after the fact using tags based on timestamps. The lastest
checkin was at Mar 22, 2002 8:55 PM PST. You can use the
rtag command to apply the Rel_3_x_y tags after the lock has
been cleared. I have updated the request to remove the stale
locks so hopefully this won't take too long. If there are no
changes to the jetty module you could tag everything but that
module and apply the tags after the lock is cleared as both tags
will point to the same versions in the jetty module.

Setting a tag that is local to a few files is not very useful 


Scott Stark
Chief Technology Officer
JBoss Group, LLC

- Original Message - 
From: Adrian Brock [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Saturday, March 23, 2002 10:11 AM
Subject: Re: [JBoss-dev] CVS locks?


 I've got just over 40 source modifications.
 
 Is it acceptable to tag individually using a
 non Rel_3_* tag?
 
 I can do the tagging by hand on individual sources.
 
 Alternatively, I could just commit the changes.
 There are already java 1.4 users using jbossmx with
 jboss3 to solve the jsr77 problem, but these probably
 aren't live users using it in anger.
 
 Regards,
 Adrian
 



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

Re: [JBoss-dev] CVS locks?

2002-03-23 Thread Adrian Brock


Hi Scott,

I didn't think the local tags would be very useful, 
except to me if I had to reverse the mod on individual
sources.
Yes, I am trying to get a before and after snapshot.

Perhaps I should just stop worrying about it and
keep a diff in a safe place.

Regards,
Adrian

 What is the purpose of the tag your trying to apply?
 If
 your trying to define snaphosts before and after a
 move
 to the JBossMX JMX implementation this can be done
 after the fact using tags based on timestamps. The
 lastest
 checkin was at Mar 22, 2002 8:55 PM PST. You can use
 the
 rtag command to apply the Rel_3_x_y tags after the
 lock has
 been cleared. I have updated the request to remove
 the stale
 locks so hopefully this won't take too long. If there
 are no
 changes to the jetty module you could tag everything
 but that
 module and apply the tags after the lock is cleared
 as both tags
 will point to the same versions in the jetty module.
 
 Setting a tag that is local to a few files is not
 very useful 
 
 
 Scott Stark
 Chief Technology Officer
 JBoss Group, LLC
 
 - Original Message - 
 From: Adrian Brock [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Sent: Saturday, March 23, 2002 10:11 AM
 Subject: Re: [JBoss-dev] CVS locks?
 
 
  I've got just over 40 source modifications.
  
  Is it acceptable to tag individually using a
  non Rel_3_* tag?
  
  I can do the tagging by hand on individual sources.
  
  Alternatively, I could just commit the changes.
  There are already java 1.4 users using jbossmx with
  jboss3 to solve the jsr77 problem, but these
 probably
  aren't live users using it in anger.
  
  Regards,
  Adrian
  
 
 
 
 ___
 Jboss-development mailing list
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/jboss-dev
 lopment


_
View thread online: http://main.jboss.org/thread.jsp?forum=66thread=11429

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

[JBoss-dev] Re: JBossMQ problem of Softalia

2002-03-23 Thread Hiram Chirino



Hi, I'm done..

I'm attaching the diff right now.

The one major thing that changed is that the oswego-concurrent.jar must now 
be in the client's classpath also.  The diff includes an udpate to the 
build.xml so that it gets placed in the /client directory.

Regards,
Hiram

From: Andreas Schaefer [EMAIL PROTECTED]
To: Hiram Chirino [EMAIL PROTECTED]
Subject: Re: JBossMQ problem of Softalia
Date: Sat, 23 Mar 2002 10:30:00 -0800

Hi Hiram

Great that you could solve it on your own.
I have to call Softalia soon and tell them
when we can provide them with the path.
Do you have (roughly) an idea when you
are ready ?

Thanx - Andy






_
Chat with friends online, try MSN Messenger: http://messenger.msn.com

[JBoss-dev] CVS update: jbossmx/src/main/org/jbossmx/cluster/watchdog/mbean Watchdog.java

2002-03-23 Thread Adrian Brock


  User: ejort   
  Date: 02/03/23 13:10:59

  Modified:src/main/org/jbossmx/cluster/watchdog/mbean Watchdog.java
  Log:
  JBoss/JBossMX integration. Also includes a fix to the cluster tests and a more 
complete ejblink test that currently fails
  
  Revision  ChangesPath
  1.6   +1 -5  
jbossmx/src/main/org/jbossmx/cluster/watchdog/mbean/Watchdog.java
  
  Index: Watchdog.java
  ===
  RCS file: 
/cvsroot/jboss/jbossmx/src/main/org/jbossmx/cluster/watchdog/mbean/Watchdog.java,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -r1.5 -r1.6
  --- Watchdog.java 4 Dec 2001 22:34:01 -   1.5
  +++ Watchdog.java 23 Mar 2002 21:10:59 -  1.6
  @@ -1087,8 +1087,6 @@
   {
   result = ((Integer) m_server.invoke(objectName, 
retrieveMBeanState,
   new Object[0], new String[0])).intValue();
  -
  -//result = ((Integer) 
m_server.invoke(objectInstance.getObjectName(), getMBeanState, new Object[0], new 
String[0])).intValue();
   }
   catch(Exception e)
   {
  @@ -1616,8 +1614,6 @@
   Integer result = (Integer) 
m_server.invoke(objectName,retrieveMBeanState,
   new Object[0], new String[0]);
   
  -//m_server.invoke(objectInstance.getObjectName(), getMBeanState, 
new Object[0], new String[0]);
  -
   running = (result.intValue() == Startable.RUNNING);
   }
   catch(Exception e)
  @@ -1745,7 +1741,7 @@
   m_watchdogEventManagerObjectName = objectName;
   
   m_watchdogEventManagerRemoteInterface = 
(WatchdogEventManagerRemoteInterface)
  -m_server.invoke(objectName, getRemoteInterface, new Object[0], new 
String[0]);
  +m_server.getAttribute(objectName, RemoteInterface);
   }
   
   /**
  
  
  

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

[JBoss-dev] CVS update: jbossmx build.xml

2002-03-23 Thread Adrian Brock


  User: ejort   
  Date: 02/03/23 13:10:59

  Modified:.build.xml
  Log:
  JBoss/JBossMX integration. Also includes a fix to the cluster tests and a more 
complete ejblink test that currently fails
  
  Revision  ChangesPath
  1.32  +9 -9  jbossmx/build.xml
  
  Index: build.xml
  ===
  RCS file: /cvsroot/jboss/jbossmx/build.xml,v
  retrieving revision 1.31
  retrieving revision 1.32
  diff -u -r1.31 -r1.32
  --- build.xml 28 Feb 2002 04:08:01 -  1.31
  +++ build.xml 23 Mar 2002 21:10:59 -  1.32
  @@ -12,7 +12,7 @@
   !----
   !-- == --
   
  -!-- $Id: build.xml,v 1.31 2002/02/28 04:08:01 user57 Exp $ --
  +!-- $Id: build.xml,v 1.32 2002/03/23 21:10:59 ejort Exp $ --
   
   project default=main name=JBoss/Cluster
   
  @@ -69,13 +69,6 @@
   !-- Libraries --
   !-- = --
   
  -!-- Java Management Extensions (JMX) --
  -property name=sun.jmx.root value=${project.thirdparty}/sun/jmx/
  -property name=sun.jmx.lib value=${sun.jmx.root}/lib/
  -path id=sun.jmx.classpath
  -  pathelement path=${sun.jmx.lib}/jmxri.jar/
  -/path
  -
   !-- Java API for XML Processing (JAXP) --
   property name=sun.jaxp.root value=${project.thirdparty}/sun/jaxp/
   property name=sun.jaxp.lib value=${sun.jaxp.root}/lib/
  @@ -131,7 +124,6 @@
   
   !-- The combined library classpath --
   path id=library.classpath
  -  path refid=sun.jmx.classpath/
 path refid=sun.jaxp.classpath/
 path refid=sun.jaas.classpath/
 path refid=sun.jsse.classpath/
  @@ -187,6 +179,13 @@
 pathelement path=${jboss.server.lib}/jboss.jar/
   /path
   
  +!-- JMX --
  +property name=jboss.jmx.root value=${project.root}/jmx/output/
  +property name=jboss.jmx.lib value=${jboss.jmx.root}/lib/
  +path id=jboss.jmx.classpath
  +  pathelement path=${jboss.jmx.lib}/jboss-jmx.jar/
  +/path
  +
   !-- The combined dependent module classpath --
   path id=dependentmodule.classpath
 path refid=jboss.j2ee.classpath/
  @@ -195,6 +194,7 @@
 path refid=jboss.naming.classpath/
 path refid=jboss.messaging.classpath/
 path refid=jboss.server.classpath/
  +  path refid=jboss.jmx.classpath/
   /path
   
   !-- = --
  
  
  

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

[JBoss-dev] CVS update: jboss-common/src/main/org/jboss/util/jmx MBeanProxy.java

2002-03-23 Thread Adrian Brock


  User: ejort   
  Date: 02/03/23 13:11:00

  Modified:src/main/org/jboss/util/jmx MBeanProxy.java
  Log:
  JBoss/JBossMX integration. Also includes a fix to the cluster tests and a more 
complete ejblink test that currently fails
  
  Revision  ChangesPath
  1.3   +99 -3 jboss-common/src/main/org/jboss/util/jmx/MBeanProxy.java
  
  Index: MBeanProxy.java
  ===
  RCS file: /cvsroot/jboss/jboss-common/src/main/org/jboss/util/jmx/MBeanProxy.java,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- MBeanProxy.java   5 Mar 2002 02:59:52 -   1.2
  +++ MBeanProxy.java   23 Mar 2002 21:11:00 -  1.3
  @@ -13,16 +13,29 @@
   import java.lang.reflect.Proxy;
   import java.lang.reflect.InvocationHandler;
   
  +import java.util.HashMap;
  +
  +import javax.management.Attribute;
  +import javax.management.InstanceNotFoundException;
  +import javax.management.MBeanAttributeInfo;
  +import javax.management.MBeanInfo;
   import javax.management.MBeanServer;
   import javax.management.ObjectName;
   import javax.management.MalformedObjectNameException;
   
   /**
* A factory for producing MBean proxies.
  - *  
  + *
  + * pbRevisions:/b
  + * pb20020321 Adrian Brock:/b
  + * ul
  + * liDon't process attributes using invoke.
  + * /ul
  + *
* @author a href=mailto:[EMAIL PROTECTED];Rickard Öberg/a.
* @author a href=mailto:[EMAIL PROTECTED];Jason Dillon/a
  - * @version $Revision: 1.2 $
  + * @author a href=mailto:[EMAIL PROTECTED];Adrian Brock/a.
  + * @version $Revision: 1.3 $
*/
   public class MBeanProxy
  implements InvocationHandler
  @@ -32,6 +45,9 @@
   
  /** The name of the object to invoke. */
  private final ObjectName name;
  +
  +   /** The MBean's attributes */
  +   private HashMap attributeMap  = new HashMap();
  
  /**
   * Construct a MBeanProxy.
  @@ -48,6 +64,20 @@
  {
 this.name = name;
 this.server = server;
  +
  +  // The MBean's attributes
  +  try
  +  {
  + MBeanInfo info = server.getMBeanInfo(name);
  + MBeanAttributeInfo[] attributes = info.getAttributes();
  +
  + for (int i = 0; i  attributes.length; ++i)
  +attributeMap.put(attributes[i].getName(), attributes[i]);
  +  }
  +  catch (Exception e)
  +  {
  + throw new RuntimeException(Error creating MBeanProxy:  + name);
  +  }
  }
  
  /**
  @@ -59,6 +89,72 @@
   Object[] args)
 throws Throwable
  {
  +  String methodName = method.getName();
  +
  +  // Get attribute
  +  if (methodName.startsWith(get)  args == null)
  +  {
  + String attrName = methodName.substring(3);
  + MBeanAttributeInfo info = (MBeanAttributeInfo) attributeMap.get(attrName);
  + if (info != null)
  + {
  +String retType = method.getReturnType().getName();
  +if (retType.equals(info.getType()))
  +{
  +   try
  +   {
  +  return server.getAttribute(name, attrName);
  +   }
  +   catch (Exception e)
  +   {
  +  throw JMXExceptionDecoder.decode(e);
  +   }
  +}
  + }
  +  }
  +
  +  // Is attribute
  +  else if (methodName.startsWith(is)  args == null)
  +  {
  + String attrName = methodName.substring(2);
  + MBeanAttributeInfo info = (MBeanAttributeInfo) attributeMap.get(attrName);
  + if (info != null  info.isIs())
  + {
  +Class retType = method.getReturnType();
  +if (retType.equals(Boolean.class) || retType.equals(Boolean.TYPE))
  +{
  +   try
  +   {
  +  return server.getAttribute(name, attrName);
  +   }
  +   catch (Exception e)
  +   {
  +  throw JMXExceptionDecoder.decode(e);
  +   }
  +}
  + }
  +  }
  +
  +  // Set attribute
  +  else if (methodName.startsWith(set)  args != null  args.length == 1)
  +  {
  + String attrName = methodName.substring(3);
  + MBeanAttributeInfo info = (MBeanAttributeInfo) attributeMap.get(attrName);
  + if (info != null  method.getReturnType() == Void.TYPE)
  + {
  +try
  +{
  +   server.setAttribute(name, new Attribute(attrName, args[0]));
  +   return null;
  +}
  +catch (Exception e)
  +{
  +   throw JMXExceptionDecoder.decode(e);
  +}
  + }
  +  }
  +
  +  // Operation
 if (args == null) args = new Object[0];
   
 // convert the parameter types to strings for JMX
  @@ -70,7 +166,7 @@
   
 // invoke the server

[JBoss-dev] CVS update: jbossmx/src/main/org/jbossmx/cluster/watchdog/agent BaseAgent.java

2002-03-23 Thread Adrian Brock


  User: ejort   
  Date: 02/03/23 13:10:59

  Modified:src/main/org/jbossmx/cluster/watchdog/agent BaseAgent.java
  Log:
  JBoss/JBossMX integration. Also includes a fix to the cluster tests and a more 
complete ejblink test that currently fails
  
  Revision  ChangesPath
  1.6   +35 -2 
jbossmx/src/main/org/jbossmx/cluster/watchdog/agent/BaseAgent.java
  
  Index: BaseAgent.java
  ===
  RCS file: 
/cvsroot/jboss/jbossmx/src/main/org/jbossmx/cluster/watchdog/agent/BaseAgent.java,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -r1.5 -r1.6
  --- BaseAgent.java8 Oct 2001 16:52:59 -   1.5
  +++ BaseAgent.java23 Mar 2002 21:10:59 -  1.6
  @@ -372,8 +372,7 @@
   {
   try
   {
  -return (String) m_server.invoke(m_rmiConnectorObjectName, getJNDIName,
  -m_sEmptyObject, m_sEmptyString);
  +return (String) m_server.getAttribute(m_rmiConnectorObjectName, 
JNDIName);
   }
   catch(Exception e)
   {
  @@ -428,6 +427,40 @@
   {
   //LOG.warning(infe);
   
  +throw new RemoteException(, infe);
  +}
  +}
  +
  +/**
  + * Get an attribute from an MBean.
  + *
  + * @paramobjectName The object name of the MBean.
  + * @paramattrName The name of the attribute.
  + *
  + * @return The object returned by the operation, which represents the value of 
the attribute.
  + * @throws RemoteException
  + */
  +public Object getMBeanAttribute(String objectName, String attrName)
  +throws RemoteException
  +{
  +try
  +{
  +return m_server.getAttribute(new ObjectName(objectName), attrName)
  +}
  +catch(MalformedObjectNameException mone)
  +{
  +throw new RemoteException(, mone);
  +}
  +catch(ReflectionException re)
  +{
  +throw new RemoteException(, re);
  +}
  +catch(MBeanException me)
  +{
  +throw new RemoteException(, me);
  +}
  +catch(InstanceNotFoundException infe)
  +{
   throw new RemoteException(, infe);
   }
   }
  
  
  

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

[JBoss-dev] CVS update: jbosscx build.xml

2002-03-23 Thread Adrian Brock


  User: ejort   
  Date: 02/03/23 13:11:00

  Modified:.build.xml
  Log:
  JBoss/JBossMX integration. Also includes a fix to the cluster tests and a more 
complete ejblink test that currently fails
  
  Revision  ChangesPath
  1.33  +9 -9  jbosscx/build.xml
  
  Index: build.xml
  ===
  RCS file: /cvsroot/jboss/jbosscx/build.xml,v
  retrieving revision 1.32
  retrieving revision 1.33
  diff -u -r1.32 -r1.33
  --- build.xml 22 Mar 2002 01:37:45 -  1.32
  +++ build.xml 23 Mar 2002 21:11:00 -  1.33
  @@ -12,7 +12,7 @@
   !----
   !-- == --
   
  -!-- $Id: build.xml,v 1.32 2002/03/22 01:37:45 user57 Exp $ --
  +!-- $Id: build.xml,v 1.33 2002/03/23 21:11:00 ejort Exp $ --
   
   project default=main name=JBoss/Connector
   
  @@ -69,13 +69,6 @@
   !-- Libraries --
   !-- = --
   
  -!-- Java Management Extensions (JMX) --
  -property name=sun.jmx.root value=${project.thirdparty}/sun/jmx/
  -property name=sun.jmx.lib value=${sun.jmx.root}/lib/
  -path id=sun.jmx.classpath
  -  pathelement path=${sun.jmx.lib}/jmxri.jar/
  -/path
  -
   !-- Java API for XML Processing (JAXP) --
   property name=sun.jaxp.root value=${project.thirdparty}/sun/jaxp/
   property name=sun.jaxp.lib value=${sun.jaxp.root}/lib/
  @@ -108,7 +101,6 @@
   
   !-- The combined library classpath --
   path id=library.classpath
  -  path refid=sun.jmx.classpath/
 path refid=sun.jaxp.classpath/
 path refid=sun.jaas.classpath/
 path refid=apache.log4j.classpath/
  @@ -162,6 +154,13 @@
 pathelement path=${jboss.management.lib}/jboss-management.jar/
   /path
   
  +!-- JMX --
  +property name=jboss.jmx.root value=${project.root}/jmx/output/
  +property name=jboss.jmx.lib value=${jboss.jmx.root}/lib/
  +path id=jboss.jmx.classpath
  +  pathelement path=${jboss.jmx.lib}/jboss-jmx.jar/
  +/path
  +
   !-- The combined depedant module classpath --
   path id=dependentmodule.classpath
 path refid=jboss.j2ee.classpath/
  @@ -170,6 +169,7 @@
 path refid=jboss.server.classpath/
 path refid=jboss.pool.classpath/
 path refid=jboss.management.classpath/
  +  path refid=jboss.jmx.classpath/
   /path
   
   !-- = --
  
  
  

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

[JBoss-dev] CVS update: jmx build.xml

2002-03-23 Thread Adrian Brock


  User: ejort   
  Date: 02/03/23 13:11:01

  Modified:.build.xml
  Log:
  JBoss/JBossMX integration. Also includes a fix to the cluster tests and a more 
complete ejblink test that currently fails
  
  Revision  ChangesPath
  1.30  +21 -1 jmx/build.xml
  
  Index: build.xml
  ===
  RCS file: /cvsroot/jboss/jmx/build.xml,v
  retrieving revision 1.29
  retrieving revision 1.30
  diff -u -r1.29 -r1.30
  --- build.xml 14 Mar 2002 18:28:25 -  1.29
  +++ build.xml 23 Mar 2002 21:11:01 -  1.30
  @@ -12,7 +12,7 @@
   !----
   !-- == --
   
  -!-- $Id: build.xml,v 1.29 2002/03/14 18:28:25 juhalindfors Exp $ --
  +!-- $Id: build.xml,v 1.30 2002/03/23 21:11:01 ejort Exp $ --
   
   project default=main name=JBoss/JMX
   
  @@ -287,6 +287,26 @@
 fileset dir=${build.classes}
   include name=**/
   exclude name=test/**/
  +  /fileset
  +/jar
  +
  +!-- Build the jboss-jmx-core.jar --
  +jar jarfile=${build.lib}/jboss-jmx-core.jar
  +  fileset dir=${build.classes}
  +include name=**/
  +exclude name=javax/management/monitor/**/
  +exclude name=javax/management/relation/**/
  +exclude name=javax/management/timer/**/
  +exclude name=test/**/
  +  /fileset
  +/jar
  +
  +!-- Build the jboss-jmx-services.jar --
  +jar jarfile=${build.lib}/jboss-jmx-services.jar
  +  fileset dir=${build.classes}
  +include name=javax/management/monitor/**/
  +include name=javax/management/relation/**/
  +include name=javax/management/timer/**/
 /fileset
   /jar
   
  
  
  

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

[JBoss-dev] CVS update: jboss-ejb build.xml

2002-03-23 Thread Adrian Brock


  User: ejort   
  Date: 02/03/23 13:11:00

  Modified:.build.xml
  Log:
  JBoss/JBossMX integration. Also includes a fix to the cluster tests and a more 
complete ejblink test that currently fails
  
  Revision  ChangesPath
  1.3   +9 -9  jboss-ejb/build.xml
  
  Index: build.xml
  ===
  RCS file: /cvsroot/jboss/jboss-ejb/build.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- build.xml 28 Feb 2002 04:08:02 -  1.2
  +++ build.xml 23 Mar 2002 21:11:00 -  1.3
  @@ -12,7 +12,7 @@
   !----
   !-- == --
   
  -!-- $Id: build.xml,v 1.2 2002/02/28 04:08:02 user57 Exp $ --
  +!-- $Id: build.xml,v 1.3 2002/03/23 21:11:00 ejort Exp $ --
   
   project default=main name=JBoss/EJB
   
  @@ -69,13 +69,6 @@
   !-- Libraries --
   !-- = --
   
  -!-- Java Management Extensions (JMX) --
  -property name=sun.jmx.root value=${project.thirdparty}/sun/jmx/
  -property name=sun.jmx.lib value=${sun.jmx.root}/lib/
  -path id=sun.jmx.classpath
  -  pathelement path=${sun.jmx.lib}/jmxri.jar/
  -/path
  -
   !-- JUnit --
   property name=junit.junit.root value=${project.thirdparty}/junit/junit/
   property name=junit.junit.lib value=${junit.junit.root}/lib/
  @@ -85,15 +78,22 @@
   
   !-- The combined library classpath --
   path id=library.classpath
  -  path refid=sun.jmx.classpath/
   /path
   
   !-- === --
   !-- Modules --
   !-- === --
   
  +!-- JMX --
  +property name=jboss.jmx.root value=${project.root}/jmx/output/
  +property name=jboss.jmx.lib value=${jboss.jmx.root}/lib/
  +path id=jboss.jmx.classpath
  +  pathelement path=${jboss.jmx.lib}/jboss-jmx.jar/
  +/path
  +
   !-- The combined dependent module classpath --
   path id=dependentmodule.classpath
  +  path refid=jboss.jmx.classpath/
   /path
   
   !-- = --
  
  
  

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

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

2002-03-23 Thread Adrian Brock


  User: ejort   
  Date: 02/03/23 13:11:02

  Modified:src/main/org/jboss/ejb EjbModule.java
  Log:
  JBoss/JBossMX integration. Also includes a fix to the cluster tests and a more 
complete ejblink test that currently fails
  
  Revision  ChangesPath
  1.14  +40 -10jboss/src/main/org/jboss/ejb/EjbModule.java
  
  Index: EjbModule.java
  ===
  RCS file: /cvsroot/jboss/jboss/src/main/org/jboss/ejb/EjbModule.java,v
  retrieving revision 1.13
  retrieving revision 1.14
  diff -u -r1.13 -r1.14
  --- EjbModule.java17 Mar 2002 12:59:44 -  1.13
  +++ EjbModule.java23 Mar 2002 21:11:02 -  1.14
  @@ -9,16 +9,20 @@
   
   
   import java.lang.reflect.Constructor;
  +import java.net.MalformedURLException;
   import java.net.URL;
  +import java.net.URLClassLoader;
   import java.rmi.RemoteException;
  +import java.util.ArrayList;
   import java.util.Collection;
   import java.util.HashMap;
   import java.util.Hashtable;
   import java.util.Iterator;
  -import java.util.WeakHashMap;
   import javax.ejb.EJBLocalHome;
  +import javax.naming.InitialContext;
   import javax.management.MBeanServer;
   import javax.management.ObjectName;
  +import org.jboss.deployment.DeploymentException;
   import org.jboss.deployment.DeploymentInfo;
   import org.jboss.ejb.BeanLockManager;
   import org.jboss.ejb.Container;
  @@ -44,10 +48,6 @@
   import org.jboss.system.ServiceMBeanSupport;
   import org.jboss.system.UnifiedClassLoader;
   import org.jboss.util.jmx.MBeanProxy;
  -import java.util.ArrayList;
  -import javax.naming.InitialContext;
  -import java.net.URLClassLoader;
  -import org.jboss.deployment.DeploymentException;
   import org.jboss.verifier.BeanVerifier;
   import org.jboss.verifier.event.VerificationEvent;
   import org.jboss.verifier.event.VerificationListener;
  @@ -78,7 +78,7 @@
* @author a href=mailto:[EMAIL PROTECTED];David Jencks/a
* @author a href=mailto:[EMAIL PROTECTED];Francisco Reverbel/a
* @author a href=mailto:[EMAIL PROTECTED];Adrian.Brock/a
  - * @version $Revision: 1.13 $
  + * @version $Revision: 1.14 $
*
* @jmx:mbean extends=org.jboss.system.ServiceMBean
*/
  @@ -135,7 +135,7 @@
  // Static 
  
  /** Stores a map of DeploymentInfos to EjbModules. */
  -   private static WeakHashMap ejbModulesByDeploymentInfo = new WeakHashMap();
  +   private static HashMap ejbModulesByDeploymentInfo = new HashMap();
   
  // Public 
   
  @@ -145,9 +145,6 @@
  {
 this.deploymentInfo = di;
 this.name = deploymentInfo.url.toString();
  -
  -  // Keep track of which deployments are ejbModules
  -  ejbModulesByDeploymentInfo.put(di, this);
  }
   
  /**
  @@ -286,6 +283,12 @@
  // Service implementation 
  public void createService() throws Exception 
  {
  +  // Keep track of which deployments are ejbModules
  +  synchronized(ejbModulesByDeploymentInfo)
  +  {
  + ejbModulesByDeploymentInfo.put(deploymentInfo, this);
  +  }
  +
 serviceController = (ServiceControllerMBean)
 MBeanProxy.create(ServiceControllerMBean.class,
   ServiceControllerMBean.OBJECT_NAME,
  @@ -442,6 +445,12 @@
 {  
EJBModule.destroy(server, getModuleName().toString() );
 }
  +
  +  // Keep track of which deployments are ejbModules
  +  synchronized(ejbModulesByDeploymentInfo)
  +  {
  + ejbModulesByDeploymentInfo.remove(deploymentInfo);
  +  }
  }

  // **
  @@ -930,6 +939,10 @@
   */
  private Container locateContainer(String name)
  {
  +  // Check for a relative path
  +  if (name.startsWith(..))
  + return locateContainerRelative(name);
  +
 // Get the top level deployment
 DeploymentInfo info = deploymentInfo;
 while (info.parent != null)
  @@ -974,6 +987,23 @@
 }
   
 // Nothing found
  +  return null;
  +   }
  +
  +   /**
  +* Find a container from this deployment package, used to process ejb-link
  +* that is a relative pathp
  +* 
  +* Determines the path based on the url.
  +*
  +* @param   name  ejb-name name defined in ejb-jar.xml in some jar in
  +*  the same deployment package
  +* @return  container for the named bean, or null if the container was
  +*  not found   
  +*/
  +   private Container locateContainerRelative(String name)
  +   {
  +  log.warn(Not implemented:  + name);
 return null;
  }
   }
  
  
  

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

[JBoss-dev] CVS update: jbosstest/src/resources/naming/ear/a/META-INF ejb-jar.xml jboss.xml

2002-03-23 Thread Adrian Brock


  User: ejort   
  Date: 02/03/23 13:11:04

  Modified:src/resources/naming/ear/a/META-INF ejb-jar.xml jboss.xml
  Log:
  JBoss/JBossMX integration. Also includes a fix to the cluster tests and a more 
complete ejblink test that currently fails
  
  Revision  ChangesPath
  1.2   +2 -0  jbosstest/src/resources/naming/ear/a/META-INF/ejb-jar.xml
  
  Index: ejb-jar.xml
  ===
  RCS file: /cvsroot/jboss/jbosstest/src/resources/naming/ear/a/META-INF/ejb-jar.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- ejb-jar.xml   17 Mar 2002 12:56:30 -  1.1
  +++ ejb-jar.xml   23 Mar 2002 21:11:04 -  1.2
  @@ -7,6 +7,8 @@
 ejb-nameSessionA/ejb-name
 homeorg.jboss.test.naming.interfaces.TestEjbLinkHome/home
 remoteorg.jboss.test.naming.interfaces.TestEjbLink/remote 
  +  local-homeorg.jboss.test.naming.interfaces.TestEjbLinkLocalHome/local-home
  +  localorg.jboss.test.naming.interfaces.TestEjbLinkLocal/local 
 ejb-classorg.jboss.test.naming.ejb.TestEjbLinkBean/ejb-class 
 session-typeStateless/session-type
 transaction-typeContainer/transaction-type
  
  
  
  1.2   +1 -0  jbosstest/src/resources/naming/ear/a/META-INF/jboss.xml
  
  Index: jboss.xml
  ===
  RCS file: /cvsroot/jboss/jbosstest/src/resources/naming/ear/a/META-INF/jboss.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- jboss.xml 17 Mar 2002 12:56:30 -  1.1
  +++ jboss.xml 23 Mar 2002 21:11:04 -  1.2
  @@ -5,6 +5,7 @@
   session
  ejb-nameSessionA/ejb-name
  jndi-namenaming/SessionA/jndi-name
  +   local-jndi-namenaming/local/SessionA/local-jndi-name
   /session
 /enterprise-beans
   /jboss
  
  
  

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

[JBoss-dev] CVS update: jboss-management build.xml

2002-03-23 Thread Adrian Brock


  User: ejort   
  Date: 02/03/23 13:11:01

  Modified:.build.xml
  Log:
  JBoss/JBossMX integration. Also includes a fix to the cluster tests and a more 
complete ejblink test that currently fails
  
  Revision  ChangesPath
  1.4   +9 -9  jboss-management/build.xml
  
  Index: build.xml
  ===
  RCS file: /cvsroot/jboss/jboss-management/build.xml,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- build.xml 11 Mar 2002 22:32:31 -  1.3
  +++ build.xml 23 Mar 2002 21:11:01 -  1.4
  @@ -12,7 +12,7 @@
   !----
   !-- == --
   
  -!-- $Id: build.xml,v 1.3 2002/03/11 22:32:31 starksm Exp $ --
  +!-- $Id: build.xml,v 1.4 2002/03/23 21:11:01 ejort Exp $ --
   
   project default=main name=JBoss/Management
   
  @@ -69,13 +69,6 @@
   !-- Libraries --
   !-- = --
   
  -!-- Java Management Extensions (JMX) --
  -property name=sun.jmx.root value=${project.thirdparty}/sun/jmx/
  -property name=sun.jmx.lib value=${sun.jmx.root}/lib/
  -path id=sun.jmx.classpath
  -  pathelement path=${sun.jmx.lib}/jmxri.jar/
  -/path
  -
   !-- JUnit --
   property name=junit.junit.root value=${project.thirdparty}/junit/junit/
   property name=junit.junit.lib value=${junit.junit.root}/lib/
  @@ -99,7 +92,6 @@
   
   !-- The combined library classpath --
   path id=library.classpath
  -  path refid=sun.jmx.classpath/
 path refid=apache.log4j.classpath/
 path refid=remote-mbeanserver.classpath/
   /path
  @@ -129,11 +121,19 @@
 pathelement path=${jboss.system.lib}/jboss-system.jar/
   /path
   
  +!-- JMX --
  +property name=jboss.jmx.root value=${project.root}/jmx/output/
  +property name=jboss.jmx.lib value=${jboss.jmx.root}/lib/
  +path id=jboss.jmx.classpath
  +  pathelement path=${jboss.jmx.lib}/jboss-jmx.jar/
  +/path
  +
   !-- The combined dependent module classpath --
   path id=dependentmodule.classpath
 path refid=jboss.j2ee.classpath/
 path refid=jboss.common.classpath/
 path refid=jboss.system.classpath/
  +  path refid=jboss.jmx.classpath/
   /path
   
   !-- = --
  
  
  

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

[JBoss-dev] CVS update: jboss/src/etc/manifest connector-client-factory.mf deploy.mf ejb-connector-client.mf ejb-connector.mf rmi-adaptor.mf rmi-connector-client.mf stop.mf

2002-03-23 Thread Adrian Brock


  User: ejort   
  Date: 02/03/23 13:11:02

  Modified:src/etc/manifest connector-client-factory.mf deploy.mf
ejb-connector-client.mf ejb-connector.mf
rmi-adaptor.mf rmi-connector-client.mf stop.mf
  Log:
  JBoss/JBossMX integration. Also includes a fix to the cluster tests and a more 
complete ejblink test that currently fails
  
  Revision  ChangesPath
  1.3   +1 -1  jboss/src/etc/manifest/connector-client-factory.mf
  
  Index: connector-client-factory.mf
  ===
  RCS file: /cvsroot/jboss/jboss/src/etc/manifest/connector-client-factory.mf,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- connector-client-factory.mf   17 Feb 2002 08:37:56 -  1.2
  +++ connector-client-factory.mf   23 Mar 2002 21:11:02 -  1.3
  @@ -1,5 +1,5 @@
   Main-Class: org.jboss.jmx.connector.TestClient
  -Class-Path: ./ ./jmx-rmi-connector-client.jar ./jmx-ejb-connector-client.jar 
./jmxri.jar ../lib/jmxri.jar ./jnp-client.jar ../lib/jnp-client.jar ./log4j.jar
  +Class-Path: ./ ./jmx-rmi-connector-client.jar ./jmx-ejb-connector-client.jar 
./jboss-jmx.jar ../lib/jboss-jmx.jar ./jnp-client.jar ../lib/jnp-client.jar ./log4j.jar
   Specification-Title: 
[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@@version.tag@
   Specification-Version: 
@version.major@[EMAIL PROTECTED]@[EMAIL PROTECTED]@@version.tag@
   Specification-Vendor: JBoss Group, LLC
  
  
  
  1.2   +1 -1  jboss/src/etc/manifest/deploy.mf
  
  Index: deploy.mf
  ===
  RCS file: /cvsroot/jboss/jboss/src/etc/manifest/deploy.mf,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- deploy.mf 16 Feb 2002 01:33:26 -  1.1
  +++ deploy.mf 23 Mar 2002 21:11:02 -  1.2
  @@ -1,2 +1,2 @@
   Main-Class: org.jboss.jmx.service.Deployer
  -Class-Path: ./ jnp-client.jar jmxri.jar ../conf/ ../lib/jmxri.jar
  +Class-Path: ./ jnp-client.jar jboss-jmx.jar ../conf/ ../lib/jboss-jmx.jar
  
  
  
  1.4   +1 -1  jboss/src/etc/manifest/ejb-connector-client.mf
  
  Index: ejb-connector-client.mf
  ===
  RCS file: /cvsroot/jboss/jboss/src/etc/manifest/ejb-connector-client.mf,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- ejb-connector-client.mf   17 Feb 2002 09:52:52 -  1.3
  +++ ejb-connector-client.mf   23 Mar 2002 21:11:02 -  1.4
  @@ -1 +1 @@
  -Class-Path: ./ ./jmxri.jar ../lib/jmxri.jar ./jnp-client.jar ./jboss-j2ee.jar 
./jboss-client.jar ./jbossmq-client.jar ./log4j.jar
  +Class-Path: ./ ./jboss-jmx.jar ../lib/jboss-jmx.jar ./jnp-client.jar 
./jboss-j2ee.jar ./jboss-client.jar ./jbossmq-client.jar ./log4j.jar
  
  
  
  1.4   +1 -1  jboss/src/etc/manifest/ejb-connector.mf
  
  Index: ejb-connector.mf
  ===
  RCS file: /cvsroot/jboss/jboss/src/etc/manifest/ejb-connector.mf,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- ejb-connector.mf  17 Feb 2002 09:52:52 -  1.3
  +++ ejb-connector.mf  23 Mar 2002 21:11:02 -  1.4
  @@ -1,2 +1,2 @@
   Main-Class: org.jboss.jmx.connector.ejb.TestClient
  -Class-Path: ./ ../lib/jmxri.jar ./jnp-client.jar ./jboss-j2ee.jar 
./jboss-client.jar ./jbossmq-client.jar ./log4j.jar
  +Class-Path: ./ ../lib/jboss-jmx.jar ./jnp-client.jar ./jboss-j2ee.jar 
./jboss-client.jar ./jbossmq-client.jar ./log4j.jar
  
  
  
  1.3   +1 -1  jboss/src/etc/manifest/rmi-adaptor.mf
  
  Index: rmi-adaptor.mf
  ===
  RCS file: /cvsroot/jboss/jboss/src/etc/manifest/rmi-adaptor.mf,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- rmi-adaptor.mf17 Feb 2002 08:37:56 -  1.2
  +++ rmi-adaptor.mf23 Mar 2002 21:11:02 -  1.3
  @@ -1,5 +1,5 @@
   Main-Class: org.jboss.jmx.connector.rmi.TestServer
  -Class-Path: ./ ./jmxri.jar ../lib/jmxri.jar ./jnpserver.jar 
../lib/ext/jnpserver.jar ./log4j.jar
  +Class-Path: ./ ./jboss-jmx.jar ../lib/jboss-jmx.jar ./jnpserver.jar 
../lib/ext/jnpserver.jar ./log4j.jar
   Specification-Title: 
[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@@version.tag@
   Specification-Version: 
@version.major@[EMAIL PROTECTED]@[EMAIL PROTECTED]@@version.tag@
   Specification-Vendor: JBoss Group, LLC
  
  
  
  1.2   +1 -1  jboss/src/etc/manifest/rmi-connector-client.mf
  
  Index: rmi-connector-client.mf
  ===
  RCS file: /cvsroot/jboss/jboss/src/etc/manifest/rmi-connector-client.mf,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- rmi-connector-client.mf   16 Feb 2002 01:33:26 -  1.1
  +++

[JBoss-dev] CVS update: contrib/jboss.net/testsuite/src/bin testAxis.bat

2002-03-23 Thread Adrian Brock


  User: ejort   
  Date: 02/03/23 13:11:01

  Modified:jboss.net/testsuite/src/bin testAxis.bat
  Log:
  JBoss/JBossMX integration. Also includes a fix to the cluster tests and a more 
complete ejblink test that currently fails
  
  Revision  ChangesPath
  1.2   +1 -1  contrib/jboss.net/testsuite/src/bin/testAxis.bat
  
  Index: testAxis.bat
  ===
  RCS file: /cvsroot/jboss/contrib/jboss.net/testsuite/src/bin/testAxis.bat,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- testAxis.bat  7 Oct 2001 20:06:11 -   1.1
  +++ testAxis.bat  23 Mar 2002 21:11:01 -  1.2
  @@ -1,4 +1,4 @@
  -set 
JBOSS_CLASSPATH=.;%JBOSS_CLASSPATH%;..\lib\ext\axis.jar;..\lib\ext\log4j.jar;..\deploy\lib\jbossdotnet.sar;..\lib\crimson.jar;..\lib\jmxri.jar
  +set 
JBOSS_CLASSPATH=.;%JBOSS_CLASSPATH%;..\lib\axis.jar;..\lib\log4j.jar;..\server\default\deploy\jbossdotnet.sar;..\lib\crimson.jar;..\lib\jboss-jmx.jar
   
   java -classpath %JBOSS_CLASSPATH% org.jboss.net.axis.AxisInvocationHandler 
http://localhost:8080/axis/services  
   java -classpath %JBOSS_CLASSPATH% org.jboss.net.jmx.MBeanInvocationHandler 
http://localhost:8080/axis/services 
  
  
  

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

[JBoss-dev] CVS update: contrib/jetty build.xml

2002-03-23 Thread Adrian Brock


  User: ejort   
  Date: 02/03/23 13:11:01

  Modified:jettybuild.xml
  Log:
  JBoss/JBossMX integration. Also includes a fix to the cluster tests and a more 
complete ejblink test that currently fails
  
  Revision  ChangesPath
  1.47  +8 -8  contrib/jetty/build.xml
  
  Index: build.xml
  ===
  RCS file: /cvsroot/jboss/contrib/jetty/build.xml,v
  retrieving revision 1.46
  retrieving revision 1.47
  diff -u -r1.46 -r1.47
  --- build.xml 16 Mar 2002 01:27:21 -  1.46
  +++ build.xml 23 Mar 2002 21:11:01 -  1.47
  @@ -76,13 +76,6 @@
 pathelement path=${sun.jndi.lib}/jndi.jar/
   /path
   
  -!-- Java Management Extensions (JMX) --
  -property name=sun.jmx.root value=${project.thirdparty}/sun/jmx/
  -property name=sun.jmx.lib value=${sun.jmx.root}/lib/
  -path id=sun.jmx.classpath
  -  pathelement path=${sun.jmx.lib}/jmxri.jar/
  -/path
  -
   !-- Java API for XML Processing (JAXP) --
   property name=sun.jaxp.root value=${project.thirdparty}/sun/jaxp/
   property name=sun.jaxp.lib value=${sun.jaxp.root}/lib/
  @@ -143,7 +136,6 @@
   !-- The combined library classpath --
   path id=library.classpath
 path refid=sun.jndi.classpath/
  -  path refid=sun.jmx.classpath/
 path refid=sun.jaxp.classpath/
 path refid=sun.jaas.classpath/
 path refid=sun.jsse.classpath/
  @@ -184,6 +176,13 @@
 pathelement path=${jboss.server.lib}/jboss.jar/
   /path
   
  +!-- JMX --
  +property name=jboss.jmx.root value=${project.root}/jmx/output/
  +property name=jboss.jmx.lib value=${jboss.jmx.root}/lib/
  +path id=jboss.jmx.classpath
  +  pathelement path=${jboss.jmx.lib}/jboss-jmx.jar/
  +/path
  +
!-- Cluster --
property name=jboss.cluster.root value=${project.root}/cluster/output/
property name=jboss.cluster.lib value=${jboss.cluster.root}/lib/
  @@ -201,6 +200,7 @@
 path refid=jboss.common.classpath/
 path refid=jboss.system.classpath/
 path refid=jboss.server.classpath/
  +  path refid=jboss.jmx.classpath/
 path refid=jboss.cluster.classpath/
   /path
   
  
  
  

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

[JBoss-dev] CVS update: jbosstest/src/main/org/jboss/test/naming/test EjbLinkUnitTestCase.java

2002-03-23 Thread Adrian Brock


  User: ejort   
  Date: 02/03/23 13:11:04

  Modified:src/main/org/jboss/test/naming/test EjbLinkUnitTestCase.java
  Log:
  JBoss/JBossMX integration. Also includes a fix to the cluster tests and a more 
complete ejblink test that currently fails
  
  Revision  ChangesPath
  1.2   +57 -0 
jbosstest/src/main/org/jboss/test/naming/test/EjbLinkUnitTestCase.java
  
  Index: EjbLinkUnitTestCase.java
  ===
  RCS file: 
/cvsroot/jboss/jbosstest/src/main/org/jboss/test/naming/test/EjbLinkUnitTestCase.java,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- EjbLinkUnitTestCase.java  17 Mar 2002 12:56:29 -  1.1
  +++ EjbLinkUnitTestCase.java  23 Mar 2002 21:11:03 -  1.2
  @@ -53,6 +53,63 @@
 bean.remove();
  }
   
  +   /**
  +* Test an ejblink with a relative path
  +*
  +* @exception Exception  Description of Exception
  +*/
  +   public void testEjbLinkRelative() throws Exception
  +   {
  +  Object obj = getInitialContext().lookup(naming/SessionB);
  +  obj = PortableRemoteObject.narrow(obj, TestEjbLinkHome.class);
  +  TestEjbLinkHome home = (TestEjbLinkHome)obj;
  +  getLog().debug(Found naming/SessionB);
  +
  +  TestEjbLink bean = home.create();
  +  getLog().debug(Created the bean);
  +  assertEquals(Works, 
bean.testEjbLinkCaller(java:comp/env/ejb/RelativeSessionA));
  +  getLog().debug(Test succeeded);
  +  bean.remove();
  +   }
  +
  +   /**
  +* Test an ejblink using a local ejb-ref
  +*
  +* @exception Exception  Description of Exception
  +*/
  +   public void testEjbLinkLocalNamed() throws Exception
  +   {
  +  Object obj = getInitialContext().lookup(naming/SessionB);
  +  obj = PortableRemoteObject.narrow(obj, TestEjbLinkHome.class);
  +  TestEjbLinkHome home = (TestEjbLinkHome)obj;
  +  getLog().debug(Found naming/SessionB);
  +
  +  TestEjbLink bean = home.create();
  +  getLog().debug(Created the bean);
  +  assertEquals(Works, 
bean.testEjbLinkCallerLocal(java:comp/env/ejb/LocalSessionA));
  +  getLog().debug(Test succeeded);
  +  bean.remove();
  +   }
  +
  +   /**
  +* Test an ejblink using a local ejb-ref with a relative path
  +*
  +* @exception Exception  Description of Exception
  +*/
  +   public void testEjbLinkLocalRelative() throws Exception
  +   {
  +  Object obj = getInitialContext().lookup(naming/SessionB);
  +  obj = PortableRemoteObject.narrow(obj, TestEjbLinkHome.class);
  +  TestEjbLinkHome home = (TestEjbLinkHome)obj;
  +  getLog().debug(Found naming/SessionB);
  +
  +  TestEjbLink bean = home.create();
  +  getLog().debug(Created the bean);
  +  assertEquals(Works, 
bean.testEjbLinkCallerLocal(java:comp/env/ejb/LocalRelativeSessionA));
  +  getLog().debug(Test succeeded);
  +  bean.remove();
  +   }
  +
  public static Test suite() throws Exception
  {
 return getDeploySetup(EjbLinkUnitTestCase.class, naming.ear);
  
  
  

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

[JBoss-dev] CVS update: build/jboss build.xml

2002-03-23 Thread Adrian Brock


  User: ejort   
  Date: 02/03/23 13:10:59

  Modified:jbossbuild.xml
  Log:
  JBoss/JBossMX integration. Also includes a fix to the cluster tests and a more 
complete ejblink test that currently fails
  
  Revision  ChangesPath
  1.111 +14 -21build/jboss/build.xml
  
  Index: build.xml
  ===
  RCS file: /cvsroot/jboss/build/jboss/build.xml,v
  retrieving revision 1.110
  retrieving revision 1.111
  diff -u -r1.110 -r1.111
  --- build.xml 12 Mar 2002 10:55:19 -  1.110
  +++ build.xml 23 Mar 2002 21:10:59 -  1.111
  @@ -12,7 +12,7 @@
   !----
   !-- == --
   
  -!-- $Id: build.xml,v 1.110 2002/03/12 10:55:19 cgjung Exp $ --
  +!-- $Id: build.xml,v 1.111 2002/03/23 21:10:59 ejort Exp $ --
   
   project default=main name=JBoss/Build
   
  @@ -175,12 +175,12 @@
   
 !-- Modules --
   
  +  module name=jmx/
 module name=j2ee/
 module name=common/
 module name=system/
 module name=ejb/
 module name=naming/
  -  module name=jmx/
 module name=management/
 module name=server/
 module name=security/
  @@ -199,7 +199,7 @@
 !-- Module groups --
   
 group name=core
  -include modules=common, system/
  +include modules=jmx, common, system/
 /group
   
 group name=basic
  @@ -211,11 +211,10 @@
   
 group name=standard
   include modules=security,
  -  jmx,
 messaging,
 pool, 
 connector,
  -   cluster,
  +  cluster,
 admin,
 jetty,
 varia/
  @@ -415,6 +414,8 @@
   include name=crimson.jar/
   include name=xalan.jar/
 /fileset
  +
  +  !-- FIXME This should go away when we have our own html adaptor --
 fileset dir=${sun.jmx.lib}
   include name=jmxri.jar/
   include name=jmxtools.jar/
  @@ -926,7 +927,14 @@
   property name=_module.output override=true
  value=${project.root}/${_module.name}/output/
   
  -!-- TODO Install --
  +!-- Copy the generated libraries --
  +mkdir dir=${install.lib}/
  +copy todir=${install.lib} filtering=no
  +  fileset dir=${_module.output}/lib
  + include name=jboss-jmx-core.jar/
  + include name=jboss-jmx-services.jar/
  +  /fileset
  +/copy
   
 /target
   
  @@ -1313,21 +1321,6 @@
include name=jboss-jsr77.jar/
 /fileset
   /copy
  -
  -!-- Copy thirdparty code --
  -!-- FIXME
  -copy todir=${install.lib} filtering=no
  -  fileset dir=${sun.jaxp.lib}
  -include name=jaxp.jar/
  -include name=crimson.jar/
  -include name=xalan.jar/
  -  /fileset
  -  fileset dir=${sun.jmx.lib}
  -include name=jmxri.jar/
  -include name=jmxtools.jar/
  -  /fileset
  -/copy
  ---
 /target
   
 target name=_module-management-all depends=_module-management-most
  
  
  

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

[JBoss-dev] CVS update: jboss-system build.xml

2002-03-23 Thread Adrian Brock


  User: ejort   
  Date: 02/03/23 13:11:03

  Modified:.build.xml
  Log:
  JBoss/JBossMX integration. Also includes a fix to the cluster tests and a more 
complete ejblink test that currently fails
  
  Revision  ChangesPath
  1.9   +9 -9  jboss-system/build.xml
  
  Index: build.xml
  ===
  RCS file: /cvsroot/jboss/jboss-system/build.xml,v
  retrieving revision 1.8
  retrieving revision 1.9
  diff -u -r1.8 -r1.9
  --- build.xml 5 Mar 2002 05:35:38 -   1.8
  +++ build.xml 23 Mar 2002 21:11:03 -  1.9
  @@ -12,7 +12,7 @@
   !----
   !-- == --
   
  -!-- $Id: build.xml,v 1.8 2002/03/05 05:35:38 d_jencks Exp $ --
  +!-- $Id: build.xml,v 1.9 2002/03/23 21:11:03 ejort Exp $ --
   
   project default=main name=JBoss/System
   
  @@ -69,13 +69,6 @@
   !-- Libraries --
   !-- = --
   
  -!-- Java Management Extensions (JMX) --
  -property name=sun.jmx.root value=${project.thirdparty}/sun/jmx/
  -property name=sun.jmx.lib value=${sun.jmx.root}/lib/
  -path id=sun.jmx.classpath
  -  pathelement path=${sun.jmx.lib}/jmxri.jar/
  -/path
  -
   !-- Java API for XML Processing (JAXP) --
   property name=sun.jaxp.root value=${project.thirdparty}/sun/jaxp/
   property name=sun.jaxp.lib value=${sun.jaxp.root}/lib/
  @@ -110,7 +103,6 @@
   
   !-- The combined library classpath --
   path id=library.classpath
  -  path refid=sun.jmx.classpath/
 path refid=sun.jaxp.classpath/
 path refid=gnu.getopt.classpath/
 path refid=apache.log4j.classpath/
  @@ -127,9 +119,17 @@
 pathelement path=${jboss.common.lib}/jboss-common.jar/
   /path
   
  +!-- JMX --
  +property name=jboss.jmx.root value=${project.root}/jmx/output/
  +property name=jboss.jmx.lib value=${jboss.jmx.root}/lib/
  +path id=jboss.jmx.classpath
  +  pathelement path=${jboss.jmx.lib}/jboss-jmx.jar/
  +/path
  +
   !-- The combined dependant module classpath --
   path id=dependentmodule.classpath
 path refid=jboss.common.classpath/
  +  path refid=jboss.jmx.classpath/
   /path
   
   !-- = --
  
  
  

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

[JBoss-dev] CVS update: jbosspool build.xml

2002-03-23 Thread Adrian Brock


  User: ejort   
  Date: 02/03/23 13:11:02

  Modified:.build.xml
  Log:
  JBoss/JBossMX integration. Also includes a fix to the cluster tests and a more 
complete ejblink test that currently fails
  
  Revision  ChangesPath
  1.22  +9 -9  jbosspool/build.xml
  
  Index: build.xml
  ===
  RCS file: /cvsroot/jboss/jbosspool/build.xml,v
  retrieving revision 1.21
  retrieving revision 1.22
  diff -u -r1.21 -r1.22
  --- build.xml 9 Mar 2002 02:45:34 -   1.21
  +++ build.xml 23 Mar 2002 21:11:02 -  1.22
  @@ -12,7 +12,7 @@
   !----
   !-- == --
   
  -!-- $Id: build.xml,v 1.21 2002/03/09 02:45:34 user57 Exp $ --
  +!-- $Id: build.xml,v 1.22 2002/03/23 21:11:02 ejort Exp $ --
   
   project default=main name=JBoss/Pool
   
  @@ -69,13 +69,6 @@
   !-- Libraries --
   !-- = --
   
  -!-- Java Management Extensions (JMX) --
  -property name=sun.jmx.root value=${project.thirdparty}/sun/jmx/
  -property name=sun.jmx.lib value=${sun.jmx.root}/lib/
  -path id=sun.jmx.classpath
  -  pathelement path=${sun.jmx.lib}/jmxri.jar/
  -/path
  -
   !-- Java API for XML Processing (JAXP) --
   property name=sun.jaxp.root value=${project.thirdparty}/sun/jaxp/
   property name=sun.jaxp.lib value=${sun.jaxp.root}/lib/
  @@ -108,7 +101,6 @@
   
   !-- The combined library classpath --
   path id=library.classpath
  -  path refid=sun.jmx.classpath/
 path refid=sun.jaxp.classpath/
 path refid=sun.jaas.classpath/
 path refid=apache.log4j.classpath/
  @@ -126,9 +118,17 @@
 pathelement path=${jboss.common.lib}/jboss-common.jar/
   /path
   
  +!-- JMX --
  +property name=jboss.jmx.root value=${project.root}/jmx/output/
  +property name=jboss.jmx.lib value=${jboss.jmx.root}/lib/
  +path id=jboss.jmx.classpath
  +  pathelement path=${jboss.jmx.lib}/jboss-jmx.jar/
  +/path
  +
   !-- The combined depedant module classpath --
   path id=dependentmodule.classpath
 path refid=jboss.common.classpath/
  +  path refid=jboss.jmx.classpath/
   /path
   
   !-- = --
  
  
  

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

[JBoss-dev] CVS update: jbosstest/src/etc manifest.mf

2002-03-23 Thread Adrian Brock


  User: ejort   
  Date: 02/03/23 13:11:03

  Modified:src/etc  manifest.mf
  Log:
  JBoss/JBossMX integration. Also includes a fix to the cluster tests and a more 
complete ejblink test that currently fails
  
  Revision  ChangesPath
  1.2   +1 -1  jbosstest/src/etc/manifest.mf
  
  Index: manifest.mf
  ===
  RCS file: /cvsroot/jboss/jbosstest/src/etc/manifest.mf,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- manifest.mf   27 Aug 2000 09:13:09 -  1.1
  +++ manifest.mf   23 Mar 2002 21:11:03 -  1.2
  @@ -1 +1 @@
  -Class-Path: ejb.jar jnp-client.jar jboss-client.jar jndi.jar jmxri.jar junit.jar 
deploy.jar
  +Class-Path: ejb.jar jnp-client.jar jboss-client.jar jndi.jar jboss-jmx.jar 
junit.jar deploy.jar
  
  
  

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

[JBoss-dev] CVS update: jbossmx/src/main/org/jbossmx/cluster/watchdog/mbean/xmlet XMLetMetaDataNodeProcessor.java

2002-03-23 Thread Adrian Brock


  User: ejort   
  Date: 02/03/23 13:11:00

  Modified:src/main/org/jbossmx/cluster/watchdog/mbean/xmlet
XMLetMetaDataNodeProcessor.java
  Log:
  JBoss/JBossMX integration. Also includes a fix to the cluster tests and a more 
complete ejblink test that currently fails
  
  Revision  ChangesPath
  1.2   +3 -3  
jbossmx/src/main/org/jbossmx/cluster/watchdog/mbean/xmlet/XMLetMetaDataNodeProcessor.java
  
  Index: XMLetMetaDataNodeProcessor.java
  ===
  RCS file: 
/cvsroot/jboss/jbossmx/src/main/org/jbossmx/cluster/watchdog/mbean/xmlet/XMLetMetaDataNodeProcessor.java,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- XMLetMetaDataNodeProcessor.java   10 Apr 2001 20:50:09 -  1.1
  +++ XMLetMetaDataNodeProcessor.java   23 Mar 2002 21:10:59 -  1.2
  @@ -18,6 +18,7 @@
   import org.jbossmx.cluster.watchdog.util.xml.XMLScripter;
   import org.jbossmx.cluster.watchdog.util.xml.XMLScriptException;
   
  +import javax.management.Attribute;
   import javax.management.MBeanServer;
   import javax.management.ObjectInstance;
   import javax.management.ObjectName;
  @@ -64,9 +65,8 @@
   
   MBeanServer mbeanServer = xmlet.getMBeanServer();
   
  -mbeanServer.invoke(new 
ObjectName(MetaDataServiceMBean.OBJECT_NAME), setMetaData,
  -new Object[] {objectNameMetaData},
  -new String[] {ObjectNameMetaData.class.getName()});
  +mbeanServer.setAttribute(new 
ObjectName(MetaDataServiceMBean.OBJECT_NAME), 
  +new Attribute(MetaData, objectNameMetaData));
   }
   catch (Throwable t)
   {
  
  
  

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

[JBoss-dev] CVS update: contrib/catalina build.xml

2002-03-23 Thread Adrian Brock


  User: ejort   
  Date: 02/03/23 13:10:59

  Modified:catalina build.xml
  Log:
  JBoss/JBossMX integration. Also includes a fix to the cluster tests and a more 
complete ejblink test that currently fails
  
  Revision  ChangesPath
  1.12  +9 -9  contrib/catalina/build.xml
  
  Index: build.xml
  ===
  RCS file: /cvsroot/jboss/contrib/catalina/build.xml,v
  retrieving revision 1.11
  retrieving revision 1.12
  diff -u -r1.11 -r1.12
  --- build.xml 28 Feb 2002 04:08:01 -  1.11
  +++ build.xml 23 Mar 2002 21:10:59 -  1.12
  @@ -12,7 +12,7 @@
   !----
   !-- == --
   
  -!-- $Id: build.xml,v 1.11 2002/02/28 04:08:01 user57 Exp $ --
  +!-- $Id: build.xml,v 1.12 2002/03/23 21:10:59 ejort Exp $ --
   
   project default=main name=JBoss/Tomcat-4
   
  @@ -52,13 +52,6 @@
 pathelement path=${sun.jndi.lib}/jndi.jar/
   /path
   
  -!-- Java Management Extensions (JMX) --
  -property name=sun.jmx.root value=${project.thirdparty}/sun/jmx/
  -property name=sun.jmx.lib value=${sun.jmx.root}/lib/
  -path id=sun.jmx.classpath
  -  pathelement path=${sun.jmx.lib}/jmxri.jar/
  -/path
  -
   !-- Java API for XML Processing (JAXP) --
   property name=sun.jaxp.root value=${project.thirdparty}/sun/jaxp/
   property name=sun.jaxp.lib value=${sun.jaxp.root}/lib/
  @@ -101,7 +94,6 @@
   !-- The combined library classpath --
   path id=library.classpath
 path refid=sun.jndi.classpath/
  -  path refid=sun.jmx.classpath/
 path refid=sun.jaxp.classpath/
 path refid=sun.jaas.classpath/
 path refid=sun.jsse.classpath/
  @@ -142,6 +134,13 @@
 pathelement path=${project.root}/security/output/lib/jbosssx.jar/
   /path
   
  +!-- JMX --
  +property name=jboss.jmx.root value=${project.root}/jmx/output/
  +property name=jboss.jmx.lib value=${jboss.jmx.root}/lib/
  +path id=jboss.jmx.classpath
  +  pathelement path=${jboss.jmx.lib}/jboss-jmx.jar/
  +/path
  +
   !-- This corresponds to the tomcat4 dist existing in this module root --
   property name=tomcat.server.root 
value=${module.root}/jakarta-tomcat-4.0.2/
   path id=tomcat.server.classpath
  @@ -158,6 +157,7 @@
 path refid=jboss.system.classpath/
 path refid=jboss.server.classpath/
 path refid=jboss.common.classpath/
  +  path refid=jboss.jmx.classpath/
 path refid=tomcat.server.classpath/
   /path
   
  
  
  

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

[JBoss-dev] CVS update: jbossmx/src/main/org/jbossmx/cluster/watchdog SwapMachines.java

2002-03-23 Thread Adrian Brock


  User: ejort   
  Date: 02/03/23 13:10:59

  Modified:src/main/org/jbossmx/cluster/watchdog SwapMachines.java
  Log:
  JBoss/JBossMX integration. Also includes a fix to the cluster tests and a more 
complete ejblink test that currently fails
  
  Revision  ChangesPath
  1.2   +2 -2  jbossmx/src/main/org/jbossmx/cluster/watchdog/SwapMachines.java
  
  Index: SwapMachines.java
  ===
  RCS file: 
/cvsroot/jboss/jbossmx/src/main/org/jbossmx/cluster/watchdog/SwapMachines.java,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- SwapMachines.java 29 Mar 2001 13:49:30 -  1.1
  +++ SwapMachines.java 23 Mar 2002 21:10:59 -  1.2
  @@ -343,8 +343,8 @@
   //System.out.println(watchdogMachineAgent= + 
watchdogMachineAgent);
   //System.out.println(watchdogObjectName= + 
watchdogObjectName);
   
  -watchedRmiBinding = (String) 
watchdogMachineAgent.invokeMethodOnMBean(
  -watchdogObjectName, getRmiAgentBinding, new Object[0], 
new String[0]);
  +watchedRmiBinding = (String) 
watchdogMachineAgent.getMBeanAttribute(
  +watchdogObjectName, RmiAgentBinding);
   
   //watchedRmiBinding = 
Configuration.getAgentWatcherDetails(rmiAgentBinding)[0];
   
  
  
  

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

[JBoss-dev] CVS update: contrib/iiop build.xml

2002-03-23 Thread Adrian Brock


  User: ejort   
  Date: 02/03/23 13:11:00

  Modified:iiop build.xml
  Log:
  JBoss/JBossMX integration. Also includes a fix to the cluster tests and a more 
complete ejblink test that currently fails
  
  Revision  ChangesPath
  1.10  +9 -9  contrib/iiop/build.xml
  
  Index: build.xml
  ===
  RCS file: /cvsroot/jboss/contrib/iiop/build.xml,v
  retrieving revision 1.9
  retrieving revision 1.10
  diff -u -r1.9 -r1.10
  --- build.xml 15 Mar 2002 22:19:53 -  1.9
  +++ build.xml 23 Mar 2002 21:11:00 -  1.10
  @@ -12,7 +12,7 @@
   !----
   !-- == --
   
  -!-- $Id: build.xml,v 1.9 2002/03/15 22:19:53 reverbel Exp $ --
  +!-- $Id: build.xml,v 1.10 2002/03/23 21:11:00 ejort Exp $ --
   
   project default=main name=JBoss/IIOP
   
  @@ -76,13 +76,6 @@
 pathelement path=${sun.jndi.lib}/jndi.jar/
   /path
   
  -!-- Java Management Extensions (JMX) --
  -property name=sun.jmx.root value=${project.thirdparty}/sun/jmx/
  -property name=sun.jmx.lib value=${sun.jmx.root}/lib/
  -path id=sun.jmx.classpath
  -  pathelement path=${sun.jmx.lib}/jmxri.jar/
  -/path
  -
   !-- Java API for XML Processing (JAXP) --
   property name=sun.jaxp.root value=${project.thirdparty}/sun/jaxp/
   property name=sun.jaxp.lib value=${sun.jaxp.root}/lib/
  @@ -117,7 +110,6 @@
   !-- The combined library classpath --
   path id=library.classpath
 path refid=sun.jndi.classpath/
  -  path refid=sun.jmx.classpath/
 path refid=sun.jaxp.classpath/
 path refid=apache.log4j.classpath/
 path refid=junit.junit.classpath/
  @@ -158,12 +150,20 @@
 pathelement path=${jboss.server.lib}/jboss-util.jar/
   /path
   
  +!-- JMX --
  +property name=jboss.jmx.root value=${project.root}/jmx/output/
  +property name=jboss.jmx.lib value=${jboss.jmx.root}/lib/
  +path id=jboss.jmx.classpath
  +  pathelement path=${jboss.jmx.lib}/jboss-jmx.jar/
  +/path
  +
   !-- The combined dependent module classpath --
   path id=dependentmodule.classpath
 path refid=jboss.j2ee.classpath/
 path refid=jboss.common.classpath/
 path refid=jboss.system.classpath/
 path refid=jboss.server.classpath/
  +  path refid=jboss.jmx.classpath/
   /path
   
   !-- = --
  
  
  

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

[JBoss-dev] CVS update: jboss-common build.xml

2002-03-23 Thread Adrian Brock


  User: ejort   
  Date: 02/03/23 13:11:00

  Modified:.build.xml
  Log:
  JBoss/JBossMX integration. Also includes a fix to the cluster tests and a more 
complete ejblink test that currently fails
  
  Revision  ChangesPath
  1.10  +9 -9  jboss-common/build.xml
  
  Index: build.xml
  ===
  RCS file: /cvsroot/jboss/jboss-common/build.xml,v
  retrieving revision 1.9
  retrieving revision 1.10
  diff -u -r1.9 -r1.10
  --- build.xml 28 Feb 2002 04:08:01 -  1.9
  +++ build.xml 23 Mar 2002 21:11:00 -  1.10
  @@ -12,7 +12,7 @@
   !----
   !-- == --
   
  -!-- $Id: build.xml,v 1.9 2002/02/28 04:08:01 user57 Exp $ --
  +!-- $Id: build.xml,v 1.10 2002/03/23 21:11:00 ejort Exp $ --
   
   project default=main name=JBoss/Common
   
  @@ -69,13 +69,6 @@
   !-- Libraries --
   !-- = --
   
  -!-- Java Management Extensions (JMX) --
  -property name=sun.jmx.root value=${project.thirdparty}/sun/jmx/
  -property name=sun.jmx.lib value=${sun.jmx.root}/lib/
  -path id=sun.jmx.classpath
  -  pathelement path=${sun.jmx.lib}/jmxri.jar/
  -/path
  -
   !-- Java API for XML Processing (JAXP) --
   property name=sun.jaxp.root value=${project.thirdparty}/sun/jaxp/
   property name=sun.jaxp.lib value=${sun.jaxp.root}/lib/
  @@ -101,7 +94,6 @@
   
   !-- The combined library classpath --
   path id=library.classpath
  -  path refid=sun.jmx.classpath/
 path refid=sun.jaxp.classpath/
 path refid=apache.log4j.classpath/
   /path
  @@ -110,8 +102,16 @@
   !-- Modules --
   !-- === --
   
  +!-- JMX --
  +property name=jboss.jmx.root value=${project.root}/jmx/output/
  +property name=jboss.jmx.lib value=${jboss.jmx.root}/lib/
  +path id=jboss.jmx.classpath
  +  pathelement path=${jboss.jmx.lib}/jboss-jmx.jar/
  +/path
  +
   !-- The combined dependent module classpath --
   path id=dependentmodule.classpath
  +  path refid=jboss.jmx.classpath/
   /path
   
   !-- = --
  
  
  

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

[JBoss-dev] CVS update: jboss/src/main/org/jboss/jmx/connector/notification PollingClientNotificationListener.java

2002-03-23 Thread Adrian Brock


  User: ejort   
  Date: 02/03/23 13:11:03

  Modified:src/main/org/jboss/jmx/connector/notification
PollingClientNotificationListener.java
  Log:
  JBoss/JBossMX integration. Also includes a fix to the cluster tests and a more 
complete ejblink test that currently fails
  
  Revision  ChangesPath
  1.3   +2 -4  
jboss/src/main/org/jboss/jmx/connector/notification/PollingClientNotificationListener.java
  
  Index: PollingClientNotificationListener.java
  ===
  RCS file: 
/cvsroot/jboss/jboss/src/main/org/jboss/jmx/connector/notification/PollingClientNotificationListener.java,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- PollingClientNotificationListener.java11 Oct 2001 01:41:59 -  1.2
  +++ PollingClientNotificationListener.java23 Mar 2002 21:11:03 -  1.3
  @@ -60,11 +60,9 @@
 while( true ) {
try {
   try {
  -   List lNotifications = (List) mConnector.invoke(
  +   List lNotifications = (List) mConnector.getAttribute(
 getRemoteListenerName(),
  -  getNotifications,
  -  new Object[] {},
  -  new String[] {}
  +  Notifications
  );
  Iterator i = lNotifications.iterator();
  while( i.hasNext() ) {
  
  
  

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

[JBoss-dev] CVS update: contrib/jboss.net build.xml

2002-03-23 Thread Adrian Brock


  User: ejort   
  Date: 02/03/23 13:11:00

  Modified:jboss.net build.xml
  Log:
  JBoss/JBossMX integration. Also includes a fix to the cluster tests and a more 
complete ejblink test that currently fails
  
  Revision  ChangesPath
  1.18  +9 -9  contrib/jboss.net/build.xml
  
  Index: build.xml
  ===
  RCS file: /cvsroot/jboss/contrib/jboss.net/build.xml,v
  retrieving revision 1.17
  retrieving revision 1.18
  diff -u -r1.17 -r1.18
  --- build.xml 15 Mar 2002 10:04:23 -  1.17
  +++ build.xml 23 Mar 2002 21:11:00 -  1.18
  @@ -12,7 +12,7 @@
   !----
   !-- == --
   
  -!-- $Id: build.xml,v 1.17 2002/03/15 10:04:23 cgjung Exp $ --
  +!-- $Id: build.xml,v 1.18 2002/03/23 21:11:00 ejort Exp $ --
   
   project default=main name=JBoss/JBoss.Net
   
  @@ -69,13 +69,6 @@
   !-- Libraries --
   !-- = --
   
  -!-- Java Management Extensions (JMX) --
  -property name=sun.jmx.root value=${project.thirdparty}/sun/jmx/
  -property name=sun.jmx.lib value=${sun.jmx.root}/lib/
  -path id=sun.jmx.classpath
  -  pathelement path=${sun.jmx.lib}/jmxri.jar/
  -/path
  -
   !-- Java API for XML Processing (JAXP) --
   property name=sun.jaxp.root value=${project.thirdparty}/sun/jaxp/
   property name=sun.jaxp.lib value=${sun.jaxp.root}/lib/
  @@ -131,7 +124,6 @@
   
   !-- The combined library classpath --
   path id=library.classpath
  -  path refid=sun.jmx.classpath/
 path refid=sun.jaxp.classpath/
 path refid=sun.jaas.classpath/
 path refid=sun.servlet.classpath/
  @@ -173,12 +165,20 @@
 pathelement path=${jboss.server.lib}/jboss.jar/
   /path
   
  +!-- JMX --
  +property name=jboss.jmx.root value=${project.root}/jmx/output/
  +property name=jboss.jmx.lib value=${jboss.jmx.root}/lib/
  +path id=jboss.jmx.classpath
  +  pathelement path=${jboss.jmx.lib}/jboss-jmx.jar/
  +/path
  +
   !-- The combined dependent module classpath --
   path id=dependentmodule.classpath
 path refid=jboss.j2ee.classpath/
 path refid=jboss.common.classpath/
 path refid=jboss.system.classpath/
 path refid=jboss.server.classpath/
  +  path refid=jboss.jmx.classpath/
   /path
   
   !-- = --
  
  
  

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

[JBoss-dev] CVS update: jboss build.xml

2002-03-23 Thread Adrian Brock


  User: ejort   
  Date: 02/03/23 13:11:02

  Modified:.build.xml
  Log:
  JBoss/JBossMX integration. Also includes a fix to the cluster tests and a more 
complete ejblink test that currently fails
  
  Revision  ChangesPath
  1.80  +13 -9 jboss/build.xml
  
  Index: build.xml
  ===
  RCS file: /cvsroot/jboss/jboss/build.xml,v
  retrieving revision 1.79
  retrieving revision 1.80
  diff -u -r1.79 -r1.80
  --- build.xml 11 Mar 2002 04:31:34 -  1.79
  +++ build.xml 23 Mar 2002 21:11:02 -  1.80
  @@ -12,7 +12,7 @@
   !----
   !-- == --
   
  -!-- $Id: build.xml,v 1.79 2002/03/11 04:31:34 schaefera Exp $ --
  +!-- $Id: build.xml,v 1.80 2002/03/23 21:11:02 ejort Exp $ --
   
   project default=main name=JBoss/Server
   
  @@ -73,6 +73,10 @@
   property name=sun.javacc.root value=${project.thirdparty}/sun/javacc/
   property name=sun.javacc.lib value=${sun.javacc.root}/lib/
   
  +!-- Java Management Extensions (JMX) --
  +property name=sun.jmx.root value=${project.thirdparty}/sun/jmx/
  +property name=sun.jmx.lib value=${sun.jmx.root}/lib/
  +
   !-- Java Naming and Directory Interface (JNDI) --
   property name=sun.jndi.root value=${project.thirdparty}/sun/jndi/
   property name=sun.jndi.lib value=${sun.jndi.root}/lib/
  @@ -80,13 +84,6 @@
 pathelement path=${sun.jndi.lib}/jndi.jar/
   /path
   
  -!-- Java Management Extensions (JMX) --
  -property name=sun.jmx.root value=${project.thirdparty}/sun/jmx/
  -property name=sun.jmx.lib value=${sun.jmx.root}/lib/
  -path id=sun.jmx.classpath
  -  pathelement path=${sun.jmx.lib}/jmxri.jar/
  -/path
  -
   !-- Java API for XML Processing (JAXP) --
   property name=sun.jaxp.root value=${project.thirdparty}/sun/jaxp/
   property name=sun.jaxp.lib value=${sun.jaxp.root}/lib/
  @@ -175,7 +172,6 @@
   !-- The combined library classpath --
   path id=library.classpath
 path refid=sun.jndi.classpath/
  -  path refid=sun.jmx.classpath/
 path refid=sun.jaxp.classpath/
 path refid=sun.jaas.classpath/
 path refid=sun.jsse.classpath/
  @@ -213,6 +209,13 @@
 pathelement path=${jboss.system.lib}/jboss-system.jar/
   /path
   
  +!-- JMX --
  +property name=jboss.jmx.root value=${project.root}/jmx/output/
  +property name=jboss.jmx.lib value=${jboss.jmx.root}/lib/
  +path id=jboss.jmx.classpath
  +  pathelement path=${jboss.jmx.lib}/jboss-jmx.jar/
  +/path
  +
   !-- Naming --
   property name=jboss.naming.root value=${project.root}/naming/output/
   property name=jboss.naming.lib value=${jboss.naming.root}/lib/
  @@ -233,6 +236,7 @@
 path refid=jboss.j2ee.classpath/
 path refid=jboss.common.classpath/
 path refid=jboss.system.classpath/
  +  path refid=jboss.jmx.classpath/
 path refid=jboss.naming.classpath/
 path refid=jboss.management.classpath/
   /path
  
  
  

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

[JBoss-dev] CVS update: contrib/jboss.net/testsuite build.xml

2002-03-23 Thread Adrian Brock


  User: ejort   
  Date: 02/03/23 13:11:01

  Modified:jboss.net/testsuite build.xml
  Log:
  JBoss/JBossMX integration. Also includes a fix to the cluster tests and a more 
complete ejblink test that currently fails
  
  Revision  ChangesPath
  1.10  +9 -9  contrib/jboss.net/testsuite/build.xml
  
  Index: build.xml
  ===
  RCS file: /cvsroot/jboss/contrib/jboss.net/testsuite/build.xml,v
  retrieving revision 1.9
  retrieving revision 1.10
  diff -u -r1.9 -r1.10
  --- build.xml 12 Mar 2002 11:04:47 -  1.9
  +++ build.xml 23 Mar 2002 21:11:01 -  1.10
  @@ -12,7 +12,7 @@
   !----
   !-- == --
   
  -!-- $Id: build.xml,v 1.9 2002/03/12 11:04:47 cgjung Exp $ --
  +!-- $Id: build.xml,v 1.10 2002/03/23 21:11:01 ejort Exp $ --
   
   project default=main name=JBoss/JBoss.net/TestSuite
   
  @@ -87,13 +87,6 @@
 pathelement path=${sun.jndi.lib}/jndi.jar/
   /path
   
  -!-- Java Management Extensions (JMX) --
  -property name=sun.jmx.root value=${project.thirdparty.local}/sun/jmx/
  -property name=sun.jmx.lib value=${sun.jmx.root}/lib/
  -path id=sun.jmx.classpath
  -  pathelement path=${sun.jmx.lib}/jmxri.jar/
  -/path
  -
   !-- Java API for XML Processing (JAXP) --
   property name=sun.jaxp.root value=${project.thirdparty.local}/sun/jaxp/
   property name=sun.jaxp.lib value=${sun.jaxp.root}/lib/
  @@ -168,7 +161,6 @@
   !-- The combined library classpath --
   path id=library.classpath
 path refid=sun.jndi.classpath/
  -  path refid=sun.jmx.classpath/
 path refid=sun.jaxp.classpath/
 path refid=sun.jaas.classpath/
 path refid=sun.javamail.classpath/
  @@ -208,6 +200,13 @@
 pathelement path=${jboss.server.lib}/deploy.jar/
   /path
   
  +!-- JMX --
  +property name=jboss.jmx.root value=${project.root}/jmx/output/
  +property name=jboss.jmx.lib value=${jboss.jmx.root}/lib/
  +path id=jboss.jmx.classpath
  +  pathelement path=${jboss.jmx.lib}/jboss-jmx.jar/
  +/path
  +
   !-- Messaging --
   property name=jboss.messaging.root 
value=${project.root.local}/messaging/output/
   property name=jboss.messaging.lib value=${jboss.messaging.root}/lib/
  @@ -251,6 +250,7 @@
 path refid=jboss.j2ee.classpath/
 path refid=jboss.naming.classpath/
 path refid=jboss.server.classpath/
  +  path refid=jboss.jmx.classpath/
 path refid=jboss.messaging.classpath/
 path refid=jboss.security.classpath/
 path refid=jboss.cluster.classpath/
  
  
  

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

[JBoss-dev] CVS update: jbosssx build.xml

2002-03-23 Thread Adrian Brock


  User: ejort   
  Date: 02/03/23 13:11:02

  Modified:.build.xml
  Log:
  JBoss/JBossMX integration. Also includes a fix to the cluster tests and a more 
complete ejblink test that currently fails
  
  Revision  ChangesPath
  1.23  +9 -9  jbosssx/build.xml
  
  Index: build.xml
  ===
  RCS file: /cvsroot/jboss/jbosssx/build.xml,v
  retrieving revision 1.22
  retrieving revision 1.23
  diff -u -r1.22 -r1.23
  --- build.xml 13 Mar 2002 08:15:07 -  1.22
  +++ build.xml 23 Mar 2002 21:11:02 -  1.23
  @@ -12,7 +12,7 @@
   !----
   !-- == --
   
  -!-- $Id: build.xml,v 1.22 2002/03/13 08:15:07 starksm Exp $ --
  +!-- $Id: build.xml,v 1.23 2002/03/23 21:11:02 ejort Exp $ --
   
   project default=main name=JBoss/Security
   
  @@ -69,13 +69,6 @@
   !-- Libraries --
   !-- = --
   
  -!-- Java Management Extensions (JMX) --
  -property name=sun.jmx.root value=${project.thirdparty}/sun/jmx/
  -property name=sun.jmx.lib value=${sun.jmx.root}/lib/
  -path id=sun.jmx.classpath
  -  pathelement path=${sun.jmx.lib}/jmxri.jar/
  -/path
  -
   !-- Java API for XML Processing (JAXP) --
   property name=sun.jaxp.root value=${project.thirdparty}/sun/jaxp/
   property name=sun.jaxp.lib value=${sun.jaxp.root}/lib/
  @@ -133,7 +126,6 @@
   
   !-- The combined library classpath --
   path id=library.classpath
  -  path refid=sun.jmx.classpath/
 path refid=sun.jaxp.classpath/
 path refid=sun.jaas.classpath/
 path refid=sun.jsse.classpath/
  @@ -183,6 +175,13 @@
 pathelement path=${jboss.server.lib}/jboss-security.jar/
   /path
   
  +!-- JMX --
  +property name=jboss.jmx.root value=${project.root}/jmx/output/
  +property name=jboss.jmx.lib value=${jboss.jmx.root}/lib/
  +path id=jboss.jmx.classpath
  +  pathelement path=${jboss.jmx.lib}/jboss-jmx.jar/
  +/path
  +
   !-- The combined dependent module classpath --
   path id=dependentmodule.classpath
 path refid=jboss.j2ee.classpath/
  @@ -190,6 +189,7 @@
 path refid=jboss.system.classpath/
 path refid=jboss.naming.classpath/
 path refid=jboss.server.classpath/
  +  path refid=jboss.jmx.classpath/
   /path
   
   !-- = --
  
  
  

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

[JBoss-dev] CVS update: jbossmq build.xml

2002-03-23 Thread Adrian Brock


  User: ejort   
  Date: 02/03/23 13:11:01

  Modified:.build.xml
  Log:
  JBoss/JBossMX integration. Also includes a fix to the cluster tests and a more 
complete ejblink test that currently fails
  
  Revision  ChangesPath
  1.27  +9 -9  jbossmq/build.xml
  
  Index: build.xml
  ===
  RCS file: /cvsroot/jboss/jbossmq/build.xml,v
  retrieving revision 1.26
  retrieving revision 1.27
  diff -u -r1.26 -r1.27
  --- build.xml 6 Mar 2002 21:03:02 -   1.26
  +++ build.xml 23 Mar 2002 21:11:01 -  1.27
  @@ -12,7 +12,7 @@
   !----
   !-- == --
   
  -!-- $Id: build.xml,v 1.26 2002/03/06 21:03:02 chirino Exp $ --
  +!-- $Id: build.xml,v 1.27 2002/03/23 21:11:01 ejort Exp $ --
   
   project default=main name=JBoss/Messaging
   
  @@ -80,13 +80,6 @@
 pathelement path=${sun.jndi.lib}/jndi.jar/
   /path
   
  -!-- Java Management Extensions (JMX) --
  -property name=sun.jmx.root value=${project.thirdparty}/sun/jmx/
  -property name=sun.jmx.lib value=${sun.jmx.root}/lib/
  -path id=sun.jmx.classpath
  -  pathelement path=${sun.jmx.lib}/jmxri.jar/
  -/path
  -
   !-- Java API for XML Processing (JAXP) --
   property name=sun.jaxp.root value=${project.thirdparty}/sun/jaxp/
   property name=sun.jaxp.lib value=${sun.jaxp.root}/lib/
  @@ -134,7 +127,6 @@
   !-- The combined library classpath --
   path id=library.classpath
 path refid=sun.jndi.classpath/
  -  path refid=sun.jmx.classpath/
 path refid=sun.jaxp.classpath/
 path refid=sun.jaas.classpath/
 path refid=apache.log4j.classpath/
  @@ -182,6 +174,13 @@
 pathelement path=${jboss.server.lib}/jboss.jar/
   /path
   
  +!-- JMX --
  +property name=jboss.jmx.root value=${project.root}/jmx/output/
  +property name=jboss.jmx.lib value=${jboss.jmx.root}/lib/
  +path id=jboss.jmx.classpath
  +  pathelement path=${jboss.jmx.lib}/jboss-jmx.jar/
  +/path
  +
   !-- Security --
   property name=jboss.security.root value=${project.root}/security/output/
   property name=jboss.security.lib value=${jboss.security.root}/lib/
  @@ -196,6 +195,7 @@
 path refid=jboss.system.classpath/
 path refid=jboss.naming.classpath/
 path refid=jboss.server.classpath/
  +  path refid=jboss.jmx.classpath/
 path refid=jboss.security.classpath/
   /path
   
  
  
  

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

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

2002-03-23 Thread Adrian Brock


  User: ejort   
  Date: 02/03/23 13:11:03

  Modified:src/main/org/jboss Main.java
  Log:
  JBoss/JBossMX integration. Also includes a fix to the cluster tests and a more 
complete ejblink test that currently fails
  
  Revision  ChangesPath
  1.7   +9 -2  jboss-system/src/main/org/jboss/Main.java
  
  Index: Main.java
  ===
  RCS file: /cvsroot/jboss/jboss-system/src/main/org/jboss/Main.java,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -u -r1.6 -r1.7
  --- Main.java 7 Mar 2002 06:27:43 -   1.6
  +++ Main.java 23 Mar 2002 21:11:03 -  1.7
  @@ -39,9 +39,16 @@
*   ./run.sh -Dlog4j.configuration=log4j-debug.properties
* /pre
*
  + * pbRevisions:/b
  + * pb20020321 Adrian Brock:/b
  + * ul
  + * liUse JBossMX to run JBoss
  + * /ul
  + *
* @author a href=mailto:[EMAIL PROTECTED];Marc Fleury/a
* @author a href=mailto:[EMAIL PROTECTED];Jason Dillon/a
  - * @version $Revision: 1.6 $
  + * @author a href=mailto:[EMAIL PROTECTED];Adrian Brock/a
  + * @version $Revision: 1.7 $
*/
   public class Main
   {
  @@ -49,7 +56,7 @@
  private String jaxpLib = crimson.jar;
   
  /** The JMX library to use. */
  -   private String jmxLib = jmxri.jar;
  +   private String jmxLib = jboss-jmx-core.jar;
   
  /** Extra libraries to load the server with .*/
  private List extraLibraries = new LinkedList();
  
  
  

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

[JBoss-dev] CVS update: jbossmq/src/main/org/jboss/mq/sm/file OldStateManager.java

2002-03-23 Thread Adrian Brock


  User: ejort   
  Date: 02/03/23 13:11:02

  Modified:src/main/org/jboss/mq/sm/file OldStateManager.java
  Log:
  JBoss/JBossMX integration. Also includes a fix to the cluster tests and a more 
complete ejblink test that currently fails
  
  Revision  ChangesPath
  1.2   +1 -8  jbossmq/src/main/org/jboss/mq/sm/file/OldStateManager.java
  
  Index: OldStateManager.java
  ===
  RCS file: /cvsroot/jboss/jbossmq/src/main/org/jboss/mq/sm/file/OldStateManager.java,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- OldStateManager.java  6 Mar 2002 17:27:51 -   1.1
  +++ OldStateManager.java  23 Mar 2002 21:11:01 -  1.2
  @@ -46,7 +46,7 @@
* @author Norbert Lataille ([EMAIL PROTECTED])
* @author a href=[EMAIL PROTECTED]Hiram Chirino/a
* @author a href=mailto:[EMAIL PROTECTED];Peter Antman/a
  - * @version$Revision: 1.1 $
  + * @version$Revision: 1.2 $
*/
   public class OldStateManager
  extends ServiceMBeanSupport
  @@ -425,13 +425,6 @@
  {
   
 loadConfig();
  -
  -  /*JMSServer server = (JMSServer)getServer().invoke(new 
ObjectName(org.jboss.mq.server.JBossMQServiceMBean.OBJECT_NAME), getJMSServer, new 
Object[]{
  -}, new String[]{
  -});*/
  -  //server.setStateManager(this);
  -  //initDurableSubscriptions(server);
  -
  }
   
  public Collection getDurableSubscriptionIdsForTopic(SpyTopic topic)
  
  
  

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

[JBoss-dev] CVS update: jbosstest/src/bin jmx-test.sh

2002-03-23 Thread Adrian Brock


  User: ejort   
  Date: 02/03/23 13:11:03

  Modified:src/bin  jmx-test.sh
  Log:
  JBoss/JBossMX integration. Also includes a fix to the cluster tests and a more 
complete ejblink test that currently fails
  
  Revision  ChangesPath
  1.4   +2 -2  jbosstest/src/bin/jmx-test.sh
  
  Index: jmx-test.sh
  ===
  RCS file: /cvsroot/jboss/jbosstest/src/bin/jmx-test.sh,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- jmx-test.sh   17 Feb 2002 09:52:52 -  1.3
  +++ jmx-test.sh   23 Mar 2002 21:11:03 -  1.4
  @@ -1,11 +1,11 @@
   #! /bin/sh
  -# $Id: jmx-test.sh,v 1.3 2002/02/17 09:52:52 user57 Exp $
  +# $Id: jmx-test.sh,v 1.4 2002/03/23 21:11:03 ejort Exp $
   
   
   TARGET_CLASSPATH=../lib/junit.jar
   
   
  -TARGET_CLASSPATH=$TARGET_CLASSPATH:../lib/jmxri.jar
  +TARGET_CLASSPATH=$TARGET_CLASSPATH:../lib/jboss-jmx.jar
   TARGET_CLASSPATH=$TARGET_CLASSPATH:../lib/jnp-client.jar
   TARGET_CLASSPATH=$TARGET_CLASSPATH:../lib/connector.jar
   TARGET_CLASSPATH=$TARGET_CLASSPATH:../lib/testjmx.jar
  
  
  

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

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

2002-03-23 Thread Adrian Brock


  User: ejort   
  Date: 02/03/23 13:11:03

  Modified:src/main/org/jboss/system/server ServerLoader.java
  Log:
  JBoss/JBossMX integration. Also includes a fix to the cluster tests and a more 
complete ejblink test that currently fails
  
  Revision  ChangesPath
  1.7   +9 -2  jboss-system/src/main/org/jboss/system/server/ServerLoader.java
  
  Index: ServerLoader.java
  ===
  RCS file: 
/cvsroot/jboss/jboss-system/src/main/org/jboss/system/server/ServerLoader.java,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -u -r1.6 -r1.7
  --- ServerLoader.java 27 Feb 2002 09:24:26 -  1.6
  +++ ServerLoader.java 23 Mar 2002 21:11:03 -  1.7
  @@ -33,7 +33,7 @@
*
*// add the jaxp  jmx library to use
*loader.addLibrary(crimson.jar);
  - *loader.addLibrary(jmxri.jar);
  + *loader.addLibrary(jboss-jmx-core.jar);
*
*// load and initialize the server instance
*ClassLoader parent = Thread.currentThread().getContextClassLoader();
  @@ -50,8 +50,15 @@
*server.shutdown();
* /pre
*
  - * @version tt$Revision: 1.6 $/tt
  + * pbRevisions:/b
  + * pb20020321 Adrian Brock:/b
  + * ul
  + * liUse JBossMX to run JBoss
  + * /ul
  + *
  + * @version tt$Revision: 1.7 $/tt
* @author  a href=mailto:[EMAIL PROTECTED];Jason Dillon/a
  + * @author a href=mailto:[EMAIL PROTECTED];Adrian Brock/a
*/
   public class ServerLoader
   {
  
  
  

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

[JBoss-dev] CVS update: jbosstest build.xml

2002-03-23 Thread Adrian Brock


  User: ejort   
  Date: 02/03/23 13:11:03

  Modified:.build.xml
  Log:
  JBoss/JBossMX integration. Also includes a fix to the cluster tests and a more 
complete ejblink test that currently fails
  
  Revision  ChangesPath
  1.96  +13 -108   jbosstest/build.xml
  
  Index: build.xml
  ===
  RCS file: /cvsroot/jboss/jbosstest/build.xml,v
  retrieving revision 1.95
  retrieving revision 1.96
  diff -u -r1.95 -r1.96
  --- build.xml 23 Mar 2002 03:55:08 -  1.95
  +++ build.xml 23 Mar 2002 21:11:03 -  1.96
  @@ -13,22 +13,7 @@
   !----
   !-- == --
   
  -!-- [EMAIL PROTECTED] --
  -!-- TEMPORARY: Until JBossMX is stable the tests are run over JMXRI --
  -!--But for the JBossMX tests to compile we have to build--
  -!--over jboss-jmx.jar and those tests need to run over  --
  -!--that jar.--
  -!-- CHANGES:   The classpaths have changed as follows.  --
  -!-- most.classpath contains all jars except the jmx implementation  --
  -!-- javac.classpath adds jboss-jmx.jar for compilation  --
  -!-- tests.classpath adds jmxri.jar for running the main tests   --
  -!-- tests.jbossmx.classpath adds jboss-jmx.jar for running JBossMX tests--
  -!-- NOTE:  If somebody can think of a cleaner way of doing this --
  -!--please feel free to fix it. But the test --
  -!--tests-jmxri-compliance still needs to run over jmxri.jar --
  -!--the aim of that test is to check our compliance suite.   --
  -
  -!-- $Id: build.xml,v 1.95 2002/03/23 03:55:08 starksm Exp $ --
  +!-- $Id: build.xml,v 1.96 2002/03/23 21:11:03 ejort Exp $ --
   
   project default=main name=JBoss/Testsuite
   
  @@ -92,13 +77,6 @@
 pathelement path=${sun.jndi.lib}/jndi.jar/
   /path
   
  -!-- Java Management Extensions (JMX) --
  -property name=sun.jmx.root value=${project.thirdparty}/sun/jmx/
  -property name=sun.jmx.lib value=${sun.jmx.root}/lib/
  -path id=sun.jmx.classpath
  -  pathelement path=${sun.jmx.lib}/jmxri.jar/
  -/path
  -
   !-- Java API for XML Processing (JAXP) --
   property name=sun.jaxp.root value=${project.thirdparty}/sun/jaxp/
   property name=sun.jaxp.lib value=${sun.jaxp.root}/lib/
  @@ -185,8 +163,6 @@
   !-- The combined library classpath --
   path id=library.classpath
 path refid=sun.jndi.classpath/
  -!-- See comment at start --
  -!--  path refid=sun.jmx.classpath/ --
 path refid=sun.jaxp.classpath/
 path refid=sun.jaas.classpath/
 path refid=sun.jce.classpath/
  @@ -348,41 +324,20 @@
   property name=classpath value=/
   property name=local.classpath value=/
   
  -!-- Class minus JMX implementation see comment at start --
  -path id=most.classpath
  +!-- Classpath to build and run the tests --
  +path id=tests.classpath
 pathelement path=${classpath}/
 pathelement path=${local.classpath}/
 pathelement path=${project.tools}/lib/ant.jar/
 pathelement path=${project.tools}/lib/junit.jar/
 pathelement path=${project.tools}/lib/optional.jar/
  -  path refid=thirdparty.classpath/
  -/path
  -
  -!-- The classpath required to build classes. --
  -!-- Used for building see comment at start --
  -path id=javac.classpath
  -  path refid=most.classpath/
 path refid=jboss.jmx.classpath/
  -/path
  -
  -!-- The classpath required to run tests classes. --
  -!-- Run over JMXRI see comment at start --
  -path id=tests.classpath
  -  path refid=most.classpath/
  -  path refid=sun.jmx.classpath/
  -/path
  -
  -!-- The classpath required to run tests for JBossMX classes. --
  -!-- Run over JBossMX see comment at start --
  -path id=tests.jbossmx.classpath
  -  path refid=most.classpath/
  -  path refid=jboss.jmx.classpath/
  -  pathelement path=${jboss.server.lib}/jboss.jar/
  +  path refid=thirdparty.classpath/
   /path
   
   !-- The classpath required to build javadocs. --
   path id=javadoc.classpath
  -  path refid=javac.classpath/
  +  path refid=tests.classpath/
   /path
   
   !-- Packages to include when generating api documentation --
  @@ -404,7 +359,7 @@
   
   !-- xdoclet --
   path id=xdoclet.task.classpath
  -  path refid=javac.classpath/
  +  path refid=tests.classpath/
 pathelement location=${project.tools}/lib/xdoclet.jar/
 pathelement location=${project.tools}/lib/ant.jar/
   /path
  @@ -629,7 +584,7 @@
   failonerror=${javac.fail.onerror}

[JBoss-dev] CVS update: jbosstest/src/resources/naming/ear/b/META-INF ejb-jar.xml

2002-03-23 Thread Adrian Brock


  User: ejort   
  Date: 02/03/23 13:11:04

  Modified:src/resources/naming/ear/b/META-INF ejb-jar.xml
  Log:
  JBoss/JBossMX integration. Also includes a fix to the cluster tests and a more 
complete ejblink test that currently fails
  
  Revision  ChangesPath
  1.2   +21 -0 jbosstest/src/resources/naming/ear/b/META-INF/ejb-jar.xml
  
  Index: ejb-jar.xml
  ===
  RCS file: /cvsroot/jboss/jbosstest/src/resources/naming/ear/b/META-INF/ejb-jar.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- ejb-jar.xml   17 Mar 2002 12:56:30 -  1.1
  +++ ejb-jar.xml   23 Mar 2002 21:11:04 -  1.2
  @@ -17,6 +17,27 @@
   remoteorg.jboss.test.naming.interfaces.TestEjbLink/remote 
   ejb-linkSessionA/ejb-link
 /ejb-ref
  +  ejb-local-ref
  +ejb-ref-nameejb/LocalSessionA/ejb-ref-name
  +ejb-ref-typeSession/ejb-ref-type
  +
local-homeorg.jboss.test.naming.interfaces.TestEjbLinkLocalHome/local-home
  +localorg.jboss.test.naming.interfaces.TestEjbLinkLocal/local 
  +ejb-linkSessionA/ejb-link
  +  /ejb-local-ref
  +  ejb-ref
  +ejb-ref-nameejb/RelativeSessionA/ejb-ref-name
  +ejb-ref-typeSession/ejb-ref-type
  +homeorg.jboss.test.naming.interfaces.TestEjbLinkHome/home
  +remoteorg.jboss.test.naming.interfaces.TestEjbLink/remote 
  +ejb-link../subdir/naminga.jar#SessionA/ejb-link
  +  /ejb-ref
  +  ejb-local-ref
  +ejb-ref-nameejb/LocalRelativeSessionA/ejb-ref-name
  +ejb-ref-typeSession/ejb-ref-type
  +
local-homeorg.jboss.test.naming.interfaces.TestEjbLinkLocalHome/local-home
  +localorg.jboss.test.naming.interfaces.TestEjbLinkLocal/local 
  +ejb-link../subdir/naminga.jar#SessionA/ejb-link
  +  /ejb-local-ref
   /session
 /enterprise-beans
   /ejb-jar
  
  
  

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

[JBoss-dev] CVS update: contrib/varia build.xml

2002-03-23 Thread Adrian Brock


  User: ejort   
  Date: 02/03/23 13:11:04

  Modified:variabuild.xml
  Log:
  JBoss/JBossMX integration. Also includes a fix to the cluster tests and a more 
complete ejblink test that currently fails
  
  Revision  ChangesPath
  1.27  +9 -9  contrib/varia/build.xml
  
  Index: build.xml
  ===
  RCS file: /cvsroot/jboss/contrib/varia/build.xml,v
  retrieving revision 1.26
  retrieving revision 1.27
  diff -u -r1.26 -r1.27
  --- build.xml 11 Mar 2002 04:31:35 -  1.26
  +++ build.xml 23 Mar 2002 21:11:04 -  1.27
  @@ -12,7 +12,7 @@
   !----
   !-- == --
   
  -!-- $Id: build.xml,v 1.26 2002/03/11 04:31:35 schaefera Exp $ --
  +!-- $Id: build.xml,v 1.27 2002/03/23 21:11:04 ejort Exp $ --
   
   project default=main name=JBoss/Varia
   
  @@ -76,13 +76,6 @@
 pathelement path=${sun.jndi.lib}/jndi.jar/
   /path
   
  -!-- Java Management Extensions (JMX) --
  -property name=sun.jmx.root value=${project.thirdparty}/sun/jmx/
  -property name=sun.jmx.lib value=${sun.jmx.root}/lib/
  -path id=sun.jmx.classpath
  -  pathelement path=${sun.jmx.lib}/jmxri.jar/
  -/path
  -
   !-- Java API for XML Processing (JAXP) --
   property name=sun.jaxp.root value=${project.thirdparty}/sun/jaxp/
   property name=sun.jaxp.lib value=${sun.jaxp.root}/lib/
  @@ -188,7 +181,6 @@
   !-- The combined library classpath --
   path id=library.classpath
 path refid=sun.jndi.classpath/
  -  path refid=sun.jmx.classpath/
 path refid=sun.jaxp.classpath/
 path refid=sun.jaas.classpath/
 path refid=sun.jaf.classpath/
  @@ -228,6 +220,13 @@
 pathelement path=${jboss.system.lib}/jboss-system.jar/
   /path
   
  +!-- JMX --
  +property name=jboss.jmx.root value=${project.root}/jmx/output/
  +property name=jboss.jmx.lib value=${jboss.jmx.root}/lib/
  +path id=jboss.jmx.classpath
  +  pathelement path=${jboss.jmx.lib}/jboss-jmx.jar/
  +/path
  +
   !-- Naming --
   property name=jboss.naming.root value=${project.root}/naming/output/
   property name=jboss.naming.lib value=${jboss.naming.root}/lib/
  @@ -255,6 +254,7 @@
 path refid=jboss.j2ee.classpath/
 path refid=jboss.common.classpath/
 path refid=jboss.system.classpath/
  +  path refid=jboss.jmx.classpath/
 path refid=jboss.naming.classpath/
 path refid=jboss.server.classpath/
 path refid=jboss.management.classpath/
  
  
  

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

[JBoss-dev] java.nio

2002-03-23 Thread James Cook


What will JDK 1.4's non-blocking i/o do for the scalability of a single
machine when the appserver takes full advantage?



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

[JBoss-dev] JBossMX and JBoss

2002-03-23 Thread Adrian Brock


Ok,

JBoss now builds and runs with JBossMX.

I'll post other issues in different threads. Sorry for
the mail bombing, but I hate interlocking threads with
5 or 6 different topics.

Since I'm posting from the forums, my direct mail
address for any problems is
[EMAIL PROTECTED]

any means jbossmx integration problems :-)

Regards,
Adrian
_
View thread online: http://main.jboss.org/thread.jsp?forum=66thread=11474

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

[JBoss-dev] Clustering and JBossMX integration

2002-03-23 Thread Adrian Brock


Hi,

I fixed the clustering tests that weren't deploying.

I've also made a few mods where MBeanServer.invoke()
was used to get/set attributes.

I don't know enough to test this properly.
I did cluster my Windows laptop and my Linux desktop
using the bean from the testsuite.
Cool stuff guys!

Regards,
Adrian
_
View thread online: http://main.jboss.org/thread.jsp?forum=66thread=11475

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

RE: [JBoss-dev] JBoss and Apache

2002-03-23 Thread marc fleury


Hey,

|Apache's stated mission is to foster collaborative development and
|distribution of open-source software. JBoss Group has shown impressive
|technical capability and more importantly the ability to work and
|collaborate as a team.  Consequently, I believe that JBoss could be an
|excellent addition to Apache.

Thanks we have a ton of respect for Apache,

|I am willing to work in order to sort out the details. However, it
|won't happen
|without willingness on your part. Is this a venue you wish to explore?

The interview states very clearly where I stand...

The Apache Foundation model is incompatible with our professional vision. I
view the ASF as a failure of the open source business model.  I view Linux
as an even bigger failure of the open source business model, so you see...
:).

We want to grow the JBoss Group as an umbrella for all JBoss developers to
offer professional services, it is already on.  In Apache this is lost, it's
not the model.

We are about promoting our way of life and I don't want to be employee of
the month

Take care,

marcf


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

RE: [JBoss-dev] JBossMX and JBoss

2002-03-23 Thread marc fleury


And for the thousands fucking time please send me your BIO and picture for
the site

PLEASE! it's been what... 2 month?

come'on you earned it already!

marcf

|-Original Message-
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of
|Adrian Brock
|Sent: Saturday, March 23, 2002 1:57 PM
|To: [EMAIL PROTECTED]
|Subject: [JBoss-dev] JBossMX and JBoss
|
|
|Ok,
|
|JBoss now builds and runs with JBossMX.
|
|I'll post other issues in different threads. Sorry for
|the mail bombing, but I hate interlocking threads with
|5 or 6 different topics.
|
|Since I'm posting from the forums, my direct mail
|address for any problems is
|[EMAIL PROTECTED]
|
|any means jbossmx integration problems :-)
|
|Regards,
|Adrian
|_
|View thread online: http://main.jboss.org/thread.jsp?forum=66thread=11474
|
|___
|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] JBoss.net/IIOP and JBossMX integration

2002-03-23 Thread Adrian Brock


Hi,

I've changed these modules to build with jbossmx.
Let me know if there are any problems.

I also changed a .bat test program in axis that looked
like they hadn't been modified since the alpha.

Regards,
Adrian
_
View thread online: http://main.jboss.org/thread.jsp?forum=66thread=11476

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

[JBoss-dev] JBossMX - Core/Kernel

2002-03-23 Thread Adrian Brock


So far I've split out the basic jmx services.

There's plenty of other bits I can move from
core to services, e.g. QueryExp
It just needs some testing and maybe some minor code
changes.

If we really wanted to provide a minimal kernel,
Standard and ModelMBeans are really services
on top of the DynamicMBean core. But that's probably
not relevent to most users of JMX

Regards,
Adrian
_
View thread online: http://main.jboss.org/thread.jsp?forum=66thread=11478

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

[JBoss-dev] JBossMX - Features

2002-03-23 Thread Adrian Brock


Hi,

There are couple of features that JBoss could use.

1) UnifiedLoaderRepository.
2) BCEL compilation of Standard MBeans to get near
Dynamic MBean performance.

It is probably best to speak to Juha about these.

Regards,
Adrian
_
View thread online: http://main.jboss.org/thread.jsp?forum=66thread=11479

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

RE: [JBoss-dev] JBossMX - Features

2002-03-23 Thread marc fleury


|1) UnifiedLoaderRepository.

We will do that at Tahoe,

|2) BCEL compilation of Standard MBeans to get near
|Dynamic MBean performance.

ummm I think we could use it in the invocation chain to call the target,
this way we would speed up the invocation chain on JDK1.3.  Supposedly
JDK1.4 has an optimized invocation chain anyway sooo...

marcf

|
|It is probably best to speak to Juha about these.
|
|Regards,
|Adrian
|_
|View thread online: http://main.jboss.org/thread.jsp?forum=66thread=11479
|
|___
|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] JBoss and Apache

2002-03-23 Thread Ceki Gülcü


At 14:02 23.03.2002 -0800, marc fleury wrote:
The interview states very clearly where I stand...

Actually, your comments in the interview came though like an unwarranted
attack against Jakarta whereas now your concern seems to be focused on the
business model which is a very legitimate concern.

The Apache Foundation model is incompatible with our professional vision. I
view the ASF as a failure of the open source business model.  I view Linux
as an even bigger failure of the open source business model, so you see...
:).

Apache is rather big, Linux is even bigger. So characterizing Apache or Linux
as one big flop is inaccurate. I don't think Apache is about financial 
success.
We measure success by a different yardstick. I would even adventure to say
that we don't really measure it.

We want to grow the JBoss Group as an umbrella for all JBoss developers to
offer professional services, it is already on.  In Apache this is lost, it's
not the model.

Why do you think you couldn't pursue the same goals within Apache? What is
there to prevent you?

We are about promoting our way of life and I don't want to be employee of
the month

You can promote your way of life at Apache. The foundation takes great 
pride in
not intervening in any project's internal affairs. That is how the 
foundation scales.

Thanks for your time,


--
Ceki
My link of the month: http://java.sun.com/aboutJava/standardization/


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

[JBoss-dev] JBossMX and JBossMQ standalone

2002-03-23 Thread Adrian Brock


There is a standalone checkout of JBossMQ that is
still using jmxri.jar

Part of the reason for doing the integration is to stop
developers using invoke() to get/set attributes.
Something that should never have been allowed and will be
stopped in the RI from JMX1.1

I can modify this, but it means modifying CVSROOT/modules
to include the jmx module.

I can do this, but should I?

Regards,
Adrian
_
View thread online: http://main.jboss.org/thread.jsp?forum=66thread=11480

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

Re: RE: [JBoss-dev] JBossMX - Features

2002-03-23 Thread Adrian Brock


 |1) UnifiedLoaderRepository.
 
 We will do that at Tahoe,
 
 |2) BCEL compilation of Standard MBeans to get near
 |Dynamic MBean performance.
 
 ummm I think we could use it in the invocation chain
 to call the target,
 this way we would speed up the invocation chain on
 JDK1.3.  Supposedly
 JDK1.4 has an optimized invocation chain anyway
 sooo...

It has been optimized, but...
Look at these links

http://main.jboss.org/thread.jsp?forum=63thread=8590
http://main.jboss.org/thread.jsp?forum=63thread=9047

 
 marcf
 
 |
 |It is probably best to speak to Juha about these.
 |
 |Regards,
 |Adrian
 |_
 ___
 |View thread online:
 http://main.jboss.org/thread.jsp?forum=66thread=11479
 |
 |___
 |Jboss-development mailing list
 |[EMAIL PROTECTED]
 |https://lists.sourceforge.net/lists/listinfo/jboss-de
 elopment
 
 
 ___
 Jboss-development mailing list
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/jboss-dev
 lopment

Regards,
Adrian
_
View thread online: http://main.jboss.org/thread.jsp?forum=66thread=11479

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

Re: RE: [JBoss-dev] JBossMX and JBoss

2002-03-23 Thread Adrian Brock


 And for the thousands fucking time please send me
 your BIO and picture for
 the site
 
 PLEASE! it's been what... 2 month?

I suppose you don't want to hear it is the only
outstanding item in my e-mails ;-)

I'm tempted to send you a Silhouette with a ?

PS. England thrashed Wales, but it looks like France
are going to win the Grand Slam, they easily beat
Scotland.

Regards,
Adrian

 
 come'on you earned it already!
 
 marcf
 
 |-Original Message-
 |From: [EMAIL PROTECTED]
 |[mailto:[EMAIL PROTECTED]
 On Behalf Of
 |Adrian Brock
 |Sent: Saturday, March 23, 2002 1:57 PM
 |To: [EMAIL PROTECTED]
 |Subject: [JBoss-dev] JBossMX and JBoss
 |
 |
 |Ok,
 |
 |JBoss now builds and runs with JBossMX.
 |
 |I'll post other issues in different threads. Sorry
 for
 |the mail bombing, but I hate interlocking threads
 with
 |5 or 6 different topics.
 |
 |Since I'm posting from the forums, my direct mail
 |address for any problems is
 |[EMAIL PROTECTED]
 |
 |any means jbossmx integration problems :-)
 |
 |Regards,
 |Adrian
 |_
 ___
 |View thread online:
 http://main.jboss.org/thread.jsp?forum=66thread=11474
 |
 |___
 |Jboss-development mailing list
 |[EMAIL PROTECTED]
 |https://lists.sourceforge.net/lists/listinfo/jboss-de
 elopment
 
 
 ___
 Jboss-development mailing list
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/jboss-dev
 lopment


_
View thread online: http://main.jboss.org/thread.jsp?forum=66thread=11474

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

RE: [JBoss-dev] JBoss and Apache

2002-03-23 Thread marc fleury


|The interview states very clearly where I stand...
|
|Actually, your comments in the interview came though like an unwarranted
|attack against Jakarta whereas now your concern seems to be focused on the
|business model which is a very legitimate concern.

I am sorry if the interview ruffled some feathers. My intention was not to
attack Jakarta. It was simply to state my view that JBoss Group and Jakarta
have different agendas. JBoss Group does not aspire to be a non-profit
organization. We actually want to pay for J2EE certification. Also, we are
extremely protective of our independence. My feeling is that IBM is calling
the shots at Apache right now. The JBoss LGPL license and JBoss Group brand
are an important part of our business, as is our independence from larger
organizations.

|The Apache Foundation model is incompatible with our professional
|vision. I
|view the ASF as a failure of the open source business model.  I view Linux
|as an even bigger failure of the open source business model, so you see...
|:).
|
|Apache is rather big, Linux is even bigger. So characterizing
|Apache or Linux
|as one big flop is inaccurate. I don't think Apache is about financial
|success.
|We measure success by a different yardstick. I would even adventure to say
|that we don't really measure it.

I never called Apache a flop. I only stated my opinion that it's not
independent developers calling the shots, but IBM and to a lesser degree
Sun. Apache is a big success from an open source standpoint, Linux is king
in that category.  But we want to move beyond simple open source success.
We want a business model that favors the developers in the group.  By this
measure, the business of Linux is small, the developers are in their corner,
the Linux distrubtors in another.  Apache... httpd? as a protitable market?
Financially, it's been victimized by its own success. There's no way to make
an independent living out of it. If that's what you and the Apache guys
want, that's fine. It's just not what we want for JBoss.  J2EE is a
different beast altogether.  Everyone says Open Source needs services as a
b-model, well J2EE is an inherently rich deep integration field.  We want to
be a player in it. We feel, it is only by earning money that we can achieve
our independence and we simply would rather deal with clients than donors.
Fact is that there's no free lunch. You're going to have to serve
somebody--in the words of Bob Dylan. We want to choose who we serve and
how.

We are about commoditizing the appserver and getting paid as developers. The
major thrust of corporate software is about pursuing the reverse,
commoditize the developer and make people pay through the nose for the
software.

JBoss Group is the professional umbrella for a core group of developers and
affiliates.

|Why do you think you couldn't pursue the same goals within Apache? What is
|there to prevent you?

See above: it's about maintaining independence vis a vis other corporations
and being able to choose the license we want. It's about the JBoss Group
brand and benefiting the JBoss developers. Furthermore, right now Apache is
not a J2EE play. You have excellent software (your own log4J, XML parsers,
ANT, etc.), but when it comes to J2EE you only have 20%, with Tomcat JSP
servlet spec (done by Sun). We already implement the other 80% (EJB, JMS,
JCA, JMX, etc). With Jetty, we have the full stack, including HTTPD.

We respect your work and philosophy. There's room for difference.

Peace,

marcf


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

[JBoss-dev] [ jboss-Change Notes-534166 ] JBoss integrated with JBossMX

2002-03-23 Thread noreply


Change Notes item #534166, was opened at 2002-03-24 00:12
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detailatid=381174aid=534166group_id=22866

Category: None
Group: None
Status: Open
Priority: 5
Submitted By: Adrian Brock (ejort)
Assigned to: Nobody/Anonymous (nobody)
Summary: JBoss integrated with JBossMX

Initial Comment:
JBoss now uses JBossMX to build and run.

This fixes the problem with JSR77 and java 1.4

jmxri.jar is still used to run the html adaptor
in jmxtools.jar The html adaptor uses the trace
classes from jmxri.jar

For further information on JBossMX visit the website
http://www.jboss.org/developers/jboss-jbossmx.jsp

Regards,
Adrian

--

You can respond by visiting: 
http://sourceforge.net/tracker/?func=detailatid=381174aid=534166group_id=22866

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

[JBoss-dev] [ jboss-Bugs-525412 ] EAR Deployment Problem with ejb-link

2002-03-23 Thread noreply


Bugs item #525412, was opened at 2002-03-04 07:47
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detailatid=376685aid=525412group_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 ejb-link

Initial Comment:

According to the dtd for an ejb-jar,
(http://java.sun.com/dtd/ejb-jar_2_0.dtd), the value of
the ejb-link element must be omitted. 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
ejb-linkCabinEJB/ejb-link. 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:

datestamp 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-24 00:14

Message:
Logged In: YES 
user_id=9459

Hi,

This should be fixed in latest CVS. I'm not closing this
bug report until jboss does relative ejb-link

Regards,
Adrian

--

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=detailatid=376685aid=525412group_id=22866

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

[JBoss-dev] Automated JBoss Testsuite Results: 24-March-2002

2002-03-23 Thread chris




JBoss daily test results

SUMMARY

Number of tests run:   540



Successful tests:  512

Errors:24

Failures:  4





[time of test: 24 March 2002 1:3 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] Automated JBoss Testsuite Results: 24-March-2002

2002-03-23 Thread chris




JBoss daily test results

SUMMARY

Number of tests run:   547



Successful tests:  521

Errors:22

Failures:  4





[time of test: 24 March 2002 1:50 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] CVS update: jboss-management/src/main/org/jboss/management/mejb ClientNotificationListener.java ManagementBean.java RMIClientNotificationListener.java

2002-03-23 Thread Andreas Schaefer


  User: schaefera
  Date: 02/03/23 18:25:05

  Modified:src/main/org/jboss/management/mejb
ClientNotificationListener.java ManagementBean.java
RMIClientNotificationListener.java
  Log:
  Fixed a problem with the RMINotificationListener and wrong numbering of
  the State in StateManageable found by Dirk Laessig (thanx).
  
  Revision  ChangesPath
  1.2   +6 -3  
jboss-management/src/main/org/jboss/management/mejb/ClientNotificationListener.java
  
  Index: ClientNotificationListener.java
  ===
  RCS file: 
/cvsroot/jboss/jboss-management/src/main/org/jboss/management/mejb/ClientNotificationListener.java,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- ClientNotificationListener.java   11 Mar 2002 04:31:33 -  1.1
  +++ ClientNotificationListener.java   24 Mar 2002 02:25:05 -  1.2
  @@ -49,7 +49,7 @@
  
  public ObjectName createListener(
 MEJB pConnector,
  -  String mClass,
  +  String pClass,
 Object[] pParameters,
 String[] pSignatures
  ) throws
  @@ -57,14 +57,15 @@
 ReflectionException,
 MBeanRegistrationException,
 MBeanException,
  -  NotCompliantMBeanException
  +  NotCompliantMBeanException,
  +  RemoteException
  {
 ObjectName lName = null;
 while( lName == null ) {
try {
   lName = new ObjectName( JMX:type=listener,id= + mRandom.nextLong() );
   ObjectInstance lInstance = pConnector.createMBean(
  -   mClass,
  +   pClass,
  lName,
  pParameters,
  pSignatures
  @@ -74,9 +75,11 @@
catch( InstanceAlreadyExistsException iaee ) {
   lName = null;
}
  +/* A remote exception could cause an endless loop therefore take it out
catch( RemoteException re ) {
   lName = null;
}
  +*/
 }
 mRemoteListener = lName;
 return lName;
  
  
  
  1.3   +6 -7  
jboss-management/src/main/org/jboss/management/mejb/ManagementBean.java
  
  Index: ManagementBean.java
  ===
  RCS file: 
/cvsroot/jboss/jboss-management/src/main/org/jboss/management/mejb/ManagementBean.java,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- ManagementBean.java   14 Mar 2002 22:59:35 -  1.2
  +++ ManagementBean.java   24 Mar 2002 02:25:05 -  1.3
  @@ -52,21 +52,19 @@
   *
   * @author a href=mailto:[EMAIL PROTECTED];Marc Fleury/a
   * @author a href=mailto:[EMAIL PROTECTED];Andreas Schaefer/a
  -* @version $Revision: 1.2 $
  +* @version $Revision: 1.3 $
   *
   * @ejb:bean name=MEJB
   *   display-name=JBoss Management EJB (MEJB)
   *   type=Stateless
   *   jndi-name=ejb/mgmt/MEJB
  -* @--ejb:interface generate=none
  -*remote-class=javax.management.j2ee.Management
   * @ejb:interface extends=javax.management.j2ee.Management
  -* @--ejb:home extends=javax.management.j2ee.ManagementHome
   * @ejb:home generate=none
   *   remote-class=javax.management.j2ee.ManagementHome
   * @ejb:env-entry description=JNDI-Name of the MBeanServer to be used to look it 
up. If 'null' the first of all listed local MBeanServer is taken
   *name=Server-Name
   *value=null
  +* @ejb:transaction type=Supports
   *
   **/
   public class ManagementBean
  @@ -143,7 +141,8 @@
 try {
return new Integer(
   queryNames(
  -   new ObjectName( getDefaultDomain() + :* )
  +   new ObjectName( getDefaultDomain() + :* ),
  +   null
   ).size()
);
 }
  @@ -228,10 +227,10 @@
   *
   * @ejb:interface-method view-type=remote
   **/
  -   public Set queryNames( ObjectName pName )
  +   public Set queryNames( ObjectName pName, QueryExp pQuery )
 throws RemoteException
  {
  -  return mConnector.queryNames( pName, null );
  +  return mConnector.queryNames( pName, pQuery );
  }
  
  /**
  
  
  
  1.2   +15 -7 
jboss-management/src/main/org/jboss/management/mejb/RMIClientNotificationListener.java
  
  Index: RMIClientNotificationListener.java
  ===
  RCS file: 
/cvsroot/jboss/jboss-management/src/main/org/jboss/management/mejb/RMIClientNotificationListener.java,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- RMIClientNotificationListener.java11 Mar 2002 04:31:33 -  1.1
  +++ RMIClientNotificationListener.java24 Mar 2002 02:25:05 -  1.2
  @@ -43,12 +43,12 @@
  {
 super( pSender, pClientListener, pHandback );

[JBoss-dev] CVS update: jboss-management build.xml

2002-03-23 Thread Andreas Schaefer


  User: schaefera
  Date: 02/03/23 18:25:05

  Modified:.build.xml
  Log:
  Fixed a problem with the RMINotificationListener and wrong numbering of
  the State in StateManageable found by Dirk Laessig (thanx).
  
  Revision  ChangesPath
  1.5   +2 -1  jboss-management/build.xml
  
  Index: build.xml
  ===
  RCS file: /cvsroot/jboss/jboss-management/build.xml,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- build.xml 23 Mar 2002 21:11:01 -  1.4
  +++ build.xml 24 Mar 2002 02:25:04 -  1.5
  @@ -12,7 +12,7 @@
   !----
   !-- == --
   
  -!-- $Id: build.xml,v 1.4 2002/03/23 21:11:01 ejort Exp $ --
  +!-- $Id: build.xml,v 1.5 2002/03/24 02:25:04 schaefera Exp $ --
   
   project default=main name=JBoss/Management
   
  @@ -297,6 +297,7 @@
 !-- Compile RMI stubs --
 target name=compile-rmi depends=compile-classes
   rmic base=${build.classes}
  +  sourcebase=${build.classes}
   verify=${rmic.verify}
   debug=${rmic.debug}
 stubVersion=${rmic.stubVersion}
  
  
  

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

[JBoss-dev] CVS update: jboss-management/src/main/org/jboss/management/j2ee J2EEDeployedObject.java J2EEManagedObject.java StateManageable.java StateManagement.java

2002-03-23 Thread Andreas Schaefer


  User: schaefera
  Date: 02/03/23 18:25:05

  Modified:src/main/org/jboss/management/j2ee J2EEDeployedObject.java
J2EEManagedObject.java StateManageable.java
StateManagement.java
  Log:
  Fixed a problem with the RMINotificationListener and wrong numbering of
  the State in StateManageable found by Dirk Laessig (thanx).
  
  Revision  ChangesPath
  1.2   +4 -2  
jboss-management/src/main/org/jboss/management/j2ee/J2EEDeployedObject.java
  
  Index: J2EEDeployedObject.java
  ===
  RCS file: 
/cvsroot/jboss/jboss-management/src/main/org/jboss/management/j2ee/J2EEDeployedObject.java,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- J2EEDeployedObject.java   11 Mar 2002 04:31:32 -  1.1
  +++ J2EEDeployedObject.java   24 Mar 2002 02:25:05 -  1.2
  @@ -21,7 +21,7 @@
* {@link javax.management.j2ee.J2EEDeployedObject J2EEDeployedObject}.
*
* @author  a href=mailto:[EMAIL PROTECTED];Andreas Schaefer/a.
  - * @version $Revision: 1.1 $
  + * @version $Revision: 1.2 $
*   
* pbRevisions:/b
*
  @@ -43,12 +43,14 @@
  public static final int WEB = 1;
  public static final int EJB = 2;
  public static final int RAR = 3;
  +   public static final int SAR = 4;
  
  private static final String[] sDescriptors = new String[] {
  META-INF/application.xml,
  WEB-INF/web.xml,
  META-INF/ejb-jar.xml,
  -   META-INF/ra.xml
  +   META-INF/ra.xml,
  +   META-INF/jboss-service.xml
   };
  
  // Attributes 
  
  
  
  1.6   +7 -1  
jboss-management/src/main/org/jboss/management/j2ee/J2EEManagedObject.java
  
  Index: J2EEManagedObject.java
  ===
  RCS file: 
/cvsroot/jboss/jboss-management/src/main/org/jboss/management/j2ee/J2EEManagedObject.java,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -r1.5 -r1.6
  --- J2EEManagedObject.java19 Mar 2002 02:50:18 -  1.5
  +++ J2EEManagedObject.java24 Mar 2002 02:25:05 -  1.6
  @@ -25,7 +25,7 @@
* {@link javax.management.j2ee.J2EEManagedObject J2EEManagedObject}.
*
* @author  a href=mailto:[EMAIL PROTECTED];Andreas Schaefer/a.
  - * @version $Revision: 1.5 $
  + * @version $Revision: 1.6 $
*   
* pbRevisions:/b
*
  @@ -225,6 +225,7 @@
   * override {@link #postCreation postCreation()} method.
   **/
  public final void postRegister( java.lang.Boolean pRegistrationDone ) {
  +  try {
 log.debug(postRegister(), parent:  + mParent );
 if( pRegistrationDone.booleanValue() ) {
// Let the subclass handle post creation steps
  @@ -246,6 +247,11 @@
  super.postRegister( new Boolean( false ) );
   }
}
  +  }
  +  }
  +  catch( RuntimeException re ) {
  + log.error( Caught Runtime Exception is postRegister(), re );
  + throw re;
 }
  }
  
  
  
  
  1.2   +4 -4  
jboss-management/src/main/org/jboss/management/j2ee/StateManageable.java
  
  Index: StateManageable.java
  ===
  RCS file: 
/cvsroot/jboss/jboss-management/src/main/org/jboss/management/j2ee/StateManageable.java,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- StateManageable.java  11 Mar 2002 04:31:32 -  1.1
  +++ StateManageable.java  24 Mar 2002 02:25:05 -  1.2
  @@ -27,7 +27,7 @@
*
* @author a href=mailto:[EMAIL PROTECTED];Marc Fleury/a
* @author a href=mailto:[EMAIL PROTECTED];Andreas Schaefer/a
  - * @version $Revision: 1.1 $
  + * @version $Revision: 1.2 $
*   
* pbRevisions:/b
*
  @@ -42,10 +42,10 @@
   {
  // Constants -
  
  -   public static final int STOPPED = 0;
  -   public static final int STOPPING = 1;
  -   public static final int STARTING = 2;
  -   public static final int RUNNING = 3;
  +   public static final int STARTING = 0;
  +   public static final int RUNNING = 1;
  +   public static final int STOPPING = 2;
  +   public static final int STOPPED = 3;
  public static final int FAILED = 4;
  
  // Public 
  
  
  
  1.3   +45 -4 
jboss-management/src/main/org/jboss/management/j2ee/StateManagement.java
  
  Index: StateManagement.java

[JBoss-dev] CVS update: jboss-management/src/main/javax/management/j2ee Management.java

2002-03-23 Thread Andreas Schaefer


  User: schaefera
  Date: 02/03/23 18:25:05

  Modified:src/main/javax/management/j2ee Management.java
  Log:
  Fixed a problem with the RMINotificationListener and wrong numbering of
  the State in StateManageable found by Dirk Laessig (thanx).
  
  Revision  ChangesPath
  1.2   +4 -2  jboss-management/src/main/javax/management/j2ee/Management.java
  
  Index: Management.java
  ===
  RCS file: 
/cvsroot/jboss/jboss-management/src/main/javax/management/j2ee/Management.java,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- Management.java   11 Mar 2002 04:31:31 -  1.1
  +++ Management.java   24 Mar 2002 02:25:05 -  1.2
  @@ -15,6 +15,7 @@
   import javax.management.MBeanException;
   import javax.management.MBeanInfo;
   import javax.management.ObjectName;
  +import javax.management.QueryExp;
   import javax.management.ReflectionException;
   
   /**
  @@ -22,7 +23,7 @@
*
* @author a href=mailto:[EMAIL PROTECTED];Marc Fleury/a
* @author a href=mailto:[EMAIL PROTECTED];Andreas Schaefer/a
  - * @version $Revision: 1.1 $
  + * @version $Revision: 1.2 $
*   
* pbRevisions:/b
*
  @@ -176,10 +177,11 @@
  * @param pName Object Name pattern identifying the managed objects to be 
retrieved.
  *  If null or no domain and key properties are specified, all the
  *  managed objects registered will be retrieved.
  +   * @param pQuery Query Expression instance for further select the desired objecs
  * @return Set of ObjectNames for the managed objects selected. If no managed
  * object satisfied the query, an emtpy list is returned
  **/
  -   public Set queryNames( ObjectName pName )
  +   public Set queryNames( ObjectName pName, QueryExp pQuery )
 throws
RemoteException;
  
  
  
  

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

[JBoss-dev] CVS update: jbosstest/src/main/org/jboss/test/management/test JSR77SpecUnitTestCase.java

2002-03-23 Thread Andreas Schaefer


  User: schaefera
  Date: 02/03/23 18:27:49

  Modified:src/main/org/jboss/test/management/test
JSR77SpecUnitTestCase.java
  Log:
  getLog() in inner class listener fails at runtime therefore removed but
  brought the Notification Listener test back in after the fixes.
  
  Revision  ChangesPath
  1.7   +49 -30
jbosstest/src/main/org/jboss/test/management/test/JSR77SpecUnitTestCase.java
  
  Index: JSR77SpecUnitTestCase.java
  ===
  RCS file: 
/cvsroot/jboss/jbosstest/src/main/org/jboss/test/management/test/JSR77SpecUnitTestCase.java,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -u -r1.6 -r1.7
  --- JSR77SpecUnitTestCase.java15 Mar 2002 07:04:41 -  1.6
  +++ JSR77SpecUnitTestCase.java24 Mar 2002 02:27:49 -  1.7
  @@ -30,12 +30,17 @@
   import org.jboss.test.JBossTestCase;
   import org.jboss.test.JBossTestSetup;
   
  +import org.jboss.management.j2ee.J2EEDomain;
  +import org.jboss.management.j2ee.J2EEManagedObject;
  +import org.jboss.management.j2ee.J2EEServer;
  +import org.jboss.management.j2ee.JDBCDataSource;
  +
   /**
* Test of JSR-77 specification conformance using the ??ToDo
* These test the basic JSR-77 handling and access.
*
* @author  a href=mailto:[EMAIL PROTECTED];Andreas Schaefer/a.
  - * @version $Revision: 1.6 $
  + * @version $Revision: 1.7 $
*   
* pbRevisions:/b
*
  @@ -49,6 +54,8 @@
   {
  // Constants -
  
  +   public static final String TEST_DATASOURCE = DefaultDS;
  +   
  // Attributes 
  
  // Static 
  @@ -114,14 +121,17 @@
 Management lManagement = getManagementEJB();
 Set lNames = lManagement.queryNames(
new ObjectName(
  -lManagement.getDefaultDomain() + :j2eeType=J2EEDomain,*
  - )
  +lManagement.getDefaultDomain() + : +
  +J2EEManagedObject.TYPE + = + J2EEDomain.J2EE_TYPE + , +
  +*
  + ),
  + null
 );
 if( lNames.isEmpty() ) {
  - fail( Could not found JSR-77 root object of j2eeType 'J2EEDomain' );
  + fail( Could not found JSR-77 root object of type ' + 
J2EEDomain.J2EE_TYPE + ' );
 }
 if( lNames.size()  1 ) {
  - fail( Found more than one JSR-77 root objects of j2eeType 'J2EEDomain' );
  + fail( Found more than one JSR-77 root objects of type ' + 
J2EEDomain.J2EE_TYPE + ' );
 }
 ObjectName lManagementDomain = (ObjectName) lNames.iterator().next();
 getLog().debug( +++ testGetManagementDomain, root:  + lManagementDomain );
  @@ -140,19 +150,23 @@
 Management lManagement = getManagementEJB();
 Set lNames = lManagement.queryNames(
new ObjectName(
  -lManagement.getDefaultDomain() + 
:j2eeType=JDBCDataSource,name=DefaultDS,*
  - )
  +lManagement.getDefaultDomain() + : +
  +J2EEManagedObject.TYPE + = + JDBCDataSource.J2EE_TYPE + , +
  +name= + TEST_DATASOURCE + , +
  +*
  + ),
  + null
 );
 if( lNames.isEmpty() ) {
  - fail( Could not found JSR-77 JDBC DataSource named 'DefaultDS' );
  + fail( Could not found JSR-77 JDBC DataSource named ' + TEST_DATASOURCE + 
' );
 }
 if( lNames.size()  1 ) {
  - fail( Found more than one JSR-77 JDBC DataSource named 'DefaultDS' );
  + fail( Found more than one JSR-77 JDBC DataSource named ' + 
TEST_DATASOURCE + ' );
 }
 ObjectName lDataSource = (ObjectName) lNames.iterator().next();
  -  getLog().debug( +++ testGetDataSource, DefaultDS:  + lDataSource );
  +  getLog().debug( +++ testGetDataSource,  + TEST_DATASOURCE + :  + 
lDataSource );
 getLog().debug(
  - +++ testGetDataSource, DefaultDS status:  +
  + +++ testGetDataSource,  + TEST_DATASOURCE +  status:  +
lManagement.getAttribute( lDataSource, State )
 );
 lManagement.remove();
  @@ -169,20 +183,24 @@
 Management lManagement = getManagementEJB();
 Set lNames = lManagement.queryNames(
new ObjectName(
  -lManagement.getDefaultDomain() + 
:j2eeType=JDBCDataSource,name=DefaultDS,*
  - )
  +lManagement.getDefaultDomain() + : +
  +J2EEManagedObject.TYPE + = + JDBCDataSource.J2EE_TYPE + , +
  +name= + TEST_DATASOURCE + , +
  +*
  + ),
  + null
 );
 if( lNames.isEmpty() ) {
  - fail( Could not found JSR-77 JDBC DataSource named 'DefaultDS' );
  + fail( Could not found JSR-77 JDBC DataSource named ' + TEST_DATASOURCE + 
' );
 }
 if( lNames.size()  1

[JBoss-dev] CVS update: jbosstest build.xml

2002-03-23 Thread Andreas Schaefer


  User: schaefera
  Date: 02/03/23 18:27:49

  Modified:.build.xml
  Log:
  getLog() in inner class listener fails at runtime therefore removed but
  brought the Notification Listener test back in after the fixes.
  
  Revision  ChangesPath
  1.97  +8 -9  jbosstest/build.xml
  
  Index: build.xml
  ===
  RCS file: /cvsroot/jboss/jbosstest/build.xml,v
  retrieving revision 1.96
  retrieving revision 1.97
  diff -u -r1.96 -r1.97
  --- build.xml 23 Mar 2002 21:11:03 -  1.96
  +++ build.xml 24 Mar 2002 02:27:49 -  1.97
  @@ -13,7 +13,7 @@
   !----
   !-- == --
   
  -!-- $Id: build.xml,v 1.96 2002/03/23 21:11:03 ejort Exp $ --
  +!-- $Id: build.xml,v 1.97 2002/03/24 02:27:49 schaefera Exp $ --
   
   project default=main name=JBoss/Testsuite
   
  @@ -135,13 +135,6 @@
 pathelement path=${jacorb.jacorb.lib}/jacorb.jar/
   /path
   
  -!-- JSR 77 --
  -property name=sun.jsr77.root value=${project.thirdparty}/sun/jsr77/
  -property name=sun.jsr77.lib value=${sun.jsr77.root}/lib/
  -path id=sun.jsr77.classpath
  -  pathelement path=${sun.jsr77.lib}/jsr77.jar/
  -/path
  -
   !-- JUnit --
   property name=junit.junit.root value=${project.thirdparty}/junit/junit/
   property name=junit.junit.lib value=${junit.junit.root}/lib/
  @@ -172,7 +165,6 @@
 path refid=oswego.concurrent.classpath/
 path refid=junit.junit.classpath/
 path refid=junitejb.junitejb.classpath/
  -  path refid=sun.jsr77.classpath/
   /path
   
   !-- === --
  @@ -1947,6 +1939,13 @@
 !-- jsr77 test --
 target name=_jars-jsr77
   mkdir dir=${build.lib}/
  +
  +!-- build ejbconf-test.jar --
  +jar jarfile=${build.lib}/jsr77-test.jar
  +  fileset dir=${build.classes}
  +   include name=org/jboss/test/management/**/
  +  /fileset
  +/jar
 /target
   
 !-- cmp2 tests --
  
  
  

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

[JBoss-dev] Automated JBoss Testsuite Results: 24-March-2002

2002-03-23 Thread chris




JBoss daily test results

SUMMARY

Number of tests run:   547



Successful tests:  522

Errors:22

Failures:  3





[time of test: 24 March 2002 2:37 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: 24-March-2002

2002-03-23 Thread chris




JBoss daily test results

SUMMARY

Number of tests run:   547



Successful tests:  522

Errors:22

Failures:  3





[time of test: 24 March 2002 4:11 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

Re: [JBoss-dev] JBossMX and JBossMQ standalone

2002-03-23 Thread Hiram Chirino



Yes please modify.  The standalone JBossMQ should run  under the same 
enviorment that the integrated one does.  So if JBoss is making the switch 
to JBossMX, JBossMQ should do the same also.  Makes maintenance easier.

Regards,
Hiram

From: Adrian Brock [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: [JBoss-dev] JBossMX and JBossMQ standalone
Date: Sat, 23 Mar 2002 16:29:44 -0600

There is a standalone checkout of JBossMQ that is
still using jmxri.jar

Part of the reason for doing the integration is to stop
developers using invoke() to get/set attributes.
Something that should never have been allowed and will be
stopped in the RI from JMX1.1

I can modify this, but it means modifying CVSROOT/modules
to include the jmx module.

I can do this, but should I?

Regards,
Adrian
_
View thread online: http://main.jboss.org/thread.jsp?forum=66thread=11480

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




_
Join the worlds largest e-mail service with MSN Hotmail. 
http://www.hotmail.com


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

[JBoss-dev] CVS update: jboss-system build.xml

2002-03-23 Thread David Jencks


  User: d_jencks
  Date: 02/03/23 21:35:01

  Modified:.build.xml
  Log:
  Moved mbean xml config processing entirely into ServiceConfigurator and added nested 
mbean configuration processing.  Made a couple more mbean interfaces xdoclet generated
  
  Revision  ChangesPath
  1.10  +3 -1  jboss-system/build.xml
  
  Index: build.xml
  ===
  RCS file: /cvsroot/jboss/jboss-system/build.xml,v
  retrieving revision 1.9
  retrieving revision 1.10
  diff -u -r1.9 -r1.10
  --- build.xml 23 Mar 2002 21:11:03 -  1.9
  +++ build.xml 24 Mar 2002 05:35:01 -  1.10
  @@ -12,7 +12,7 @@
   !----
   !-- == --
   
  -!-- $Id: build.xml,v 1.9 2002/03/23 21:11:03 ejort Exp $ --
  +!-- $Id: build.xml,v 1.10 2002/03/24 05:35:01 d_jencks Exp $ --
   
   project default=main name=JBoss/System
   
  @@ -238,6 +238,8 @@
 fileset dir=${source.java}
   include name=org/jboss/deployment/JARDeployer.java/
   include name=org/jboss/deployment/MainDeployer.java/
  +include name=org/jboss/deployment/SARDeployer.java/
  +include name=org/jboss/system/ServiceController.java/
 /fileset
 mbeaninterface mergedir=${project.tools}/etc/xdoclet/templates/
   
  
  
  

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

[JBoss-dev] CVS update: jbosstest/src/main/org/jboss/test/jmx/test DeployServiceUnitTestCase.java

2002-03-23 Thread David Jencks


  User: d_jencks
  Date: 02/03/23 21:35:01

  Modified:src/main/org/jboss/test/jmx/test
DeployServiceUnitTestCase.java
  Log:
  Moved mbean xml config processing entirely into ServiceConfigurator and added nested 
mbean configuration processing.  Made a couple more mbean interfaces xdoclet generated
  
  Revision  ChangesPath
  1.12  +10 -6 
jbosstest/src/main/org/jboss/test/jmx/test/DeployServiceUnitTestCase.java
  
  Index: DeployServiceUnitTestCase.java
  ===
  RCS file: 
/cvsroot/jboss/jbosstest/src/main/org/jboss/test/jmx/test/DeployServiceUnitTestCase.java,v
  retrieving revision 1.11
  retrieving revision 1.12
  diff -u -r1.11 -r1.12
  --- DeployServiceUnitTestCase.java29 Jan 2002 22:00:04 -  1.11
  +++ DeployServiceUnitTestCase.java24 Mar 2002 05:35:01 -  1.12
  @@ -31,7 +31,7 @@
   /**
* @see   related
* @authora href=mailto:[EMAIL PROTECTED];David Jencks/a
  - * @version   $Revision: 1.11 $
  + * @version   $Revision: 1.12 $
*/
   public class DeployServiceUnitTestCase
  extends JBossTestCase
  @@ -381,12 +381,15 @@
undeploy(testUrlD);
   
//check they aren't there any more
  - Collection ds = 
Arrays.asList((ObjectName[])getServer().getAttribute(serviceControllerName, 
Deployed));
  + Collection ds = (Collection)getServer().invoke(serviceControllerName, 
  +  listDeployedNames,
  +  new Object[] {},
  +  new String[] {});
assertTrue(test mbean A still registered after undeploy, 
!ds.contains(testObjectNameA));
   
  - assertTrue(test mbean A still registered after undeploy, 
!ds.contains(testObjectNameB));
  + assertTrue(test mbean B still registered after undeploy, 
!ds.contains(testObjectNameB));
   
  - assertTrue(test mbean A still registered after undeploy, 
!ds.contains(testObjectNameC));
  + assertTrue(test mbean C still registered after undeploy, 
!ds.contains(testObjectNameC));
assertTrue(test mbean D still registered after undeploy, 
!ds.contains(testObjectNameD));
 }
 finally
  @@ -522,7 +525,8 @@
 } // end of try-catch
 
  }
  -
  +   /* This test seems to be wrong.  Currently an exception in deployment of any 
mbean in a 
  +  sar results int the complete undeployment of the sar.
  public void testCrashInStart() throws Exception
  //Thanks to David Budworth for this test.
  {
  @@ -551,7 +555,7 @@
 } // end of try-catch
 
  }
  -
  +   */
  public void testNullInfoInDynamicMBean() throws Exception
  //Thanks to David Budworth for this test.
  //Tries to deploy a DynamicMBean that returns null from getMBeanInfo.
  
  
  

___
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 SARDeployer.java SARDeployerMBean.java

2002-03-23 Thread David Jencks


  User: d_jencks
  Date: 02/03/23 21:35:01

  Modified:src/main/org/jboss/deployment SARDeployer.java
  Removed: src/main/org/jboss/deployment SARDeployerMBean.java
  Log:
  Moved mbean xml config processing entirely into ServiceConfigurator and added nested 
mbean configuration processing.  Made a couple more mbean interfaces xdoclet generated
  
  Revision  ChangesPath
  1.3   +25 -18jboss-system/src/main/org/jboss/deployment/SARDeployer.java
  
  Index: SARDeployer.java
  ===
  RCS file: 
/cvsroot/jboss/jboss-system/src/main/org/jboss/deployment/SARDeployer.java,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- SARDeployer.java  9 Mar 2002 05:23:16 -   1.2
  +++ SARDeployer.java  24 Mar 2002 05:35:01 -  1.3
  @@ -69,7 +69,7 @@
* @author a href=mailto:[EMAIL PROTECTED];David Maplesden/a
* @author a href=mailto:[EMAIL PROTECTED];David Jencks/a
* @author a href=mailto:[EMAIL PROTECTED];Jason Dillon/a
  - * @version $Revision: 1.2 $
  + * @version $Revision: 1.3 $
*
* pb20010830 marc fleury:/b
* ul
  @@ -105,6 +105,10 @@
* ul
*   lirewrite
* /ul
  + *
  + * @jmx:mbean name=jboss.system:service=ServiceDeployer
  + *extends=org.jboss.deployment.DeployerMBean
  + *extends=org.jboss.system.Service
*/
   public class SARDeployer
  extends ServiceMBeanSupport
  @@ -133,6 +137,7 @@
   * ending in service.xml are accepted.
   *
   * @return   The FileNameFilter for use by the AutoDeployer.
  +* @jmx:managed-operation
   */
  public boolean accepts(DeploymentInfo di) 
  {
  @@ -140,6 +145,13 @@
 || di.url.toString().endsWith(service.xml));
  }   
   
  +   /**
  +* Describe codeinit/code method here.
  +*
  +* @param di a codeDeploymentInfo/code value
  +* @exception DeploymentException if an error occurs
  +* @jmx:managed-operation
  +*/
  public void init(DeploymentInfo di)
 throws DeploymentException
  {
  @@ -205,6 +217,13 @@
 }
  }
   
  +   /**
  +* Describe codecreate/code method here.
  +*
  +* @param di a codeDeploymentInfo/code value
  +* @exception DeploymentException if an error occurs
  +* @jmx:managed-operation
  +*/
  public void create(DeploymentInfo di)
 throws DeploymentException
  {
  @@ -216,23 +235,8 @@

List mbeans = di.mbeans;
mbeans.clear();
  - 
  - NodeList nl = di.document.getElementsByTagName(mbean);
  - 
  - for (int i = 0; i  nl.getLength(); i++)
  - {
  -Element mbean = (Element)nl.item(i);
  -
  -log.debug(deploying with ServiceController mbean  + mbean);
  - ObjectName service = serviceController.install(mbean);
  -
  -if (service != null)
  -{
  -   mbeans.add(service);
  -   // objectNameToSupplyingPackageMap.put(service, url);
  -}
  - }
  - 
  +
  + mbeans.addAll(serviceController.install(di.document.getDocumentElement()));
   
// create the services
for (Iterator iter = di.mbeans.iterator(); iter.hasNext(); ) 
  @@ -255,6 +259,7 @@
   *
   * @param di a codeDeploymentInfo/code value
   * @exception DeploymentException if an error occurs
  +* @jmx:managed-operation
   */
  public void start(DeploymentInfo di) throws DeploymentException
  {
  @@ -515,6 +520,7 @@
   * @param service the codeDeploymentInfo/code value to stop.
   * @exception DeploymentExceptionThrown if the package could not be
   *   undeployed
  +* @jmx:managed-operation
   */
  public void stop(DeploymentInfo di)
 //throws DeploymentException
  @@ -545,6 +551,7 @@
   *
   * @param service a codeDeploymentInfo/code value
   * @exception DeploymentException if an error occurs
  +* @jmx:managed-operation
   */
  public void destroy(DeploymentInfo di)
 //throws DeploymentException
  
  
  

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

[JBoss-dev] CVS update: jboss-system/src/main/org/jboss/system ServiceConfigurator.java ServiceContext.java ServiceController.java ServiceControllerMBean.java

2002-03-23 Thread David Jencks


  User: d_jencks
  Date: 02/03/23 21:35:01

  Modified:src/main/org/jboss/system ServiceConfigurator.java
ServiceContext.java ServiceController.java
  Removed: src/main/org/jboss/system ServiceControllerMBean.java
  Log:
  Moved mbean xml config processing entirely into ServiceConfigurator and added nested 
mbean configuration processing.  Made a couple more mbean interfaces xdoclet generated
  
  Revision  ChangesPath
  1.4   +290 -160  jboss-system/src/main/org/jboss/system/ServiceConfigurator.java
  
  Index: ServiceConfigurator.java
  ===
  RCS file: 
/cvsroot/jboss/jboss-system/src/main/org/jboss/system/ServiceConfigurator.java,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- ServiceConfigurator.java  2 Mar 2002 01:16:37 -   1.3
  +++ ServiceConfigurator.java  24 Mar 2002 05:35:01 -  1.4
  @@ -9,50 +9,54 @@
   
   package org.jboss.system;
   
  +
  +
  +
  +
   import java.beans.PropertyEditor;
   import java.beans.PropertyEditorManager;
   import java.io.StringWriter;
   import java.io.Writer;
   import java.lang.reflect.Method;
   import java.lang.reflect.Modifier;
  -import java.util.StringTokenizer;
  -import java.util.LinkedList;
   import java.util.ArrayList;
   import java.util.Hashtable;
  -
  +import java.util.LinkedList;
  +import java.util.List;
  +import java.util.ListIterator;
  +import java.util.StringTokenizer;
   import javax.management.Attribute;
   import javax.management.InstanceNotFoundException;
   import javax.management.MBeanAttributeInfo;
  +import javax.management.MBeanException;
   import javax.management.MBeanInfo;
   import javax.management.MBeanServer;
   import javax.management.MalformedObjectNameException;
   import javax.management.ObjectInstance;
   import javax.management.ObjectName;
  -import javax.management.MBeanException;
   import javax.management.ReflectionException;
  -import javax.management.RuntimeOperationsException;
  -import javax.management.RuntimeMBeanException;
   import javax.management.RuntimeErrorException;
  -
  +import javax.management.RuntimeMBeanException;
  +import javax.management.RuntimeOperationsException;
   import javax.xml.parsers.DocumentBuilder;
   import javax.xml.parsers.DocumentBuilderFactory;
  -
  +import org.jboss.deployment.DeploymentException;
  +import org.jboss.logging.Logger;
  +import org.jboss.util.jmx.JMXExceptionDecoder;
  +import org.jboss.util.jmx.ObjectNameFactory;
  +import org.jboss.util.xml.DOMWriter;
   import org.w3c.dom.Document;
   import org.w3c.dom.Element;
   import org.w3c.dom.Node;
   import org.w3c.dom.NodeList;
   import org.w3c.dom.Text;
   
  -import org.jboss.deployment.DeploymentException;
  -import org.jboss.logging.Logger;
  -import org.jboss.util.xml.DOMWriter;
  -
   /**
* Service configuration helper.
*
* @author a href=mailto:[EMAIL PROTECTED];Marc Fleury/a
* @author a href=mailto:[EMAIL PROTECTED];Hiram Chirino/a
  - * @version $Revision: 1.3 $
  + * @version $Revision: 1.4 $
*
* pb20010830 marc fleury:/b
* ul
  @@ -81,119 +85,111 @@
  }
  
  /** The MBean server which this service is registered in. */
  -   private MBeanServer server;
  +   private final MBeanServer server;
  +   private final ServiceController serviceController;
  +   private final ServiceCreator serviceCreator;
  
  /** The instance logger. */
  -   private static Logger log = Logger.getLogger(ServiceConfigurator.class);
  +   private final Logger log = Logger.getLogger(getClass());
  
  // Constructors --
  
  -   public ServiceConfigurator(final MBeanServer server)
  +   public ServiceConfigurator(final MBeanServer server,
  +  final ServiceController serviceController,
  +  final ServiceCreator serviceCreator)
  {
 this.server = server;
  +  this.serviceController = serviceController;
  +  this.serviceCreator = serviceCreator;
  }
  
  // Public  ---
  
  -   /** A helper to deal with those pesky JMX exceptions. */
  -   private void setAttribute(ObjectName name, Attribute attr)
  -  throws Exception
  -   {
  -  try {
  - server.setAttribute(name, attr);
  -  }
  -  catch (MBeanException e) {
  - throw e.getTargetException();
  -  }
  -  catch (ReflectionException e) {
  - throw e.getTargetException();
  -  }
  -  catch (RuntimeOperationsException e) {
  - throw e.getTargetException();
  -  }
  -  catch (RuntimeMBeanException e) {
  - throw e.getTargetException();
  -  }
  -  catch (RuntimeErrorException e) {
  - throw e.getTargetError();
  -  }
  -   }
  +
  +   // Public

[JBoss-dev] Automated JBoss Testsuite Results: 24-March-2002

2002-03-23 Thread chris




JBoss daily test results

SUMMARY

Number of tests run:   538



Successful tests:  510

Errors:23

Failures:  5





[time of test: 24 March 2002 5:50 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: 24-March-2002

2002-03-23 Thread chris




JBoss daily test results

SUMMARY

Number of tests run:   540



Successful tests:  512

Errors:24

Failures:  4





[time of test: 24 March 2002 7:9 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: 24-March-2002

2002-03-23 Thread chris




JBoss daily test results

SUMMARY

Number of tests run:   547



Successful tests:  519

Errors:25

Failures:  3





[time of test: 24 March 2002 7:59 GMT]
[java.version: 1.4.0]
[java.vendor: Sun Microsystems Inc.]
[java.vm.version: 1.4.0-b92]
[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

82 matches

Mail list logo