Thanks for the clarification. As I see it TUSCANY-1297 should be
assigned to #11012. #11004 is an issue that I feel I was able to solve
by hacking the SCA WSDL generator code. I think Matthew may disagree
with my raised issue (looking forward to his response), but it is
entirely solvable in the PHP code.
> -----Original Message-----
> From: firstname.lastname@example.org [mailto:[EMAIL PROTECTED] On
> Behalf Of Caroline Maynard
> Sent: June 11, 2007 12:15 PM
> To: email@example.com
> Subject: [phpsoa] Re: Time for DUNLIN to peck its way out?
> Michael Caplan wrote:
> > I'd like to petition to get Bug #11004 (WSDL Generated Does Not
> > Validate) and Request #10994 (Business Exceptions Data Returned to
> > Client) in this release.
> > Judging from [EMAIL PROTECTED] (sorry not sure who
> that is) final comment on
> > #11004, I think this ticket is being confused with Request #11012
> > (Visual Studio Consumption of SCA Generated WSDL) as suggested by
> > referenced by the Tuscany ticket. I believe #11012 should have the
> > Tuscany ticket associated. If #11004 is being confused, I'd like to
> > raise it hear again. The gist of #11004 is WSDL validation, and if
> > am correct about this, the fix seems to be simple, and outlined in
> > ticket.
> It was me, but only from the point of view of getting that bug
> according to our standard procedure for handing off bugs to Tuscany.
> Matthew had already raised it as a Tuscany JIRA, and my "contribution"
> was to update his link from 11004 to the Tuscany defect with one that
> would be clickable from within the PECL bug tracker.
> The Tuscany issue: http://issues.apache.org/jira/browse/TUSCANY-1297
> indeed the one about suppressing the xsi:type attribute, so I see what
> you mean. But I'm not sure whether the other one is also in Tuscany or
> in Matthew's WSDL generation code. I'll hope that he responds ...
> E-mail messages may contain viruses, worms, or other malicious code. By
> reading the message and opening any attachments, the recipient accepts full
> responsibility for taking protective action against such code. Henry Schein
> is not liable for any loss or damage arising from this message.
The information in this email is confidential and may be legally privileged. It
is intended solely for the addressee(s). Access to this e-mail by anyone else
You received this message because you are subscribed to the Google Groups
To post to this group, send email to firstname.lastname@example.org
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at