Re: [JBoss-dev] Jboss + Junit?

2003-01-03 Thread David Jencks
There's also something Dain wrote, that I think is now in the blocks
module, for testing local interfaces.  I think it runs your junit test
inside the jboss  vm.  it's used in the cmp2 tests.

With the plain testsuite way of doing things, you have to write something
like an mbean to deploy explicitly to do your testing.  The thing Dain
wrote (as I understnad it) lets you just write tests, and takes care of
running  them in jboss.

david jencks


On 2003.01.03 00:13:01 -0500 Bill Burke wrote:
> MessageJames,
> 
> The way JBoss Unit tests work is that an EAR, SAR, EJB Jar, whatever is
> built.  The client test remotely hot-deploys the EAR, SAR, whatever, and
> then calls methods on the EJBS, MBeans, whatever to test things.
> 
> I'd really like to productize our testsuite and am looking for somebody
> to
> do this work.  The reporting, the JUnit extensions, and have example
> tests
> to show how to use the functionality and documentation.
> 
> 
> Bill Burke
> Chief Architect
> JBoss Group, LLC
> 
> 
> 
> 
> 
>   -Original Message-
>   From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of James
> Higginbotham
>   Sent: Thursday, January 02, 2003 11:57 PM
>   To: [EMAIL PROTECTED]
>   Subject: RE: [JBoss-dev] Jboss + Junit?
> 
> 
>   Bill,
> 
>   Thanks for the tip, this is some interesting stuff.. I was thinking of
> taking it one step further and constructing a TestRunner that is really
> an
> mbean. So, you could in fact deploy your ear, a jar with the unit tests,
> then through the console run a single class's tests.. I haven't quite
> figured out how to run more than one without writing either a custom
> deployer and use some extension like .junit for the jar of test class(es)
> or
> having the mbean querying the respository and finding all *Test classes
> deployed. This way, the test can actually be on the server side and
> invoke
> local methods. You could also hot deploy your ear and your unit tests and
> run them again without shutting down. Thoughts? Is this in there and I
> just
> missed it? Or, do I just have way too much time to think about
> applications
> of JBoss? I'm just tired of the same ol' J2EE applications I guess I
> really like the JBossTestSetup and assoc classes - really nice!
> 
>   James
> -Original Message-
> From: Bill Burke [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, January 02, 2003 5:08 PM
> To: [EMAIL PROTECTED]
> Subject: RE: [JBoss-dev] Jboss + Junit?
> 
> 
> Our Junit extensions support all of what you want.
> 
> Its under testsuite/...
> 
> We need somebody to document this stuff.  Somebody volunteered once,
> but
> never got back to me.
> 
> Bill
>   -Original Message-
>   From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of James
> Higginbotham
>   Sent: Thursday, January 02, 2003 4:23 PM
>   To: [EMAIL PROTECTED]
>   Subject: [JBoss-dev] Jboss + Junit?
> 
> 
>   Hi,
> 
>   I wanted to drop this note on the dev list since this question is
> in
> regards to a previous posting on the dev list. I had heard that the jboss
> team had made some extensions to Junit, is that right? If so, what were
> they
> in a nutshell? Can someone point me to the source as well?
> 
>   Also, does anyone know if there is a project out that provides
> Junit
> as an mbean such that unit tests can be deployed and run within the jboss
> runtime and test local EJB methods, utilize hot deploy (like the junit
> custom classloader concept), etc? I was just wondering if anyone had
> considered such a thing, knowing full well that it would be a JB only
> thing
> and that more cross-server solutions have been made (Cactus for one). It
> seems to be that it would be a more beneficial solution - write, compile,
> deploy, test within one VM in theory, possibly kicked off from the
> beanshell
> in Emacs (David should like that one!). Ok, so I'm dreaming a little..
> Thoughts?
> 
>   James
> 
> 
> 
> Message
> 
> 
> 
>  size=2>James,
>  size=2> 
>  size=2>The 
> way JBoss Unit tests work is that an EAR, SAR, EJB Jar, whatever is
> built.  
> The client test remotely hot-deploys the EAR, SAR, whatever, and
> then calls 
> methods on the EJBS, MBeans, whatever to test things.
>  size=2> 
>  size=2>I'd 
> really like to productize our testsuite and am looking for somebody to do
> this 
> work.  The reporting, the JUnit extensions, and have example tests
> to show 
> how to use the functionality and documentation.
>  size=2> 
> 
> Bill BurkeChief
> ArchitectJBoss 
> Group, LLC
>  size=2> 
>  size=2> 
>  style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #ff 2px
> solid; MARGIN-RIGHT: 0px">
>  size=2>-Original Message-From: 
>   [EMAIL PROTECTED] 
>   [mailto:[EMAIL PROTECTED]]On Behalf Of 
>   James HigginbothamSent: Thursday, January 02, 2003 11:57
> 
>   PMTo: [EMAIL PROTECTED]Subject:
> 
>   RE: [JBoss-d

[JBoss-dev] Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 3-January-2003

2003-01-03 Thread scott . stark


JBoss daily test results

SUMMARY

Number of tests run:   1044



Successful tests:  1035

Errors:7

Failures:  2





[time of test: 2003-01-04.03-12 GMT]
[java.version: 1.4.1_01]
[java.vendor: Sun Microsystems Inc.]
[java.vm.version: 1.4.1_01-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://users.jboss.org/~starksm/Branch_3_2/2003-01-04.03-12 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:   DeployXMBeanUnitTestCase
Test:testDeployUserXMBean(org.jboss.test.jmx.test.DeployXMBeanUnitTestCase)
Type:error
Exception:   org.jboss.deployment.DeploymentException
Message: create operation failed for package 
file:/C:/usr/JBoss3.2/jboss-3.2/testsuite/output/lib/user-xmbean.sar; - nested 
throwable: (org.jboss.deployment.DeploymentException: Error parsing the XML file: 
org.xml.sax.SAXParseException: Attribute "persistPolicy" with value "Never" must have 
a value from the list "NEVER ONUPDATE NOMOREOFTENTHAN ONTIMER ".; - nested throwable: 
(javax.management.NotCompliantMBeanException: Error parsing the XML file: 
org.xml.sax.SAXParseException: Attribute "persistPolicy" with value "Never" must have 
a value from the list "NEVER ONUPDATE NOMOREOFTENTHAN ONTIMER ".))
-



Suite:   JarInSarJSR77UnitTestCase
Test:
testFakeParentCreatedAndRemoved(org.jboss.test.jmx.test.JarInSarJSR77UnitTestCase)
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: fakeApp jsr-77 mbean is still present
-



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:/usr/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:   java.lang.NullPointerException
Message: 
-



Suite:   SimpleUnitTestCase
Test:testSecureHttpInvoker(org.jboss.test.naming.test.SimpleUnitTestCase)
Type:error
Exception:   javax.security.auth.login.LoginException
Message: Missing users.properties file.
-



Suite:   SimpleUnitTestCase
Test:testLoginInitialContext(org.jboss.test.naming.test.SimpleUnitTestCase)
Type:error
Exception:   javax.naming.AuthenticationException
Message: Failed to login using protocol=testLoginInitialContext
-



Suite:   SecurePerfStressTestCase
Test:java.lang.SecurityException: Configuration Error:  Line 0: expected [{], 
found [null]
Type:error
Exception:   java.lang.SecurityException
Message: Configuration Error:  Line 0: expected [{], found [null]
-



Suite:   EJBSpecUnitTestCase
Test:testMDBRunAs(org.jboss.test.security.test.EJBSpecUnitTestCase)
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Recevied exception reply, info=Failed, ex=EJBException:; nested exception 
is:   javax.ejb.EJBException: checkSecurityAssociation; CausedByException is:  
Authentication exception, principal=null
-



Suite:   HttpsUnitTestCase
Test:testHttpsURL(org.jboss.test.security.test.HttpsUnitTestCase)
Type:error
Exception:   java.io.IOException
Message: Failed to get SSLContext for TLS algorithm
-




---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



Re: [JBoss-dev] 3.0.5RC1 available

2003-01-03 Thread Adam Heath
On Fri, 3 Jan 2003, Scott M Stark wrote:

> Runs fine for me on RedHat 8.0 with Sun JDK 1.4.1_01. It looks like whatever JDK
> you are using is botching the search for a jar protocol handler, which does not 
>exist.

bash-2.05b$ /usr/lib/j2se/1.3/bin/java -version
java version "1.3.1"
Java(TM) 2 Runtime Environment, Standard Edition (build Blackdown-1.3.1-02b-FCS)
Java HotSpot(TM) Client VM (build Blackdown-1.3.1_02b-FCS, mixed mode) 1.3.1

Debian unstable(doubt this part matters much).




---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



Re: [JBoss-dev] 3.0.5RC1 available

2003-01-03 Thread Scott M Stark
Runs fine for me on RedHat 8.0 with Sun JDK 1.4.1_01. It looks like whatever JDK
you are using is botching the search for a jar protocol handler, which does not exist.


Scott Stark
Chief Technology Officer
JBoss Group, LLC


- Original Message - 
From: "Adam Heath" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Friday, January 03, 2003 3:59 PM
Subject: Re: [JBoss-dev] 3.0.5RC1 available


> On Tue, 24 Dec 2002, Scott M Stark wrote:
> 
> > A 3.0.5 pre-release has been made available for testing. The primary purpse
> > is to get feedback about the latest class loader changes made to address
> > the outstanding IllegalAccessErrors. If you have experienced problems
> > with IllegalAccessErrors or LinkageErrors please try this version or the
> > 3.2.0beta3 version. Both are available from SourceForge here:
> >
> > http://sourceforge.net/project/showfiles.php?group_id=22866
> >
> > If you experience any class loading related problems follow the bug
> > reporting proceedure described in the release notes:
> > http://sourceforge.net/project/shownotes.php?release_id=129789
> 
> Downloaded the 3.0.5RC1-tomcat4.1.18 version.  Unpacked.  did bin/run.sh.  Got
> this error:
> 
> 17:58:11,026 ERROR [MainDeployer] could not create deployment:
> file:/home.local/adam/brainfood/jboss/3.0.5rc1/server/default/conf/jboss-servi
> ce.xml
> org.jboss.deployment.DeploymentException: instantiating
> org.jboss.varia.property.PropertyEditorManagerService failed:
> java.lang.NoClassDefFou
> ndError: org/jboss/net/protocol/jar/Handler (wrong name:
> org/jboss/varia/property/PropertyEditorManagerService); - nested throwable:
> (Runtime
> ErrorException: instantiating
> org.jboss.varia.property.PropertyEditorManagerService failed:
> java.lang.NoClassDefFoundError: org/jboss/net/pro
> tocol/jar/Handler (wrong name:
> org/jboss/varia/property/PropertyEditorManagerService)
> Cause: java.lang.NoClassDefFoundError: org/jboss/net/protocol/jar/Handler
> (wrong name: org/jboss/varia/property/PropertyEditorManagerService)
> )
> 
> Running this shell snippet:
> 
> for a in `find -name '*.jar'`;do if unzip -lv $a  |grep
> org/jboss/net/protocol;then echo $a;fi;done
> 
> Find something about an njar handler, but no jar handler.
> 
> So, for me, 3.0.5RC1 is dead in the water.
> 
> 
> 
> ---
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> ___
> Jboss-development mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-development
> 


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 3-January-2003

2003-01-03 Thread scott . stark


JBoss daily test results

SUMMARY

Number of tests run:   1051



Successful tests:  1043

Errors:6

Failures:  2





[time of test: 2003-01-03.23-32 GMT]
[java.version: 1.3.1_05]
[java.vendor: Sun Microsystems Inc.]
[java.vm.version: 1.3.1_05-b02]
[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://users.jboss.org/~starksm/Branch_3_2/2003-01-03.23-32 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:   DeployXMBeanUnitTestCase
Test:testDeployUserXMBean(org.jboss.test.jmx.test.DeployXMBeanUnitTestCase)
Type:error
Exception:   org.jboss.deployment.DeploymentException
Message: create operation failed for package 
file:/C:/usr/JBoss3.2/jboss-3.2/testsuite/output/lib/user-xmbean.sar; - nested 
throwable: (org.jboss.deployment.DeploymentException: Error parsing the XML file: 
org.xml.sax.SAXParseException: Attribute "persistPolicy" with value "Never" must have 
a value from the list "NEVER ONUPDATE NOMOREOFTENTHAN ONTIMER ".; - nested throwable: 
(javax.management.NotCompliantMBeanException: Error parsing the XML file: 
org.xml.sax.SAXParseException: Attribute "persistPolicy" with value "Never" must have 
a value from the list "NEVER ONUPDATE NOMOREOFTENTHAN ONTIMER ".))
-



Suite:   JarInSarJSR77UnitTestCase
Test:
testFakeParentCreatedAndRemoved(org.jboss.test.jmx.test.JarInSarJSR77UnitTestCase)
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: fakeApp jsr-77 mbean is still present
-



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:/usr/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:   java.lang.NullPointerException
Message: 
-



Suite:   SimpleUnitTestCase
Test:testSecureHttpInvoker(org.jboss.test.naming.test.SimpleUnitTestCase)
Type:error
Exception:   javax.security.auth.login.LoginException
Message: Missing users.properties file.
-



Suite:   SimpleUnitTestCase
Test:testLoginInitialContext(org.jboss.test.naming.test.SimpleUnitTestCase)
Type:error
Exception:   javax.naming.AuthenticationException
Message: Failed to login using protocol=testLoginInitialContext
-



Suite:   EJBSpecUnitTestCase
Test:testMDBRunAs(org.jboss.test.security.test.EJBSpecUnitTestCase)
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Recevied exception reply, info=Failed, ex=EJBException:; nested exception 
is:   javax.ejb.EJBException: checkSecurityAssociation; CausedByException is:  
Authentication exception, principal=null
-



Suite:   HttpsUnitTestCase
Test:testHttpsURL(org.jboss.test.security.test.HttpsUnitTestCase)
Type:error
Exception:   java.io.IOException
Message: Failed to get SSLContext for TLS algorithm
-




---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



Re: [JBoss-dev] 3.0.5RC1 available

2003-01-03 Thread Adam Heath
On Tue, 24 Dec 2002, Scott M Stark wrote:

> A 3.0.5 pre-release has been made available for testing. The primary purpse
> is to get feedback about the latest class loader changes made to address
> the outstanding IllegalAccessErrors. If you have experienced problems
> with IllegalAccessErrors or LinkageErrors please try this version or the
> 3.2.0beta3 version. Both are available from SourceForge here:
>
> http://sourceforge.net/project/showfiles.php?group_id=22866
>
> If you experience any class loading related problems follow the bug
> reporting proceedure described in the release notes:
> http://sourceforge.net/project/shownotes.php?release_id=129789

Downloaded the 3.0.5RC1-tomcat4.1.18 version.  Unpacked.  did bin/run.sh.  Got
this error:

17:58:11,026 ERROR [MainDeployer] could not create deployment:
file:/home.local/adam/brainfood/jboss/3.0.5rc1/server/default/conf/jboss-servi
ce.xml
org.jboss.deployment.DeploymentException: instantiating
org.jboss.varia.property.PropertyEditorManagerService failed:
java.lang.NoClassDefFou
ndError: org/jboss/net/protocol/jar/Handler (wrong name:
org/jboss/varia/property/PropertyEditorManagerService); - nested throwable:
(Runtime
ErrorException: instantiating
org.jboss.varia.property.PropertyEditorManagerService failed:
java.lang.NoClassDefFoundError: org/jboss/net/pro
tocol/jar/Handler (wrong name:
org/jboss/varia/property/PropertyEditorManagerService)
Cause: java.lang.NoClassDefFoundError: org/jboss/net/protocol/jar/Handler
(wrong name: org/jboss/varia/property/PropertyEditorManagerService)
)

Running this shell snippet:

for a in `find -name '*.jar'`;do if unzip -lv $a  |grep
org/jboss/net/protocol;then echo $a;fi;done

Find something about an njar handler, but no jar handler.

So, for me, 3.0.5RC1 is dead in the water.



---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] Does JRockit work yet?

2003-01-03 Thread Dain Sundstrom
Does JBoss run on JRockit yet?  I mean run for a long while without 
crashing?  I remember posts on it being broken.

-dain



---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed

2003-01-03 Thread chris

=
==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net FOR DETAILS=
=

JAVA VERSION DETAILS
java version "1.3.1_06"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_06-b01)
Java HotSpot(TM) Server VM (build 1.3.1_06-b01, mixed mode)

=

HERE ARE THE LAST 50 LINES OF THE LOG FILE

[javac] Compiling 595 source files to 
/home/jboss/jbossci/jboss-head/server/output/classes
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/ejb/EnterpriseContext.java:11:
 warning: java.security.Identity in java.security has been deprecated
import java.security.Identity;
 ^
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/ejb/EnterpriseContext.java:244:
 warning: java.security.Identity in java.security has been deprecated
  public Identity getCallerIdentity() 
 ^
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/ejb/EnterpriseContext.java:370:
 warning: java.security.Identity in java.security has been deprecated
  public boolean isCallerInRole(Identity id) 
^
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/ejb/EnterpriseContext.java:370:
 warning: java.security.Identity in java.security has been deprecated
  public boolean isCallerInRole(Identity id) 
^
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/jmx/connector/rmi/RMIConnectorImpl.java:88:
 org.jboss.jmx.connector.rmi.RMIConnectorImpl should be declared abstract; it does not 
define getDomains() in org.jboss.jmx.connector.rmi.RMIConnectorImpl
public class RMIConnectorImpl
   ^
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/jmx/connector/rmi/RMIConnectorImpl.java:88:
 warning: deserialize(java.lang.String,javax.management.ObjectName,byte[]) in 
javax.management.MBeanServer has been deprecated
public class RMIConnectorImpl
   ^
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/jmx/connector/rmi/RMIConnectorImpl.java:88:
 warning: deserialize(java.lang.String,byte[]) in javax.management.MBeanServer has 
been deprecated
public class RMIConnectorImpl
   ^
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/jmx/connector/rmi/RMIConnectorImpl.java:88:
 warning: deserialize(javax.management.ObjectName,byte[]) in 
javax.management.MBeanServer has been deprecated
public class RMIConnectorImpl
   ^
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/jmx/connector/ejb/EJBConnector.java:56:
 warning: deserialize(java.lang.String,javax.management.ObjectName,byte[]) in 
javax.management.MBeanServer has been deprecated
public class EJBConnector
   ^
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/jmx/connector/ejb/EJBConnector.java:56:
 warning: deserialize(java.lang.String,byte[]) in javax.management.MBeanServer has 
been deprecated
public class EJBConnector
   ^
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/jmx/connector/ejb/EJBConnector.java:56:
 warning: deserialize(javax.management.ObjectName,byte[]) in 
javax.management.MBeanServer has been deprecated
public class EJBConnector
   ^
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/jmx/connector/ejb/EJBConnector.java:56:
 warning: deserialize(java.lang.String,javax.management.ObjectName,byte[]) in 
javax.management.MBeanServer has been deprecated
public class EJBConnector
   ^
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/jmx/connector/ejb/EJBConnector.java:56:
 warning: deserialize(java.lang.String,byte[]) in javax.management.MBeanServer has 
been deprecated
public class EJBConnector
   ^
/home/jboss/jbossci/jboss-head/server/src/main/org/jboss/jmx/connector/ejb/EJBConnector.java:56:
 warning: deserialize(javax.management.ObjectName,byte[]) in 
javax.management.MBeanServer has been deprecated
public class EJBConnector
   ^
1 error
13 warnings

BUILD FAILED
file:/home/jboss/jbossci/jboss-head/server/build.xml:282: Compile failed; see the 
compiler error output for details.

Total time: 1 minute 29 seconds


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] Automated JBoss(Branch_3_0) Testsuite Results: 3-January-2003

2003-01-03 Thread scott . stark


JBoss daily test results

SUMMARY

Number of tests run:   1004



Successful tests:  998

Errors:5

Failures:  1





[time of test: 2003-01-03.12-19 GMT]
[java.version: 1.3.1]
[java.vendor: Apple Computer, Inc.]
[java.vm.version: 1.3.1_03-69]
[java.vm.name: Java HotSpot(TM) Client VM]
[java.vm.info: mixed mode]
[os.name: Mac OS X]
[os.arch: ppc]
[os.version: 10.2.3]

See http://users.jboss.org/~starksm/Branch_3_0/2003-01-03.12-19
for details 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:   LocalWrapperCleanupUnitTestCase
Test:
testAutoCommitOffInRemoteUserTx(org.jboss.test.jca.test.LocalWrapperCleanupUnitTestCase)
Type:error
Exception:   java.rmi.ServerException
Message: RemoteException occurred in server thread; nested exception is:   
java.rmi.ServerException: EJBException:; nested exception is:   
javax.ejb.EJBException: Row committed, autocommit still on!
-



Suite:   MissingClassUnitTestCase
Test:
testDeployServiceWithoutClass(org.jboss.test.jmx.test.MissingClassUnitTestCase)
Type:error
Exception:   org.jboss.deployment.DeploymentException
Message: jboss.test:name=missingclasstest is not registered.; - nested throwable: 
(javax.management.InstanceNotFoundException: jboss.test:name=missingclasstest is not 
registered.)
-



Suite:   SimpleUnitTestCase
Test:testSecureHttpInvoker(org.jboss.test.naming.test.SimpleUnitTestCase)
Type:error
Exception:   javax.security.auth.login.LoginException
Message: Missing users.properties file.
-



Suite:   SimpleUnitTestCase
Test:testLoginInitialContext(org.jboss.test.naming.test.SimpleUnitTestCase)
Type:error
Exception:   javax.naming.AuthenticationException
Message: Failed to login using protocol=testLoginInitialContext
-



Suite:   HttpsUnitTestCase
Test:testHttpsURL(org.jboss.test.security.test.HttpsUnitTestCase)
Type:error
Exception:   java.io.IOException
Message: Failed to get SSLContext for TLS algorithm
-



Suite:   BeanStressTestCase
Test:testDeadLockFromClient(org.jboss.test.deadlock.test.BeanStressTestCase)
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: expected a client deadlock for AB BA
-




---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] [ jboss-Bugs-661682 ] 3.1 dtd missing from XmlFileLoader

2003-01-03 Thread SourceForge.net
Bugs item #661682, was opened at 2003-01-03 17:38
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=661682&group_id=22866

Category: JBossServer
Group: v3.2
Status: Open
Resolution: None
>Priority: 6
Submitted By: Oskari Kettunen (aok)
Assigned to: Nobody/Anonymous (nobody)
Summary: 3.1 dtd missing from XmlFileLoader

Initial Comment:
Hello gents,

Somewhere along the way of fitting together xdoclet1.2 
and jboss3.2 I ran into a stalemate of descriptors ad 
dtds fixed easiest by adding the 3.1 dtd to 
XmlFileLoader.

I suspect you might have some reason for keeping it out 
of 3.2, but in case this is just an oversight, attached is a 
one-line diff.

Oskari Kettunen,
Krocus Communications OY
Finland

--

>Comment By: Oskari Kettunen (aok)
Date: 2003-01-03 17:39

Message:
Logged In: YES 
user_id=558871

this file upload thingy is taking a piss at me...

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=661682&group_id=22866


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] [ jboss-Bugs-661682 ] 3.1 dtd missing from XmlFileLoader

2003-01-03 Thread SourceForge.net
Bugs item #661682, was opened at 2003-01-03 17:38
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=661682&group_id=22866

Category: JBossServer
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Oskari Kettunen (aok)
Assigned to: Nobody/Anonymous (nobody)
Summary: 3.1 dtd missing from XmlFileLoader

Initial Comment:
Hello gents,

Somewhere along the way of fitting together xdoclet1.2 
and jboss3.2 I ran into a stalemate of descriptors ad 
dtds fixed easiest by adding the 3.1 dtd to 
XmlFileLoader.

I suspect you might have some reason for keeping it out 
of 3.2, but in case this is just an oversight, attached is a 
one-line diff.

Oskari Kettunen,
Krocus Communications OY
Finland

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=661682&group_id=22866


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



RE: [JBoss-dev] Jboss + Junit?

2003-01-03 Thread Scott Stirling
Hi,

I wrote an MBean JUnit TestRunner for JRun 4, which is JMX-based.  I did it
for exactly the reasons you described below.  I'll see if I can dig it up.

Best,
Scott Stirling

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of James
Higginbotham

Bill,

Thanks for the tip, this is some interesting stuff.. I was thinking of
taking it one step further and constructing a TestRunner that is really an
mbean. So, you could in fact deploy your ear, a jar with the unit tests,
then through the console run a single class's tests.. I haven't quite
figured out how to run more than one without writing either a custom
deployer and use some extension like .junit for the jar of test class(es) or
having the mbean querying the respository and finding all *Test classes
deployed. This way, the test can actually be on the server side and invoke
local methods. You could also hot deploy your ear and your unit tests and
run them again without shutting down. Thoughts? Is this in there and I just
missed it? Or, do I just have way too much time to think about applications
of JBoss? I'm just tired of the same ol' J2EE applications I guess I
really like the JBossTestSetup and assoc classes - really nice!

James




---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development