[jBPM Users] - Re: Variable missing in assignment handler
by nizzy
"Implicit is possible by extending and overriding the subprocess node implementation."
--
Why are super-process variables not by default copied into the sub-process?
Am I missing something or is this not the behaviour what most people require, should it not be included as part of Jboss JBPM core functionality?
It may just be the way we use JBPM but I always want the super-process variables to be available to the sub-process, without having to worry about overriding SubprocessNode implementation!
Indeed it is counter-intuitive that they are not available.
Defining them in the process definition is IMO not the best way to achieve this; since a dependecny is introduced between the business logic layer and the process definition xml.
I assume there is a very good reason for this limitation?
Could someone enlighten me please!!!!
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4268592#4268592
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4268592
16 years, 4 months
[JBoss Web Services Users] - Invalid HTTP server response [400] - Bad Request
by suryasahu
Hi
I have a web application running on JBoss 4.2.2 on a Windows Xp machine. It has a Web Service client that was built using JBossWS Native 3.0.4. This client is sending a SOAP packet to a .NET WebService. I get a very high failure rate with the following error.
>From the exception, it looks like there is something wrong with the Request that is being created. How can find out what exactly is wrong with it? Is there a way to influence the way the request is generated? Any documentation, any pointer would help.
Thanks.
2009-12-02 10:38:03,234 DEBUG [org.jboss.ws.core.soap.SOAPContentElement] --------------------------
| ---------
| 2009-12-02 10:38:03,234 DEBUG [org.jboss.remoting.transport.http.HTTPClientInvoker] Error invoking h
| ttp client invoker.
| org.jboss.ws.WSException: Invalid HTTP server response [400] - Bad Request ( The HTTP request includ
| es a non-supported header. Contact your ISA Server administrator. )
| at org.jboss.ws.core.soap.SOAPMessageUnMarshallerHTTP.read(SOAPMessageUnMarshallerHTTP.java:75)
| at org.jboss.remoting.transport.http.HTTPClientInvoker.readResponse(HTTPClientInvoker.java:473)
| at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:
| 305)
| at org.jboss.remoting.transport.http.HTTPClientInvoker.transport(HTTPClientInvoker.java:135)
| at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
| at org.jboss.remoting.Client.invoke(Client.java:1634)
| at org.jboss.remoting.Client.invoke(Client.java:548)
| at org.jboss.ws.core.client.HTTPRemotingConnection.invoke(HTTPRemotingConnection.java:242)
| at org.jboss.ws.core.client.SOAPProtocolConnectionHTTP.invoke(SOAPProtocolConnectionHTTP.java:71)
| at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:340)
| at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:291)
| at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:170)
| at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:150)
| at $Proxy80.sendNotification(Unknown Source)
| at gov.pacts.vccaNotification.queue.QueueProcessor.run(QueueProcessor.java:211)
| at java.lang.Thread.run(Thread.java:619)
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4268591#4268591
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4268591
16 years, 4 months
[Beginner's Corner] - JBoss and Sockets
by komyg
Hi, I am new to JBoss and I need to develop a scalable application that should function as a Web Service. Furthermore all of the requests and responses to and from this application should be inside a transaction.
Reding through the net, I saw that JBoss has built in scalability and transaction support.
However, even though the traditional way to develop my application would be by using Web Services, I have some concerns about its performance, because since this application should deal with a really big amount of requests in a very short amount of time, the time spent in creating, parsing, etc the Web Service's XMLs can become an issue.
Therefore I was thinking of using a socket to handle the communication between the client and the server applications.
So I would like to know if there is a way to open tcp sockets to and from JBoss and if those sockets would still be sacalable and transactioned.
Thanks,
Komyg
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4268585#4268585
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4268585
16 years, 4 months
[JBoss Portal Users] - Web Service client runs into Error invoking http client invo
by suryasahu
Hi
I have a web application running on JBoss 4.2.2 on a Windows Xp machine. It has a Web Service client that was built using JBossWS Native 3.0.4. This client is sending a SOAP packet to a .NET WebService. I get a very high failure rate with the following error.
>From the exception, it looks like there is something wrong with the Request that is being created. How can find out what exactly is wrong with it? Is there a way to influence the way the request is generated? Any documentation, any pointer would help.
Thanks,
2009-12-02 10:38:03,234 DEBUG [org.jboss.ws.core.soap.SOAPContentElement] -----------------------------------
| 2009-12-02 10:38:03,234 DEBUG [org.jboss.remoting.transport.http.HTTPClientInvoker] Error invoking http client invoker.
| org.jboss.ws.WSException: Invalid HTTP server response [400] - Bad Request ( The HTTP request includes a non-supported header. Contact your ISA Server administrator. )
| at org.jboss.ws.core.soap.SOAPMessageUnMarshallerHTTP.read(SOAPMessageUnMarshallerHTTP.java:75)
| at org.jboss.remoting.transport.http.HTTPClientInvoker.readResponse(HTTPClientInvoker.java:473)
| at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:305)
| at org.jboss.remoting.transport.http.HTTPClientInvoker.transport(HTTPClientInvoker.java:135)
| at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
| at org.jboss.remoting.Client.invoke(Client.java:1634)
| at org.jboss.remoting.Client.invoke(Client.java:548)
| at org.jboss.ws.core.client.HTTPRemotingConnection.invoke(HTTPRemotingConnection.java:242)
| at org.jboss.ws.core.client.SOAPProtocolConnectionHTTP.invoke(SOAPProtocolConnectionHTTP.java:71)
| at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:340)
| at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:291)
| at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:170)
| at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:150)
| at $Proxy80.sendNotification(Unknown Source)
| at gov.pacts.vccaNotification.queue.QueueProcessor.run(QueueProcessor.java:211)
| at java.lang.Thread.run(Thread.java:619)
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4268579#4268579
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4268579
16 years, 4 months