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
| Field | Original Value | New Value |
|---|---|---|
| Link | This issue blocks SPVEOLIAE-28 [ SPVEOLIAE-28 ] |
| Priority | Minor [ 4 ] |
| Attachment | petals-view.properties [ 10111 ] | |
| Attachment | svn.zip.1 [ 10112 ] | |
| Attachment | conf.xml [ 10113 ] |
| Attachment | sl-oracle-driver-10.2.0.2.zip [ 10114 ] | |
| Attachment | sa-AD004-RecupMissionSigma-1.0.0-SNAPSHOT.zip [ 10115 ] |
| Description |
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 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 :-) |
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 :-) |
| Attachment | petals-se-notification-1.0.2.zip [ 10116 ] |
| Attachment | petals-se-kpi-1.0.4-SNAPSHOT.zip [ 10117 ] |
| Attachment | petals-se-eip-2.5-20100610.103318-7.zip [ 10118 ] |
| Attachment | petals-se-xslt-2.3.3-SNAPSHOT.zip [ 10119 ] |
| Attachment | petals-bc-soap-4.0.3-20100704.073518-7.zip [ 10125 ] |
-
- Time Worked:
- 2 hours
- The endpoint we got has been registered on the Petals-SE-EIP. When the endpoint is proxified by the Petals-BC-SOAP the document description we retrieve is already corrupted.
| Remaining Estimate | 0 minutes [ 0 ] | |
| Time Spent | 2 hours [ 7200 ] |
| Project | Petals-BC-SOAP [ 10038 ] | Petals-SE-EIP [ 10041 ] |
| Key | PETALSBCSOAP-27 | PETALSSEEIP-2 |
| Affects Version/s | 2.4.3 [ 10035 ] | |
| Affects Version/s | 4.0.3 [ 10050 ] | |
| Assignee | Nicolas Oddoux [ noddoux ] | Marc Jambert [ mjambert ] |
| Project | Petals-SE-EIP [ 10041 ] | Petals-CDK [ 10032 ] |
| Key | PETALSSEEIP-2 | PETALSCDK-8 |
| Affects Version/s | 5.0.3 [ 10027 ] | |
| Affects Version/s | 2.4.3 [ 10035 ] | |
| Assignee | Marc Jambert [ mjambert ] | Mathieu Carrolle [ mcarrolle ] |
| Project | Petals-CDK [ 10032 ] | Easy-WSDL [ 10020 ] |
| Key | PETALSCDK-8 |
|
| Affects Version/s | 2.3 [ 10012 ] | |
| Affects Version/s | 5.0.3 [ 10027 ] | |
| Assignee | Mathieu Carrolle [ mcarrolle ] | Marc Jambert [ mjambert ] |
| Status | Resolved [ 10004 ] | Closed [ 10005 ] |
| Fix Version/s | 2.3 [ 10012 ] |
| Transition | Status Change Time | Execution Times | Last Executer | Last Execution Date | |||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
It seems like the svn.zip does not contain all the required XSDs. I have put them in the blocked issue