Re: [jboss-dev-forums] [JBoss ESB Development] - Problem in retrieving WSDL from remote endpoint
by David Ward
David Ward [http://community.jboss.org/people/dward] replied to the discussion
"Problem in retrieving WSDL from remote endpoint"
To view the discussion, visit: http://community.jboss.org/message/540614#540614
--------------------------------------------------------------
https://jira.jboss.org/jira/browse/JBESB-3279 JBESB-3279 is closed.
Kev and I continued this discussion over IM, and decided on the following, which I implemented in the fix:
1. Even though WS Basic Profile has rules about http://www.ws-i.org/Profiles/BasicProfile-1.0-2004-04-16.html#refinement1... Acceptable WSDL Character Encodings, we will do our best to handle those situations - where we can - so that +our+ code will output compliant WSDL.
2. WSDL can be read in using internal://, classpath://, file://, http:// http:// and https:// https:// protocols. In the case of internal://, which is provided by JBossWS, it is already UTF-8. In the case of http:// http:// or https:// https://, we will try to look for the charset specified by the HTTP response header "Content-Type". If that is specified, we will try to convert from that specified encoding to UTF-8.
3. A new SOAPProxy action property has been added: wsdlCharset (the camel case property name was chosen so it is consistent with the wsdlTransform property). If the developer specifies the wsdlCharset property, the WSDL will be read in using that encoding, and we will try to convert from that specified encoding to UTF-8. The presence of that property takes priority over the Content-Type header in the case of http:// http:// or https:// https://.
4. The contract JSP (in the case of using JBR/HTTP gateway) and the HttpGatewayServlet both now always output UTF-8.
5. The Programmer's Guid has been updated to include a description about the new wsdlCharset property.
Please refer to the jira item for a test case as well as a screenshot of some Russian characters in Unicode.
Vitaliy, with this fix, all you should have to do is add this property to your SOAPProxy action:
<property name="wsdlCharset" value="Cp1251"/>
I have tested the fix on both AS4+Java5 and AS5+Java6. I also ran a clean integration build.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/540614#540614]
Start a new discussion in JBoss ESB Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 11 months
Re: [jboss-dev-forums] [jBPM Development] - JBPM-2537
by Huisheng Xu
Huisheng Xu [http://community.jboss.org/people/rebody] replied to the discussion
"JBPM-2537"
To view the discussion, visit: http://community.jboss.org/message/540581#540581
--------------------------------------------------------------
Hi Sebastian.
I am agree that timeout is very useful and it is necessary for TaskActivity and other Waitable Activities. But there are many situations to activate the Waitable Acitivity. the 'time out' situation is just one of these situations. So I want to find a way to handle all of them. There may be cancel() or interrupt() method with a 'state' argument, but not timeout().
For example, now we saw TimerImpl could complete a TaskActivity with timeout status. So we add a timeout() method in ExternalActivityBehaviour. Some days later, we want to let people cancel a TaskActivity by hande, does we need add a cancelByHuman() method in ExternalActivityBehaviour, too? And so on. If there are more cancel activity situations, does we need add more xxx() methods in ExternalActivityBehaviour?
So, in my opinion, we should make a better plan for how to handle these activity cancellation situations, not just add a timeout() method in ExternalActivityBehaviour.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/540581#540581]
Start a new discussion in jBPM Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 11 months