11:28 p.m.
Create a WSDL based WS Resource Adapter
---------------------------------------
Key: TEIID-1241
URL: https://jira.jboss.org/browse/TEIID-1241
Project: Teiid
Issue Type: Feature Request
Components: Misc. Connectors
Affects Versions: 7.2
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 7.2
The current WS resource adapter was designed for low-level usage, which doesn't even
consult a WSDL. It would be good though to update the existing adapter (or introduce a
new) to utilize a WSDL. The WSDL would be used to expose the operations through connector
metadata, so that the translator could create the corresponding procedures
model.service.port.binding.operation(arg...). Import options could be used to limit the
import to only particular services/ports.
The WSDL based approach would also allow for the CXF configuration to apply to more than a
single port and to more easily allow the policy definition for WS security.
Additional semantic support for RPC could be considered, but would need to use JAX-RPC
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:22 p.m.
New subject: [JBoss JIRA] Commented: (TEIID-1241) Create a WSDL based WS Resource Adapter
[
https://jira.jboss.org/browse/TEIID-1241?page=com.atlassian.jira.plugin.s...
]
Steven Hawkins commented on TEIID-1241:
---------------------------------------
Now that designer supports wsdl based imports again, the importance of this issue has
lessened. It would be good though to have the multiple port based configuration and
higher level dynamic vdb support for wsdl operations.
Create a WSDL based WS Resource Adapter
---------------------------------------
Key: TEIID-1241
URL: https://jira.jboss.org/browse/TEIID-1241
Project: Teiid
Issue Type: Feature Request
Components: Misc. Connectors
Affects Versions: 7.2
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 7.2
The current WS resource adapter was designed for low-level usage, which doesn't even
consult a WSDL. It would be good though to update the existing adapter (or introduce a
new) to utilize a WSDL. The WSDL would be used to expose the operations through connector
metadata, so that the translator could create the corresponding procedures
model.service.port.binding.operation(arg...). Import options could be used to limit the
import to only particular services/ports.
The WSDL based approach would also allow for the CXF configuration to apply to more than
a single port and to more easily allow the policy definition for WS security.
Additional semantic support for RPC could be considered, but would need to use JAX-RPC
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:39 p.m.
New subject: [JBoss JIRA] Updated: (TEIID-1241) Create a WSDL based WS Resource Adapter
[
https://jira.jboss.org/browse/TEIID-1241?page=com.atlassian.jira.plugin.s...
]
Steven Hawkins updated TEIID-1241:
----------------------------------
Fix Version/s: 7.3
(was: 7.2)
Pushing to 7.3
Create a WSDL based WS Resource Adapter
---------------------------------------
Key: TEIID-1241
URL: https://jira.jboss.org/browse/TEIID-1241
Project: Teiid
Issue Type: Feature Request
Components: Misc. Connectors
Affects Versions: 7.2
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 7.3
The current WS resource adapter was designed for low-level usage, which doesn't even
consult a WSDL. It would be good though to update the existing adapter (or introduce a
new) to utilize a WSDL. The WSDL would be used to expose the operations through connector
metadata, so that the translator could create the corresponding procedures
model.service.port.binding.operation(arg...). Import options could be used to limit the
import to only particular services/ports.
The WSDL based approach would also allow for the CXF configuration to apply to more than
a single port and to more easily allow the policy definition for WS security.
Additional semantic support for RPC could be considered, but would need to use JAX-RPC
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:28 p.m.
New subject: [JBoss JIRA] Updated: (TEIID-1241) Create a WSDL based WS Resource Adapter
[
https://issues.jboss.org/browse/TEIID-1241?page=com.atlassian.jira.plugin...
]
Steven Hawkins updated TEIID-1241:
----------------------------------
Fix Version/s: 7.4
(was: 7.3)
Pushing to 7.4
Create a WSDL based WS Resource Adapter
---------------------------------------
Key: TEIID-1241
URL: https://issues.jboss.org/browse/TEIID-1241
Project: Teiid
Issue Type: Feature Request
Components: Misc. Connectors
Affects Versions: 7.2
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 7.4
The current WS resource adapter was designed for low-level usage, which doesn't even
consult a WSDL. It would be good though to update the existing adapter (or introduce a
new) to utilize a WSDL. The WSDL would be used to expose the operations through connector
metadata, so that the translator could create the corresponding procedures
model.service.port.binding.operation(arg...). Import options could be used to limit the
import to only particular services/ports.
The WSDL based approach would also allow for the CXF configuration to apply to more than
a single port and to more easily allow the policy definition for WS security.
Additional semantic support for RPC could be considered, but would need to use JAX-RPC
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:49 a.m.
New subject: [JBoss JIRA] Updated: (TEIID-1241) Create a WSDL based WS Resource Adapter
[
https://issues.jboss.org/browse/TEIID-1241?page=com.atlassian.jira.plugin...
]
Steven Hawkins updated TEIID-1241:
----------------------------------
Fix Version/s: 9.0
(was: 7.4)
Create a WSDL based WS Resource Adapter
---------------------------------------
Key: TEIID-1241
URL: https://issues.jboss.org/browse/TEIID-1241
Project: Teiid
Issue Type: Feature Request
Components: Misc. Connectors
Affects Versions: 7.2
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 9.0
The current WS resource adapter was designed for low-level usage, which doesn't even
consult a WSDL. It would be good though to update the existing adapter (or introduce a
new) to utilize a WSDL. The WSDL would be used to expose the operations through connector
metadata, so that the translator could create the corresponding procedures
model.service.port.binding.operation(arg...). Import options could be used to limit the
import to only particular services/ports.
The WSDL based approach would also allow for the CXF configuration to apply to more than
a single port and to more easily allow the policy definition for WS security.
Additional semantic support for RPC could be considered, but would need to use JAX-RPC
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:57 p.m.
New subject: [JBoss JIRA] (TEIID-1241) Create a WSDL based WS translator
[
https://issues.jboss.org/browse/TEIID-1241?page=com.atlassian.jira.plugin...
]
Steven Hawkins updated TEIID-1241:
----------------------------------
Summary: Create a WSDL based WS translator (was: Create a WSDL based WS
Resource Adapter)
Fix Version/s: 8.1
(was: 9.0)
Description:
The current WS resource adapter was designed for low-level usage, which doesn't even
consult a WSDL. It would be good though to update the existing adapter/translator to
utilize a WSDL. The WSDL would be used to expose the operations through connector
metadata, so that the translator could create the corresponding procedures
model.service.port.binding.operation(arg...). Import options could be used to limit the
import to only particular services/ports.
The WSDL based approach would also allow for the CXF configuration to apply to more than a
single port and to more easily allow the policy definition for WS security.
Additional semantic support for RPC could be considered, but would need to use JAX-RPC
was:
The current WS resource adapter was designed for low-level usage, which doesn't even
consult a WSDL. It would be good though to update the existing adapter (or introduce a
new) to utilize a WSDL. The WSDL would be used to expose the operations through connector
metadata, so that the translator could create the corresponding procedures
model.service.port.binding.operation(arg...). Import options could be used to limit the
import to only particular services/ports.
The WSDL based approach would also allow for the CXF configuration to apply to more than a
single port and to more easily allow the policy definition for WS security.
Additional semantic support for RPC could be considered, but would need to use JAX-RPC
Updating and targeting at 8.1
Create a WSDL based WS translator
---------------------------------
Key: TEIID-1241
URL: https://issues.jboss.org/browse/TEIID-1241
Project: Teiid
Issue Type: Feature Request
Components: Misc. Connectors
Affects Versions: 7.2
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.1
The current WS resource adapter was designed for low-level usage, which doesn't even
consult a WSDL. It would be good though to update the existing adapter/translator to
utilize a WSDL. The WSDL would be used to expose the operations through connector
metadata, so that the translator could create the corresponding procedures
model.service.port.binding.operation(arg...). Import options could be used to limit the
import to only particular services/ports.
The WSDL based approach would also allow for the CXF configuration to apply to more than
a single port and to more easily allow the policy definition for WS security.
Additional semantic support for RPC could be considered, but would need to use JAX-RPC
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:07 p.m.
New subject: [JBoss JIRA] (TEIID-1241) Create a WSDL based WS translator
[
https://issues.jboss.org/browse/TEIID-1241?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-1241:
---------------------------------------
This could be bumped up to 7.7.1 based upon using the existing invoke method with the
action parameter as the port name to assist in situations where the WSDL specifies static
soap header information.
Create a WSDL based WS translator
---------------------------------
Key: TEIID-1241
URL: https://issues.jboss.org/browse/TEIID-1241
Project: Teiid
Issue Type: Feature Request
Components: Misc. Connectors
Affects Versions: 7.2
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.1
The current WS resource adapter was designed for low-level usage, which doesn't even
consult a WSDL. It would be good though to update the existing adapter/translator to
utilize a WSDL. The WSDL would be used to expose the operations through connector
metadata, so that the translator could create the corresponding procedures
model.service.port.binding.operation(arg...). Import options could be used to limit the
import to only particular services/ports.
The WSDL based approach would also allow for the CXF configuration to apply to more than
a single port and to more easily allow the policy definition for WS security.
Additional semantic support for RPC could be considered, but would need to use JAX-RPC
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:09 p.m.
New subject: [JBoss JIRA] (TEIID-1241) Create a WSDL based WS translator
[
https://issues.jboss.org/browse/TEIID-1241?page=com.atlassian.jira.plugin...
]
Steven Hawkins updated TEIID-1241:
----------------------------------
Fix Version/s: 8.2
(was: 8.1)
Pushing to 8.2
Create a WSDL based WS translator
---------------------------------
Key: TEIID-1241
URL: https://issues.jboss.org/browse/TEIID-1241
Project: Teiid
Issue Type: Feature Request
Components: Misc. Connectors
Affects Versions: 7.2
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.2
The current WS resource adapter was designed for low-level usage, which doesn't even
consult a WSDL. It would be good though to update the existing adapter/translator to
utilize a WSDL. The WSDL would be used to expose the operations through connector
metadata, so that the translator could create the corresponding procedures
model.service.port.binding.operation(arg...). Import options could be used to limit the
import to only particular services/ports.
The WSDL based approach would also allow for the CXF configuration to apply to more than
a single port and to more easily allow the policy definition for WS security.
Additional semantic support for RPC could be considered, but would need to use JAX-RPC
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:31 p.m.
New subject: [JBoss JIRA] (TEIID-1241) Create a WSDL based WS translator
[
https://issues.jboss.org/browse/TEIID-1241?page=com.atlassian.jira.plugin...
]
Steven Hawkins updated TEIID-1241:
----------------------------------
Assignee: Ramesh Reddy (was: Steven Hawkins)
Create a WSDL based WS translator
---------------------------------
Key: TEIID-1241
URL: https://issues.jboss.org/browse/TEIID-1241
Project: Teiid
Issue Type: Feature Request
Components: Misc. Connectors
Affects Versions: 7.2
Reporter: Steven Hawkins
Assignee: Ramesh Reddy
Fix For: 8.2
The current WS resource adapter was designed for low-level usage, which doesn't even
consult a WSDL. It would be good though to update the existing adapter/translator to
utilize a WSDL. The WSDL would be used to expose the operations through connector
metadata, so that the translator could create the corresponding procedures
model.service.port.binding.operation(arg...). Import options could be used to limit the
import to only particular services/ports.
The WSDL based approach would also allow for the CXF configuration to apply to more than
a single port and to more easily allow the policy definition for WS security.
Additional semantic support for RPC could be considered, but would need to use JAX-RPC
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:04 p.m.
New subject: [JBoss JIRA] (TEIID-1241) Create a WSDL based WS translator
[
https://issues.jboss.org/browse/TEIID-1241?page=com.atlassian.jira.plugin...
]
Ramesh Reddy updated TEIID-1241:
--------------------------------
Git Pull Request: https://github.com/teiid/teiid/pull/15
Create a WSDL based WS translator
---------------------------------
Key: TEIID-1241
URL: https://issues.jboss.org/browse/TEIID-1241
Project: Teiid
Issue Type: Feature Request
Components: Misc. Connectors
Affects Versions: 7.2
Reporter: Steven Hawkins
Assignee: Ramesh Reddy
Fix For: 8.2
The current WS resource adapter was designed for low-level usage, which doesn't even
consult a WSDL. It would be good though to update the existing adapter/translator to
utilize a WSDL. The WSDL would be used to expose the operations through connector
metadata, so that the translator could create the corresponding procedures
model.service.port.binding.operation(arg...). Import options could be used to limit the
import to only particular services/ports.
The WSDL based approach would also allow for the CXF configuration to apply to more than
a single port and to more easily allow the policy definition for WS security.
Additional semantic support for RPC could be considered, but would need to use JAX-RPC
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:10 p.m.
New subject: [JBoss JIRA] (TEIID-1241) Create a WSDL based WS translator
[
https://issues.jboss.org/browse/TEIID-1241?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIID-1241:
-------------------------------------
Added functionality to the existing "ws" translator to read the WSDL defined
operations, if the ws-connector supplies a valid wsdl file during the import.
The model "importer.serviceName" and "importer.portName" need to be
used select the operation set that need to be imported as model.
Create a WSDL based WS translator
---------------------------------
Key: TEIID-1241
URL: https://issues.jboss.org/browse/TEIID-1241
Project: Teiid
Issue Type: Feature Request
Components: Misc. Connectors
Affects Versions: 7.2
Reporter: Steven Hawkins
Assignee: Ramesh Reddy
Fix For: 8.2
The current WS resource adapter was designed for low-level usage, which doesn't even
consult a WSDL. It would be good though to update the existing adapter/translator to
utilize a WSDL. The WSDL would be used to expose the operations through connector
metadata, so that the translator could create the corresponding procedures
model.service.port.binding.operation(arg...). Import options could be used to limit the
import to only particular services/ports.
The WSDL based approach would also allow for the CXF configuration to apply to more than
a single port and to more easily allow the policy definition for WS security.
Additional semantic support for RPC could be considered, but would need to use JAX-RPC
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:51 p.m.
New subject: [JBoss JIRA] (TEIID-1241) Create a WSDL based WS translator
[
https://issues.jboss.org/browse/TEIID-1241?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-1241.
-----------------------------------
Resolution: Done
Updated the resource adapter / translator for wsdl specific calls. The resource adapter
can now be configured with Wsdl, NamespaceUri, EndPointName, and ServiceName properties to
use a specific WSDL service/port. The endpoint override is not yet used in WSDL mode as
it is assumed that the user will just update the WSDL file.
A CXF config can still be specified - with the benefit that it can now match the WSDL
rather than using the dummy teiid local names.
When used in a dynamic vdb all of the soap operations on the service/port will be exposed
a procedures.
Create a WSDL based WS translator
---------------------------------
Key: TEIID-1241
URL: https://issues.jboss.org/browse/TEIID-1241
Project: Teiid
Issue Type: Feature Request
Components: Misc. Connectors
Affects Versions: 7.2
Reporter: Steven Hawkins
Assignee: Ramesh Reddy
Fix For: 8.2
The current WS resource adapter was designed for low-level usage, which doesn't even
consult a WSDL. It would be good though to update the existing adapter/translator to
utilize a WSDL. The WSDL would be used to expose the operations through connector
metadata, so that the translator could create the corresponding procedures
model.service.port.binding.operation(arg...). Import options could be used to limit the
import to only particular services/ports.
The WSDL based approach would also allow for the CXF configuration to apply to more than
a single port and to more easily allow the policy definition for WS security.
Additional semantic support for RPC could be considered, but would need to use JAX-RPC
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:53 p.m.
New subject: [JBoss JIRA] (TEIID-1241) Create a WSDL based WS translator
[
https://issues.jboss.org/browse/TEIID-1241?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-1241:
---------------------------------------
I should also add that https://issues.apache.org/jira/browse/CXF-4608 was logged and a
workaround was added in the connector so that streaming is still used rather than
returning domsources from the call.
Create a WSDL based WS translator
---------------------------------
Key: TEIID-1241
URL: https://issues.jboss.org/browse/TEIID-1241
Project: Teiid
Issue Type: Feature Request
Components: Misc. Connectors
Affects Versions: 7.2
Reporter: Steven Hawkins
Assignee: Ramesh Reddy
Fix For: 8.2
The current WS resource adapter was designed for low-level usage, which doesn't even
consult a WSDL. It would be good though to update the existing adapter/translator to
utilize a WSDL. The WSDL would be used to expose the operations through connector
metadata, so that the translator could create the corresponding procedures
model.service.port.binding.operation(arg...). Import options could be used to limit the
import to only particular services/ports.
The WSDL based approach would also allow for the CXF configuration to apply to more than
a single port and to more easily allow the policy definition for WS security.
Additional semantic support for RPC could be considered, but would need to use JAX-RPC
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:31 p.m.
New subject: [JBoss JIRA] (TEIID-1241) Create a WSDL based WS translator
[
https://issues.jboss.org/browse/TEIID-1241?page=com.atlassian.jira.plugin...
]
Steven Hawkins closed TEIID-1241.
---------------------------------
Create a WSDL based WS translator
---------------------------------
Key: TEIID-1241
URL: https://issues.jboss.org/browse/TEIID-1241
Project: Teiid
Issue Type: Feature Request
Components: Misc. Connectors
Affects Versions: 7.2
Reporter: Steven Hawkins
Assignee: Ramesh Reddy
Fix For: 8.2
The current WS resource adapter was designed for low-level usage, which doesn't even
consult a WSDL. It would be good though to update the existing adapter/translator to
utilize a WSDL. The WSDL would be used to expose the operations through connector
metadata, so that the translator could create the corresponding procedures
model.service.port.binding.operation(arg...). Import options could be used to limit the
import to only particular services/ports.
The WSDL based approach would also allow for the CXF configuration to apply to more than
a single port and to more easily allow the policy definition for WS security.
Additional semantic support for RPC could be considered, but would need to use JAX-RPC
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
4179
days inactive
4989
days old
13 comments
2 participants
participants (2)
-
Ramesh Reddy (JIRA) -
Steven Hawkins (JIRA)