Chathura
On 6/2/06, Lawrence Mandel <[EMAIL PROTECTED]> wrote:
Excellent suggestions!
+1 to creating Jira's for work items
+1 to referencing the Jira ID in the commit comment
+1 to referencing the mailing list discussion and cutting over to Jira sooner rather than later
+1 for adding a comment to the Jira with the revision number
Lawrence
Arthur Ryman/Toronto/[EMAIL PROTECTED] 06/02/2006 08:58 AM
[email protected]
[EMAIL PROTECTED], [email protected] Re: Woden Access to XML Schema Schema
Jeremy,
+1, however we should cut over to JIRA as soon as it becauses clear that a bug exists or an enhancement is needed. Linking to the email thread is problematic since the thread can get quite tangled. Having the history laid out as a linear sequence of comments in JIRA makes it easy to follow the discussion. It's also easier to link to JIRA from email since JIRAs have predictable URLs.
Arthur Ryman,
IBM Software Group, Rational Division
blog: http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: [EMAIL PROTECTED]
"Jeremy Hughes" <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]06/01/2006 06:08 PM
[email protected]
[email protected] Re: Woden Access to XML Schema Schema
+1 for that. Also, it would be good to see the last comment in the JIRA being something like "fixed in r41xxxx" to indicate which revision of the repo the fix is in. Axis2 tend to do it like this.
There are of course many ways of working w.r.t commenting in JIRAs. I saw somewhere that a recommended way of discussing bugs was to have the discussion on the list then when there was a resolution to open a JIRA and link to the discussion in the mailing list archive.
Howabout this: during the course of a discussion if someone says "this is a bug please open a JIRA" then we do that & the bug gets a link to the discussion on the mail archive. Then further discussion happens on the JIRA. This is actually pretty close to what we do today in fact.
Cheers,
Jeremy
On 6/1/06, Arthur Ryman <[EMAIL PROTECTED] > wrote:
Graham,
You're welcome. :)
All,
I think we should be making more use of JIRA now to track issues and work items. In WTP, my Eclipse project, we adopted the practice of including the bugzilla number in every cvs commit comment, i.e. no one should commit a change without having an open bug. I have been openning JIRAs for every problem or work item I run across, and then when I commit the fix, I add the comment, e.g.
[WODEN- 24] Added the widget thing.
What does everyone think?
If you like this practice we could start by converting the Task List in the Wiki [1] into JIRAs and then add the link to the JIRA from the Wiki.
[1] http://wiki.apache.org/ws/FrontPage/Woden/TaskList
Arthur Ryman,
IBM Software Group, Rational Division
blog: http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: [EMAIL PROTECTED]
Graham Turrell < [EMAIL PROTECTED] > 05/31/2006 06:00 PM
[email protected]
[email protected] Re: Woden Access to XML Schema Schema
Arthur,
Many thanks. I resolve to check open issues more thoroughly in future :)
Kind Regards,
Graham.
_____________________________________________
Graham C Turrell CEng, MBCS
Chartered IT Practitioner
WebSphere ESB Foundation Technologies
DE3F16 / MP 211
IBM Labs
Hursley Park
Winchester, Hampshire
England. SO21 2JN
Tel +44-(0)1962-815018
email: [EMAIL PROTECTED]
"No army can withstand the force of an idea whose time
has come.". -Victor Hugo
Arthur Ryman
<[EMAIL PROTECTED]
> To
[email protected]
31/05/2006 21:25 cc
[email protected]
Subject
Please respond to Re: Woden Access to XML Schema
[EMAIL PROTECTED] Schema
he.org
Graham,
This has been reported in [1]. The fix is to use a catalog and uri resolver
that points to it.
[1] http://issues.apache.org/jira/browse/WODEN-14
Arthur Ryman,
IBM Software Group, Rational Division
blog: http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: [EMAIL PROTECTED]
Graham Turrell <[EMAIL PROTECTED] >
To
05/31/2006 02:12 PM [EMAIL PROTECTED]
rg
cc
Please respond to
[email protected] Subject
Woden Access to XML
Schema Schema
This could be another woden-user posting ?! :)
When I'm using Woden to read wsdl2.0 documents, it seems I need internet
connectivity, since WSDLReader.readWSDL()
goes out to find the XML Schema Schema document at
http://www.w3.org/2001/XMLSchema.xsd .
I may be missing something fundamental in the way I'm using the method.
But if not (and behaviour is by design), is there (or are there plans for)
a property that can be set to use an woden internal representation of
XMLSchema.xsd,
or perhaps even a local copy of the file? Not sure what the (wsdl4j)
precedent is here ...
Kind Regards,
Graham.
_____________________________________________
Graham C Turrell CEng, MBCS
Chartered IT Practitioner
WebSphere ESB Foundation Technologies
DE3F16 / MP 211
IBM Labs
Hursley Park
Winchester, Hampshire
England. SO21 2JN
Tel +44-(0)1962-815018
email: [EMAIL PROTECTED]
"No army can withstand the force of an idea whose time
has come.". -Victor Hugo
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Chathura Herath
http://people.apache.org/~chathura/
http://chathurah.blogspot.com/
