Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: 2.3
-
Fix Version/s: 2.3
-
Component/s: None
-
Security Level: Public
-
- Description:
-
Hide
WSDL can use external imports (through url). If we install a provide service unit using such WSDL, it works fine...but things get a bit wrong when we choose to uninstall this provide service unit, modify the imports and re-install the same service unit we have a problem. The component gives us the old XSD !
Reproduction :
- Install & configure a new Apache server (on localhost, which allows you to use the given SA directly)
- copy the content of the svn.zip in /var/www
- launch Petals ESB
- Modify the SE-XSLT to use the given conf.xml
- Modify the SE-KPI to use the given petalsview.properties
- Deploy the shared library
- Deploy all the components
- Deploy the given service assembly
- Get the WSDL exposed by the SOAP-BC
- take a look at the imported XSD (by following their url)
- Undeploy the service assembly
- Change the content of the XSD
- Redeploy the service assembly
- Get the WSDL exposed by the SOAP-BC
- take a look at the imported XSD ==> woops
ShowWSDL can use external imports (through url). If we install a provide service unit using such WSDL, it works fine...but things get a bit wrong when we choose to uninstall this provide service unit, modify the imports and re-install the same service unit we have a problem. The component gives us the old XSD ! Reproduction :- Install & configure a new Apache server (on localhost, which allows you to use the given SA directly)
- copy the content of the svn.zip in /var/www
- launch Petals ESB
- Modify the SE-XSLT to use the given conf.xml
- Modify the SE-KPI to use the given petalsview.properties
- Deploy the shared library
- Deploy all the components
- Deploy the given service assembly
- Get the WSDL exposed by the SOAP-BC
- take a look at the imported XSD (by following their url)
- Undeploy the service assembly
- Change the content of the XSD
- Redeploy the service assembly
- Get the WSDL exposed by the SOAP-BC
- take a look at the imported XSD ==> woops
-
- Environment:
- PetalsESB 3.1 / petals-se-notification / petals-se-kpi 1.0.4 / petals-bc-soap / petals-se-xslt (mod veolia) / petals-se-eip
Attachments
Activity
| Transition | Status Change Time | Execution Times | Last Executer | Last Execution Date | |||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
