[JBoss-dev] [ jboss-Change Notes-416227 ] Resource adapters can be auto-deployed
Change Notes item #416227, was updated on 2001-04-14 22:50 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=381174&aid=416227&group_id=22866 Category: None Group: v2.4 Status: Open Priority: 5 Submitted By: Toby Allsopp (tobyallsopp) Assigned to: Nobody/Anonymous (nobody) Summary: Resource adapters can be auto-deployed Initial Comment: It is possible to configure the AutoDeployer service to use the RARDeployer service from the JBossCX module to deploy resource adapters. An example of this is included in jboss.jcml. This example sets up the directory deploy/lib to be watched for resource adapters. The bundled Minerva JDBC resource adapters are installed in this directory and are thus available at server startup. -- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=381174&aid=416227&group_id=22866 ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jboss/src/lib jbosscx-0.2.jar
User: tobyallsopp Date: 01/04/14 22:41:21 Modified:src/lib jbosscx-0.2.jar Log: Modified AutoDeployer so that it can be configured to deploy RARs (inspired by Patch #415321 from David Jencks). - added jboss-deployer target to build.xml that builds dist/external/jboss-deployer.jar which contains the classes required by deployers that implement org.jboss.deployment.DeployerMBean. - added a method to DeployerMBean: getDeployableFilter that returns a java.io.FilenameFilter that AutoDeployer uses to decide what it can deploy rather than using a hardcoded list of filename extensions. - made J2eeDeployerMBean extend DeployerMBean and added an implementation of getDeployableFilter to J2eeDeployer. - updated JBossCX jar so that RARDeployer implements getDeployableFilter. - added an AutoDeployer watching deploy/lib and using RARDeployer to jboss.jcml. - changed the JBossCX examples in jboss.jcml to use the Minerva resource adapters bundled with JBoss instead of the BlackBox adapters. - temporarily removed the Minerva XA resource adapter until Aaron fixes it. - some minor cosmetic changesto jboss.jcml. Revision ChangesPath 1.4 +71 -64jboss/src/lib/jbosscx-0.2.jar <> ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jboss/src/etc/deploy minerva-xa-1.0b3.rar
User: tobyallsopp Date: 01/04/14 22:41:21 Removed: src/etc/deploy minerva-xa-1.0b3.rar Log: Modified AutoDeployer so that it can be configured to deploy RARs (inspired by Patch #415321 from David Jencks). - added jboss-deployer target to build.xml that builds dist/external/jboss-deployer.jar which contains the classes required by deployers that implement org.jboss.deployment.DeployerMBean. - added a method to DeployerMBean: getDeployableFilter that returns a java.io.FilenameFilter that AutoDeployer uses to decide what it can deploy rather than using a hardcoded list of filename extensions. - made J2eeDeployerMBean extend DeployerMBean and added an implementation of getDeployableFilter to J2eeDeployer. - updated JBossCX jar so that RARDeployer implements getDeployableFilter. - added an AutoDeployer watching deploy/lib and using RARDeployer to jboss.jcml. - changed the JBossCX examples in jboss.jcml to use the Minerva resource adapters bundled with JBoss instead of the BlackBox adapters. - temporarily removed the Minerva XA resource adapter until Aaron fixes it. - some minor cosmetic changesto jboss.jcml. ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jboss/src/main/org/jboss/ejb AutoDeployer.java
User: tobyallsopp
Date: 01/04/14 22:41:21
Modified:src/main/org/jboss/ejb AutoDeployer.java
Log:
Modified AutoDeployer so that it can be configured to deploy RARs (inspired
by Patch #415321 from David Jencks).
- added jboss-deployer target to build.xml that builds
dist/external/jboss-deployer.jar which contains the classes required by
deployers that implement org.jboss.deployment.DeployerMBean.
- added a method to DeployerMBean: getDeployableFilter that returns a
java.io.FilenameFilter that AutoDeployer uses to decide what it can deploy
rather than using a hardcoded list of filename extensions.
- made J2eeDeployerMBean extend DeployerMBean and added an implementation
of getDeployableFilter to J2eeDeployer.
- updated JBossCX jar so that RARDeployer implements getDeployableFilter.
- added an AutoDeployer watching deploy/lib and using RARDeployer to
jboss.jcml.
- changed the JBossCX examples in jboss.jcml to use the Minerva resource
adapters bundled with JBoss instead of the BlackBox adapters.
- temporarily removed the Minerva XA resource adapter until Aaron fixes it.
- some minor cosmetic changesto jboss.jcml.
Revision ChangesPath
1.13 +46 -39jboss/src/main/org/jboss/ejb/AutoDeployer.java
Index: AutoDeployer.java
===
RCS file: /cvsroot/jboss/jboss/src/main/org/jboss/ejb/AutoDeployer.java,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- AutoDeployer.java 2001/03/25 20:27:04 1.12
+++ AutoDeployer.java 2001/04/15 05:41:21 1.13
@@ -10,6 +10,7 @@
import java.net.URLClassLoader;
import java.net.MalformedURLException;
import java.io.File;
+import java.io.FilenameFilter;
import java.io.IOException;
import java.util.Iterator;
import java.util.StringTokenizer;
@@ -17,30 +18,33 @@
import java.util.ArrayList;
import javax.management.MBeanServer;
import javax.management.MBeanException;
+import javax.management.ReflectionException;
import javax.management.RuntimeErrorException;
import javax.management.RuntimeMBeanException;
import javax.management.ObjectName;
import org.jboss.logging.Log;
-import org.jboss.util.MBeanProxy;
import org.jboss.util.ServiceMBeanSupport;
-import org.jboss.deployment.J2eeDeployerMBean;
/**
- * The AutoDeployer is used to automatically deploy EJB-jars.
- * It can be used on either .jar or .xml files. The AutoDeployer can
- * be configured to "watch" one or more files. If they are updated they will
- * be redeployed.
+ * The AutoDeployer is used to automatically deploy applications or
+ * components thereof.
*
- * If it is set to watch a directory instead of a single file, all files within
that
- * directory will be watched separately.
+ *It can be used on either .jar or .xml files. The AutoDeployer
+ * can be configured to "watch" one or more files. If they are
+ * updated they will be redeployed.
*
- * When a jar is to be deployed, the AutoDeployer will use a ContainerFactory
to deploy it.
+ *If it is set to watch a directory instead of a single file,
+ * all files within that directory will be watched separately.
*
- * @see ContainerFactory
+ *When a file is to be deployed, the AutoDeployer will use the
+ * configured deployer to deploy it.
+ *
+ * @see org.jboss.deployment.J2eeDeployer
* @author Rickard Öberg ([EMAIL PROTECTED])
- * @version $Revision: 1.12 $
+ * @author Toby Allsopp ([EMAIL PROTECTED])
+ * @version $Revision: 1.13 $
*/
public class AutoDeployer
extends ServiceMBeanSupport
@@ -74,6 +78,10 @@
// URL list
String urlList = "";
+ /** Filter to decide which files are deployable and which should be
+ ignored */
+ FilenameFilter deployableFilter = null;
+
// Static
// Constructors --
@@ -136,18 +144,15 @@
{
URL fileUrl = files[idx].toURL();
- // Check if it's a JAR or zip or ear or war
- if (!(fileUrl.getFile().endsWith(".jar") ||
-fileUrl.getFile().endsWith(".ear") ||
-fileUrl.getFile().endsWith(".war") ||
-fileUrl.getFile().endsWith(".zip")))
- continue; // Was not a JAR or zip - skip it...
+ // Check if it's a deployable file
+ if (!deployableFilter.accept(null, fileUrl.getFile()))
+ continue; // Was not deployable - skip it...
if (deployedURLs.get(fileUrl) == null)
{
[JBoss-dev] CVS update: jboss/src/main/org/jboss/deployment DeployerMBean.java DeploymentException.java J2eeDeployer.java J2eeDeployerMBean.java J2eeDeploymentException.java
User: tobyallsopp
Date: 01/04/14 22:41:21
Modified:src/main/org/jboss/deployment DeployerMBean.java
DeploymentException.java J2eeDeployer.java
J2eeDeployerMBean.java J2eeDeploymentException.java
Log:
Modified AutoDeployer so that it can be configured to deploy RARs (inspired
by Patch #415321 from David Jencks).
- added jboss-deployer target to build.xml that builds
dist/external/jboss-deployer.jar which contains the classes required by
deployers that implement org.jboss.deployment.DeployerMBean.
- added a method to DeployerMBean: getDeployableFilter that returns a
java.io.FilenameFilter that AutoDeployer uses to decide what it can deploy
rather than using a hardcoded list of filename extensions.
- made J2eeDeployerMBean extend DeployerMBean and added an implementation
of getDeployableFilter to J2eeDeployer.
- updated JBossCX jar so that RARDeployer implements getDeployableFilter.
- added an AutoDeployer watching deploy/lib and using RARDeployer to
jboss.jcml.
- changed the JBossCX examples in jboss.jcml to use the Minerva resource
adapters bundled with JBoss instead of the BlackBox adapters.
- temporarily removed the Minerva XA resource adapter until Aaron fixes it.
- some minor cosmetic changesto jboss.jcml.
Revision ChangesPath
1.2 +13 -1 jboss/src/main/org/jboss/deployment/DeployerMBean.java
Index: DeployerMBean.java
===
RCS file: /cvsroot/jboss/jboss/src/main/org/jboss/deployment/DeployerMBean.java,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- DeployerMBean.java2001/01/15 05:06:54 1.1
+++ DeployerMBean.java2001/04/15 05:41:21 1.2
@@ -7,6 +7,7 @@
package org.jboss.deployment;
import java.io.IOException;
+import java.io.FilenameFilter;
import java.net.MalformedURLException;
import org.jboss.util.ServiceMBean;
@@ -16,7 +17,7 @@
* components.
*
* @author Toby Allsopp ([EMAIL PROTECTED])
- * @version $Revision: 1.1 $
+ * @version $Revision: 1.2 $
*/
public interface DeployerMBean
extends ServiceMBean
@@ -24,6 +25,17 @@
// Constants -
// Public
+
+ /**
+* Provides a filter that decides whether a file can be deployed by
+* this deployer based on the filename. This is for the benefit of
+* the {@link org.jboss.ejb.AutoDeployer} service.
+*
+* @return a FilenameFilter that only
+* accepts files with names that can be
+* deployed by this deployer
+*/
+ FilenameFilter getDeployableFilter();
void deploy (String url)
throws MalformedURLException, IOException, DeploymentException;
1.2 +6 -7 jboss/src/main/org/jboss/deployment/DeploymentException.java
Index: DeploymentException.java
===
RCS file:
/cvsroot/jboss/jboss/src/main/org/jboss/deployment/DeploymentException.java,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- DeploymentException.java 2001/01/15 05:06:54 1.1
+++ DeploymentException.java 2001/04/15 05:41:21 1.2
@@ -11,9 +11,8 @@
* deployed.
*
* @see DeployerMBean
- * @author Rickard Öberg ([EMAIL PROTECTED])
* @author Toby Allsopp ([EMAIL PROTECTED])
- * @version $Revision: 1.1 $
+ * @version $Revision: 1.2 $
*/
public class DeploymentException
extends Exception
@@ -21,7 +20,7 @@
// Attributes
/** The root cause of this exception */
- protected Exception cause;
+ protected Throwable cause;
// Static
@@ -32,20 +31,20 @@
super(message);
}
- public DeploymentException(String message, Exception e)
+ public DeploymentException(String message, Throwable cause)
{
super(message);
- cause = e;
+ this.cause = cause;
}
// Public
- public Exception getCause() { return cause; }
+ public Throwable getCause() { return cause; }
public String toString()
{
return cause == null ? super.toString()
- : super.toString()+", Cause: "+cause;
+ : super.toString() + ", Cause: " + cause;
}
}
1.21 +20 -2 jboss/src/main/org/jboss/deployment/J2eeDeployer.java
Index: J2eeDeployer.java
===
RCS file: /cvsroot/jboss/jboss/src/main/org/j
[JBoss-dev] CVS update: jboss/src/etc/conf/default jboss.jcml
User: tobyallsopp Date: 01/04/14 22:41:21 Modified:src/etc/conf/default jboss.jcml Log: Modified AutoDeployer so that it can be configured to deploy RARs (inspired by Patch #415321 from David Jencks). - added jboss-deployer target to build.xml that builds dist/external/jboss-deployer.jar which contains the classes required by deployers that implement org.jboss.deployment.DeployerMBean. - added a method to DeployerMBean: getDeployableFilter that returns a java.io.FilenameFilter that AutoDeployer uses to decide what it can deploy rather than using a hardcoded list of filename extensions. - made J2eeDeployerMBean extend DeployerMBean and added an implementation of getDeployableFilter to J2eeDeployer. - updated JBossCX jar so that RARDeployer implements getDeployableFilter. - added an AutoDeployer watching deploy/lib and using RARDeployer to jboss.jcml. - changed the JBossCX examples in jboss.jcml to use the Minerva resource adapters bundled with JBoss instead of the BlackBox adapters. - temporarily removed the Minerva XA resource adapter until Aaron fixes it. - some minor cosmetic changesto jboss.jcml. Revision ChangesPath 1.24 +52 -22jboss/src/etc/conf/default/jboss.jcml Index: jboss.jcml === RCS file: /cvsroot/jboss/jboss/src/etc/conf/default/jboss.jcml,v retrieving revision 1.23 retrieving revision 1.24 diff -u -r1.23 -r1.24 --- jboss.jcml2001/04/13 21:12:37 1.23 +++ jboss.jcml2001/04/15 05:41:21 1.24 @@ -7,24 +7,32 @@ --> - + + + 8083 - + + + 1099 - + + + 300 - + + + - + + + + org.hsql.jdbcDriver,org.enhydra.instantdb.jdbc.idbDriver @@ -107,7 +118,9 @@ 0 - + + + true @@ -149,8 +162,11 @@ J2EE:service=J2eeDeployer ../deploy + + + + - @@ -187,13 +203,18 @@ - + +JCA:service=RARDeployer +../deploy/lib + + + -BlackBoxDS + name="JCA:service=ConnectionFactoryLoader,name=MinervaDS"> +MinervaDS JCA:service=RARDeployer -Black Box LocalTx Adapter +Minerva JDBC LocalTransaction ResourceAdapter ConnectionURL=jdbc:HypersonicSQL:hsql://localhost:1476 @@ -229,26 +250,26 @@ + + + + - @@ -290,7 +314,9 @@ 8082 - + + + Mail mail.properties @@ -298,10 +324,14 @@ password + + - + + + ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jboss/src/build build.xml
User: tobyallsopp Date: 01/04/14 22:41:21 Modified:src/build build.xml Log: Modified AutoDeployer so that it can be configured to deploy RARs (inspired by Patch #415321 from David Jencks). - added jboss-deployer target to build.xml that builds dist/external/jboss-deployer.jar which contains the classes required by deployers that implement org.jboss.deployment.DeployerMBean. - added a method to DeployerMBean: getDeployableFilter that returns a java.io.FilenameFilter that AutoDeployer uses to decide what it can deploy rather than using a hardcoded list of filename extensions. - made J2eeDeployerMBean extend DeployerMBean and added an implementation of getDeployableFilter to J2eeDeployer. - updated JBossCX jar so that RARDeployer implements getDeployableFilter. - added an AutoDeployer watching deploy/lib and using RARDeployer to jboss.jcml. - changed the JBossCX examples in jboss.jcml to use the Minerva resource adapters bundled with JBoss instead of the BlackBox adapters. - temporarily removed the Minerva XA resource adapter until Aaron fixes it. - some minor cosmetic changesto jboss.jcml. Revision ChangesPath 1.61 +34 -0 jboss/src/build/build.xml Index: build.xml === RCS file: /cvsroot/jboss/jboss/src/build/build.xml,v retrieving revision 1.60 retrieving revision 1.61 diff -u -r1.60 -r1.61 --- build.xml 2001/04/15 05:12:12 1.60 +++ build.xml 2001/04/15 05:41:20 1.61 @@ -50,10 +50,12 @@ + + @@ -459,6 +465,34 @@ includes="org/jboss/util/**, org/jboss/logging/**, org/jboss/monitor/**" +/> + + + + + + + + + + + + + + + + ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jboss/src/build build.xml
User: tobyallsopp Date: 01/04/14 22:12:12 Modified:src/build build.xml Log: Removed org.jboss.dependencies from list of packages so that javadocs will build. Revision ChangesPath 1.60 +1 -1 jboss/src/build/build.xml Index: build.xml === RCS file: /cvsroot/jboss/jboss/src/build/build.xml,v retrieving revision 1.59 retrieving revision 1.60 diff -u -r1.59 -r1.60 --- build.xml 2001/04/10 22:45:17 1.59 +++ build.xml 2001/04/15 05:12:12 1.60 @@ -43,7 +43,7 @@ - + ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbosscx/src/main/org/jboss/resource RARDeployer.java RARDeployerMBean.java RARMetaData.java
User: tobyallsopp
Date: 01/04/14 21:31:39
Modified:src/main/org/jboss/resource RARDeployer.java
RARDeployerMBean.java RARMetaData.java
Log:
- Reduced verbosity of deployment of RARs containing license terms
- Removed classes duplicated from the core - these are now in the
jboss-deployer.jar file
- Implemented getDeplyableFilter for the upcoming AutoDeployer enhancement
Revision ChangesPath
1.2 +13 -1 jbosscx/src/main/org/jboss/resource/RARDeployer.java
Index: RARDeployer.java
===
RCS file: /cvsroot/jboss/jbosscx/src/main/org/jboss/resource/RARDeployer.java,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- RARDeployer.java 2001/02/06 06:54:40 1.1
+++ RARDeployer.java 2001/04/15 04:31:39 1.2
@@ -10,6 +10,7 @@
import java.io.FileFilter;
import java.io.FileInputStream;
import java.io.FileOutputStream;
+import java.io.FilenameFilter;
import java.io.IOException;
import java.io.InputStream;
import java.io.OutputStream;
@@ -47,7 +48,7 @@
* ConnectionFactoryLoader service.
*
* @author Toby Allsopp ([EMAIL PROTECTED])
- * @version $Revision: 1.1 $
+ * @version $Revision: 1.2 $
*
* @see org.jboss.resource.ConnectionFactoryLoader
*/
@@ -72,6 +73,17 @@
// Public
+ public FilenameFilter getDeployableFilter()
+ {
+ return new FilenameFilter()
+ {
+public boolean accept(File dir, String filename)
+{
+ return filename.endsWith(".rar");
+}
+ };
+ }
+
// RARDeployerMBean implementation ---
// DeployerMBeanSupport overrides -
1.2 +3 -3 jbosscx/src/main/org/jboss/resource/RARDeployerMBean.java
Index: RARDeployerMBean.java
===
RCS file: /cvsroot/jboss/jbosscx/src/main/org/jboss/resource/RARDeployerMBean.java,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- RARDeployerMBean.java 2001/02/06 06:54:40 1.1
+++ RARDeployerMBean.java 2001/04/15 04:31:39 1.2
@@ -9,11 +9,11 @@
import org.jboss.deployment.DeployerMBean;
/**
- *
+ * Exposed management interface for the RARDeployer
+ * service.
*
- * @see
* @author Toby Allsopp ([EMAIL PROTECTED])
- * @version $Revision: 1.1 $
+ * @version $Revision: 1.2 $
*/
public interface RARDeployerMBean
extends DeployerMBean
1.3 +8 -12 jbosscx/src/main/org/jboss/resource/RARMetaData.java
Index: RARMetaData.java
===
RCS file: /cvsroot/jboss/jbosscx/src/main/org/jboss/resource/RARMetaData.java,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- RARMetaData.java 2001/02/08 05:08:19 1.2
+++ RARMetaData.java 2001/04/15 04:31:39 1.3
@@ -26,7 +26,7 @@
*
* @see RARDeployer
* @author Toby Allsopp ([EMAIL PROTECTED])
- * @version $Revision: 1.2 $
+ * @version $Revision: 1.3 $
*/
public class RARMetaData
// extends Y
@@ -325,17 +325,13 @@
"license-required");
Element descriptionE = MetaData.getOptionalChild(element,
"description");
- boolean required = new
Boolean(getElementContent(requiredE).trim()).booleanValue();
- if(required) {
-log.warning("By using this resource adapter, you are accepting the");
-log.warning("following license. If you object to the license, you");
-log.warning("must undeploy the resource adapter immediately.");
-log.warning(getElementContent(descriptionE).trim());
- } else {
-log.warning("This resource adapter has license terms that you may");
-log.warning("want to be aware of, though you are not required to");
-log.warning("accept them in order to use the adapter.");
- }
+ boolean required =
+new Boolean(getElementContent(requiredE).trim()).booleanValue();
+ if(required)
+log.warning("Required license terms present. See deployment " +
+"descriptor.");
+ else
+log.log("License terms present. See deployment descriptor.");
}
catch (org.jboss.ejb.DeploymentException de)
{
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbosscx/src/build build.xml
User: tobyallsopp Date: 01/04/14 21:31:39 Modified:src/build build.xml Log: - Reduced verbosity of deployment of RARs containing license terms - Removed classes duplicated from the core - these are now in the jboss-deployer.jar file - Implemented getDeplyableFilter for the upcoming AutoDeployer enhancement Revision ChangesPath 1.3 +1 -1 jbosscx/src/build/build.xml Index: build.xml === RCS file: /cvsroot/jboss/jbosscx/src/build/build.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- build.xml 2001/02/06 07:27:50 1.2 +++ build.xml 2001/04/15 04:31:39 1.3 @@ -30,7 +30,7 @@ - + ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbosscx/src/lib jboss-deployer.jar
User: tobyallsopp Date: 01/04/14 21:31:39 Added: src/lib jboss-deployer.jar Log: - Reduced verbosity of deployment of RARs containing license terms - Removed classes duplicated from the core - these are now in the jboss-deployer.jar file - Implemented getDeplyableFilter for the upcoming AutoDeployer enhancement Revision ChangesPath 1.1 jbosscx/src/lib/jboss-deployer.jar <> ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbosscx/src/main/org/jboss/deployment DeployerMBean.java DeployerMBeanSupport.java DeploymentException.java
User: tobyallsopp Date: 01/04/14 21:31:39 Removed: src/main/org/jboss/deployment DeployerMBean.java DeployerMBeanSupport.java DeploymentException.java Log: - Reduced verbosity of deployment of RARs containing license terms - Removed classes duplicated from the core - these are now in the jboss-deployer.jar file - Implemented getDeplyableFilter for the upcoming AutoDeployer enhancement ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] DependencyManager & jboss.dependencies
Just to clarify, I should talk to Peter about adding a openjms contrib
module. And for the tests, this is from the jbosstest module... perhaps
the bin/mdbtest.sh script? Is there more documentation on this anywhere?
--jason
On Sun, 15 Apr 2001, Juha Lindfors wrote:
>
> Factoring out the openjms stuff from the server to a contrib module seems
> like a good idea to me. Ping Peter Antman for comments/help (the email is
> at SF) before commiting. Also run mdb tests from test module.
>
> the log4j should be as easy as removing the log4j-old.jar from the cvs,
> don't remove any classes, log4j is being used
>
> -- Juha
>
>
> At 16:31 14.4.2001 -0700, you wrote:
> >Ok, it looks like the OpenJMS is only referenced directly in these
> >files:
> >
> > o src/main/org/jboss/jms/asf/OpenJMSServerSessionPoolFactory.java:
> >
> > import org.exolab.jms.client.OpenJMSServerSessionPool;
> > import org.exolab.jms.client.JmsServerSessionPool;
> >org.exolab.core.logger.LoggerIfc logger =
> > org.exolab.core.logger.LoggerFactory.create(null, null);
> >org.exolab.core.logger.LogEventType event =
> > org.exolab.core.logger.LogEventType.getLogEventType("debug");
> >
> > o src/main/org/jboss/jms/jndi/OpenJMSProvider.java:
> >
> >public static final String INITIAL_CONTEXT_FACTORY =
> > "org.exolab.jms.jndi.rmi.RmiJndiInitialContextFactory";
> >private static final String HOST_PROP_NAME="org.exolab.jms.jndi.Host";
> >private static final String
> > PORT_PROP_NAME="org.exolab.jms.jndi.PortNumber";
> >
> > o src/main/org/jboss/ejb/plugins/jms/JMSContainerInvoker.java:
> >
> >public String getType() { return "org.exolab.castor.jdo.DataObjects";
> >
> > //import org.exolab.jms.jndi.JndiConstants;
> > import org.exolab.jms.client.JmsServerSessionPool;
> >
> >---
> >
> >The last of which imports an OpenJMS class, but does not make use of it.
> >Except for JMSContainerInvoker, these classes are not referenced anywhere
> >else in the system either.
> >
> >I can understand wanting to clean up unused sources and thirdparty
> >libraries, but I am wondering what if someone wanted to make use of
> >OpenJMS? These classes seem like a good candidate for an external plugin
> >module, but I am not really sure what the precedent is for that.
> >
> >It would be nice to have a 'plugin' module, which could some child
> >modules, one for 'openjms'. Perhaps that is what the 'contrib' module is
> >for?
> >
> >With the above OpenJMS specific classes removed and these library files:
> >
> > o src/lib/openjms-client-patched-0.5.1.jar
> > o src/lib/openjms-patched-0.5.1.jar
> > o src/lib/openjms-pool.jar
> > o src/lib/openjms-rmi-patched-0.5.1.jar
> >
> >I was able to build and execute the default configuration with no errors.
> >
> >So any ideas on what I should do? Should I proceed and commit these
> >changes, thus removing OpenJMS support from JBoss, or should I attempt to
> >preserve these classes in an external project for those who still use
> >OpenJMS?
> >
> >I have not investigated the log4j bits yet, are there classes as well as
> >library files for that too?
> >
> >--jason
> >
> >On Sun, 15 Apr 2001, Juha Lindfors wrote:
> >
> >>
> >> Wanna take a look at the OpenJMS stuff too? :)
> >>
> >> It takes a meg in our package, and seems unnecessary as we use JBossMQ for
> >> MDB.
> >> The old log4j might be a good candidate for removal as well.
> >>
> >> -- Juha
> >>
> >> At 14:17 14.4.2001 -0700, you wrote:
> >> >DependencyManager and jboss.dependencies have been removed. I also
> >> >updated Main to remove the import of DependencyManager. I verified that
> >> >the system builds correctly and runs with no other modifications too.
> >> >
> >> >--jason
> >> >
> >> >On Sat, 14 Apr 2001, marc fleury wrote:
> >> >
> >> >> |>From my investigation I would say that it is not being used anywhere
> >> >> |inside of the jboss project. If this is true, it might be a good
> >> >> |idea to at
> >> >> |least remove the jboss.dependencies from the conf/default directory so
> >> that
> >> >> |it does not confuse anyone.
> >> >>
> >> >> correct,
> >> >>
> >> >> |I think that the DependencyManager is a good one, so I would not
> >> >> |be so quick
> >> >> |to suggest that it be removed.
> >> >>
> >> >> it was not a good one, remove it, we need to simplify simplify simplify
> >> >>
> >> >> marc
> >> >> |http://lists.sourceforge.net/lists/listinfo/jboss-development
> >> >>
> >> >>
> >> >> ___
> >> >> Jboss-development mailing list
> >> >> [EMAIL PROTECTED]
> >> >> http://lists.sourceforge.net/lists/listinfo/jboss-development
> >> >>
> >> >
> >> >
> >> >___
> >> >Jboss-development mailing list
> >> >[EMAIL PROTECTED]
> >> >http://lists.sourceforge.net/lists/listinfo/jboss-development
> >> >
> >>
> >> ___
> >> Jboss-development mailing list
> >> [EMAIL PROTECTED]
> >> http://l
RE: [JBoss-dev] DependencyManager & jboss.dependencies
Factoring out the openjms stuff from the server to a contrib module seems
like a good idea to me. Ping Peter Antman for comments/help (the email is
at SF) before commiting. Also run mdb tests from test module.
the log4j should be as easy as removing the log4j-old.jar from the cvs,
don't remove any classes, log4j is being used
-- Juha
At 16:31 14.4.2001 -0700, you wrote:
>Ok, it looks like the OpenJMS is only referenced directly in these
>files:
>
> o src/main/org/jboss/jms/asf/OpenJMSServerSessionPoolFactory.java:
>
> import org.exolab.jms.client.OpenJMSServerSessionPool;
> import org.exolab.jms.client.JmsServerSessionPool;
>org.exolab.core.logger.LoggerIfc logger =
> org.exolab.core.logger.LoggerFactory.create(null, null);
>org.exolab.core.logger.LogEventType event =
> org.exolab.core.logger.LogEventType.getLogEventType("debug");
>
> o src/main/org/jboss/jms/jndi/OpenJMSProvider.java:
>
>public static final String INITIAL_CONTEXT_FACTORY =
> "org.exolab.jms.jndi.rmi.RmiJndiInitialContextFactory";
>private static final String HOST_PROP_NAME="org.exolab.jms.jndi.Host";
>private static final String
> PORT_PROP_NAME="org.exolab.jms.jndi.PortNumber";
>
> o src/main/org/jboss/ejb/plugins/jms/JMSContainerInvoker.java:
>
>public String getType() { return "org.exolab.castor.jdo.DataObjects";
>
> //import org.exolab.jms.jndi.JndiConstants;
> import org.exolab.jms.client.JmsServerSessionPool;
>
>---
>
>The last of which imports an OpenJMS class, but does not make use of it.
>Except for JMSContainerInvoker, these classes are not referenced anywhere
>else in the system either.
>
>I can understand wanting to clean up unused sources and thirdparty
>libraries, but I am wondering what if someone wanted to make use of
>OpenJMS? These classes seem like a good candidate for an external plugin
>module, but I am not really sure what the precedent is for that.
>
>It would be nice to have a 'plugin' module, which could some child
>modules, one for 'openjms'. Perhaps that is what the 'contrib' module is
>for?
>
>With the above OpenJMS specific classes removed and these library files:
>
> o src/lib/openjms-client-patched-0.5.1.jar
> o src/lib/openjms-patched-0.5.1.jar
> o src/lib/openjms-pool.jar
> o src/lib/openjms-rmi-patched-0.5.1.jar
>
>I was able to build and execute the default configuration with no errors.
>
>So any ideas on what I should do? Should I proceed and commit these
>changes, thus removing OpenJMS support from JBoss, or should I attempt to
>preserve these classes in an external project for those who still use
>OpenJMS?
>
>I have not investigated the log4j bits yet, are there classes as well as
>library files for that too?
>
>--jason
>
>On Sun, 15 Apr 2001, Juha Lindfors wrote:
>
>>
>> Wanna take a look at the OpenJMS stuff too? :)
>>
>> It takes a meg in our package, and seems unnecessary as we use JBossMQ for
>> MDB.
>> The old log4j might be a good candidate for removal as well.
>>
>> -- Juha
>>
>> At 14:17 14.4.2001 -0700, you wrote:
>> >DependencyManager and jboss.dependencies have been removed. I also
>> >updated Main to remove the import of DependencyManager. I verified that
>> >the system builds correctly and runs with no other modifications too.
>> >
>> >--jason
>> >
>> >On Sat, 14 Apr 2001, marc fleury wrote:
>> >
>> >> |>From my investigation I would say that it is not being used anywhere
>> >> |inside of the jboss project. If this is true, it might be a good
>> >> |idea to at
>> >> |least remove the jboss.dependencies from the conf/default directory so
>> that
>> >> |it does not confuse anyone.
>> >>
>> >> correct,
>> >>
>> >> |I think that the DependencyManager is a good one, so I would not
>> >> |be so quick
>> >> |to suggest that it be removed.
>> >>
>> >> it was not a good one, remove it, we need to simplify simplify simplify
>> >>
>> >> marc
>> >> |http://lists.sourceforge.net/lists/listinfo/jboss-development
>> >>
>> >>
>> >> ___
>> >> Jboss-development mailing list
>> >> [EMAIL PROTECTED]
>> >> http://lists.sourceforge.net/lists/listinfo/jboss-development
>> >>
>> >
>> >
>> >___
>> >Jboss-development mailing list
>> >[EMAIL PROTECTED]
>> >http://lists.sourceforge.net/lists/listinfo/jboss-development
>> >
>>
>> ___
>> Jboss-development mailing list
>> [EMAIL PROTECTED]
>> http://lists.sourceforge.net/lists/listinfo/jboss-development
>>
>
>
>___
>Jboss-development mailing list
>[EMAIL PROTECTED]
>http://lists.sourceforge.net/lists/listinfo/jboss-development
>
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] DependencyManager & jboss.dependencies
Ok, it looks like the OpenJMS is only referenced directly in these
files:
o src/main/org/jboss/jms/asf/OpenJMSServerSessionPoolFactory.java:
import org.exolab.jms.client.OpenJMSServerSessionPool;
import org.exolab.jms.client.JmsServerSessionPool;
org.exolab.core.logger.LoggerIfc logger =
org.exolab.core.logger.LoggerFactory.create(null, null);
org.exolab.core.logger.LogEventType event =
org.exolab.core.logger.LogEventType.getLogEventType("debug");
o src/main/org/jboss/jms/jndi/OpenJMSProvider.java:
public static final String INITIAL_CONTEXT_FACTORY =
"org.exolab.jms.jndi.rmi.RmiJndiInitialContextFactory";
private static final String HOST_PROP_NAME="org.exolab.jms.jndi.Host";
private static final String
PORT_PROP_NAME="org.exolab.jms.jndi.PortNumber";
o src/main/org/jboss/ejb/plugins/jms/JMSContainerInvoker.java:
public String getType() { return "org.exolab.castor.jdo.DataObjects";
//import org.exolab.jms.jndi.JndiConstants;
import org.exolab.jms.client.JmsServerSessionPool;
---
The last of which imports an OpenJMS class, but does not make use of it.
Except for JMSContainerInvoker, these classes are not referenced anywhere
else in the system either.
I can understand wanting to clean up unused sources and thirdparty
libraries, but I am wondering what if someone wanted to make use of
OpenJMS? These classes seem like a good candidate for an external plugin
module, but I am not really sure what the precedent is for that.
It would be nice to have a 'plugin' module, which could some child
modules, one for 'openjms'. Perhaps that is what the 'contrib' module is
for?
With the above OpenJMS specific classes removed and these library files:
o src/lib/openjms-client-patched-0.5.1.jar
o src/lib/openjms-patched-0.5.1.jar
o src/lib/openjms-pool.jar
o src/lib/openjms-rmi-patched-0.5.1.jar
I was able to build and execute the default configuration with no errors.
So any ideas on what I should do? Should I proceed and commit these
changes, thus removing OpenJMS support from JBoss, or should I attempt to
preserve these classes in an external project for those who still use
OpenJMS?
I have not investigated the log4j bits yet, are there classes as well as
library files for that too?
--jason
On Sun, 15 Apr 2001, Juha Lindfors wrote:
>
> Wanna take a look at the OpenJMS stuff too? :)
>
> It takes a meg in our package, and seems unnecessary as we use JBossMQ for
> MDB.
> The old log4j might be a good candidate for removal as well.
>
> -- Juha
>
> At 14:17 14.4.2001 -0700, you wrote:
> >DependencyManager and jboss.dependencies have been removed. I also
> >updated Main to remove the import of DependencyManager. I verified that
> >the system builds correctly and runs with no other modifications too.
> >
> >--jason
> >
> >On Sat, 14 Apr 2001, marc fleury wrote:
> >
> >> |>From my investigation I would say that it is not being used anywhere
> >> |inside of the jboss project. If this is true, it might be a good
> >> |idea to at
> >> |least remove the jboss.dependencies from the conf/default directory so
> that
> >> |it does not confuse anyone.
> >>
> >> correct,
> >>
> >> |I think that the DependencyManager is a good one, so I would not
> >> |be so quick
> >> |to suggest that it be removed.
> >>
> >> it was not a good one, remove it, we need to simplify simplify simplify
> >>
> >> marc
> >> |http://lists.sourceforge.net/lists/listinfo/jboss-development
> >>
> >>
> >> ___
> >> Jboss-development mailing list
> >> [EMAIL PROTECTED]
> >> http://lists.sourceforge.net/lists/listinfo/jboss-development
> >>
> >
> >
> >___
> >Jboss-development mailing list
> >[EMAIL PROTECTED]
> >http://lists.sourceforge.net/lists/listinfo/jboss-development
> >
>
> ___
> Jboss-development mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-development
>
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] RE: Jboss-development digest, Vol 1 #111 - 4 msgs
no answering jboss-user here PLEASE, you just encourage the same behavior over and over, marc ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] RE: Jboss-development digest, Vol 1 #111 - 4 msgs
Add the jta jar file to your classpath. Cheers ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] DependencyManager & jboss.dependencies
Wanna take a look at the OpenJMS stuff too? :) It takes a meg in our package, and seems unnecessary as we use JBossMQ for MDB. The old log4j might be a good candidate for removal as well. -- Juha At 14:17 14.4.2001 -0700, you wrote: >DependencyManager and jboss.dependencies have been removed. I also >updated Main to remove the import of DependencyManager. I verified that >the system builds correctly and runs with no other modifications too. > >--jason > >On Sat, 14 Apr 2001, marc fleury wrote: > >> |>From my investigation I would say that it is not being used anywhere >> |inside of the jboss project. If this is true, it might be a good >> |idea to at >> |least remove the jboss.dependencies from the conf/default directory so that >> |it does not confuse anyone. >> >> correct, >> >> |I think that the DependencyManager is a good one, so I would not >> |be so quick >> |to suggest that it be removed. >> >> it was not a good one, remove it, we need to simplify simplify simplify >> >> marc >> |http://lists.sourceforge.net/lists/listinfo/jboss-development >> >> >> ___ >> Jboss-development mailing list >> [EMAIL PROTECTED] >> http://lists.sourceforge.net/lists/listinfo/jboss-development >> > > >___ >Jboss-development mailing list >[EMAIL PROTECTED] >http://lists.sourceforge.net/lists/listinfo/jboss-development > ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] DependencyManager & jboss.dependencies
DependencyManager and jboss.dependencies have been removed. I also updated Main to remove the import of DependencyManager. I verified that the system builds correctly and runs with no other modifications too. --jason On Sat, 14 Apr 2001, marc fleury wrote: > |>From my investigation I would say that it is not being used anywhere > |inside of the jboss project. If this is true, it might be a good > |idea to at > |least remove the jboss.dependencies from the conf/default directory so that > |it does not confuse anyone. > > correct, > > |I think that the DependencyManager is a good one, so I would not > |be so quick > |to suggest that it be removed. > > it was not a good one, remove it, we need to simplify simplify simplify > > marc > |http://lists.sourceforge.net/lists/listinfo/jboss-development > > > ___ > Jboss-development mailing list > [EMAIL PROTECTED] > http://lists.sourceforge.net/lists/listinfo/jboss-development > ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jboss/src/main/org/jboss/dependencies DependencyManager.java
User: user57 Date: 01/04/14 15:14:14 Removed: src/main/org/jboss/dependencies DependencyManager.java Log: o Removing DependencyManager and jboss.dependencies, since they were not in use by any other part of the system. o Removed import of DependencyManager from Main. ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: newsite/business binary.html
User: juhalindfors Date: 01/04/14 15:17:41 Modified:business binary.html Log: Redirecting downloads to SourceForge. Revision ChangesPath 1.14 +3 -3 newsite/business/binary.html Index: binary.html === RCS file: /cvsroot/jboss/newsite/business/binary.html,v retrieving revision 1.13 retrieving revision 1.14 diff -u -r1.13 -r1.14 --- binary.html 2001/04/13 21:28:10 1.13 +++ binary.html 2001/04/14 22:17:41 1.14 @@ -40,13 +40,13 @@ This is our full suite of Products and it is likely to be all you will need to try out our technology. Download it and find out why many people are switching to jboss every day! Download now: - JBoss-2.2(4.30M) [APR-08-2001] + http://prdownloads.sourceforge.net/jboss/jboss-2.2.zip">JBoss-2.2(4.30M) [APR-08-2001] If you need a servlet container, we package JBoss-2.2 and http://jakarta.apache.org/tomcat" target="_top">Tomcat or http://jetty.mortbay.com/" target="_top">Jetty (no configuration needed!) - JBoss-2.2 + Tomcat-3.2.1 (8.72M) [APR-08-2001] - JBoss-2.2 + Jetty-3.1.RC2 (7.62M) [APR-08-2001] + http://prdownloads.sourceforge.net/jboss/jboss-tomcat-2.2.zip">JBoss-2.2 + Tomcat-3.2.1 (8.72M) [APR-08-2001] + http://prdownloads.sourceforge.net/jboss/jboss_jetty.zip">JBoss-2.2 + Jetty-3.1.RC2 (7.62M) [APR-08-2001] JBoss-2.1 + Tomcat-4.0-b1 (7.52M) [MAR-26-2001] (realm with jboss and web application environment support not implemented) ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jboss/src/main/org/jboss Main.java
User: user57
Date: 01/04/14 15:14:14
Modified:src/main/org/jboss Main.java
Log:
o Removing DependencyManager and jboss.dependencies, since they were not
in use by any other part of the system.
o Removed import of DependencyManager from Main.
Revision ChangesPath
1.32 +1 -2 jboss/src/main/org/jboss/Main.java
Index: Main.java
===
RCS file: /cvsroot/jboss/jboss/src/main/org/jboss/Main.java,v
retrieving revision 1.31
retrieving revision 1.32
diff -u -r1.31 -r1.32
--- Main.java 2001/04/04 20:26:39 1.31
+++ Main.java 2001/04/14 22:14:14 1.32
@@ -24,7 +24,6 @@
import javax.xml.parsers.DocumentBuilderFactory;
-import org.jboss.dependencies.DependencyManager;
import org.jboss.security.SecurityAssociation;
/**
@@ -32,7 +31,7 @@
* @see
* @author Rickard Öberg ([EMAIL PROTECTED])
* @author mailto:[EMAIL PROTECTED]">Daniel O'Connor.
- * @version $Revision: 1.31 $
+ * @version $Revision: 1.32 $
*/
public class Main
{
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jboss/src/etc/conf/default jboss.dependencies
User: user57 Date: 01/04/14 15:14:14 Removed: src/etc/conf/default jboss.dependencies Log: o Removing DependencyManager and jboss.dependencies, since they were not in use by any other part of the system. o Removed import of DependencyManager from Main. ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] The new Service solution
Hey, > 1. Can a service started later, after jboss.jcml is processed.. such as > dynamically through the html interface, or by jetty's service starter > mbean, get registered with the ServiceControl? so as for instance to have > its shutdown managed. (jetty is a bad example, this all started so they > wouldn't get managed) > Not right now, but it would be trivial to add this feature at ConfigurationService. public void registerService(String objectName,String serviceFactory) public void unregisterService(String objectName) > 2. Can a service started through jboss.jcml not register with service > control? I think yes, this is what the new attribute is for. > Actaully it seems no. Service will always have proxy, but methods (start/stop) invoked on proxy will be missed. > 3. What are the advantages of having a 3rd party (ConfigurationService) > register the desire for lifecycle management through a non mbean > notification procedure over having each mbean wanting lifecyle management > try to find a manager through the mbean notification? I would think as > far > as changing code just modifying the ServiceMBeanSupport class to ask for > management would make all existing jboss services work just as they do > now. For notification, you would have to have special Notification event (instead of generic REGISTRATION_NOTIFICATION) published stating that mbean whants to be managed, this could be added to ServiceMBeanSupport. 3party Mbean knows how to publish this notification, and ServiceProxy (as now) facades MBean with incompatible lifecycle interface. That also seems to be a viable solution. Vladimir ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbosstest/src/main/org/jboss/test/cts/test BmpTest.java StatefulSessionTest.java
User: peterbraswell
Date: 01/04/14 06:34:53
Modified:src/main/org/jboss/test/cts/test BmpTest.java
StatefulSessionTest.java
Log:
Modified some failure messages.
Revision ChangesPath
1.2 +2 -4 jbosstest/src/main/org/jboss/test/cts/test/BmpTest.java
Index: BmpTest.java
===
RCS file: /cvsroot/jboss/jbosstest/src/main/org/jboss/test/cts/test/BmpTest.java,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- BmpTest.java 2001/03/06 20:41:06 1.1
+++ BmpTest.java 2001/04/14 13:34:52 1.2
@@ -26,8 +26,8 @@
/**
* Class BmpTest
*
- * @author $Author: osh $
- * @version $Revision: 1.1 $
+ * @author $Author: peterbraswell $
+ * @version $Revision: 1.2 $
*/
public class BmpTest
@@ -218,9 +218,7 @@
} catch(java.rmi.NoSuchObjectException nsoex) {
System.out.println("OK");
} catch(Exception ex) {
- System.err.println("FAILED");
- ex.printStackTrace();
- fail("Got Exception: expecting java.rmi.NoSuchObjectException" );
+ fail("Got Exception: expecting NoSuchObjectException" + ex.toString() );
}
} catch (Exception ex) {
ex.printStackTrace();
1.6 +8 -13
jbosstest/src/main/org/jboss/test/cts/test/StatefulSessionTest.java
Index: StatefulSessionTest.java
===
RCS file:
/cvsroot/jboss/jbosstest/src/main/org/jboss/test/cts/test/StatefulSessionTest.java,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- StatefulSessionTest.java 2001/01/31 20:26:53 1.5
+++ StatefulSessionTest.java 2001/04/14 13:34:52 1.6
@@ -1,7 +1,5 @@
package org.jboss.test.cts.test;
-
-
import java.io.*;
import java.util.*;
import java.lang.reflect.*;
@@ -19,8 +17,8 @@
/**
*
* @see
- * @author $Author: osh $
- * @version $Revision: 1.5 $
+ * @author $Author: peterbraswell $
+ * @version $Revision: 1.6 $
*/
public class StatefulSessionTest
@@ -173,22 +171,23 @@
( StatefulSessionHome ) ctx.lookup("ejbcts/StatefulSessionBean");
sessionBean = home.create();
-
+ System.out.println("OK");
+ System.out.println("Call remove using a primary key");
home.remove(new AccountPK("pk"));
+
}
catch (javax.ejb.RemoveException rmEx)
{
-
+ System.out.println("OK, got a remove exception!" );
// Expected behavior
return;
}
catch (Exception ex)
{
- ex.printStackTrace();
- fail("Expected javax.ejb.RemoveException, got Unknown Exception");
+ fail("[EJB 1.1, p42] Expected 'RemoveException', detail:" + ex.toString());
}
- fail("Expected javax.ejb.RemoveException, got NO exception");
+ fail("Expected 'RemoveException', got NO exception");
System.out.println(
"**");
}
@@ -443,17 +442,14 @@
}
catch (javax.naming.NamingException ne)
{
-ne.printStackTrace();
fail("Naming exception failure");
}
catch (java.rmi.ServerException se)
{
-se.printStackTrace();
fail("Server exception");
}
catch (java.rmi.RemoteException re)
{
-re.printStackTrace();
fail("Remote exception");
}
finally
@@ -467,7 +463,6 @@
}
catch (Exception ex)
{
- ex.printStackTrace();
fail("Caught an unknown exception in testProbeBeanContex");
}
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] JBoss-user questions on JBoss-dev
JBoss-user is overflowing, there is a steady stream of newcomers and new developers that help people but the user base is outpacing the developer base. We are seeing a recrudescence of mails that are purely support questions on this list. I will ask all of you to stand fast and be FIRM in redirecting questions to jboss-user. Please do not answer questions for support on jboss-dev, thanks marc |-Original Message- |From: [EMAIL PROTECTED] |[mailto:[EMAIL PROTECTED]]On Behalf Of Toby |Allsopp |Sent: Saturday, April 14, 2001 7:28 AM |To: [EMAIL PROTECTED] |Subject: Re: [JBoss-dev] RE: Jboss-development digest, Vol 1 #111 - 4 |msgs | | |For God's sake, man, trim your replies! | |Harishankar Nair wrote: | |[37kB of stuff] | | |___ |Jboss-development mailing list |[EMAIL PROTECTED] |http://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] DependencyManager & jboss.dependencies
|>From my investigation I would say that it is not being used anywhere |inside of the jboss project. If this is true, it might be a good |idea to at |least remove the jboss.dependencies from the conf/default directory so that |it does not confuse anyone. correct, |I think that the DependencyManager is a good one, so I would not |be so quick |to suggest that it be removed. it was not a good one, remove it, we need to simplify simplify simplify marc |http://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] RE: Jboss-development digest, Vol 1 #111 - 4 msgs
For God's sake, man, trim your replies! Harishankar Nair wrote: [37kB of stuff] ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Urgent help needed - Class not found exception
Hi Tobias , I again encounter the same error , even after making changes mentioned by you , while testing with the sample bean - InterestClient and Interest bean. Here is the exception I get : C:\jBoss\jbossinterestEjb\interest>java InterestClient Got context Exception in thread "main" java.lang.NoClassDefFoundError: javax/transaction/TransactionManager at java.lang.Class.getMethods0(Native Method) at java.lang.Class.getDeclaredMethods(Class.java:1039) at java.io.ObjectStreamClass.computeSerialVersionUID(ObjectStreamClass.java:873 ) at java.io.ObjectStreamClass.access$200(ObjectStreamClass.java:46) at java.io.ObjectStreamClass$2.run(ObjectStreamClass.java:420) at java.security.AccessController.doPrivileged(Native Method) at java.io.ObjectStreamClass.init(ObjectStreamClass.java:401) at java.io.ObjectStreamClass.lookupInternal(ObjectStreamClass.java:112) at java.io.ObjectStreamClass.lookup(ObjectStreamClass.java:59) at java.io.ObjectStreamClass.lookupInternal(ObjectStreamClass.java:88) at java.io.ObjectStreamClass.lookup(ObjectStreamClass.java:59) at java.io.ObjectStreamClass.lookupInternal(ObjectStreamClass.java:88) at java.io.ObjectStreamClass.setClass(ObjectStreamClass.java:566) at java.io.ObjectInputStream.inputClassDescriptor(ObjectInputStream.java:936) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:366) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236) at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1186) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:386) at java.io.ObjectInputStream.inputClassFields(ObjectInputStream.java:2262) at java.io.ObjectInputStream.defaultReadObject(ObjectInputStream.java:519) at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1411) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:386) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236) at java.rmi.MarshalledObject.get(MarshalledObject.java:138) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:299) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:279) at javax.naming.InitialContext.lookup(InitialContext.java:350) at InterestClient.main(InterestClient.java:44) My classpath is : C:\jBoss\jboss-tomcat-2.2\jboss-2.2\client\jboss-client.jar;C:\jBoss\jboss-t omcat-2.2\jboss-2.2\client\jbosssx-client.jar;C:\jBoss\jboss-tomcat-2.2\jbos s-2.2\client\jnp-client.jar;C:\jBoss\jboss-tomcat-2.2\jboss-2.2\client\deplo y.jar;C:\jBoss\jbossinterestEjb\interest;C:\jdk1.3\bin;C:\jdk1.3\lib\tools.j ar;C:\jdk1.3\jre\lib\rt.jar;C:\jBoss\jbossinterestEjb\interest;. I have now changed my jdk from 1.3.1 to jdk1.3.0 to find a possible solution to the problem. And am using jboss2.2. I tried adding jta-spec1_0_1.jar too in the classpath later - but even that does not help. What more needs to be done to solve this??? Regards Harishankar Nair ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] RE: Jboss-development digest, Vol 1 #111 - 4 msgs
Hello ToBias , I again get the same exception : C:\jBoss\jbossinterestEjb\interest>java InterestClient Got context Exception in thread "main" java.lang.NoClassDefFoundError: javax/transaction/TransactionManager at java.lang.Class.getMethods0(Native Method) at java.lang.Class.getDeclaredMethods(Class.java:1039) at java.io.ObjectStreamClass.computeSerialVersionUID(ObjectStreamClass.java:873 ) at java.io.ObjectStreamClass.access$200(ObjectStreamClass.java:46) at java.io.ObjectStreamClass$2.run(ObjectStreamClass.java:420) at java.security.AccessController.doPrivileged(Native Method) at java.io.ObjectStreamClass.init(ObjectStreamClass.java:401) at java.io.ObjectStreamClass.lookupInternal(ObjectStreamClass.java:112) at java.io.ObjectStreamClass.lookup(ObjectStreamClass.java:59) at java.io.ObjectStreamClass.lookupInternal(ObjectStreamClass.java:88) at java.io.ObjectStreamClass.lookup(ObjectStreamClass.java:59) at java.io.ObjectStreamClass.lookupInternal(ObjectStreamClass.java:88) at java.io.ObjectStreamClass.setClass(ObjectStreamClass.java:566) at java.io.ObjectInputStream.inputClassDescriptor(ObjectInputStream.java:936) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:366) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236) at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1186) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:386) at java.io.ObjectInputStream.inputClassFields(ObjectInputStream.java:2262) at java.io.ObjectInputStream.defaultReadObject(ObjectInputStream.java:519) at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1411) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:386) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236) at java.rmi.MarshalledObject.get(MarshalledObject.java:138) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:299) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:279) at javax.naming.InitialContext.lookup(InitialContext.java:350) at InterestClient.main(InterestClient.java:44) My classpath is : javac -classpath C:\jBoss\jboss-tomcat-2.2\jboss-2.2\client\jboss -client.jar;C:\jBoss\jboss-tomcat-2.2\jboss-2.2\client\jbosssx-client.jar;C: \jBoss\jboss-tomcat-2.2\ jboss-2.2\client\jnp-client.jar;C:\jBoss\jboss-tomcat-2.2\jboss-2.2\client\d eploy.jar;C:\jBoss\jboss interestEjb\interest;C:\jdk1.3\bin;C:\jdk1.3\lib\tools.jar;C:\jdk1.3\jre\lib \rt.jar;C:\jBoss\jbossin terestEjb\interest;. Would like to know what else should be done to solve this problem. Look forward to your help. Regards Harish -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of [EMAIL PROTECTED] Sent: Friday, April 13, 2001 4:06 PM To: [EMAIL PROTECTED] Subject: Jboss-development digest, Vol 1 #111 - 4 msgs Send Jboss-development mailing list submissions to [EMAIL PROTECTED] To subscribe or unsubscribe via the World Wide Web, visit http://lists.sourceforge.net/lists/listinfo/jboss-development or, via email, send a message with subject or body 'help' to [EMAIL PROTECTED] You can reach the person managing the list at [EMAIL PROTECTED] When replying, please edit your Subject line so it is more specific than "Re: Contents of Jboss-development digest..." Today's Topics: 1. [ jboss-Feature Requests-415856 ] SQL persistence for JBossMQ ([EMAIL PROTECTED]) 2. Urgent help needed - Class not found exception (Harishankar Nair) 3. Re: Nested JMX Service Groups...??! (Greg Wilkins) 4. Re: Urgent help needed - Class not found exception (Tobias Frech) --__--__-- Message: 1 To: [EMAIL PROTECTED] From: [EMAIL PROTECTED] Date: Fri, 13 Apr 2001 01:32:09 -0700 Subject: [JBoss-dev] [ jboss-Feature Requests-415856 ] SQL persistence for JBossMQ Reply-To: [EMAIL PROTECTED] Feature Requests item #415856, was updated on 2001-04-13 01:32 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=376688&aid=415856&group_id= 22866 Category: None Group: None Status: Open Priority: 5 Submitted By: Jan B. Krejci (pokqwd) Assigned to: Nobody/Anonymous (nobody) Summary: SQL persistence for JBossMQ Initial Comment: Will MQ store the messages into SQL instead of filesystem in near future? -=jbk=- Jan B. Krejci -- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=376688&aid=415856&group_id= 22866 --__--__-- Message: 2 From: "Harishankar Nair" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Date: Fri, 13 Apr 2001 15:22:56 +0530 Subject: [JBoss-dev] Urgent help needed - Class not found exception Reply-To: [EMAIL PROTECTED] This is a multi-part message in MIME format. --=_NextPart_000_000B_0
[JBoss-dev] [ jboss-Change Notes-416083 ] Patch #415652: Jaws Mapping for SQL2000
Change Notes item #416083, was updated on 2001-04-14 01:45 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=381174&aid=416083&group_id=22866 Category: None Group: v2.4 Status: Open Priority: 5 Submitted By: Juha Lindfors (juhalindfors) Assigned to: Nobody/Anonymous (nobody) Summary: Patch #415652: Jaws Mapping for SQL2000 Initial Comment: http://sourceforge.net/tracker/?func=detail&atid=376687&aid=415652&group_id=22866 -- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=381174&aid=416083&group_id=22866 ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jboss/src/etc/conf/default standardjaws.xml
User: juhalindfors Date: 01/04/14 01:39:45 Modified:src/etc/conf/default standardjaws.xml Log: Jaws DB Mapping for MSSQL2000 (Patch #415652 Submitted by Nobody/Anonymous) Revision ChangesPath 1.15 +94 -0 jboss/src/etc/conf/default/standardjaws.xml Index: standardjaws.xml === RCS file: /cvsroot/jboss/jboss/src/etc/conf/default/standardjaws.xml,v retrieving revision 1.14 retrieving revision 1.15 diff -u -r1.14 -r1.15 --- standardjaws.xml 2001/04/11 12:10:12 1.14 +++ standardjaws.xml 2001/04/14 08:39:44 1.15 @@ -842,6 +842,100 @@ + +MS SQLSERVER2000 + + +java.lang.Integer +INTEGER +INTEGER + + + +java.lang.Character +CHAR +CHAR + + + +java.lang.Short +SMALLINT +SMALLINT + + + +java.lang.Long +BIGINT +BIGINT + + + +java.math.BigDecimal +VARCHAR +VARCHAR(256) + + + +java.lang.String +VARCHAR +VARCHAR(256) + + + +java.lang.Object +JAVA_OBJECT +IMAGE + + + +java.lang.Byte +TINYINT +TINYINT + + + +java.sql.Timestamp +TIMESTAMP +TIMESTAMP + + + +java.sql.Date +DATE +DATETIME + + + +java.sql.Time +TIME +DATETIME + + + +java.util.Date +DATE +DATETIME + + + +java.lang.Boolean +BIT +BIT + + + +java.lang.Float +REAL +REAL + + + +java.lang.Double +DOUBLE +FLOAT + + + DB2/400 ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
