[JBossWS] - Re: How to register SerializerFactory and DeSerializerFactor
by thomas.dieslerï¼ jboss.com
This change might work for you
|
| public EncodedTypeMapping()
| {
| registerStandardLiteralTypes();
| registerStandardSOAP11EncodedTypes();
|
| // register mapping for xsd:anyType
| register(SOAPElement.class, Constants.TYPE_LITERAL_ANYTYPE, new SOAPElementSerializerFactory(), new SOAPElementDeserializerFactory());
| register(Element.class, Constants.TYPE_LITERAL_ANYTYPE, new ElementSerializerFactory(), new ElementDeserializerFactory());
|
| // register mapping for soap11-enc:anyType
| register(SOAPElement.class, Constants.TYPE_SOAP11_ANYTYPE, new SOAPElementSerializerFactory(), new SOAPElementDeserializerFactory());
| register(Element.class, Constants.TYPE_SOAP11_ANYTYPE, new ElementSerializerFactory(), new ElementDeserializerFactory());
| }
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4033019#4033019
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4033019
19Â years
[Messaging, JMS & JBossMQ] - MQ over SSL
by jbarrancos
Hello,
Our IBM MQ's are being reconfigured for SSL. Now we wanted to enable this under JBoss and do it the same way as in WebSphere, by adding the sslCipherSuite attribute. We tried it as shown below in the Factory:
| <server>
| <mbean code="jmx.service.wsmq.WSMQConnectionFactory"
| name="jmx.service.wsmq:service=FuturoscoopVaredocsQueueConnectionFactory">
| <attribute name="JndiName">jms/FUTUROSCOOP/QueueConnectionFactory</attribute>
| <attribute name="JMSStyle">Queue</attribute>
| <attribute name="IsXA">false</attribute>
| <attribute name="QueueManagerName">MQACC</attribute>
| <attribute name="HostName">mq.acc.bank.local</attribute>
| <attribute name="Port">1414</attribute>
| <attribute name="Channel">SVR_PARIS_ACC</attribute>
| <attribute name="TransportType">MQJMS_TP_CLIENT_MQ_TCPIP</attribute>
| <attribute name="sslCipherSuite">SSL_RSA_WITH_3DES_EDE_CBC_SHA</attribute> <depends>jboss:service=Naming</depends>
| </mbean>
| </server>
|
But the following error will be shown in the logs:
2007-03-27 11:10:22,946 INFO [ScannerThread] [org.jboss.system.ServiceConfigurator] Problem configuring service jmx.service.wsmq:service=FuturoscoopVaredocsQueueConnectionFactory
org.jboss.deployment.DeploymentException: No Attribute found with name: sslCipherSuite
....
How do we configure the sslCipherSuite (sslCipherSpec) variable within the MQ Configuration to enable SSL.
Thanks!
Jordy
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4033018#4033018
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4033018
19Â years
[JBossWS] - Name of generated exception class
by magnus.ahlander
In my endpoint implementation I have a user-defined exception thrown by some operations. The generated wsdl then looks something like:
...
| <xs:complexType name='AuthorizationException'>
| <xs:sequence>
| <xs:element minOccurs='0' name='message' type='xs:string'/>
| </xs:sequence>
| </xs:complexType>
| ...
| <operation name='read'>
| ...
| <fault name='AuthorizationException'>
| <soap:fault name='AuthorizationException' use='literal'/>
| </fault>
| </operation>
| ...
>From this wsdl wsconsume generates the following client-side artifacts:
AuthorizationException (jaxb type)
AuthorizationException_Exception (java exception)
In the client I then I then get some awkward code like
try {...}
| catch (AuthorizationException_Exception ex) {...}
To get around these problems I defined a custom jax-ws binding, which is then provided to wsconsume:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
| <bindings
| xmlns:xsd="http://www.w3.org/2001/XMLSchema"
| xmlns:jaxb="http://java.sun.com/xml/ns/jaxb"
| xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
| wsdlLocation="http://localhost:8080/static/test.wsdl"
| xmlns="http://java.sun.com/xml/ns/jaxws">
| <bindings node="wsdl:definitions">
| <package name="com.test"/>
| </bindings>
| <bindings node="wsdl:definitions/wsdl:types/xsd:schema[@targetNamespace='http://com.test']">
| <jaxb:schemaBindings>
| <jaxb:package name="com.test.jaxb"/>
| </jaxb:schemaBindings>
| </bindings>
| </bindings>
basically this puts jaxws and jaxb generated artifacts into separate packages.
However, this works only if I remove the 'package' attribute from the wsconsume task. From this I conclude that the 'package' attribute takes precedence over any custom bindings. Why is this so?
Is there any other way to get nice exception class names with wsconsume?
Regards,
Magnus
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4033007#4033007
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4033007
19Â years