Tomi, I understand that your site uses the W3C XSLT server. I regard your site as a service to end users. What I was proposing is that we simply build the all-in-one xslt and publish it at a durable, public URL. Then anyone who wants the latest copy can simply reference it. Your site could reference the Woden site to get the latest version.
People should be able to insert an stylesheet processing instruction in their WSDL documents and reference the Woden hosted version of the viewer. Then the brower should be able to transform the WSDL without using the W3C service. Can you see any reason why that wouldn't work? Arthur Ryman, PhD, AoT, DE Process and Portfolio Management, Rational Division phone: +1-905-413-3077, TL 313-3077 assistant: +1-905-413-3831, TL 313-3831 fax: +1-905-413-4920, TL 313-4920 mobile: +1-416-939-5063, text: [EMAIL PROTECTED] "tomi vanek" <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 12/17/2007 12:15 PM Please respond to woden-dev@ws.apache.org To woden-dev@ws.apache.org cc Subject Re: Agenda of the Woden Status Telecon, 2007-12-11 Arthur, Well - I do not host any service per-se - I am using w3c WSLT service for creating the HTML - so the 'service' is just a link (concatenated by JavaScript): http://www.w3.org/2000/06/webdata/xslt?xslfile=http://tomi.vanek.sk/xml/wsdl-viewer.xsl&xmlfile=http://api.google.com/GoogleSearch.wsdl&transform=Submit This is a nice feature if somebody accidentally comes around and wants to see what the XSLT does / if it works for him. So the only think we really need is a nice intuitive permanent address for the XSLT. One more think to consider: the current version is modularized into more XSLT files, but for the end-user it could be easier to handle an all-in-one version. This version is concatenated by an ant + xslt (in java/wsdl-viewer/build) and zipped into a download-package. So the master maven task could include also the wsdl-viewer ant task into the continuous integration job... tomi On Dec 17, 2007 5:11 PM, Arthur Ryman <[EMAIL PROTECTED]> wrote: Lawrence, I wasn't planning on hosting a service like Tomi, just publish the xslt at a durable, public place where people can reference it. Arthur Ryman, PhD, AoT, DE Process and Portfolio Management, Rational Division phone: +1-905-413-3077, TL 313-3077 assistant: +1-905-413-3831, TL 313-3831 fax: +1-905-413-4920, TL 313-4920 mobile: +1-416-939-5063, text: [EMAIL PROTECTED] Lawrence Mandel/Toronto/[EMAIL PROTECTED] 12/10/2007 09:28 PM Please respond to woden-dev@ws.apache.org To woden-dev@ws.apache.org cc [EMAIL PROTECTED] Subject Re: Agenda of the Woden Status Telecon, 2007-12-11 What about including an automatic publish in our release process? That way we will update the service when we release a new version of the WSDL pretty printer. Lawrence Arthur Ryman/Toronto/[EMAIL PROTECTED] 12/10/2007 02:23 PM Please respond to woden-dev@ws.apache.org To woden-dev@ws.apache.org cc [EMAIL PROTECTED], woden-dev@ws.apache.org Subject Re: Agenda of the Woden Status Telecon, 2007-12-11 +1 for automating the publish step. Maybe this can be triggered from SVN? Of maybe we provide a script and some one (an admin) just runs it manually with their credentials. Arthur Ryman, PhD, AoT, DE Process and Portfolio Management, Rational Division phone: +1-905-413-3077, TL 313-3077 assistant: +1-905-413-3831, TL 313-3831 fax: +1-905-413-4920, TL 313-4920 mobile: +1-416-939-5063, text: [EMAIL PROTECTED] "Jeremy Hughes" <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 12/10/2007 02:08 PM Please respond to woden-dev@ws.apache.org To woden-dev@ws.apache.org cc Subject Re: Agenda of the Woden Status Telecon, 2007-12-11 +1 to having this available from our web site. Howabout automating it so that the latest snapshot build is deployed to our site. That would be much more preferable than manually updating it. Jeremy On 10/12/2007, Arthur Ryman <[EMAIL PROTECTED]> wrote: Lawrence, My status on: 2007-12-04 - Arthur will review Tomi Vanek's WSDL pretty printer contribution. Arthur (via dev list): I have looked at Tomi's code and asked him to insert the Apache Licence before I commit it. I committed the code over the weekend so you can close this item. I also created a test script and reported errors WODEN-188. I assign that to Tomi so it's business as usual for now. I do have a question though. We should make this wsdl-viewer.xsl available at a public, permanent, URL on the Woden site. Suggestions? Also, how should be handle publishing updates to it? i.e. what;s the process for updating Web content? Arthur Ryman, PhD, AoT, DE Process and Portfolio Management, Rational Division phone: +1-905-413-3077, TL 313-3077 assistant: +1-905-413-3831, TL 313-3831 fax: +1-905-413-4920, TL 313-4920 mobile: +1-416-939-5063, text: [EMAIL PROTECTED] Lawrence Mandel/Toronto/[EMAIL PROTECTED] 12/10/2007 01:32 PM Please respond to woden-dev@ws.apache.org To woden-dev@ws.apache.org cc Subject Agenda of the Woden Status Telecon, 2007-12-11 See [1] for call and IRC information. [1] http://incubator.apache.org/woden/dev/index.html#Weekly+Status+Call Agenda 1. Open Action Items - Lawrence Mandel 2007-12-04 - Lawrence will create a wiki page with thoughts on the assertion API. 2007-12-04 - Arthur will review Tomi Vanek's WSDL pretty printer contribution. Arthur (via dev list): I have looked at Tomi's code and asked him to insert the Apache Licence before I commit it. 2. Milestone 8 (M8) Status - John Kaputin 3. Graduation from Incubation - Lawrence Mandel 4. Development Discussion - All 5. Other Business - All Thanks, Lawrence Mandel --------------------------------------------------------------------- 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]
