[JBoss-dev] CVS update: jbossmq/src/main/org/jbossmq/filepersistence - New directory
User: pkendall Date: 01/05/15 00:17:06 jbossmq/src/main/org/jbossmq/filepersistence - New directory ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbossmq/src/main/org/jbossmq/server StartServer.java PersistenceManager.java JMSDestination.java
User: pkendall
Date: 01/05/15 00:16:48
Modified:src/main/org/jbossmq/server StartServer.java
PersistenceManager.java JMSDestination.java
Log:
Modifications for abstracting out persistence package.
Revision ChangesPath
1.3 +24 -14jbossmq/src/main/org/jbossmq/server/StartServer.java
Index: StartServer.java
===
RCS file: /cvsroot/jboss/jbossmq/src/main/org/jbossmq/server/StartServer.java,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- StartServer.java 2001/03/02 01:13:02 1.2
+++ StartServer.java 2001/05/15 07:16:48 1.3
@@ -40,7 +40,7 @@
/**
* Class used to start a JMS service. This can be called from inside another
-
+
* application to start the JMS provider.
*
* @author Norbert Lataille ([EMAIL PROTECTED])
@@ -48,7 +48,7 @@
* @author Vincent Sheffer ([EMAIL PROTECTED])
* @author Hiram Chirino ([EMAIL PROTECTED])
*
- * @version $Revision: 1.2 $
+ * @version $Revision: 1.3 $
*/
public class StartServer implements Runnable
{
@@ -143,10 +143,10 @@
public void run() {
try {
-
+
//Load the property file
InputStream in =
getClass().getClassLoader().getResource("jbossmq.xml").openStream();
- XElement serverCfg = XElement.createFrom(in);
+ XElement serverCfg = XElement.createFrom(in);
in.close();
// Make sure that we loaded the right type of xml file
@@ -166,15 +166,25 @@
UserManager userManager=new UserManager(theServer,
serverCfg.getElement("UserManager"));
theServer.userManager = userManager;
- //Creatye a PersistenceManager object
- PersistenceManager persistenceManager = new
PersistenceManager(theServer, serverCfg.getElement("PersistenceManager"));
+ //Create a PersistenceManager object
+ PersistenceManager persistenceManager;
+ XElement pmcfg = serverCfg.getElement("PersistenceManager");
+ if( pmcfg.getAttribute("class") == null ) {
+ persistenceManager = new
org.jbossmq.persistence.PersistenceManager(theServer, pmcfg);
+ }
+ else {
+ Class pmc = getClass().forName(pmcfg.getAttribute("class"));
+ Class[] types = {theServer.getClass(),
pmcfg.getClass()};
+ Object[] args = {theServer, pmcfg};
+ persistenceManager =
(PersistenceManager)pmc.getConstructor(types).newInstance(args);
+ }
theServer.persistenceManager = persistenceManager;
-
+
registerService(theServer, new
ObjectName(JMSServer.OBJECT_NAME));
//create the known topics
Context subcontext=ctx.createSubcontext("topic");
-
+
Enumeration enum = serverCfg.getElementsNamed("Topic");
while( enum.hasMoreElements() ) {
XElement element = (XElement)enum.nextElement();
@@ -183,11 +193,11 @@
Topic t=theServer.newTopic(name);
subcontext.rebind(name,t);
}
-
+
//create the known queues
subcontext=ctx.createSubcontext("queue");
-
+
enum = serverCfg.getElementsNamed("Queue");
while( enum.hasMoreElements() ) {
XElement element = (XElement)enum.nextElement();
@@ -205,7 +215,7 @@
enum = serverCfg.getElementsNamed("InvocationLayer");
while( enum.hasMoreElements()) {
-
+
XElement element = (XElement)enum.nextElement();
String name = element.getField("Name");
String topicConnectionFactoryJNDI =
element.getField("TopicConnectionFactoryJNDI");
@@ -228,12 +238,12 @@
//(re)bind the connection factories in the JNDI
namespace
ctx.rebind(topicConnectionFactoryJNDI,invocationLayerFactory.spyTopicConnectionFactory);
-
ctx.rebind(queueConnectionFactoryJNDI,invocationLayerFactory.spyQueueConnectionFactory);
+
[JBoss-dev] CVS update: jbossmq/src/main/org/jbossmq/persistence PersistenceManager.java
User: pkendall
Date: 01/05/15 00:15:45
Added: src/main/org/jbossmq/persistence PersistenceManager.java
Log:
Taken & modified from server package to form new persistence logfile based
persistence package.
Revision ChangesPath
1.1 jbossmq/src/main/org/jbossmq/persistence/PersistenceManager.java
Index: PersistenceManager.java
===
/*
* JBossMQ, the OpenSource JMS implementation
*
* Distributable under LGPL license.
* See terms of license at gnu.org.
*/
package org.jbossmq.persistence;
import javax.jms.JMSException;
import java.net.URL;
import java.util.HashMap;
import java.util.TreeSet;
import java.util.Iterator;
import java.util.LinkedList;
import org.jbossmq.xml.XElement;
import org.jbossmq.server.JMSServer;
import org.jbossmq.server.JMSDestination;
import org.jbossmq.SpyMessage;
import org.jbossmq.SpyDestination;
import org.jbossmq.SpyDistributedConnection;
/**
*This class manages all persistence related services.
*
*@author Hiram Chirino ([EMAIL PROTECTED])
*
*@version $Revision: 1.1 $
*/
public class PersistenceManager extends org.jbossmq.server.PersistenceManager {
// The server this persistence manager is providing service for
JMSServer server;
// The configuration data for the manager.
XElement configElement;
// The directory where persistence data should be stored
URL dataDirectory;
// Log file used to store commited transactions.
SpyTxLog spyTxLog;
// Maps SpyDestinations to SpyMessageLogs
HashMap messageLogs = new HashMap();
static class LogInfo {
SpyMessageLog log;
SpyDestination destination;
String queueId;
LogInfo(SpyMessageLog log, SpyDestination destination, String queueId)
{
this.log=log;
this.destination=destination;
this.queueId=queueId;
}
}
/**
* PersistenceManager constructor.
*/
public PersistenceManager(JMSServer server, XElement configElement) throws
javax.jms.JMSException {
try {
this.server = server;
this.configElement = configElement;
URL configFile =
getClass().getClassLoader().getResource("jbossmq.xml");
dataDirectory = new URL(configFile,
configElement.getField("DataDirectory"));
URL txLogFile = new URL(dataDirectory, "transactions.dat");
spyTxLog = new SpyTxLog(txLogFile.getFile());
} catch (Exception e) {
javax.jms.JMSException newE = new
javax.jms.JMSException("Invalid configuration.");
newE.setLinkedException(e);
throw newE;
}
}
public Long createPersistentTx() throws javax.jms.JMSException {
return spyTxLog.createTx();
}
public void commitPersistentTx(Long txId) throws javax.jms.JMSException {
spyTxLog.commitTx(txId);
}
public void rollbackPersistentTx(Long txId) throws javax.jms.JMSException {
spyTxLog.rollbackTx(txId);
}
public void restore() throws javax.jms.JMSException {
TreeSet commitedTXs = spyTxLog.restore();
HashMap clone;
synchronized (messageLogs) {
clone = (HashMap) messageLogs.clone();
}
Iterator iter = clone.values().iterator();
while (iter.hasNext()) {
LogInfo logInfo = (LogInfo)iter.next();
JMSDestination q =
server.getJMSDestination(logInfo.destination);
SpyMessage rebuild[] = logInfo.log.restore(commitedTXs);
//TODO: make sure this lock is good enough
synchronized (q) {
for (int i = 0; i < rebuild.length; i++) {
q.restoreMessage(rebuild[i], logInfo.queueId);
}
}
}
}
public void initQueue( SpyDestination dest, String queueId ) throws
javax.jms.JMSException {
try {
URL logFile = new URL(dataDirectory,
dest.toString()+"-"+queueId+".dat");
SpyMessageLog log = new SpyMessageLog(logFile.getFile());
LogInfo info = new LogInfo(log, dest, queueId);
messageLogs.put(""+dest+"-"+queueId, info);
} catch (javax.jms.J
[JBoss-dev] CVS update: jboss/src/main/org/jboss/deployment J2eeDeployer.java
User: schaefera
Date: 01/05/14 11:39:27
Modified:src/main/org/jboss/deployment J2eeDeployer.java
Log:
Implementation of the 1. draft for the JBoss management class in the
J2EEDeployer to figure out what applications are deployed.
Revision ChangesPath
1.22 +88 -1 jboss/src/main/org/jboss/deployment/J2eeDeployer.java
Index: J2eeDeployer.java
===
RCS file: /cvsroot/jboss/jboss/src/main/org/jboss/deployment/J2eeDeployer.java,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -r1.21 -r1.22
--- J2eeDeployer.java 2001/04/15 05:41:21 1.21
+++ J2eeDeployer.java 2001/05/14 18:39:27 1.22
@@ -41,6 +41,9 @@
import javax.management.RuntimeMBeanException;
import javax.management.RuntimeErrorException;
+import org.jboss.mgt.Application;
+import org.jboss.mgt.Module;
+import org.jboss.mgt.ServerDataCollector;
import org.jboss.logging.Log;
import org.jboss.util.MBeanProxy;
import org.jboss.util.ServiceMBeanSupport;
@@ -67,7 +70,7 @@
*
* @author mailto:[EMAIL PROTECTED]";>Daniel Schulze
* @author Toby Allsopp ([EMAIL PROTECTED])
-* @version $Revision: 1.21 $
+* @version $Revision: 1.22 $
*/
public class J2eeDeployer
extends ServiceMBeanSupport
@@ -178,10 +181,24 @@
{
URL url = new URL (_url);
+ ObjectName lCollector = null;
+ try {
+ lCollector = new ObjectName( "Management", "service", "Collector" );
+ }
+ catch( Exception e ) {
+ }
+
// undeploy first if it is a redeploy
try
{
undeploy (_url);
+ // Remove application data by its id
+ server.invoke(
+lCollector,
+"removeApplication",
+new Object[] { _url },
+new String[] { "java.lang.String" }
+ );
}
catch (Exception _e)
{}
@@ -195,6 +212,25 @@
{
startApplication (d);
log.log ("J2EE application: " + _url + " is deployed.");
+try {
+// Now the application is deployed add it to the server data collector
+Application lApplication = convert2Application( _url, d );
+server.invoke(
+ lCollector,
+ "saveApplication",
+ new Object[] {
+ _url,
+ lApplication
+ },
+ new String[] {
+ "java.lang.String",
+ lApplication.getClass().getName()
+ }
+);
+}
+catch( Exception e ) {
+ log.log ("Report of deployment of J2EE application: " + _url + " could
not be reported.");
+}
}
catch (Exception _e)
{
@@ -648,5 +684,56 @@
// set it as the context class loader for the deployment thread
Thread.currentThread().setContextClassLoader(appCl);
+ }
+
+ /**
+* Converts a given Deployment to a Management Application
+*
+* @param pId Application Id
+* @param pDeployment Deployment to be converted
+*
+* @return Converted Applicaiton
+**/
+ public Application convert2Application(
+ String pId,
+ Deployment pDeployment
+ ) {
+ Collection lModules = new ArrayList();
+ // Go through web applications
+ Iterator i = pDeployment.webModules.iterator();
+ Collection lItems = new ArrayList();
+ while( i.hasNext() ) {
+ Deployment.Module lModule = (Deployment.Module) i.next();
+ lItems.add( lModule.webContext );
+ }
+ // Add Web Module
+ lModules.add(
+ new Module(
+"WebModule:FixeLater",
+"DD:FixeLater",
+lItems
+ )
+ );
+ // Go through ejb applications
+ i = pDeployment.webModules.iterator();
+ lItems = new ArrayList();
+ while( i.hasNext() ) {
+ Deployment.Module lModule = (Deployment.Module) i.next();
+ lItems.add( ( (URL) lModule.localUrls.firstElement() ).getFile() );
+ }
+ // Add EJB Module
+ lModules.add(
+ new Module(
+"EJBModule:FixeLater",
+"DD:FixeLater",
+lItems
+ )
+ );
+ // Create Applications
+ return new Application(
+ pId,
+ "DD:FixeLater",
+ lModules
+ );
}
}
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jboss/src/main/org/jboss/jmx/client RMIClientConnectorImpl.java
User: schaefera
Date: 01/05/14 11:39:27
Modified:src/main/org/jboss/jmx/client RMIClientConnectorImpl.java
Log:
Implementation of the 1. draft for the JBoss management class in the
J2EEDeployer to figure out what applications are deployed.
Revision ChangesPath
1.6 +1 -0 jboss/src/main/org/jboss/jmx/client/RMIClientConnectorImpl.java
Index: RMIClientConnectorImpl.java
===
RCS file:
/cvsroot/jboss/jboss/src/main/org/jboss/jmx/client/RMIClientConnectorImpl.java,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- RMIClientConnectorImpl.java 2000/12/11 16:11:54 1.5
+++ RMIClientConnectorImpl.java 2001/05/14 18:39:27 1.6
@@ -486,6 +486,7 @@
}
catch( RemoteException re ) {
//AS Not a good style but for now
+ re.printStackTrace();
return null;
}
}
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jboss/src/etc/conf/default jboss.jcml
User: schaefera Date: 01/05/14 11:39:26 Modified:src/etc/conf/default jboss.jcml Log: Implementation of the 1. draft for the JBoss management class in the J2EEDeployer to figure out what applications are deployed. Revision ChangesPath 1.31 +1 -1 jboss/src/etc/conf/default/jboss.jcml Index: jboss.jcml === RCS file: /cvsroot/jboss/jboss/src/etc/conf/default/jboss.jcml,v retrieving revision 1.30 retrieving revision 1.31 diff -u -r1.30 -r1.31 --- jboss.jcml2001/05/13 03:34:20 1.30 +++ jboss.jcml2001/05/14 18:39:26 1.31 @@ -391,7 +391,7 @@ - +
[JBoss-dev] CVS update: jboss/src/main/org/jboss/mgt Application.java Module.java ServerDataCollector.java ServerDataCollectorMBean.java JBossApplication.java JBossModule.java JBossServer.java JBossServerMBean.java
User: schaefera
Date: 01/05/14 11:39:27
Added: src/main/org/jboss/mgt Application.java Module.java
ServerDataCollector.java
ServerDataCollectorMBean.java
Removed: src/main/org/jboss/mgt JBossApplication.java
JBossModule.java JBossServer.java
JBossServerMBean.java
Log:
Implementation of the 1. draft for the JBoss management class in the
J2EEDeployer to figure out what applications are deployed.
Revision ChangesPath
1.1 jboss/src/main/org/jboss/mgt/Application.java
Index: Application.java
===
/*
* JBoss, the OpenSource EJB server
*
* Distributable under LGPL license.
* See terms of license at gnu.org.
*/
package org.jboss.mgt;
import java.io.Serializable;
import java.util.ArrayList;
import java.util.Collection;
/**
* Contains the management information about
* a deployed applications.
*
* @author Marc Fleury
**/
public class Application
implements Serializable
{
// -
// Members
// -
private String mApplicationId;
private String mDeploymentDescriptor;
private Collection mModules;
// -
// Constructors
// -
/**
* @param pApplicationId Id of these Application which must be unique within
* the node/server.
* @param pDeploymentDescriptor Deployment Descriptor of this application
* which maybe is not set.
* @param pModules Collection of modules deployed with the given application
* each item is of type {@link org.jboss.mgt.JBossModule
* JBossModule}.
**/
public Application(
String pApplicationId,
String pDeploymentDescriptor,
Collection pModules
) {
mApplicationId = pApplicationId;
setDeploymentDescriptor( pDeploymentDescriptor );
setModules( pModules );
}
// -
// Properties (Getters/Setters)
// -
/**
* @return Id of these Application
**/
public String getId() {
return mApplicationId;
}
/**
* Returns the deployment descriptor
*
* @return Deployment Descriptor of this application which maybe is not set.
**/
public String getDeploymentDescriptor() {
return mDeploymentDescriptor;
}
/**
* Sets the deployment descriptor
*
* @param pDeploymentDescriptor Deployment Descriptor of this application
* which maybe is not set.
**/
public void setDeploymentDescriptor( String pDeploymentDescriptor ) {
mDeploymentDescriptor = pDeploymentDescriptor;
}
/**
* @return Collection of Modules deployed with this application. Each
* item is of type {@link org.jboss.mgt.JBossModule JBossModule}.
**/
public Collection getModules() {
return mModules;
}
/**
* Sets a new list of modules
*
* @param pModules New list of modules to be set
**/
public void setModules( Collection pModules ) {
if( pModules == null ) {
// If null is passed then keep the list
mModules = new ArrayList();
}
else {
mModules = pModules;
}
}
public String toString() {
return "Application [ " + getId() +
", deployment descriptor : " + getDeploymentDescriptor() +
", modules: " + getModules() + " ]";
}
}
1.1 jboss/src/main/org/jboss/mgt/Module.java
Index: Module.java
===
/*
* JBoss, the OpenSource EJB server
*
* Distributable under LGPL license.
* See terms of license at gnu.org.
*/
package org.jboss.mgt;
import java.io.Serializable;
import java.util.Collection;
/**
* Contains the management information about
* a deployed applications.
*
* @author Marc Fleury
**/
public class Module
implements Serializable
{
// -
// Members
// -
private String mModuleId;
private String mDeploymentDescriptor;
private
[JBoss-dev] Tis quiet on JBoss-dev
:) so scott stark and myself are giving training in Atlanta and the list is dead? ah come on, it will make us feel like without us there is nothing going us but the rent. marc _ Marc Fleury, Ph.D [EMAIL PROTECTED] _ ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss daily test results
= ==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS= = JBoss daily test results SUMMARY Number of tests run: 67 Successful tests: 61 Errors:2 Failures: 4 DETAILS OF ERRORS Suite: org.jboss.test.cts.test.AllJUnitTests Test:testRemoveSessionObject Type:failure Exception: junit.framework.AssertionFailedError Message: [EJB 1.1, p42, section 5.3.2] Expected 'RemoveException' when remove-ing a session object, detail:java.rmi.ServerException: RemoteException occurred in server thread; nested exception is: javax.transaction.TransactionRolledbackException: Could not activate; nested exception is: java.io.FileNotFoundException: [EMAIL PROTECTED] (No such file or directory); nested exception is: java.rmi.NoSuchObjectException: Could not activate; nested exception is: java.io.FileNotFoundException: [EMAIL PROTECTED] (No such file or directory) Stack Trace: junit.framework.AssertionFailedError: [EJB 1.1, p42, section 5.3.2] Expected 'RemoveException' when remove-ing a session object, detail:java.rmi.ServerException: RemoteException occurred in server thread; nested exception is: javax.transaction.TransactionRolledbackException: Could not activate; nested exception is: java.io.FileNotFoundException: [EMAIL PROTECTED] (No such file or directory); nested exception is: java.rmi.NoSuchObjectException: Could not activate; nested exception is: java.io.FileNotFoundException: [EMAIL PROTECTED] (No such file or directory) at junit.framework.Assert.fail(Assert.java:143) at org.jboss.test.cts.test.StatefulSessionTest.testRemoveSessionObject(StatefulSessionTest.java:188) at java.lang.reflect.Method.invoke(Native Method) at junit.framework.TestCase.runTest(TestCase.java:155) at junit.framework.TestCase.runBare(TestCase.java:129) at junit.framework.TestResult$1.protect(TestResult.java:100) at junit.framework.TestResult.runProtected(TestResult.java:117) at junit.framework.TestResult.run(TestResult.java:103) at junit.framework.TestCase.run(TestCase.java:120) at junit.framework.TestSuite.run(TestSuite.java:144) at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:202) at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:326) - Suite: org.jboss.test.cts.test.AllJUnitTests Test:testProbeBeanContext Type:failure Exception: junit.framework.AssertionFailedError Message: Caught an unknown exception in testProbeBeanContex Stack Trace: junit.framework.AssertionFailedError: Caught an unknown exception in testProbeBeanContex at junit.framework.Assert.fail(Assert.java:143) at org.jboss.test.cts.test.StatefulSessionTest.testProbeBeanContext(StatefulSessionTest.java:467) at java.lang.reflect.Method.invoke(Native Method) at junit.framework.TestCase.runTest(TestCase.java:155) at junit.framework.TestCase.runBare(TestCase.java:129) at junit.framework.TestResult$1.protect(TestResult.java:100) at junit.framework.TestResult.runProtected(TestResult.java:117) at junit.framework.TestResult.run(TestResult.java:103) at junit.framework.TestCase.run(TestCase.java:120) at junit.framework.TestSuite.run(TestSuite.java:144) at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:202) at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:326) - Suite: org.jboss.test.cts.test.AllJUnitTests Test:testEjbRemove Type:failure Exception: junit.framework.AssertionFailedError Message: Got Exception: expecting NoSuchObjectExceptionjava.rmi.ServerException: RemoteException occurred in server thread; nested exception is: javax.transaction.TransactionRolledbackException: Instance 007 not found in database.; nested exception is: javax.ejb.NoSuchEntityException: Instance 007 not found in database. Stack Trace: junit.framework.AssertionFailedError: Got Exception: expecting NoSuchObjectExceptionjava.rmi.ServerException: RemoteException occurred in server thread; nested exception is: javax.transaction.TransactionRolledbackException: Instance 007 not found in database.; nested exception is: javax.ejb.NoSuchEntityException: Instance 007 not found in database. at junit.framework.Assert.fail(Assert.java:143) at org.jboss.test.cts.test.BmpTest.testEjbRemove(BmpTest.java:224) at java.lang.reflect.Method
[JBoss-dev] [ jboss-Patches-424075 ] HOWTO - Using Sybase with JBoss
Patches item #424075, was updated on 2001-05-14 16:11 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=376687&aid=424075&group_id=22866 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Jason Wells (electrocute) Assigned to: Nobody/Anonymous (nobody) Summary: HOWTO - Using Sybase with JBoss Initial Comment: >From reading the JBoss-Users list, I understand this is a good way to submit documentation. If it's not, just let me know. This HOWTO walks through the process of setting up JBoss so that (for example) CMP entity beans may go against entities in a Sybase database. It is based on (and adapted from) the "Using MS SQL Server with JBoss" HOWTO. They are very similar, but I found there are enough Sybase-related land mines to warrant specific documentation. Enjoy, Jason Wells -- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=376687&aid=424075&group_id=22866 ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-424059 ] CMP Field of type Object Fails
Bugs item #424059, was updated on 2001-05-14 15:32 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=376685&aid=424059&group_id=22866 Category: JBossCMP Group: v2.2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Matthew Cooper (matthewcooper) Assigned to: Nobody/Anonymous (nobody) Summary: CMP Field of type Object Fails Initial Comment: I have a CMP managed entity with some cmp fields, one of which is java.lang.Object. After persisting a value in this field (it happens to be a String) and bouncing jboss to make it re-load from the db, I get back an instance of java.rmi.MarshalledObject. I've looked at the code in org.jboss.ejb.plugins.jaws.jdbc.JDBCCommand and this is what I think is happening... The method: setParameter(PreparedStatement stmt, int idx, int jdbcType, Object value) determines this is a binary type and wraps it in a MashalledObject and serializes it to a byte arry before writign that to the db. The method: getResultObject(ResultSet rs, int idx, Class destination) Finds no special methods for retriving the destination type (which is java.lang.Object in my case) and so calls rs.getObject(idx). The code... if(destination.isAssignableFrom(result.getClass())) return result; then says is the result an instanec of my destination type (java.lang.Object) which is always true in this case. hence it doesn't do any unwrapping, etc. danch suggested I raise this as a bug - and that I try a patch - I may do that later this week... -- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=376685&aid=424059&group_id=22866 ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Open letter: ZOAP is dead, long live JBossSOAP!
Hi Jung, I've been subscribed for a while in the jboss-development list, and I'm interested in helping in its development, but I haven't really get involved on it... I've 2 years of experience in java doing middleware stuff, I have also experience used Castor for a XML based server. I'd like to get involved in the SOAP support for JBoss (right now I have some spare time...), so if please count for this development... "Jung , Dr. Christoph" wrote: > Dear fellow JBoss developers, dear JBoss board, dear JBoss users striving > for SOAP-support in their favorite bean container! > > As the initiator of the ZOAP module, I must excuse for making myself quite > scare to the JBoss-lists for the last months (this was not only because of > having huge ssh-problems accessing sourceforge) - hereby leaving many people > puzzled about the state of the project. My professional engagement (as you > all have experienced: first your have to earn bread, then the butter) does > not allow me anymore to operate as the single architect, developer, > documentation writer and (perhaps the most important role, from what I > learned during the past year) supporter of the module. > > I have to admit that this typical OS dead-end situation has been my own > fault: I made a lot of mistakes when it comes to finding the right way of > attaching to existing code, sharing the results, engaging people, > advertising the project, etc. My only excuse is that I was coming straight > from university/research at that time and I had to learn a lot about > "real-world" programming practices in general and engaging into Open Source > in particular ... > > Maybe also the point in time (mid-2000) when we were first propagating SOAP > for EJBs was rather early such that > - there was not yet any broad need, and > - there was no fixed and accepted standard to which you can commit > to > (see the Apache-MS-SOAP-interoperablity thread that is relevant > until today!). > > Hence, the decision to write a proprietary and generic (de-)serialisation > framework was motivated by IBM´s/Apache´s neglectance of DOM-impasses, > XML-Schema and most of EJB. This decision has helped me to deepen my > understanding of which added-value purist XML-middleware could introduce > into todays business platforms (and we have a working system based on that > ideas here at infor). But this has in turn cost a lot of resources and, > finally, acceptance in the community. > > IMHO (and I refer to the latest contributions to the mailing-lists as > examples) this situation has changed now. The role of XML in business > frameworks has been widely recognized and emphasised. The need for our > beloved JBoss beans to interoperate with XML-enabled Web-applications is > definitely there. And the SOAP standard has now a quite accepted and fixed > basis; Open Source implementations such as Apache and IdooXoap are heading > towards practicability. Thus, it would be silly to neglect SOAP in a > first-class project such as JBoss and it would be even more silly if an > existing, but more or less closed module, such as ZOAP, would prevent doing > a first-class integration of SOAP into JBoss. > > After having put enough ashes onto my head, here is now a proposal how to > proceed: > > - Let´s face the dead of the ZOAP (code). > - Let´s find out who is still interested and willing to > contribute to the issue of integration XML/SOAP into jBoss. > - Let´s discuss the prime needs of the community with respect to > this topic. > - Let´s initiate the "real" JBossSOAP project as a properly > structured contrib-module which takes over > Apache/Axis/whateverCodeIsMostAppropriate in a realistic setting/timeframe > with several architects/developers, > supporters, example and documentation writers, and testers. > > - first a plain but most useful > invocationhandler-invoker-integration with servlets using the pure > Apache/.../... > (the ZOAP code and existing knowledge on the JBoss-lists > could certainly give some useful hints for reaching > this in a couple of weeks) > - later we could think about integrating Castor for doing > more advanced mapping/serialisation (here, the ZOAP mapping > idea could survive, but in a more standardised setting) > - MDB-support > - ... > > I would like to ask the board to evaluate and comment my email/proposal. If > we somehow agree on that issue being important and promising, I would ASAP > care about updating the web-presentation, inform the community, etc. > > I would like to ask interested developers that have already done or that are > about to do some Apache-SOAP/whatever-SOAP integration > to join this effort as I am convinced that sharing knowledge and code will > pay off in the long run. If there are enough people committed, > we will agree on an
[JBoss-dev] [ jboss-Bugs-423986 ] Exception on Server Startup
Bugs item #423986, was updated on 2001-05-14 10:31 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=376685&aid=423986&group_id=22866 Category: JBossServer Group: v2.2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Exception on Server Startup Initial Comment: Maybe a bug or misconfiguration: Platform (W2000 Professional) jdk 1.3 Output: C:\JBoss-2.2.1\bin>java -version java version "1.3.0" Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0-C) Java HotSpot(TM) Client VM (build 1.3.0-C, mixed mode) C:\JBoss-2.2.1\bin>run.bat JBOSS_CLASSPATH=;run.jar;../lib/crimson.jar jboss.home = C:\JBoss-2.2.1 Using configuration "default" [Info] Java version: 1.3.0,Sun Microsystems Inc. [Info] Java VM: Java HotSpot(TM) Client VM 1.3.0-C,Sun Microsystems Inc. [Info] System: Windows 2000 5.0,x86 [Shutdown] Shutdown hook added [Service Control] Registered with server Exception in thread "main" [Default] javax.xml.parsers.FactoryConfigurationErro : org.apache.crimson.jaxp.DocumentBuilderFactoryImpl [Default] at javax.xml.parsers.DocumentBuilderFactory.newInstance(Documen BuilderFactory.java:80) [Default] at org.jboss.Main.(Main.java:192) [Default] at org.jboss.Main$1.run(Main.java:107) [Default] at java.security.AccessController.doPrivileged(Native Method) [Default] at org.jboss.Main.main(Main.java:103) [Default] Shutting down [Service Control] Stopping 0 MBeans [Service Control] Stopped 0 services [Service Control] Destroying 0 MBeans [Service Control] Destroyed 0 services [Default] Shutdown complete Presione una tecla para continuar . . . C:\JBoss-2.2.1\bin> -- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=376685&aid=423986&group_id=22866 ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] RE: Welcome to the "Jboss-development" mailing list
Isidoro Fernández Díaz mailto:[EMAIL PROTECTED] Software Engineer TELENIUM, The New Millennium Telecom Company Agustín de Foxá, 25, plta. 13 28036 MADRID Tel. +34 91 315 85 62 Fax +34 91 315 63 37 http://www.telenium.es -Mensaje original- De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]En nombre de [EMAIL PROTECTED] Enviado el: lunes 14 de mayo de 2001 16:59 Para: [EMAIL PROTECTED] Asunto: Welcome to the "Jboss-development" mailing list Welcome to the [EMAIL PROTECTED] mailing list! To post to this list, send your email to: [EMAIL PROTECTED] General information about the mailing list is at: http://lists.sourceforge.net/lists/listinfo/jboss-development If you ever want to unsubscribe or change your options (eg, switch to or from digest mode, change your password, etc.), visit your subscription page at: http://lists.sourceforge.net/lists/options/jboss-development/ifernandez%40te lenium.es You can also make such adjustments via email by sending a message to: [EMAIL PROTECTED] with the word `help' in the subject or body (don't include the quotes), and you will get back a message with instructions. You must know your password to change your options (including changing the password, itself) or to unsubscribe. It is: golondrina If you forget your password, don't worry, you will receive a monthly reminder telling you what all your lists.sourceforge.net mailing list passwords are, and how to unsubscribe or change your options. There is also a button on your options page that will email your current password to you. You may also have your password mailed to you automatically off of the Web page noted above. ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Open letter: ZOAP is dead, long live JBossSOAP!
Dear fellow JBoss developers, dear JBoss board, dear JBoss users striving for SOAP-support in their favorite bean container! As the initiator of the ZOAP module, I must excuse for making myself quite scare to the JBoss-lists for the last months (this was not only because of having huge ssh-problems accessing sourceforge) - hereby leaving many people puzzled about the state of the project. My professional engagement (as you all have experienced: first your have to earn bread, then the butter) does not allow me anymore to operate as the single architect, developer, documentation writer and (perhaps the most important role, from what I learned during the past year) supporter of the module. I have to admit that this typical OS dead-end situation has been my own fault: I made a lot of mistakes when it comes to finding the right way of attaching to existing code, sharing the results, engaging people, advertising the project, etc. My only excuse is that I was coming straight from university/research at that time and I had to learn a lot about "real-world" programming practices in general and engaging into Open Source in particular ... Maybe also the point in time (mid-2000) when we were first propagating SOAP for EJBs was rather early such that - there was not yet any broad need, and - there was no fixed and accepted standard to which you can commit to (see the Apache-MS-SOAP-interoperablity thread that is relevant until today!). Hence, the decision to write a proprietary and generic (de-)serialisation framework was motivated by IBM´s/Apache´s neglectance of DOM-impasses, XML-Schema and most of EJB. This decision has helped me to deepen my understanding of which added-value purist XML-middleware could introduce into todays business platforms (and we have a working system based on that ideas here at infor). But this has in turn cost a lot of resources and, finally, acceptance in the community. IMHO (and I refer to the latest contributions to the mailing-lists as examples) this situation has changed now. The role of XML in business frameworks has been widely recognized and emphasised. The need for our beloved JBoss beans to interoperate with XML-enabled Web-applications is definitely there. And the SOAP standard has now a quite accepted and fixed basis; Open Source implementations such as Apache and IdooXoap are heading towards practicability. Thus, it would be silly to neglect SOAP in a first-class project such as JBoss and it would be even more silly if an existing, but more or less closed module, such as ZOAP, would prevent doing a first-class integration of SOAP into JBoss. After having put enough ashes onto my head, here is now a proposal how to proceed: - Let´s face the dead of the ZOAP (code). - Let´s find out who is still interested and willing to contribute to the issue of integration XML/SOAP into jBoss. - Let´s discuss the prime needs of the community with respect to this topic. - Let´s initiate the "real" JBossSOAP project as a properly structured contrib-module which takes over Apache/Axis/whateverCodeIsMostAppropriate in a realistic setting/timeframe with several architects/developers, supporters, example and documentation writers, and testers. - first a plain but most useful invocationhandler-invoker-integration with servlets using the pure Apache/.../... (the ZOAP code and existing knowledge on the JBoss-lists could certainly give some useful hints for reaching this in a couple of weeks) - later we could think about integrating Castor for doing more advanced mapping/serialisation (here, the ZOAP mapping idea could survive, but in a more standardised setting) - MDB-support - ... I would like to ask the board to evaluate and comment my email/proposal. If we somehow agree on that issue being important and promising, I would ASAP care about updating the web-presentation, inform the community, etc. I would like to ask interested developers that have already done or that are about to do some Apache-SOAP/whatever-SOAP integration to join this effort as I am convinced that sharing knowledge and code will pay off in the long run. If there are enough people committed, we will agree on an architecture (first cut should be quite straightforward) and start we will committing source and doco ;-) And I would like to ask anyone interested in this topic to share experiences and needs such that we will not run into a dead-end again. Peace, Dr. Christoph G. Jung Software Engineer infor: business solutions AG http://www.infor.de/ mailto:[EMAIL PROTECTED] ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
