[JBossWS] - Re: jbossws1.0.x is a preview implementation with support fo
by bocio
"maeste" wrote :
| IMHO opinion jboss still the best AS on the market. And I mean the best one, not the best open source.
| I started to use jboss since 2.0 (first production environment 2.4.1) and I read forums and ML since the beginning. I agree with you, a lot of things changed, community is changed (more noise) and jboss' staff become more and more busy.
|
I 100% agree
"maeste" wrote :
| Before someone other of the staff will tell you: The only sure way to get immediately feed back is the professional support. The community support is not so responsive, and mainly intend for guys wearing "engineer white coat". :)
|
I know but here I definitively go OT ;-) Inside my company we have so many websphere installations that we pay ibm just flat-rate. I could install how much websphere as I would. So price is not a problem. Even so up to now my group was able to mantain a little entrenched JBoss Island. Now would be impossible for me to ask for a professional support while we have two ibm guys free of charge all the year inside the company. So my island must be self contained :-)
"maeste" wrote :
| Next days we have to implement ws clients and I'll keep you post of our result or problem. Well the goal of project is 2nd quarter 07 and I don't exclude to use jbossws 2.0CR
|
I'll look forward to hear about your tests
Bye
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3989626#3989626
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3989626
17 years, 5 months
[JBossWS] - Re: jbossws1.0.x is a preview implementation with support fo
by maeste
I didn' want to start a flame. In fact I didn't understand you refer to client. It seems to have trouble, we don't use it except in some little use case. We works mainly on the server side.
IMHO opinion jboss still the best AS on the market. And I mean the best one, not the best open source.
I started to use jboss since 2.0 (first production environment 2.4.1) and I read forums and ML since the beginning. I agree with you, a lot of things changed, community is changed (more noise) and jboss' staff become more and more busy.
Before someone other of the staff will tell you: The only sure way to get immediately feed back is the professional support. The community support is not so responsive, and mainly intend for guys wearing "engineer white coat". :)
This is just my humble opinion, my impression and I'm just a user like you...really passionated end user.
Next days we have to implement ws clients and I'll keep you post of our result or problem. Well the goal of project is 2nd quarter 07 and I don't exclude to use jbossws 2.0CR
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3989592#3989592
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3989592
17 years, 5 months
[JBossWS] - Re: Exception with JBoss-4.0.5-SP1 and JBossWS-1.0.3-SP1 but
by lafr
I enabled DEBUG for org.jboss.ws and got this:
2006-11-28 23:45:49,480 DEBUG [org.jboss.ws.server.StandardEndpointServlet] doPost: /mbi-ws/mbi2e-lafr-sb2000-ipc/core/MessageServic
| eWS
| 2006-11-28 23:45:49,488 DEBUG [org.jboss.ws.soap.MessageContextAssociation] pushMessageContext: org.jboss.ws.soap.SOAPMessageContext
| Impl@171cb85
| 2006-11-28 23:45:49,525 DEBUG [org.jboss.ws.server.ServiceEndpoint] BEGIN handleRequest: jboss.ws:context=mbi-ws/mbi2e-lafr-sb2000-i
| pc/core,endpoint=MessageServiceWS
| 2006-11-28 23:45:49,525 DEBUG [org.jboss.ws.server.ServiceEndpoint] Init handler chain with [0] handlers
| 2006-11-28 23:45:49,547 DEBUG [org.jboss.ws.handler.HandlerChainBaseImpl] Create a handler chain for roles: []
| 2006-11-28 23:45:49,547 DEBUG [org.jboss.ws.handler.HandlerChainBaseImpl] init: [config=null]
| 2006-11-28 23:45:49,548 DEBUG [org.jboss.ws.server.ServiceEndpoint] Init handler chain with [0] handlers
| 2006-11-28 23:45:49,548 DEBUG [org.jboss.ws.handler.HandlerChainBaseImpl] Create a handler chain for roles: []
| 2006-11-28 23:45:49,548 DEBUG [org.jboss.ws.handler.HandlerChainBaseImpl] init: [config=null]
| 2006-11-28 23:45:49,548 DEBUG [org.jboss.ws.server.ServiceEndpoint] Init handler chain with [0] handlers
| 2006-11-28 23:45:49,548 DEBUG [org.jboss.ws.handler.HandlerChainBaseImpl] Create a handler chain for roles: []
| 2006-11-28 23:45:49,548 DEBUG [org.jboss.ws.handler.HandlerChainBaseImpl] init: [config=null]
| 2006-11-28 23:45:49,568 DEBUG [org.jboss.ws.soap.MessageFactoryImpl] createMessage: [contentType=text/xml]
| 2006-11-28 23:45:49,693 DEBUG [org.jboss.ws.soap.SOAPContentElement] setXMLFragment: <MessageHead_1><businessProcessId>3</businessPr
| ocessId><hostname>sb2000</hostname><isoLanguageId>de</isoLanguageId><isoLanguageIdDef/><loginBezCreated>mbi</loginBezCreated><messag
| eId>0</messageId><processId>26848</processId><sessionId>763</sessionId><status>0</status><timeCreated>2006-11-28 23:45:49</timeCreat
| ed></MessageHead_1>
| 2006-11-28 23:45:49,694 DEBUG [org.jboss.ws.soap.SOAPContentElement] setXMLFragment: <MessagePart_2><additionalData/><businessProces
| sTaskId>1</businessProcessTaskId><line>3573</line><messageLines><lineOfText>Start Reorganisation mit folgenden Funktionen:</lineOfTe
| xt></messageLines><messageLines><lineOfText>- L\303\266schen Bestellvorschl\303\244ge</lineOfText></messageLines><messageLines><line
| OfText>- L\303\266schen Propositionskonto, Bestellvorschl\303\244ge -> Neuaufbau</lineOfText></messageLines><messageLines><lineOf
| Text>- Neuaufbau - Dispokonto (mbi_dispo, dispo_serial)</lineOfText></messageLines><messageLines><lineOfText>- Neuaufbau Bedarfsdec
| ker - Dispokonto (mbi_dispo, dispo_serial)</lineOfText></messageLines><messageLines><lineOfText>- Neuaufbau Reservierungen aus Lager
| best\303\244nden (mbi_dires)</lineOfText></messageLines><messageLines><lineOfText>- Neuaufbau Reservierungen aus Fertigungsauft
| r\303\244gen (mbi_dires)</lineOfText></messageLines><messageLines><lineOfText>- Neuaufbau Reservierungen aus Nachbearbeitung (mb
| i_dires)</lineOfText></messageLines><messageLines><lineOfText>- Neuaufbau Reservierungen aus Bestellungen (mbi_dires)</lineOf
| Text></messageLines><messageLines><lineOfText>- Neuaufbau Reservierungen aus Vorabdispo -> Neuaufbau BV</lineOfText></messageLine
| s><messageLines><lineOfText>- Neuaufbau Reservierungen aus Transport (mbi_dires)</lineOfText></messageLines><messageLines>
| <lineOfText>- Anonymisieren Bedarfsdecker</lineOfText></messageLines><messageType/><source>mbi_proini.ec</source><timeCreated>2006-1
| 1-28 23:45:49</timeCreated></MessagePart_2>
| 2006-11-28 23:45:49,717 DEBUG [org.jboss.ws.soap.SOAPMessageDispatcher] getDispatchDestination: {http://core.ws.fn.mbisoftware.biz}c
| reateMultiInfo
| 2006-11-28 23:45:49,735 DEBUG [org.jboss.ws.binding.soap.SOAPBindingProvider] unbindRequestMessage: {http://core.ws.fn.mbisoftware.b
| iz}createMultiInfo
| 2006-11-28 23:45:49,741 DEBUG [org.jboss.ws.binding.EndpointInvocation] setRequestParamValue: [name=MessageHead_1,value=org.jboss.ws
| .soap.SOAPContentElement]
| 2006-11-28 23:45:49,741 DEBUG [org.jboss.ws.binding.EndpointInvocation] setRequestParamValue: [name=MessagePart_2,value=org.jboss.ws
| .soap.SOAPContentElement]
| 2006-11-28 23:45:49,742 DEBUG [org.jboss.ws.metadata.OperationMetaData] Get java method for: {http://core.ws.fn.mbisoftware.biz}crea
| teMultiInfo
| 2006-11-28 23:45:49,748 DEBUG [org.jboss.ws.metadata.OperationMetaData] Found best matching java method: public abstract biz.mbisoft
| ware.fn.wstypes.ServiceIntegerResponse biz.mbisoftware.fn.ws.core.MessageServiceWSI.createMultiInfo(biz.mbisoftware.fn.wstypes.core.
| MessageHead,biz.mbisoftware.fn.wstypes.core.MessagePart) throws java.rmi.RemoteException
| 2006-11-28 23:45:49,748 DEBUG [org.jboss.ws.server.ServiceEndpointInvokerJSE] invokeServiceEndpoint: createMultiInfo
| 2006-11-28 23:45:49,749 DEBUG [org.jboss.ws.binding.EndpointInvocation] getRequestPayload
| 2006-11-28 23:45:49,750 DEBUG [org.jboss.ws.binding.EndpointInvocation] getRequestParamValue: MessageHead_1
| 2006-11-28 23:45:49,750 DEBUG [org.jboss.ws.soap.SOAPContentElement] getObjectValue [xmlType={http://core.ws.fn.mbisoftware.biz}Mess
| ageHead,javaType=class biz.mbisoftware.fn.wstypes.core.MessageHead]
| 2006-11-28 23:45:49,764 DEBUG [org.jboss.ws.jaxrpc.encoding.JAXBDeserializer] deserialize: [xmlName=MessageHead_1,xmlType={http://co
| re.ws.fn.mbisoftware.biz}MessageHead]
| 2006-11-28 23:45:50,110 DEBUG [org.jboss.ws.server.ServiceEndpoint] END handleRequest: jboss.ws:context=mbi-ws/mbi2e-lafr-sb2000-ipc
| /core,endpoint=MessageServiceWS
| 2006-11-28 23:45:50,124 DEBUG [org.jboss.ws.soap.MessageContextAssociation] popMessageContext: org.jboss.ws.soap.SOAPMessageContextI
| mpl@171cb85
| 2006-11-28 23:45:50,128 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/mbi-ws/mbi2e-lafr-sb2000-ipc/core].[
| MessageServiceWS]] Servlet.service() for servlet MessageServiceWS threw exception
| java.lang.ExceptionInInitializerError
| at java.lang.Class.forName0(Native Method)
| at java.lang.Class.forName(Class.java:164)
| ...
|
My wsdl file generated with jwsdp-2.0:
<?xml version="1.0" encoding="UTF-8"?>
|
| <definitions name="MessageServiceWS" targetNamespace="http://core.ws.fn.mbisoftware.biz" xmlns:tns="http://core.ws.fn.mbisoftware.biz" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/">
| <types>
| <schema targetNamespace="http://core.ws.fn.mbisoftware.biz" xmlns:tns="http://core.ws.fn.mbisoftware.biz" xmlns:soap11-enc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns="http://www.w3.org/2001/XMLSchema">
| <complexType name="MessagePart">
| <sequence>
| <element name="additionalData" type="string" nillable="true"/>
| <element name="businessProcessTaskId" type="int" nillable="true"/>
| <element name="line" type="int" nillable="true"/>
| <element name="messageLines" type="tns:MessageLine" nillable="true" minOccurs="0" maxOccurs="unbounded"/>
| <element name="messageType" type="string" nillable="true"/>
| <element name="source" type="string" nillable="true"/>
| <element name="timeCreated" type="string" nillable="true"/></sequence></complexType>
| <complexType name="MessageLine">
| <sequence>
| <element name="lineOfText" type="string" nillable="true"/></sequence></complexType>
| <complexType name="ServiceResponse">
| <sequence>
| <element name="errorCode" type="int" nillable="true"/>
| <element name="errorMessages" type="string" nillable="true" minOccurs="0" maxOccurs="unbounded"/>
| <element name="numRowsError" type="int" nillable="true"/>
| <element name="numRowsSuccess" type="int" nillable="true"/>
| <element name="numRowsWarning" type="int" nillable="true"/>
| <element name="successMessages" type="string" nillable="true" minOccurs="0" maxOccurs="unbounded"/>
| <element name="warnMessages" type="string" nillable="true" minOccurs="0" maxOccurs="unbounded"/></sequence></complexType>
| <complexType name="ServiceIntegerResponse">
| <complexContent>
| <extension base="tns:ServiceResponse">
| <sequence>
| <element name="value" type="int" nillable="true"/></sequence></extension></complexContent></complexType>
| <complexType name="MessagePartResponse">
| <complexContent>
| <extension base="tns:ServiceResponse">
| <sequence>
| <element name="messagePart" type="tns:MessagePart" nillable="true"/></sequence></extension></complexContent></complexType>
| <complexType name="MessageHeadResponse">
| <complexContent>
| <extension base="tns:ServiceResponse">
| <sequence>
| <element name="messageHead" type="tns:MessageHead" nillable="true"/></sequence></extension></complexContent></complexType>
| <complexType name="MessageHead">
| <sequence>
| <element name="businessProcessId" type="int" nillable="true"/>
| <element name="hostname" type="string" nillable="true"/>
| <element name="isoLanguageId" type="string" nillable="true"/>
| <element name="isoLanguageIdDef" type="string" nillable="true"/>
| <element name="loginBezCreated" type="string" nillable="true"/>
| <element name="messageId" type="int" nillable="true"/>
| <element name="messageParts" type="tns:MessagePart" nillable="true" minOccurs="0" maxOccurs="unbounded"/>
| <element name="processId" type="int" nillable="true"/>
| <element name="sessionId" type="int" nillable="true"/>
| <element name="status" type="int" nillable="true"/>
| <element name="timeCreated" type="string" nillable="true"/></sequence></complexType>
| <complexType name="ServiceStringResponse">
| <complexContent>
| <extension base="tns:ServiceResponse">
| <sequence>
| <element name="value" type="string" nillable="true"/></sequence></extension></complexContent></complexType>
| <complexType name="LanguageCodes">
| <sequence>
| <element name="codes" type="string" nillable="true" minOccurs="0" maxOccurs="unbounded"/></sequence></complexType></schema></types>
| <message name="MessageServiceWSI_appendDebug">
| <part name="Integer_1" type="xsd:int"/>
| <part name="MessagePart_2" type="tns:MessagePart"/></message>
| <message name="MessageServiceWSI_appendDebugResponse">
| <part name="result" type="tns:ServiceResponse"/></message>
| <message name="MessageServiceWSI_appendError">
| <part name="Integer_1" type="xsd:int"/>
| <part name="MessagePart_2" type="tns:MessagePart"/></message>
| <message name="MessageServiceWSI_appendErrorResponse">
| <part name="result" type="tns:ServiceResponse"/></message>
| <message name="MessageServiceWSI_appendFatal">
| <part name="Integer_1" type="xsd:int"/>
| <part name="MessagePart_2" type="tns:MessagePart"/></message>
| <message name="MessageServiceWSI_appendFatalResponse">
| <part name="result" type="tns:ServiceResponse"/></message>
| <message name="MessageServiceWSI_appendInfo">
| <part name="Integer_1" type="xsd:int"/>
| <part name="MessagePart_2" type="tns:MessagePart"/></message>
| <message name="MessageServiceWSI_appendInfoResponse">
| <part name="result" type="tns:ServiceResponse"/></message>
| <message name="MessageServiceWSI_appendWarn">
| <part name="Integer_1" type="xsd:int"/>
| <part name="MessagePart_2" type="tns:MessagePart"/></message>
| <message name="MessageServiceWSI_appendWarnResponse">
| <part name="result" type="tns:ServiceResponse"/></message>
| <message name="MessageServiceWSI_createMultiDebug">
| <part name="MessageHead_1" type="tns:MessageHead"/>
| <part name="MessagePart_2" type="tns:MessagePart"/></message>
| <message name="MessageServiceWSI_createMultiDebugResponse">
| <part name="result" type="tns:ServiceIntegerResponse"/></message>
| <message name="MessageServiceWSI_createMultiError">
| <part name="MessageHead_1" type="tns:MessageHead"/>
| <part name="MessagePart_2" type="tns:MessagePart"/></message>
| <message name="MessageServiceWSI_createMultiErrorResponse">
| <part name="result" type="tns:ServiceIntegerResponse"/></message>
| <message name="MessageServiceWSI_createMultiFatal">
| <part name="MessageHead_1" type="tns:MessageHead"/>
| <part name="MessagePart_2" type="tns:MessagePart"/></message>
| <message name="MessageServiceWSI_createMultiFatalResponse">
| <part name="result" type="tns:ServiceIntegerResponse"/></message>
| <message name="MessageServiceWSI_createMultiInfo">
| <part name="MessageHead_1" type="tns:MessageHead"/>
| <part name="MessagePart_2" type="tns:MessagePart"/></message>
| <message name="MessageServiceWSI_createMultiInfoResponse">
| <part name="result" type="tns:ServiceIntegerResponse"/></message>
| <message name="MessageServiceWSI_createMultiWarn">
| <part name="MessageHead_1" type="tns:MessageHead"/>
| <part name="MessagePart_2" type="tns:MessagePart"/></message>
| <message name="MessageServiceWSI_createMultiWarnResponse">
| <part name="result" type="tns:ServiceIntegerResponse"/></message>
| <message name="MessageServiceWSI_createSingleDebug">
| <part name="MessageHead_1" type="tns:MessageHead"/>
| <part name="MessagePart_2" type="tns:MessagePart"/></message>
| <message name="MessageServiceWSI_createSingleDebugResponse">
| <part name="result" type="tns:ServiceIntegerResponse"/></message>
| <message name="MessageServiceWSI_createSingleError">
| <part name="MessageHead_1" type="tns:MessageHead"/>
| <part name="MessagePart_2" type="tns:MessagePart"/></message>
| <message name="MessageServiceWSI_createSingleErrorResponse">
| <part name="result" type="tns:ServiceIntegerResponse"/></message>
| <message name="MessageServiceWSI_createSingleFatal">
| <part name="MessageHead_1" type="tns:MessageHead"/>
| <part name="MessagePart_2" type="tns:MessagePart"/></message>
| <message name="MessageServiceWSI_createSingleFatalResponse">
| <part name="result" type="tns:ServiceIntegerResponse"/></message>
| <message name="MessageServiceWSI_createSingleInfo">
| <part name="MessageHead_1" type="tns:MessageHead"/>
| <part name="MessagePart_2" type="tns:MessagePart"/></message>
| <message name="MessageServiceWSI_createSingleInfoResponse">
| <part name="result" type="tns:ServiceIntegerResponse"/></message>
| <message name="MessageServiceWSI_createSingleWarn">
| <part name="MessageHead_1" type="tns:MessageHead"/>
| <part name="MessagePart_2" type="tns:MessagePart"/></message>
| <message name="MessageServiceWSI_createSingleWarnResponse">
| <part name="result" type="tns:ServiceIntegerResponse"/></message>
| <message name="MessageServiceWSI_getMessageHead">
| <part name="Integer_1" type="xsd:int"/></message>
| <message name="MessageServiceWSI_getMessageHeadResponse">
| <part name="result" type="tns:MessageHeadResponse"/></message>
| <message name="MessageServiceWSI_getMessagePart">
| <part name="Integer_1" type="xsd:int"/>
| <part name="Integer_2" type="xsd:int"/></message>
| <message name="MessageServiceWSI_getMessagePartResponse">
| <part name="result" type="tns:MessagePartResponse"/></message>
| <message name="MessageServiceWSI_getMessagePartsAdditionalDataAsHtml">
| <part name="Integer_1" type="xsd:int"/>
| <part name="Integer_2" type="xsd:int"/>
| <part name="LanguageCodes_3" type="tns:LanguageCodes"/></message>
| <message name="MessageServiceWSI_getMessagePartsAdditionalDataAsHtmlResponse">
| <part name="result" type="tns:ServiceStringResponse"/></message>
| <message name="MessageServiceWSI_setRecipient">
| <part name="Integer_1" type="xsd:int"/>
| <part name="Integer_2" type="xsd:int"/></message>
| <message name="MessageServiceWSI_setRecipientResponse">
| <part name="result" type="tns:ServiceResponse"/></message>
| <message name="MessageServiceWSI_setStateReady">
| <part name="Integer_1" type="xsd:int"/></message>
| <message name="MessageServiceWSI_setStateReadyResponse">
| <part name="result" type="tns:ServiceResponse"/></message>
| <portType name="MessageServiceWSI">
| <operation name="appendDebug" parameterOrder="Integer_1 MessagePart_2">
| <input message="tns:MessageServiceWSI_appendDebug"/>
| <output message="tns:MessageServiceWSI_appendDebugResponse"/></operation>
| <operation name="appendError" parameterOrder="Integer_1 MessagePart_2">
| <input message="tns:MessageServiceWSI_appendError"/>
| <output message="tns:MessageServiceWSI_appendErrorResponse"/></operation>
| <operation name="appendFatal" parameterOrder="Integer_1 MessagePart_2">
| <input message="tns:MessageServiceWSI_appendFatal"/>
| <output message="tns:MessageServiceWSI_appendFatalResponse"/></operation>
| <operation name="appendInfo" parameterOrder="Integer_1 MessagePart_2">
| <input message="tns:MessageServiceWSI_appendInfo"/>
| <output message="tns:MessageServiceWSI_appendInfoResponse"/></operation>
| <operation name="appendWarn" parameterOrder="Integer_1 MessagePart_2">
| <input message="tns:MessageServiceWSI_appendWarn"/>
| <output message="tns:MessageServiceWSI_appendWarnResponse"/></operation>
| <operation name="createMultiDebug" parameterOrder="MessageHead_1 MessagePart_2">
| <input message="tns:MessageServiceWSI_createMultiDebug"/>
| <output message="tns:MessageServiceWSI_createMultiDebugResponse"/></operation>
| <operation name="createMultiError" parameterOrder="MessageHead_1 MessagePart_2">
| <input message="tns:MessageServiceWSI_createMultiError"/>
| <output message="tns:MessageServiceWSI_createMultiErrorResponse"/></operation>
| <operation name="createMultiFatal" parameterOrder="MessageHead_1 MessagePart_2">
| <input message="tns:MessageServiceWSI_createMultiFatal"/>
| <output message="tns:MessageServiceWSI_createMultiFatalResponse"/></operation>
| <operation name="createMultiInfo" parameterOrder="MessageHead_1 MessagePart_2">
| <input message="tns:MessageServiceWSI_createMultiInfo"/>
| <output message="tns:MessageServiceWSI_createMultiInfoResponse"/></operation>
| <operation name="createMultiWarn" parameterOrder="MessageHead_1 MessagePart_2">
| <input message="tns:MessageServiceWSI_createMultiWarn"/>
| <output message="tns:MessageServiceWSI_createMultiWarnResponse"/></operation>
| <operation name="createSingleDebug" parameterOrder="MessageHead_1 MessagePart_2">
| <input message="tns:MessageServiceWSI_createSingleDebug"/>
| <output message="tns:MessageServiceWSI_createSingleDebugResponse"/></operation>
| <operation name="createSingleError" parameterOrder="MessageHead_1 MessagePart_2">
| <input message="tns:MessageServiceWSI_createSingleError"/>
| <output message="tns:MessageServiceWSI_createSingleErrorResponse"/></operation>
| <operation name="createSingleFatal" parameterOrder="MessageHead_1 MessagePart_2">
| <input message="tns:MessageServiceWSI_createSingleFatal"/>
| <output message="tns:MessageServiceWSI_createSingleFatalResponse"/></operation>
| <operation name="createSingleInfo" parameterOrder="MessageHead_1 MessagePart_2">
| <input message="tns:MessageServiceWSI_createSingleInfo"/>
| <output message="tns:MessageServiceWSI_createSingleInfoResponse"/></operation>
| <operation name="createSingleWarn" parameterOrder="MessageHead_1 MessagePart_2">
| <input message="tns:MessageServiceWSI_createSingleWarn"/>
| <output message="tns:MessageServiceWSI_createSingleWarnResponse"/></operation>
| <operation name="getMessageHead" parameterOrder="Integer_1">
| <input message="tns:MessageServiceWSI_getMessageHead"/>
| <output message="tns:MessageServiceWSI_getMessageHeadResponse"/></operation>
| <operation name="getMessagePart" parameterOrder="Integer_1 Integer_2">
| <input message="tns:MessageServiceWSI_getMessagePart"/>
| <output message="tns:MessageServiceWSI_getMessagePartResponse"/></operation>
| <operation name="getMessagePartsAdditionalDataAsHtml" parameterOrder="Integer_1 Integer_2 LanguageCodes_3">
| <input message="tns:MessageServiceWSI_getMessagePartsAdditionalDataAsHtml"/>
| <output message="tns:MessageServiceWSI_getMessagePartsAdditionalDataAsHtmlResponse"/></operation>
| <operation name="setRecipient" parameterOrder="Integer_1 Integer_2">
| <input message="tns:MessageServiceWSI_setRecipient"/>
| <output message="tns:MessageServiceWSI_setRecipientResponse"/></operation>
| <operation name="setStateReady" parameterOrder="Integer_1">
| <input message="tns:MessageServiceWSI_setStateReady"/>
| <output message="tns:MessageServiceWSI_setStateReadyResponse"/></operation></portType>
| <binding name="MessageServiceWSIBinding" type="tns:MessageServiceWSI">
| <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="rpc"/>
| <operation name="appendDebug">
| <soap:operation soapAction=""/>
| <input>
| <soap:body use="literal" namespace="http://core.ws.fn.mbisoftware.biz"/></input>
| <output>
| <soap:body use="literal" namespace="http://core.ws.fn.mbisoftware.biz"/></output></operation>
| <operation name="appendError">
| <soap:operation soapAction=""/>
| <input>
| <soap:body use="literal" namespace="http://core.ws.fn.mbisoftware.biz"/></input>
| <output>
| <soap:body use="literal" namespace="http://core.ws.fn.mbisoftware.biz"/></output></operation>
| <operation name="appendFatal">
| <soap:operation soapAction=""/>
| <input>
| <soap:body use="literal" namespace="http://core.ws.fn.mbisoftware.biz"/></input>
| <output>
| <soap:body use="literal" namespace="http://core.ws.fn.mbisoftware.biz"/></output></operation>
| <operation name="appendInfo">
| <soap:operation soapAction=""/>
| <input>
| <soap:body use="literal" namespace="http://core.ws.fn.mbisoftware.biz"/></input>
| <output>
| <soap:body use="literal" namespace="http://core.ws.fn.mbisoftware.biz"/></output></operation>
| <operation name="appendWarn">
| <soap:operation soapAction=""/>
| <input>
| <soap:body use="literal" namespace="http://core.ws.fn.mbisoftware.biz"/></input>
| <output>
| <soap:body use="literal" namespace="http://core.ws.fn.mbisoftware.biz"/></output></operation>
| <operation name="createMultiDebug">
| <soap:operation soapAction=""/>
| <input>
| <soap:body use="literal" namespace="http://core.ws.fn.mbisoftware.biz"/></input>
| <output>
| <soap:body use="literal" namespace="http://core.ws.fn.mbisoftware.biz"/></output></operation>
| <operation name="createMultiError">
| <soap:operation soapAction=""/>
| <input>
| <soap:body use="literal" namespace="http://core.ws.fn.mbisoftware.biz"/></input>
| <output>
| <soap:body use="literal" namespace="http://core.ws.fn.mbisoftware.biz"/></output></operation>
| <operation name="createMultiFatal">
| <soap:operation soapAction=""/>
| <input>
| <soap:body use="literal" namespace="http://core.ws.fn.mbisoftware.biz"/></input>
| <output>
| <soap:body use="literal" namespace="http://core.ws.fn.mbisoftware.biz"/></output></operation>
| <operation name="createMultiInfo">
| <soap:operation soapAction=""/>
| <input>
| <soap:body use="literal" namespace="http://core.ws.fn.mbisoftware.biz"/></input>
| <output>
| <soap:body use="literal" namespace="http://core.ws.fn.mbisoftware.biz"/></output></operation>
| <operation name="createMultiWarn">
| <soap:operation soapAction=""/>
| <input>
| <soap:body use="literal" namespace="http://core.ws.fn.mbisoftware.biz"/></input>
| <output>
| <soap:body use="literal" namespace="http://core.ws.fn.mbisoftware.biz"/></output></operation>
| <operation name="createSingleDebug">
| <soap:operation soapAction=""/>
| <input>
| <soap:body use="literal" namespace="http://core.ws.fn.mbisoftware.biz"/></input>
| <output>
| <soap:body use="literal" namespace="http://core.ws.fn.mbisoftware.biz"/></output></operation>
| <operation name="createSingleError">
| <soap:operation soapAction=""/>
| <input>
| <soap:body use="literal" namespace="http://core.ws.fn.mbisoftware.biz"/></input>
| <output>
| <soap:body use="literal" namespace="http://core.ws.fn.mbisoftware.biz"/></output></operation>
| <operation name="createSingleFatal">
| <soap:operation soapAction=""/>
| <input>
| <soap:body use="literal" namespace="http://core.ws.fn.mbisoftware.biz"/></input>
| <output>
| <soap:body use="literal" namespace="http://core.ws.fn.mbisoftware.biz"/></output></operation>
| <operation name="createSingleInfo">
| <soap:operation soapAction=""/>
| <input>
| <soap:body use="literal" namespace="http://core.ws.fn.mbisoftware.biz"/></input>
| <output>
| <soap:body use="literal" namespace="http://core.ws.fn.mbisoftware.biz"/></output></operation>
| <operation name="createSingleWarn">
| <soap:operation soapAction=""/>
| <input>
| <soap:body use="literal" namespace="http://core.ws.fn.mbisoftware.biz"/></input>
| <output>
| <soap:body use="literal" namespace="http://core.ws.fn.mbisoftware.biz"/></output></operation>
| <operation name="getMessageHead">
| <soap:operation soapAction=""/>
| <input>
| <soap:body use="literal" namespace="http://core.ws.fn.mbisoftware.biz"/></input>
| <output>
| <soap:body use="literal" namespace="http://core.ws.fn.mbisoftware.biz"/></output></operation>
| <operation name="getMessagePart">
| <soap:operation soapAction=""/>
| <input>
| <soap:body use="literal" namespace="http://core.ws.fn.mbisoftware.biz"/></input>
| <output>
| <soap:body use="literal" namespace="http://core.ws.fn.mbisoftware.biz"/></output></operation>
| <operation name="getMessagePartsAdditionalDataAsHtml">
| <soap:operation soapAction=""/>
| <input>
| <soap:body use="literal" namespace="http://core.ws.fn.mbisoftware.biz"/></input>
| <output>
| <soap:body use="literal" namespace="http://core.ws.fn.mbisoftware.biz"/></output></operation>
| <operation name="setRecipient">
| <soap:operation soapAction=""/>
| <input>
| <soap:body use="literal" namespace="http://core.ws.fn.mbisoftware.biz"/></input>
| <output>
| <soap:body use="literal" namespace="http://core.ws.fn.mbisoftware.biz"/></output></operation>
| <operation name="setStateReady">
| <soap:operation soapAction=""/>
| <input>
| <soap:body use="literal" namespace="http://core.ws.fn.mbisoftware.biz"/></input>
| <output>
| <soap:body use="literal" namespace="http://core.ws.fn.mbisoftware.biz"/></output></operation></binding>
| <service name="MessageServiceWS">
| <port name="MessageServiceWSIPort" binding="tns:MessageServiceWSIBinding">
| <soap:address location="@MBI_WS_URL@/core/MessageServiceWS"/></port></service></definitions>
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3989508#3989508
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3989508
17 years, 5 months
[JBossWS] - jboss-4.0.5 jbossws-1.0.3.SP1 deployment exceptions
by zurchman
I know you don't want to read long stack traces, so here's the synopsis:
jboss-4.0.5 has problems resolving three jbossws jars.
I've noticed several posts calling attention to this problem, but have not found references to any resolutions.
| 2006-11-28 14:18:13,260 DEBUG [org.jboss.deployment.MainDeployer] resolveLibraries: jaxb-api.jar activation.jar jsr173_1.0_api.jar jaxb1-impl.jar
|
I installed jboss-4.0.5 with the "jems-installer". The configuration is "ejb-clustered" and named "default".
Here are some relevant portions of the stack trace:
| 2006-11-28 14:18:12,668 DEBUG [org.jboss.deployment.JARDeployer] looking for nested deployments in : file:/usr/local/JBoss/jboss-4.0.5.GA/server/default/deploy/jbossws.sar/jaxb-impl.jar
| 2006-11-28 14:18:13,257 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] Added url: file:/usr/local/JBoss/jboss-4.0.5.GA/server/default/tmp/deploy/tmp8839jaxb-impl.jar, to ucl: org.jboss.mx.loading.UnifiedClassLoader3@12922f6{ url=file:/usr/local/JBoss/jboss-4.0.5.GA/server/default/deploy/jbossws.sar/ ,addedOrder=12}
| 2006-11-28 14:18:13,260 DEBUG [org.jboss.deployment.MainDeployer] resolveLibraries: jaxb-api.jar activation.jar jsr173_1.0_api.jar jaxb1-impl.jar
| 2006-11-28 14:18:13,260 DEBUG [org.jboss.deployment.MainDeployer] new manifest entry for sdi at jaxb-impl.jar entry is jaxb-api.jar
| 2006-11-28 14:18:13,260 DEBUG [org.jboss.deployment.MainDeployer] new manifest entry for sdi at jaxb-impl.jar entry is activation.jar
| 2006-11-28 14:18:13,267 DEBUG [org.jboss.deployment.MainDeployer] The manifest entry in file:/usr/local/JBoss/jboss-4.0.5.GA/server/default/deploy/jbossws.sar/jaxb-impl.jar references URL file:/usr/local/JBoss/jboss-4.0.5.GA/server/default/deploy/jbossws.sar/activation.jar which could not be opened, entry ignored
| 2006-11-28 14:18:13,277 DEBUG [org.jboss.util.NestedThrowable] org.jboss.util.NestedThrowable.parentTraceEnabled=true
| 2006-11-28 14:18:13,277 DEBUG [org.jboss.util.NestedThrowable] org.jboss.util.NestedThrowable.nestedTraceEnabled=false
| 2006-11-28 14:18:13,278 DEBUG [org.jboss.util.NestedThrowable] org.jboss.util.NestedThrowable.detectDuplicateNesting=true
| org.jboss.deployment.DeploymentException: url file:/usr/local/JBoss/jboss-4.0.5.GA/server/default/deploy/jbossws.sar/activation.jar could not be opened, does it exist?
| at org.jboss.deployment.DeploymentInfo.<init>(DeploymentInfo.java:214)
|
|
| 2006-11-28 14:18:13,285 DEBUG [org.jboss.deployment.MainDeployer] new manifest entry for sdi at jaxb-impl.jar entry is jsr173_1.0_api.jar
| 2006-11-28 14:18:13,285 DEBUG [org.jboss.deployment.MainDeployer] The manifest entry in file:/usr/local/JBoss/jboss-4.0.5.GA/server/default/deploy/jbossws.sar/jaxb-impl.jar references URL file:/usr/local/JBoss/jboss-4.0.5.GA/server/default/deploy/jbossws.sar/jsr173_1.0_api.jar which could not be opened, entry ignored
| org.jboss.deployment.DeploymentException: url file:/usr/local/JBoss/jboss-4.0.5.GA/server/default/deploy/jbossws.sar/jsr173_1.0_api.jar could not be opened, does it exist?
|
|
| 2006-11-28 14:18:13,291 DEBUG [org.jboss.deployment.MainDeployer] new manifest entry for sdi at jaxb-impl.jar entry is jaxb1-impl.jar
| 2006-11-28 14:18:13,292 DEBUG [org.jboss.deployment.MainDeployer] The manifest entry in file:/usr/local/JBoss/jboss-4.0.5.GA/server/default/deploy/jbossws.sar/jaxb-impl.jar references URL file:/usr/local/JBoss/jboss-4.0.5.GA/server/default/deploy/jbossws.sar/jaxb1-impl.jar which could not be opened, entry ignored
| org.jboss.deployment.DeploymentException: url file:/usr/local/JBoss/jboss-4.0.5.GA/server/default/deploy/jbossws.sar/jaxb1-impl.jar could not be opened, does it exist?
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3989498#3989498
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3989498
17 years, 5 months
[JBossWS] - Using JBoss Web Services in the jbpm-starters-kit-3.1.2
by ian.griggs
I am trying to demonstrate an XML/SOAP Web Service operation that starts a jBPM process instance I want advice on which JBoss tools to use to do this.
I installed jbossws-1.0.3.GA in the JBoss server supplied with the jBPM starters kit 3.1.2. (I am running Windows XP.)
Is this an appropriate combination? Should I use the "standard" Jboss server instead?
I followed the installation instructions, copying in jboss-xml-binding.jar from the CV7 directory. I tried to build the "Duke's Bank" example supplied with jbossws. The ant compile worked, but the ant wstool didn't.
I googled the class name and found posts indicating that the problem had been fixed by alex.loubyansky(a)jboss.com in CR 6. (http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3959866)
C:\j2eetutorial14\examples\bank>ant -f jboss-build.xml compile
Buildfile: jboss-build.xml
prepare:
compile:
BUILD SUCCESSFUL
Total time: 0 seconds
C:\j2eetutorial14\examples\bank>ant -f jboss-build.xml wstool
Buildfile: jboss-build.xml
wstool:
[wstools] log4j:WARN No appenders could be found for logger (org.jboss.ws.too
s.WSTools).
[wstools] log4j:WARN Please initialize the log4j system properly.
BUILD FAILED
java.lang.NoSuchMethodError: org.jboss.xb.binding.Unmarshaller.setSchemaValidat
on(Z)V
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3989488#3989488
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3989488
17 years, 5 months
[JBossWS] - Re: jbossws1.0.x is a preview implementation with support fo
by bocio
"maeste" wrote : Probably you didn't understand what here and in other post was said.
| Just jsr-181 is a preview.
|
| Jbossws is production ready and we use it in our production environment with something like 200 operations in 49 wsdls.
|
| Of course we made some investments to understand in deep ws standards and jboss' implementations.
|
Stefano,
probably you didn't read my first reply: I'm testing it as JSR109 client and it has a lot of problem. Please read my recent posts on this.
For me worked nearly flowless only in a JBoss - JBoss environment.
But... giving that, on production site I have to face with server endpoints running on websphere 6.1 and, of course, I cannot change the Italy Ministry of Finance WS interface, I stated that current version simply doesn't work for me.
Same thing with webservices exposed by another legacy application here. They are generated with Axis2 and again, jbossws 1.0.4 client simply does not work. All operations returns or accepts custom value objects. I posted some messages for this.
On another side project I have to implement both endpoints. The only requirement to meet is tomcat standalone. I said "Ok, on this I will use a pure jbossws implementation..."
Unfortunately the installation is broken and I opened a bug report on jiira.
Nobody replied and maybe I'm asking things answered 10000 times. I found nothing on docs, wiki and forums. Maybe I'm wrong but this should be the goal of these forums. I just expressed my opinion (IMHO). And I'm patiently waiting that these problems will be solved or someone will have some spare time to reply me. Even a "you wrote a lot of bullshits" would be enough :-)
"maeste" wrote :
| Of course we made some investments to understand in deep ws standards and jboss' implementations.
|
I'm using JBoss in production sites since 2.4.6 version many years ago, and I brought it with me across three companies. On summer 2004 we spent about 17.000 Euro for training from the only jboss certified italian company. Is it enough?
You see, while I know I didn't pay the car, I'm becoming a little tired to wear an "engineer white coat" each time just to drive this car ;-)
And reading Jboss mailing lists and forum since so many years I can assure you that a lot of things changed. JBoss AS became very popular and consequently background noise increased. Quality on forums lowered on both sides and the jboss staff attitude has changed a lot.
Moderators, please feel free to move this message to the useless rants corner
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3989434#3989434
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3989434
17 years, 5 months
[JBossWS] - Re: Enabling transport compression with JBossWS
by mo_ctaylor
I discovered that there were performance fixes with JBossWS and with JBossXB so I have followed the upgrade instructions and have upgraded to JBossWS-1.0.4.GA.
The Web Services do work faster now but we will still have a performance issue. I would like to get transport compression working with JBossWS but still have not figured out how to do so. I am wondering if JBoss Remoting can be used to get compression working. As far as I can tell it seems like JBoss Web Services uses JBoss Remoting. JBoss Remoting has pluggable data marshallers and on the JBoss Remoting Wiki it states that there exists data compression marshallers/unmarshallers for compression of large payloads. Is there a configuration file that I can modify so that my JBoss Web Services Clients and Providers use the CompressingMarshaller and CompressingUnMarshaller? Is there another way to get transport compression to work with JBoss Web Services?
Thanks,
CIndy
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3989395#3989395
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3989395
17 years, 5 months