Ramesh Reddy <rareddy> made a comment on jira TEIID-2035 Here is another variation of the script that is without the remove per the workaround suggested in the original JIRA. Note we are looking for a solution that does not require a restart. {code} /subsystem=resource-adapters/resource-adapter=ws/connection-definitions=wsDS:add(jndi-name=java:/wsDS, class-name=org.teiid.resource.adapter.ws.WSManagedConnectionFactory, enabled=true, use-java-context=true) /subsystem=resource-adapters/resource-adapter=ws/connection-definitions=wsDS/config-properties=EndPoint:add(value=http://foo.com) /subsystem=resource-adapters/resource-adapter=ws:activate /subsystem=resource-adapters/resource-adapter=ws/connection-definitions=wsDS/config-properties=EndPoint:remove /subsystem=resource-adapters/resource-adapter=ws/connection-definitions=wsDS/config-properties=EndPoint:add(value=http://foo1.com) {code} I even tried the undefine-attribute instead of "remove" and "add" in last two lines of the script.
Ramesh Reddy <rareddy> updated the status of jira TEIID-2035 to Resolved
Ramesh Reddy <rareddy> made a comment on jira TEIID-2035 Implemented the workaround defined in the thread https://community.jboss.org/message/832363 This solution requires creating a resource-adapter for each connection factory, also when the connection factory is deleted then the resource-adapter also deleted. Once side effect is user uses Admin API it completely will be consistent in creation/deletion of sources, if they mix in editing XML file directly and Admin API some in-consistency is expected the way they are handled.
Fixed before GA - setting to requires_doc_text- accordingly
Steven Hawkins <shawkins> updated the status of jira TEIID-2035 to Closed
Verified in JBDSIS-7.0.0.GA-GA + DV 6.0.0.GA.