[JBoss JIRA] Created: (JBWS-1726) Modularize MetaDataBuilder
by Thomas Diesler (JIRA)
Modularize MetaDataBuilder
--------------------------
Key: JBWS-1726
URL: http://jira.jboss.com/jira/browse/JBWS-1726
Project: JBoss Web Services
Issue Type: Task
Security Level: Public (Everyone can see)
Components: jbossws-jaxrpc, jbossws-jaxws
Reporter: Thomas Diesler
Fix For: jbossws-2.1.0
Especially, revisit 'toolMode'. Is that really needed? The return below is questionable
// The server must always generate WSDL
if (generateWsdl || !toolMode)
processOrGenerateWSDL(seiClass, serviceMetaData, result.wsdlLocation, sepMetaData);
// No need to process endpoint items if we are in tool mode
if (toolMode)
return sepMetaData;
// Sanity check: read the generated WSDL and initialize the schema model
// Note, this should no longer be needed, look into removing it
WSDLDefinitions wsdlDefinitions = serviceMetaData.getWsdlDefinitions();
JBossXSModel schemaModel = WSDLUtils.getSchemaModel(wsdlDefinitions.getWsdlTypes());
serviceMetaData.getTypesMetaData().setSchemaModel(schemaModel);
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 10 months
[JBoss JIRA] Created: (JBWS-1664) Add support for external policy attachment
by Alessio Soldano (JIRA)
Add support for external policy attachment
------------------------------------------
Key: JBWS-1664
URL: http://jira.jboss.com/jira/browse/JBWS-1664
Project: JBoss Web Services
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: ws-policy
Reporter: Alessio Soldano
Assigned To: Alessio Soldano
Priority: Minor
Fix For: jbossws-2.1.0
WS-Policy Attachment specs, chapter 3.4 on external policy attachment:
"This mechanism allows Policies to be associated with a Policy Subject independent of that subject's definition and/or representation through the use of a <wsp:PolicyAttachment> element. This element has three components: the Policy Scope of the attachment, the Policy Expressions being bound, and optional security information. The Policy Scope of the attachment is defined using one or more extensible domain expressions that identify Policy Subjects, typically using URIs. [...]"
This is supposed to use WS-Addressing to deal with policy scopes.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 10 months
[JBoss JIRA] Created: (JBWS-1395) Add a Standard All Client Configuration to standard-jbossws-client-config.xml
by John Gilbert (JIRA)
Add a Standard All Client Configuration to standard-jbossws-client-config.xml
-----------------------------------------------------------------------------
Key: JBWS-1395
URL: http://jira.jboss.com/jira/browse/JBWS-1395
Project: JBoss Web Services
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: jaxws
Reporter: John Gilbert
Priority: Trivial
It would be nice to have this in addition to Standard Client, Standard Secure Client, and Standard Addressing Client, so that all clients don't have to create their config file.
<client-config>
<config-name>Standard All Client</config-name>
<post-handler-chain>
<handler-chain-name>PostHandlerChain</handler-chain-name>
<handler>
<j2ee:handler-name>WSSecurityHandlerOutbound</j2ee:handler-name>
<j2ee:handler-class>org.jboss.ws.wsse.WSSecurityHandlerOutbound</j2ee:handler-class>
</handler>
<handler>
<j2ee:handler-name>SOAPClientHandler</j2ee:handler-name>
<j2ee:handler-class>org.jboss.ws.addressing.soap.SOAPClientHandler</j2ee:handler-class>
</handler>
</post-handler-chain>
</client-config>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 10 months
[JBoss JIRA] Created: (JBWS-1314) Precursor to streaming optimizations, elimination of xmlFragment
by Thomas Diesler (JIRA)
Precursor to streaming optimizations, elimination of xmlFragment
----------------------------------------------------------------
Key: JBWS-1314
URL: http://jira.jboss.com/jira/browse/JBWS-1314
Project: JBoss Web Services
Issue Type: Task
Security Level: Public (Everyone can see)
Components: jaxws
Reporter: Thomas Diesler
Fix For: jbossws-2.0.1
At some point, we should remove the xml string fragment processing phase. It's not needed in our long term streaming optimization plan, and it adds unneeded performance overhead in the current design.
Instead we could pass the corresponding DOM chunk directly to the marshalling layer. JAXB supports this using javax.xml.transform.Source, and it wouldn't be difficult to enhance JBossXB to do the same. This would also be more robust because it would eliminate the xml escape processing that we duplicate from a standard XML parser (see [JBWS-1240] for an example).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 10 months