[JBoss-dev] CVS update: jmx/src/main/test/compliance/loading MLetTEST.java
User: juhalindfors
Date: 02/03/17 02:17:47
Modified:src/main/test/compliance/loading MLetTEST.java
Log:
Revision ChangesPath
1.6 +27 -38jmx/src/main/test/compliance/loading/MLetTEST.java
Index: MLetTEST.java
===
RCS file: /cvsroot/jboss/jmx/src/main/test/compliance/loading/MLetTEST.java,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- MLetTEST.java 14 Mar 2002 18:14:45 - 1.5
+++ MLetTEST.java 17 Mar 2002 10:17:47 - 1.6
@@ -249,54 +249,43 @@
}
}
- public void testArchiveListInMLet()
+ public void testArchiveListInMLet() throws Exception
{
// NOTE:
// the urls used here are relative to the location of the build.xml
final String MLET_URL =
file:./output/etc/test/compliance/loading/ArchiveList.mlet;
+
+ MBeanServer server = MBeanServerFactory.createMBeanServer();
+ MLet mlet = new MLet();
+ ObjectName name = new ObjectName(test:name=mlet);
+ server.registerMBean(mlet, name);
- try
- {
- MBeanServer server = MBeanServerFactory.createMBeanServer();
- MLet mlet = new MLet();
- ObjectName name = new ObjectName(test:name=mlet);
- server.registerMBean(mlet, name);
-
- server.invoke(name, getMBeansFromURL,
- new Object[] { MLET_URL },
- new String[] { String.class.getName() }
- );
-
- Class c = null;
-
- try
- {
-c = mlet.loadClass(test.compliance.loading.support.AClass);
- }
- catch (ClassNotFoundException e)
- {
-URL[] urls = mlet.getURLs();
-fail(FAILS IN RI: SUN JMX RI builds a malformed URL from an MLet text
file URL ' +
- MLET_URL + ' resulting into MLET codebase URL ' + urls[0] + '
and therefore fails +
- to load the required classes from the Java archive.);
- }
-
- Object o = c.newInstance();
-
- server.setAttribute(new ObjectName(test:name=AnotherTrivial), new
Attribute(Something, o));
- o = server.getAttribute(new ObjectName(test:name=AnotherTrivial),
Something);
-
- assertTrue(o.getClass().isAssignableFrom(c));
- }
- catch (AssertionFailedError e)
+ server.invoke(name, getMBeansFromURL,
+ new Object[] { MLET_URL },
+ new String[] { String.class.getName() }
+ );
+
+ Class c = null;
+
+ try
{
- throw e;
+ c = mlet.loadClass(test.compliance.loading.support.AClass);
}
- catch (Throwable t)
+ catch (ClassNotFoundException e)
{
- fail(Unexpected error: + t.toString());
+ URL[] urls = mlet.getURLs();
+ fail(FAILS IN RI: SUN JMX RI builds a malformed URL from an MLet text
file URL ' +
+ MLET_URL + ' resulting into MLET codebase URL ' + urls[0] + ' and
therefore fails +
+ to load the required classes from the Java archive.);
}
+
+ Object o = c.newInstance();
+
+ server.setAttribute(new ObjectName(test:name=AnotherTrivial), new
Attribute(Something, o));
+ o = server.getAttribute(new ObjectName(test:name=AnotherTrivial),
Something);
+
+ assertTrue(o.getClass().isAssignableFrom(c));
}
public void testUnexpectedEndOfFile()
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jmx/src/main/test/implementation/loading LoaderRepositoryTEST.java
User: juhalindfors
Date: 02/03/17 02:19:24
Modified:src/main/test/implementation/loading
LoaderRepositoryTEST.java
Log:
Revision ChangesPath
1.3 +5 -3
jmx/src/main/test/implementation/loading/LoaderRepositoryTEST.java
Index: LoaderRepositoryTEST.java
===
RCS file:
/cvsroot/jboss/jmx/src/main/test/implementation/loading/LoaderRepositoryTEST.java,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- LoaderRepositoryTEST.java 14 Mar 2002 18:09:09 - 1.2
+++ LoaderRepositoryTEST.java 17 Mar 2002 10:19:24 - 1.3
@@ -25,8 +25,9 @@
import javax.management.loading.DefaultLoaderRepository;
import org.jboss.mx.util.AgentID;
+import org.jboss.mx.server.ServerConstants;
-public class LoaderRepositoryTEST extends TestCase
+public class LoaderRepositoryTEST extends TestCase implements ServerConstants
{
public LoaderRepositoryTEST(String s)
{
@@ -86,7 +87,7 @@
new String[] { String.class.getName() }
);
- fail(Expected to fail due to two different mlet loaders having a class
mismatch.);
+ //fail(Expected to fail due to two different mlet loaders having a class
mismatch.);
}
catch (MBeanException e)
{
@@ -94,9 +95,10 @@
{
// expected, argument type mismatch error since the arg of type AClass
is
// loaded by diff mlet loader than the target MBean with AClass in its
sign.
+e.printStackTrace();
}
else throw e;
}
}
-
+
}
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jmx/src/main/org/jboss/mx/server ServerConstants.java
User: juhalindfors Date: 02/03/17 02:22:50 Modified:src/main/org/jboss/mx/server ServerConstants.java Log: Revision ChangesPath 1.7 +5 -3 jmx/src/main/org/jboss/mx/server/ServerConstants.java Index: ServerConstants.java === RCS file: /cvsroot/jboss/jmx/src/main/org/jboss/mx/server/ServerConstants.java,v retrieving revision 1.6 retrieving revision 1.7 diff -u -r1.6 -r1.7 --- ServerConstants.java 1 Mar 2002 19:25:57 - 1.6 +++ ServerConstants.java 17 Mar 2002 10:22:50 - 1.7 @@ -18,7 +18,7 @@ * * @author a href=mailto:[EMAIL PROTECTED];Juha Lindfors/a. * @author a href=mailto:[EMAIL PROTECTED];Adrian Brock/a. - * @version $Revision: 1.6 $ + * @version $Revision: 1.7 $ * */ public interface ServerConstants @@ -86,9 +86,11 @@ final static String LOADER_REPOSITORY_CLASS_PROPERTY = jbossmx.loader.repository.class; final static String DEFAULT_LOADER_REPOSITORY_CLASS= org.jboss.mx.loading.BasicLoaderRepository; + //final static String DEFAULT_LOADER_REPOSITORY_CLASS= org.jboss.mx.loading.UnifiedLoaderRepository; + final static String UNIFIED_LOADER_REPOSITORY_CLASS= org.jboss.mx.loading.UnifiedLoaderRepository; - final static String MBEAN_REGISTRY_CLASS_PROPERTY= jbossmx.mbean.registry.class; - final static String DEFAULT_MBEAN_REGISTRY_CLASS = org.jboss.mx.server.registry.BasicMBeanRegistry; + final static String MBEAN_REGISTRY_CLASS_PROPERTY = jbossmx.mbean.registry.class; + final static String DEFAULT_MBEAN_REGISTRY_CLASS = org.jboss.mx.server.registry.BasicMBeanRegistry; final static String MBEAN_SERVER_CLASS_PROPERTY= jbossmx.mbean.server.class; final static String DEFAULT_MBEAN_SERVER_CLASS = org.jboss.mx.server.MBeanServerImpl; ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jmx/src/main/org/jboss/mx/loading UnifiedClassLoader.java UnifiedLoaderRepository.java
User: juhalindfors
Date: 02/03/17 02:30:31
Added: src/main/org/jboss/mx/loading UnifiedClassLoader.java
UnifiedLoaderRepository.java
Log:
Unified class loader integration. Maybe still a bit flaky, but can handle
at least the basic test -- two MLet loaders loading the same class definition
only once and avoid a conflicting class definition.
Revision ChangesPath
1.1 jmx/src/main/org/jboss/mx/loading/UnifiedClassLoader.java
Index: UnifiedClassLoader.java
===
/***
* *
* JBoss: The OpenSource J2EE WebOS *
* *
* Distributable under LGPL license. *
* See terms of license at gnu.org. *
* *
***/
package org.jboss.mx.loading;
import java.net.URL;
import java.net.URLClassLoader;
import java.io.InputStream;
import java.util.Map;
import EDU.oswego.cs.dl.util.concurrent.ConcurrentReaderHashMap;
/**
* A ClassLoader which loads classes from a single URL in conjunction with
* the {@link UnifiedLoaderRepository}. Notice that this classloader does
* not work independently without the repository. A repository reference
* must be provided via the constructor or the classloader must be explicitly
* registered to the repository before any attempt to load a class.
*
* @author a href=[EMAIL PROTECTED]Marc Fleury/a
* @author a href=[EMAIL PROTECTED]Christoph G. Jung/a
* @author a href=[EMAIL PROTECTED]Scott Stark/a
* @author a href=[EMAIL PROTECTED]Juha Lindfors/a
* @version tt$Revision: 1.1 $/tt
*
* pb20010830 marc fleury:/b
* ul
* liInitial import
* /ul
*
* pb20011009 cgj:/b
* ul
* lifixed default resolution behaviour
* /ul
*
* pb20020315 Juha Lindfors:/b
* ul
* li Support for adding your own class definitions instead of just an URL./li
*
* li Removed static reference to repository. This is now set as the classloader
* is registered to the repository via setRepository() call.
* /li
*/
public class UnifiedClassLoader
extends URLClassLoader
{
// Attributes
/** Reference to the unified repository. */
private UnifiedLoaderRepository repository = null;
/** One URL per ClassLoader in our case */
private URL url = null;
/** Class definitions */
private Map classes = new ConcurrentReaderHashMap();
// Constructors --
/**
* Construct a ttUnifiedClassLoader/tt without registering it to the
* classloader repository.
*
* @param url the single URL to load classes from.
*/
public UnifiedClassLoader(URL url)
{
super(new URL[] {url}, UnifiedClassLoader.class.getClassLoader());
// FIXME: log it
System.out.println(New UCL with url + url);
this.url = url;
}
/**
* Construct a ttUnifiedClassLoader/tt and registers it to the given
* repository.
*
* @param url The single URL to load classes from.
* @param repository the repository this classloader delegates to
*/
public UnifiedClassLoader(URL url, UnifiedLoaderRepository repository)
{
this(url);
// set the repository reference
this.repository = repository;
// register this loader to the given repository
repository.addClassLoader(this);
}
/**
* Constructs a ttUnifiedClassLoader/tt with given class definition.
*
* @param names class name
* @param codes class definition
*/
public UnifiedClassLoader(String name, byte[] code)
{
// FIXME: UCL cloader or ctx cl as parent??
super(new URL[] {}, UnifiedClassLoader.class.getClassLoader());
addClass(name, code);
}
// Public
public void addClass(String name, byte[] code)
{
classes.put(name, code);
}
public void setRepository(UnifiedLoaderRepository repository)
{
this.repository = repository;
}
/**
*/
public Class loadClassLocally(String name, boolean resolve)
throws ClassNotFoundException
{
// check our own class definitions foist, then delegate to parent
Object o = classes.get(name);
if (o != null)
{
byte[] code = (byte[])o;
return defineClass(name, code, 0, code.length);
}
else
{
return super.loadClass(name, resolve);
}
}
/**
[JBoss-dev] CVS update: jmx/src/main/org/jboss/mx/loading LoaderRepository.java
User: juhalindfors
Date: 02/03/17 02:26:14
Modified:src/main/org/jboss/mx/loading LoaderRepository.java
Log:
always set the class name of the loader repository in system properties
Revision ChangesPath
1.3 +11 -5 jmx/src/main/org/jboss/mx/loading/LoaderRepository.java
Index: LoaderRepository.java
===
RCS file: /cvsroot/jboss/jmx/src/main/org/jboss/mx/loading/LoaderRepository.java,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- LoaderRepository.java 28 Jan 2002 23:53:36 - 1.2
+++ LoaderRepository.java 17 Mar 2002 10:26:14 - 1.3
@@ -17,7 +17,7 @@
* @see org.jboss.mx.loading.BasicLoaderRepository
*
* @author a href=mailto:[EMAIL PROTECTED];Juha Lindfors/a.
- * @version $Revision: 1.2 $
+ * @version $Revision: 1.3 $
*/
public abstract class LoaderRepository
implements ServerConstants
@@ -61,12 +61,14 @@
public synchronized static LoaderRepository getDefaultLoaderRepository()
{
- ClassLoader cl = Thread.currentThread().getContextClassLoader();
- String className = System.getProperty(LOADER_REPOSITORY_CLASS_PROPERTY,
DEFAULT_LOADER_REPOSITORY_CLASS);
-
+
if (instance != null)
return instance;
+ ClassLoader cl = Thread.currentThread().getContextClassLoader();
+ String className = System.getProperty(LOADER_REPOSITORY_CLASS_PROPERTY,
DEFAULT_LOADER_REPOSITORY_CLASS);
+ System.setProperty(LOADER_REPOSITORY_CLASS_PROPERTY, className);
+
try
{
Class repository = cl.loadClass(className);
@@ -88,13 +90,17 @@
}
}
+ // Public
public Vector getLoaders()
{
return loaders;
}
- // Public
public abstract Class loadClass(String className) throws ClassNotFoundException;
+// {
+// return loadClassWithout(null, className);
+// }
+
public abstract Class loadClassWithout(ClassLoader loader, String className)
throws ClassNotFoundException;
public abstract void addClassLoader(ClassLoader cl);
public abstract void removeClassLoader(ClassLoader cl);
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jmx/src/main/org/jboss/mx/capability OptimizedMBeanDispatcher.java
User: juhalindfors
Date: 02/03/17 02:33:22
Modified:src/main/org/jboss/mx/capability
OptimizedMBeanDispatcher.java
Log:
if ULR is used, create a UCL and directly feed it the bytecodes that define
the generated class
Revision ChangesPath
1.4 +16 -8
jmx/src/main/org/jboss/mx/capability/OptimizedMBeanDispatcher.java
Index: OptimizedMBeanDispatcher.java
===
RCS file:
/cvsroot/jboss/jmx/src/main/org/jboss/mx/capability/OptimizedMBeanDispatcher.java,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- OptimizedMBeanDispatcher.java 8 Mar 2002 00:41:36 - 1.3
+++ OptimizedMBeanDispatcher.java 17 Mar 2002 10:33:22 - 1.4
@@ -74,6 +74,9 @@
import org.apache.bcel.classfile.JavaClass;
import org.jboss.mx.loading.LoaderRepository;
+import org.jboss.mx.loading.UnifiedClassLoader;
+
+import org.jboss.mx.server.ServerConstants;
import org.jboss.mx.metadata.AttributeOperationResolver;
@@ -91,10 +94,10 @@
* @see org.jboss.mx.capability.DispatchClassLoader
*
* @author a href=mailto:[EMAIL PROTECTED];Juha Lindfors/a.
- * @version $Revision: 1.3 $
+ * @version $Revision: 1.4 $
*
*/
-public class OptimizedMBeanDispatcher
+public class OptimizedMBeanDispatcher implements ServerConstants
{
// Constants -
final static Class SUPER_CLASS = ReflectedMBeanDispatcher.class;
@@ -125,12 +128,17 @@
BufferedOutputStream bos = new BufferedOutputStream(baos);
c.dump(bos);
- LoaderRepository rep = LoaderRepository.getDefaultLoaderRepository();
-
- // FIXME: what about ctx cl?
- // FIXME: also I dont know if the parent is right here, have to check later
- DispatchClassLoader dcl = new
DispatchClassLoader(resource.getClass().getClassLoader(), className,
baos.toByteArray());
- rep.addClassLoader(dcl);
+ ClassLoader ocl;
+
+ if
(System.getProperty(ServerConstants.LOADER_REPOSITORY_CLASS_PROPERTY).equals(
+ ServerConstants.UNIFIED_LOADER_REPOSITORY_CLASS))
+ocl = new UnifiedClassLoader(className, baos.toByteArray());
+ else
+// FIXME: what about ctx cl?
+// FIXME: also I dont know if the parent is right here, have to check
later
+ocl = new DispatchClassLoader(resource.getClass().getClassLoader(),
className, baos.toByteArray());
+
+ LoaderRepository.getDefaultLoaderRepository().addClassLoader(ocl);
// FIXME: throw the DLC away when an MBean is unregistered!
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jmx/src/main/javax/management/loading MLet.java
User: juhalindfors
Date: 02/03/17 02:35:55
Modified:src/main/javax/management/loading MLet.java
Log:
unified classloader support
Revision ChangesPath
1.8 +73 -4 jmx/src/main/javax/management/loading/MLet.java
Index: MLet.java
===
RCS file: /cvsroot/jboss/jmx/src/main/javax/management/loading/MLet.java,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- MLet.java 13 Mar 2002 14:44:53 - 1.7
+++ MLet.java 17 Mar 2002 10:35:55 - 1.8
@@ -32,6 +32,11 @@
import org.jboss.mx.loading.MBeanFileParser;
import org.jboss.mx.loading.MLetParser;
import org.jboss.mx.loading.MBeanElement;
+import org.jboss.mx.loading.LoaderRepository;
+import org.jboss.mx.loading.UnifiedClassLoader;
+import org.jboss.mx.loading.UnifiedLoaderRepository;
+
+import org.jboss.mx.server.ServerConstants;
/**
* URL classloader capable of parsing an MLet text file adhering to the file
@@ -40,7 +45,7 @@
* @see javax.management.loading.MLetMBean
*
* @author a href=mailto:[EMAIL PROTECTED];Juha Lindfors/a.
- * @version $Revision: 1.7 $
+ * @version $Revision: 1.8 $
*
* pbRevisions:/b
*
@@ -48,14 +53,34 @@
* ul
* li Added MLet text file ARG tag support /li
* /ul
+ *
+ * pb20020317 Juha Lindfors:/b
+ * ul
+ * li Unified Loader Repository support /li
+ *
+ * li We need to intercept addURL() call since MLet CL exposes this as a
+ * public method (unlike URL CL). This means the set of URLs in this
+ * classloaders scope may change after it has been registered to the
+ * repository. /li
+ *
+ * li We override loadClass() to delegate class loading directly to the
+ * repository in case a Unified Loader Repository is installed. This means
+ * in case of ULR this classloader is never used to load classes. The ULR
+ * has a set of Unified CLs that match the URLs added to this CL. /li
+ * /ul
*/
public class MLet
extends URLClassLoader
implements MLetMBean, MBeanRegistration
{
- // FIXME: (RI javadoc) Note - The MLet class loader uses the
DefaultLoaderRepository to load classes that could not be found in the loaded jar
files.
+ // FIXME: (RI javadoc) Note - The MLet class loader uses the
DefaultLoaderRepository
+ //to load classes that could not be found in the loaded jar files.
+ //
+ // IOW we need to override findClass for this cl...
+ // I think we can avoid the ugly dlr field hack from RI
+
// Attributes
/** Reference to the MBean server this loader is registered to. */
private MBeanServer server= null;
@@ -162,6 +187,12 @@
try
{
+ // FIXME: see the note at the beginning... we use an explicit loader
+ //in the createMBean() call to force this classloader to
+ //be used first to load all MLet classes. Normally this form
+ //of createMBean() call will not delegate to DLR even though
+ //the javadoc requires it. Therefore the findClass() should
+ //be overridden to delegate to the repository.
mbeans.add(server.createMBean(
element.getCode(),
(element.getName() != null) ? new
ObjectName(element.getName()) : null,
@@ -190,14 +221,28 @@
public void addURL(URL url)
{
- super.addURL(url);
+ if
(System.getProperty(ServerConstants.LOADER_REPOSITORY_CLASS_PROPERTY).equals(
+ServerConstants.UNIFIED_LOADER_REPOSITORY_CLASS))
+ {
+ // since we don't have the URLs til getMBeansFromURL() is called we
+ // need to add these UCLs late, after the MBean registration
+ LoaderRepository.getDefaultLoaderRepository().addClassLoader(new
UnifiedClassLoader(url));
+ }
+
+ else
+ {
+ // will probably override to add individual URL CL to repository as well
+ // in the same style as with ULR. This would allow findClass() to safely
+ // delegate to the BLR without having to deal with infinite looping.
+ super.addURL(url);
+ }
}
public void addURL(String url) throws ServiceNotFoundException
{
try
{
- super.addURL(new URL(url));
+ this.addURL(new URL(url));
}
catch (MalformedURLException e)
{
@@ -207,13 +252,37 @@
public String getLibraryDirectory()
{
+ // FIXME
throw new Error(NYI);
}
public void setLibraryDirectory(String libdir)
{
+ // FIXME
throw new Error(NYI);
}
[JBoss-dev] [ jboss-Bugs-530925 ] Fields cut off at 2^16 bytes
Bugs item #530925, was opened at 2002-03-17 12:14 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=530925group_id=22866 Category: JBossCMP Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 5 Submitted By: Eric Jain (ejain) Assigned to: Nobody/Anonymous (nobody) Summary: Fields cut off at 2^16 bytes Initial Comment: Only 2^16 bytes for each serializable object within a CMP entity bean are written to the database. This behavior was observed with MySQL and Oracle. -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=530925group_id=22866 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-530925 ] Fields cut off at 2^16 bytes
Bugs item #530925, was opened at 2002-03-17 12:14 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=530925group_id=22866 Category: JBossCMP Group: v3.0 Rabbit Hole Status: Closed Resolution: Invalid Priority: 5 Submitted By: Eric Jain (ejain) Assigned to: Nobody/Anonymous (nobody) Summary: Fields cut off at 2^16 bytes Initial Comment: Only 2^16 bytes for each serializable object within a CMP entity bean are written to the database. This behavior was observed with MySQL and Oracle. -- Comment By: Eric Jain (ejain) Date: 2002-03-17 12:41 Message: Logged In: YES user_id=474829 Fixed by changing BLOB to LONGBLOB in the mySQL type- mapping in standardjbosscmp-jdbc.xml. Perhaps it would be a good idea to make this the default? -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=530925group_id=22866 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Change Notes-530933 ] Unified classloaders integrated.
Change Notes item #530933, was opened at 2002-03-17 14:33 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=381174aid=530933group_id=22866 Category: JBossMX Group: None Status: Open Priority: 5 Submitted By: Juha Lindfors (juhalindfors) Assigned to: Juha Lindfors (juhalindfors) Summary: Unified classloaders integrated. Initial Comment: Unified classloaders integrated to the JMX base via UnifiedLoaderRepository. ULR extends LoaderRepository and can be installed as an implementation of the DefaultLoaderRepository. Both MLet classloader and Dispatcher classloader modified to work with ULR. Code integrated as part of the 1.1 development branch. -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=381174aid=530933group_id=22866 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbosstest/src/resources/naming/ear - New directory
User: ejort Date: 02/03/17 04:43:59 jbosstest/src/resources/naming/ear - New directory ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbosstest/src/resources/naming/jar/META-INF - New directory
User: ejort Date: 02/03/17 04:44:24 jbosstest/src/resources/naming/jar/META-INF - New directory ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbosstest/src/resources/naming/jar - New directory
User: ejort Date: 02/03/17 04:44:00 jbosstest/src/resources/naming/jar - New directory ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbosstest/src/resources/naming/ear/b/META-INF - New directory
User: ejort Date: 02/03/17 04:45:54 jbosstest/src/resources/naming/ear/b/META-INF - New directory ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbosstest/src/resources/naming/ear/META-INF - New directory
User: ejort Date: 02/03/17 04:44:56 jbosstest/src/resources/naming/ear/META-INF - New directory ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbosstest/src/resources/naming/ear/b - New directory
User: ejort Date: 02/03/17 04:44:57 jbosstest/src/resources/naming/ear/b - New directory ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbosstest/src/resources/naming/ear/a/META-INF - New directory
User: ejort Date: 02/03/17 04:45:21 jbosstest/src/resources/naming/ear/a/META-INF - New directory ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbosstest/src/resources/naming/ear/a - New directory
User: ejort Date: 02/03/17 04:44:56 jbosstest/src/resources/naming/ear/a - New directory ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbosstest/src/main/org/jboss/test/naming/interfaces TestEjbLink.java TestEjbLinkHome.java
User: ejort
Date: 02/03/17 04:56:29
Added: src/main/org/jboss/test/naming/interfaces TestEjbLink.java
TestEjbLinkHome.java
Log:
ejb-link test for an ear
Revision ChangesPath
1.1
jbosstest/src/main/org/jboss/test/naming/interfaces/TestEjbLink.java
Index: TestEjbLink.java
===
package org.jboss.test.naming.interfaces;
import java.rmi.RemoteException;
import javax.ejb.EJBObject;
/**
@author a href=mailto:[EMAIL PROTECTED];Adrian.Brock/a
@version $Revision: 1.1 $
*/
public interface TestEjbLink extends EJBObject
{
/**
* Call a bean with the passed jndi name bound using ejb-link
* @param jndiName the name of the bean specified in ejb-ref
* @return the result of the call or Failed on an error
*/
public String testEjbLinkCaller(String jndiName)
throws RemoteException;
/**
* Called by a bean specified in ejb-link
* @return the string Works
*/
public String testEjbLinkCalled()
throws RemoteException;
}
1.1
jbosstest/src/main/org/jboss/test/naming/interfaces/TestEjbLinkHome.java
Index: TestEjbLinkHome.java
===
package org.jboss.test.naming.interfaces;
import java.rmi.RemoteException;
import javax.ejb.CreateException;
import javax.ejb.EJBHome;
/**
@author a href=mailto:[EMAIL PROTECTED]Adrian Brock/a
@version $Revision: 1.1 $
*/
public interface TestEjbLinkHome extends EJBHome
{
public TestEjbLink create() throws CreateException, RemoteException;
}
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbosstest/src/main/org/jboss/test/naming/test EjbLinkUnitTestCase.java
User: ejort
Date: 02/03/17 04:56:29
Added: src/main/org/jboss/test/naming/test EjbLinkUnitTestCase.java
Log:
ejb-link test for an ear
Revision ChangesPath
1.1
jbosstest/src/main/org/jboss/test/naming/test/EjbLinkUnitTestCase.java
Index: EjbLinkUnitTestCase.java
===
/*
* JBoss, the OpenSource J2EE webOS
*
* Distributable under LGPL license.
* See terms of license at gnu.org.
*/
package org.jboss.test.naming.test;
import javax.naming.InitialContext;
import javax.rmi.PortableRemoteObject;
import junit.framework.Test;
import junit.framework.TestCase;
import junit.framework.TestSuite;
import org.jboss.test.JBossTestCase;
import org.jboss.test.naming.interfaces.TestEjbLinkHome;
import org.jboss.test.naming.interfaces.TestEjbLink;
/**
* Tests of EjbLink.
*
* @author a href=mailto:[EMAIL PROTECTED];Adrian Brock/a
*/
public class EjbLinkUnitTestCase extends JBossTestCase
{
/**
* Constructor for the test
*
* @param name Testcase name
*/
public EjbLinkUnitTestCase(String name)
{
super(name);
}
/**
* Test an ejblink
*
* @exception Exception Description of Exception
*/
public void testEjbLinkNamed() throws Exception
{
Object obj = getInitialContext().lookup(naming/SessionB);
obj = PortableRemoteObject.narrow(obj, TestEjbLinkHome.class);
TestEjbLinkHome home = (TestEjbLinkHome)obj;
getLog().debug(Found naming/SessionB);
TestEjbLink bean = home.create();
getLog().debug(Created the bean);
assertEquals(Works, bean.testEjbLinkCaller(java:comp/env/ejb/SessionA));
getLog().debug(Test succeeded);
bean.remove();
}
public static Test suite() throws Exception
{
return getDeploySetup(EjbLinkUnitTestCase.class, naming.ear);
}
}
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbosstest build.xml
User: ejort
Date: 02/03/17 04:56:29
Modified:.build.xml
Log:
ejb-link test for an ear
Revision ChangesPath
1.94 +38 -3 jbosstest/build.xml
Index: build.xml
===
RCS file: /cvsroot/jboss/jbosstest/build.xml,v
retrieving revision 1.93
retrieving revision 1.94
diff -u -r1.93 -r1.94
--- build.xml 15 Mar 2002 22:36:28 - 1.93
+++ build.xml 17 Mar 2002 12:56:27 - 1.94
@@ -28,7 +28,7 @@
!--tests-jmxri-compliance still needs to run over jmxri.jar --
!--the aim of that test is to check our compliance suite. --
-!-- $Id: build.xml,v 1.93 2002/03/15 22:36:28 reverbel Exp $ --
+!-- $Id: build.xml,v 1.94 2002/03/17 12:56:27 ejort Exp $ --
project default=main name=JBoss/Testsuite
@@ -1378,8 +1378,8 @@
include name=org/jboss/test/naming/ejb/**/
include name=org/jboss/test/naming/interfaces/**/
/fileset
- fileset dir=${build.resources}/naming
-include name=**/*.xml/
+ fileset dir=${build.resources}/naming/jar
+include name=META-INF/*.xml/
/fileset
/jar
@@ -1392,6 +1392,41 @@
/fileset
fileset dir=${build.resources}/remote-naming
include name=**/*.xml/
+ /fileset
+/jar
+
+!-- build naminga.jar --
+jar jarfile=${build.lib}/naminga.jar
+ fileset dir=${build.classes}
+patternset refid=common.test.application.classes/
+include name=org/jboss/test/naming/ejb/**/
+include name=org/jboss/test/naming/interfaces/**/
+ /fileset
+ fileset dir=${build.resources}/naming/ear/a
+include name=META-INF/*.xml/
+ /fileset
+/jar
+
+!-- build namingb.jar --
+jar jarfile=${build.lib}/namingb.jar
+ fileset dir=${build.classes}
+patternset refid=common.test.application.classes/
+include name=org/jboss/test/naming/ejb/**/
+include name=org/jboss/test/naming/interfaces/**/
+ /fileset
+ fileset dir=${build.resources}/naming/ear/b
+include name=META-INF/*.xml/
+ /fileset
+/jar
+
+!-- build naming.ear --
+jar jarfile=${build.lib}/naming.ear
+ fileset dir=${build.lib}
+include name=naminga.jar/
+include name=namingb.jar/
+ /fileset
+ fileset dir=${build.resources}/naming/ear
+include name=META-INF/*.xml/
/fileset
/jar
/target
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbosstest/src/resources/naming/ear/b/META-INF ejb-jar.xml jboss.xml
User: ejort Date: 02/03/17 04:56:30 Added: src/resources/naming/ear/b/META-INF ejb-jar.xml jboss.xml Log: ejb-link test for an ear Revision ChangesPath 1.1 jbosstest/src/resources/naming/ear/b/META-INF/ejb-jar.xml Index: ejb-jar.xml === ?xml version=1.0 encoding=ISO-8859-1 standalone=yes? ejb-jar descriptionTest ENC/description enterprise-beans session descriptionSession Bean/description ejb-nameSessionB/ejb-name homeorg.jboss.test.naming.interfaces.TestEjbLinkHome/home remoteorg.jboss.test.naming.interfaces.TestEjbLink/remote ejb-classorg.jboss.test.naming.ejb.TestEjbLinkBean/ejb-class session-typeStateless/session-type transaction-typeContainer/transaction-type ejb-ref ejb-ref-nameejb/SessionA/ejb-ref-name ejb-ref-typeSession/ejb-ref-type homeorg.jboss.test.naming.interfaces.TestEjbLinkHome/home remoteorg.jboss.test.naming.interfaces.TestEjbLink/remote ejb-linkSessionA/ejb-link /ejb-ref /session /enterprise-beans /ejb-jar 1.1 jbosstest/src/resources/naming/ear/b/META-INF/jboss.xml Index: jboss.xml === ?xml version=1.0 encoding=UTF-8? jboss enterprise-beans session ejb-nameSessionB/ejb-name jndi-namenaming/SessionB/jndi-name /session /enterprise-beans /jboss ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbosstest/src/resources/naming/ear/META-INF application.xml
User: ejort Date: 02/03/17 04:56:29 Added: src/resources/naming/ear/META-INF application.xml Log: ejb-link test for an ear Revision ChangesPath 1.1 jbosstest/src/resources/naming/ear/META-INF/application.xml Index: application.xml === ?xml version=1.0 encoding=ISO-8859-1? application display-namenaming ear test/display-name module ejbnaminga.jar/ejb /module module ejbnamingb.jar/ejb /module /application ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbosstest/src/resources/naming/META-INF ejb-jar.xml jboss.xml
User: ejort Date: 02/03/17 04:56:29 Removed: src/resources/naming/META-INF ejb-jar.xml jboss.xml Log: ejb-link test for an ear ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbosstest/src/resources/naming/ear/a/META-INF ejb-jar.xml jboss.xml
User: ejort Date: 02/03/17 04:56:30 Added: src/resources/naming/ear/a/META-INF ejb-jar.xml jboss.xml Log: ejb-link test for an ear Revision ChangesPath 1.1 jbosstest/src/resources/naming/ear/a/META-INF/ejb-jar.xml Index: ejb-jar.xml === ?xml version=1.0 encoding=ISO-8859-1 standalone=yes? ejb-jar descriptionTest ENC/description enterprise-beans session descriptionSession Bean/description ejb-nameSessionA/ejb-name homeorg.jboss.test.naming.interfaces.TestEjbLinkHome/home remoteorg.jboss.test.naming.interfaces.TestEjbLink/remote ejb-classorg.jboss.test.naming.ejb.TestEjbLinkBean/ejb-class session-typeStateless/session-type transaction-typeContainer/transaction-type /session /enterprise-beans /ejb-jar 1.1 jbosstest/src/resources/naming/ear/a/META-INF/jboss.xml Index: jboss.xml === ?xml version=1.0 encoding=UTF-8? jboss enterprise-beans session ejb-nameSessionA/ejb-name jndi-namenaming/SessionA/jndi-name /session /enterprise-beans /jboss ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbosstest/src/main/org/jboss/test/naming/ejb TestEjbLinkBean.java
User: ejort
Date: 02/03/17 04:56:29
Added: src/main/org/jboss/test/naming/ejb TestEjbLinkBean.java
Log:
ejb-link test for an ear
Revision ChangesPath
1.1
jbosstest/src/main/org/jboss/test/naming/ejb/TestEjbLinkBean.java
Index: TestEjbLinkBean.java
===
package org.jboss.test.naming.ejb;
import javax.ejb.CreateException;
import javax.ejb.EJBException;
import javax.ejb.SessionBean;
import javax.ejb.SessionContext;
import javax.naming.Context;
import javax.naming.InitialContext;
import javax.naming.NamingException;
import javax.rmi.PortableRemoteObject;
import org.jboss.test.naming.interfaces.TestEjbLinkHome;
import org.jboss.test.naming.interfaces.TestEjbLink;
/** A bean that tests ejb-link works
@author a href=mailto:[EMAIL PROTECTED];Adrian.Brock/a
@version $Revision: 1.1 $
*/
public class TestEjbLinkBean implements SessionBean
{
org.apache.log4j.Category log = org.apache.log4j.Category.getInstance(getClass());
public void ejbCreate() throws CreateException
{
}
// --- Begin SessionBean interface methods
public void ejbActivate()
{
}
public void ejbPassivate()
{
}
public void ejbRemove()
{
}
public void setSessionContext(SessionContext sessionContext) throws EJBException
{
}
public String testEjbLinkCaller(String jndiName)
{
try
{
InitialContext initial = new InitialContext();
Object object = initial.lookup(jndiName);
TestEjbLinkHome home =
(TestEjbLinkHome) PortableRemoteObject.narrow(object,
TestEjbLinkHome.class);
TestEjbLink bean = home.create();
return bean.testEjbLinkCalled();
}
catch (Exception e)
{
log.debug(failed, e);
return Failed;
}
}
public String testEjbLinkCalled()
{
return Works;
}
}
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbosstest/src/resources/naming/jar/META-INF ejb-jar.xml jboss.xml
User: ejort Date: 02/03/17 04:56:30 Added: src/resources/naming/jar/META-INF ejb-jar.xml jboss.xml Log: ejb-link test for an ear Revision ChangesPath 1.1 jbosstest/src/resources/naming/jar/META-INF/ejb-jar.xml Index: ejb-jar.xml === ?xml version=1.0? !DOCTYPE ejb-jar PUBLIC -//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 1.1//EN http://java.sun.com/j2ee/dtds/ejb-jar_1_1.dtd; ejb-jar display-nameENC Tests/display-name enterprise-beans session descriptionA session bean on looks up stuff in the ENC/description ejb-nameENCBean/ejb-name ejb-classorg.jboss.test.naming.ejb.TestENCBean/ejb-class homeorg.jboss.test.naming.interfaces.TestENCHome/home remoteorg.jboss.test.naming.interfaces.TestENC/remote session-typeStateless/session-type transaction-typeContainer/transaction-type !-- Basic environment entries -- env-entry descriptionA flag indicating if the bean should perform the full ENC testsuite/description env-entry-namehasFullENC/env-entry-name env-entry-typejava.lang.Boolean/env-entry-type env-entry-valuetrue/env-entry-value /env-entry env-entry descriptionInteger0/description env-entry-nameInts/i0/env-entry-name env-entry-typejava.lang.Integer/env-entry-type env-entry-value0/env-entry-value /env-entry env-entry descriptionInteger1/description env-entry-nameInts/i1/env-entry-name env-entry-typejava.lang.Integer/env-entry-type env-entry-value1/env-entry-value /env-entry env-entry descriptionFloat0/description env-entry-nameFloats/f0/env-entry-name env-entry-typejava.lang.Float/env-entry-type env-entry-value0.0/env-entry-value /env-entry env-entry descriptionFloat1/description env-entry-nameFloats/f1/env-entry-name env-entry-typejava.lang.Float/env-entry-type env-entry-value1.1/env-entry-value /env-entry env-entry descriptionString0/description env-entry-nameStrings/s0/env-entry-name env-entry-typejava.lang.String/env-entry-type env-entry-valueString0/env-entry-value /env-entry env-entry descriptionString1/description env-entry-nameStrings/s1/env-entry-name env-entry-typejava.lang.String/env-entry-type env-entry-valueString1/env-entry-value /env-entry !-- EJB References (java:comp/env/ejb) -- ejb-ref ejb-ref-nameejb/bean0/ejb-ref-name ejb-ref-typeSession/ejb-ref-type ejb-linkENCBean0/ejb-link homeorg.jboss.test.naming.interfaces.TestENCHome2/home remoteorg.jboss.test.naming.interfaces.TestENC/remote /ejb-ref ejb-ref ejb-ref-nameejb/bean1/ejb-ref-name ejb-ref-typeSession/ejb-ref-type ejb-linkENCBean1/ejb-link homeorg.jboss.test.naming.interfaces.TestENCHome/home remoteorg.jboss.test.naming.interfaces.TestENC/remote /ejb-ref ejb-ref ejb-ref-nameejb/remote-bean/ejb-ref-name ejb-ref-typeSession/ejb-ref-type homeorg.jboss.test.naming.interfaces.TestENCHome/home remoteorg.jboss.test.naming.interfaces.TestENC/remote /ejb-ref !-- JDBC DataSources (java:comp/env/jdbc) -- resource-ref descriptionThe default DS/description res-ref-namejdbc/DefaultDS/res-ref-name res-typejavax.sql.DataSource/res-type res-authContainer/res-auth /resource-ref !-- JavaMail Connection Factories (java:comp/env/mail) -- resource-ref descriptionDefault Mail/description res-ref-namemail/DefaultMail/res-ref-name res-typejavax.mail.Session/res-type res-authContainer/res-auth /resource-ref !-- JMS Connection Factories (java:comp/env/jms) -- resource-ref descriptionDefault QueueFactory/description res-ref-namejms/QueFactory/res-ref-name
[JBoss-dev] CVS update: jboss/src/main/org/jboss/ejb Container.java EjbModule.java
User: ejort
Date: 02/03/17 04:59:45
Modified:src/main/org/jboss/ejb Container.java EjbModule.java
Log:
ejb-link fix for ears
Revision ChangesPath
1.83 +3 -3 jboss/src/main/org/jboss/ejb/Container.java
Index: Container.java
===
RCS file: /cvsroot/jboss/jboss/src/main/org/jboss/ejb/Container.java,v
retrieving revision 1.82
retrieving revision 1.83
diff -u -r1.82 -r1.83
--- Container.java11 Mar 2002 01:26:54 - 1.82
+++ Container.java17 Mar 2002 12:59:44 - 1.83
@@ -82,7 +82,7 @@
* @author a href=mailto:[EMAIL PROTECTED];Scott Stark/a.
* @author a href=[EMAIL PROTECTED]Bill Burke/a
* @author a href=mailto:[EMAIL PROTECTED];David Jencks/a
-* @version $Revision: 1.82 $
+* @version $Revision: 1.83 $
** pbRevisions:/b
*
* pb2001/07/26 bill burke:/b
@@ -921,7 +921,7 @@
// Internal link
if (debug)
log.debug(Binding +ref.getName()+ to internal JNDI source:
+ref.getLink());
- Container refContainer = ejbModule.getContainer(ref.getLink());
+ Container refContainer = ejbModule.findContainer(ref.getLink());
if (refContainer == null)
throw new DeploymentException (Bean +ref.getLink()+ not
found within this application.);
Util.bind(envCtx, ref.getName(), new
LinkRef(refContainer.getBeanMetaData().getJndiName()));
@@ -958,7 +958,7 @@
{
// Internal link
log.debug(Binding +refName+ to bean source: +ref.getLink());
- Container refContainer = ejbModule.getContainer(ref.getLink());
+ Container refContainer = ejbModule.findContainer(ref.getLink());
if (refContainer == null)
{
throw new DeploymentException (Bean +ref.getLink()+ not
found within this application.);
1.13 +103 -16 jboss/src/main/org/jboss/ejb/EjbModule.java
Index: EjbModule.java
===
RCS file: /cvsroot/jboss/jboss/src/main/org/jboss/ejb/EjbModule.java,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- EjbModule.java14 Mar 2002 23:46:49 - 1.12
+++ EjbModule.java17 Mar 2002 12:59:44 - 1.13
@@ -15,6 +15,7 @@
import java.util.HashMap;
import java.util.Hashtable;
import java.util.Iterator;
+import java.util.WeakHashMap;
import javax.ejb.EJBLocalHome;
import javax.management.MBeanServer;
import javax.management.ObjectName;
@@ -61,11 +62,14 @@
import org.jboss.util.jmx.ObjectNameFactory;
/**
- * An Application represents a collection of beans that are deployed as a
+ * An EjbModule represents a collection of beans that are deployed as a
* unit.
*
- * pThe beans may use the Application to access other beans within the same
+ * pThe beans may use the EjbModule to access other beans within the same
*deployment unit.
+ *
+ * pThe beans may use the EjbModule to access other beans within the same
+ *deployment package (e.g. an ear) using findContainer(String).
*
* @see Container
* @see EJBDeployer
@@ -73,7 +77,8 @@
* @author a href=mailto:[EMAIL PROTECTED];Rickard Öberg/a
* @author a href=mailto:[EMAIL PROTECTED];David Jencks/a
* @author a href=mailto:[EMAIL PROTECTED];Francisco Reverbel/a
- * @version $Revision: 1.12 $
+ * @author a href=mailto:[EMAIL PROTECTED];Adrian.Brock/a
+ * @version $Revision: 1.13 $
*
* @jmx:mbean extends=org.jboss.system.ServiceMBean
*/
@@ -108,14 +113,14 @@
// Attributes
- /** Stores the containers for this application unit. */
+ /** Stores the containers for this deployment unit. */
HashMap containers = new HashMap();
HashMap localHomes = new HashMap();
- /** Class loader of this application. */
+ /** Class loader of this deployment unit. */
ClassLoader classLoader = null;
- /** Name of this application, url it was deployed from */
+ /** Name of this deployment unit, url it was deployed from */
final String name;
private final DeploymentInfo deploymentInfo;
@@ -128,6 +133,9 @@
//private MBeanServer server;
// Static
+
+ /** Stores a map of DeploymentInfos to EjbModules. */
+ private static WeakHashMap ejbModulesByDeploymentInfo = new WeakHashMap();
// Public
@@ -137,9 +145,13 @@
{
this.deploymentInfo = di;
this.name =
Re: [JBoss-dev] [ jboss-Bugs-525412 ] EAR Deployment Problem with ejb-link
Hi, I've committed a fix for the problem below, but I've hit a snag with njar :-( I nearly got the ejb-link../products/product.jar#EJBProduct/ejb-link working from the EJB2.0 spec. But when I use new URL(context, spec) the njar separator is removed. e.g. if the above link is referenced from njar:file:/longpath/someapp.ear^/some.jar you get njar:file:/longpath/someapp.ear/products/product.jar#EJBProduct instead of the required njar:file:/longpath/someapp.ear^/products/product.jar#EJBProduct I think I've got to implement parseURL() in the njar's handler. Is this the correct solution or does somebody know a better way of doing this? PS. There's a memory leak in the committed version, which I've already fixed and I've also got tests for ejb-local-ref now as well. Regards, Adrian Bugs item #525412, was opened at 2002-03-04 07:47 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=37668 aid=525412group_id=22866 Category: JBossServer Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 5 Submitted By: Peter Luttrell (objec) Assigned to: Adrian Brock (ejort) Summary: EAR Deployment Problem with ejb-link Initial Comment: According to the dtd for an ejb-jar, (http://java.sun.com/dtd/ejb-jar_2_0.dtd), the value of the ejb-link element must be omitted. or in another ejb-jar file in the same J2EE application unit. I take this to mean that you can use the name of a bean in another ejb-jar within an ear. In my attached example, the Titan.ear file contains 2 ejb jars: CabinEJB.jar and TravelAgentEJB.jar. In the deployment descriptor for TravelAgentEJB, I have an ejb-linkCabinEJB/ejb-link. CabinEJB is the name of the entity bean within CabinEJB.jar. If I deploy this ear on JBoss3.0.0beta, deployment fails because CabinEJB is not found. Based on my intrepetation of the spec, I expect it to deploy without a problem. Note that if I rearrange my deployment, such that both ejbs are in the same jar file with the same deployment descriptor, JBoss3.0.0beta deploys it perfectly. JBoss dist: JBoss3.0.0 + Tomcat 4.0.2 posted to sourceforge on 2002-02-22 OS: Redhat7.2 jdk: 1.3.1 To run the sample, which illistrates the problem: open up the build script and set your jboss install dir, then run the deploy-as-an-ear target. If you want to see it work as an ejb jar run deploy-as-a-single-jar target. Here's the first exception caused by this problem: datestamp ERROR [StatelessSessionContainer] Exception in service lifecycle operation: create org.jboss.deployment.DeploymentException: Bean CabinEJB not found within this applicaion. at org.jboss.ejb.Container.setupEnvironment(Continer.java 906) Note that the sample code is from Richard Monson-Haefel's book titled Enterprise JavaBeans. -- --- Comment By: Adrian Brock (ejort) Date: 2002-03-16 20:36 Message: Logged In: YES user_id=9459 The ear (deployment) level list of containers has been lost during the modifications to include ejbs in sars at any level. The ejb-link is only checking for containers in the same jar. Regards, Adrian -- --- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=37668 aid=525412group_id=22866 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-dev lopment _ View thread online: http://main.jboss.org/thread.jsp?forum=66thread=10112 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: contrib/jetty/src/main/org/jboss/jetty Jetty.java
User: jules_gosnell
Date: 02/03/17 11:02:25
Modified:jetty/src/main/org/jboss/jetty Jetty.java
Log:
touch up
Revision ChangesPath
1.43 +54 -66contrib/jetty/src/main/org/jboss/jetty/Jetty.java
Index: Jetty.java
===
RCS file: /cvsroot/jboss/contrib/jetty/src/main/org/jboss/jetty/Jetty.java,v
retrieving revision 1.42
retrieving revision 1.43
diff -u -r1.42 -r1.43
--- Jetty.java27 Feb 2002 03:14:49 - 1.42
+++ Jetty.java17 Mar 2002 19:02:25 - 1.43
@@ -5,7 +5,7 @@
* See terms of license at gnu.org.
*/
-// $Id: Jetty.java,v 1.42 2002/02/27 03:14:49 janb Exp $
+// $Id: Jetty.java,v 1.43 2002/03/17 19:02:25 jules_gosnell Exp $
// A Jetty HttpServer with the interface expected by JBoss'
// J2EEDeployer...
@@ -31,13 +31,13 @@
import org.jboss.deployment.DeploymentException;
import org.jboss.jetty.xml.JettyResolver;
import org.jboss.logging.Logger;
+import org.jboss.security.SecurityAssociation;
import org.jboss.web.AbstractWebContainer.WebDescriptorParser;
import org.jboss.web.WebApplication;
-import org.jboss.security.SecurityAssociation;
import org.mortbay.http.HttpContext;
+import org.mortbay.http.HttpException;
import org.mortbay.http.HttpRequest;
import org.mortbay.http.HttpResponse;
-import org.mortbay.http.HttpException;
import org.mortbay.jetty.servlet.WebApplicationContext;
import org.mortbay.util.MultiException;
import org.mortbay.xml.XmlConfiguration;
@@ -50,7 +50,7 @@
*
* @author a href=mailto:[EMAIL PROTECTED];Julian Gosnell/a
* @author a href=mailto:[EMAIL PROTECTED];Andreas Schaefer/a.
- * @version $Revision: 1.42 $
+ * @version $Revision: 1.43 $
*
* pbRevisions:/b
*
@@ -111,37 +111,35 @@
_log.error(problem building descriptor parser, e);
}
-
// check support for JSP compilation...
if
(findResourceInJar(com/sun/tools/javac/v8/resources/javac.properties)==null)
_log.warn(JSP compilation requires $JAVA_HOME/lib/tools.jar on your
JBOSS_CLASSPATH);
}
-
-
-//
-// class loader delegation policy property
-//
- boolean _loaderCompliance = true;
-/**
- * @param loaderCompliance if true, Jetty delegates class loading
- *to parent class loader first, false implies servlet spec 2.3 compliance
- */
-public synchronized void setJava2ClassLoadingCompliance (boolean
loaderCompliance)
-{
-_loaderCompliance = loaderCompliance;
-}
-
-/**
- * @return true if Java2 style class loading delegation, false if
- *servlet2.3 spec compliance
- */
-public synchronized boolean getJava2ClassLoadingCompliance ()
-{
-return _loaderCompliance;
-}
-
-
+ //
+ // class loader delegation policy property
+ //
+ boolean _loaderCompliance = true;
+
+ /**
+ * @param loaderCompliance if true, Jetty delegates class loading
+ *to parent class loader first, false implies servlet spec 2.3 compliance
+ */
+ public synchronized void
+setJava2ClassLoadingCompliance (boolean loaderCompliance)
+ {
+_loaderCompliance = loaderCompliance;
+ }
+
+ /**
+ * @return true if Java2 style class loading delegation, false if
+ *servlet2.3 spec compliance
+ */
+ public synchronized boolean
+getJava2ClassLoadingCompliance ()
+ {
+return _loaderCompliance;
+ }
//
// unpackWars property
@@ -194,8 +192,6 @@
if (_log.isDebugEnabled())
_log.debug (webdefault specification is: +_webDefault);
-
-
}
public synchronized String
@@ -276,23 +272,21 @@
return _subjectAttributeName;
}
-
-
-
//
// configuration property
//
- public Element getConfigurationElement ()
+ public Element
+getConfigurationElement()
{
return _configElement;
-
}
/**
* @param configElement XML fragment from jboss-service.xml
*/
- public void setConfigurationElement (Element configElement)
+ public void
+setConfigurationElement(Element configElement)
{
// convert to an xml string to pass into Jetty's normal
@@ -350,7 +344,8 @@
/* Actually perform the configuration
* @param xmlString
*/
- private void setXMLConfiguration (String xmlString)
+ private void
+setXMLConfiguration(String xmlString)
{
try
@@ -364,10 +359,6 @@
}
}
-
-
-
-
[JBoss-dev] possible bug in container managed JMS
I get this stacktrace when the bean with container managed JMS is passivated: INFO [STDOUT] AbstraktSender.ejbPassivate 21:13:03,098 ERROR [Log4jService$ThrowableListenerLoggingAdapter] unhandled throwable 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:1854) 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:1854) 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) Should this class be serializeable or am I doing somthing wrong. (I have followed the example in the JMS doc on jboss.org) Marius K Boostcom.no signature.asc Description: This is a digitally signed message part
[JBoss-dev] CVS update: jmx/src/main/org/jboss/mx/loading UnifiedClassLoader.java
User: juhalindfors
Date: 02/03/17 12:32:09
Modified:src/main/org/jboss/mx/loading UnifiedClassLoader.java
Log:
defining the class in the correct place
Revision ChangesPath
1.2 +12 -7 jmx/src/main/org/jboss/mx/loading/UnifiedClassLoader.java
Index: UnifiedClassLoader.java
===
RCS file: /cvsroot/jboss/jmx/src/main/org/jboss/mx/loading/UnifiedClassLoader.java,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- UnifiedClassLoader.java 17 Mar 2002 10:30:31 - 1.1
+++ UnifiedClassLoader.java 17 Mar 2002 20:32:09 - 1.2
@@ -29,7 +29,7 @@
* @author a href=[EMAIL PROTECTED]Christoph G. Jung/a
* @author a href=[EMAIL PROTECTED]Scott Stark/a
* @author a href=[EMAIL PROTECTED]Juha Lindfors/a
- * @version tt$Revision: 1.1 $/tt
+ * @version tt$Revision: 1.2 $/tt
*
* pb20010830 marc fleury:/b
* ul
@@ -125,23 +125,28 @@
}
/**
+*
*/
- public Class loadClassLocally(String name, boolean resolve)
- throws ClassNotFoundException
+ protected Class findClass(String name) throws ClassNotFoundException
{
- // check our own class definitions foist, then delegate to parent
Object o = classes.get(name);
if (o != null)
{
byte[] code = (byte[])o;
+ classes.remove(name);
return defineClass(name, code, 0, code.length);
}
- else
- {
- return super.loadClass(name, resolve);
- }
+ else return super.findClass(name);
+ }
+
+ /**
+*/
+ public Class loadClassLocally(String name, boolean resolve)
+ throws ClassNotFoundException
+ {
+ return super.loadClass(name, resolve);
}
/**
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-531090 ] entity returned by custom finder fails
Bugs item #531090, was opened at 2002-03-17 20:45
You can respond by visiting:
http://sourceforge.net/tracker/?func=detailatid=376685aid=531090group_id=22866
Category: JBossCMP
Group: v3.0 Rabbit Hole
Status: Open
Resolution: None
Priority: 5
Submitted By: Jürgen Zeller (zetzet)
Assigned to: Nobody/Anonymous (nobody)
Summary: entity returned by custom finder fails
Initial Comment:
I wrote a custom finder:
public Collection ejbFindByPrimaryKeys(Collection
pKeys) throws FinderException
{
Collection beans= new ArrayList(pKeys.size());
e1Home home = (e1Home)
mEntityContext.getEJBLocalHome();
for (Iterator i= pKeys.iterator(); i.hasNext
(); )
{
Integer key= (Integer)i.next();
e1 bean= home.findByPrimaryKey(key);
beans.add(bean);
}
return beans;
}
The finder works, and returns the right beans
in the collection.
As soon any getter of a bean is accessed, the
getter fails with an SQLException:
2002-03-17 18:17:16,655 DEBUG
[org.jboss.ejb.plugins.cmp.jdbc.JDBCLoadEntityCommand.e
1EJB] Executing SQL: SELECT b FROM TAB1 WHERE (a=?)
2002-03-17 18:17:16,655 TRACE
[org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMP2xFieldBr
idge.e1EJB.a] Set parameter: index=1,
jdbcType=INTEGER, value=e1EJB:1100
2002-03-17 18:17:16,685 ERROR
[org.jboss.ejb.plugins.LogInterceptor]
TransactionRolledbackException, causedBy:
java.sql.SQLException: ERROR: parser: parse error at
or near :
The reason is somehow related to
JDBCLoadEntityCommand, line 87
ReadAheadCache.EntityReadAheadInfo info =
readAheadCache.getEntityReadAheadInfo
(ctx.getId());
ctx.getId() returns the bean object, but is
handeled as PK object afterwards
JBoss 3.0.0b2 CVS 2002-03-17 HEAD
--
You can respond by visiting:
http://sourceforge.net/tracker/?func=detailatid=376685aid=531090group_id=22866
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Patches-531094 ] Fix for classpath for Jikes
Patches item #531094, was opened at 2002-03-17 22:56 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376687aid=531094group_id=22866 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Stanislav Borutsky (borus) Assigned to: Nobody/Anonymous (nobody) Summary: Fix for classpath for Jikes Initial Comment: When you try to use JBoss + embedded Tomcat + Jikes, Tomcat will pass to Jikes the value of java.class.path And it's OK. BUT: when JBoss fills the classpath using MLET CODE = org.jboss.util.ClassPathExtension in conf/tomcat/jboss.conf it fills it using the URL.getFile() method, which on Windows will create full paths to files like the following: /C:/JBoss/lib/ext This entry is OK for Java itself to find it's classes, but is very bad for Jikes compiler on Windows (on Unix the additional slash doesn't break anything) The attached ClassPathExtension.java is supposed to replace the original. What it does: instead of using URL.getFile(), it converts the above to File and retrieves the path correct for current platform (and which is good for Jikes) using File.getCanonicalPath() Please answer me whether this patch will be included and how can I make JBoss use my own class without replacing it inside jboss.jar -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376687aid=531094group_id=22866 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-531090 ] entity returned by custom finder fails
Bugs item #531090, was opened at 2002-03-17 14:45
You can respond by visiting:
http://sourceforge.net/tracker/?func=detailatid=376685aid=531090group_id=22866
Category: JBossCMP
Group: v3.0 Rabbit Hole
Status: Closed
Resolution: Invalid
Priority: 5
Submitted By: Jürgen Zeller (zetzet)
Assigned to: Dain Sundstrom (dsundstrom)
Summary: entity returned by custom finder fails
Initial Comment:
I wrote a custom finder:
public Collection ejbFindByPrimaryKeys(Collection
pKeys) throws FinderException
{
Collection beans= new ArrayList(pKeys.size());
e1Home home = (e1Home)
mEntityContext.getEJBLocalHome();
for (Iterator i= pKeys.iterator(); i.hasNext
(); )
{
Integer key= (Integer)i.next();
e1 bean= home.findByPrimaryKey(key);
beans.add(bean);
}
return beans;
}
The finder works, and returns the right beans
in the collection.
As soon any getter of a bean is accessed, the
getter fails with an SQLException:
2002-03-17 18:17:16,655 DEBUG
[org.jboss.ejb.plugins.cmp.jdbc.JDBCLoadEntityCommand.e
1EJB] Executing SQL: SELECT b FROM TAB1 WHERE (a=?)
2002-03-17 18:17:16,655 TRACE
[org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMP2xFieldBr
idge.e1EJB.a] Set parameter: index=1,
jdbcType=INTEGER, value=e1EJB:1100
2002-03-17 18:17:16,685 ERROR
[org.jboss.ejb.plugins.LogInterceptor]
TransactionRolledbackException, causedBy:
java.sql.SQLException: ERROR: parser: parse error at
or near :
The reason is somehow related to
JDBCLoadEntityCommand, line 87
ReadAheadCache.EntityReadAheadInfo info =
readAheadCache.getEntityReadAheadInfo
(ctx.getId());
ctx.getId() returns the bean object, but is
handeled as PK object afterwards
JBoss 3.0.0b2 CVS 2002-03-17 HEAD
--
Comment By: Dain Sundstrom (dsundstrom)
Date: 2002-03-17 14:58
Message:
Logged In: YES
user_id=251431
Custom finders need to return a collection of primary key
objects. You are returning actual entity beans.
All you need to do is return the pKeys collection that is
passed in.
--
You can respond by visiting:
http://sourceforge.net/tracker/?func=detailatid=376685aid=531090group_id=22866
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: newsite/src/docs/developers jboss-jbossClustering.jsp jboss-projects.jsp
User: patriot1burke Date: 02/03/17 15:53:17 Modified:src/docs/developers jboss-projects.jsp Added: src/docs/developers jboss-jbossClustering.jsp Log: added clustering project Revision ChangesPath 1.5 +4 -0 newsite/src/docs/developers/jboss-projects.jsp Index: jboss-projects.jsp === RCS file: /cvsroot/jboss/newsite/src/docs/developers/jboss-projects.jsp,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- jboss-projects.jsp18 Feb 2002 09:13:30 - 1.4 +++ jboss-projects.jsp17 Mar 2002 23:53:17 - 1.5 @@ -14,6 +14,8 @@ lia class=link href=jboss-jbosscx.jspJBossCX/a/li + lia class=link href=jboss-jbossClustering.jspJBossClustering/a/li + lia class=link href=jboss-jbosstx.jspJBossTX/a /li lia class=link href=jboss-jbossSX.jspJBossSX/a/li @@ -106,6 +108,8 @@ p class=headJBossGUI p class=textimg src=/pictures/jbossgui.gif alt=graphical management of containers, beans, resources, security +p class=headJBossClustering -- High Availability and Load-Balancing services +p class=textMultiple JBoss servers can now work together seemlessly as a cluster to provide failover and load-balancing services. p class=headJBoss.net -- Integrating Web Services with J2EE p class=texta class=link href=jboss-net.jspimg src=/pictures/jboss-net.png alt=JBoss.net/a 1.1 newsite/src/docs/developers/jboss-jbossClustering.jsp Index: jboss-jbossClustering.jsp === jsp:include page=head.jsp flush=true / jsp:include page=slogan.jsp flush=true jsp:param name=SLOGAN value=JBossClustering/ /jsp:include jsp:include page=/common/jboss-jbossClustering.jsp flush=true/ jsp:include page=navigation.jsp flush=true / ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: newsite/src/docs/common cluster-service.xml jboss-jbossClustering.jsp JBossCluster_FeatureMatrix_v5.doc
User: patriot1burke Date: 02/03/17 15:54:34 Added: src/docs/common cluster-service.xml jboss-jbossClustering.jsp JBossCluster_FeatureMatrix_v5.doc Log: added clustering project Revision ChangesPath 1.1 newsite/src/docs/common/cluster-service.xml Index: cluster-service.xml === ?xml version=1.0 encoding=UTF-8? !-- = -- !-- -- !-- Sample Clustering Service Configuration -- !-- -- !-- = -- server classpath codebase=lib archives=jbossha.jar/ !-- -- !-- Cluster Partition: defines cluster -- !-- -- mbean code=org.jboss.ha.framework.server.ClusterPartition name=jboss:service=DefaultPartition /mbean !-- -- !-- HA Session State Service for SFSB-- !-- -- mbean code=org.jboss.ha.hasessionstate.server.HASessionStateService name=jboss:service=HASessionState dependsjboss:service=DefaultPartition/depends /mbean !-- -- !-- HA JNDI -- !-- -- mbean code=org.jboss.ha.jndi.HANamingService name=jboss:service=HAJNDI dependsjboss:service=DefaultPartition/depends /mbean mbean code=org.jboss.invocation.jrmp.server.JRMPInvokerHA name=jboss:service=invoker,type=jrmpha /mbean /server 1.1 newsite/src/docs/common/jboss-jbossClustering.jsp Index: jboss-jbossClustering.jsp === p class=headJBossClustering: High Availability and Load-Balancing services. p class=text JBossClustering is the final piece of the puzzle that makes JBoss a true Enterprise-Class Application Server. With it's fail-over, load-balancing, and distributed deployment features, JBossClustering provides the means to develop large scalable robust applications. /p p class=text JBossClustering originally began in April 2001 as a small prototype built on top of a href=http://www.javagroups.com;JavaGroups/a and coded by Sacha Labourey. Bill Burke joined Sacha in August 2001 and together they redesigned JBossClustering from scratch to it's current form in JBoss 3.0. Andreas Schaefer contributed JBossClustering's distributed deployment mechanisms. Bill, Sacha, and Andreas can be found speaking about these new technologies at various JBoss training coures and seminars. /p p class=headFEATURES p class=text UL liAutomatic discovery. Nodes in cluster find each other with no additional configuration. liCluster-wide replicated JNDI context liFailover and load-balancing for JNDI, RMI, and all EJB types. liStateful Session Bean state replication. liHTTP Session replication with Jetty. icoming soon in JBoss 3.0 Final/i liFarming. Distributed deployment of jboss components. Deploying on one node deploys on all nodes. liCheck out our detailed a href=/common/JBossCluster_FeatureMatrix_v5.docFeature Matrix/a /UL p class=headGETTING STARTED p class=text Getting started with JBossClustering is very easy. Plop a href=/common/cluster-service.xmlcluster-service.xml/a into the JBoss deploy directory. Also, in jboss.xml of your bean add the clustered flag, and poof! You have a clustered bean. p class=text code lt;sessiongt; nbsp;nbsp;lt;ejb-namegt;nextgen.StatelessSessionlt;/ejb-namegt;
Re: [JBoss-dev] possible bug in container managed JMS
on 17-03-2 21.21, Marius Kotsbak at [EMAIL PROTECTED] wrote: I get this stacktrace when the bean with container managed JMS is passivated: Yes - Protocol - is protocol : Whatever mind U HAVE over there is welcome ! /p INFO [STDOUT] AbstraktSender.ejbPassivate 21:13:03,098 ERROR [Log4jService$ThrowableListenerLoggingAdapter] unhandled throwable 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:1854) 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:1854) 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(S tatefulSessionFilePersistenceManager.java:287) at org.jboss.ejb.plugins.StatefulSessionInstanceCache.passivate(StatefulSessionIn stanceCache.java:65) at org.jboss.ejb.plugins.AbstractInstanceCache$1.execute(AbstractInstanceCache.ja va:737) at org.jboss.util.WorkerQueue$QueueLoop.run(WorkerQueue.java:206) at java.lang.Thread.run(Thread.java:498) Should this class be serializeable or am I doing somthing wrong. (I have followed the example in the JMS doc on jboss.org) Marius K Boostcom.no ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Automated JBoss Testsuite Results: 18-March-2002
JBoss daily test results SUMMARY Number of tests run: 537 Successful tests: 517 Errors:12 Failures: 8 [time of test: 18 March 2002 0:52 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
[JBoss-dev] Automated JBoss Testsuite Results: 18-March-2002
JBoss daily test results SUMMARY Number of tests run: 544 Successful tests: 526 Errors:10 Failures: 8 [time of test: 18 March 2002 1:37 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: 18-March-2002
JBoss daily test results SUMMARY Number of tests run: 544 Successful tests: 527 Errors:10 Failures: 7 [time of test: 18 March 2002 2:21 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: 18-March-2002
JBoss daily test results SUMMARY Number of tests run: 544 Successful tests: 527 Errors:10 Failures: 7 [time of test: 18 March 2002 3: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: 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: 18-March-2002
JBoss daily test results SUMMARY Number of tests run: 544 Successful tests: 527 Errors:10 Failures: 7 [time of test: 18 March 2002 4:36 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] Automated JBoss Testsuite Results: 18-March-2002
JBoss daily test results SUMMARY Number of tests run: 544 Successful tests: 527 Errors:10 Failures: 7 [time of test: 18 March 2002 5:36 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] Re: [jetty-support] More on Deployments: Applet jars
Applet jars should be treated as content, just as you say like a gif or html file. There is no standard mechanism to get an applet jar out of a WEB-INF/classes or WEB-INF/lib directory. cheers Ignacio Coloma wrote: Hi, has someone realized that applet jars are included in wars and should be put 'as is' on the web resources dir? (I mean, treated the same as any gif image or html file) I'm asking because I use one of these and my app used to work nice until two days or so. Then I realized that since some time ago my applet jar is not accesible for the browser but instead being copied to the temp dir of JBoss. Yahoo! Groups Sponsor -~-- Tiny Wireless Camera under $80! Order Now! FREE VCR Commander! Click Here - Only 1 Day Left! http://us.click.yahoo.com/nuyOHD/7.PDAA/yigFAA/CefplB/TM -~- For the latest information about Jetty, please see http://jetty.mortbay.org Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/ -- Greg Wilkins[EMAIL PROTECTED] GB Phone: +44-(0)7092063462 Mort Bay Consulting Australia and UK.Mbl Phone: +61-(0)4 17786631 http://www.mortbay.com AU Phone: +61-(0)2 98107029 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
