Thanks for the heads-up, Helder.
I do know that the Oracle web interface requires that ALL incoming
parameters be defined in the procedure spec, otherwise it fails to find
a matching procedure to activate/run. Oracle provides the ability to
overload the same procedure name with different parameter lists/types,
and this gets in the way when it can't determine the appropriate
overloaded procedure based on incoming parameters in the request. So,
it might have been as easy as making sure the no-cache parameter was
included in the procedure parameter list. Unfortunately, it makes
server development a bit trickier than PHP coding, where you can define
any parameters in the request, whether they get used in the PHP code or
not.
I appreciate the added information. It's good to have this reference in
case the problem crops up for me.
I do a fair amount of Oracle PL/SQL development for a couple of my
clients, and I really want to be able to leverage the power of Qooxdoo
widgets in my Oracle-based projects. This is critical for moving my
implementations beyond mere HTML code - I'm completely surprised that
Oracle hasn't built JSON capability into their provided packages, but I
was able to find and install PL/JSON from Sourceforge to provide the
needed JSON conversion capabilities in my PL/SQL code.
I'll keep the list updated on my progress.
Thanks,
Gene
On Wed, 2009-12-02 at 08:06 -0800, Helder Magalhães wrote:
> Hi Gene,
>
>
>
> Gene Amtower wrote:
> >
> > All of Christian's activity on the RPC servers has prompted me to re-
> > engage my efforts at creating an Oracle-based PL/SQL RPC server.
> >
>
> Glad to know you are motivated again. :-)
>
>
>
> Gene Amtower wrote:
> >
> > If any other Oracle developers know of anything that might be helpful,
> > please share your thoughts and ideas.
> >
>
> With basically no experience with PL/SQL (only a couple of experiments
> during uni.), I did bump at a weird behavior to which I only found in Oracle
> documentation. The issue is already solved in the framework but, as it isn't
> the default behavior, being aware about it may save you from a headache
> whenever you actually start doing client<-->server communication. ;-)
>
>
> Hope this helps,
> Helder
>
>
> [1] http://bugzilla.qooxdoo.org/show_bug.cgi?id=1017#c7
------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing.
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
