Index Changes

Difference between version and version     

Back to Open ES Bv 2.next App Verifier, or Open ES Bv 2.next App Verifier Info


At line 6 changed 1 line.
The goal of this enhancement is to allow verifier to process application zip in memory, including reading SA zip entries and SU jar engries, reading SA's jbi.xml contents, and reading SU's jbi.xml and wsdl files. Prior to this enhancement, The application verifier extracted the given application in temporary dir which may lead to some cleanup issues.
The goal of this enhancement is to allow verifier to process application zip in memory, including reading SA zip entries, SU jar entries, and reading SA's jbi.xml contents, SU's jbi.xml and wsdl files. Prior to this enhancement, the application verifier extracted the given application in temporary dir which may lead to some cleanup issues.
At line 8 changed 1 line.
In verifier, we need to reading the application zip contents on both server side and client side, and then make the comparision. On the server side, since the application zip contents already have been extracted into server side directory, we keep using the existing code (reding from directory) and do not change anything.
The SA zip file which is going to be verified is processed using java.zip.util.* APIs, and the SU jar files inside the SA zip are loaded back to memory using the combination of java.zip.util.* APIs and ByteArrayOutputStream/StringReader. Basically the contents (wsdls and jbi.xml) of SU jars are output to String objects using ByteArrayOutputStream, and then loaded into XML InputSource using StringReader.
At line 10 changed 4 lines.
On the client side, we skip the step which we extracted the application zip into a temp directory. the SA zip file which is going to be verified is processed
using java.zip.util.* APIs, and the SU jar files inside the SA zip are loaded back to memory using the combination of java.zip.util.* APIs and
ByteArrayOutputStream/StringReader. Basically the contents (wsdls and jbi.xml) of SU jars are output to String objects using ByteArrayOutputStream, and then
loaded into XML InputSource using StringReader.
!!Verifier should handle WSDL 2.0 deployments
The goal of this enhancement is to allow verifier to support WSDL 2.0. Prior to this enhancement, verifier supported WSDL 1.1 only.
There are three parts for this enhancement:
First, we split WSDL11NanespaceContext class into WSDLNamespaceContext (handles jbi.xml related common XPath queries), WSDL11NamespaceContext (handles wsdl 1.1 related XPath queries) and WSDL20NamespaceContext (handles wsdl 2.0 XPath queries).
Second, we mirror all WSDL 1.1 XPath queries to create WSDL 2.0 XPath queries accordingly.
Third, before trying to interpreting a WSDL file, we peek into the WSDL file to see if this is version 1.1 or version 2.0, and then calling different XPath queries accordingly.

JSPWiki v2.4.100
[RSS]
« Home Index Changes Prefs
This page (revision-7) was last changed on 15-Jul-08 18:31 PM, -0700 by 192.18.101.18