[JBoss-dev] Automated JBoss(Branch_3_0) Testsuite Results: 4-April-2003
Automated JBoss(Branch_3_0) Testsuite Results: 4-April-2003\n\n
begin 644 TESTS-TestSuites.txt
M#0H-DI;W-S(1A:6QY('1EW0@F5S=6QTPT*#0I354U-05)9#0H-DYU
M;6)EB!O9B!T97-TR!R=6XZ( @,3$Q,0T*#0HM+2TM+2TM+2TM+2TM+2TM
M+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+0T*#0I3=6-C97-S9G5L('1E
MW1S.B @( @(#$Q,#4-@T*17)R;W)S.B @( @( @( @( @( Q#0H-
MD9A:6QUF5S.B @( @( @( @( @-0T*#0HM+2TM+2TM+2TM+2TM+2TM
M+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+0T*#0H-@T*6W1I;64@;V8@
M=5S=#H@,C P,RTP-TP,RXR,RTT,B!'351=#0I;:F%V82YV97)S:6]N.B Q
M+C0N,5\P,ET-EMJ879A+G9E;F1O[EMAIL PROTECTED]($UI8W)OWES=5MR!);F,N
M70T*6VIA=F$N=FTN=F5RVEO;CH@,2XT+C%?,#(M8C V70T*6VIA=F$N=FTN
M;[EMAIL PROTECTED](;W13]T*%1-*2!#;EE;[EMAIL PROTECTED];:F%V82YV;2YI
M;F9O.B!M:7AE9!M;V1E70T*6V]S+FYA;64Z(%=I;F1O=W,@,C P,%T-EMO
MRYAF-H.B!X.#9=#0I;;W,N=F5RVEO;[EMAIL PROTECTED]@:'1T#HO
M+V)L:7-S+FIB;W-S+F]R9R]^W1AFMS;2]F%N8VA?,U\P+S(P,#,M,#0M
M,#,N,C,M-#(-F9OB!D971A:6QS(]F('1H:7,@=5S=[EMAIL PROTECTED]DY/5$4Z
M($EF('1H97)E(%R92!A;[EMAIL PROTECTED])R;W)S('-H;W=N(%B;W9E([EMAIL PROTECTED]AIR!M
M86EL(ES(]N;'D@:EG:QI9VAT:6YG( T*=AE;2 M(ET(ES($Y/5!I
M;F1I8V%T:6YG('[EMAIL PROTECTED]AE2!A[EMAIL PROTECTED];F@;]O:V5D(%T()Y(%N
M6]N92X-@T*270@:7,@87-S=6UE9!T:%T('=H;V5V97(@;6%K97,@8VAA
M;F=E*',I('1O(IB;W-S('[EMAIL PROTECTED]F5A:R!T:[EMAIL PROTECTED]5S=!W:6QL()E
M(9IEN9R!T:[EMAIL PROTECTED]5S=!OB!J8F]S[EMAIL PROTECTED],@87!PF]PFEA=4A#0H-
MBTM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM
M#0H-@T*#0I$151!24Q3($]($524D]24PT*#0H-@T*4W5I=4Z( @( @
M($)E86Y3=')EW-497-T0V%S90T*55S=#H@( @( @('1EW1$96%D3]C
M:T9R;VU#;EE;G0H;W)G+FIB;W-S+G1EW0N95A9QO8VLN=5S=Y96%N
M4W1R97-S55S=$-AV4I#0I47!E.B @( @( @9F%I;'5R90T*17AC97!T
M:6]N.B @(IU;FET+F9R86UE=V]R:RY!W-EG1I;VY86EL961%G)O@T*
M365SV%G93H@( @(5X5C=5D([EMAIL PROTECTED](1E861L;V-K(9OB!!
M0B!00T*+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM#0H-@T*
M#0I3=6ET93H@( @( @25L;]#;'5S=5R961(='1P4W1R97-S55S=$-A
MV4-E1EW0Z( @( @(!T97-T0TY14]B:F5C=AOFN:F)OW,N=5S
M=YH96QL;RYT97-T+DAE;QO0VQUW1EF5D2'1T%-TF5SU1EW1#87-E
M*0T*5'EP93H@( @( @(9A:6QUF4-D5X8V5P=EO;CH@(!J=6YI=YF
MF%M97=OFLN07-S97)T:6]N1F%I;5D17)R;W(-DUEW-A9V4Z( @(!7
M87,@86)L92!T;R!I;G9O:V4@F5M;W9E#0HM+2TM+2TM+2TM+2TM+2TM+2TM
M+2TM+2TM+2TM+2TM+2T-@T*#0H-E-U:71E.B @( @(!,87)G94UEW-A
M9V55;FET55S=$-AV4-E1EW0Z( @( @(!T97-T54E,3%R9V5-97-S
M86=E*]R9RYJ8F]SRYT97-T+FIB;W-S;7$N=5S=Y,87)G94UEW-A9V55
M;FET55S=$-AV4I#0I47!E.B @( @( @9F%I;'5R90T*17AC97!T:6]N
M.B @(IU;FET+F9R86UE=V]R:RY!W-EG1I;VY86EL961%G)O@T*365S
MV%G93H@( @(%=E('-H;W5L9!N;[EMAIL PROTECTED]($@EN9R!E-E'1I;VX@
M8F5C875S92!I=!S:]U;0@]N9R!E=F5R2!C:'5N:SH@;W)G+FIB;W-S
M+FUQ+E-P4I-4T5X8V5P=EO;[EMAIL PROTECTED]EN9R!T:6UE;W5T+!N;R!P:6YG(')E
MQY('-E96X@:6XZ(#$P,# @37,-BTM+2TM+2TM+2TM+2TM+2TM+2TM+2TM
M+2TM+2TM+2TM+0T*#0H-@T*4W5I=4Z( @( @($UIW-I;F=#;%SU5N
M:71497-T0V%S90T*55S=#H@( @( @('1EW1$97!L;WE397)V:6-E5VET
M:]U=$-L87-S*]R9RYJ8F]SRYT97-T+FIMYT97-T+DUIW-I;F=#;%S
MU5N:71497-T0V%S92D-E1Y4Z( @( @(!EG)O@T*17AC97!T:6]N
M.B @(]R9RYJ8F]SRYD97!L;WEM96YT+D1EQO6UE;G1%-E'1I;VX-
MDUEW-A9V4Z( @(!J8F]SRYT97-T.FYA;64];6ESVEN9V-L87-S=5S
M=!IR!N;W0@F5G:7-T97)E9X[(T@;F5S=5D('1HF]W86)[EMAIL PROTECTED]IA
M=F%X+FUA;F%G96UE;G0N26YS=%N8V5.;W1;W5N9$5X8V5P=EO;CH@:F)O
MW,N=5S=#IN86UE/6UIW-I;F=C;%SW1EW0@:7,@;F]T(')E9VES=5R
M960N*0T*+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM#0H-@T*
M#0I3=6ET93H@( @( @4V5C=7)I='E5;FET55S=$-AV4-E1EW0Z( @
M( @(!T97-T4V5C=7)E2'1T$EN=F]K97(H;W)G+FIB;W-S+G1EW0N;F%M
M:6YG+G1EW0N4V5C=7)I='E5;FET55S=$-AV4I#0I47!E.B @( @( @
M9F%I;'5R90T*17AC97!T:6]N.B @(IU;FET+F9R86UE=V]R:RY!W-EG1I
M;VY86EL961%G)O@T*365SV%G93H@( @(%-H;W5L9!N;W0@:%V92!B
M965N(%B;[EMAIL PROTECTED]\@;]O:W5P*EN=F]K97)S*0T*+2TM+2TM+2TM+2TM+2TM
M+2TM+2TM+2TM+2TM+2TM+2TM#0H-@T*#0I3=6ET93H@( @( @4V5C=7)I
M='E5;FET55S=$-AV4-E1EW0Z( @( @(!T97-T4V5C=7)E2'1T$EN
M=F]K97)86EL=7)E*]R9RYJ8F]SRYT97-T+FYA;6EN9RYT97-T+E-E8W5R
M:71Y56YI=%1EW1#87-E*0T*5'EP93H@( @( @(9A:6QUF4-D5X8V5P
M=EO;CH@(!J=6YI=YFF%M97=OFLN07-S97)T:6]N1F%I;5D17)R;W(-
MDUEW-A9V4Z( @(!3:]U;0@;F]T([EMAIL PROTECTED];B!A8FQE('1O(QO
M;VMUAI;G9O:V5RRD-BTM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM
(+2TM+0T*#0H!
end
---
This SF.net email is sponsored by: ValueWeb:
Dedicated Hosting for just $79/mo with 500 GB of bandwidth!
No other company gives more support or power for your dedicated server
http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] JB4DR1 Deadline MAY 26
I talked with Dr Jung yesterday, the Webservices part is going pretty well but JAXR is 70% there and W2EE is still 80% to go (but easy) (Dr. Jung's words) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dain Sundstrom Sent: vendredi, 4. avril 2003 00:48 To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] JB4DR1 Deadline MAY 26 I don't think we can support J2EE 1.4 for the DR1 release unless someone gets in and makes whatever changes are required to get our metadata classes to support the XML schemas used in J2EE 1.4. Besides meta data are there other big things in J2EE 1.4 that we haven't addressed yet? -dain On Thursday, April 3, 2003, at 04:30 PM, Igor Fedorenko wrote: What J2EE specification version are you planning to support in JBoss 4.0? J2EE 1.4 is not final as far as I know... -Original Message- From: marc fleury [mailto:[EMAIL PROTECTED] Sent: Thursday, April 03, 2003 3:47 PM To: [EMAIL PROTECTED] Sourceforge. Net Subject: [JBoss-dev] JB4DR1 Deadline MAY 26 Guys, We are thinking a lot about the forthcoming JB4 release. It is a truly exciting step for us as we believe we will bring a programming style, whose time has come, to a mass audience. AOP as Bill says is a clear wave for system level services on par with OOP. On top of it and also as a proof of how powerful the approach is we still develop a full J2EE server. Meaning that you can choose to live in the J2EE world work on JBoss J2EE and access all the prepackaged AOP goodies as you have been doing since JBoss2.0. There seems to be a lot of fear at SUN from what I can tell in the press, that we will abandon J2EE. We love J2EE. When really we will support J2EE for the forthcoming future. Never do we talk about abandoning J2EE, we just let the user access core functionality in the open server and think at the AOP level. A more fundamental construct of the framework. The reason we are almost there is that it is also a very old implementation in JBoss. We have been doing it for a long time but never talked/packaged it this way. We make it easy for you to leverage the AOP layer. The implementation is old the way you interact with JBoss is new. It can also be old if you decide to stay at the J2EE level which will be fully supported. But you are now invited to roam in the core JBoss system, in fact you may find it very cozy as you port POJO based applications to JBoss. There will be a stabilization period though. We are making an aggressive push to release JB4 by JavaONE with all our resources dedicated to implementing the final AOP system aspects and porting some of the existing code to that. We're making an aggressive push to release JBoss 4.0 by JavaOne. We're targeting May 26th. That leaves us 2 month from now. I REPEAT TARGET FOR JBOSS4.0 DR1 MAY 26TH To meet this aggressive deadline, we need to set some dates. There will be a functionality freeze, Monday, May 5th. All new functionality commits after May 5th must be approved by either Scott Stark, or Bill Burke. We will not branch May 5th, but instead make the month of May, JBoss 4.0 stability en route to a Developpers Release 1 (DR1). Please think long and hard and fast about your modules. Many of you are involved in core modules that need to move fast in the coming weeks. Don't be afraid to talk and say who needs help etc. PLgC marcf --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] class loader problem
This code is worfking fine as
standlone.
ClassLoader.getSystemClassLoader().loadClass(paramStr[1]);
But the same is code is not working in jboss
for javax. package
ClassLoader.getSystemClassLoader().loadClass("javax.mail.Message");
I have kept the mail.jar in lib folder still
it is not working . Same code is working for the default pacakages for ex
java.util.Vector is loading successfully.
please help me for the above problem.
Thanks and Regards
surendra
Why the forums suck (Was: Re: [JBoss-dev] AOP versioned ACID objects 1st iteration)
On Thursday, Mar 27, 2003, at 18:25 Europe/Amsterdam, Bill Burke wrote: We've been trying hard to keep the development forums as the base of design discussions. There's a lot of good information there. The information there is good, but it is a pain to access the forums. Here are some of the reasons: The jboss site is bloated with content. If i'm there to read forums I don't want to see flashing banners all the time. It slows down page loading a lot and takes up a lot of space on the screen. The development forums are marked with 'no user questions here please' but nobody seems to care much. Questions about *any* subject are posted in random forums. Searching in the forums is a pain. It would be so much nicer to be able to search by subject, and not see every single article in a thread but just the unqiue thread names. It is *slow* to read. Nothing beats a good news or email reader. I read/browse through a backlog of 100 messages on this list in 15 minutes. On the forums it will take hours to even find the last messages. What would really help is a forum2email gateway to relay new messages to an email address. I know that begging for features is not allowed here :) so if it an option to add that as a module to the new nukes stuff then I can help out with that. S. --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: Why the forums suck (Was: Re: [JBoss-dev] AOP versioned ACID objects 1st iteration)
\ What would really help is a forum2email gateway to relay new messages to an email address. I know that begging for features is not allowed here :) so if it an option to add that as a module to the new nukes stuff then I can help out with that. OK :) marcf S. --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020 aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: AW: [JBoss-dev] JB4DR1 Deadline MAY 26
If we can include/redistribute the jaxm libraries adding the ability to accept jaxm calls from a jca 1.5 resource adapter to an mdb is very easy. I can't understand the license terms and the last time I asked I got no response. Is there another jca part to the webservices? thanks david jencks On 2003.04.04 01:44 Jung , Dr. Christoph wrote: Until 26th of May, I will have a version of W2EE deployment ready (at least the subset of the webservices.xml and jaxrpc-mapping.xml that can be easily mapped via a XSL-driven WebServiceDeployer to the existing web-service.xml/AxisService; deployer hooks in EJBDeployer+WARDeployer-WebServiceDeployer must be coordinated with Bill? And Scott?). I will also have catered for a reasonable auto-registration of web service wsdl in uddi until then. I cannot guarantuee Xdoclet support to generate J2EE1.4 webservices.xml and JAXRPC mappings. Maybe there will be a volunteer for this (one of the xpetstore guys was interested in trying that out?). Maybe the xdoclet team will have something in that direction anyway ... I would delay all web service extensions of JCA and JMS (just a guess from a quick look into the draft) and the tighter integration of the Axis and Jboss invocation stacks then after JB4DR1. CGJ -Ursprüngliche Nachricht- Von: Bill Burke [mailto:[EMAIL PROTECTED] Gesendet: Freitag, 4. April 2003 00:28 An: [EMAIL PROTECTED] Betreff: RE: [JBoss-dev] JB4DR1 Deadline MAY 26 JBoss Remoting AOP + tx, security, versioning, remoting, clustering, txlock, caching DTM (waiting on David's response) EMB (Enterprise Media Beans) JUDDI integration If I can get it done: AOP + EJB (packaged extensions to EJB) and don't forget Nukes! Anybody got anything to add to this list? Who doesn't think they'll be done by May 5th? Who thinks they'll be cutting it close? Bill -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Dain Sundstrom Sent: Thursday, April 03, 2003 4:48 PM To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] JB4DR1 Deadline MAY 26 Ok then there are 4 weeks to get the new stuff done? Marc, Bill, sure we could do a release but what difference would it make if the new features are not in it. Is this a release just to show off AOP? What about any of the other new stuff? Just give the users a solid 3.2 and they will be happy. -dain On Thursday, April 3, 2003, at 03:30 PM, Bill Burke wrote: It will be ready and stable. Functionality freeze is May 5th. What functionality doesn't make it by then will be left out of the release. Bill -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Dain Sundstrom Sent: Thursday, April 03, 2003 4:01 PM To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] JB4DR1 Deadline MAY 26 I think you are delusional if you think JB4 will be ready for JavaOne. -dain On Thursday, April 3, 2003, at 02:47 PM, marc fleury wrote: Guys, We are thinking a lot about the forthcoming JB4 release. It is a truly exciting step for us as we believe we will bring a programming style, whose time has come, to a mass audience. AOP as Bill says is a clear wave for system level services on par with OOP. On top of it and also as a proof of how powerful the approach is we still develop a full J2EE server. Meaning that you can choose to live in the J2EE world work on JBoss J2EE and access all the prepackaged AOP goodies as you have been doing since JBoss2.0. There seems to be a lot of fear at SUN from what I can tell in the press, that we will abandon J2EE. We love J2EE. When really we will support J2EE for the forthcoming future. Never do we talk about abandoning J2EE, we just let the user access core functionality in the open server and think at the AOP level. A more fundamental construct of the framework. The reason we are almost there is that it is also a very old implementation in JBoss. We have been doing it for a long time but never talked/packaged it this way. We make it easy for you to leverage the AOP layer. The implementation is old the way you interact with JBoss is new. It can also be old if you decide to stay at the J2EE level which will be fully supported. But you are now invited to roam in the core JBoss system, in fact you may find it very cozy as you port POJO based applications to JBoss. There will be a stabilization period though. We are making an aggressive push to release JB4 by JavaONE with all our resources dedicated to implementing the final AOP system aspects and porting some of the existing code to that. We're making an aggressive push to release JBoss 4.0 by JavaOne. We're targeting May 26th. That leaves us 2 month from now. I
Re: Why the forums suck (Was: Re: [JBoss-dev] AOP versioned ACIDobjects 1st iteration)
I agree with everything you say which is why I only read the forums when I have to. Pitch in to help Julien create something useable. -- Scott Stark Chief Technology Officer JBoss Group, LLC Stefan Arentz wrote: On Thursday, Mar 27, 2003, at 18:25 Europe/Amsterdam, Bill Burke wrote: We've been trying hard to keep the development forums as the base of design discussions. There's a lot of good information there. The information there is good, but it is a pain to access the forums. Here are some of the reasons: The jboss site is bloated with content. If i'm there to read forums I don't want to see flashing banners all the time. It slows down page loading a lot and takes up a lot of space on the screen. The development forums are marked with 'no user questions here please' but nobody seems to care much. Questions about *any* subject are posted in random forums. Searching in the forums is a pain. It would be so much nicer to be able to search by subject, and not see every single article in a thread but just the unqiue thread names. It is *slow* to read. Nothing beats a good news or email reader. I read/browse through a backlog of 100 messages on this list in 15 minutes. On the forums it will take hours to even find the last messages. What would really help is a forum2email gateway to relay new messages to an email address. I know that begging for features is not allowed here :) so if it an option to add that as a module to the new nukes stuff then I can help out with that. S. --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] class loader problem
The system class loader is the wrong thing to be using in JBoss. Read the class loading docs on sourceforge and then the Thread.getContextClassLoader() javadocs. -- Scott Stark Chief Technology Officer JBoss Group, LLC Surendranath Reddy Yanam wrote: This code is worfking fine as standlone. ClassLoader.getSystemClassLoader().loadClass(paramStr[1]); But the same is code is not working in jboss for javax. package ClassLoader.getSystemClassLoader().loadClass(javax.mail.Message); I have kept the mail.jar in lib folder still it is not working . Same code is working for the default pacakages for ex java.util.Vector is loading successfully. please help me for the above problem. Thanks and Regards surendra --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] JBoss remoting callbacks [was JB4DR1 Deadline MAY 26]
I question if A JMSServerInvocationHandler is even necessary (along with the JMS Subsystem) if Bill exposes the callbacks via the AOP remoting framework. Frankly, I have the same thought about all the subsystems as I know EJB for instance will also being using the AOP framework and therefore the AOPServerInvocationHandler. I know you guys have a JMX subsystem which you have used to implement JMX remoting, but if you decide to refactor that to use the AOP framework that subsystem wouldn't be necessary either as far as I understand it. What I'm getting at is that it is my understanding that the future of J2EE flavored services on JBoss will be built on top of the AOP framework, and therefore AOP remoting is going to be the only InvocationHandler used because it is what gives us the modern interceptor stack. Bill, am I correct? Thanks, Nathan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tom Elrod Sent: Friday, April 04, 2003 1:05 AM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] JBoss remoting callbacks [was JB4DR1 Deadline MAY 26] Guess Jeff beat me to it ;) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Tom Elrod Sent: Friday, April 04, 2003 1:49 AM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] JBoss remoting callbacks [was JB4DR1 Deadline MAY 26] Jeff made the fix last night and I have not looked at the code yet (he still has it local while we are testing that and some other fixes out). However, my understanding from Jeff is that the invoker client passes its locator to the invoker server if it wishes to receive callbacks. The invoker server will then use that for establishing the connection back to the client to send notifications (callbacks). Given this, it will be pretty easy to make it so the calling code can give the client invoker the locator to use for callbacks, which it then gives the invoker server (and will use its own by default as is now). I can put this in this weekend (if Jeff doesn't beat me to it). It sounds like there won't be enough time to include JMS as one of the invoker transport before the deadline. However, I would personally be interested in working with you on it. Depending on how soon you will have time to start on it, might be wise to make a branch just for the JMS transport, until JB4DR1. -Tom -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Nathan Phelps Sent: Thursday, April 03, 2003 11:44 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] JB4DR1 Deadline MAY 26 Did you guys end up doing it in such a way so that you can use one protocol one way and another protocol the other way like you had mentioned? Secondly, what is really going to be cool when we expose this via AOP remoting... Bill, what are your plans for that? Thanks, Nathan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeff Haynie Sent: Thursday, April 03, 2003 8:21 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] JB4DR1 Deadline MAY 26 Jboss Remoting callbacks are in - I wil commit in the next day or so when tom and I finish testing. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bill Burke Sent: Thursday, April 03, 2003 6:06 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] JB4DR1 Deadline MAY 26 I'm ok with JMS. I didn't think you could rewrite in such short of time. Especially with Remoting and AOP just now becoming stable. I think this email thread is good because it will allow us to determine whether or not we can release. I still think there is enough functionality. Bill -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Nathan Phelps Sent: Thursday, April 03, 2003 5:48 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] JB4DR1 Deadline MAY 26 I agree that there is some great stuff in there already. However, being that the AOP transaction, security, remoting, etc. was only recently released in its first iteration, and the fact that JBoss remoting doesn't yet support true callbacks (Jeff says it is coming) there is simply no way I can deliver the new JMS implementation BUILT ON TOP of these services by May 5th! And I'm going to be out basically two weeks between now and then with customers as I know others will be as well. Since the whole point of the JMS rewrite is to take advantage of the core JBoss AOP services, I haven't really had that much time to do so since the services have only recently been released. Therefore, I expect that a May 26th release will ONLY INCLUDE THE OLD JMS CODE which is currently in HEAD. It is the only option with a May 5th deadline in my opinion. If everyone
RE: [JBoss-dev] JBoss remoting callbacks [was JB4DR1 Deadline MAY 26]
I think Bill and I need to come up with a generic enough AOP remoting with callbacks (which we have a start of) and provide that as part of the Invocation to interceptors so that the J2EE services can just use that w/o having to know anything about the remoting parts. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Nathan Phelps Sent: Friday, April 04, 2003 10:23 AM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] JBoss remoting callbacks [was JB4DR1 Deadline MAY 26] I question if A JMSServerInvocationHandler is even necessary (along with the JMS Subsystem) if Bill exposes the callbacks via the AOP remoting framework. Frankly, I have the same thought about all the subsystems as I know EJB for instance will also being using the AOP framework and therefore the AOPServerInvocationHandler. I know you guys have a JMX subsystem which you have used to implement JMX remoting, but if you decide to refactor that to use the AOP framework that subsystem wouldn't be necessary either as far as I understand it. What I'm getting at is that it is my understanding that the future of J2EE flavored services on JBoss will be built on top of the AOP framework, and therefore AOP remoting is going to be the only InvocationHandler used because it is what gives us the modern interceptor stack. Bill, am I correct? Thanks, Nathan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tom Elrod Sent: Friday, April 04, 2003 1:05 AM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] JBoss remoting callbacks [was JB4DR1 Deadline MAY 26] Guess Jeff beat me to it ;) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Tom Elrod Sent: Friday, April 04, 2003 1:49 AM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] JBoss remoting callbacks [was JB4DR1 Deadline MAY 26] Jeff made the fix last night and I have not looked at the code yet (he still has it local while we are testing that and some other fixes out). However, my understanding from Jeff is that the invoker client passes its locator to the invoker server if it wishes to receive callbacks. The invoker server will then use that for establishing the connection back to the client to send notifications (callbacks). Given this, it will be pretty easy to make it so the calling code can give the client invoker the locator to use for callbacks, which it then gives the invoker server (and will use its own by default as is now). I can put this in this weekend (if Jeff doesn't beat me to it). It sounds like there won't be enough time to include JMS as one of the invoker transport before the deadline. However, I would personally be interested in working with you on it. Depending on how soon you will have time to start on it, might be wise to make a branch just for the JMS transport, until JB4DR1. -Tom -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Nathan Phelps Sent: Thursday, April 03, 2003 11:44 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] JB4DR1 Deadline MAY 26 Did you guys end up doing it in such a way so that you can use one protocol one way and another protocol the other way like you had mentioned? Secondly, what is really going to be cool when we expose this via AOP remoting... Bill, what are your plans for that? Thanks, Nathan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeff Haynie Sent: Thursday, April 03, 2003 8:21 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] JB4DR1 Deadline MAY 26 Jboss Remoting callbacks are in - I wil commit in the next day or so when tom and I finish testing. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bill Burke Sent: Thursday, April 03, 2003 6:06 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] JB4DR1 Deadline MAY 26 I'm ok with JMS. I didn't think you could rewrite in such short of time. Especially with Remoting and AOP just now becoming stable. I think this email thread is good because it will allow us to determine whether or not we can release. I still think there is enough functionality. Bill -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Nathan Phelps Sent: Thursday, April 03, 2003 5:48 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] JB4DR1 Deadline MAY 26 I agree that there is some great stuff in there already. However, being that the AOP transaction, security, remoting, etc. was only recently released in its first iteration, and the fact that JBoss remoting doesn't yet support true callbacks (Jeff says it is coming) there is simply no way I can deliver the new JMS implementation BUILT ON TOP of these services by May
Re: Why the forums suck (Was: Re: [JBoss-dev] AOP versioned ACIDobjects 1st iteration)
Scott M Stark wrote: I agree with everything you say which is why I only read the forums when I have to. Pitch in to help Julien create something useable. Newsserver with web interface through forums for those who can use only http? --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] JBoss remoting callbacks [was JB4DR1 Deadline MAY 26]
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Nathan Phelps Sent: Friday, April 04, 2003 10:23 AM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] JBoss remoting callbacks [was JB4DR1 Deadline MAY 26] I question if A JMSServerInvocationHandler is even necessary (along with the JMS Subsystem) if Bill exposes the callbacks via the AOP remoting framework. Frankly, I have the same thought about all the subsystems as I know EJB for instance will also being using the AOP framework and therefore the AOPServerInvocationHandler. I know you guys have a JMX subsystem which you have used to implement JMX remoting, but if you decide to refactor that to use the AOP framework that subsystem wouldn't be necessary either as far as I understand it. What I'm getting at is that it is my understanding that the future of J2EE flavored services on JBoss will be built on top of the AOP framework, and therefore AOP remoting is going to be the only InvocationHandler used because it is what gives us the modern interceptor stack. Bill, am I correct? I'm not sure yet. I hope JMX and AOP and everybody else could use the same Invocation object and Interceptor interfaces, but JMX may have other requirements that require its own Handler. Iteration will allow us to explore the possibilities. Thanks, Nathan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tom Elrod Sent: Friday, April 04, 2003 1:05 AM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] JBoss remoting callbacks [was JB4DR1 Deadline MAY 26] Guess Jeff beat me to it ;) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Tom Elrod Sent: Friday, April 04, 2003 1:49 AM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] JBoss remoting callbacks [was JB4DR1 Deadline MAY 26] Jeff made the fix last night and I have not looked at the code yet (he still has it local while we are testing that and some other fixes out). However, my understanding from Jeff is that the invoker client passes its locator to the invoker server if it wishes to receive callbacks. The invoker server will then use that for establishing the connection back to the client to send notifications (callbacks). Given this, it will be pretty easy to make it so the calling code can give the client invoker the locator to use for callbacks, which it then gives the invoker server (and will use its own by default as is now). I can put this in this weekend (if Jeff doesn't beat me to it). It sounds like there won't be enough time to include JMS as one of the invoker transport before the deadline. However, I would personally be interested in working with you on it. Depending on how soon you will have time to start on it, might be wise to make a branch just for the JMS transport, until JB4DR1. -Tom -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Nathan Phelps Sent: Thursday, April 03, 2003 11:44 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] JB4DR1 Deadline MAY 26 Did you guys end up doing it in such a way so that you can use one protocol one way and another protocol the other way like you had mentioned? Secondly, what is really going to be cool when we expose this via AOP remoting... Bill, what are your plans for that? Thanks, Nathan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeff Haynie Sent: Thursday, April 03, 2003 8:21 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] JB4DR1 Deadline MAY 26 Jboss Remoting callbacks are in - I wil commit in the next day or so when tom and I finish testing. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bill Burke Sent: Thursday, April 03, 2003 6:06 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] JB4DR1 Deadline MAY 26 I'm ok with JMS. I didn't think you could rewrite in such short of time. Especially with Remoting and AOP just now becoming stable. I think this email thread is good because it will allow us to determine whether or not we can release. I still think there is enough functionality. Bill -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Nathan Phelps Sent: Thursday, April 03, 2003 5:48 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] JB4DR1 Deadline MAY 26 I agree that there is some great stuff in there already. However, being that the AOP transaction, security, remoting, etc. was only recently released in its first iteration, and the fact that JBoss remoting doesn't yet support true callbacks (Jeff says it is coming) there is simply no way
Re: [JBoss-dev] Does clustering work on OS X?
I commented out that code. Can you try HEAD on that box? The way I got it to hang was to start all, run tests-unit (which worked great), and when the test completed, I just pressed ctrl^C in the console. -dain On Friday, April 4, 2003, at 12:04 AM, Scott M Stark wrote: 3.2 works fine on the same box/JDK. I'm clustering web sessions just fine. Scott Stark Chief Technology Officer JBoss Group, LLC - Original Message - From: Dain Sundstrom [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, April 03, 2003 1:13 PM Subject: Re: [JBoss-dev] Does clustering work on OS X? Hey that is my code Is it not even starting for you? I can remove the ObjectCopier service until I figure out why it is hanging? I don't see why this would effect shutdown. Does this happen when you run the default configuration. Is it a problem to reference awt classes like Color from the server? I can remove all awt references from these classes. I was just trying to support copying of all data objects included in the JDK. -dain --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Why is JDOM version in JBoss so old
Because there has been no reason to update it apparently. On head jdom should be dropped. I'll update 3.2 to b8. -- Scott Stark Chief Technology Officer JBoss Group, LLC Colin Sampaleanu wrote: Is there are particular reason JBoss ships with what appears to be the almost 2 year old JDOM b7, instead of the 'current' (about a year old) b8? I've done a search through the mailing lists and couldn't find any reference to this. Upgrading the version in /lib to b8 seems to resolve the MethodNotFoundError my app was getting since it expected b8, without apparently adversely affecting JBoss, but it is still annoying to have to patch JBoss like this. Regards, Colin --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Why is JDOM version in JBoss so old
Is there something that replaces JDOM in 4.x? JDOM can make XML experts out of dummies, and if you're working with XML-based apps, it's nice to have in the server classpath. Scott Stark wrote: ... On head jdom should be dropped. --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Why is JDOM version in JBoss so old
dom4j or perhaps even a metadata service. I'm getting tired of seeing N different sets of xml parser api code spread throughout core components that should not be tied to xml. Tom Coleman wrote: Is there something that replaces JDOM in 4.x? JDOM can make XML experts out of dummies, and if you're working with XML-based apps, it's nice to have in the server classpath. Scott Stark wrote: ... On head jdom should be dropped. --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development -- Scott Stark Chief Technology Officer JBoss Group, LLC --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Why is JDOM version in JBoss so old
yes the replacment is dom4j. Check it out at dom4j.org Regards, Hiram --- Tom Coleman [EMAIL PROTECTED] wrote: Is there something that replaces JDOM in 4.x? JDOM can make XML experts out of dummies, and if you're working with XML-based apps, it's nice to have in the server classpath. Scott Stark wrote: ... On head jdom should be dropped. --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development __ Do you Yahoo!? Yahoo! Tax Center - File online, calculators, forms, and more http://tax.yahoo.com --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 4-April-2003
JBoss daily test results SUMMARY Number of tests run: 1223 Successful tests: 1217 Errors:3 Failures: 3 [time of test: 2003-04-04.20-54 GMT] [java.version: 1.3.1_06] [java.vendor: Sun Microsystems Inc.] [java.vm.version: 1.3.1_06-b01] [java.vm.name: Java HotSpot(TM) Client VM] [java.vm.info: mixed mode] [os.name: Windows 2000] [os.arch: x86] [os.version: 5.0] Useful resources: - http://bliss.jboss.org/~starksm/Branch_3_2/2003-04-04.20-54 for the junit report of this test. NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. It is assumed that whoever makes change(s) to jboss that break the test will be fixing the test or jboss, as appropriate! DETAILS OF ERRORS Suite: StatefulSessionUnitTestCase Test:testStrictPooling(org.jboss.test.cts.test.StatefulSessionUnitTestCase) Type:failure Exception: junit.framework.AssertionFailedError Message: SessionInvoker.runEx != null - Suite: LargeMessageUnitTestCase Test:testUILLargeMessage(org.jboss.test.jbossmq.test.LargeMessageUnitTestCase) Type:failure Exception: junit.framework.AssertionFailedError Message: We should not get a ping exception because it should pong every chunk: org.jboss.mq.SpyJMSException: Connection Failed; - nested throwable: (java.io.IOException: ping timeout.) - Suite: RollBackUnitTestCase Test: testAsynchDurableTopicReceiveRollBack(org.jboss.test.jbossmq.test.RollBackUnitTestCase) Type:failure Exception: junit.framework.AssertionFailedError Message: Topic should be full - Suite: MissingClassUnitTestCase Test: testDeployServiceWithoutClass(org.jboss.test.jmx.test.MissingClassUnitTestCase) Type:error Exception: org.jboss.deployment.DeploymentException Message: create operation failed for package file:/C:/cvs/JBoss3.2/jboss-3.2/testsuite/output/lib/missingclass-service.xml; - nested throwable: (javax.management.InstanceNotFoundException: jboss.test:name=missingclasstest is not registered.) - Suite: JSR77SpecUnitTestCase Test:testNavigation(org.jboss.test.management.test.JSR77SpecUnitTestCase) Type:error Exception: javax.management.InstanceNotFoundException Message: jboss.management.local:J2EEApplication=cts-v1cmp.ear,J2EEServer=Local,j2eeType=EJBModule,name=cts-v1cmp.jar is not registered. - Suite: SRPUnitTestCase Test:testEchoArgs(org.jboss.test.security.test.SRPUnitTestCase) Type:error Exception: java.rmi.ServerError Message: Error occurred in server thread; nested exception is: java.lang.NoClassDefFoundError: Ljavax/crypto/Cipher; - --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Subscribe to the list
Go to the source forge jboss project page and find the list section to subscribe. Angela O'Connell wrote: Hi, Could you please tell me how to subscribe to this list for JBOSS-Development? Thanks, Angela --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development -- Scott Stark Chief Technology Officer JBoss Group, LLC --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Does clustering work on OS X?
With that change it starts up and and shuts down fine. -- Scott Stark Chief Technology Officer JBoss Group, LLC Dain Sundstrom wrote: I commented out that code. Can you try HEAD on that box? The way I got it to hang was to start all, run tests-unit (which worked great), and when the test completed, I just pressed ctrl^C in the console. -dain --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-715680 ] Incorrect jboss-service-3-2.dtd
Bugs item #715680, was opened at 2003-04-04 18:31 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=715680group_id=22866 Category: JBossCMP Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: Han Ming ONG (hanming) Assigned to: Nobody/Anonymous (nobody) Summary: Incorrect jboss-service-3-2.dtd Initial Comment: I know that jboss-service-3-2.dtd is not used to validate any XML file but it is best to keep it correct. This concerns the element depends. Here's what David Jencks said: we do not have a dtd for *-service files because attributes can have xml element values. AFAIK the only way to cater to this is with namespaces and xml schema. We may need to do this for jboss 4. basically... depends optional-attribute-name=foo[object name or another mbean dd]/depends I have the patch here. Thanks! %cvs diff -u jboss-service_3_2.dtd /Users/Shared/proj/jboss-3.2/DTDs Index: jboss-service_3_2.dtd === RCS file: /cvsroot/jboss/jboss/src/resources/org/jboss/metadata/jboss-service_3_2.dtd,v retrieving revision 1.2 diff -u -r1.2 jboss-service_3_2.dtd --- jboss-service_3_2.dtd 20 Mar 2003 23:10:48 - 1.2 +++ jboss-service_3_2.dtd 5 Apr 2003 01:54:55 - @@ -123,7 +123,7 @@ depends optional-attribute-name=yNamedomain:name=y/depends /mbean -- -!ELEMENT depends (#PCDATA) +!ELEMENT depends (#PCDATA | mbean) !-- The optional-attribute-name attribute specifies the attribute name which should be populated with the JMX ObjectName of the depends element. This allows an mbean to have access to the name of the mbean on which -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=715680group_id=22866 --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-715680 ] Incorrect jboss-service-3-2.dtd
Bugs item #715680, was opened at 2003-04-04 18:31 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=715680group_id=22866 Category: JBossCMP Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: Han Ming ONG (hanming) Assigned to: Nobody/Anonymous (nobody) Summary: Incorrect jboss-service-3-2.dtd Initial Comment: I know that jboss-service-3-2.dtd is not used to validate any XML file but it is best to keep it correct. This concerns the element depends. Here's what David Jencks said: we do not have a dtd for *-service files because attributes can have xml element values. AFAIK the only way to cater to this is with namespaces and xml schema. We may need to do this for jboss 4. basically... depends optional-attribute-name=foo[object name or another mbean dd]/depends I have the patch here. Thanks! %cvs diff -u jboss-service_3_2.dtd /Users/Shared/proj/jboss-3.2/DTDs Index: jboss-service_3_2.dtd === RCS file: /cvsroot/jboss/jboss/src/resources/org/jboss/metadata/jboss-service_3_2.dtd,v retrieving revision 1.2 diff -u -r1.2 jboss-service_3_2.dtd --- jboss-service_3_2.dtd 20 Mar 2003 23:10:48 - 1.2 +++ jboss-service_3_2.dtd 5 Apr 2003 01:54:55 - @@ -123,7 +123,7 @@ depends optional-attribute-name=yNamedomain:name=y/depends /mbean -- -!ELEMENT depends (#PCDATA) +!ELEMENT depends (#PCDATA | mbean) !-- The optional-attribute-name attribute specifies the attribute name which should be populated with the JMX ObjectName of the depends element. This allows an mbean to have access to the name of the mbean on which -- Comment By: Han Ming ONG (hanming) Date: 2003-04-04 18:37 Message: Logged In: YES user_id=741972 See oracle-service.xml as an example. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=715680group_id=22866 --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-715680 ] Incorrect jboss-service-3-2.dtd
Bugs item #715680, was opened at 2003-04-04 18:31 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=715680group_id=22866 Category: JBossServer Group: v3.2 Status: Closed Resolution: Fixed Priority: 5 Submitted By: Han Ming ONG (hanming) Assigned to: Scott M Stark (starksm) Summary: Incorrect jboss-service-3-2.dtd Initial Comment: I know that jboss-service-3-2.dtd is not used to validate any XML file but it is best to keep it correct. This concerns the element depends. Here's what David Jencks said: we do not have a dtd for *-service files because attributes can have xml element values. AFAIK the only way to cater to this is with namespaces and xml schema. We may need to do this for jboss 4. basically... depends optional-attribute-name=foo[object name or another mbean dd]/depends I have the patch here. Thanks! %cvs diff -u jboss-service_3_2.dtd /Users/Shared/proj/jboss-3.2/DTDs Index: jboss-service_3_2.dtd === RCS file: /cvsroot/jboss/jboss/src/resources/org/jboss/metadata/jboss-service_3_2.dtd,v retrieving revision 1.2 diff -u -r1.2 jboss-service_3_2.dtd --- jboss-service_3_2.dtd 20 Mar 2003 23:10:48 - 1.2 +++ jboss-service_3_2.dtd 5 Apr 2003 01:54:55 - @@ -123,7 +123,7 @@ depends optional-attribute-name=yNamedomain:name=y/depends /mbean -- -!ELEMENT depends (#PCDATA) +!ELEMENT depends (#PCDATA | mbean) !-- The optional-attribute-name attribute specifies the attribute name which should be populated with the JMX ObjectName of the depends element. This allows an mbean to have access to the name of the mbean on which -- Comment By: Scott M Stark (starksm) Date: 2003-04-04 18:50 Message: Logged In: YES user_id=175228 Its been updated. -- Comment By: Han Ming ONG (hanming) Date: 2003-04-04 18:37 Message: Logged In: YES user_id=741972 See oracle-service.xml as an example. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=715680group_id=22866 --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Help needed for running client EJB
I m trying to solve interest EJB example provided with Jboss documentation. This is wht i m getting when i run interest client Buildfile: build.xml validate-servlet: validate-jboss: fail_if_not_valid: init: [echo] Using JBoss directory=C:\jboss [echo] Using base classpath=C:\jboss\client\jboss-j2ee.jar;C:\jboss\client\jaas.jar;C:\jboss\client\jbosssx-client.jar;C:\jboss\client\jboss-client.jar;C:\jboss\client\jnp-client.jar;C:\jboss\examples\COULD_NOT_FIND_SERVLET_JAR [echo] Using Source directory=C:\jboss\examples [echo] Using Build directory=C:\jboss\examples/build-examples intro-interest-client: compile: interest-client: [java] java.lang.NoClassDefFoundError: org/jboss/logging/Logger [java] at org.jnp.interfaces.NamingContext.clinit(NamingContext.java:95) [java] at org.jnp.interfaces.NamingContextFactory.getInitialContext(NamingContextFactory.java:42) [java] at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662) [java] at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243) [java] at javax.naming.InitialContext.init(InitialContext.java:219) [java] at javax.naming.InitialContext.init(InitialContext.java:175) [java] at org.jboss.docs.interest.InterestClient.main(InterestClient.java:27) [java] Exception in thread "main" [java] Java Result: 1 BUILD SUCCESSFUL Pls help !! Tx Anukampa
