[Persistence, JBoss/CMP, Hibernate, Database] - Can JBoss 4.0.5 integrate with Oracle OCI XA Type 2 Driver?
by wangdongfox
Because we will configure the oracle RAC in the JBoss environment, so we need the Oracle OCI Type 2 driver, and in our environment, we must support XA because our environment has more than one data storage, so we must use the Oracle OCI XA Type 2 Driver. But after we configure it in our environment, we find it doesn't work, but if we use the Oracle OCI Type 2 Driver that doesn't support the XA, we find it works. Can anybody tell me if the JBoss 4.0.5 can integrate with Oracle OCI XA Type 2 Driver. And if it is OK, can you tell me how to configure? Thank you very much.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051255#4051255
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4051255
18Â years, 10Â months
[JBoss jBPM] - Custom define process-definition.xml file?
by shiliang
I want to add Attribute to process-definition.xml ,
like this
<variable name="schemeConofirm" access="read,write" mapped-name="schemeConofirm" display-type="radio">
and i add Attribute in jpdl3.0.xsd and jpdl3.1.xsd
<xs:element name="variable">
<xs:complexType>
<xs:sequence>
<xs:any processContents="lax" minOccurs="0" maxOccurs="unbounded" />
</xs:sequence>
<xs:attribute name="name" type="xs:string" use="required"/>
<xs:attribute name="access" type="xs:string" default="read,write"/>
<xs:attribute name="mapped-name" type="xs:string" />
<xs:attribute name="display-type" type="xs:string" default="text"/>
</xs:complexType>
</xs:element>
but i get some error like this,
org.jbpm.jpdl.JpdlException: [[ERROR] line 26: cvc-complex-type.3.2.2: Attribute 'display-type' is not allowed to appear in element 'variable'., [ERROR] line 28: cvc-complex-type.3.2.2: Attribute 'display-type' is not allowed to appear in element 'variable'., [ERROR] line 48: cvc-complex-type.3.2.2: Attribute 'display-type' is not allowed to appear in element 'variable'., [ERROR] line 60: cvc-complex-type.3.2.2: Attribute 'display-type' is not allowed to appear in element 'variable'., [ERROR] line 62: cvc-complex-type.3.2.2: Attribute 'display-type' is not allowed to appear in element 'variable'., [ERROR] line 66: cvc-complex-type.3.2.2: Attribute 'display-type' is not allowed to appear in element 'variable'., [ERROR] line 77: cvc-complex-type.3.2.2: Attribute 'display-type' is not allowed to appear in element 'variable'., [ERROR] line 79: cvc-complex-type.3.2.2: Attribute 'display-type' is not allowed to appear in element 'variable'., [ERROR] line 83: cvc-complex-type.3.2.2: Attribute 'display-type' is not allowed to appear in element 'variable'., [ERROR] line 85: cvc-complex-type.3.2.2: Attribute 'display-type' is not allowed to appear in element 'variable'.]
at org.jbpm.jpdl.xml.JpdlXmlReader.readProcessDefinition(JpdlXmlReader.java:163)
at org.jbpm.jpdl.par.JpdlArchiveParser.readFromArchive(JpdlArchiveParser.java:53)
at org.jbpm.jpdl.par.ProcessArchive.parseProcessDefinition(ProcessArchive.java:81)
at org.jbpm.graph.def.ProcessDefinition.parseParZipInputStream(ProcessDefinition.java:190)
at org.jbpm.webapp.servlet.UploadServlet.doDeployment(UploadServlet.java:92)
at org.jbpm.webapp.servlet.UploadServlet.handleRequest(UploadServlet.java:81)
at org.jbpm.webapp.servlet.UploadServlet.service(UploadServlet.java:50)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.jbpm.webapp.filter.AuthenticationFilter.doFilter(AuthenticationFilter.java:56)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.jbpm.web.JbpmContextFilter.doFilter(JbpmContextFilter.java:83)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.jbpm.webapp.filter.LogFilter.doFilter(LogFilter.java:59)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:744)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
at java.lang.Thread.run(Thread.java:595)
please help me!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051251#4051251
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4051251
18Â years, 10Â months
[JBoss jBPM] - Re: Problem in getting proper workflow transitions:
by maxp
Ok let me give a concrete example:
| <process-definition
| xmlns="urn:jbpm.org:jpdl-3.1" name="credit-request-approval">
|
| <start-state name="start">
| <task name="task-node1" ></task>
| <transition name="send for approval" to="task-node2">
| </start-state>
|
| </task-node>
| <task-node name="task-node2">
| <task name="approval1"></task>
| <transition name="approved" to="task-node3"></transition>
| <transition name="rejected" to="Request rejected"></transition>
| </task-node>
| <task-node name="task-node3">
| <task name="approval2"></task>
| <transition name="approved" to="Request Approved"></transition>
| <transition name="rejected" to="Request rejected"></transition>
| </task-node>
| <end-state name="Request Approved"></end-state>
| <end-state name="Request rejected"></end-state>
| </process-definition>
|
if i do
| {
|
| ProcessInstance processInstance = new ProcessInstance(processDefinition2);
| TaskInstance taskInstance = processInstance.getTaskMgmtInstance().createStartTaskInstance();
| taskInstance.start();
| context.save(processInstance);
|
| Token token = processInstance.getRootToken();
| System.out.println(token.getNode().getName() + " <br><br>");
|
| taskInstance.end("send for approval");
|
| token = processInstance.getRootToken();
| System.out.println(token.getNode().getName() + " <br><br>");
| }
|
2 task instances are created for me
start and task-node2
But, say i do something like this
|
| ProcessInstance processInstance = new ProcessInstance(processDefinition2);
| TaskInstance taskInstance = processInstance.getTaskMgmtInstance().createStartTaskInstance();
| taskInstance.start();
| context.save(processInstance);
|
and in a seperate servlet i do
| TaskMgmtSession taskMgmtSession = context.getTaskMgmtSession();
| TaskInstance taskInstance = context.loadTaskInstanceForUpdate(1L);
| taskInstance.end("send for approval");
|
then only the start taskinstance is created.
Any ideas why this might be the case.
Is it something related to same context or something ? Any ideas how i can achieve this .
I must mention i am creating seperate contexts in these different servlets if that might be the case. I am really unsure of this behaviour .
Ideas ? ?
- MAx
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051250#4051250
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4051250
18Â years, 10Â months
[JBoss jBPM] - Superstate-enter event not fired
by jeanbobby
Hi,
This is my first usage of super states, as phases in a process.
here's an extact:
<start-state name="start">
| <transition to="buildPhase"/>
| </start-state>
|
| <super-state name="buildPhase">
|
| <event type="superstate-enter">
| <action class="com..." />
| </event>
|
| ...
|
| <state name="waitForValidation">
| <transition to="../deliveryPhase"/>
| </state>
|
| <event type="superstate-leave">
| <action class="com..." />
| </event>
The super state leave event is fired, but enter is not.
>From what I read I cant say the doc is precise about this specific behaviour.
Looking at the code this seems 'normal' :
- Transition.take:
if ( destination.getSuperState()!=null ) {
| ... fire the event ...
- SuperState.execute :
Node startNode = (Node) nodes.get(0);
| startNode.enter(executionContext);
Going from a node to a super-state taking an explicit transition wont cause the event to be fired as dest.getSuperState == null.
Then the super state will be executed and the first node will be entered without any kind of 'transient' transition being taken.
What do you guys think about that ?
AFAIAC I would expect the super-enter event being fired whatever the enter context (thru an innder node, or referencing the super-state itself).
Thanks for your input.
Best regards
Olivier
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051249#4051249
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4051249
18Â years, 10Â months
[JBoss Portal] - Re: xwiki-1.0.war on JBoss Portal as a portlet
by julienï¼ jboss.com
XWiki portlet cannot run in JBoss Portal without modifications.
Actually XWiki wants to access the requet URL
Since the request URL is not provided by the PortletRequest, it has an abstraction to get the request URL by using hacks like a cast to a specific class from portal vendors.
That has not been implemented for JBoss Portal.
You should look at the source code of xwiki and see if you can recompile with the following modification:
In the class com.xpn.xwiki.web.XWikiPortletRequest there is a getHttpServletRequest() method. You should try to add the following code:
| if (request.getSession().getPortletContext().getServerName().equals("JBossPortal/1.0")))
| {
| Class clazz = Thread.currentThread().getContextClassLoader().loadClass("org.jboss.portal.bridge.JBossServletContextProvider");
| Method getHttpServletRequest = clazz.getMethod("getHttpServletRequest", new Class[]{GenericPortlet.class,PortletRequest.class};
| return (HttpServletRequest)getHttpServletRequest.invoke(null, new Object[]{null,portletRequest});
| }
|
That should fix that first issue you are having.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051247#4051247
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4051247
18Â years, 10Â months
[JBoss Seam] - Recommendation for layered architecture???
by maku01
In my former jsf projects I used a classical layered architecture with spring (and hibernate) for implementing a completely stateless service layer.
e.g.
UI (JSF) --> Delegate --> Service Layer --> DAO Layer
With the help of Spring I was able to handle the transactions declaratively, handle exceptions and so on with the help of AOP.
I had a clear demarcation between UI and backend.
I structured this architecture in some distinct projects:
- generic backend func.
- app. specific backend func.
- generic ui func.
- app. specific ui func.
Maven2 does the magic when it comes to deployment.
Now I evaluate Seam an I see a very interesting UI framework on top of JSF which is able to help the developer in a great manner.
(and I would really like to move in this direction)
But, I'm a little bit confused about the coherence between the UI and the business logic.
What I have to achieve is to use the business logic in a non UI app e.g. for batch purposes (bill computations and so on)
I would need a recommendation for structuring my app so that the usage of the business logic is possible without pain.
Also I see little problems when developing with the seam ant approach because of the separation of the app in several projects.
(a Maven approach would be very helpful in this context)
Could anybody of you give me an advice or share the experience in context with the topics above.
TIA
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051238#4051238
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4051238
18Â years, 10Â months