]
Kevin Conner commented on JBESB-3374:
-------------------------------------
I believe what you are asking for is already possible, as the WSDL can be located on the
classpath.
The use of internal is only necessary to access co-located services.
WSDL/XSD concerns with hanging ESB
----------------------------------
Key: JBESB-3374
URL:
https://jira.jboss.org/browse/JBESB-3374
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Configuration
Affects Versions: 4.7
Reporter: Brian Fitzpatrick
This conversation was started by Gary Lamparillo in JBIDE-6161 a while back... Some of
the relevant bits from that conversation are...
"I understand that the way the wsdls come in and are not cached is an issue. Can we
pursue this with the esb team? Using internal is not ideal, since that only takes care of
one use case, and given that if it is external(remote), it will hang the server.There are
some items that need deployment.xml modified still, for example the queue dependencies.
It is all about dependency on the wsdl. And also xsds inside the wsdl. It would be
nice, if an option was available to cache the wsdl at design time in a file. Similar to
how the Rules Engine works with Guvnor. In addition, from migration from Dev, QA, to
Prod, We need a location to put endpoint updates, but not the entire wsdl."
Not sure where or how to get this addressed, but will help if I can...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: