headers
Matthew Peters | 1 Jul 2008 15:37

Re: Explicitly specifying type of xsd:anyType in soap request


Hi Charlie, just to say that I am sorry to say that the person who is
looking into this is busy elesewhere right now so although I expect
him to get to it in time, right now it's on hold. Just thought I ought
to let you know. We do agree it needs fixing though.

Matthew

On Jun 24, 1:56 pm, "Charlie Moad" <cwm...@...> wrote:
> Thanks for looking into this.  I just did some testing with the php soap
> extension and specifying the type as "xsd:string" on the anyType argument
> indeed fixes my problem.  It would be great to somehow specify the type of
> the anyType.  Just trying to infer the type might not be powerful enough to
> detect complex types.
>
Permalink | Reply | 0 comments |
headers
Yannick | 9 Jul 2008 22:53
Picon

Re: Dokeos developers considering SCA


Just to keep you informed, about our progress, Kariboe has started
testing it out (I still haven't) but is concerned about the fact that
we have to install SCA/SDO as a server "plugin", which isn't super-
suitable for an open-source web project (it means we add a requirement
for potential users, which takes out the complete range of free-
hosting users).
I am personally not really concerned about this point as I'm expecting
our implementation to offer a conditional use of the web services we
would provide (either you have SCA/SDO and it works, or you don't and
it doesn't). Most of our user base will only want to use web services
if they have their portal hosted with some kind of caring hosting
provider.

Anyway... Dokeos 2.0 is planned only for mid-2009 but I'm still
hopeful I'm going to be able to implement it for a few stuff before
the end of the north-hemisphere's summer.

Bye,

Yannick
Permalink | Reply | 1 comment |
headers
Graham Charters | 17 Jul 2008 08:45

Re: Dokeos developers considering SCA


Hi Yannick, thanks for the update.

Having to install SCA/SDO as a plugin and the issue with Web hosts is
something we've agonized over on numerous occasions.  SCA itself is
user-land code, but it makes extensive use of SDO in the
implementation and also requires SDO for complex types.  SDO is the
extension code based on Apache Tuscany C++.  Unfortunately, it would
take a lot of effort to replace the SDO implementation with one in
user-land code.

It's great to hear you're making progress.  I look forward to hearing
more.

Regards, Graham.

On 9 Jul, 21:53, Yannick <ywarn...@...> wrote:
> Just to keep you informed, about our progress, Kariboe has started
> testing it out (I still haven't) but is concerned about the fact that
> we have to install SCA/SDO as a server "plugin", which isn't super-
> suitable for an open-source web project (it means we add a requirement
> for potential users, which takes out the complete range of free-
> hosting users).
> I am personally not really concerned about this point as I'm expecting
> our implementation to offer a conditional use of the web services we
> would provide (either you have SCA/SDO and it works, or you don't and
> it doesn't). Most of our user base will only want to use web services
> if they have their portal hosted with some kind of caring hosting
> provider.
>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Yannick | 27 Jul 2008 01:24
Picon

Error with documentation example


Hi there,

I'm currently taking my first steps with SCA-SDO following the example
given here:

http://www.osoa.org/display/PHP/SCA+Documentation#SCADocumentation-2.5

I am using an Ubuntu 8.04 system ad I downloaded SCA_SDO using the
PECL command line interface.
Now I'm sure I'm going to find the problem soon, but as the
documentation, as it is, is leading me to a problem and obviously I
can't create and account to edit that page, I wanted to mention it.

When I try getting the WSDL for that page, I get a (double) error
message:

[Sat Jul 26 11:58:27 2008] [error] [client 127.0.0.1] PHP Warning:
SCA_Binding_Factory::require(SCA/Bindings/ws/RequestTester.php) [<a
href='function.SCA-Binding-Factory-require'>function.SCA-Binding-
Factory-require</a>]: failed to open stream: No such file or directory
in /usr/share/php/SCA/SCA_BindingFactory.php on line 68
[Sat Jul 26 11:58:27 2008] [error] [client 127.0.0.1] PHP Fatal
error:  SCA_Binding_Factory::require() [<a
href='function.require'>function.require</a>]: Failed opening required
'SCA/Bindings/ws/RequestTester.php' (include_path='.:/usr/share/php:/
usr/share/pear') in /usr/share/php/SCA/SCA_BindingFactory.php on line
68

Looking into my /usr/share/php/SCA/ directory, I have:
(Continue reading)

Permalink | Reply | 2 comments |
headers
Yannick | 28 Jul 2008 00:39
Picon

Re: Error with documentation example


Like I said, finding the problem was not difficult nor long, but it's
still confusing that there is no explanation of what "ws" could be
replaced by in  <at> binding.ws. Of course, replacing it by  <at> binding.soap
worked immediately.
However, I tried to change it to  <at> binding.restrpc and that,
apparently, brings me back to the initial state (blank page); but this
time I get no error report.
Changing it back to  <at> binding.soap doesn't work.

Yannick

On 26 juil, 18:24, Yannick <ywarn...@...> wrote:
> Hi there,
>
> I'm currently taking my first steps with SCA-SDO following the example
> given here:
>
> http://www.osoa.org/display/PHP/SCA+Documentation#SCADocumentation-2.5
>
> I am using an Ubuntu 8.04 system ad I downloaded SCA_SDO using the
> PECL command line interface.
> Now I'm sure I'm going to find the problem soon, but as the
> documentation, as it is, is leading me to a problem and obviously I
> can't create and account to edit that page, I wanted to mention it.
>
> When I try getting the WSDL for that page, I get a (double) error
> message:
>
> [Sat Jul 26 11:58:27 2008] [error] [client 127.0.0.1] PHP Warning:
(Continue reading)

Permalink | Reply | 1 comment |
headers
Yannick | 28 Jul 2008 01:00
Picon

Re: Error with documentation example


Sorry,  <at> binding.soap definitely works. I've been trying all the other
types (atom, jsonrpc, message, restrpc, tuscany, ebaysoap, local,
restresource, xmlrpc) but none of these generate a wsdl, even though
they don't generate any error message either.
Is that due to something proper to each of these other web services
types?

Yannick

On 27 juil, 17:39, Yannick <ywarn...@...> wrote:
> Like I said, finding the problem was not difficult nor long, but it's
> still confusing that there is no explanation of what "ws" could be
> replaced by in  <at> binding.ws. Of course, replacing it by  <at> binding.soap
> worked immediately.
> However, I tried to change it to  <at> binding.restrpc and that,
> apparently, brings me back to the initial state (blank page); but this
> time I get no error report.
> Changing it back to  <at> binding.soap doesn't work.
>
> Yannick
>
> On 26 juil, 18:24, Yannick <ywarn...@...> wrote:
>
> > Hi there,
>
> > I'm currently taking my first steps with SCA-SDO following the example
> > given here:
>
> >http://www.osoa.org/display/PHP/SCA+Documentation#SCADocumentation-2.5
(Continue reading)

Permalink | Reply | 0 comments |
headers
Yannick | 28 Jul 2008 02:52
Picon

Possible to offer a service from a simple function?


Hi there,

As I am trying out SCA, a bunch of questions come to mind. I'll try to
stick to one-question-per-mail for clarity and indexing of the
answers.

Following the documentation here http://www.osoa.org/display/PHP/SCA+Documentation#SCADocumentation-2:
"...PHP annotations are used to define PHP classes as SCA
components,...".
As far as I can see, there's no way to use a simple functions library
and provide web services from it, is there?

If not, considering a functions library should also use a file-level
header for PHPDocumentor, is there a particular reason why it is not
possible to use simple functions?

Thanks,

Yannick
Permalink | Reply | 1 comment |
headers
Yannick | 28 Jul 2008 03:52
Picon

PHPDoc parsing too restrictive?


Hi again,

Apparently, the parsing of the PHPDoc comments is so severe that if I
use:

/**
 * This library provides functions for user management.
 * it in your code to use its functionality.
 *
 *  <at> service
 *  <at> binding.soap
*
*/

it won't work, but if I add one space before the star on the line
before the last, then it works:

/**
 * This library provides functions for user management.
 * it in your code to use its functionality.
 *
 *  <at> service
 *  <at> binding.soap
 *
*/

However, the last line (the closing tag) works, with or without space.
I haven't found any documentation about this, but it sure takes some
time to figure out! (and error reporting is un-existing about that
(Continue reading)

Permalink | Reply | 3 comments |
headers
Yannick | 28 Jul 2008 02:55
Picon

Impact of SCA on performance?


Hi again,

If I decide to use SCA to provide services from my existing classes,
should I be worried about performances in terms of parsing? Will any
single include of this class file trigger a parsing of my PHPDoc
documentation, or is it going to detect, somehow, that the class has
been called through a local call rather than a web service, and
consequently ignore the parsing?

Thanks,

Yannick
Permalink | Reply | 1 comment |
headers
Graham Charters | 29 Jul 2008 09:21

Re: Error with documentation example


Hi Yannick,

Thanks for pointing out the documentation problem on osoa.org.  I'll
try to fix that shortly.

Dalibor is correct that WSDL is only generated for binding.soap.
Other bindings will generate their own kinds of service descriptions
where appropriate.  For example, binding.jsonrpc with generate a
service method description if you add ?smd.

Regards, Graham.

On 28 Jul, 00:01, Dalibor Andzakovic <Dalibor.Andzako...@...>
wrote:
> Correct. WSDL only gets created for SOAP services AFAIK.
>
> dali
>
> -----Original Message-----
> From: phpsoa@... on behalf of Yannick
> Sent: Mon 2008-07-28 11:00
> To: phpsoa
> Subject: [phpsoa] Re: Error with documentation example
>
> Sorry,  <at> binding.soap definitely works. I've been trying all the other
> types (atom, jsonrpc, message, restrpc, tuscany, ebaysoap, local,
> restresource, xmlrpc) but none of these generate a wsdl, even though
> they don't generate any error message either.
> Is that due to something proper to each of these other web services
(Continue reading)

Permalink | Reply | 1 comment |

Gmane