June 2010 - jboss-user - Jboss List Archives

by Fabio Spiga

Fabio Spiga [http://community.jboss.org/people/Spiga] created the discussion "Join jBPM with Domain data" To view the discussion, visit: http://community.jboss.org/message/548949#548949 -------------------------------------------------------------- Hello, I have a performance problem that seems to be quite standard. In my web-app, the domain data are for example DOCUMENTS. Each Document is bound to a jBPM instance. Both the domain and the jBPM tables are in the same database. When I list the personal tasks for a user, I would like to see in the same table both the domain data for the Document (type, referrer, size, ...) and the jBPM data (taskname, task priority, jbpm_ID, ...) So far, the only way I found to obtain these information is: 1) to call findPersonalTasks() from jBPM API 2) loop the Collection returned and, for each Task, call another query to get domain data about the Document related (or viceversa) This way is very heavy, is there a way to get these information by a single query? Or I have to change my data structure? Thanks, Fabio -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/548949#548949] Start a new discussion in jBPM at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

15 years, 10 months

1
0
0 / 0

Re: [jboss-user] [JBoss Web Services CXF] - Continuing problem with XTS WS-T tests in AS trunk/CXF 2.2.9

by Andrew Dinn

Andrew Dinn [http://community.jboss.org/people/adinn] replied to the discussion "Continuing problem with XTS WS-T tests in AS trunk/CXF 2.2.9" To view the discussion, visit: http://community.jboss.org/message/548945#548945 -------------------------------------------------------------- Hi Jim, > I tested modify the schemaLocation to " http://schemas.xmlsoap.org/soap/envelope/ http://schemas.xmlsoap.org/soap/envelope/" can fix this issue . I tried that and it did not seem to fix things. However, I have just tried it again and it does resolve the parsing problem -- thanks very much for the diagnosis. Unfortunately, the tests are still failing because of another problem which is much more serious. I failed to notice it because it was masked by the parsing error. The fault is still not being delivered and the problem is still because of a failure to obtain a proxy under getPort. However, the reason I am getting the error is different. The thing which has changed between the old native/cxf and the latest cxf and which is causing this error is the FaultTo endpoint used as the address for the fault I am sending via the SoapFaultService. The previous implementations did not contain metadata, they only contained the address of the Initiator service and the reference parameter identifying the transaction. Or at least if they did include metadata it was not used when creating the proxy and dispatching the fault. The current CXF includes metadata for my Initiator service i.e. it defines the service as InitiatorService and the port as InitiatorPortType. However, I am trying to obtain a port for the SoapFaultService with name SoapFaultPortType and use this port to route the fault back to my endpoint bean. The call to getPort is failing because the metadata does not mention a port with name InitiatorPortType. Using this mechanism the way I have been doing is probably an abuse of JaxWS. However, it used to work and, in fact, it was the only way of sending an asynchronous fault to the originating endpoint. This is not the only place I had to bend the rules. I was also relying upon Native and CXF to accept an incoming fault addressed to the Initiator endpoint bean and invoke the soapFault() web method associated with the SoapFault Action attached to the fault. They both used to do this even though the wsdl which defines the service and port under which the endpoint bean was published do not include this web method. I am not sure if they will still do this however I had to rely on this in order to be able to send asynchronous faults using only JaxWS. I invented the SoapFaultService provide a uniform way of dispatching faults on the client side but it is not part of the OASIS spec. The spec does not address how asynchronous faults are dispatched or delivered. It merely assumes that this can will happen. Ok, so having diagnosed the problem what can be done about it? Well, there are two things I can try in order to get XTS working again JBoss to JBoss (I am not yet sure whta the implications are for interoperability). Firstly, when I create the FaultTo endpoint I can set the service and port in the endpoint to be SoapFaultService and SoapFaultPortType. So, if any of my services need to dispatch a fault then this will mean that they will be able to obtain a JaxWS proxy for the fault service and hence use JaxWS to dispatch the fault. Once I have done this I will then be able to see whether CXF will deliver an incoming asynchronous fault to my endpoint beans according to the SoapFault Action even thoguht the endpoint wsdl does not define the web method. If it does then I can perhaps continue to use my endpoint beans to field the faults. If it doesn't (or if I decide not to rely on this continuing to work -- it is a maybe a little fragile) I will have to provide a SoapFaultService endpoint bean to field the incoming faults and route them back to the relevant XTS beans. These two changesought to allow me to get JBoss to JBoss working again. My concern is that this may cause a problem for interoperability. Why? Well, lets recap the situation. My code has to use JaxWS to dispatch an asynchronous fault to the FaultTo endpoint -- the whole point of the XTS redesign between 1.0 and 1.1 was to remove our own SOAP stack from the XTS codebase and rely entirely on JBossWS. I cannot change the the OASIS spec wsdl which my service bean simplement. Since it does not not define any operations allowing me to dispatch/receive faults I have had to invent an independent fault service for asynchronous fault delivery. This means I have to include the service and port names in the FaultTo endpoint and use the invented fault service wsdl to deliver the fault. Now, if we are now handing out FaultTo endpoints which inlcude metadata referencing this invented service then it is not clear whether this will cause problems for other implementations which are not built over JaxWS. They might ignore any metadat and only consider the service address. However, they might also quite legitimately expect the metadata in the FaultTo endpoint to refer to the OASIS service and port which passed them the endpoint. After all that is the service which they expect to be communicating with. By contrast, any implementation which +is+ based on JaxWS will not be able to dispatch faults unless it uses my SoapFaultService wsdl. So, what was a protocol private to the JBoss implementation may now need to become a public protocol and require, at least, documentation and, at worst, agreement and standardization. There is one further option I might pursue. When I create the FaultTo endpoint woudl it be possible to create it without any medtadata by not specifying a service/port? Will the CXF endpoint builder build such an endpoint? If it does then will ServiceImpl.getPort allow me to create a JaxWS port for the SoapFault service? I am half-convinced that a FaultTo endpoint really ought not to have any service/port metadata associated with it anyway. After all it is only supposed to be used for delivering faults. I will experiment with making each of the two changes I described above, one after the other -- changing the endpoint metadata, adding an independent endpoint/bean for receipt of the fault messages. However, I would also be interested to hear what others think about what I am trying to do here. Here is a summary of my posiiton * services which employ multi-message dialogues based on OneWay MEPs will benefit from being able to dispatch asynchronous faults to a FaultTo endpoint supplied in the OneWay message Message Addressing Properties (MAP) * these services ought to be able to employ JaxWS to dispatch and deliver the fault * if there is a need for metadata to be included in the FaultTo endpoint in order to guarantee dispatch and/or delivery then the metadata ought to reference a JaxWS standard wsdl defining the relevant service and ports (i.e. somethign liek my SoapFaultService ought to be agreed on as a standard way to do this) * if there is no need for any metadata to be included in the FaultTo endpoint then it should be possible to create a FaultTo endpoint without specifying a sevrice/port name and pass this using the MAP I'll follow up with progress on the results of making the changes I described above. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/548945#548945] Start a new discussion in JBoss Web Services CXF at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

15 years, 10 months

1
0
0 / 0

Re: [jboss-user] [jBPM] - The external Trigger makes the transition from subprocess node to the next node while subprocess is active.

by Maciej Swiderski

Maciej Swiderski [http://community.jboss.org/people/swiderski.maciej] replied to the discussion "The external Trigger makes the transition from subprocess node to the next node while subprocess is active." To view the discussion, visit: http://community.jboss.org/message/548936#548936 -------------------------------------------------------------- The fix will do what you expect. In case of signal of main process while sub process is still running it will throw an exception that main process is not active. In addition, since 4.4 there will be API method exposing subprocess instance so you will not need to use internal classes to get hold of this information. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/548936#548936] Start a new discussion in jBPM at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

15 years, 10 months

1
0
0 / 0

Re: [jboss-user] [jBPM] - Multiple JBPM4_VARIABLE records pointing to same LOB_ and different EXECUTIONID_

by Jorge Ferreira

Jorge Ferreira [http://community.jboss.org/people/imjorge] replied to the discussion "Multiple JBPM4_VARIABLE records pointing to same LOB_ and different EXECUTIONID_" To view the discussion, visit: http://community.jboss.org/message/548934#548934 -------------------------------------------------------------- At the moment I cannot create a test case that reproduces this problem. This issue appears from time to time in a large system. My best bet so far would be concurrency and some FK becomes mangled in the middle. I will continue to work on this issue to understand the root cause of the problem. -- Jorge -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/548934#548934] Start a new discussion in jBPM at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

15 years, 10 months

1
0
0 / 0

[JBoss Web Services] - web-service authentication problem

by Christy Christy

Christy Christy [http://community.jboss.org/people/christy] created the discussion "web-service authentication problem" To view the discussion, visit: http://community.jboss.org/message/548931#548931 -------------------------------------------------------------- Hi to everyone! I want to secure the endpoint but do not want to secure thr wsdl file. I tried to do it two ways but I can not do it. The first way: I tried to use annotations. This is my simple POJO web-service: > @WebContext(contextRoot="/testFormats", urlPattern="/*", authMethod="BASIC", transportGuarantee="NONE", secureWSDLAccess=false) > @SecurityDomain("JBossWS") > @RolesAllowed("friend") > @WebService( > portName = "TestFormatsPort", > serviceName = "TestFormatsService", > targetNamespace = " http://testservices/ http://testservices/" > ) > public class TestFormatsService { > @WebMethod > public int getNumber(Double d) { > ///// > } In this case wsdl is not secure, but the endpoint is not secure too. I can easy get access to web-service through client stubs. the second way: I did not used any annotations, I configured web.xml: > <web-app version='2.4' xmlns=' http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee' xmlns:xsi=' http://www.w3.org/2001/XMLSchema-instance http://www.w3.org/2001/XMLSchema-instance' xsi:schemaLocation=' http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd'> > <servlet> > <servlet-name>TestFormatsService</servlet-name> > <servlet-class>testservices.TestFormatsService</servlet-class> > </servlet> > <servlet-mapping> > <servlet-name>TestFormatsService</servlet-name> > <url-pattern>/*</url-pattern> > </servlet-mapping> > > <security-constraint> > <web-resource-collection> > <web-resource-name>All resources</web-resource-name> > <url-pattern>/*</url-pattern> > </web-resource-collection> > <auth-constraint> > <role-name>friend</role-name> > </auth-constraint> > </security-constraint> > <login-config> > <auth-method>BASIC</auth-method> > </login-config> > <security-role> > <role-name>friend</role-name> > </security-role> > </web-app> And I configured +jboss-web.xlm:+ + +> > <?xml version="1.0" encoding="UTF-8"?> > <jboss-web> > <security-domain>java:/jaas/foobar</security-domain> > </jboss-web> > In this case I have secured wsdl. Please help me to do the secure endpoint but not secure wsdl. thanks in advance -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/548931#548931] Start a new discussion in JBoss Web Services at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

15 years, 10 months

1
0
0 / 0

Re: [jboss-user] [jBPM] - The external Trigger makes the transition from subprocess node to the next node while subprocess is active.

by HuiSheng Xu

HuiSheng Xu [http://community.jboss.org/people/rebody] replied to the discussion "The external Trigger makes the transition from subprocess node to the next node while subprocess is active." To view the discussion, visit: http://community.jboss.org/message/548920#548920 -------------------------------------------------------------- Hi Felix, Maciej's patch could fix the bug that after signal a main process, then automaticly end the related sub process. So we won't leave a lonely sub process instance whose main process instance had bean signaled. If you want to get an exception and forbid main process to continue when it has an un-ended sub process instance, you could open an issue, And we could achieve it in the next version. Thank you very much. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/548920#548920] Start a new discussion in jBPM at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

15 years, 10 months

1
0
0 / 0

Re: [jboss-user] [jBPM] - The external Trigger makes the transition from subprocess node to the next node while subprocess is active.

by Felix Jose

Felix Jose [http://community.jboss.org/people/FelixKJose] replied to the discussion "The external Trigger makes the transition from subprocess node to the next node while subprocess is active." To view the discussion, visit: http://community.jboss.org/message/548919#548919 -------------------------------------------------------------- Hi Maceij, Thank you for your reply. The JBPM-2874, the test case "testSubProcessWithStateFailure" is making the transition from the subprocess node to the next node using the main process instance id while the subprocess is in "wait" state. And then checking the process stateagainst the subprocess state. And my doubt is why the JBPM is not throwing any exception? Because 1. The sub process is in active state(wait state). 2. The main process is not making the transition over the sub process nodes. So whether only a state check will do the solution or make a change in the implementation class of executionService's "signalExecutionById" method to check the subprocess instance is active or not and throw an exception saying the "Invalid transition. Subprocess [subprocess id =<Sub 19>] is active." while the sub process is active. And should not able to transition from sub process node to next node. Please let me know about your thoughts on the same. By using ExecutionImpl I am getting the subprocess Id and using that I am able to transition through the subprocess nodes. ExecutionImpl subExecutionImpl = executionImpl.getSubProcessInstance(); Because by using the ExecutionImpl I can get the subprocessId and main processId. But when I am doing a transition ( +executionService.signalExecutionById(executionImpl.getId())+ from subprocess node to the next node, it is happening successfully, while the subprocess is active(wait). This is not the intended output. My expected result in this case is "throw an exception saying the "Invalid transition. Subprocess [subprocess id =<Sub 19>] is active." Please give me a reply regarding this as soon as possible. Thank You and Regards, Felix K Jose +executionService+.signalExecutionById(subExecutionImpl.getId()); But please let me know how the ExecutionImpl will do the workaround? -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/548919#548919] Start a new discussion in jBPM at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

15 years, 10 months

1
0
0 / 0

[Beginner's Corner] - Drools Planner: Examples not running. Kindly suggest.....

by Chiranjeevi Reddy

Chiranjeevi Reddy [http://community.jboss.org/people/Chiruu] created the discussion "Drools Planner: Examples not running. Kindly suggest....." To view the discussion, visit: http://community.jboss.org/message/548918#548918 -------------------------------------------------------------- Hi All, I have downloaded the Drools Planner as well as Drools Solver examples from the downloads seciton of Drools. I have been trying to run the runExamples.bat on Windows XP SP2 as well as runExamples.sh on Linux flavor - Ubuntu 9. Neither of the script files open and run those examples. Kindly let me know if I need to edit the script and run those examples or change my configurations. Also kindly guide me as how to install Drools Planner on to Eclipse IDE and start of a new project. Thanks & Regards REDDY -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/548918#548918] Start a new discussion in Beginner's Corner at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

15 years, 10 months

1
0
0 / 0

Re: [jboss-user] [jBPM] - Multiple JBPM4_VARIABLE records pointing to same LOB_ and different EXECUTIONID_

by HuiSheng Xu

HuiSheng Xu [http://community.jboss.org/people/rebody] replied to the discussion "Multiple JBPM4_VARIABLE records pointing to same LOB_ and different EXECUTIONID_" To view the discussion, visit: http://community.jboss.org/message/548912#548912 -------------------------------------------------------------- Hi Jorge, Could you provide a testcase to reproduce this problem. It will help us to understand this problem more clearly. Thank you very much. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/548912#548912] Start a new discussion in jBPM at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

15 years, 10 months

1
0
0 / 0

Re: [jboss-user] [jBPM] - How to link a Java-class to end-point of all tasks

by HuiSheng Xu

HuiSheng Xu [http://community.jboss.org/people/rebody] replied to the discussion "How to link a Java-class to end-point of all tasks" To view the discussion, visit: http://community.jboss.org/message/548911#548911 -------------------------------------------------------------- Hi Evgeniy, At this moment HistorySession Chain is the only solution for your requirement. And you are right, there is no way to get task information from TaskComplete. I think you could open an issue for this scenario. Now, you have to use reflect to get the execution from TaskComplete, then you could get related task information -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/548911#548911] Start a new discussion in jBPM at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

15 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-user June 2010