[JBoss-dev] CVS update: jbosstest/src/resources/jmx test-service.xml
User: d_jencks Date: 02/04/06 21:26:00 Modified:src/resources/jmx test-service.xml Log: updated to new mbeans used in test Revision ChangesPath 1.6 +60 -25jbosstest/src/resources/jmx/test-service.xml Index: test-service.xml === RCS file: /cvsroot/jboss/jbosstest/src/resources/jmx/test-service.xml,v retrieving revision 1.5 retrieving revision 1.6 diff -u -r1.5 -r1.6 --- test-service.xml 3 Jan 2002 04:01:02 - 1.5 +++ test-service.xml 7 Apr 2002 05:25:59 - 1.6 @@ -6,34 +6,69 @@ server - !--classpath archive=jbosscx.sar/classpath-- - + mbean code=org.jboss.resource.connectionmanager.LocalTxConnectionManager name=jboss.test:service=LocalTxCM +!--make the rar deploy! hack till better deployment-- +dependsjboss.jca:service=RARDeployer/depends -!--This ds goes with hypersonic, so will work with default installation-- - mbean code=org.jboss.resource.ConnectionFactoryLoader name=TestDomain:service=ConnectionFactoryLoader,name=DeployTestDS -attribute name=ManagedConnectionFactoryPropertiesConnectionURL=jdbc:hsqldb:hsql://localhost:1476 - DriverClass=org.hsqldb.jdbcDriver/attribute -attribute name=JndiNameDeployTestDS/attribute -attribute name=TransactionManagerNamejava:/TransactionManager/attribute -!--Anonymous depends to database being started -- -dependsjboss:service=Hypersonic/depends +depends optional-attribute-name=ManagedConnectionFactoryName + !--embedded mbean-- + mbean code=org.jboss.resource.connectionmanager.RARDeployment name=jboss.test:service=LocalTxDS +!--hack-- +depends optional-attribute-name=OldRarDeploymentjboss.jca:service=RARDeployment,name=Minerva JDBC LocalTransaction ResourceAdapter/depends +dependsjboss:service=Hypersonic/depends -depends optional-attribute-name=ResourceAdapterNamejboss.jca:service=RARDeployment,name=Minerva JDBC LocalTransaction ResourceAdapter/depends -depends optional-attribute-name=ConnectionManagerFactoryLoaderNamejboss.jca:service=ConnectionManagerFactoryLoader,name=MinervaSharedLocalCMFactory/depends -attribute name=ConnectionManagerProperties# - #Wed Aug 15 16:17:29 EDT 2001 - MinSize=0 - MaxSize=10 - BlockingTimeoutMillis=5000 - IdleTimeoutMinutes=30 - CleanupIntervalMinutes=10 - MaxIdleTimeoutPercent=1.0 -/attribute -attribute name=PrincipalMappingClass - org.jboss.resource.security.ManyToOnePrincipalMapping -/attribute -attribute name=PrincipalMappingPropertiesuserName=sa/attribute +!--real attributes-- +attribute name=ManagedConnectionFactoryProperties + properties +config-property + config-property-nameConnectionURL/config-property-name + config-property-typejava.lang.String/config-property-type + config-property-valuejdbc:hsqldb:hsql://localhost:1476/config-property-value +/config-property +config-property + config-property-nameDriverClass/config-property-name + config-property-typejava.lang.String/config-property-type + config-property-valueorg.hsqldb.jdbcDriver/config-property-value +/config-property +config-property + config-property-nameUserName/config-property-name + config-property-typejava.lang.String/config-property-type + config-property-value/config-property-value +/config-property +config-property + config-property-namePassword/config-property-name + config-property-typejava.lang.String/config-property-type + config-property-value/config-property-value +/config-property + /properties +/attribute +attribute name=JndiNameDeployTestDS/attribute + /mbean +/depends +depends optional-attribute-name=ManagedConnectionPool + !--embedded mbean-- + mbean code=org.jboss.resource.connectionmanager.JBossManagedConnectionPool name=jboss.test:service=LocalTxPool + +attribute name=MinSize0/attribute +attribute name=MaxSize50/attribute +attribute name=BlockingTimeoutMillis5000/attribute +attribute name=IdleTimeoutMinutes15/attribute +!--criteria indicates if Subject (from security domain) or app supplied +parameters (such as from getConnection(user, pw)) are used to distinguish +connections in the pool. Choices are +ByContainerAndApplication (use both), +ByContainer (use Subject), +ByApplication (use app supplied params only), +ByNothing (all connections are equivalent,
[JBoss-dev] CVS update: tools/lib xdoclet.jar
User: d_jencks Date: 02/04/06 18:57:12 Modified:lib xdoclet.jar Log: This is tagged jboss_1_6 in xdoclet cvs Revision ChangesPath 1.6 +1574 -1578tools/lib/xdoclet.jar Binary file ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: build/jboss build.xml
User: d_jencks
Date: 02/04/06 18:59:30
Modified:jbossbuild.xml
Log:
updated to xjavadoc and jmx documentation generator
Revision ChangesPath
1.114 +8 -1 build/jboss/build.xml
Index: build.xml
===
RCS file: /cvsroot/jboss/build/jboss/build.xml,v
retrieving revision 1.113
retrieving revision 1.114
diff -u -r1.113 -r1.114
--- build.xml 3 Apr 2002 22:29:34 - 1.113
+++ build.xml 7 Apr 2002 02:59:30 - 1.114
@@ -12,7 +12,7 @@
!----
!-- == --
-!-- $Id: build.xml,v 1.113 2002/04/03 22:29:34 user57 Exp $ --
+!-- $Id: build.xml,v 1.114 2002/04/07 02:59:30 d_jencks Exp $ --
project default=main name=JBoss/Build
@@ -280,6 +280,7 @@
property name=install.docs value=${install.root}/docs/
property name=install.api value=${install.docs}/api/
+property name=install.jmx-api value=${install.docs}/jmx-api/
property name=install.todo value=${install.docs}/todo/
property name=install.examples value=${install.docs}/examples/
@@ -817,6 +818,12 @@
mkdir dir=${install.api}/${_module.name}/
copy todir=${install.api}/${_module.name} filtering=no
fileset dir=${_module.output}/api
+ include name=**/*/
+ /fileset
+/copy
+mkdir dir=${install.jmx-api}/
+copy todir=${install.jmx-api} filtering=no
+ fileset dir=${_module.output}/jmx-api
include name=**/*/
/fileset
/copy
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jboss-common build.xml
User: d_jencks
Date: 02/04/06 18:59:30
Modified:.build.xml
Log:
updated to xjavadoc and jmx documentation generator
Revision ChangesPath
1.11 +2 -1 jboss-common/build.xml
Index: build.xml
===
RCS file: /cvsroot/jboss/jboss-common/build.xml,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- build.xml 23 Mar 2002 21:11:00 - 1.10
+++ build.xml 7 Apr 2002 02:59:30 - 1.11
@@ -12,7 +12,7 @@
!----
!-- == --
-!-- $Id: build.xml,v 1.10 2002/03/23 21:11:00 ejort Exp $ --
+!-- $Id: build.xml,v 1.11 2002/04/07 02:59:30 d_jencks Exp $ --
project default=main name=JBoss/Common
@@ -172,6 +172,7 @@
path id=xdoclet.task.classpath
path refid=javac.classpath/
pathelement location=${project.tools}/lib/xdoclet.jar/
+ pathelement location=${project.tools}/lib/xjavadoc.jar/
pathelement location=${project.tools}/lib/ant.jar/
/path
property name=xdoclet.task.classpath
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: admin build.xml
User: d_jencks
Date: 02/04/06 18:59:29
Modified:.build.xml
Log:
updated to xjavadoc and jmx documentation generator
Revision ChangesPath
1.21 +2 -1 admin/build.xml
Index: build.xml
===
RCS file: /cvsroot/jboss/admin/build.xml,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -r1.20 -r1.21
--- build.xml 23 Mar 2002 21:10:58 - 1.20
+++ build.xml 7 Apr 2002 02:59:29 - 1.21
@@ -12,7 +12,7 @@
!----
!-- == --
-!-- $Id: build.xml,v 1.20 2002/03/23 21:10:58 ejort Exp $ --
+!-- $Id: build.xml,v 1.21 2002/04/07 02:59:29 d_jencks Exp $ --
project default=main name=JBoss/Admin
@@ -218,6 +218,7 @@
path id=xdoclet.task.classpath
path refid=javac.classpath/
pathelement location=${project.tools}/lib/xdoclet.jar/
+ pathelement location=${project.tools}/lib/xjavadoc.jar/
pathelement location=${project.tools}/lib/ant.jar/
/path
property name=xdoclet.task.classpath
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbosscx/src/main/org/jboss/resource/connectionmanager LocalTxConnectionManager.java XATxConnectionManager.java NoTxConnectionManager.java
User: d_jencks Date: 02/04/06 20:16:49 Modified:src/main/org/jboss/resource/connectionmanager LocalTxConnectionManager.java XATxConnectionManager.java NoTxConnectionManager.java Log: removed unused import Revision ChangesPath 1.3 +0 -1 jbosscx/src/main/org/jboss/resource/connectionmanager/LocalTxConnectionManager.java Index: LocalTxConnectionManager.java === RCS file: /cvsroot/jboss/jbosscx/src/main/org/jboss/resource/connectionmanager/LocalTxConnectionManager.java,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- LocalTxConnectionManager.java 6 Apr 2002 04:34:28 - 1.2 +++ LocalTxConnectionManager.java 7 Apr 2002 04:16:49 - 1.3 @@ -34,7 +34,6 @@ import javax.transaction.xa.XAException; import javax.transaction.xa.XAResource; import javax.transaction.xa.Xid; -import org.jboss.resource.ResourceSubjectFactory; import org.jboss.system.Registry; /** 1.3 +0 -1 jbosscx/src/main/org/jboss/resource/connectionmanager/XATxConnectionManager.java Index: XATxConnectionManager.java === RCS file: /cvsroot/jboss/jbosscx/src/main/org/jboss/resource/connectionmanager/XATxConnectionManager.java,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- XATxConnectionManager.java6 Apr 2002 04:34:28 - 1.2 +++ XATxConnectionManager.java7 Apr 2002 04:16:49 - 1.3 @@ -28,7 +28,6 @@ import javax.transaction.Transaction; import javax.transaction.TransactionManager; import javax.transaction.xa.XAResource; -import org.jboss.resource.ResourceSubjectFactory; import org.jboss.system.Registry; /** 1.3 +0 -1 jbosscx/src/main/org/jboss/resource/connectionmanager/NoTxConnectionManager.java Index: NoTxConnectionManager.java === RCS file: /cvsroot/jboss/jbosscx/src/main/org/jboss/resource/connectionmanager/NoTxConnectionManager.java,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- NoTxConnectionManager.java6 Apr 2002 04:34:28 - 1.2 +++ NoTxConnectionManager.java7 Apr 2002 04:16:49 - 1.3 @@ -13,7 +13,6 @@ import javax.resource.spi.ConnectionEventListener; import javax.resource.ResourceException; import javax.resource.spi.ManagedConnection; -import org.jboss.resource.ResourceSubjectFactory; import javax.resource.spi.ManagedConnectionFactory; /** ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jboss/src/etc/deploy jms-service.xml
User: d_jencks Date: 02/04/06 20:49:47 Modified:src/etc/deploy jms-service.xml Log: fix config so both topics and queues can be used with the same adapter Revision ChangesPath 1.8 +9 -32 jboss/src/etc/deploy/jms-service.xml Index: jms-service.xml === RCS file: /cvsroot/jboss/jboss/src/etc/deploy/jms-service.xml,v retrieving revision 1.7 retrieving revision 1.8 diff -u -r1.7 -r1.8 --- jms-service.xml 24 Mar 2002 22:03:15 - 1.7 +++ jms-service.xml 7 Apr 2002 04:49:47 - 1.8 @@ -27,38 +27,7 @@ /mbean !-- JMS XA Resource adapter, use this to get transacted JMS in beans -- -!--old configuration, see below for new choice. - mbean code=org.jboss.resource.ConnectionFactoryLoader - name=jboss.jca:service=ConnectionFactoryLoader,name=JmsXA -attribute name=JndiNameJmsXA/attribute -depends optional-attribute-name=ResourceAdapterNamejboss.jca:service=RARDeployment,name=JMS Adapter/depends -depends optional-attribute-name=ConnectionManagerFactoryLoaderNamejboss.jca:service=ConnectionManagerFactoryLoader,name=MinervaXACMFactory/depends -attribute name=ManagedConnectionFactoryProperties - SessionDefaultType=javax.jms.Topic - #UserName=guest - #Password=guest - /attribute -attribute name=ConnectionManagerProperties - # Pool type - uncomment to force, otherwise it is the default - #PoolConfiguration=per-factory - - # Connection pooling properties - see - # org.jboss.resource.connectionmanager.PoolParameters - MinSize=0 - MaxSize=10 - BlockingTimeoutMillis=5000 - IdleTimeoutMinutes=30 - CleanupIntervalMinutes=10 - MaxIdleTimeoutPercent=1.0 -/attribute -attribute name=PrincipalMappingClass - org.jboss.resource.security.ManyToOnePrincipalMapping -/attribute -attribute name=PrincipalMappingProperties -/attribute - /mbean --- !--new configuration for new ConnectionManager-- mbean code=org.jboss.resource.connectionmanager.XATxConnectionManager name=jboss.jca:service=JmsXACM !--make the rar deploy!-- @@ -89,7 +58,15 @@ attribute name=MaxSize50/attribute attribute name=BlockingTimeoutMillis5000/attribute attribute name=IdleTimeoutMinutes15/attribute -attribute name=CriteriaByContainer/attribute +!--criteria indicates if Subject (from security domain) or app supplied +parameters (such as from getConnection(user, pw)) are used to distinguish +connections in the pool. Choices are +ByContainerAndApplication (use both), +ByContainer (use Subject), +ByApplication (use app supplied params only), +ByNothing (all connections are equivalent, usually if adapter supports + reauthentication)-- +attribute name=CriteriaByContainerAndApplication/attribute /mbean /depends depends optional-attribute-name=CachedConnectionManagerjboss.jca:service=CachedConnectionManager/depends ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jboss-system build.xml
User: d_jencks
Date: 02/04/06 18:59:33
Modified:.build.xml
Log:
updated to xjavadoc and jmx documentation generator
Revision ChangesPath
1.14 +2 -1 jboss-system/build.xml
Index: build.xml
===
RCS file: /cvsroot/jboss/jboss-system/build.xml,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- build.xml 4 Apr 2002 04:32:35 - 1.13
+++ build.xml 7 Apr 2002 02:59:33 - 1.14
@@ -12,7 +12,7 @@
!----
!-- == --
-!-- $Id: build.xml,v 1.13 2002/04/04 04:32:35 user57 Exp $ --
+!-- $Id: build.xml,v 1.14 2002/04/07 02:59:33 d_jencks Exp $ --
project default=main name=JBoss/System
@@ -196,6 +196,7 @@
path id=xdoclet.task.classpath
path refid=javac.classpath/
pathelement location=${project.tools}/lib/xdoclet.jar/
+ pathelement location=${project.tools}/lib/xjavadoc.jar/
pathelement location=${project.tools}/lib/ant.jar/
/path
property name=xdoclet.task.classpath
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jboss build.xml
User: d_jencks
Date: 02/04/06 18:59:32
Modified:.build.xml
Log:
updated to xjavadoc and jmx documentation generator
Revision ChangesPath
1.82 +2 -1 jboss/build.xml
Index: build.xml
===
RCS file: /cvsroot/jboss/jboss/build.xml,v
retrieving revision 1.81
retrieving revision 1.82
diff -u -r1.81 -r1.82
--- build.xml 24 Mar 2002 21:44:32 - 1.81
+++ build.xml 7 Apr 2002 02:59:32 - 1.82
@@ -12,7 +12,7 @@
!----
!-- == --
-!-- $Id: build.xml,v 1.81 2002/03/24 21:44:32 d_jencks Exp $ --
+!-- $Id: build.xml,v 1.82 2002/04/07 02:59:32 d_jencks Exp $ --
project default=main name=JBoss/Server
@@ -310,6 +310,7 @@
path id=xdoclet.task.classpath
path refid=javac.classpath/
pathelement location=${project.tools}/lib/xdoclet.jar/
+ pathelement location=${project.tools}/lib/xjavadoc.jar/
pathelement location=${project.tools}/lib/ant.jar/
/path
property name=xdoclet.task.classpath
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbosstest build.xml
User: d_jencks
Date: 02/04/06 18:59:33
Modified:.build.xml
Log:
updated to xjavadoc and jmx documentation generator
Revision ChangesPath
1.103 +2 -1 jbosstest/build.xml
Index: build.xml
===
RCS file: /cvsroot/jboss/jbosstest/build.xml,v
retrieving revision 1.102
retrieving revision 1.103
diff -u -r1.102 -r1.103
--- build.xml 6 Apr 2002 04:45:19 - 1.102
+++ build.xml 7 Apr 2002 02:59:33 - 1.103
@@ -13,7 +13,7 @@
!----
!-- == --
-!-- $Id: build.xml,v 1.102 2002/04/06 04:45:19 user57 Exp $ --
+!-- $Id: build.xml,v 1.103 2002/04/07 02:59:33 d_jencks Exp $ --
project default=main name=JBoss/Testsuite
@@ -390,6 +390,7 @@
path id=xdoclet.task.classpath
path refid=tests.classpath/
pathelement location=${project.tools}/lib/xdoclet.jar/
+ pathelement location=${project.tools}/lib/xjavadoc.jar/
pathelement location=${project.tools}/lib/ant.jar/
/path
property name=xdoclet.task.classpath
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbosscx/src/etc/example-config - New directory
User: d_jencks Date: 02/04/06 19:26:33 jbosscx/src/etc/example-config - New directory ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: tools/lib xjavadoc.jar
User: d_jencks Date: 02/04/06 18:56:14 Added: lib xjavadoc.jar Log: This is tagged jboss_1_1 in xdoclet cvs Revision ChangesPath 1.1 tools/lib/xjavadoc.jar Binary file ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Need help to start
On Thu, Apr 04, 2002 at 08:49:00PM -0800, Ashutosh Nadkarni wrote: Hi all, I am new member joined here. I want to understand as a developer how jboss is developed and go though the code. Unfortunately I have not used CVS. Can anybody help me with steps of how I could download source, build and run an example. I request a simple step by step procedure. Check this: http://jboss.org/developers/guide/quickstart.jsp Christopher -- .Digital.Yearning.for.Networked.Assassination.and.Xenocide ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: contrib/varia/src/main/org/jboss/jdbc HypersonicDatabase.java HypersonicDatabaseMBean.java
User: user57
Date: 02/04/07 01:07:23
Modified:varia/src/main/org/jboss/jdbc HypersonicDatabase.java
Removed: varia/src/main/org/jboss/jdbc HypersonicDatabaseMBean.java
Log:
o Using XDoclet to generate *MBean interfaces
Revision ChangesPath
1.16 +32 -2 contrib/varia/src/main/org/jboss/jdbc/HypersonicDatabase.java
Index: HypersonicDatabase.java
===
RCS file:
/cvsroot/jboss/contrib/varia/src/main/org/jboss/jdbc/HypersonicDatabase.java,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- HypersonicDatabase.java 4 Apr 2002 04:33:08 - 1.15
+++ HypersonicDatabase.java 7 Apr 2002 09:07:23 - 1.16
@@ -31,13 +31,14 @@
*
* pStarts a patched HSQLDB 1.61 Hypersonic database in-VM.
*
- * @see HypersonicDatabaseMBean
+ * @jmx:mbean name=jboss:service=Hypersonic
+ *extends=org.jboss.system.ServiceMBean
*
* @author a href=mailto:[EMAIL PROTECTED];Rickard Öberg/a
* @author a href=mailto:[EMAIL PROTECTED];Scott Stark/a.
* @author a href=mailto:[EMAIL PROTECTED];Peter Fagerlund/a
* @author a href=mailto:[EMAIL PROTECTED];Jason Dillon/a
- * @version $Revision: 1.15 $
+ * @version $Revision: 1.16 $
*/
public class HypersonicDatabase
extends ServiceMBeanSupport
@@ -65,38 +66,65 @@
// empty
}
+ /**
+* @jmx:managed-attribute
+*/
public void setDatabase(final String name) {
this.name = name;
}
+ /**
+* @jmx:managed-attribute
+*/
public String getDatabase() {
return name;
}
+ /**
+* @jmx:managed-attribute
+*/
public void setPort(final int port) {
this.port = port;
}
+ /**
+* @jmx:managed-attribute
+*/
public int getPort() {
return port;
}
+ /**
+* @jmx:managed-attribute
+*/
public void setSilent(final boolean silent) {
this.silent = silent;
}
+ /**
+* @jmx:managed-attribute
+*/
public boolean getSilent() {
return silent;
}
+ /**
+* @jmx:managed-attribute
+*/
public void setTrace(final boolean trace) {
this.trace = trace;
}
+ /**
+* @jmx:managed-attribute
+*/
public boolean getTrace() {
return trace;
}
+ /**
+* @jmx:managed-attribute
+*/
public String getDatabasePath() {
return dbPath.toString();
}
@@ -109,6 +137,8 @@
/**
* start of DatabaseManager accesible from the localhost:8082
+*
+* @jmx:managed-operation
*/
public void startDatabaseManager() {
// Start DBManager in new thread
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: contrib/varia/src/main/org/jboss/varia/counter CounterInterceptor.java CounterService.java CounterServiceMBean.java
User: user57
Date: 02/04/07 01:07:23
Modified:varia/src/main/org/jboss/varia/counter
CounterInterceptor.java CounterService.java
Removed: varia/src/main/org/jboss/varia/counter
CounterServiceMBean.java
Log:
o Using XDoclet to generate *MBean interfaces
Revision ChangesPath
1.2 +1 -1
contrib/varia/src/main/org/jboss/varia/counter/CounterInterceptor.java
Index: CounterInterceptor.java
===
RCS file:
/cvsroot/jboss/contrib/varia/src/main/org/jboss/varia/counter/CounterInterceptor.java,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- CounterInterceptor.java 16 Feb 2002 04:16:32 - 1.1
+++ CounterInterceptor.java 7 Apr 2002 09:07:23 - 1.2
@@ -43,7 +43,7 @@
* statistics.
*
* @author a href=mailto:[EMAIL PROTECTED];Dan Christopherson/href
- * @version $Revision: 1.1 $
+ * @version $Revision: 1.2 $
*/
public class CounterInterceptor
extends AbstractInterceptor
@@ -105,7 +105,7 @@
if (counter == null) {
try {
InitialContext ctx = new InitialContext();
-counter = (CounterService)ctx.lookup(CounterServiceMBean.JNDI_NAME);
+counter = (CounterService)ctx.lookup(CounterService.JNDI_NAME);
} catch (NamingException ne) {
if (!loggedNoCounter) {
log.warn(CounterInterceptor can't get counter service , ne);
1.2 +8 -1
contrib/varia/src/main/org/jboss/varia/counter/CounterService.java
Index: CounterService.java
===
RCS file:
/cvsroot/jboss/contrib/varia/src/main/org/jboss/varia/counter/CounterService.java,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- CounterService.java 16 Feb 2002 04:16:32 - 1.1
+++ CounterService.java 7 Apr 2002 09:07:23 - 1.2
@@ -21,14 +21,18 @@
/**
* A service offering accumulator style counters to help in diagnosing
* performance issues.
+ *
+ * @jmx:mbean extends=org.jboss.system.ServiceMBean
*
* @author a href=mailto:[EMAIL PROTECTED];Dan Christopherson/href
- * @version $Revision: 1.1 $
+ * @version $Revision: 1.2 $
*/
public class CounterService
extends ServiceMBeanSupport
implements CounterServiceMBean
{
+ public static final String JNDI_NAME = java:/CounterService;
+
private HashMap counterMap = new HashMap();
/**
@@ -68,6 +72,9 @@
NonSerializableFactory.unbind(JNDI_NAME);
}
+ /**
+* @jmx:managed-operation
+*/
public String list()
{
DecimalFormat format = new DecimalFormat(0.);
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: contrib/varia/src/main/org/jboss/varia/scheduler/example SchedulableMBeanExample.java SchedulableMBeanExampleMBean.java
User: user57
Date: 02/04/07 01:07:24
Modified:varia/src/main/org/jboss/varia/scheduler/example
SchedulableMBeanExample.java
Removed: varia/src/main/org/jboss/varia/scheduler/example
SchedulableMBeanExampleMBean.java
Log:
o Using XDoclet to generate *MBean interfaces
Revision ChangesPath
1.2 +6 -1
contrib/varia/src/main/org/jboss/varia/scheduler/example/SchedulableMBeanExample.java
Index: SchedulableMBeanExample.java
===
RCS file:
/cvsroot/jboss/contrib/varia/src/main/org/jboss/varia/scheduler/example/SchedulableMBeanExample.java,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- SchedulableMBeanExample.java 16 Feb 2002 03:52:53 - 1.1
+++ SchedulableMBeanExample.java 7 Apr 2002 09:07:24 - 1.2
@@ -33,9 +33,11 @@
* jboss:service=Scheduler,schedule=you schedule namebr
* This way you should not run into a name conflict.
*
+ * @jmx:mbean extends=org.jboss.system.ServiceMBean
+ *
* @author a href=mailto:[EMAIL PROTECTED];Andreas Schaefer/a
* @author Cameron (camtabor)
- * @version $Revision: 1.1 $
+ * @version $Revision: 1.2 $
*
* pbRevisions:/b/p
* pb20010814 Cameron:/b
@@ -83,6 +85,9 @@
// SchedulableExampleMBean Methods
// -
+ /**
+* @jmx:managed-operation
+*/
public void hit( Notification lNotification, Date lDate, long lRepetitions,
ObjectName lName, String lTest ) {
log.info( got hit
+ , notification: + lNotification
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: contrib/varia/src/main/org/jboss/jdo/castor CastorJDOImpl.java CastorJDOImplMBean.java
User: user57
Date: 02/04/07 01:07:23
Modified:varia/src/main/org/jboss/jdo/castor CastorJDOImpl.java
Removed: varia/src/main/org/jboss/jdo/castor CastorJDOImplMBean.java
Log:
o Using XDoclet to generate *MBean interfaces
Revision ChangesPath
1.11 +319 -281 contrib/varia/src/main/org/jboss/jdo/castor/CastorJDOImpl.java
Index: CastorJDOImpl.java
===
RCS file:
/cvsroot/jboss/contrib/varia/src/main/org/jboss/jdo/castor/CastorJDOImpl.java,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- CastorJDOImpl.java24 Feb 2002 10:18:51 - 1.10
+++ CastorJDOImpl.java7 Apr 2002 09:07:23 - 1.11
@@ -45,323 +45,361 @@
/**
- * Castor JDO support
+ * Castor JDO support.
*
- * @author Oleg Nitz ([EMAIL PROTECTED])
- * @version $Revision: 1.10 $
+ * @jmx:mbean name=jboss:type=Service,service=JDO,flavor=Castor
+ *extends=org.jboss.system.ServiceMBean
+ *
+ * @version tt$Revision: 1.11 $/tt
+ * @author Oleg Nitz ([EMAIL PROTECTED])
*/
public class CastorJDOImpl extends ServiceMBeanSupport
-implements DataObjects, ObjectFactory, Referenceable, Serializable,
- CastorJDOImplMBean, MBeanRegistration, LogInterceptor {
+ implements DataObjects, ObjectFactory, Referenceable, Serializable,
+ CastorJDOImplMBean, MBeanRegistration, LogInterceptor {
-private String _jndiName;
+ private String _jndiName;
-private String _dbConf;
+ private String _dbConf;
-private JDO _jdo = new JDO();
+ private JDO _jdo = new JDO();
-private String _dataSourceName;
-
-private static HashMap _instances = new HashMap();
-
-private transient PrintWriter writer;
-
-/**
- * Do JDO classes should be loader by the global class loader
- * (the same class loader as Castor classes)?
- */
-private boolean _commonClassPath;
-
-/*
- * True if user prefer all reachable object to be stored automatically.
- * False (default) if user want only dependent object to be stored.
- */
-private boolean _autoStore = false;
-
-/*
- * True if user prefers application-server database pooling.
- * False (default) if user wants a new connection for each invocation of
- * getDatabase().
- */
-private boolean _dbPooling = false;
-
-public CastorJDOImpl() {
-}
-
-public ObjectName getObjectName(MBeanServer server, ObjectName name)
-throws javax.management.MalformedObjectNameException {
-return new ObjectName(OBJECT_NAME+,name=+_jndiName);
-}
-
-public String getName() {
-return CastorJDO;
-}
-
-public void startService() throws Exception {
-org.exolab.castor.jdo.conf.Database database;
-Unmarshaller unm;
-int pos;
-Method m;
-
-boolean debug = log.isDebugEnabled();
-
-// Bind in JNDI
-bind(new InitialContext(), java:/ + _jndiName, this);
-
-_jdo.setTransactionManager(java:/TransactionManager);
-_jdo.setConfiguration(_dbConf);
-unm = new Unmarshaller(org.exolab.castor.jdo.conf.Database.class);
-database = (org.exolab.castor.jdo.conf.Database) unm.unmarshal(new
InputSource(_dbConf));
-_jdo.setDatabaseName(database.getName());
-if (database.getJndi() != null) {
-_dataSourceName = database.getJndi().getName();
-}
-// Older Castor versions older don't have these methods,
-// we'll use reflection for backward compatibility
-//_jdo.setAutoStore(_autoStore);
-//_jdo.setDatabasePooling(_dbpooling);
-try {
-// 0.9.4
-m = _jdo.getClass().getMethod(setAutoStore,
- new Class[] {boolean.class});
-m.invoke(_jdo, new Object[] {new Boolean(_autoStore)});
-} catch (Exception ex) {
-if (debug)
- log.debug(couldn't invoke setAutoStore());
-}
-
-try {
-// 0.9.3
-m = _jdo.getClass().getMethod(setDatabasePooling,
- new Class[] {boolean.class});
-m.invoke(_jdo, new Object[] {new Boolean(_dbPooling)});
-} catch (Exception ex) {
-if (debug)
- log.debug(couldn't invoke setDatabasePooling());
-}
-_instances.put(_jndiName, this);
-if (debug)
- log.debug(DataObjects factory for + _dataSourceName + bound to +
_jndiName);
-}
-
-public void stopService() {
-// Unbind from JNDI
-try {
-new InitialContext().unbind(java:/ +
[JBoss-dev] CVS update: contrib/varia/src/main/org/jboss/tm/plugins/tyrex TransactionManagerService.java TransactionManagerServiceMBean.java
User: user57
Date: 02/04/07 01:07:23
Modified:varia/src/main/org/jboss/tm/plugins/tyrex
TransactionManagerService.java
Removed: varia/src/main/org/jboss/tm/plugins/tyrex
TransactionManagerServiceMBean.java
Log:
o Using XDoclet to generate *MBean interfaces
Revision ChangesPath
1.7 +26 -15
contrib/varia/src/main/org/jboss/tm/plugins/tyrex/TransactionManagerService.java
Index: TransactionManagerService.java
===
RCS file:
/cvsroot/jboss/contrib/varia/src/main/org/jboss/tm/plugins/tyrex/TransactionManagerService.java,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- TransactionManagerService.java15 Feb 2002 00:46:53 - 1.6
+++ TransactionManagerService.java7 Apr 2002 09:07:23 - 1.7
@@ -31,13 +31,17 @@
import org.apache.log4j.Category;
/**
- * This is a JMX service which manages the Tyrex TransactionManager
(tyrex.exolab.org).
- * The service creates it and binds a Reference to it into JNDI. It also
initializes
- * the object that manages Tyrex TransactionPropagationContext.
+ * This is a JMX service which manages the Tyrex TransactionManager
(tyrex.exolab.org).
+ * The service creates it and binds a Reference to it into JNDI. It also initializes
+ * the object that manages Tyrex TransactionPropagationContext.
*
- * @see TyrexTransactionPropagationContextManager, tyrex.tm.TransactionDomain
- * @author a href=mailto:[EMAIL PROTECTED];Anatoly Akkerman/a
- * @version $Revision: 1.6 $
+ * @jmx:mbean name=jboss:type=TransactionManager,flavor=Tyrex
+ *extends=org.jboss.system.ServiceMBean
+ *
+ * @see TyrexTransactionPropagationContextManager, tyrex.tm.TransactionDomain
+ *
+ * @version tt$Revision: 1.7 $/tt
+ * @author a href=mailto:[EMAIL PROTECTED];Anatoly Akkerman/a
*/
public class TransactionManagerService
extends ServiceMBeanSupport
@@ -109,26 +113,33 @@
bindRef(JNDI_EXPORTER, org.jboss.tm.TransactionPropagationContextFactory);
}
- protected void stopService()
+ protected void stopService() throws Exception
{
+ // Remove TM
+ Context ctx = new InitialContext();
try {
- // Remove TM
- Context ctx = new InitialContext();
ctx.unbind(JNDI_NAME);
ctx.unbind(JNDI_TPC_SENDER);
ctx.unbind(JNDI_TPC_RECEIVER);
ctx.unbind(JNDI_IMPORTER);
ctx.unbind(JNDI_EXPORTER);
- } catch (Exception e) {
- log.error(e);
+ }
+ catch (Exception e) {
+ ctx.close();
}
}
- public String getConfigFileName()
- {
-return this.configFile;
- }
+ /**
+* @jmx:managed-attribute
+*/
+ public String getConfigFileName()
+ {
+ return this.configFile;
+ }
+ /**
+* @jmx:managed-attribute
+*/
public void setConfigFileName(String name) throws IOException
{
// See if the name is a URL
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: contrib/varia/src/main/org/jboss/mail MailService.java MailServiceMBean.java
User: user57
Date: 02/04/07 01:07:23
Modified:varia/src/main/org/jboss/mail MailService.java
Removed: varia/src/main/org/jboss/mail MailServiceMBean.java
Log:
o Using XDoclet to generate *MBean interfaces
Revision ChangesPath
1.7 +45 -5 contrib/varia/src/main/org/jboss/mail/MailService.java
Index: MailService.java
===
RCS file: /cvsroot/jboss/contrib/varia/src/main/org/jboss/mail/MailService.java,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- MailService.java 8 Mar 2002 23:19:44 - 1.6
+++ MailService.java 7 Apr 2002 09:07:23 - 1.7
@@ -39,7 +39,10 @@
* MBean that gives support for JavaMail. Object of class javax.mail.Session will
be bound
* in JNDI under java:/ namespace with the name provided with method {@link
#setJNDIName}.
*
- * @version tt$Revision: 1.6 $/tt
+ * @jmx:mbean name=jboss:type=Service,service=Mail
+ *extends=org.jboss.system.ServiceMBean
+ *
+ * @version tt$Revision: 1.7 $/tt
* @author a href=mailto:[EMAIL PROTECTED];Simone Bordet/a
* @author a href=mailto:[EMAIL PROTECTED];Jason Dillon/a
*/
@@ -47,33 +50,67 @@
extends ServiceMBeanSupport
implements MailServiceMBean
{
+ public static final String JNDI_NAME = java:/Mail;
+
private String user;
private String password;
private String jndiName = JNDI_NAME;
private Element config;
- /** Object Name of the JSR-77 representant of this servie **/
+
+ /** Object Name of the JSR-77 representant of this service */
ObjectName mMail;
+ /**
+* User id used to connect to a mail server
+*
+* @see #setPassword
+*
+* @jmx:managed-attribute
+*/
public void setUser(final String user) {
this.user = user;
}
- protected String getUser() {
+ /**
+* @jmx:managed-attribute
+*/
+ public String getUser() {
return user;
}
+ /**
+* Password used to connect to a mail server
+*
+* @see #setUser
+*
+* @jmx:managed-attribute
+*/
public void setPassword(final String password) {
this.password = password;
}
-
+
+ /**
+* Password is read only.
+*/
protected String getPassword() {
return password;
}
+ /**
+* Configuration for the mail service.
+*
+* @jmx:managed-attribute
+*/
public void setConfiguration(final Element element) {
config = element;
}
+ /**
+* The JNDI name under the java:/ namespace to which javax.mail.Session
+* objects are bound.
+*
+* @jmx:managed-attribute
+*/
public void setJNDIName(final String name) {
if (!name.startsWith(java:/)) {
jndiName = java:/ + name;
@@ -83,7 +120,10 @@
}
}
- protected String getJNDIName() {
+ /**
+* @jmx:managed-attribute
+*/
+ public String getJNDIName() {
return jndiName;
}
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: contrib/varia build.xml
User: user57
Date: 02/04/07 01:07:22
Modified:variabuild.xml
Log:
o Using XDoclet to generate *MBean interfaces
Revision ChangesPath
1.29 +34 -2 contrib/varia/build.xml
Index: build.xml
===
RCS file: /cvsroot/jboss/contrib/varia/build.xml,v
retrieving revision 1.28
retrieving revision 1.29
diff -u -r1.28 -r1.29
--- build.xml 3 Apr 2002 22:29:17 - 1.28
+++ build.xml 7 Apr 2002 09:07:22 - 1.29
@@ -12,7 +12,7 @@
!----
!-- == --
-!-- $Id: build.xml,v 1.28 2002/04/03 22:29:17 user57 Exp $ --
+!-- $Id: build.xml,v 1.29 2002/04/07 09:07:22 user57 Exp $ --
project default=main name=JBoss/Varia
@@ -276,6 +276,7 @@
property name=build.etc value=${module.output}/etc/
property name=build.resources value=${module.output}/resources/
property name=build.reports value=${module.output}/reports/
+property name=build.gen-src value=${module.output}/gen-src/
!-- Install/Release structure --
property name=install.id value=${module.name}-${module.version}/
@@ -317,6 +318,20 @@
property name=junit.timeout value=24/ !-- 4 minutes --
property name=junit.batchtest.todir value=${build.reports}/
property name=junit.jvm.options value=-Ddummy/
+
+!-- xdoclet --
+path id=xdoclet.task.classpath
+ path refid=javac.classpath/
+ pathelement location=${project.tools}/lib/xdoclet.jar/
+ pathelement location=${project.tools}/lib/xjavadoc.jar/
+ pathelement location=${project.tools}/lib/ant.jar/
+/path
+property name=xdoclet.task.classpath
+ refid=xdoclet.task.classpath/
+
+taskdef name=todo
+ classname=xdoclet.doc.DocumentDocletTask
+ classpathref=xdoclet.task.classpath/
/target
@@ -332,9 +347,25 @@
| documentation compiles.
--
target name=compile
- depends=compile-classes, compile-rmi, compile-etc
+ depends=compile-mbean-sources, compile-classes, compile-rmi, compile-etc
description=Compile all source files./
+ !-- Compile mbeans with XDoclet --
+ target name=compile-mbean-sources depends=init
+taskdef name=xdoclet classname=xdoclet.jmx.JMXDocletTask/
+
+mkdir dir=${build.gen-src}/
+xdoclet sourcepath=${source.java}
+ destdir=${build.gen-src}
+ classpath=${xdoclet.task.classpath}
+ excludedtags=@version,@author
+ fileset dir=${source.java}
+include name=**/*.java/
+ /fileset
+ mbeaninterface mergedir=${project.tools}/etc/xdoclet/templates/
+/xdoclet
+ /target
+
!-- Compile all class files --
target name=compile-classes depends=init
mkdir dir=${build.classes}/
@@ -349,6 +380,7 @@
includeJavaRuntime=${javac.include.java.runtime}
failonerror=${javac.fail.onerror}
src path=${source.java}/
+ src path=${build.gen-src}/
classpath refid=javac.classpath/
include name=${javac.includes}/
exclude name=${javac.excludes}/
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: contrib/varia/src/main/org/jboss/varia/scheduler Scheduler.java SchedulerMBean.java
User: user57
Date: 02/04/07 01:07:23
Modified:varia/src/main/org/jboss/varia/scheduler Scheduler.java
Removed: varia/src/main/org/jboss/varia/scheduler SchedulerMBean.java
Log:
o Using XDoclet to generate *MBean interfaces
Revision ChangesPath
1.2 +248 -1contrib/varia/src/main/org/jboss/varia/scheduler/Scheduler.java
Index: Scheduler.java
===
RCS file:
/cvsroot/jboss/contrib/varia/src/main/org/jboss/varia/scheduler/Scheduler.java,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- Scheduler.java16 Feb 2002 03:52:53 - 1.1
+++ Scheduler.java7 Apr 2002 09:07:23 - 1.2
@@ -50,9 +50,12 @@
* :service=Scheduler,schedule=you schedule namebr
* This way you should not run into a name conflict.
*
+ * @jmx:mbean name=jboss:service=Scheduler
+ *extends=org.jboss.system.ServiceMBean
+ *
* @author a href=mailto:[EMAIL PROTECTED];Andreas Schaefer/a
* @author Cameron (camtabor)
- * @version $Revision: 1.1 $
+ * @version $Revision: 1.2 $
*
* pbRevisions:/b/p
* pb20010814 Cameron:/b
@@ -199,6 +202,17 @@
// SchedulerMBean Methods
// -
+ /**
+* Starts the schedule if the schedule is stopped otherwise nothing will happen.
+* The Schedule is immediately set to started even the first call is in the
+* future.
+*
+* @jms:managed-operation
+*
+* @throws InvalidParameterException If any of the necessary values are not set
+* or invalid (especially for the Schedulable
+* class attributes).
+*/
public void startSchedule() {
// Check if not already started
if( !isStarted() ) {
@@ -374,6 +388,16 @@
}
}
+ /**
+* Stops the schedule because it is either not used anymore or to restart it with
+* new values.
+*
+* @jmx:managed-operation
+*
+* @param pDoItNow If true the schedule will be stopped without waiting for the
next
+* scheduled call otherwise the next call will be performed
before
+* the schedule is stopped.
+*/
public void stopSchedule(boolean pDoItNow)
{
try {
@@ -409,11 +433,22 @@
}
}
+ /**
+* Stops the server right now and starts it right now.
+*
+* @jmx:managed-operation
+*/
public void restartSchedule() {
stopSchedule( true );
startSchedule();
}
+ /**
+* @jmx:managed-attribute
+*
+* @return Full qualified Class name of the schedulable class called by the
schedule or
+* null if not set.
+*/
public String getSchedulableClass() {
if( mSchedulableClass == null ) {
return null;
@@ -421,6 +456,19 @@
return mSchedulableClass.getName();
}
+ /**
+* Sets the fully qualified Class name of the Schedulable Class being called by
the
+* Scheduler. Must be set before the Schedule is started. Please also set the
+* {@link #setSchedulableArguments} and {@link #setSchedulableArgumentTypes}.
+*
+* @jmx:managed-attribute
+*
+* @param pSchedulableClass Fully Qualified Schedulable Class.
+*
+* @throws InvalidParameterException If the given value is not a valid class or
cannot
+* be loaded by the Scheduler or is not of
instance
+* Schedulable.
+*/
public void setSchedulableClass( String pSchedulableClass )
throws InvalidParameterException
{
@@ -454,10 +502,28 @@
mUseMBean = false;
}
+ /**
+* @jmx:managed-attribute
+*
+* @return Comma seperated list of Constructor Arguments used to instantiate the
+* Schedulable class instance. Right now only basic data types, String
and
+* Classes with a Constructor with a String as only argument are
supported.
+*/
public String getSchedulableArguments() {
return mSchedulableArguments;
}
+ /**
+* @jmx:managed-attribute
+*
+* Sets the comma seperated list of arguments for the Schedulable class. Note
that
+* this list must have as many elements as the Schedulable Argument Type list
otherwise
+* the start of the Scheduler will fail. Right now only basic data types, String
and
+* Classes with a Constructor with a String as only argument are supported.
+*
+* @param pArgumentList List of arguments used to create the Schedulable
intance. If
+* the list is null or empty then the no-args constructor
is
[JBoss-dev] [ jboss-Bugs-540270 ] Classloader-problem with Tomcat 4.0.3
Bugs item #540270, was opened at 2002-04-06 19:57
You can respond by visiting:
http://sourceforge.net/tracker/?func=detailatid=376685aid=540270group_id=22866
Category: JBossServer
Group: v3.0 Rabbit Hole
Status: Open
Resolution: None
Priority: 5
Submitted By: Thomas Peuss (tpeuss)
Assigned to: Nobody/Anonymous (nobody)
Summary: Classloader-problem with Tomcat 4.0.3
Initial Comment:
I am trying the embeddeded catalina service with JBoss
3.0 beta 2. The servlet-engine finds no classes besides
the standard Java-classes.
Log-file follows:
19:37:12,678 ERROR [EmbeddedCatalinaServiceSX]
StandardWrapperValve[jsp]: Servlet.service() for
servlet jsp threw exception
org.apache.jasper.JasperException: Unable to compile
class for JSP
/scratch/thomas/jakarta-tomcat-4.0.3/work/localhost/jsp_jmx_view/mbs$jsp.java:3:
Package javax.management not found in import.
import javax.management.*;
^
/scratch/thomas/jakarta-tomcat-4.0.3/work/localhost/jsp_jmx_view/mbs$jsp.java:6:
Package javax.servlet not found in import.
import javax.servlet.*;
^
/scratch/thomas/jakarta-tomcat-4.0.3/work/localhost/jsp_jmx_view/mbs$jsp.java:7:
Package javax.servlet.http not found in import.
import javax.servlet.http.*;
^
/scratch/thomas/jakarta-tomcat-4.0.3/work/localhost/jsp_jmx_view/mbs$jsp.java:8:
Package javax.servlet.jsp not found in import.
import javax.servlet.jsp.*;
^
/scratch/thomas/jakarta-tomcat-4.0.3/work/localhost/jsp_jmx_view/mbs$jsp.java:9:
Package org.apache.jasper.runtime not found in import.
import org.apache.jasper.runtime.*;
^
/scratch/thomas/jakarta-tomcat-4.0.3/work/localhost/jsp_jmx_view/mbs$jsp.java:12:
Superclass org.apache.jsp.HttpJspBase of class
org.apache.jsp.mbs$jsp not found.public class mbs$jsp
extends HttpJspBase {
^
6 errors
at
org.apache.jasper.compiler.Compiler.compile(Compiler.java:285)
at
org.apache.jasper.servlet.JspServlet.loadJSP(JspServlet.java:552)
at
org.apache.jasper.servlet.JspServlet$JspServletWrapper.loadIfNecessary(JspServlet.java:177)
at
org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServlet.java:189)
at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:382)
at
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:474)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:243)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:190)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at
org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:246)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2343)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at
org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:170)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.java:1012)
at
org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java:1107)
at java.lang.Thread.run(Thread.java:484)
--
Comment By: Thomas Peuss (tpeuss)
Re: [JBoss-dev] Patched HSQLDB sources?
on 07-04-2 09.30, Jason Dillon at [EMAIL PROTECTED] wrote: If one uses ones own ServerSocket and connection threads that use the hsqldb.Database class directly - then We do not need to touch the hsqldb code and have more controll over the listeners in JBoss ... this is how the Avalon project has solved there embedded hsqldb. Does it make sence to implement this now, incase the method the hsqldb folks decide on isn't enough... or takes too long? I think they will provide us with something satisfactory ... Do you understand how to implement this? If so and it makes sence to add, then lets do it. It will make this more maintainable. Doing a plain Jane implementation is easy - unless You use the JNP way as a pattern for doing it ;-) ... It growed on me to be able to have all listerners (NAME:PORT) registred in a component for easy access by other components, to be able to understand what ports are running in the WM and be JMX intra-machine negotiation capable. what do You think ? ... /peter_f ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] I want my docbook-xsl
Did a clean CVS co and the build.xml complains at line 530 about FNFE docbook-xsl - I do not eaven have a thirdparty/oasis/ folder ??? ... I go for a espresso meanwhile ... /peter_f ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: AW: [JBoss-dev] JMX HTML... From the Pure Fluff Department...
Project is a href=http://jmxview.sf.net;here/a _ View thread online: http://main.jboss.org/thread.jsp?forum=66thread=11622 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] I want my docbook-xsl
on 07-04-2 16.10, Peter Fagerlund at [EMAIL PROTECTED] wrote: Did a clean CVS co and the build.xml complains at line 530 about FNFE docbook-xsl - I do not eaven have a thirdparty/oasis/ folder ??? ... I go for a espresso meanwhile ... did a -dP and got it now - sorry ... /peter_f ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: CVSROOT modules
User: d_jencks Date: 02/04/07 08:35:48 Modified:.modules Log: oasis is now used by main build in jmx-api generation Revision ChangesPath 1.111 +1 -0 CVSROOT/modules Index: modules === RCS file: /cvsroot/jboss/CVSROOT/modules,v retrieving revision 1.110 retrieving revision 1.111 diff -u -r1.110 -r1.111 --- modules 2 Apr 2002 14:27:56 - 1.110 +++ modules 7 Apr 2002 15:35:47 - 1.111 @@ -87,6 +87,7 @@ thirdparty/techtrader \ thirdparty/jdom \ thirdparty/junitejb \ +thirdparty/oasis \ thirdparty/oswego \ thirdparty/xml ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] I want my docbook-xsl
I wonder how I got oasis in my checkout??!?!? I added oasis to the appropriate place in CVSROOT/modules so all should work now with a clean co. with luck I didn't break anything else;-) david jencks On 2002.04.07 10:10:46 -0400 Peter Fagerlund wrote: Did a clean CVS co and the build.xml complains at line 530 about FNFE docbook-xsl - I do not eaven have a thirdparty/oasis/ folder ??? ... I go for a espresso meanwhile ... /peter_f ___ 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] JSR-88 - J2EE Deployment
Has work been started on JSR-88 for jboss? View thread online: http://main.jboss.org/thread.jsp?forum=66thread=12322 I don't think so, though I am interested in contributing to it as well (it is related to my research project). I did create a toy implementation of DDBean classes but don't have a clear idea of how to proceed with the overall design. I would be very much interested in specifying an overall architecture of an implementation with people on the list. - Anatoly Akkerman Computer Science Dept. Courant Institute of Mathematical Sciences, NYU 715 Broadway, #719 Tel: 212 998-3493 New York, NY 10003 Fax: 212 995-4123 - ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] JBoss 3 users -- warning of impending configuration change
Thanks for the note about the postgres config. I tried leaving out the security domain with hsql and it seems to work ok, what error are you getting? If you don't set something up in auth.conf, you do have to leave out the SecurityDomainJndiName attribute. david jencks On 2002.04.07 01:36:45 -0500 Stephen Coy wrote: Is there a way to get jdbc connections to use the UserName/Password properties specified in the: attribute name=ManagedConnectionFactoryProperties properties config-property config-property-nameConnectionURL/config-property-name config-property-typejava.lang.String/config-property-type config-property-valuejdbc:oracle:thin:@mydatabasebox:1521:db1/config-property-value /config-property config-property config-property-nameDriverClass/config-property-name config-property-typejava.lang.String/config-property-type config-property-valueoracle.jdbc.driver.OracleDriver/config-property-value /config-property config-property config-property-nameUserName/config-property-name config-property-typejava.lang.String/config-property-type config-property-valuenotmyrealuserid/config-property-value /config-property config-property config-property-namePassword/config-property-name config-property-typejava.lang.String/config-property-type config-property-valuenotmyrealpassword/config-property-value /config-property /properties ... tags, or must we have to have a security domain set up in auth.conf? In which case, why have them here as well? I have an Oracle8 version of this stuff working, but I had to set up the userid/password in auth.conf. BTW, the sample postgres-service.xml file has a missing /depends tag, to match the one that opens on line 21. _ View thread online: http://main.jboss.org/thread.jsp?forum=66thread=12301 ___ 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: AW: [JBoss-dev] JMX HTML... From the Pure Fluff Department...
Hello James! On Sun, Apr 07, 2002 at 06:49:11PM +0200, Marcus Redeker wrote: James, your screenshots look almos like the SUN stuff ;-) Is there already a CVS module or some files to download and take 'live' look at it? I want to help with this project, too. CU Thomas -- AIM-Nickname : tpeuss Homepage : http://www.peuss.de/ PGP-Public-Key : http://www.peuss.de/PublicKey.asc ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] I want my docbook-xsl
This has been there for a while... unless someone changed CVSROOT/modules to exclude it. CVS update should bring it back if that is the case. What module are you trying to build? --jason Quoting Peter Fagerlund [EMAIL PROTECTED]: Did a clean CVS co and the build.xml complains at line 530 about FNFE docbook-xsl - I do not eaven have a thirdparty/oasis/ folder ??? ... I go for a espresso meanwhile ... /peter_f ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development - This mail sent through IMP: http://horde.org/imp/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Re: Should we add .sar to cvswrappers?
Sounds reason enough. I just added .sar and .wsr for good measure. All of these silly extenstions are starting to become annoying. It is too bad they didn't use subprefixes, like .web.jar or .app.jar instead of .war and .ear and such... --jason Quoting David Jencks [EMAIL PROTECTED]: Hmm.. It's not so easy to think of a circumstance... If we start using an externally developed opensource project based on JBoss in the website? Not a big deal david jencks On 2002.04.07 01:06:18 -0500 Jason Dillon wrote: Why would a .sar ever be checked in? I can add, but why? --jason Quoting David Jencks [EMAIL PROTECTED]: I'm a little nervous about messing with cvs settings or I'd do it. thanks david jencks - This mail sent through IMP: http://horde.org/imp/ ___ 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 - This mail sent through IMP: http://horde.org/imp/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: CVSROOT cvswrappers
User: user57 Date: 02/04/07 13:29:47 Modified:.cvswrappers Log: o added .sar .wsr (just in case) Revision ChangesPath 1.5 +2 -0 CVSROOT/cvswrappers Index: cvswrappers === RCS file: /cvsroot/jboss/CVSROOT/cvswrappers,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- cvswrappers 30 Aug 2001 22:13:55 - 1.4 +++ cvswrappers 7 Apr 2002 20:29:47 - 1.5 @@ -34,6 +34,8 @@ *.ear-k 'b' -m 'COPY' *.war-k 'b' -m 'COPY' *.tar-k 'b' -m 'COPY' +*.sar -k 'b' -m 'COPY' +*.wsr -k 'b' -m 'COPY' *.tgz-k 'b' -m 'COPY' *.gz -k 'b' -m 'COPY' *.pdf-k 'b' -m 'COPY' ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: AW: [JBoss-dev] JMX HTML... From the Pure Fluff Department...
Very nice, just looked at the shoot, will look into more later. Are you expecting to maintain this yourself? Just currious if you had though of making this a part og JBoss, thus opening up the maintenece to a wider audience? Either way, looks great. I have been meaning to do something like this for a while, and or convince some people I work with to do it for me. Have to look in more detail, but if nothing stands out as problem we could make this the default jmx html adapter and be done with the sun fluff. --jason Quoting James Birchfield [EMAIL PROTECTED]: Project is a href=http://jmxview.sf.net;here/a _ View thread online: http://main.jboss.org/thread.jsp?forum=66thread=11622 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development - This mail sent through IMP: http://horde.org/imp/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: AW: [JBoss-dev] JMX HTML... From the Pure Fluff Department...
I would love to do that!(integrate with JBoss.org) I am hoping to get a core code base out to SourceForge sometime this week. I need to clean up some stuff, and then I can push it out. The framework is built using Jetty deployed as an MBean, and Tapestry as the web framework driving the presentation. James Birchfield Director, Application Development Genscape, Inc. (502) 583-2298 (o) (502) 639-3136 (c) -Original Message- From: Jason Dillon [mailto:[EMAIL PROTECTED]] Sent: Sunday, April 07, 2002 4:48 PM To: [EMAIL PROTECTED]; James Birchfield Subject: Re: AW: [JBoss-dev] JMX HTML... From the Pure Fluff Department... Very nice, just looked at the shoot, will look into more later. Are you expecting to maintain this yourself? Just currious if you had though of making this a part og JBoss, thus opening up the maintenece to a wider audience? Either way, looks great. I have been meaning to do something like this for a while, and or convince some people I work with to do it for me. Have to look in more detail, but if nothing stands out as problem we could make this the default jmx html adapter and be done with the sun fluff. --jason Quoting James Birchfield [EMAIL PROTECTED]: Project is a href=http://jmxview.sf.net;here/a _ View thread online: http://main.jboss.org/thread.jsp?forum=66thread=11622 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development - This mail sent through IMP: http://horde.org/imp/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: AW: [JBoss-dev] JMX HTML... From the Pure Fluff Department...
Please let me know when you have finished your cleaning and have published the sources. I am going to be busy for the next week (perhaps, unless I under estimate my efficency =), but I have been planing to start a JBoss/Console module, which contains web, command line telnet/ssh console access to JBoss. I would be interesed to see how your work might fit in there. --jason Quoting Jim Birchfield [EMAIL PROTECTED]: I would love to do that!(integrate with JBoss.org) I am hoping to get a core code base out to SourceForge sometime this week. I need to clean up some stuff, and then I can push it out. The framework is built using Jetty deployed as an MBean, and Tapestry as the web framework driving the presentation. James Birchfield Director, Application Development Genscape, Inc. (502) 583-2298 (o) (502) 639-3136 (c) -Original Message- From: Jason Dillon [mailto:[EMAIL PROTECTED]] Sent: Sunday, April 07, 2002 4:48 PM To: [EMAIL PROTECTED]; James Birchfield Subject: Re: AW: [JBoss-dev] JMX HTML... From the Pure Fluff Department... Very nice, just looked at the shoot, will look into more later. Are you expecting to maintain this yourself? Just currious if you had though of making this a part og JBoss, thus opening up the maintenece to a wider audience? Either way, looks great. I have been meaning to do something like this for a while, and or convince some people I work with to do it for me. Have to look in more detail, but if nothing stands out as problem we could make this the default jmx html adapter and be done with the sun fluff. --jason Quoting James Birchfield [EMAIL PROTECTED]: Project is a href=http://jmxview.sf.net;here/a _ View thread online: http://main.jboss.org/thread.jsp?forum=66thread=11622 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development - This mail sent through IMP: http://horde.org/imp/ - This mail sent through IMP: http://horde.org/imp/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-531524 ] Error in passivation of bean with JMS
Bugs item #531524, was opened at 2002-03-18 12:28 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=531524group_id=22866 Category: JBossMQ Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 8 Submitted By: Marius Kotsbak (mkotsbak) Assigned to: Jason Dillon (user57) Summary: Error in passivation of bean with JMS Initial Comment: I get this exception when using JMS as managed resource: java.rmi.ServerException: Could not passivate; nested exception is: java.io.NotSerializableException: org.jboss.resource.adapter.jms.JmsManagedConnectionFactory java.io.NotSerializableException: org.jboss.resource.adapter.jms.JmsManagedConnectionFactory at java.io.ObjectOutputStream.outputObject(ObjectOutputStream.java:1161) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java(Compiled Code)) at java.io.ObjectOutputStream.outputClassFields(ObjectOutputStream.java(Compiled Code)) at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:486) at java.io.ObjectOutputStream.outputObject(ObjectOutputStream.java:1227) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java(Compiled Code)) at java.io.ObjectOutputStream.outputClassFields(ObjectOutputStream.java(Compiled Code)) at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:486) at java.io.ObjectOutputStream.outputObject(ObjectOutputStream.java:1227) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java(Compiled Code)) at org.jboss.ejb.plugins.StatefulSessionFilePersistenceManager.passivateSession(StatefulSessionFilePersistenceManager.java:287) at org.jboss.ejb.plugins.StatefulSessionInstanceCache.passivate(StatefulSessionInstanceCache.java:65) at org.jboss.ejb.plugins.AbstractInstanceCache$1.execute(AbstractInstanceCache.java:737) at org.jboss.util.WorkerQueue$QueueLoop.run(WorkerQueue.java:206) at java.lang.Thread.run(Thread.java:498) Is this a bug (the class should be serializable for example), or have I done something wrong (then it is a bg too, because the errormessage should be better!) Marius K -- Comment By: Jason Dillon (user57) Date: 2002-04-07 15:05 Message: Logged In: YES user_id=15045 Please confrim that your bean has a field which is a QueueConnection and not a QueueConnectionFactory. The factory case should be handled by the container, but not the connection. If you are holding a connection, make it transient, then on activate reconnect either by looking up the factory or save the factory as a non-transient field. If the container does not properly handle the factory as a field, then it is a bug. Let us know so we can close this bug. We should also make sure there is a test case which covers this, but I haven't time to look right now. --jason -- Comment By: Marius Kotsbak (mkotsbak) Date: 2002-04-05 03:59 Message: Logged In: YES user_id=366650 I have a QueueConnection -- Comment By: Jason Dillon (user57) Date: 2002-04-04 16:18 Message: Logged In: YES user_id=15045 Hrm... do you have a TopicConnection or QueueConnection? Perhaps this is a bug, but I am not sure exactly. The 2.0 specs says: 7.4.1 Instance passivation and conversational state ... The Bean Provider is required to ensure that the ejbPassivate method leaves the instance fields ready to be serialized by the Container. The objects that are assigned to the instances non-transient fields after the ejbPassivate method completes must be one of the following: ... o A reference to a resource manager connection factory. This means (as I read it) that if you have a ConnectionFactory as a field that the container should handle passivation, but if you have a Conection then you should stop/close/null it out in ejbPassivate(). I don't currently know if the container correctly handle this though... need to check. --jason -- Comment By: Marius Kotsbak (mkotsbak) Date: 2002-03-19 10:55 Message: Logged In: YES user_id=366650 I am in fact not holding A ConnectionFactory in my bean! The only attributes of the bean are Queue and QueueConnection. I only use the QueueConnectionFactory as a local variable in ejbCreate (like the example). Have anyone else used managed JMS successfully? -- Comment By: Chris Harris (charris) Date: 2002-03-19 08:29 Message: Logged In: YES user_id=8915 The example code keeps a Topic and a TopicConnection around as instance variables of the bean. Presumably these are serialisable. Your problem is with keeping a TopicConnectionFactory around, which
[JBoss-dev] JBoss.net class not found and deployer registration problems
Christoph/whoever, I have been trying to get JBoss.net up and running to have a play about with, and have hit a few problems. Before going too much further, I just wanted to check that I'm not doing something stupid, as I'm a relative novice with both JBoss and Axis. I'm using the head revision of jboss-all from earlier this evening, with Sun JDK 1.3.1-b24 on SuSE Linux w/ hotspot client VM in mixed mode. I built using ./build.sh all, then ./build.sh -Dgroups=optional. Firstly, I got a NoClassDefFoundError trying on starting JBoss.net trying to find some of the techtrader classes. I temporarily fixed this by copying thirdparty/techtrader/lib/tt-bytecode.jar to build/output/jboss-3.0.0beta2/lib, but it should really be fixed in the jboss.net build.xml as far as I can see (looks simple enough, I will submit a patch if someone can integrate it for me). This got rid of the initial error, but I now get an exception as follows: 21:50:09,318 ERROR [AxisService] Could not register with MainDeployer ReflectionException: Exception when calling method for 'addDeployer(,org.jboss.deployment.SubDeployer)' Cause: java.lang.IllegalArgumentException: argument type mismatch at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispat cher.java:312) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:441) at org.jboss.net.axis.server.AxisService.startService(AxisService.java:329) at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:162) at java.lang.reflect.Method.invoke(Native Method) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispat cher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:441) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.jav a:805) at $Proxy1.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:309) at org.jboss.system.ServiceController.start(ServiceController.java:327) at java.lang.reflect.Method.invoke(Native Method) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispat cher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:441) at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174) at $Proxy4.start(Unknown Source) at org.jboss.deployment.SARDeployer.start(SARDeployer.java:278) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:672) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:517) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:480) at java.lang.reflect.Method.invoke(Native Method) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispat cher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:441) at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174) at $Proxy5.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanne r.java:329) at org.jboss.deployment.scanner.URLDeploymentScanner.scanDirectory(URLDeploymen tScanner.java:516) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner. java:389) at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(Abstract DeploymentScanner.java:237) at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:162) at java.lang.reflect.Method.invoke(Native Method) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispat cher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:441) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.jav a:805) at $Proxy1.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:309) at org.jboss.system.ServiceController.start(ServiceController.java:327) at java.lang.reflect.Method.invoke(Native Method) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispat cher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:441) at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:324) at org.jboss.system.server.ServerImpl.start(ServerImpl.java:213) at org.jboss.Main.boot(Main.java:138) at org.jboss.Main$1.run(Main.java:371) at java.lang.Thread.run(Thread.java:484) I had a quick look and it appears that AxisService is attempting to register itself with the main deployer, but doesn't seem to implement the SubDeployer interface, instead implementing (via AxisServiceMBean) SubDeployerMBean from the server project. From a cursory glance, it looks like it should probably extend SubDeployerSupport instead of
AW: AW: [JBoss-dev] JMX HTML... From the Pure Fluff Department...
Jason, as you can see there are a lot of people trying to help building a console/management tool for JBosss. In the project I am currently involved the project manager is really looking for a tool which provides monitoring functions like the JSR-77 specs provide. He always looks for something like the BEA console. Is that something you had in mind or just more a replacement for the SUN HTML-Adaptor? Thanks, --Marcus -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]Im Auftrag von Jason Dillon Gesendet: Sonntag, 7. April 2002 23:40 An: Jim Birchfield Cc: [EMAIL PROTECTED]; Jim Birchfield; [EMAIL PROTECTED] Betreff: RE: AW: [JBoss-dev] JMX HTML... From the Pure Fluff Department... Please let me know when you have finished your cleaning and have published the sources. I am going to be busy for the next week (perhaps, unless I under estimate my efficency =), but I have been planing to start a JBoss/Console module, which contains web, command line telnet/ssh console access to JBoss. I would be interesed to see how your work might fit in there. --jason Quoting Jim Birchfield [EMAIL PROTECTED]: I would love to do that!(integrate with JBoss.org) I am hoping to get a core code base out to SourceForge sometime this week. I need to clean up some stuff, and then I can push it out. The framework is built using Jetty deployed as an MBean, and Tapestry as the web framework driving the presentation. James Birchfield Director, Application Development Genscape, Inc. (502) 583-2298 (o) (502) 639-3136 (c) -Original Message- From: Jason Dillon [mailto:[EMAIL PROTECTED]] Sent: Sunday, April 07, 2002 4:48 PM To: [EMAIL PROTECTED]; James Birchfield Subject: Re: AW: [JBoss-dev] JMX HTML... From the Pure Fluff Department... Very nice, just looked at the shoot, will look into more later. Are you expecting to maintain this yourself? Just currious if you had though of making this a part og JBoss, thus opening up the maintenece to a wider audience? Either way, looks great. I have been meaning to do something like this for a while, and or convince some people I work with to do it for me. Have to look in more detail, but if nothing stands out as problem we could make this the default jmx html adapter and be done with the sun fluff. --jason Quoting James Birchfield [EMAIL PROTECTED]: Project is a href=http://jmxview.sf.net;here/a _ View thread online: http://main.jboss.org/thread.jsp?forum=66thread=11622 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development - This mail sent through IMP: http://horde.org/imp/ - This mail sent through IMP: http://horde.org/imp/ ___ 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: AW: AW: [JBoss-dev] JMX HTML... From the Pure Fluff Department...
In the project I am currently involved the project manager is really looking for a tool which provides monitoring functions like the JSR-77 specs provide. He always looks for something like the BEA console. Is that something you had in mind or just more a replacement for the SUN HTML-Adaptor? Short-term, yes a direct replacement for the SUN adapter, with a few changes to provide JBoss branding and possibly (if easy to implement) collapsable hierarchy of JMX domains, so the first look shows only the top level domains and does not overwhelm the admin with ever MBean in the system. Longger-term, I want a simple pluggable view system which uses consistent lf. The current SUN-like adapter would then become a view (perhaps the default, using tab-like nav or something similar simple). Then a JNDI view, with collapsable tree-like view (would be a replacement for curremt JNDIView MBean) Then other views can be created which provide a rich set of admin functionality on top of the basic MBean system. For example, consider a wizard-like view which walked an admin through the steps of creating a new JMS Queue or ConnectionFactory. The view would gather information, then eventually invoke some target MBean to get the work done. I think that JMX is a good base for raw administration, but we need to provide some sugar on top to make it easier and straight forward for anyone to use. That said, I don't have time or the expertese to build such a web app now, and perhaps never will. So I am trying to motivate others with such skills and motivation to work together to make this happen. Once my plate empties a little more, I will be starting to work on the telnet/ssh access + sctiptable interface, as I am very motivated to do that. If you have time and energy to help with the web console, along with anyone else (I am sure there are at least a few), that would be great! The concept is simple, and the code is not hard... just need to find the right people who can spare some time. --jason - This mail sent through IMP: http://horde.org/imp/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Patched HSQLDB sources?
Great, let us know when you have something to look at. --jason Quoting Peter Fagerlund [EMAIL PROTECTED]: on 07-04-2 23.48, Jason Dillon at [EMAIL PROTECTED] wrote: It growed on me to be able to have all listerners (NAME:PORT) registred in a component for easy access by other components, to be able to understand what ports are running in the WM and be JMX intra-machine negotiation capable. what do You think ? ... I think it is a good idea also, but perhaps difficult/tricky to implement in a generic fashion. It is easy - I send You some birds ! ... I have not thought about this in much detail, so perhaps it is easier than I expect. XP == Messure Twice Cut Once ... or was that ZEN ... I forget - heh... If you have a design + usage schenarios for the current set of port using components which JBoss uses, I would be interested to see it. I would like to get feedback from U all before trying to cut a first implementation ... /peter_f - This mail sent through IMP: http://horde.org/imp/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Automated JBoss Testsuite Results: 8-April-2002
JBoss daily test results SUMMARY Number of tests run: 568 Successful tests: 542 Errors:19 Failures: 7 [time of test: 8 April 2002 0:59 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
Re: [JBoss-dev] JBoss 3 users -- warning of impending configuration change
The attachment seems to be missing david jencks On 2002.04.07 19:32:11 -0400 Stephen Coy wrote: OK. I got it working. I didn't look closely enough at the tags and was commenting out the CachedConnectionManager dependency and the TransactionManager attribute, together with the SecurityDomainJndiName attribute. I thought they were all nested in the dependency. The attached oracle-service.xml works for me. _ View thread online: http://main.jboss.org/thread.jsp?forum=66thread=12301 ___ 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 3 users -- warning of impending configuration change
Probably because I posted from the forum. It seems to be available there. _ View thread online: http://main.jboss.org/thread.jsp?forum=66thread=12301 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Automated JBoss Testsuite Results: 8-April-2002
JBoss daily test results SUMMARY Number of tests run: 575 Successful tests: 550 Errors:18 Failures: 7 [time of test: 8 April 2002 1:46 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] Automated JBoss Testsuite Results: 8-April-2002
JBoss daily test results SUMMARY Number of tests run: 575 Successful tests: 553 Errors:18 Failures: 4 [time of test: 8 April 2002 2:32 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: 8-April-2002
JBoss daily test results SUMMARY Number of tests run: 575 Successful tests: 549 Errors:19 Failures: 7 [time of test: 8 April 2002 3:45 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
[JBoss-dev] Automated JBoss Testsuite Results: 8-April-2002
JBoss daily test results SUMMARY Number of tests run: 575 Successful tests: 551 Errors:18 Failures: 6 [time of test: 8 April 2002 5:7 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] Strange problem
Hi Everybody I am facing a very strange problem in my application which is running in Jboss. I am creating a Request in my application and saving that Request in the database(MySql), that mean, I inserted a new row in a table. When I come to my application again to see that Request , the application says that unable to find the request. Strange!! But when I tried for next time, the application shows the Request without any exception. This problem is not repeatable but occurs very frequently. Please give me some suggestion regarding this error. Thanks a lot in advance Mahesh ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Automated JBoss Testsuite Results: 8-April-2002
JBoss daily test results SUMMARY Number of tests run: 575 Successful tests: 551 Errors:18 Failures: 6 [time of test: 8 April 2002 6:8 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: 8-April-2002
JBoss daily test results SUMMARY Number of tests run: 544 Successful tests: 221 Errors:315 Failures: 8 [time of test: 8 April 2002 7:12 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
