[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: ECF 4.0 web services SIP - possible adiitional errors
ECF TC: Thanks to Gary for identifying a
few spelling and namespace issues in the revised WSDL. I addressed the
spelling issues and, for consistency, I changed all references to “WebServiceMessagingProfile”
to simply “WebServicesProfile”. The latest version of the 2.01 web services
SIP is attached. Thanks, Jim Cabral James
E. Cabral Jr. Helping our clients make a
difference in the lives of the people they serve. The information transmitted is intended only for the person or
entity to which it is addressed and may contain confidential and/or privileged
material. If you received this in error, please contact the sender and delete
the material from any computer. From: Graham, Gary
[mailto:GGraham@courts.az.gov] When I open
ECF-4.0-WebServicesProfile-ImplementationExample.wsdl into XMLSpy it reports an
error: Failed to open import location 'C:\Users\ggraham\Documents\ecf-v4.0-webservices-spec-cd01\ecf-v4.0-webservices-spec\ECF-4.0-WebServicesMessagingProfile-Definitions.wsdl'
specified in file
'C:\Users\ggraham\Documents\ecf-v4.0-webservices-spec-cd01\ecf-v4.0-webservices-spec\ECF-4.0-WebServicesProfile-ImplementationExample.wsdl'! Refer to line 15 in
ECF-4.0-WebServicesProfile-ImplementationExample.wsdl (shown below): <import
namespace="urn:oasis:names:tc:legalxml-courtfiling:wsdl:WebServiceMessagingProfile-Definitions-4.0"
location="ECF-4.0-WebServicesMessagingProfile-Definitions.wsdl"/> There were 4 files provided in
your zip file: (1) build.xml, (2) ECF-4.0-WebServicesProfile-Definitions.wsdl,
(3) ECF-4.0-WebServicesProfile-ImplementationExample.wsdl, and (4)
ecf-v4.0-webservices-v2.01-spec-cd01.doc. If the second file is renamed
to: ECF-4.0-WebServicesMessagingProfile-Definitions.wsdl Then the Error reported by
XMLSpy goes away. I’m not sure if the file should
be renamed or the Example wsdl file should be revised. I renamed the file to
ECF-4.0-WebServicesMessagingProfile-Definitions.wsdl, but now XMLSpy is
reporting: Invalid XML schema:
''ecf:ElectronicFilingMessageType' must refer to an existing simple or complex
type.' From: Graham, Gary Thanks Jim I have noted a couple of
possible typos in the wsdl file. Line 146, which currently
contains: <part name=”CaseQueryMessae”
element=”casequery:CaseQueryMessage”/> Should probably be:
“CaseQueryMessage” Also, line 192 which is: <part
name=”DocumentResponeMessage”
element=”docresponse:DocumentResponseMessage”/> Should probably
be: “DocumentResponseMessage” Gary Graham From: Cabral, James E.
[mailto:JCabral@mtgmc.com] ECF TC: I attach the proposed patched
web service spec. Note that it is actually v2.01 of the web service spec
(not 4.01). Hopefully, we can either vote on it during the TC call
tomorrow or at least decide on a schedule for bringing it to a vote. Then
we’ll need to request the OASIS staff to post it to the docs.oasis-open.org
site which may take some time. Thanks, Jim Cabral James
E. Cabral Jr. Helping our clients make a
difference in the lives of the people they serve. The information transmitted is intended only for the person or
entity to which it is addressed and may contain confidential and/or privileged
material. If you received this in error, please contact the sender and delete
the material from any computer. From: Graham, Gary
[mailto:GGraham@courts.az.gov] I read with interest the ‘ECF 4.0 web services SIP
conformance issue with WS-I Basic Profile’ thread in the ‘archive’ since this
is an area I have been wrestling with the past couple of days. A June 9, 2009 entry identified that a release 4.01 bug fix
to the web services SIP would be available by the end of the month. I have just visited the ‘download page’ (http://docs.oasis-open.org/legalxml-courtfiling/specs/ecf/v4.0/ecf-v4.0-webservices-spec/)
but do not see anything recent or indentified as 4.01. When will this bug
fix release be available? Gary Graham Arizona Supreme Court |
ecf-v4.0-webservices-v2.01-spec.zip
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]