[Design of JBoss internal QA (Test Suite)] - Re: SSLUnitTestCase failures with the IBM JVM
by mwringe
The keystore type is not pksc12 (its JKS). This is the SSLUnitTestCase from the testsuite, no other changes have been made it. This test passes when the Sun JDK is used, but always fails when the IBM jdk is used.
The only change I have done is adding algorithm=IbmX509 to the server.xml of the jbossweb-tomcat55.sar (none of the other suggestions have worked). This at least allows the server to start without error.
But I am still geting the protocol version error when the tests are run
| Testcase: testHttps took 0.017 sec
| Caused an ERROR
| protocol version
| javax.net.ssl.SSLHandshakeException: protocol version
| at com.ibm.jsse.bv.a(Unknown Source)
| at com.ibm.jsse.b.a(Unknown Source)
| at com.ibm.jsse.b.write(Unknown Source)
| at org.apache.commons.httpclient.HttpConnection$WrappedOutputStream.write(HttpConnection.java:1360)
| at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:86)
| at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:144)
| at org.apache.commons.httpclient.HttpConnection.flushRequestOutputStream(HttpConnection.java:790)
| at org.apache.commons.httpclient.HttpMethodBase.writeRequest(HttpMethodBase.java:2271)
| at org.apache.commons.httpclient.HttpMethodBase.processRequest(HttpMethodBase.java:2651)
| at org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:1087)
| at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:643)
| at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:497)
| at org.jboss.test.web.test.ssl.SSLUnitTestCase.doHttps(SSLUnitTestCase.java:117)
| at org.jboss.test.web.test.ssl.SSLUnitTestCase.testHttps(SSLUnitTestCase.java:77)
| at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
| at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
| at junit.extensions.TestSetup.run(TestSetup.java:23)
|
Any more help on this would be greatly appreciated
PS: java.net.debug does not give nearly as much information when the IBM jvm is used
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968242#3968242
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3968242
18 years, 2 months
[Design of JBoss jBPM] - Re: web services question
by alex.guizar＠jboss.com
Ronald,
Adding a new operation per command is fine; I wanted to confirm it was the approach you were following. The only alternative I can think of is a message-style endpoint. That option would take us back to deal with SOAP elements ourselves, tough.
We can do the "overloading" with the document bare approach. The command will be a single structure instead of individual parameters. By wrapping related optional parameters in separate elements, you can easily tell the 'overload' of the command being requested in the service implementation bean:
class StartProcessCommand {
| ProcessDefinitionInfo processDefinition;
| VariablesInfo variables;
| }
|
| class CommandServiceImplBean {
|
| public void startProcess(StartProcessCommand command) {
| ProcessInstance pi;
|
| if (command.variables == null)
| pi = jbpmContext.newProcessInstance(command.processDefinition.name);
| else
| pi = jbpmContext.newProcessInstance(command.processDefinition.name,
| command.variables.toMap());
|
| pi.signal();
| }
| }
The above snippet is pseudocode, but you get the idea. I do not see a good reason to use the command facility as opposed to invoking operations in the jbpm context directly either.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968200#3968200
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3968200
18 years, 2 months
