[JBoss jBPM] - Re: Searching tasks by task variables (hibernated business o
by hstrack
Hi,
OK, I did with the Hibernate Tools. It was a pain, to install them properly (I am also using spring). But I found the query. Here it is, for interested people:
| select taskinstance from Domain as dom,
| TaskInstance taskinstance,
| HibernateLongInstance as hibernatelonginstance
| where
| taskinstance.name = 'Change Provider Request'
| and taskinstance.isOpen = true
| and hibernatelonginstance.id =taskinstance.variableInstances.id
| and hibernatelonginstance.name = 'domain'
| and hibernatelonginstance.value.id = dom.id
| and dom.name = :varvalue
|
| varvalue: a domain Name (class Domain has a "name" field)
|
This query searches a TaskInstance that has a "Domain" object assigned.
Take care: it may only work with jbpm >= 3.1.4
The TaskInstance is created like this:
| <task-node name="Task DomBla task">
| <task name="Task DomBla" swimlane="swimlane1">
| <controller>
| <variable name="domain" access="read"></variable>
| <variable name="approve" access="read,write,required"></variable>
| </controller>
| </task>
| <transition name="" to="isApproved"></transition>
| </task-node>
|
This way you may also list some BusinessObjects with their assigned tasks (if you skip the last line of the query)...
When I executed the query in the hibernate console (eclipse) I got a result and eclipse was getting stuck on 100% CPU for quite a while (tested on freebsd, linux and windows). Seems to be a bug in the hibernate console - however - it is beta software.
It may help anyone who neither has a clue about HQL...
Greetings
Harry
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4028452#4028452
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4028452
19Â years, 1Â month
[JCA/JBoss] - Re: Hibernate+JBossTS+SybaseXA=XAException
by roist
simple explanation:
sybase XADatasource Driver is not 100% XA-compliant.
according to my bible: (http://docs.jboss.org/jbossas/jboss4guide/r5/html/ch7.chapt.html#ch7.jdbc...)
anonymous wrote :
| track-connection-by-tx: Specifying a true value for this element makes the connection manager keep an xid to connection map and only put the connection back in the pool when the transaction completes and all the connection handles are closed or disassociated (by the method calls returning). As a side effect, we never suspend and resume the xid on the connection's XAResource. This is the same connection tracking behavior used for local transactions.
|
| The XA spec implies that any connection may be enrolled in any transaction using any xid for that transaction at any time from any thread (suspending other transactions if necessary). The original JCA implementation assumed this and aggressively delisted connections and put them back in the pool as soon as control left the EJB they were used in or handles were closed. Since some other transaction could be using the connection the next time work needed to be done on the original transaction, there is no way to get the original connection back. It turns out that most XADataSource driver vendors do not support this, and require that all work done under a particular xid go through the same connection.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4028450#4028450
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4028450
19Â years, 1Â month
[Installation, Configuration & Deployment] - Re: BAD_POOL_HEADER, BLUE SCREEN
by PeterJ
Sorry for the delay, but I had to check this at home (I'm running Visat at work and XP at home) and my wife and kids kept on finding other things for me to do.
Anyway, I ran listdlls and here are my results:
0x00400000 0xd000 5.00.0110.0003 C:\apps\jdk1.5.0_11\bin\java.exe
0x7c900000 0xb0000 5.01.2600.2180 C:\WINDOWS\system32\ntdll.dll
0x7c800000 0xf4000 5.01.2600.2945 C:\WINDOWS\system32\kernel32.dll
0x77dd0000 0x9b000 5.01.2600.2180 C:\WINDOWS\system32\ADVAPI32.dll
0x77e70000 0x91000 5.01.2600.2180 C:\WINDOWS\system32\RPCRT4.dll
0x77c10000 0x58000 7.00.2600.2180 C:\WINDOWS\system32\MSVCRT.dll
0x6d740000 0x19d000 5.00.0110.0003 C:\apps\jdk1.5.0_11\jre\bin\client\jvm.dll
0x77d40000 0x90000 5.01.2600.2622 C:\WINDOWS\system32\USER32.dll
0x77f10000 0x47000 5.01.2600.2818 C:\WINDOWS\system32\GDI32.dll
0x76b40000 0x2d000 5.01.2600.2180 C:\WINDOWS\system32\WINMM.dll
0x76390000 0x1d000 5.01.2600.2180 C:\WINDOWS\system32\IMM32.DLL
0x6d300000 0x8000 5.00.0110.0003 C:\apps\jdk1.5.0_11\jre\bin\hpi.dll
0x76bf0000 0xb000 5.01.2600.2180 C:\WINDOWS\system32\PSAPI.DLL
0x6d710000 0xc000 5.00.0110.0003 C:\apps\jdk1.5.0_11\jre\bin\verify.dll
0x6d380000 0x1d000 5.00.0110.0003 C:\apps\jdk1.5.0_11\jre\bin\java.dll
0x6d730000 0xf000 5.00.0110.0003 C:\apps\jdk1.5.0_11\jre\bin\zip.dll
0x6d540000 0x13000 5.00.0110.0003 C:\apps\jdk1.5.0_11\jre\bin\net.dll
0x71ab0000 0x17000 5.01.2600.2180 C:\WINDOWS\system32\WS2_32.dll
0x71aa0000 0x8000 5.01.2600.2180 C:\WINDOWS\system32\WS2HELP.dll
0x71a50000 0x3f000 5.01.2600.2180 C:\WINDOWS\System32\mswsock.dll
0x76f20000 0x27000 5.01.2600.2938 C:\WINDOWS\system32\DNSAPI.dll
0x76fb0000 0x8000 5.01.2600.2180 C:\WINDOWS\System32\winrnr.dll
0x76f60000 0x2c000 5.01.2600.2180 C:\WINDOWS\system32\WLDAP32.dll
0x76fc0000 0x6000 5.01.2600.2938 C:\WINDOWS\system32\rasadhlp.dll
0x6d530000 0x8000 5.00.0110.0003 C:\apps\jdk1.5.0_11\jre\bin\management.dll
0x274c0000 0xf000 10.67.0000.0000 C:\WINDOWS\system32\ZoneLabs\vetredir.dll
0x662b0000 0x58000 5.01.2600.2180 C:\WINDOWS\system32\hnetcfg.dll
0x27690000 0x15000 10.67.0000.0000 C:\WINDOWS\system32\ZoneLabs\isafeif.dll
0x71a90000 0x8000 5.01.2600.2180 C:\WINDOWS\System32\wshtcpip.dll
0x27800000 0x28000 5.01.2600.2161 C:\WINDOWS\system32\rsaenh.dll
0x769c0000 0xb3000 5.01.2600.2180 C:\WINDOWS\system32\USERENV.dll
0x5b860000 0x54000 5.01.2600.2976 C:\WINDOWS\system32\netapi32.dll
0x6d560000 0x9000 5.00.0110.0003 C:\apps\jdk1.5.0_11\jre\bin\nio.dll
The first thing I noticed (other than you are running JRockit and I am running HotSpot, which doesn;t matter anyway) was that you have not applied thel atest patches. For example, look at the version number on kernel32.dll. Other than that there are a few dlls that show up for you that I don't have: secure32.dll, ntmarta.dll, etc. The ones I checked appear to be valid Windows DLLs, but one never knows (you can always goolge the dlls to learn about them). It is very likely that these DLLs are used by JRockit but not by HotSpot, or it could be related to various JVM options you might have set.
My recommendation is to first download the latest patches from the Windows Update site. Then also get the latest drivers for your NIC card graphics card. If that doesn't work, the next step is to swap out the NIC and graphics card for another one.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4028445#4028445
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4028445
19Â years, 1Â month
[EJB 3.0] - Create EAR with EJB3 and JAX-WS
by oskar.carlstedt
Hello!!
I have been struggling a whole day now with this topic. Reading a lot of forum questions and tips, but I can't find a solution. Now I hope some of you can help me.
I want to deploy an ear file containing a jar file that contains an EJB. The ejb jar file also contains a JAX-WS-web service endpoint provider that will "lookup" a session bean containing business methods for the actual web service request.
I have a couple of problems. JBoss (version 4.2.0.CR1). I always get the message:
16:17:41,057 WARN [verifier] EJB spec violation:
| Bean : TestEjb
| Section: 22.2
| Warning: The Bean Provider must specify the fully-qualified name of the Java class that implements the enterprise bean's business methods in the <ejb-class> element.
| Info : Class not found on 'some.package.TestEJB': No ClassLoaders found for: some.package.TestEJB
Of course, I don't have any TestEJB class. I really can't understand why it is questioning about it.
I have an interface
| public interface Test {
| ...
| }
|
And I have a class
| @Stateless
| public class TestBean implements Test {
| ...
| }
|
My JAX-WS Service enpoint provider looks something like:
| @Stateless
| @WebServiceProvider(
| serviceName = "Test",
| portName = "TestSoap11Port",
| targetNamespace = "http://my.domain.com/test-service",
| wsdlLocation = "WEB-INF/wsdl/test-service.wsdl")
| @ServiceMode(value = Service.Mode.PAYLOAD)
| public class TestEndpointProvider implements Provider<Source> {
|
| /**
| * The sei to use
| */
| private Object sei = null;
|
| @Resource
| protected WebServiceContext webServiceContext;
|
| /**
| * Does everything that must be done. This method is a kind of dispatcher
| * that finds the business method to invoke. Invokes the method and
| * serializes the response.
| */
| public Source invoke(Source requestSource) {
|
| try {
|
| ...
|
| // instantiate the sei
| InitialContext initialContext = new InitialContext();
| sei = initialContext.lookup(some.package.Test.class.getName());
|
| // get business method
| Method wsdlJavaMethod = getWsdlJavaMethod();
|
| // invoke method
| XmlObject xmlResponseObject = (XmlObject) wsdlJavaMethod.invoke(sei, xmlRequestObject);
|
| ...
|
| } catch (RuntimeException re) {
|
| throw re;
| } catch (Exception e) {
|
| throw new WebServiceException(e);
| }
| }
| }
|
I have tried to annotate my EJB with the @Local(Test.class) and also the EJB annotation @EJB(beanInterface=Test.class, name="Test").
The JAX-WS service endpoint provider does also have a Stateless annotation. Can this bean mess it up?
The other thing is that JBoss reject to load my jar files included in the EAR file. All jar dependencies are on the classpath in the META-INF/MAINIFEST.MF file (generated by maven).
My ear file has the following structure:
| test-ear-1.0-SNAPSHOT
| META-INF
| jboss-app.xml
| lib
| ...
| test-ejb-1.0-SNAPSHOT.jar
|
jboss-app.xml
| <!DOCTYPE jboss-app
| PUBLIC "-//JBoss//DTD J2EE Application 1.4//EN"
| "http://www.jboss.org/j2ee/dtd/jboss-app_4_0.dtd">
| <jboss-app>
| <loader-repository>
| some.package:loader=test-ear-1.0-SNAPSHOT
| </loader-repository>
| </jboss-app>
|
Does anyone know how I can fix these problems? DO I need anejb-jar.xml when I'm using EJB3. Do I have to configure JBoss 4.2.0.CR1. I get the same error in JBoss 4.0.5.GA with a jboss-EJB-3.0_RC9_Patch_1 installed.
Best
Oskar
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4028444#4028444
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4028444
19Â years, 1Â month