Jenkins build is back to normal : Synapse - Trunk #3347

See https://hudson.apache.org/hudson/job/Synapse%20-%20Trunk/3347/ - To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org

[jira] Commented: (SYNAPSE-735) imporve password manager XML syntax which is defined in configuration files - secure vault

[ https://issues.apache.org/jira/browse/SYNAPSE-735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13003943#comment-13003943 ] asela pathberiya commented on SYNAPSE-735: -- Hi Indika, Thanks for your

[jira] Issue Comment Edited: (SYNAPSE-735) imporve password manager XML syntax which is defined in configuration files - secure vault

[ https://issues.apache.org/jira/browse/SYNAPSE-735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13003943#comment-13003943 ] asela pathberiya edited comment on SYNAPSE-735 at 3/8/11 1:59 PM:

[jira] Commented: (SYNAPSE-736) There should be a way to get the encrpted value for a given alias from the secret repository - secure vault

[ https://issues.apache.org/jira/browse/SYNAPSE-736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13003945#comment-13003945 ] asela pathberiya commented on SYNAPSE-736: -- Hi Indika, Yes. That is the better

Function-Templates for Synapse Configuration

Hi Devs, We thought of implementing $subject for Synapse. At the moment a large portion of ESB configuration are at the micro level. Because of this Users have to individually configure each and every mediator to achieve some high level task. But what we need is a high level abstraction that users

[jira] Commented: (SYNAPSE-735) imporve password manager XML syntax which is defined in configuration files - secure vault

[ https://issues.apache.org/jira/browse/SYNAPSE-735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13004049#comment-13004049 ] indika priyantha kumara commented on SYNAPSE-735: - Asela ... It looks

Re: Function-Templates for Synapse Configuration

Udayanga, +1 for the approach. However, I have several concerns Could this and the endpoint template proposed by Supun be similar? Personally, I believe it would be better to reduce language constructs defined by the language. As the synapse language supposed to be a DSL, I think making it

[jira] Issue Comment Edited: (SYNAPSE-735) imporve password manager XML syntax which is defined in configuration files - secure vault

[ https://issues.apache.org/jira/browse/SYNAPSE-735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13004049#comment-13004049 ] indika priyantha kumara edited comment on SYNAPSE-735 at 3/8/11 5:43 PM:

Build failed in Jenkins: Synapse - Trunk #3348

See https://hudson.apache.org/hudson/job/Synapse%20-%20Trunk/3348/ -- Started by timer Building remotely on ubuntu1 FATAL: cannot assign instance of hudson.model.StreamBuildListener to field hudson.scm.subversion.WorkspaceUpdater$UpdateTask.listener of

Build failed in Jenkins: Synapse - Trunk #3349

See https://hudson.apache.org/hudson/job/Synapse%20-%20Trunk/3349/ -- [...truncated 1094 lines...] [INFO] Deleting directory https://hudson.apache.org/hudson/job/Synapse%20-%20Trunk/ws/java/modules/handler/target [INFO] [remote-resources:process

Re: Defining endpoints with a common configuration

Supun, Can we avoid 'endpoints'. When XML is used to define a data-type we usually uses an outer tag (e.g array like data structure in a SOAP message). But, I am not sure whether it is good to define language constructs in that way. Just have a look at the WSDL 2.0 As I said in another email, in

Re: Defining endpoints with a common configuration

On Wed, Mar 9, 2011 at 9:51 AM, indika kumara indika.k...@gmail.com wrote: Supun, Can we avoid 'endpoints'. When XML is used to define a data-type we usually uses an outer tag (e.g array like data structure in a SOAP message). But, I am not sure whether it is good to define language

Re: Function-Templates for Synapse Configuration

Hi Indika, On Tue, Mar 8, 2011 at 11:03 PM, indika kumara indika.k...@gmail.comwrote: Udayanga, +1 for the approach. However, I have several concerns Could this and the endpoint template proposed by Supun be similar? Personally, I believe it would be better to reduce language constructs

Re: Function-Templates for Synapse Configuration

Udayanga, lets go with what you have already done. As we discussed off-line, we can give the same experience for users for defining both endpoint and sequence templates. We can improve things at later. Thanks, Indika On Wed, Mar 9, 2011 at 11:02 AM, Udayanga Wickramasinghe

Re: Function-Templates for Synapse Configuration

Hi , On Wed, Mar 9, 2011 at 11:06 AM, indika kumara indika.k...@gmail.comwrote: Udayanga, lets go with what you have already done. As we discussed off-line, we can give the same experience for users for defining both endpoint and sequence templates. We can improve things at later. thanks a

Re: Defining endpoints with a common configuration

Spun, as we discussed off-line, we can use the same kind of approach proposed by Udanyaga for the endpoint template. BTW, any thing can be improved later. If it is urgent you can go with what you have done so far. But, we have to remove 'endpointGroup' or 'endpoints' ~ Indika On Wed, Mar 9, 2011

Re: Defining endpoints with a common configuration

On Wed, Mar 9, 2011 at 11:11 AM, indika kumara indika.k...@gmail.comwrote: Spun, as we discussed off-line, we can use the same kind of approach proposed by Udanyaga for the endpoint template. BTW, any thing can be improved later. If it is urgent you can go with what you have done so far. But,

Build failed in Jenkins: Synapse - Trunk #3350

See https://hudson.apache.org/hudson/job/Synapse%20-%20Trunk/3350/ -- [...truncated 2087 lines...] [INFO] [INFO] Building Apache Synapse - Configuration Migrator [INFO]