Ok. Please don't remove the WS API docs, but mark them as not supported for
production.

At some point we need to fix the transaction stuff in the WS API, or create
a robust REST or Thrift transport (my preferred option). The reason is that
we should be doing all the Registry stuff in the Registry Server not in the
ESB. We had this discussion before, but we didn't have Thrift at the time.

Paul

On 20 September 2012 03:32, Samisa Abeysinghe <[email protected]> wrote:

>
>
> On Thu, Sep 20, 2012 at 7:56 AM, Paul Fremantle <[email protected]> wrote:
>
>> WS API is not supported?!
>
>
> We checked with Senaka, and he agreed that transactional aspects cannot
> be achieved with WS API for mounting - it runs into problems.
> So only production recommendation is JDBC mounting.
>
>
>>
>> I thought it was supported but not our first choice.
>>
>> Paul
>>
>> On 20 September 2012 02:20, Samisa Abeysinghe <[email protected]> wrote:
>>
>>> So remove those form
>>> http://docs.wso2.org/wiki/display/Governance450/Remote+Instance+and+Mount+Configuration+Details
>>>
>>>
>>> Thanks,
>>> Samisa...
>>>
>>> Samisa Abeysinghe
>>> VP Engineering
>>> WSO2 Inc.
>>> http://wso2.com
>>> http://wso2.org
>>>
>>>
>>> _______________________________________________
>>> Dev mailing list
>>> [email protected]
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Paul Fremantle
>> CTO and Co-Founder, WSO2
>> OASIS WS-RX TC Co-chair, VP, Apache Synapse
>>
>> UK: +44 207 096 0336
>> US: +1 646 595 7614
>>
>> blog: http://pzf.fremantle.org
>> twitter.com/pzfreo
>> [email protected]
>>
>> wso2.com Lean Enterprise Middleware
>>
>> Disclaimer: This communication may contain privileged or other
>> confidential information and is intended exclusively for the addressee/s.
>> If you are not the intended recipient/s, or believe that you may have
>> received this communication in error, please reply to the sender indicating
>> that fact and delete the copy you received and in addition, you should not
>> print, copy, retransmit, disseminate, or otherwise use the information
>> contained in this communication. Internet communications cannot be
>> guaranteed to be timely, secure, error or virus-free. The sender does not
>> accept liability for any errors or omissions.
>>
>>  Thanks,
> Samisa...
>
> Samisa Abeysinghe
> VP Engineering
> WSO2 Inc.
> http://wso2.com
> http://wso2.org
>
>
>


-- 
Paul Fremantle
CTO and Co-Founder, WSO2
OASIS WS-RX TC Co-chair, VP, Apache Synapse

UK: +44 207 096 0336
US: +1 646 595 7614

blog: http://pzf.fremantle.org
twitter.com/pzfreo
[email protected]

wso2.com Lean Enterprise Middleware

Disclaimer: This communication may contain privileged or other confidential
information and is intended exclusively for the addressee/s. If you are not
the intended recipient/s, or believe that you may have received this
communication in error, please reply to the sender indicating that fact and
delete the copy you received and in addition, you should not print, copy,
retransmit, disseminate, or otherwise use the information contained in this
communication. Internet communications cannot be guaranteed to be timely,
secure, error or virus-free. The sender does not accept liability for any
errors or omissions.
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to