[JBoss jBPM] - Re: deep copy of a process Instance
by meeï¼ jboss
Hi Ronald
we implement the installation of software by jbpm on multiple stages.
First the User defines which installation workflows (and subworkflows) he wants to be executed.
According to the selected workflows he has to define the required installation attributes which will be made persistent in the process instance.
Then we execute the workflow on multiple stages (development, Production, ...)
In order that the user does not allways have to fill in similar data, we want to store and load allready executed ProcessInstances.
Therefore we wanted to deep copy a ProcessInstance, change some simple attributes and execute it again.
But questioning deep copies might be a good idea.
So I as a rookie I see two possibilities:
a) deepcopy of ProcessInstance
- ProcessInstances of subworkflows should be included
- copy the variables
(Cool if JBpm would support this ...)
b) create new ProcessInstances programmaticially
- copy the variables
In my opinion there is a need to execute an allready executed Workflow again. But without modifying the original Workflow.
Do you have another hint to solve such a requirement?
Thanks,
Andrea
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4064580#4064580
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4064580
18Â years, 12Â months
[JBoss Seam] - Re: Seam 2 beta and JPA
by jasondlee
I have removed the reference to the Hibernate persistence provider in my persistence.xml. Now I get these two errors when I deploy:
Error in allocating a connection. Cause: Connection could not be allocated because: java.net.ConnectException : Error opening socket to server localhost on port 1527 with message : Connection refused: no further information;_RequestID=9a3c9def-0d6d-4b07-9ebf-4884caec03cf;|RAR5114 : Error allocating connection : [Error in allocating a connection. Cause: Connection could not be allocated because: java.net.ConnectException : Error opening socket to server localhost on port 1527 with message : Connection refused: no further information]
Exception sending context initialized event to listener instance of class org.jboss.seam.servlet.SeamListener java.lang.NullPointerException
| at oracle.toplink.essentials.ejb.cmp3.EntityManagerFactoryProvider.createEntityManagerFactory(EntityManagerFactoryProvider.java:120)
| at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:83)
| at org.jboss.seam.persistence.EntityManagerFactory.startup(EntityManagerFactory.java:72)
If I had to guess, I'd say the first error is due to the Seam stuff trying to connect to a JNDI server, but I have no idea on the second. I guess I'm just going to have to revert to Spring-managed EMs for the time being, which is a pity, but I'm running out of time. :|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4064579#4064579
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4064579
18Â years, 12Â months
[JBoss Seam] - Batch process with seam: what is the best approach?
by titou09
We have an online application build around seam, POJOs and hibernate.
Our business seam components ("managers" + "model" classes) are isolated into a separate jar file (common.jar), the "view controler" seam components (aka "backing beans") are directly held into the war module, the war module calling the classes into the common.jar module.
We have the need for batch processes, ie processesthat will run outside any web/jee container, with a standard j2se jdk, from a plain java class, possibly running for hours. Those processes will use the seam common components from the common.jar file.
The high level algorithm is :
| - bootstrap the seam engine
| - for each business item to process (maybe tens of thousand or more...):
| - begin transaction
| - do some business stuff that update the database
| - commit
| - shutdown the seam engine
|
What is the best way to do that with seam? Is it possible to do this without instanciating or faking a web container?, ie without having in the batch classpath, jars like "servlet.jar" eand "j2ee.jar"? or something like the jboss embedded container?
We looked at the SeamTest class as the "bootstrap" class, but SeamTest depends on javax.faces.*, javax.servlet.* and org.testng.* classes and is fully designed to test online components...
Or maybe the jboss embedded container is the way to go?
Thx for your guidance here.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4064578#4064578
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4064578
18Â years, 12Â months
[Persistence, JBoss/CMP, Hibernate, Database] - No Dialect mapping for JDBC type: 3
by nholbrook
I'm getting this error in jboss 4.0.4RC1. I've seen a few things on the net about this issue and the solutions haven't solved my problem. The field that is giving me a problem is a sum(int) sql call in jdbc. Why would it return a decimal type anyway? I have written my own InformixDialect which hasn't helped yet. The returning values are as follows...
07:43:50,057 INFO [STDOUT] Type : 3
07:43:50,057 INFO [STDOUT] Size : 32
07:43:50,057 INFO [STDOUT] Precision : 32
07:43:50,057 INFO [STDOUT] Scale : 0
I added all the following column types just to try to cover my bases
registerColumnType(Types.DECIMAL, "decimal");
registerColumnType(Types.DECIMAL, "number($p,$s)" );
registerColumnType(Types.DECIMAL, "numeric($p,$s)" );
registerColumnType(Types.DECIMAL, "decimal($p,$s)" );
I am still getting the same HibernateMappingException ("No Dialect mapping for JDBC type: 3") when I try to run the query.
The query looks like this..
SELECT product_grp, sum(volume)
where product_grp is a varchar and volume is an integer field.
The database is informix 7.3.
Any help or advice you could give would be greatly appreciated.
Thanks
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4064573#4064573
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4064573
18Â years, 12Â months
[EJB 3.0] - Re: RC6-PFD broke mappedBy and GenericGenerator workaround?
by arougthopher
We were having the same problem. We are using the 4.2.0 release, which includes Hibernate 3.2.1-GA. We started looking at some of the unit tests for hibernate annotations and found that something has changed between 3.2.1 and 3.3 releases. Looking at the org.hibernate.test.annotations.onotoone package, there are two classes, Party and PartyAffiliate.
The datamodel for this is such that Party has a unique partyId column, and PartyAffiliate uses the partyId for its PK as well, creating a PrimaryKeyJoinColumn reference.
In 3.2.1:
Party.java
| @Entity
| public class Party {
| @Id
| String partyId;
|
| @OneToOne(mappedBy = "party")
| PartyAffiliate partyAffiliate;
| }
|
PartyAffliate.java
| @Entity
| public class PartyAffiliate {
| @Id
| String partyId;
|
| @OneToOne
| @PrimaryKeyJoinColumn
| Party party;
|
| String affiliateName;
| }
|
However, in 3.3, we have:
Party.java
@Entity
| public class Party {
| @Id
| String partyId;
|
| @OneToOne
| @PrimaryKeyJoinColumn
| PartyAffiliate partyAffiliate;
| }
|
PartyAfiliate.java
@Entity
| public class PartyAffiliate {
| @Id
| String partyId;
|
| @OneToOne(mappedBy="partyAffiliate")
| Party party;
|
| String affiliateName;
| }
|
As you can see, the roles have changed. My question is, which is really right according to the spec?
We have a book here that implements their examples the way 3.2.1 did.
We have also used IntelliJ-IDEA to auto-gen the entity beans from the model, and it did so the way 3.2.1 did.
Jboss 4.2.0 contains hibernate annoations 3.2.1-ga, but it fails when running in the style of 3.2.1. If we flip like the 3.3 example does, it works
Either way we have it working, but, based on the fact that both a book and a third party have implemented it the way that the 3.2.1 examples have it, it seems that there might be a but in hibernate related to this.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4064572#4064572
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4064572
18Â years, 12Â months
[JBoss/Spring Integration] - Exploded deployment problem
by purplehaze9999
Hello *,
I use Spring 2.1 M2, JBoss 4.2
I can deploy JBoss-Spring example without errors.
I wrote simple example by my self and deployed it in tree separate archives
.spring, .jar and .war. It works.
But wenn I try to deploy an application in exploded directories then I get this error:
| 15:50:15,263 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=WarP-ServerDatasource' to JNDI name 'java:WarP-ServerDatasource'
| 15:50:15,278 INFO [EARDeployer] Init J2EE application: file:/D:/Programme/jboss-4.2.0.GA/server/default/deploy/WarP-Server.ear/
| 15:50:15,325 INFO [NamedXmlApplicationContext] Refreshing org.jboss.spring.factory.NamedXmlApplicationContext@80f252: display name [org.jboss.spring.factory.NamedXmlApplicationContext@80f252]; startup date [Mon Jul 16 15:50:15 CEST 2007]; root of context hierarchy
| 15:50:15,325 INFO [NamedXmlBeanDefinitionReader] Loading XML bean definitions from URL [file:/D:/Programme/jboss-4.2.0.GA/server/default/deploy/WarP-Server.ear/WarP-Server-dao.spring/META-INF/jboss-spring.xml]
| 15:50:15,372 INFO [NamedXmlBeanDefinitionParser] Bean names [description tag]: BeanFactory=(WarP-Server-DAO)
| 15:50:15,388 INFO [NamedXmlApplicationContext] Bean factory for application context [org.jboss.spring.factory.NamedXmlApplicationContext@80f252]: org.springframework.beans.factory.support.DefaultListableBeanFactory@c83cfd
| 15:50:15,403 INFO [NamedXmlApplicationContext] Bean 'org.springframework.context.config.internalAutowiredAnnotationProcessor' is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
| 15:50:15,403 INFO [NamedXmlApplicationContext] Bean 'org.springframework.context.config.internalRequiredAnnotationProcessor' is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
| 15:50:15,403 INFO [NamedXmlApplicationContext] Bean 'org.springframework.context.config.internalCommonAnnotationProcessor' is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
| 15:50:15,403 INFO [DefaultListableBeanFactory] Pre-instantiating singletons in org.springframework.beans.factory.support.DefaultListableBeanFactory@c83cfd: defining beans [org.springframework.context.config.internalAutowiredAnnotationProcessor,org.springframework.context.config.internalRequiredAnnotationProcessor,org.springframework.context.config.internalCommonAnnotationProcessor,stockDAOImpl,dataSource,sqlMapClient]; root of factory hierarchy
| 15:50:15,481 INFO [ApplicationContextLoaderImpl] Bean factory [WarP-Server-DAO] binded to local JNDI.
| 15:50:15,481 INFO [SpringApplicationContextDeployer] Deployed Spring: file:/D:/Programme/jboss-4.2.0.GA/server/default/deploy/WarP-Server.ear/WarP-Server-dao.spring/
| 15:50:15,513 INFO [JmxKernelAbstraction] creating wrapper delegate for: org.jboss.ejb3.stateless.StatelessContainer
| 15:50:15,513 INFO [JmxKernelAbstraction] installing MBean: jboss.j2ee:ear=WarP-Server.ear,jar=WarP-Server.jar,name=StockServiceEJB,service=EJB3 with dependencies:
| 15:50:15,528 INFO [EJBContainer] STARTED EJB: de.arvatoservices.warp.session.StockServiceEJB ejbName: StockServiceEJB
| 15:50:15,528 INFO [EJBContainer] STOPPED EJB: de.arvatoservices.warp.session.StockServiceEJB ejbName: StockServiceEJB
| 15:50:15,528 WARN [ServiceController] Problem starting service jboss.j2ee:ear=WarP-Server.ear,jar=WarP-Server.jar,name=StockServiceEJB,service=EJB3
| java.lang.ClassCastException: org.jboss.spring.factory.NamedXmlApplicationContext cannot be cast to javax.naming.Context
| at org.jboss.util.naming.Util.createSubcontext(Util.java:69)
| at org.jboss.util.naming.Util.rebind(Util.java:125)
| at org.jboss.util.naming.Util.rebind(Util.java:113)
| at org.jboss.ejb3.stateless.BaseStatelessProxyFactory.bindProxy(BaseStatelessProxyFactory.java:242)
| at org.jboss.ejb3.stateless.BaseStatelessProxyFactory.start(BaseStatelessProxyFactory.java:225)
| at org.jboss.ejb3.stateless.StatelessRemoteProxyFactory.start(StatelessRemoteProxyFactory.java:107)
| at org.jboss.ejb3.ProxyDeployer.start(ProxyDeployer.java:83)
| at org.jboss.ejb3.SessionContainer.start(SessionContainer.java:128)
| at org.jboss.ejb3.stateless.StatelessContainer.start(StatelessContainer.java:94)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
| at java.lang.reflect.Method.invoke(Unknown Source)
| at org.jboss.ejb3.ServiceDelegateWrapper.startService(ServiceDelegateWrapper.java:103)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
| at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
| at java.lang.reflect.Method.invoke(Unknown Source)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
| at $Proxy0.start(Unknown Source)
| at org.jboss.system.ServiceController.start(ServiceController.java:417)
| at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
| at java.lang.reflect.Method.invoke(Unknown Source)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
| at $Proxy104.start(Unknown Source)
| at org.jboss.ejb3.JmxKernelAbstraction.install(JmxKernelAbstraction.java:120)
| at org.jboss.ejb3.Ejb3Deployment.registerEJBContainer(Ejb3Deployment.java:297)
| at org.jboss.ejb3.Ejb3Deployment.start(Ejb3Deployment.java:344)
| at org.jboss.ejb3.Ejb3Module.startService(Ejb3Module.java:91)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
| at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
| at java.lang.reflect.Method.invoke(Unknown Source)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
| at $Proxy0.start(Unknown Source)
| at org.jboss.system.ServiceController.start(ServiceController.java:417)
| at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
| at java.lang.reflect.Method.invoke(Unknown Source)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
| at $Proxy34.start(Unknown Source)
| at org.jboss.ejb3.EJB3Deployer.start(EJB3Deployer.java:512)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
| at java.lang.reflect.Method.invoke(Unknown Source)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
| at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97)
| at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorServiceMBeanSupport.java:238)
| at org.jboss.ws.integration.jboss42.DeployerInterceptor.start(DeployerInterceptor.java:93)
| at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188)
| at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
| at $Proxy35.start(Unknown Source)
| at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
| at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1015)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
| at sun.reflect.GeneratedMethodAccessor19.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
| at java.lang.reflect.Method.invoke(Unknown Source)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
| at $Proxy9.deploy(Unknown Source)
| at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
| at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
| at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
| at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:274)
| at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:225)
| 15:50:15,622 INFO [EJB3Deployer] Deployed: file:/D:/Programme/jboss-4.2.0.GA/server/default/deploy/WarP-Server.ear/WarP-Server.jar/
| 15:50:15,669 INFO [EARDeployer] Started J2EE application: file:/D:/Programme/jboss-4.2.0.GA/server/default/deploy/WarP-Server.ear/
| 15:50:15,669 ERROR [URLDeploymentScanner] Incomplete Deployment listing:
|
| --- MBeans waiting for other MBeans ---
| ObjectName: jboss.j2ee:ear=WarP-Server.ear,jar=WarP-Server.jar,name=StockServiceEJB,service=EJB3
| State: FAILED
| Reason: java.lang.ClassCastException: org.jboss.spring.factory.NamedXmlApplicationContext cannot be cast to javax.naming.Context
|
| --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
| ObjectName: jboss.j2ee:ear=WarP-Server.ear,jar=WarP-Server.jar,name=StockServiceEJB,service=EJB3
| State: FAILED
| Reason: java.lang.ClassCastException: org.jboss.spring.factory.NamedXmlApplicationContext cannot be cast to javax.naming.Context
|
application.xml:
| <application xmlns="http://java.sun.com/xml/ns/javaee"
| xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
| xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_5.xsd"
| version="5">
|
| <display-name>WarP-Server</display-name>
| <module>
| <ejb>WarP-Server-dao.spring</ejb>
| </module>
|
| <module>
| <ejb>WarP-Server.jar</ejb>
| </module>
| </application>
|
WarP-Server-dao.spring and WarP-Server.jar both are exploded archives too.
Wenn I comment out WarP-Server.jar module in application.xml then I don't get any errors.
In my EJB's I commented out all references to spring beans. Why get I then this error?
One more issue.
When I undeploy *.ear directory then I get this:
|
| 15:58:17,341 WARN [JmxKernelAbstraction] jboss.j2ee:ear=WarP-Server.ear,jar=WarP-Server.jar,name=StockServiceEJB,service=EJB3 is not registered
| 15:58:17,341 INFO [SpringApplicationContextDeployer] Undeploying Spring: file:/D:/Programme/jboss-4.2.0.GA/server/default/deploy/WarP-Server.ear/WarP-Server-dao.spring/
| 15:58:17,341 WARN [NestedThrowable] Duplicate throwable nesting of same base type: class org.jboss.deployment.DeploymentException is assignable from: class org.jboss.deployment.DeploymentException
| 15:58:17,341 ERROR [SpringApplicationContextDeployer] Failed to stop bean factory: file:/D:/Programme/jboss-4.2.0.GA/server/default/deploy/WarP-Server.ear/WarP-Server-dao.spring/
| 15:58:17,356 INFO [EARDeployer] Undeploying J2EE application, destroy step: file:/D:/Programme/jboss-4.2.0.GA/server/default/deploy/WarP-Server.ear/
| 15:58:17,356 INFO [EARDeployer] Undeployed J2EE application: file:/D:/Programme/jboss-4.2.0.GA/server/default/deploy/WarP-Server.ear/
| 15:58:17,356 INFO [ConnectionFactoryBindingService] Unbound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=WarP-ServerDatasource' from JNDI name 'java:WarP-ServerDatasource'
|
|
|
Best regards
Roman
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4064566#4064566
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4064566
18Â years, 12Â months