+1
Sagara has been involved and interested in Woden for quite a while now,
seems to have learnt about it in some depth and most importantly is willing
to commit time and effort to its continuing development. I support his
nomination.
regards,
John.
On Sun, Jul 19, 2009 at 2:27 AM, Arthur Ryman
Yes Lawrence, I will check the descriptions and examples and update them
accordingly.
regards,
John.
On Tue, Nov 11, 2008 at 4:49 AM, Lawrence Mandel (JIRA) [EMAIL
PROTECTED]wrote:
[
structure so if it happened, it should be reverted to the old package unless
the woden community agrees to do so.
Jeff MAURY
On Tue, Aug 5, 2008 at 2:27 AM, John Kaputin (gmail) [EMAIL PROTECTED]wrote:
I noticed that the package names for the 2 tools (converter and
wsdl-viewer) use different
I have some more thoughts on the source tree restructuring. I'm happy to
make the changes in the woden211 branch if people agree.
1) Could we change 'woden-commons' to 'woden-common' as this directory just
holds common woden code (not multiple common projects as per ws-commons).
2) Could we
this plugin not to use .java files
from the resources folders.
So I would not encourage such a use.
So we should remove these files and switch to the Javadoc kind of use.
Regards
Jeff MAURY
On 8/4/08, John Kaputin (gmail) [EMAIL PROTECTED] wrote:
The text files called 'about-this-package' were
I noticed that the package names for the 2 tools (converter and wsdl-viewer)
use different styles:
The converter package name under the java folder is
org.apache.woden.converter (it used to be org.apache.woden.tool.converter)
The wsdl-viewer directory structure under the css and javascript
Jeremy,
I've removed the woden47 and woden62 branches, as they have already been
merged into trunk and are no longer needed. I've recently opened woden209
and will finish that asap - I can refactor it into the new source tree if
necessary. Sagara's contributions in woden65 need to be merged into
Hi Sagara,
I committed your recent serialization patches to the woden65 branch
yesterday (thanks), but I haven't finished reviewing them yet.
If you're keen for more work, I was just reviewing the open JIRAs and
noticed a new one, WODEN-208, which looks like a useful fix, but not
something I have
it into woden-tool, but
don't know exactly how to do: if I put it as a resource, it will be in the
woden-tool JAR, do you think this is ok ?
Regards
Jeff MAURY
On Thu, Jul 3, 2008 at 4:20 PM, John Kaputin (gmail) [EMAIL PROTECTED]
wrote:
Jeff,
I think option 3 seems best too, although my
Just a quick reminder, in case new woden contributors are not aware - please
can everyone follow the java coding conventions for the Woden project
documented at http://ws.apache.org/woden/dev/devprocess.html#Source+Code.
Preferrably, set your IDE up to format to these conventions automatically.
/2008 06:36 AM
Please respond to
[EMAIL PROTECTED] woden-dev@ws.apache.org
To
[EMAIL PROTECTED] woden-dev@ws.apache.org
cc
Subject
equals method (was: Re: Questions about tests)
Hi John,
2008/6/23 John Kaputin (gmail) [EMAIL PROTECTED][EMAIL PROTECTED]
:
The WSDL 2
-939-5063
*John Kaputin (gmail) [EMAIL PROTECTED]*
07/07/2008 01:10 PM
Please respond to
woden-dev@ws.apache.org
To
woden-dev@ws.apache.org cc
Subject
Re: equals method (was: Re: Questions about tests)
Arthur,
there was some discussion last month on the original thread [1
?
And the existing WSDLComponent.equals(WSDLComponent) method will be
deprecated and removed at some point, in favour of
isEquivalentTo(WSDLComponent).
regards,
John.
On Tue, Jul 8, 2008 at 10:10 AM, John Kaputin (gmail) [EMAIL PROTECTED]
wrote:
Arthur,
there's no technical problem with your suggestion. +1
Jeff,
I think option 3 seems best too, although my knowledge of Maven is still a
bit limited. I assume you will also refactor the converter and wsdl printer
into woden-tools?
thanks, John.
On Fri, Jun 27, 2008 at 3:30 AM, Lawrence Mandel [EMAIL PROTECTED] wrote:
Jeff,
I'm in favour of
it. That was a criteria when we introduced the Maven
build. Any change to the project directory structure must not break the ANT
build, so that will need to be changed too.
regards,
John.
On Mon, Jun 23, 2008 at 11:22 PM, Jeff MAURY [EMAIL PROTECTED]
wrote:
On Mon, Jun 23, 2008 at 4:17 PM, John Kaputin (gmail
building the 3 jars
- woden-api, woden-dom-impl and woden-om-impl so just rolling the
common impl classes into the dom-impl and om-impl jars).
regards,
John.
On Tue, Jun 24, 2008 at 10:48 PM, Jeff MAURY [EMAIL PROTECTED]
wrote:
On Tue, Jun 24, 2008 at 3:00 PM, John Kaputin (gmail) [EMAIL
Hi Jeff,
last year when the ANT and Maven build was changed to separate the API and
the DOM and OM implementations, there was some talk about building the WSDL
2.0 tools into a separate tools module. At that time the only tool was the
converter, but the WSDL 2 printer has since been added. This
The WSDL 2 spec talks about equivalence between components. This is to do
with collapsing equivalent components derived from different parts of the
XML infoset into a single component in the Component model. I think there
are some assertions about it too. If I remember correctly, that was the
Folks,
I haven't really looked at this since Dan Harvey implemented the fragid
support using XPointer last year, but give me a couple of days and I'll
review this bit of the spec and the code and then reply to this thread.
John.
On Wed, May 14, 2008 at 6:36 AM, Arthur Ryman [EMAIL PROTECTED]
Arthur,
no, I just pointed out his post to the mailing list. Lawrence has since
responded about working on the converter. I will take a look at the fragid
impl and see what needs to be done.
John.
On Wed, May 14, 2008 at 6:21 AM, Arthur Ryman [EMAIL PROTECTED] wrote:
John,
Are you
Hi Sagara,
I will have time later this week to revisit woden65 and see where I got to
with your serialization work. I'll also fix the POM files as you suggest -
you can send a patch with the fixes if you have them.
thanks,
John.
On Wed, May 14, 2008 at 2:27 AM, Sagara Gunathunga
[EMAIL
Lawrence (or any other woden committer),
can you please apply this patch to woden SVN for me, as I seem to have an
SVN authentication problem I haven't figured out yet and I'd like to roll a
new M8 build asap. The patch updates the release notes and properties file
with the latest version nos.
Lawrence,
apologies. I just saw your vote email for M8 take 2. Please ignore my
comment about rolling a new M8. I am downloading it now to test, before
responding to the vote.
regards,
John.
On Wed, Apr 23, 2008 at 4:35 PM, John Kaputin (gmail) [EMAIL PROTECTED]
wrote:
Lawrence (or any other
+1.
tested the take2 woden jars against the W3C WSDL 2.0 test suite. They're
good.
regards,
John.
On Fri, Apr 18, 2008 at 8:31 AM, Arthur Ryman [EMAIL PROTECTED]
wrote:
+1
-- Arthur
On Thu, Apr 17, 2008 at 3:06 PM, Davanum Srinivas [EMAIL PROTECTED]
wrote:
-BEGIN PGP SIGNED
Thanks Dims. Woden is fine with XmlSchema 1.4.2.
regards,
John Kaputin.
On Mon, Apr 21, 2008 at 10:48 AM, Davanum Srinivas [EMAIL PROTECTED]
wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
FYI
- Original Message
Subject: Deed is done! (Re: [VOTE] XmlSchema-1.4.2 /
Thanks Dims. Woden is fine with XmlSchema 1.4.2.
regards,
John Kaputin.
On Mon, Apr 21, 2008 at 10:48 AM, Davanum Srinivas [EMAIL PROTECTED]
wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
FYI
- Original Message
Subject: Deed is done! (Re: [VOTE] XmlSchema-1.4.2 /
=revrevision=648283
|
| and see if it works for you.
|
| -- dims
|
| John Kaputin (gmail) wrote:
| | Sorry, forgot to provide a test case:
| |
| |
|
http://dev.w3.org/2002/ws/desc/test-suite/documents/good/Chameleon-1G/getBalance.wsdl
|
| |
| | The inlined schema in this WSDL2 doc includes
was automatically running the
W3C test suite. Is the W3C suite not included in the JUnit test suite?
Lawrence
John Kaputin (gmail) [EMAIL PROTECTED]
04/14/2008 01:40 PM
Please respond to
woden-dev@ws.apache.org
To
woden-dev@ws.apache.org
cc
Subject
Re: [VOTE] Woden 1.0M8 Release
assistant: +1-905-413-3831, TL 313-3831
fax:+1-905-413-4920, TL 313-4920
mobile: +1-416-939-5063
*John Kaputin (gmail) [EMAIL PROTECTED]*
04/10/2008 08:47 AM
Please respond to
woden-dev@ws.apache.org
To
woden-dev@ws.apache.org cc
Subject
Re: Please review M8
With XmlSchema 1.4.1 we are seeing a regression in the Woden test results
for the W3C WSDL 2.0 test suite. We see 4 test cases fail which passed
successfully when Woden was last tested with XmlSchema 1.3.1. It seems to
be related to chameleon includes (including a schema that has no TNS). In
With XmlSchema 1.4.1 we are seeing a regression in the Woden test results
for the W3C WSDL 2.0 test suite. We see 4 test cases fail which passed
successfully when Woden was last tested with XmlSchema 1.3.1. It seems to
be related to chameleon includes (including a schema that has no TNS). In
string.
regards,
John Kaputin.
On 4/15/08, John Kaputin (gmail) [EMAIL PROTECTED] wrote:
With XmlSchema 1.4.1 we are seeing a regression in the Woden test results
for the W3C WSDL 2.0 test suite. We see 4 test cases fail which passed
successfully when Woden was last tested with XmlSchema 1.3.1
With XmlSchema 1.4.1 we are seeing a regression in the Woden test results
for the W3C WSDL 2.0 test suite. We see 4 test cases fail which passed
successfully when Woden was last tested with XmlSchema 1.3.1. It seems to
be related to chameleon includes (including a schema that has no TNS). In
string.
regards,
John Kaputin.
On 4/15/08, John Kaputin (gmail) [EMAIL PROTECTED] wrote:
With XmlSchema 1.4.1 we are seeing a regression in the Woden test results
for the W3C WSDL 2.0 test suite. We see 4 test cases fail which passed
successfully when Woden was last tested with XmlSchema 1.3.1
Lawrence,
did you test against the W3C test suite? I am getting 4 failures in the
'good' test suite testing against Woden trunk. Chameleon-1G, 2G, 3G and 4G
are missing ElementDeclaration components in the Description component. Not
sure why yet, but will continue looking into it tomorrow. Let me
Lawrence,
The release notes refer to the Interop Dashboard results. Have these been
updated to reflect the latest W3C test results for M8 (trunk)? This requires
the ant-test result files to be checked in, then Arthur or some other WG
member to run the W3C tests and update the results page (note,
Hi Sagara,
I'm going to be travelling for the next week or two with limited time to
work on Woden, but will finish reviewing the wsdl writer after that.
thanks,
John Kaputin.
On 3/24/08, Sagara Gunathunga [EMAIL PROTECTED] wrote:
Hi John,
With my last contribution, I have completed most of
+1 to moving Axis2 to Java 5. With Woden currently at Java 1.4 (to support
Axis2) we provide a type-safe API using typed arrays. We would prefer to use
Java 5 generics.
+1 to previous suggestions about supporting existing Axis2 uses tied to Java
1.4 by rolling up trunk into an Axis2 1.4 release
Axis2 devs,
I have implemented a solution for Jira WODEN-47 [1] which adds to the Woden
API generic access to WSDL 2.0 component extension properties. Woden still
supports the original extension-specific APIs, registered via the
ExtensionRegistry, and changes to that existing programming model
Axis2 devs,
I have implemented a solution for Jira WODEN-47 [1] which adds to the Woden
API generic access to WSDL 2.0 component extension properties. Woden still
supports the original extension-specific APIs, registered via the
ExtensionRegistry, and changes to that existing programming model
Tom,
I was attempting to run a local Axis2 maven build to investigate your
problem, but got sidetracked - sorry about that. Lawrence's suggestion was
what I had in mind anyway. Sandakith's recommendations are correct too. Is
this issue resolved now - please post if you're still have problems.
Tom,
I was attempting to run a local Axis2 maven build to investigate your
problem, but got sidetracked - sorry about that. Lawrence's suggestion was
what I had in mind anyway. Sandakith's recommendations are correct too. Is
this issue resolved now - please post if you're still have problems.
,
If the geronimo stax-api 1.0 is compatible with the codehaus stax-api
1.0.1 then I can't se why we couldn't swap the one used by Axiom... do
you know if Axiom will work with the geronimo jar?
David
On 21/08/07, John Kaputin (gmail) [EMAIL PROTECTED] wrote:
Axis2 and Axiom redistribute
Axis2 and Axiom redistribute the stax-api-1.0.1.jar file from the Codehaus
StAX project under the Apache License 2.0, however it is not initially
distributed under this license. The jar file does not contain a license
file and the only reference to licensing on the StAX project website (
Axis2 and Axiom redistribute the stax-api-1.0.1.jar file from the Codehaus
StAX project under the Apache License 2.0, however it is not initially
distributed under this license. The jar file does not contain a license
file and the only reference to licensing on the StAX project website (
Please find attached a patch file containing a new testcase, Interface-6B,
which I would like to contribute to the WSDL 2.0 assertion test suite.
This testcase violates interface extension assertion Interface-1009 in a
similar way to the existing test Interface-3B. However, this new testcase
We are planning a Woden M8 release for end of July to complete the W3C spec
compliance for WSDL 2.0 assertions. WSDL 2.0 has just become a W3C
Recommendation.
I expect M8 development to complete by 20th July, with maybe 1 week of
release mgt after that. Might be able to bring M8 forward a bit
We are planning a Woden M8 release for end of July to complete the W3C spec
compliance for WSDL 2.0 assertions. WSDL 2.0 has just become a W3C
Recommendation.
I expect M8 development to complete by 20th July, with maybe 1 week of
release mgt after that. Might be able to bring M8 forward a bit
Sriram,
I've been away for a couple of weeks, but have now followed up on Arthur's
posts regarding WODEN-3.
I have renumbered assertion Schema-0016 to Schema-1066 via WODEN-149. I have
also uploaded a new patch for Messages.properties to WODEN-3 with an
improved message for Schema-1066. Would
I have uploaded new Woden test results after correcting the style defaulting
problem reported by Jacek, but Woden is still failing 2 test cases; RPC-1G
and RPC-2G. I think there's an ambiguity in the spec that has led to
different implementation assumptions between Woden and the Interchange
to the following EBNF [ISO/IEC
14977:1966] grammar, which represents the patterns for constructing the
request IRI.
regards,
John Kaputin.
On 5/4/07, John Kaputin (gmail) [EMAIL PROTECTED] wrote:
There is no WSDL assertion stating that an {http location} or
whttp:location must conform to the EBNF
or counterintuitive
to implement my:fancyDefaulting as a Woden extension.
Just something that we may want to be cautious about,
Jacek
On Thu, 2007-05-03 at 17:49 +0100, John Kaputin (gmail) wrote:
Jacek,
Originally, in Woden M6 (mid-2006), extension properties were grouped
strictly by namespace
Jacek,
Originally, in Woden M6 (mid-2006), extension properties were grouped
strictly by namespace into statically defined types like
HTTPBindingExtensions and SOAPBindingExtensions. So the isHttpCookies()
method was only present on HTTPBindingExtensions and to retrieve the
extension properties
Hi Deepal,
the Woden M7a release notes list Axiom 1.2.3 as a dependency, but I've just
tested M7a with Axiom 1.2.4 and it's okay. We now have 3 IPMC +1 votes so
I'll go ahead with the Woden M7a release today.
regards,
John.
On 4/20/07, Deepal jayasinghe [EMAIL PROTECTED] wrote:
Hi John ,
I
April 23 2007 - The Woden incubator project is please to announce its
Milestone 7a release!
This is an incremental release of Woden M7 which delivers an essential fix
to support the new shortened WSDL 2.0 namespace format.
Download the M7a release files and view the release notes at:
The results so far from woden-dev and WS general for the retry vote to
publish the Woden M7a release are:
Davanum Srinivas +1 (WSPMC binding, IPMC binding)
Aleksander Slominski +1 (WSPMC binding)
Jeremy Hughes +1 (WSPMC binding)
Ant Elder +1 (WSPMC binding)
Graham Turrell +1
John Kaputin +1
As
The Woden incubator project is developing a WSDL 2.0 processor in
conjunction with efforts of the W3C to deliver the new WSDL
2.0specification. The Woden project team would like to ask the
Incubator PMC
for approval to publish the Woden Milestone 7a release to support the
upcoming Apache WS Axis2
.
On 4/16/07, Guillaume Nodet [EMAIL PROTECTED] wrote:
It seems the incubator disclaimers are missing from the jars.
They are usually stored in META-INF/DISCLAIMER along with the LICENSE and
NOTICE files.
On 4/16/07, John Kaputin (gmail) [EMAIL PROTECTED] wrote:
Woden devs and WSPMC,
Please vote
Resending to the WS general list as the first attempt failed.
-- Forwarded message --
From: John Kaputin (gmail) [EMAIL PROTECTED]
Date: Apr 12, 2007 12:47 PM
Subject: [VOTE] Woden M7a release
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Woden devs and WSPMC,
An interim release
,
On 12/04/07, John Kaputin (gmail) [EMAIL PROTECTED] wrote:
[...]
2) XmlSchema 1.3, which will be released soon. In the meantime, M7a-RC1
is
dependent on XmlSchema 1.3 RC3.
XmlSchema 1.3 RC2 is in the apache-woden-incubating-1.0M7a-RC1.zip as
well as the RC3. Is this a mistake? Also, the axiom
the issue ran the latest woden code against
it
(Running the maven build should take care of everything ?) and
the
build succeeds. I've posted RC2 at the same location.
Please let me know of any further issues.
Ajith
On 3/30/07, John Kaputin (gmail) [EMAIL
the issue ran the latest woden code against
it
(Running the maven build should take care of everything ?) and
the
build succeeds. I've posted RC2 at the same location.
Please let me know of any further issues.
Ajith
On 3/30/07, John Kaputin (gmail) [EMAIL
Ajith,
Woden has 5 test case failures when using XmlSchema 1.3 RC1. These were OK
with XmlSchema 1.2. All 5 test cases contain xs:import statements and the
NPE occurs when Woden calls the XmlSchemaExternal.getSchema() method.
Here's the code fragment from Woden's ComponentModelBuilder class
, John Kaputin (gmail) [EMAIL PROTECTED] wrote:
Ajith,
Woden has 5 test case failures when using XmlSchema 1.3 RC1. These were OK
with XmlSchema 1.2. All 5 test cases contain xs:import statements and
the NPE occurs when Woden calls the XmlSchemaExternal.getSchema() method.
Here's the code fragment
, John Kaputin (gmail) [EMAIL PROTECTED] wrote:
Ajith,
Woden has 5 test case failures when using XmlSchema 1.3 RC1. These were OK
with XmlSchema 1.2. All 5 test cases contain xs:import statements and
the NPE occurs when Woden calls the XmlSchemaExternal.getSchema() method.
Here's the code fragment
I have changed Apache Woden to use the new WSDL2 namespaces of the form
/ns/wsdl, as per the editors copies of the WSDL2 spec. The WSDL2
namespace for SOAP 1.1 HTTP bindings, as used in {soap underlying protocol},
has not changed so this is still in the form /2006/01 in Woden. See Apache
JIRA
The document at the namespace URL http://www.w3.org/ns/wsdl/soap specifies
the following URLs for the soap.xsd file:
1) http://www.w3.org/2002/ws/desc/ns/soap.xsd for the latest version,
including errata (this currently points to the 2006/03/21 version).
2) http://www.w3.org/2007/03/wsdl/soap.xsd
The Apache Woden M7 release depends on the schemas at the following URLs:
http://www.w3.org/2006/01/wsdl/wsdl20.xsd
http://www.w3.org/2006/01/wsdl-extensions.xsd
http://www.w3.org/2006/01/wsdl/http.xsd
http://www.w3.org/2006/03/wsdl-instance.xsd
http://www.w3.org/2006/01/wsdl/rpc.xsd
and these classes can be
included the release files of those components?
thanks,
John
On 3/6/07, Ajith Ranabahu [EMAIL PROTECTED] wrote:
Hi John,
Did you mean to say to include the java5ns stuff in the release ? (The
release zip file )
On 3/6/07, John Kaputin (gmail) [EMAIL PROTECTED] wrote:
XmlSchema devs
XmlSchema devs,
Is there any plan to include javax.xml.namespace.QName and
javax.xml.namespace.NamespaceContext from the ws-commons Java5 project in
the XmlSchema releases so that in a pre-Java5 runtime XmlSchema will not
have external dependencies on these classes?
XmlSchema is dependent on
Jonathan/Arthur,
Woden is currently showing 1 red on the Component Model Test Results on the
Dashboard. This is due to a change made to the MessageTest-3G wsdl
(whttp:contentEncodingDefault corrected to whttp:contentEncoding for one of
the binding message references).
I have re-run the tests and
February 19th 2007 - The Woden incubator project has declared its Milestone
7 release!
Congratulations to the Woden team on delivering this release.
Download the M7 release files and view the release notes at:
http://people.apache.org/dist/ws/woden/milestones/1.0M7-incubating/
More
on that page. I also
don't see a KEYS file in svn that would list the gpg keys that would be
used.
Dan
On Thursday 15 February 2007 13:11, John Kaputin (gmail) wrote:
If anyone else wants to review the Woden M7 release candidate and vote,
please note that the M7 release files are now available
The voting results so far for the Woden M7 release are:
+1 Deepal Jayasinghe (WSPMC binding)
+1 Davanum Srinivas (WSPMC binding, IPMC binding)
+1 Jeremy Hughes (WSPMC binding)
+1 Paul Fremantle (WSPMC binding, IPMC binding)
+1 Lawrence Mandel
+1 Arthur Ryman
+1 Graham Turrell
+1 John Kaputin
If anyone else wants to review the Woden M7 release candidate and vote,
please note that the M7 release files are now available at:
http://people.apache.org/~jkaputin/woden/milestones/1.0M7-incubating/
thanks,
John Kaputin.
On 2/15/07, John Kaputin (gmail) [EMAIL PROTECTED] wrote:
The voting
Woden is failing this new testcase but I think it's because there's an error
in the canonical baseline.
There are 2 interfaceMessageReferences each with an elementDeclaration child
which Woden's canonical wsdlcm reports as:
elementDeclaration ref=c6 / and elementDeclaration ref=c6 /
The
I will not be able to attend the Implementors call on Thur 8th Feb.
John Kaputin.
I have an action item in the Minutes of the weekly call 25 Jan to create a
test case for the last outstanding test on the Interchange Test Coverage
Report. This is to test wsoap:header with required=false.
Two candidate test cases are attached as patch files:
1) If you want to include
/cr-issues/issues.html#CR144
*Jonathan Marsh* - http://www.wso2.com -
http://auburnmarshes.spaces.live.com
--
*From:* [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] *On
Behalf Of *John Kaputin (gmail)
*Sent:* Tuesday, January 23, 2007 2:45 PM
*To:* www-ws-desc
*Cc
Arthur,
the SOAP/HTTP extensions have changed to add:
{http query parameter separator default} to SOAPBindingExtensions
{http query parameter separator} toSOAPBindingOperationExtensions
As a result 27 testcases are now failing because the Woden interchange
format needs to be modified to emit
There's a spelling mistake in the WSDL for LocationTemplate-1G:
In the binding MixedPathsQueryParams,
whttp:queryParameterSeparaterDefault=;
should be spelt
whttp:queryParameterSeparatorDefault=;
i.e. 'Separater' should be spelt 'Separator'
So Woden is parsing this attribute as an
PROTECTED] *On
Behalf Of *John Kaputin (gmail)
*Sent:* Saturday, January 20, 2007 6:44 AM
*To:* www-ws-desc
*Cc:* woden-dev@ws.apache.org
*Subject:* Woden results should be 73 green / 1 red
I have got the SparqlQuery-1G test working in Woden and checked in the
latest Woden results. There are still 6
Keith,
as just discussed in the implementors call, I need to remove a method from
HTTPLocation as per the email below. Please advise by Friday 12th Jan if
this is a problem.
thanks,
John.
On 1/8/07, John Kaputin [EMAIL PROTECTED] wrote:
Chinthaka/Keith,
I have finished the HTTPLocation class
names in the http location template mapped to the correct message or
fault instance data?
thanks,
John Kaputin.
On 1/4/07, John Kaputin (gmail) [EMAIL PROTECTED] wrote:
Part 2, 6.7.1.1 Construction of the request IRI using the {http location}
property
This section contains the following
In defining the {http location} property the spec describes enclosing an
element local name within curly braces and it describes using double curly
braces to specify a single literal curly brace, but it is silent on the
possibility of extraneous, unmatched single curly braces appearing in the
Part 2 section 6.7.1.1 which describes the curly brace template syntax used
for {http location} contains the sentence:
A double curly brace (i.e. {{ or }}) MAY be used to include a single,
literal curly brace in the request IRI.
I am a bit confused about why this sentence is here. I assume it
Woden reports a URISyntaxException when parsing this WSDL:
Woden[Error],0:0,WSDL506,Could not create a URI from the string
?op=EchoInt;int={int};.,java.net.URISyntaxException:Illegal character
in query at index 16: ?op=EchoInt;int={int};
Woden is using the constructor of the class java.net.URI
WSDL4J v1.6.2 has just been released at http://sourceforge.net/projects/wsdl4j/.
It is incremental to v1.6.1, adding 3 new bug fixes, including a fix
for a potential NPE. See the release notes on the File download page
for details. Can you please use this for the upcoming Axis2 1.1
release.
Resending with Axis2 in subject line.-- Forwarded message --From: John Kaputin (gmail) [EMAIL PROTECTED]
Date: Nov 8, 2006 1:13 PMSubject: WSDL4J 1.6.2 releaseTo: axis-dev@ws.apache.orgCc: John Kaputin [EMAIL PROTECTED]
WSDL4J v1.6.2 has just been released at http://sourceforge.net
Arnaud,
according to the schema for W3C XML Schema at
http://www.w3.org/2001/XMLSchema.xsd the 'name' attribute of element is
xs:NCName so I think the behaviour you see with XmlSchema 1.0.3 is correct.
I think the problem with XmlSchema 1.1 is in SchemaBuilder.handleElement:
} else if
Done. WS-COMMONS-120.
On 11/2/06, Davanum Srinivas [EMAIL PROTECTED] wrote:
John,
JIRA please, the text gets mangled, so can't apply it.
thanks,
dims
On 11/2/06, John Kaputin (gmail) [EMAIL PROTECTED] wrote:
Can one of the regular XmlSchema developers please review this issue
Part 1 seems to be ambiguous about which data types from the XML Schema
namespace are automatically available in the component model, without
the need to import the XML Schema namespace.
Part 1 Section 3.1 says:
A WSDL 2.0 document that refers to any element
declaration or type definition
Can one of the regular XmlSchema developers please review this issue and the
patch below and confirm if it's appropriate for me to open a JIRA for this
and apply the patch.
The XmlSchema class inherits the equals(Object) method from XmlSchemaObject.
This method uses line number, line position
votes from the first VOTE request. Are
these still valid for the re-rolled release candidate or do I need to
start again and get three +1 binding votes for the re-rolled release.
regards,
John Kaputin.On 10/3/06, John Kaputin (gmail) [EMAIL PROTECTED] wrote:
I have re-rolled the Woden 1.0.0
Thanks Sanjiva.
Paul and Dims, are you still +1 on the re-rolled release?
regards,
John Kaputin
On 10/4/06, Sanjiva Weerawarana [EMAIL PROTECTED]
wrote:
Sorry guys .. +1 from me.Sanjiva.On Wed, 2006-10-04 at 11:52 +0100, John Kaputin (gmail) wrote: I have not yet had any response to the second
/mod_mbox/ws-woden-dev/200609.mbox/[EMAIL PROTECTED]
[2] Download, http://people.apache.org/dist/ws/woden/milestones/1.0.0M6-incubating/
[3] Release files are in directory /home/jkaputin/wodenM6 at people.apache.org
Thanks,
John Kaputin
On 9/29/06, John Kaputin (gmail) [EMAIL
Robert,
Sorry for the delayed response - hardware problem. I'll rework the release later today, based on your comments.
regards,
John Kaputin.,On 9/27/06, robert burrell donkin [EMAIL PROTECTED] wrote:
On 9/27/06, John Kaputin (gmail) [EMAIL PROTECTED]
wrote: The Woden developer community has
, this release
contains these fixes. We have tested WSDL4J v1.6.1 with the Axis2 test
suite (from SVN trunk) and the tests pass successfully.
Any chance of getting WSDL4J v1.6.1 into Axis2?
regards,
John KaputinOn 9/25/06, John Kaputin (gmail) [EMAIL PROTECTED] wrote:
Dims,
I have fixed
For the Woden committers vote on the M6 release we now have no -1 votes, no 0 votes and six +1 votes from:
Chinthaka
Arthur
Jeremy
Oshani
Dims
John
So I will now request a vote for the M6 release from the Incubator PMC.
regards,
John Kaputin.On 9/26/06, Eran Chinthaka [EMAIL PROTECTED] wrote:
The Woden developer community has voted on and approved a proposal to
release Woden 1.0.0 M6 (Milestone 6). The proposal recieved six +1 votes,
including three from WS PMC members. There were no -1 or 0 votes. The proposal can be seen at [1].
The six +1 votes were from:
Eran Chinthaka (WS PMC)
1 - 100 of 118 matches
Mail list logo
