[wsas-java-dev] Re: Try It! functionality
saminda abeyruwan
saminda at wso2.com
Fri May 25 05:21:41 PDT 2007
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
When we integrated new functionality to WSAS we came across the
following problems to version service. WSDL2 for version service is
attached herewith.
this._endpointDetails =
70 {
71 "versionSOAP12port0": {
72 "type" : "",
73 "address" : "https://10.100.1.110:9443/services/version"
74 },
75 "versionSOAP11port0": {
76 "type" : "",
77 "address" : "https://10.100.1.110:9443/services/version"
78 },
79 "versionSOAP11port1": {
80 "type" : "",
81 "address" : "https://10.100.1.110:9443/services/version"
82 },
83 "versionSOAP12port1": {
84 "type" : "",
85 "address" : "https://10.100.1.110:9443/services/version"
86 }
87 };
As you can see "type" property is "". This cause WSRequest's send method
to fail at
var soapVer = WSRequest.util._bindingVersion(this._optionSet); line 79
In addition to this, the payload pass to callback method is undefined.
Does object.innerText work with Firefox.
Thank you
Saminda
Jonathan Marsh wrote:
> Interestingly enough the links are currently under discussion on mashup-dev,
> and I'd added a parameter just this morning in case you needed it for
> locating WSRequest. So I've added a similar parameter for stubs:
>
> wsrequest-location: defaults to 'WSRequest.js', or you can specify your
> own URL.
>
> stub-location: defaults to {$service-name}.stub.{js | e4x} for now, or you
> can specify your own URL.
>
>
>
> Jonathan Marsh - http://www.wso2.com - http://auburnmarshes.spaces.live.com
>
>
>> -----Original Message-----
>> From: saminda abeyruwan [mailto:saminda at wso2.com]
>> Sent: Thursday, May 24, 2007 5:11 AM
>> To: Jonathan Marsh
>> c: 'Afkham Azeez'; Thilina Gunarathne
>> Subject: Re: Try It! functionality
>>
> Hi,
>
> Jonathan Marsh wrote:
>>>> The plan is a little more complicated:
>>>>
>>>> WSDL2.0 --> using (wsdl2sig.xslt)
>>>> --> .sig format
>>>> --> using (tryit.xslt)
>>>> --> tryit.html
>>>> --> using (jsstub.xslt)
>>>> --> .stub.js (imported by tryit.html)
> We would like to follow the prior as the starting point. We are
> planning
> to integrate this into WSAS as follows,
>
> 1. Generate the tryit.html, using generated .sig formate and put it in
> to a Map, with a generated key. (say 1000)
>
> 2. Generate the foo.stub.js (imported by tryit.html) and put it into a
> Map with a generated key. (say 2000).
>
>
> Once generated, in WSAS we called for tryit.html using GET. Inside
> WSAS,
> there is a file download filter mapped to "/filedownload", which serve
> this request. Thus, the request should be as follows,
>
> http://127.0.0.1:9762/wso2wsas/filedownload?id=1000
>
> Now we faced the problem,
>
> tryit.html is importing its corresponding js file with,
>
> <script type="text/javascript" src="foo.stub.js"></script>
>
> as you can see if the "src" is as above, this will try to import file
> from
>
> http://127.0.0.1:9762/wso2wsas/foo.stub.js
>
> but this does not exits here, it will reside in,
>
> http://127.0.0.1:9762/wso2wsas/filedownload?id=2000
>
> Thus, if a global param can be given to tryit.xsl such as
>
> <xsl:param name="genStub"/>
>
> and script generation choose can be updated as follows,
>
> <xsl:choose>
> <xsl:when test="$e4x">
> <script type="text/javascript; e4x=1"
> src="{$service-name}.stub.e4x"></script>
> </xsl:when>
> <xsl:when test=$genStub>
> <script type="text/javascript" src="{$genStub}"></script>
> </xsl:when>
> <xsl:otherwise>
> <script type="text/javascript"
> src="{$service-name}.stub.js"></script>
> </xsl:otherwise>
> </xsl:choose>
>
> and when generating the tryit.html we will injecting the value of
> "genStub" using the XSLT processor.
>
> Is it possible to have the prior XSLT fragment.
>
> Thank you,
>
> Saminda
>
>>>> Also I'm updating tryit.html to use the native JavaScript WSRequest,
> so it
>>>> will work on all browsers without any plug ins.
>>>>
>>>> I also can generate
>>>> --> using (tryit.xslt)
>>>> --> tryit.e4x.html
>>>> --> using (e4xstub.xslt)
>>>> --> .stub.e4x (imported by tryit.e4x.html)
>>>> But with the new WSRequest work this isn't really necessary to expose
> to the
>>>> user.
>>>>
>>>> Jonathan Marsh - http://www.wso2.com -
> http://auburnmarshes.spaces.live.com
>>>>> -----Original Message-----
>>>>> From: saminda abeyruwan [mailto:saminda at wso2.com]
>>>>> Sent: Tuesday, May 22, 2007 11:00 PM
>>>>> To: Jonathan Marsh
>>>>> Cc: Afkham Azeez
>>>>> Subject: Re: Try It! functionality
>>>>>
>>>> Hi Jonathan,
>>>>
>>>>
>>>>>>> I'll have a fairly major check-in in a day or two - besides that
> what
>>>> can I
>>>>>>> do to help you start integrating the ajax try-it into wsas?
>>>>>>>
>>>> Great. We are looking forward to this in WSAS. The current "try-it"
>>>> related codes are in commons/codegen project
>>>> "AjaxClientGeneratorService" java class. Here what we do is, get the
>>>> WSDL1.1 and using AJAX emitter, we create the html page. This html
> page
>>>> is stored in a MAP with a unique key, then this unique key is send
> back
>>>> to client. When ever client wants to access this he use a GET with
> this
>>>> unique ID.
>>>>
>>>>
>>>> With your AJAX try-it, the management is same. I can help you with
>>>> integrating the new try-it feature to WSAS.
>>>>
>>>> Is the following action plan is correct,
>>>>
>>>> WSDL2.0 --> using (wsdl2sig.xslt) --> .sig format --> using
>>>> (tryit.xslt)
>>>> --> tryit.html
>>>>
>>>> How should jsstub.xslt and e4xstub.xslt come into picture.
>>>>
>>>> Thank you
>>>>
>>>> Saminda
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>>>>> -----Original Message-----
>>>>>>>> From: Afkham Azeez [mailto:azeez at wso2.com]
>>>>>>>> Sent: Friday, May 18, 2007 5:13 AM
>>>>>>>> To: jonathan at wso2.com
>>>>>>>> Cc: thilina at wso2.com; sanka at wso2.com; saminda at wso2.com
>>>>>>>> Subject: Try It! functionality
>>>>>>>>
>>>>>>>> Hi Jonathan,
>>>>>>>> We are planning to have a fully fledged implementation of "Try
> It!"
>>>> in
>>>>>>>> WSAS 2.0. We are planning to use your implementation & scrap the
>>>>>>>> current implementation which has many limitations. Will you be
> able
>>>> to
>>>>>>>> finish it in time for WSAS 2.0? (at least July 15th)
>>>>>>>>
>>>>>>>> Thanks
>>>>>>>>
>>>>>>>> Afkham Azeez
>>>>>>>> GPG Fingerprint: 643F C2AF EB78 F886 40C9 B2A2 4AE2 C887 665E
> 0760
>>>>>>>> http://www.wso2.org
>>>>>>>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGVtTUYmklbLuW6wYRAmDaAKCnoG6fNtN1gHfOrYK3wOTgsulrKQCdEYIe
sQYsFGHfalWRHe4goti/ImA=
=eNg3
-----END PGP SIGNATURE-----
-------------- next part --------------
A non-text attachment was scrubbed...
Name: version.wsdl
Type: text/xml
Size: 3601 bytes
Desc: not available
Url : http://wso2.org/pipermail/wsas-java-dev/attachments/20070525/4bcb2bf1/version.bin
More information about the Wsas-java-dev
mailing list