I am seeing the same warn in the log file, Here is what I have the connector configured in the server.xml,
<Connector SSLEnabled="true" address="${jboss.bind.address}" clientAuth="false" emptySessionPath="true" keystoreFile="${jboss.server.home.dir}/conf/local.keystore" keystorePass="123456" truststoreFile="${jboss.server.home.dir}/conf/local.keystore" maxHttpHeaderSize="8192" maxThreads="100" port="8443" protocol="HTTP/1.1" scheme="https" secure="true" sslProtocol="TLS" strategy="ms"/>
Thanks.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4156076#4156076
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4156076
I'm having problems with SOAP fault declaration from JOSSO. It is like this:
<wsdl:message name="IdentityProvisioningException">
<wsdl:part name="fault" type="impl:IdentityProvisioningException" />
</wsdl:message>
The problem is 'type' attribute which according to WS-Basic Profile http://www.ws-i.org/Profiles/BasicProfile-1.1-2004-08-24.html#Bindings_an....
So 'type' should be replaced by 'element' attribute. The warning message from WCF SvcUtil is:
Warning: Fault named IdentityProvisioningException in operation resolveAuthenticationAssertion cannot be imported. Unsup
ported WSDL, the fault message part must reference an element. This fault message does not reference an element. If you
have edit access to the WSDL document, you can fix the problem by referencing a schema element using the 'element' attri
bute.
And I don't know where to start with this problem. Is is JBoss issue (Ws-BP is supported here I think), JOSSO issue or WCF problem?
Thanks in advance.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4155885#4155885
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4155885
It's the JAXWS API that uses a service loader mechanism to pull the implementation. You have to make sure that WS invocation don't have the Sun API (jaxws-rt.jar, jaxws-tools.jar, jaxws-api.jar) on the classpath. JBossWS ships with it's own impl. of the API wich then delegates to the correct provider implementation: jboss-jaxws.jar
It's a little tricky to get both tooling and web service invocations into the project, because tooling still requires those jars mentioned above.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4155882#4155882
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4155882