Patches item #493604, was opened at 2001-12-15 00:00
You can respond by visiting:
http://sourceforge.net/tracker/?func=detailatid=376687aid=493604group_id=22866
Category: JBossServer
Group: v3.0 Rabbit Hole (unstable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Allen Fogleson
JBoss daily test results
SUMMARY
Number of tests run: 203
Successful tests: 203
Errors:0
Failures: 0
[time of test: 15 December 2001 9:12 GMT]
[java.version:
User: ejort
Date: 01/12/15 03:24:10
Modified:src/main/javax/management AttributeList.java
Log:
More Javadoc
Revision ChangesPath
1.2 +107 -10 jmx/src/main/javax/management/AttributeList.java
Index: AttributeList.java
JBoss daily test results
SUMMARY
Number of tests run: 129
Successful tests: 129
Errors:0
Failures: 0
[time of test: 15 December 2001 11:58 GMT]
[java.version:
=
==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
=
HERE ARE THE LAST 50 LINES OF THE LOG FILE
Hello,
The org.jboss.Shutdown class does
User: ejort
Date: 01/12/15 04:07:44
Modified:src/main/javax/management AttributeNotFoundException.java
BadAttributeValueExpException.java
BadBinaryOpValueExpException.java
BadStringOperationException.java
Log:
Scott M Stark wrote:
...
No, java.security.MessageDigest is standard in JDK 1.3. MACs are part
of JCA. You add new digest algorithms by supplying a MessageDigestSpi
implementation and registering it using the standard security provider
mechanism.
OK. I think we're talking at cross
Hi,
I started watching your posts about this before.
But the thread got very long so I stopped paying
attention. Sorry :-(
I understand it and like it.
One mbean per deployment, with a unified deployer creating and configuring :-)
One question. How do you plug new behaviour into this
unified
Hello,
Sorry about this e-mail: forget about it... I was actually deploying
testbean2.jar but beans are contained in testbean.jar... links to the target
JNDI names were done but the actual beans were not deployed.
Cheers,
Sacha
I see a current behaviour with
User: ejort
Date: 01/12/15 08:24:36
Modified:src/main/javax/management
InvalidAttributeValueException.java
Log:
More javadoc
Revision ChangesPath
1.2 +35 -7
jmx/src/main/javax/management/InvalidAttributeValueException.java
If i try to run the EJBVerifier.bat i get an ClassNotFoundException , i look
into the bat and i see that the classpath is wrong starting from the
jboss-dist/bin directory.
if i look into the the main class of the verifier is see no real
implementation. (it looks like the EJBVerifier should be
User: ejort
Date: 01/12/15 09:00:56
Modified:src/main/javax/management JMException.java
JMRuntimeException.java
Log:
More javadoc
Revision ChangesPath
1.2 +38 -6 jmx/src/main/javax/management/JMException.java
Index:
Formatting the digest into a string is another dimension that
we would have to provide. The hash algorithm should be one login module
option, and the representation of the digest another. This should
include
'raw' for the raw digest byte[], 'base64' and 'hex'.
Won't the 'raw'
User: ejort
Date: 01/12/15 09:15:05
Modified:src/main/javax/management ListenerNotFoundException.java
Log:
More javadoc
Revision ChangesPath
1.2 +32 -3 jmx/src/main/javax/management/ListenerNotFoundException.java
Index: ListenerNotFoundException.java
User: ejort
Date: 01/12/15 09:25:41
Modified:src/main/javax/management MBeanException.java
Log:
More javadoc
Revision ChangesPath
1.2 +48 -8 jmx/src/main/javax/management/MBeanException.java
Index: MBeanException.java
User: ejort
Date: 01/12/15 09:47:15
Modified:src/main/javax/management MBeanRegistration.java
Log:
More javadoc
Revision ChangesPath
1.2 +69 -12jmx/src/main/javax/management/MBeanRegistration.java
Index: MBeanRegistration.java
User: ejort
Date: 01/12/15 10:01:06
Modified:src/main/javax/management MBeanRegistration.java
MBeanRegistrationException.java
Log:
More javadoc
Revision ChangesPath
1.3 +2 -2 jmx/src/main/javax/management/MBeanRegistration.java
User: ejort
Date: 01/12/15 10:32:16
Modified:src/main/javax/management MalformedObjectNameException.java
Log:
More javadoc
Revision ChangesPath
1.2 +32 -8 jmx/src/main/javax/management/MalformedObjectNameException.java
Index:
User: vharcq
Date: 01/12/15 10:53:18
Modified:src/build Tag: Branch_2_4 build.bat build.sh
Log:
Update of latest JAXP libraries to make testsuite run on Branch 2.4
Revision ChangesPath
No revision
No revision
1.3.2.3
User: vharcq
Date: 01/12/15 10:53:18
Modified:lib Tag: Branch_2_4 crimson.jar jaxp.jar
Added: lib Tag: Branch_2_4 xalan.jar
Log:
Update of latest JAXP libraries to make testsuite run on Branch 2.4
Revision ChangesPath
No revision
Yet another quick thought...
Why don't we use xml namespaces for root document tags in configuration
files?
For example, the service files might look like:
!DOCTYPE jboss:service
jboss:service xmlns:jboss=http://jboss.org/;
classpath archives=.../
!-- ... --
User: ejort
Date: 01/12/15 11:40:52
Modified:src/main/javax/management NotCompliantMBeanException.java
OperationsException.java ReflectionException.java
RuntimeErrorException.java
RuntimeMBeanException.java
=
==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
=
HERE ARE THE LAST 50 LINES OF THE LOG FILE
Hello,
The org.jboss.Shutdown class does
JBoss daily test results
SUMMARY
Number of tests run: 129
Successful tests: 129
Errors:0
Failures: 0
[time of test: 16 December 2001 7:48 GMT]
[java.version:
=
==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
=
HERE ARE THE LAST 50 LINES OF THE LOG FILE
Hello,
The org.jboss.Shutdown class does
25 matches
Mail list logo
