You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@synapse.apache.org by "Asankha C. Perera" <as...@wso2.com> on 2007/07/02 14:51:35 UTC
Features for 1.1 release
Hi all
I am trying to list and prioritize the set of features that we would
like to introduce into Synapse 1.1, and any defects that should be
fixed. Some of the main areas under consideration are:
1. Improvement of Transports
HTTP/S
- Ability to expose a proxy over a custom port
- Ability to use a custom SSL configuration when exposing over a
custom port
- Ability to use a custom SSL configuration for an endpoint (i.e.
certificate used for two-way authentication)
File/FTP
- Ability to use file/ftp/sftp/.. transport through Apache commons
CFS (http://jakarta.apache.org/commons/vfs)
Corba / EJB / JDBC
- Ability call into these external systems
2. Mediators
XQuery / Saxon XSLT
Cobol Copybook to XML
CSV to XML
Reporting - (for auditing etc.)
Looping mediator - to process a message as multiple smaller (one
way) messages
Mediator to call into JDBC
3. BPEL
Calling into Apache ODE to support BPEL
If you would like to suggest or add any other items to list please let
me know. I will add this into the Wiki/JIRA and prepare how we want to
achieve these, based on actual usage by users and the priorities.
thanks
asankha
---------------------------------------------------------------------
To unsubscribe, e-mail: synapse-user-unsubscribe@ws.apache.org
For additional commands, e-mail: synapse-user-help@ws.apache.org
Re: Features for 1.1 release
Posted by legolas <le...@gmail.com>.
If it is possible, I want to ask whether you have estimation about when
version 1.0.1 could be production ready, I just want to know an estimation
to arrange my planes with it.
asankha wrote:
>
> Hi Legolas
>> Apache Synapse is a good project and I am planing to use synapse for a
>> project and I want to vote for minor release model that was suggested, I
>> mean it would be good to have 1.0.1, 1.0.2, and so on.
>>
> Cool.. I agree and I think we will be heading in that path soon with a
> 1.0.1 with some minor fixes and performance improvements etc.
>> A feature that I want to vote for is mutual authentication using digital
>> certifications (SSL mutual authentication).
>> Let me explain what do i mean by ssl mutual authentication:
>> with my reading and researches it means that we have a certDB in server
>> side (Synapse side) and it contain one or more CA's certifications and in
>> client side we have a certification signed by one of those CA's . now
>> when a
>> client want to connect to Synapse Synapse can check to see whether the
>> client has a certification signed by one of those CA's which are present
>> in
>> its certDB or not. if it is singed by one of them then Synapse will
>> answer
>> otherwise it will not.
>>
> We already do have this support in the 1.0 release, but this is disabled
> by default. If you setup your certificate stores (defaults are trust.jks
> and identity.jks) properly and uncomment the "<parameter
> name="SSLVerifyClient">require</parameter>" from the axis2.xml's https
> transport listener configuration, it will do exactly what you have
> explained.
>> Also there should be some mechanism not to allow all clients with such
>> certification to connect to the server (I do not know how we should do
>> this).
>>
> I agree.. let me check with the HttpCore project how this may be
> possible.. thanks for suggesting this
>> Also In client side we should have some mechanism to check and see
>> whether
>> we are connecting to a server which has correct certification or not (I
>> think we can do this by assigning a certification to synapse and adding
>> the
>> issuer CA which issued synapse certification to client JKS file), is it
>> correct?
>>
> Right now we support hostname verification. Again this is commented by
> default on the axis2.xml's https transport sender configuration.
> "<parameter name="HostnameVerifier">DefaultAndLocalhost</parameter>" If
> you specify strict, the host name verification would be performed.
>
> asankha
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: synapse-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: synapse-user-help@ws.apache.org
>
>
>
--
View this message in context: http://www.nabble.com/Features-for-1.1-release-tf4012032.html#a11500912
Sent from the Synapse - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: synapse-user-unsubscribe@ws.apache.org
For additional commands, e-mail: synapse-user-help@ws.apache.org
Re: Features for 1.1 release
Posted by "Asankha C. Perera" <as...@wso2.com>.
Hi Legolas
> Apache Synapse is a good project and I am planing to use synapse for a
> project and I want to vote for minor release model that was suggested, I
> mean it would be good to have 1.0.1, 1.0.2, and so on.
>
Cool.. I agree and I think we will be heading in that path soon with a
1.0.1 with some minor fixes and performance improvements etc.
> A feature that I want to vote for is mutual authentication using digital
> certifications (SSL mutual authentication).
> Let me explain what do i mean by ssl mutual authentication:
> with my reading and researches it means that we have a certDB in server
> side (Synapse side) and it contain one or more CA's certifications and in
> client side we have a certification signed by one of those CA's . now when a
> client want to connect to Synapse Synapse can check to see whether the
> client has a certification signed by one of those CA's which are present in
> its certDB or not. if it is singed by one of them then Synapse will answer
> otherwise it will not.
>
We already do have this support in the 1.0 release, but this is disabled
by default. If you setup your certificate stores (defaults are trust.jks
and identity.jks) properly and uncomment the "<parameter
name="SSLVerifyClient">require</parameter>" from the axis2.xml's https
transport listener configuration, it will do exactly what you have
explained.
> Also there should be some mechanism not to allow all clients with such
> certification to connect to the server (I do not know how we should do
> this).
>
I agree.. let me check with the HttpCore project how this may be
possible.. thanks for suggesting this
> Also In client side we should have some mechanism to check and see whether
> we are connecting to a server which has correct certification or not (I
> think we can do this by assigning a certification to synapse and adding the
> issuer CA which issued synapse certification to client JKS file), is it
> correct?
>
Right now we support hostname verification. Again this is commented by
default on the axis2.xml's https transport sender configuration.
"<parameter name="HostnameVerifier">DefaultAndLocalhost</parameter>" If
you specify strict, the host name verification would be performed.
asankha
---------------------------------------------------------------------
To unsubscribe, e-mail: synapse-user-unsubscribe@ws.apache.org
For additional commands, e-mail: synapse-user-help@ws.apache.org
Re: Features for 1.1 release
Posted by legolas <le...@gmail.com>.
Thank you guys for providing apache synapse which imho is a very good project
when we deal with web services.
Apache Synapse is a good project and I am planing to use synapse for a
project and I want to vote for minor release model that was suggested, I
mean it would be good to have 1.0.1, 1.0.2, and so on.
A feature that I want to vote for is mutual authentication using digital
certifications (SSL mutual authentication).
Let me explain what do i mean by ssl mutual authentication:
with my reading and researches it means that we have a certDB in server
side (Synapse side) and it contain one or more CA's certifications and in
client side we have a certification signed by one of those CA's . now when a
client want to connect to Synapse Synapse can check to see whether the
client has a certification signed by one of those CA's which are present in
its certDB or not. if it is singed by one of them then Synapse will answer
otherwise it will not.
Also there should be some mechanism not to allow all clients with such
certification to connect to the server (I do not know how we should do
this).
Also In client side we should have some mechanism to check and see whether
we are connecting to a server which has correct certification or not (I
think we can do this by assigning a certification to synapse and adding the
issuer CA which issued synapse certification to client JKS file), is it
correct?
sorry if my explanation is not correct, and if it is not correct please let
me know and i will be thankful.
pzfreo wrote:
>
> Asankha
>
> I'd like to do a staged development. It seems like some things we
> might be able to do quickly and others may be more work. On the basis
> of release often release early maybe we should do a 1.0.1, 1.0.2,
> 1.0.3, etc.
>
> In the meantime, if I had to say the thing I'd like most, I'd suggest
> the file/ftp, the CSV handling, and the custom SSL configs, based on
> what I've heard people ask for.
>
> In the meantime, maybe we should talk to the ODE team about whether we
> can collaborate on integrating ODE.
>
> Paul
>
> On 7/2/07, Asankha C. Perera <as...@wso2.com> wrote:
>> Hi all
>>
>> I am trying to list and prioritize the set of features that we would
>> like to introduce into Synapse 1.1, and any defects that should be
>> fixed. Some of the main areas under consideration are:
>>
>> 1. Improvement of Transports
>>
>> HTTP/S
>> - Ability to expose a proxy over a custom port
>> - Ability to use a custom SSL configuration when exposing over a
>> custom port
>> - Ability to use a custom SSL configuration for an endpoint (i.e.
>> certificate used for two-way authentication)
>>
>> File/FTP
>> - Ability to use file/ftp/sftp/.. transport through Apache commons
>> CFS (http://jakarta.apache.org/commons/vfs)
>>
>> Corba / EJB / JDBC
>> - Ability call into these external systems
>>
>>
>> 2. Mediators
>>
>> XQuery / Saxon XSLT
>> Cobol Copybook to XML
>> CSV to XML
>> Reporting - (for auditing etc.)
>> Looping mediator - to process a message as multiple smaller (one
>> way) messages
>> Mediator to call into JDBC
>>
>> 3. BPEL
>>
>> Calling into Apache ODE to support BPEL
>>
>> If you would like to suggest or add any other items to list please let
>> me know. I will add this into the Wiki/JIRA and prepare how we want to
>> achieve these, based on actual usage by users and the priorities.
>>
>> thanks
>> asankha
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: synapse-user-unsubscribe@ws.apache.org
>> For additional commands, e-mail: synapse-user-help@ws.apache.org
>>
>>
>
>
> --
> Paul Fremantle
> Co-Founder and VP of Technical Sales, WSO2
> OASIS WS-RX TC Co-chair
>
> blog: http://pzf.fremantle.org
> paul@wso2.com
>
> "Oxygenating the Web Service Platform", www.wso2.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: synapse-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: synapse-user-help@ws.apache.org
>
>
>
--
View this message in context: http://www.nabble.com/Features-for-1.1-release-tf4012032.html#a11489534
Sent from the Synapse - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: synapse-user-unsubscribe@ws.apache.org
For additional commands, e-mail: synapse-user-help@ws.apache.org
Fwd: Features for 1.1 release
Posted by Paul Fremantle <pz...@gmail.com>.
Sorry forgot to copy synapse-dev!
Paul
---------- Forwarded message ----------
From: Paul Fremantle <pz...@gmail.com>
Date: Jul 3, 2007 8:28 AM
Subject: Re: Features for 1.1 release
To: synapse-user@ws.apache.org
Asankha
I'd like to do a staged development. It seems like some things we
might be able to do quickly and others may be more work. On the basis
of release often release early maybe we should do a 1.0.1, 1.0.2,
1.0.3, etc.
In the meantime, if I had to say the thing I'd like most, I'd suggest
the file/ftp, the CSV handling, and the custom SSL configs, based on
what I've heard people ask for.
In the meantime, maybe we should talk to the ODE team about whether we
can collaborate on integrating ODE.
Paul
On 7/2/07, Asankha C. Perera <as...@wso2.com> wrote:
> Hi all
>
> I am trying to list and prioritize the set of features that we would
> like to introduce into Synapse 1.1, and any defects that should be
> fixed. Some of the main areas under consideration are:
>
> 1. Improvement of Transports
>
> HTTP/S
> - Ability to expose a proxy over a custom port
> - Ability to use a custom SSL configuration when exposing over a
> custom port
> - Ability to use a custom SSL configuration for an endpoint (i.e.
> certificate used for two-way authentication)
>
> File/FTP
> - Ability to use file/ftp/sftp/.. transport through Apache commons
> CFS (http://jakarta.apache.org/commons/vfs)
>
> Corba / EJB / JDBC
> - Ability call into these external systems
>
>
> 2. Mediators
>
> XQuery / Saxon XSLT
> Cobol Copybook to XML
> CSV to XML
> Reporting - (for auditing etc.)
> Looping mediator - to process a message as multiple smaller (one
> way) messages
> Mediator to call into JDBC
>
> 3. BPEL
>
> Calling into Apache ODE to support BPEL
>
> If you would like to suggest or add any other items to list please let
> me know. I will add this into the Wiki/JIRA and prepare how we want to
> achieve these, based on actual usage by users and the priorities.
>
> thanks
> asankha
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: synapse-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: synapse-user-help@ws.apache.org
>
>
--
Paul Fremantle
Co-Founder and VP of Technical Sales, WSO2
OASIS WS-RX TC Co-chair
blog: http://pzf.fremantle.org
paul@wso2.com
"Oxygenating the Web Service Platform", www.wso2.com
--
Paul Fremantle
Co-Founder and VP of Technical Sales, WSO2
OASIS WS-RX TC Co-chair
blog: http://pzf.fremantle.org
paul@wso2.com
"Oxygenating the Web Service Platform", www.wso2.com
---------------------------------------------------------------------
To unsubscribe, e-mail: synapse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: synapse-dev-help@ws.apache.org
Re: Features for 1.1 release
Posted by Paul Fremantle <pz...@gmail.com>.
Asankha
I'd like to do a staged development. It seems like some things we
might be able to do quickly and others may be more work. On the basis
of release often release early maybe we should do a 1.0.1, 1.0.2,
1.0.3, etc.
In the meantime, if I had to say the thing I'd like most, I'd suggest
the file/ftp, the CSV handling, and the custom SSL configs, based on
what I've heard people ask for.
In the meantime, maybe we should talk to the ODE team about whether we
can collaborate on integrating ODE.
Paul
On 7/2/07, Asankha C. Perera <as...@wso2.com> wrote:
> Hi all
>
> I am trying to list and prioritize the set of features that we would
> like to introduce into Synapse 1.1, and any defects that should be
> fixed. Some of the main areas under consideration are:
>
> 1. Improvement of Transports
>
> HTTP/S
> - Ability to expose a proxy over a custom port
> - Ability to use a custom SSL configuration when exposing over a
> custom port
> - Ability to use a custom SSL configuration for an endpoint (i.e.
> certificate used for two-way authentication)
>
> File/FTP
> - Ability to use file/ftp/sftp/.. transport through Apache commons
> CFS (http://jakarta.apache.org/commons/vfs)
>
> Corba / EJB / JDBC
> - Ability call into these external systems
>
>
> 2. Mediators
>
> XQuery / Saxon XSLT
> Cobol Copybook to XML
> CSV to XML
> Reporting - (for auditing etc.)
> Looping mediator - to process a message as multiple smaller (one
> way) messages
> Mediator to call into JDBC
>
> 3. BPEL
>
> Calling into Apache ODE to support BPEL
>
> If you would like to suggest or add any other items to list please let
> me know. I will add this into the Wiki/JIRA and prepare how we want to
> achieve these, based on actual usage by users and the priorities.
>
> thanks
> asankha
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: synapse-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: synapse-user-help@ws.apache.org
>
>
--
Paul Fremantle
Co-Founder and VP of Technical Sales, WSO2
OASIS WS-RX TC Co-chair
blog: http://pzf.fremantle.org
paul@wso2.com
"Oxygenating the Web Service Platform", www.wso2.com
---------------------------------------------------------------------
To unsubscribe, e-mail: synapse-user-unsubscribe@ws.apache.org
For additional commands, e-mail: synapse-user-help@ws.apache.org