[jBPM] New message: "Creating new Configuration deletes data in JBPM_DEPLOY* tables (4.3)"
by Ryan Bartlett
User development,
A new message was posted in the thread "Creating new Configuration deletes data in JBPM_DEPLOY* tables (4.3)":
http://community.jboss.org/message/531274#531274
Author : Ryan Bartlett
Profile : http://community.jboss.org/people/RyanLBart
Message:
--------------------------------------------------------------
Everytime I execute the code below, my JBPM4 database is wiped clean (deployment tables and history tables). Originally, I thought my probelm was that I was deploying the same *.jdpl.xml files time and time again (basically everytime my service started), so I modified my code to only deploy the *.jdpl.xml files if a flag is set. Unfortunately, that didn't solve my problem. It turns out, that my data is still deleted, and it is deleted when I build the process engine. If I don't deploy and *.jdpl.xml files, the database is empty. Deploying the *.jdpl.xml files everytime isn't an option either as it deletes all of the data previosly in the history tables. So I guess I really have two questions.... 1) why does building a process engine delete my data? is there another way to get a process enging? and 2). what is the best practice in terms of deploying *.jdpl.xml files? I am assuming that they should only be deployed when they have been modified.
Thanks in advance!
*protected* *final* ProcessEngine getProcessEngine(String fileName, String fileLocation) *throws* Exception{
Configuration configuration =
*new* Configuration(); configuration.setFile(getFile(fileName, fileLocation));
* return* configuration.buildProcessEngine();}
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/531274#531274
16 years, 3 months
[JBoss Web Services] New message: "JBoss 5.1.0 + Java6 + ant = 'setProperty must be overridden' error"
by aodhan hoffman
User development,
A new message was posted in the thread "JBoss 5.1.0 + Java6 + ant = 'setProperty must be overridden' error":
http://community.jboss.org/message/531246#531246
Author : aodhan hoffman
Profile : http://community.jboss.org/people/gryffin
Message:
--------------------------------------------------------------
I've read the recent discussions on this topic, but I have not been able to overcome the 'setProperty' error by adding the the JBossws native jars to the lib/endorsed directory and adding them to the client's classpath.
Specifically, I use ant to manage my deployment states and run the client for testing. I can build and deploy the web service war file just fine, and the JBoss server deploys it handily. When I run the /client/ I get into trouble.
I installed the JBoss 5.1.0 GA JDK6 version and am running it on WindowsXP.
Here's my run-client ant target:
<target name="run-client" >
<java classname="com.nmt.nls.api.client.NlsApiClient" fork="true">
<classpath>
<pathelement location="C:/jboss-5.1.0.GA/lib/endorsed/jbossws-native-jaxrpc.jar"/>
<pathelement location="C:/jboss-5.1.0.GA/lib/endorsed/jbossws-native-jaxws.jar"/>
<pathelement location="C:/jboss-5.1.0.GA/lib/endorsed/jbossws-native-jaxws-ext.jar"/>
<pathelement location="C:/jboss-5.1.0.GA/lib/endorsed/jbossws-native-saaj.jar"/>
<pathelement location="C:/jboss-5.1.0.GA/lib/endorsed/resolver.jar"/>
<pathelement location="C:/jboss-5.1.0.GA/lib/endorsed/serializer.jar"/>
<pathelement location="C:/jboss-5.1.0.GA/lib/endorsed/stax-api.jar"/>
<pathelement location="C:/jboss-5.1.0.GA/lib/endorsed/xalan.jar"/>
<pathelement location="C:/jboss-5.1.0.GA/lib/endorsed/xercesImpl.jar"/>
<pathelement location="C:/jboss-5.1.0.GA/lib/endorsed/activation.jar"/>
<pathelement location="C:/jboss-5.1.0.GA/lib/endorsed/jaxb-api.jar"/>
<pathelement location="C:/jboss-5.1.0.GA/client/jboss-logging-log4j.jar"/>
<pathelement location="C:/jboss-5.1.0.GA/client/jboss-logging-spi.jar"/>
<pathelement location="C:/jboss-5.1.0.GA/client/jboss-client.jar"/>
<pathelement location="C:/jboss-5.1.0.GA/client/jboss-common-core.jar"/>
<pathelement location="C:/jboss-5.1.0.GA/client/jboss-common-client.jar"/>
<pathelement location="C:/jboss-5.1.0.GA/client/jbossws-spi.jar"/>
<pathelement location="C:/jboss-5.1.0.GA/client/jbossws-native-core.jar"/>
<pathelement location="C:/jboss-5.1.0.GA/client/jbossws-native-client.jar"/>
<pathelement location="C:/jboss-5.1.0.GA/client/jaxb-impl.jar"/>
<pathelement location="C:/jboss-5.1.0.GA/client/jboss-xml-binding.jar"/>
<pathelement location="C:/jboss-5.1.0.GA/client/wstx.jar"/>
<pathelement location="C:/jboss-5.1.0.GA/client/jboss-logging-jdk.jar"/>
<pathelement location="C:/jboss-5.1.0.GA/client/jboss-logging-spi.jar"/>
<pathelement location="C:/jboss-5.1.0.GA/client/jbossws-common.jar"/>
<pathelement location="C:/jboss-5.1.0.GA/client/wsdl4j.jar"/>
<pathelement location="C:/jboss-5.1.0.GA/client/mail.jar"/>
<pathelement location="C:/jboss-5.1.0.GA/client/policy.jar"/>
<pathelement location="C:/jboss-5.1.0.GA/client/commons-logging.jar"/>
<pathelement location="C:/jboss-5.1.0.GA/client/javassist.jar"/>
<pathelement location="C:/jboss-5.1.0.GA/client/jboss-remoting.jar"/>
<pathelement location="${basedir}\bin"/>
<pathelement location="${basedir}\com.nmt.nls.api.client"/>
<pathelement location="${basedir}\bin\com\nlsClient.properties"/>
</classpath>
</java>
</target>
And here is the stack trace when I run this target:
>ant run-client
Buildfile: build.xml
run-client:
[java] Getting associations for TestingAsset/NLS_Core_Team
[java] Exception in thread "main" javax.xml.ws.WebServiceException: java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage
[java] at org.jboss.ws.core.jaxws.client.ClientImpl.handleRemoteException(ClientImpl.java:396)
[java] at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:302)
[java] at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:170)
[java] at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:150)
[java] at $Proxy15.assetAssociationGet(Unknown Source)
[java] at com.nmt.nls.api.client.NlsApiClient.getAssociations(NlsApiClient.java:69)
[java] at com.nmt.nls.api.client.NlsApiClient.main(NlsApiClient.java:58)
[java] Caused by: java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage
[java] at javax.xml.soap.SOAPMessage.setProperty(SOAPMessage.java:445)
[java] at org.jboss.ws.core.soap.SOAPMessageImpl.<init>(SOAPMessageImpl.java:87)
[java] at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:169)
[java] at org.jboss.ws.core.CommonSOAP11Binding.createMessage(CommonSOAP11Binding.java:57)
[java] at org.jboss.ws.core.CommonSOAPBinding.bindRequestMessage(CommonSOAPBinding.java:157)
[java] at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:290)
[java] at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:290)
[java] ... 5 more
[java] Java Result: 1
BUILD SUCCESSFUL
Total time: 1 second
I assume I'm either not using ant correctly, or not including the correct jars. I'd appreciate some insight from someone who has some experience dealing with this incompatibility. Thanks!
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/531246#531246
16 years, 3 months
[JCA] New message: "Re: JCA / JNDI / ActiveMQ"
by Kelly Wang
User development,
A new message was posted in the thread "JCA / JNDI / ActiveMQ":
http://community.jboss.org/message/531225#531225
Author : Kelly Wang
Profile : http://community.jboss.org/people/kelly.wang@sita.aero
Message:
--------------------------------------------------------------
Hello Alexander,
Have you got your answer for this question?
Have you try to use ActiveMQ resource adaptor to connect to ActiveMQ running separately from JBoss 5.1? I am keep getting the following runtime exception when start up JBoss 5.1 instance, the same configruation works just fine in JBoss 4.2.2GA:
Caused by: java.lang.RuntimeException: Unable to choose messagingType interface for MDB AuditService from []
at org.jboss.ejb3.mdb.MDB.getMessagingType(MDB.java:76)
at org.jboss.ejb3.mdb.MDB.resolveBusinessInterfaces(MDB.java:132)
at org.jboss.ejb3.EJBContainer.instantiated(EJBContainer.java:1564)
at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:726)
Also, were you able to use JNDI name for inbound queue with ActiveMQ? I have to specify the physical Queue name inside my MDB for inbound message, but prefer to use jndi name in my code and configure the jndi name in adminobject inside activemq-jms-ds.xml file. How did you get around tis?
thanks
Kelly
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/531225#531225
16 years, 3 months
[JBoss Microcontainer Development] New message: "Updating ClassPool version at JBoss Deployers project"
by Flavia Rainone
User development,
A new message was posted in the thread "Updating ClassPool version at JBoss Deployers project":
http://community.jboss.org/message/531223#531223
Author : Flavia Rainone
Profile : http://community.jboss.org/people/flavia.rainone@jboss.com
Message:
--------------------------------------------------------------
I'm updating the version of classpool to 2.0.0.Alpha4 in jboss-deployers:
https://jira.jboss.org/jira/browse/JBDEPLOY-250
As I told Ales in a private e-mail, updating the classpool version raised new requirements for the classpool tests to work (in the jboss-deployers project).
First of all, I need to set a FilteredClassPool as the SystemClassPool so that the excluded classes can be filtered out. This should be set up by a test deleagte, but, to create a delegate, I needed to break a few of the design conventions in the tests:
- my test delegate must be a subclass of BootstrapDeployersTestDelegate, but it ended up containing duplicate code:
ClassFilter classFilter = new ClassFilter()
{
// duplicate code
};
defaultClassPool = new FilteredClassPool(AbstractClassPoolFactory.getDefaultClassPool(), classFilter);
I need to use the same classFilter that is used by BootstrapDeployersTestDelegate. However, the way the code is right now, I can't have that, so I ended up duplicating this code
- my test delegate needs to be defined for only ClassPoolTestCase and JavassistTypeInfoTestCase, but not for IntrospectionTypeInfoTestCase.
Hence, I cannot apply it by implementing a getDelegate() method at ReflectTest, which would be the right place if all subclasses needed the delegate. So, I ended up adding it to ClassPoolTest and to JavassistTypeInfoTestCase. But JavassistTITC is not abstract, and, for what I can tell, it is a design convention in the project that this method should be added always to an abstract test class. On the other hand, I'm not sure if I should add a JavassistTypeInfoTest class just for that.
- following the conventions, my TestDelegate should be named after the Test class. So, if I was applying it to ReflectTest, it would be called ReflectTestDelegate. But as I'm applying it to two test classes, I don't know what to name it? I temporarily named it JavassistTestDelegate.
FYI, another change that I'm commiting is that, with VFS3 new URL format (using file://), I will also need a FilteredIsLocalResourcePlugin, so that the classes in the excluded packages can be filtered out before the URL reaches the ClassLoader level.
I'll be committing these changes for Ales to take a look and decide what is the best way of working around these design issues.
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/531223#531223
16 years, 3 months
