Hello,
I found a lot of different issues in Eclipse VTP/OpenVXML 4.0 and I want to share them with you. I need some help to validate them.
I think I've already fixed Issues #1, #2, #3, #5 and #6, but I haven't tested them that much yet.
Issue #1: When using Eclipse VTP/OpenVXML 4.0 into Eclipse Juno the following exception appears when deploying the application in Tomcat:
Command-line arguments: -console 12345 -consoleLog
!ENTRY org.eclipse.osgi 4 0 2012-12-21 13:44:54.418
!MESSAGE Could not find bundle: org.eclipse.equinox.console
!STACK 0
org.osgi.framework.BundleException: Could not find bundle: org.eclipse.equinox.console
at org.eclipse.osgi.framework.internal.core.ConsoleManager.checkForConsoleBundle(ConsoleManager.java:211)
at org.eclipse.core.runtime.adaptor.EclipseStarter.startup(EclipseStarter.java:297)
...
Cause: Eclipse Juno is using the latest Equinox package which does not include Equinox console as default. A simple workaround was to remove the "-console 12345" parameter.
------------------------------------------------------------------------
Issue #2: when using a "Soap Webservice" item and starting the web application the following exception appears:
java.lang.Exception: Element has no children.
at org.eclipse.vtp.framework.util.XMLUtilities.getElementTextData(XMLUtilities.java:242)
at org.eclipse.vtp.framework.util.XMLUtilities.getElementTextData(XMLUtilities.java:287)
...
Cause: When using a "Soap Webservice" item, the process.xml generated a <service-info /> xml tag without any children
------------------------------------------------------------------------
Issue #3: "Soap Webservice" item is not working. The following soap response exception was being returned:
org.apache.cxf.interceptor.Fault: Unmarshalling Error: unexpected element (uri:"
http://security.test.damiox.org/", local:"userName"). Expected elements are <{}userName>,<{}password>
at org.apache.cxf.jaxb.JAXBEncoderDecoder.unmarshall(JAXBEncoderDecoder.java:823)
at org.apache.cxf.jaxb.JAXBEncoderDecoder.unmarshall(JAXBEncoderDecoder.java:644)
...
Cause: I tried the same request through SoapUI and I got the same soap exception. This Web Service is expecting the Soap Request to manage the namespace in a different way as described below:
Original Soap Request (WRONG):
<SOAP-ENV:Body>
</findSecurityUserByUserNameAndPassword>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Expected Soap Request (RIGHT):
<SOAP-NV:Body>
<ns0:findSecurityUserByUserNameAndPassword>
<userName>Administrator</userName>
<password>123456</password>
</ns0:findSecurityUserByUserNameAndPassword>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
------------------------------------------------------------------------
Issue #4: "Soap Webservice" item does not recognize a SOAP 1.2 WSDL.
Cause: Not found yet.
------------------------------------------------------------------------
Issue #5: When opening the "Database Query" item and selecting the "Fields" tab, the "Business Object Field" item is duplicated each time you repeat the process. This occurs even if you have already configured the "Fields" tab, messing up the .xml file final process
Cause: In DatabaseQueryDataMappingPropertiesPanel.java there is no check before adding an element in "settings.dataMapping".
------------------------------------------------------------------------
Issue #6: The "Database Query" is not working.
Cause 1: The export only processes files with extensions ".dot" . I changed that to "dbt".
Cause 2: When using Business Objects as the result, the "result-type" was not being populated in the process.xml and an exception was returned.
------------------------------------------------------------------------
Issue #7: Really hard to test a change in the Workflow.
Cause: We have to save all files in the project. Export the web application file. Undeploy the existing web application in Tomcat. Deploy the new web application in Tomcat. Check the catalina output log files to see what's going on. I'm trying to integrate this project with Eclipse's Tomcat Server window.
------------------------------------------------------------------------
Issue #8: The Soap Response is not mapped to a Business Object but it is saved into a WSResponse. It would be great if we may do the same mapping that it is done for "Database Query".
Cause: Not found yet.
------------------------------------------------------------------------
Issue #9: The script box in the "Soap Webservice" item which is enabled when enabling the "Process the result immediately" box is being ignored in Runtime.
Cause: Not found yet.
****
Thanks in advance for your feedback,
Damian Nardelli
