[wsas-java-dev] Re: [commons-dev] Improvements to adminui
javascript/AJAX library
saminda abeyruwan
saminda at wso2.com
Sun Mar 11 23:31:29 PDT 2007
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Sir,
Yes Sir, it's the same code in
http://wso2.org/repos/wso2/trunk/wsf/javascript/native/ we are referring
to.
>
>> I believe you are referring prior to WSRequest.js. The simplest solution
>> would be to start with native/WSRequest.js.
>
> I'm referring to the stuff at
> http://wso2.org/repos/wso2/trunk/wsf/javascript/native/. I think you
> meant the same right?
>
>> We propose that main.js contains functions related to a namespace
>> "WSO2.common", (ex: WSO2.common.send(args...)) will solve the namespace
>> issue.
>
> +1 but IMO it should be wso2.wsf.
main.js reside under commons/adminui project.
[https://wso2.org/repos/wso2/trunk/commons/adminui]. Should we use
"wso2.wsf" namespace for this too.
>
>> As an example, WSO2.common.send(args...) is the wrapper function that
>> uses WSRequest functionality to communicate with server. This is our
>> original plan and we were waiting for a release of WSRequest to achieve
>> this.
>
> No I disagree- if there's a need to wrap WSRequest then we haven't got
> WSRequest right. What is preventing you from doing
> foo=new wso2.wsf.WSRequest()
+1.
Should we do this to XPI and ActiveX Object too, namespace qualifying
WSRequest object.
Thank you
Saminda
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFF9PPAYmklbLuW6wYRAg77AKC60u7ghQ5rn/zN9jN2SFiipeySDACdE+K0
nTocYpyluVkbkZJafrQGr58=
=H+zg
-----END PGP SIGNATURE-----
More information about the Wsas-java-dev
mailing list