Hi Marcelo,
Thanks for the suggested update to allow WSDL generation to be
redirected. This looks like a useful enhancement. We'll take a look
and see about incorporating it. It's been quite a while since we did
a release so it would be good to get this rolled in with some other
outstanding it
Hi Bruno,
There is a cost over and above doing local calls for local SCA service
invocations. Firstly, SCA will reflect on the service you are going
to call, in order to understand its types and what methods are
available. Secondly, the invocation will go through a proxy (SCA/
Bindings/local/Pr
Hi Bruno, so far as I can tell, the types are soap types, not the
types on your service portType (interface). We have gone through many
iterations of WSDL generation (sometimes with xsi:type, sometimes
without :-S ) to try to get interop sorted out. What you show many
not actually be wrong. Doe
Hi Flo,
Are you using SCA on the client side? Could you post a small sample
which demonstrates the problem and I'll take a look?
Regards, Graham.
On 3 Oct, 20:58, flo <[EMAIL PROTECTED]> wrote:
> I just ran into a problem with my soap connection. Server is java6 and
> client is php5.
>
> Every
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
2 Jun, 16:53, "Silvano Girardi Jr" <[EMAIL PROTECTED]> wrote:
> Hi Graham,
> I have that interest. Where do I start? :)
>
> Thanks
> Silvano
>
> On Mon, Jun 2, 2008 at 10:19 AM, Graham Charters <[EMAIL PROTECTED]>
> wrote:
>
>
>
> > Hi
Hi Silvano,
Sorry for not replying sooner and not replying to your original note.
I always had in mind to generate documentation in the WSDL from the
methods descriptions, so what you have done is exactly the right idea.
Thanks also for the patch. I haven't taken a look at the moment. The
SCA_
Thank you, Philip.
FWIW, I agree with Caroline's suggestions. If these can't belong to
multiple categories simultaneously then I would go for the ones where
they are strongest/most used and then reference them from the others.
I would also choose the same categories as Caroline.
Regards, Graham
Rather tardy of me, but hopefully better late than never... Thanks for
doing this Matthew!
Regards, Graham.
On 4 Mar, 10:58, Matthew Peters <[EMAIL PROTECTED]>
wrote:
> I have built and released FULMAR as 1.2.4
>
> The contents are:
> # The ability to control the operations on a service interfac
Hi Dali,
I'm not sure this is a caching problem. There is some primitive
caching support, but it's only turned on for the ebaysoap binding.
Could you provide a little test case which reproduces the problem and
I'll see if I can track down what's going on?
Regards, Graham.
On 7 Feb, 23:28, Dal
Hi Muru,
This is something we've wanted to get to, but time constraints have
meant we've not been able to. The idea was we would allow the types
to be defined by PHP objects which would need to be 'documented' with
type information in order for us to derive a static type and
optionally generate
If the caching isn't close then, yes, I agree it's about time we did a
release.
Graham.
On 31 Jan, 18:26, Matthew Peters <[EMAIL PROTECTED]>
wrote:
> We have been hanging on to FULMAR hoping to get a solution to the data
> model caching in it, but this doesn't seem to be going to happen.
> Shall
I am exclusively on 5.3 now. The changes I made should be backwards
compatible, but I haven't tried on older versions.
I haven't tried Zend Studio yet.
Graham.
On 30 Jan, 14:13, Matthew Peters <[EMAIL PROTECTED]>
wrote:
> Have you tried using your 5.3 under Zend Studio? Is the debugger dll
> i
I've just checked a couple of fixes into FULMAR. Seems to work fine
now.
Graham.
On 29 Jan, 10:13, Graham Charters <[EMAIL PROTECTED]> wrote:
> I've just moved up to PHP 5.3 and encountered a few problems (e.g. a
> public const in SCA_CommentReader.php called "NAMES
I've just moved up to PHP 5.3 and encountered a few problems (e.g. a
public const in SCA_CommentReader.php called "NAMESPACE" apparently
clashing with the new namespace support). I'll try to look at this in
the next day or so, but if anyone wants to beat me too it... ;-) .
Graham.
--~--~
ension
> *
> * @service
> * @binding.soap
> */
> class DerivedClass extends ParentClass {
>
> public function method2() {}
>
> }
>
> ?>
>
> Using this files structure it doesn't work.
>
> Thank you.
>
> On 2 Jan, 14:18, Graham Charters <[EM
http://localhost/bugs/extends/
DerivedClass.php"/>
Can you give this example a try and see what happens?
Regards,
Graham.
On 2 Jan, 17:07, Graham Charters <[EMAIL PROTECTED]> wrote:
&
Hi,
Sorry for not getting back to you sooner. Extends is not something
I'm aware of being supported. The SCA_AnnotationReader uses
get_class_methods to return the methods which the class may expose
(depends on whether they're public or are restricted using an
interface). I haven't tried it yet
ay('soap'=>array('options'=>array('local_cert'=>...,
> 'passphrase'=>...)));
> for the soap binding, set the soap constructor options with the
> following name/value pairs..
>
> Now going forward after something like the above is imp
he service definition which would use this might look like
/**
* @service
* @binding.soap
* @requires confidentiality
*
*/
Is this the sort of thing you were thinking of, or have I completely
lost the plot? :-D
Graham.
On 11 Dec, 10:14, Rob <[EMAIL PROTECTED]> wrote:
> Hi Graham,
&g
Disclaimer: I've never done this...
Looking at the docs for the Soap Extension it seems you need to
specify two entries in the "options" on the soap client constructor.
These could be added as annotations that the binding understands:
/**
* @reference
* @binding.soap
* @local_cert
* @passph
Hi Tom,
Yes, this is the right place to discuss additions to the Bindings.
Looking forward to your thoughts...
Regards, Graham.
On 21 Nov, 16:41, Tom <[EMAIL PROTECTED]> wrote:
> > For the bugs, these should be raised on the bugs system, and if you have
> > proposed patches you should make them
Hi M,
Passing by-value is what the SCA specifications (see
http://osoa.org/display/Main/Service+Component+Architecture+Specifications)
say should be the calling semantics for remote services. SCA in PHP
treats all services as remote and assumes local by-reference calls
will just be done using th
Hi Silvano,
Welcome to the list.
I'm not aware of anyone doing authentication using SCA.
Unfortuantely, Kieran went silent on the subject, so the work never
progressed.
There are a couple of things we've done since that discussion which
would make implementing @authentication easier:
1. We've
n 11 Sep, 16:29, Graham Charters <[EMAIL PROTECTED]> wrote:
> > You could go the other way though, and exploit this behaviour to force
> > SCA to be deferred.
>
> Interesting idea, so I thought I'd try it. I had my SCA class
> implement an empty interface, and sadly, it ma
ere suggesting, or have I missed the point?
Graham.
On 11 Sep, 11:28, Caroline Maynard <[EMAIL PROTECTED]> wrote:
> Graham Charters wrote:
> > I've just created the test case and reproduced the behaviour (I won't
> > say "problem" because I think perhaps wha
#x27;;
interface MyServiceInterface {}
class MyService implements MyServiceInterface {}
// this must be the last include
include 'SCA/SCA.php';
I need to turn my tests into phpunit tests and merge with the latest
in pecl. I'm hoping I'll be able to do that tonight.
Graha
e SCA. If anyone has heard of anything which might be relevant,
please let me know.
Graham.
On 3 Sep, 13:18, Graham Charters <[EMAIL PROTECTED]> wrote:
> It sounds like we may have consensus. To summarise:
>
> 1. We should add the ability to specify an optional interface for the
ass. It probably wouldn't make any sense to have SCA parse
> annotations in the interface.
>
> Matt
>
> On 31 Aug, 06:20, Graham Charters <[EMAIL PROTECTED]> wrote:> Comments
> inlined below...
>
> > On 31 Aug, 11:35, [EMAIL PROTECTED] wrote:
>
> >
Comments inlined below...
On 31 Aug, 11:35, [EMAIL PROTECTED] wrote:
> Hi Graham
>
> Some more comments in line...
>
> On 31 Aug, 11:26, Graham Charters <[EMAIL PROTECTED]> wrote:
>
>
>
> > Hi Simon, thanks for the rapid comments. Here's my thou
y go away in the near future.
Does this make sense and seem sensible?
On 31 Aug, 09:30, [EMAIL PROTECTED] wrote:
> On 31 Aug, 08:42, Graham Charters <[EMAIL PROTECTED]> wrote:
>
> > Pecl Request #11944 (http://pecl.php.net/bugs/bug.php?id=11944) is
> > asking for finer-grai
Pecl Request #11944 (http://pecl.php.net/bugs/bug.php?id=11944) is
asking for finer-grained control over the methods which are surfaced
on a service interface. We currently just use class visibility (i.e.
all public methods) to control this.
There's a small amount of discussion in the request, b
. I think the PHP
class approach might need a new annotation to say they want classes
(POPO - Plain Old PHP Objects) rather than SDO.
On 30 Aug, 09:29, Graham Charters <[EMAIL PROTECTED]> wrote:
> The many-valued nature of a lot of the properties is unfortunately due
> to the inab
Thanks, Caroline, this does look useful. It also puts me to shame,
since it appears I haven't committed anything for quite some time :-S
On 24 Aug, 23:02, Caroline Maynard <[EMAIL PROTECTED]> wrote:
> I uploaded a form
> (http://groups.google.co.uk/group/phpsoa/web/commits.html) that you can
> u
The many-valued nature of a lot of the properties is unfortunately due
to the inability of XML schema to accurately describe the Atom
Syndication Format. It's a while since I wrote the schema, but I seem
to recall it was to do with the use of . The Atom XML is defined in terms of Relax NG which
We've recently had a number of XML related defect raised against SDO
(11923, 11925, 11926, 11927, 11930 and 11931). These seem to all boil
down to strictly enforcing the XML schema. See the brief discussion
in 11925 for more details.
This phpsoa group discussion (http://groups.google.co.uk/grou
Hi Caroline,
Thanks for your feedback on your experiences with the Atom binding.
Doesn't make good reading, but it's very helpful. I'm not able to
work on this for the next couple of weeks, but hope to get time to
work on SCA the week after. Atom was going to be one of the things I
wanted to lo
Hi, I've inlined some thoughts below. Others may know more and have
different views. Please follow-up if you have any more questions.
On 6 Aug, 02:55, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
> I've been reading a bit about SDO recently and using it with PHP and
> have just started trying
+1 from me too :-) . I'd like to progress this, and pecl seems like
the best place to do that.
On 17 Jul, 11:23, [EMAIL PROTECTED] wrote:
> On 17 Jul, 10:08, Matthew Peters <[EMAIL PROTECTED]>
> wrote:
>
> > Shame I didn't read it through carefully before posting - that should
> > be
> > "that h
Added simpledb as a nice to have for EIDER.
Click on
http://groups.google.co.uk/group/phpsoa/web/contents-of-release-from-eider-branch;
or copy & paste it into your browser's address bar if that does not
work.
--~--~-~--~~~---~--~~
You received this message beca
Hi Caroline,
Sorry for my silence (other project activities have taken over my life
at the moment). I would like to see this. As someone who commits
less that others and whose brain seems to flush information all to
readily, having the documented processes to refer to would be very
helpful.
Re
I don't have any thoughts on solutions at this time, but I do have a
comment on the "by design". You are right that it is not by design
that interfaces are excluded. Determining the service 'interface'
from a class's public methods is a convenience. We do want to support
explicit use of an inte
The other place would be developerWorks' phpblog, which is syndicated
onto planet-php.
On 2 Jul, 15:31, [EMAIL PROTECTED] wrote:
> I've just been doing a Tuscany blog post about the 1.2.2. release. I
> notice that the release announce didn't go out on the PECL dev list.
> There appears to be a pr
e?
Graham.
On 22 Jun, 09:42, [EMAIL PROTECTED] wrote:
> On 22 Jun, 09:14, Graham Charters <[EMAIL PROTECTED]> wrote:
>
>
>
> > Hi Simon, can you post what you're seeing for one of the failing unit
> > test for comparison?
>
> > Graham.
>
> > On 2
Hi Simon, can you post what you're seeing for one of the failing unit
test for comparison?
Graham.
On 22 Jun, 09:08, [EMAIL PROTECTED] wrote:
> On 22 Jun, 08:39, [EMAIL PROTECTED] wrote:
>
>
>
> > On 21 Jun, 22:40, Graham Charters <[EMAIL PROTECTED]> wrote:
>
Hi Matthew,
Thanks for fixing the wsdl schema fetching problem and spinning RC2.
It all looks good to me on Windows. Unit tests all pass (phpt and
phpunit). Service generation for wsdl, xmlrpc and jsonrpc all work.
Json-rpc mail example runs. Ebay soap example runs and caching works.
Regards,
I've just done 'pear run-tests' instead of 'php run-tests.php ...' and
004 passes, so I think the failure is due to running the phpt tests in
an inappropriate way.
Graham.
On 19 Jun, 15:16, Matthew Peters <[EMAIL PROTECTED]>
wrote:
> Simon, the index.php did contain a reference to helloworldscaj
Hi Simon,
Yes, I see the same problem. When run with run-tests I get the
following error (I've not had chance to investigate further):
ACTUAL OUTPUT
Warning: SDO_DAS_XML::create(): php_network_getaddresses: getaddrinfo
failed: No such host is known. in C:\php\PEAR\SCA\Bindings\soap
\Servi
hange since original post. Instead of use_lower_case in the
ini file, you can state case = "xxx" , where xxx is one of "upper",
"lower" or "mixed". Mixed just makes the first letter of each
property a capital and the rest lowercase.
Graham.
On 5 Jun, 16:5
I referred to two approaches because I felt that the two 'interfaces'
might not be progressive (i.e. steps down the same road). I suppose
in some abstract way I could be wrong in that the path info in the
URIs is an 'identity' in both cases (e.g. http:///Collection.php/12
versus http:///C
en spot patterns for other REST styles which
can then be encapsulated in new bindings or helper functions.
Graham.
On 7 Jun, 17:42, Graham Charters <[EMAIL PROTECTED]> wrote:
> On 7 Jun, 16:10, Matthew Peters <[EMAIL PROTECTED]>
> wrote:
>
> > I'm glad you like
OK, the 'experimental' tags have been removed from the XML DAS. This
will eventually make its way through to the public docs.
On 7 Jun, 16:08, Graham Charters <[EMAIL PROTECTED]> wrote:
> On 7 Jun, 10:29, Caroline Maynard <[EMAIL PROTECTED]> wrote:
>
> > Simon
On 7 Jun, 16:10, Matthew Peters <[EMAIL PROTECTED]>
wrote:
> I'm glad you like the idea, and you ask a good question. It has always
> seemed to me that right at the bottom we have service-oriented
> components and resource-oriented components, and that the service
> oriented ones can all be tota
On 7 Jun, 10:29, Caroline Maynard <[EMAIL PROTECTED]> wrote:
> Simon Laws wrote:
> > I agree with you assessment, i.e. that the XMLDAS is stable but that the
> > relational DAS is still not well used enough to decide that it has
> > settled down.
>
> What he said. (I should have removed it from t
The XML and Relational DAS docs have 'experimental' banners. I'd be
inclined to remove this from the XML DAS (I think it's stable), but am
not sure about the Relational DAS. Any thoughts?
--~--~-~--~~~---~--~~
You received this message because you are subscribed
On 5 Jun, 13:39, Caroline Maynard <[EMAIL PROTECTED]> wrote:
> Graham Charters wrote:
>
> > There have been a few occasions where I've wanted a quick and easy way
> > to access a single database table as part of an SCA component
> > implementation. I'
at this
was the SDO_DataObject. Why would this not be on the SDO_DAS_XML?
On 5 Jun, 13:20, Caroline Maynard <[EMAIL PROTECTED]> wrote:
> Graham Charters wrote:
> > I mentioned the proxies as one of the two areas where we need to keep
> > the interface clean (the other was SDO).
Hi All,
There have been a few occasions where I've wanted a quick and easy way
to access a single database table as part of an SCA component
implementation. I'm just adding the finishing touches (at least to
the point where it might do something useful) to a binding called
simpledb. This gives
On 5 Jun, 10:36, Caroline Maynard <[EMAIL PROTECTED]> wrote:
> Graham Charters wrote:
> > One *real* comment: I think we should be getting into the habit of
> > using "magic method"-style things which appear on the SDO interface
> > (and also our proxy inte
Hi Matthew,
I've just taken the latest code and it goes like something off a
shovel :-) (IMO). The response time for a GetSearchResults is in the
region of 3 seconds, which is a > 50% improvement over what I was
seeing without the caching.
Thanks!
Graham.
On 4 Jun, 11:22, Graham
On 23 May, 16:34, Matthew Peters <[EMAIL PROTECTED]>
wrote:
>
> So, any volunteers to chop it out? We could stop generating the "This
> wsdl was generated..." comment at the bottom of the wsdl since it was
> only used for that.
>
Isn't this used to identify and unwrap the interface of the doc/
In the dependencies section for 1.2.1 we list "PEAR Package: sdo",
which links to something at http://pear.php.net/package/sdo - which
clearly doesn't exist.
Do we need to do a new release to remove this, or can it be removed
independently (I'm ignorant of this process :-( ) ?
Graham.
--~--~--
Hi Matthew, this looks good to me. I'll give your changes a go and
let you know how I get on.
The proposed caching approach looks nice and simple. I guess care
must be taken to make sure keys don't collide (perhaps some
recommended best practices on creating good keys would help).
One *real*
Hi Simon, thanks for your thoughts. My comment are below.
On 23 May, 14:12, [EMAIL PROTECTED] wrote:
> Graham
>
> I was just thinking about this part of your issue...
>
> snip> I wrote an XML schema to match the schema used by the relational DAS
> > (i.e. using the urn:app_namespace, and all pri
Hi All,
I've just put some documentation up on the osoa.org wiki describing
how to use the eBay SOAP binding (see
http://osoa.org/display/PHP/eBay+SOAP+Binding+Documentation).
If you spot any problems or have suggestions for improvements, please
post them as comments to this post.
This is a con
Hi Simon, thanks for your 2c - it's always worth more than that :-)
I've inlined some questions/responses below.
On 18 May, 12:29, [EMAIL PROTECTED] wrote:
> Graham
>
> I like both of these suggestions and think they both have a place in
> the runtime.
>
> We should have a separation between Bus
I think Mike is right that we shouldn't always flow this information.
It is a potential security hole as it could divulge more information
than we would like. I had similar concerns about the information we
flow back in http responses for things like Atompub and the conclusion
was to not give any
th better examples showing that "param type1|type2" usage, and
> will
> > > also add more detail to the return tag's doc.
>
> > > Thanks for the posting...
> > > Chuck
>
> > > Now that we know that this is supported behavior, any thoughts
I've added bullets for eBay caching to improve performance and to add
the eBay binding to the release (we shouldn't put the binding into the
release without the caching). I've also added a note to remove RSS
from the release.
Graham.
On 14 May, 12:03, [EMAIL PROTECTED] wrote:
> I've created thi
I appears the RSS binding unintentionally made its way into the 1.2.1
release. This code is prototype and not intended for production use.
I've updated MakePackage.php in DUNLIN to exclude RSS from future
releases.
If anyone's interest in this RSS prototype drop a note here and I'll
happily answ
Good one, Matthew. Works fine for me on Win XP. Thanks also for
moving the eBay binding to DUNLIN.
Graham.
On 11 May, 22:11, [EMAIL PROTECTED] wrote:
> Nice one Matthew. I tried it on Fedora Core 6 and Windows XP SP2. It
> gets a clean bill of health on linux and all is OK on Windows apart
> f
Hi Mike,
One of the goals of the SCA annotations has been to try to preserve
phpDocumentor generation, so I like your suggestion a lot. I took a
look at the phpDocumentor documentation and could only see mention of
the pipe for multiple function returns, but not for parameters. I
gave it a whir
That makes sense. Lets move it out of head and into a branch.
On 11 May, 15:25, "Simon Laws" <[EMAIL PROTECTED]> wrote:
> On 5/11/07, Graham Charters <[EMAIL PROTECTED]> wrote:
>
>
>
> > Hi Simon, yes I did. I had been assured that this would be ok
No, I'm using HEAD, but 004 fails for me too, and with the same error.
On 11 May, 15:02, "Simon Laws" <[EMAIL PROTECTED]> wrote:
> > Graham
>
> Thanks for the suggestion. I did try turning my firewall of but still got
> the same effect. Does php004 pass for you?
>
> Simon
--~--~-~--~---
+1
I also agree with this. The wsdl generation should exclude all
methods beginning with '__'.
On 11 May, 12:57, [EMAIL PROTECTED] wrote:
> Edit report athttp://pecl.php.net/bugs/bug.php?id=10925&edit=1
>
> ID: 10925
> Updated by: [EMAIL PROTECTED]
> -Summary: Meg
Hi Simon, yes I did. I had been assured that this would be ok because
the 'development in a branch' approach is really only necessary for
native extension code (because pecl4win always pulls this from HEAD).
Let me know if you think the binding should go elsewhere.
On 11 May, 14:48, [EMAIL PROTE
Hi Simon,
I've seen this kind of thing happen due to firewall problems. When
you run the tests from the commandline the firewall might block
php.exe, but when you run samples in the browser it lets apache.exe
through. Might be a red herring.
On 11 May, 13:06, [EMAIL PROTECTED] wrote:
> php004.
I've just checked the ebaysoap binding into HEAD. I've also checked
in a couple of samples into the examples directory. There's a readme
in the examples directory that briefly describes how to get started.
The binding's pretty easy to use, removing the need for the coder to
work with soap heade
On Windows where folders can contain spaces, these make their way into
the URLs in service descriptions, such as the WSDL location. This has
been fixed in CURLEW under pecl defect #11006, and is a candidate for
inclusion in 1.2.1.
Click on http://groups.google.com/group/phpsoa/web/contest-of-1-2
Hi Tony,
This is something which has been on the SDO wish list for a long
time. It's on the SDO list because that's where the majority of the
work needs to be done. I had a go at prototyping this last night
thinking a small scenario might work, but hit a few snag. The issues
I encountered were
FYI: It looks like the profile editing feature is now fixed.
On 27 Apr, 14:43, [EMAIL PROTECTED] wrote:
> On 27 Apr, 14:24, cem <[EMAIL PROTECTED]> wrote:
>
> > .. in deference to the grammar police.
>
> It's seems that Google have made a few changes recently (I've seen
> changes to the interface
81 matches
Mail list logo
