Class J2EEModelerHelper
java.lang.Object
com.sun.xml.rpc.processor.modeler.j2ee.J2EEModelerHelper
- Author:
- JAX-RPC RI Development Team
-
Constructor Summary
Constructors -
Method Summary
Modifier and TypeMethodDescriptionprotected J2EEModelInfo.MetadataOperationInfofindOperationInfo(Message inputMessage) getElementTypeToLiteralType(QName elementType) protected WSDLModelerBase.WSDLExceptionInfogetExceptionInfo(Fault fault) protected StringgetJavaNameForOperation(Operation operation) protected StringgetJavaNameOfPort(QName portQName) protected StringgetJavaNameOfSEI(Port port) static QNamegetQNameOf(GloballyKnown entity) protected StringgetServiceInterfaceName(QName serviceQName, Service wsdlService) protected booleanisUnwrappable(Message inputMessage) protected voidpostProcessSOAPOperation(Operation operation) protected voidsetCurrentPort(Port port) protected voidsetJavaOperationNameProperty(Message inputMessage) protected voidBP 2707 assume "literal" if "use" attribute is not specified XXX FIXME.protected booleanuseExplicitServiceContextForDocLit(Message inputMessage) This is a complete hack.protected booleanuseExplicitServiceContextForRpcEncoded(Message inputMessage) This is a complete hack.protected booleanuseExplicitServiceContextForRpcLit(Message inputMessage) This is a complete hack.protected AbstractTypeverifyParameterType(AbstractType type, String partName, Operation operation) protected AbstractTypeverifyResultType(AbstractType type, Operation operation)
-
Constructor Details
-
J2EEModelerHelper
-
-
Method Details
-
getServiceInterfaceName
- Parameters:
serviceQName-wsdlService-- Returns:
- The name of the service in the wsdl
-
getJavaNameOfPort
-
setJavaOperationNameProperty
-
useExplicitServiceContextForDocLit
This is a complete hack. We should really be reading the mapping file and generate the java methods. Since we are retro-fitting the mapping information, we have to force jaxrpc to create the explicit context, i.e. handling soap headerfault. -
useExplicitServiceContextForRpcLit
This is a complete hack. We should really be reading the mapping file and generate the java methods. Since we are retro-fitting the mapping information, we have to force jaxrpc to create the explicit context, i.e. handling soap headerfault. -
findOperationInfo
-
useExplicitServiceContextForRpcEncoded
This is a complete hack. We should really be reading the mapping file and generate the java methods. Since we are retro-fitting the mapping information, we have to force jaxrpc to create the explicit context, i.e. handling soap headerfault. -
isUnwrappable
-
setCurrentPort
-
getJavaNameOfSEI
-
getElementTypeToLiteralType
-
verifyResultType
-
verifyParameterType
-
postProcessSOAPOperation
-
getExceptionInfo
-
setSOAPUse
protected void setSOAPUse()BP 2707 assume "literal" if "use" attribute is not specified XXX FIXME. How do we know whether useWSIBasicProfile should be used or not? XXX Also, soapheader "use" attribute not handled here -
getJavaNameForOperation
-
getQNameOf
-