On 7 Mar, 10:15, "Matthew Peters" <[EMAIL PROTECTED]>
wrote:
> I imagine that since SCA for PHP is already keen on annotations, we
> would want the developer to have exactly the same: in the component
> they just put @Authentication or @Confidential or @Integrity, and we
> do the rest. Of course w
Picking up on the question of what the developer should see: a little
bit of this is already visible in the SCA Java Annotations spec.
As you probably know, there is a generalised Policy spec for SCA, that
describes how policies should be referred to in the XML definitions.
It is intended to be a
On 6 Mar, 19:57, "Rob" <[EMAIL PROTECTED]> wrote:
> On 6 Mar, 14:03, [EMAIL PROTECTED] wrote:
>
> > On 6 Mar, 16:40, "jon" <[EMAIL PROTECTED]> wrote:
> > > Any thoughts on these issues at large? Does anybody have any resources
> > > they know of that address WS-* PHP implementation? I am interes
On 6 Mar, 14:03, [EMAIL PROTECTED] wrote:
> On 6 Mar, 16:40, "jon" <[EMAIL PROTECTED]> wrote:
> > Any thoughts on these issues at large? Does anybody have any resources
> > they know of that address WS-* PHP implementation? I am interested in
> > starting a discussion about these issues, and of co
On 6 Mar, 16:40, "jon" <[EMAIL PROTECTED]> wrote:
> Hello All,
>
> I am curious to know if the PHP SOA project team has plans to
> implement the WS-* extensions/standards that large vendors are
> implementing to help manage service/messaging security, QoS,
> transactions, coordination, etc. Or,
