Nice to hear that you got it to work. Hope you can use synapse now ;-) I was
unable to reproduce this issue and that is why I wanted the full log just to
have a look at your environment.
Thanks for letting us know that you got it resolved.
Thanks,
Ruwan
On Wed, Mar 4, 2009 at 4:59 AM, kimhorn w
Andreas,
I didn't note this earlier. My intention was to switch back to sandesha2
because the current RM implementation that Synapse is using for the moment
(WSO2 Mercury) is not supported by the WSO2 any more at least in this year
and I wanted to move back to sandesha2.
If I describe the history
Resolved the problem; FIXED, was environment problem :-)
JAVA_HOME is irrelevant. Not used by some components.
Unless the PATH has Java set at start it can run another Java; Whatever
Microsoft downloads into system.
So:
set JAVA_HOME=C:\Program Files\Java\jdk1.5.0_17
set Path=C:\Program
Files\Ja
Ruwan,
This change was proposed in SYNAPSE-493, but there the conclusion was
that this change would be in contradiction with the available
documentation in Axis2 and that it is more likely an issue in
Sandesha2.
Andreas
On Tue, Mar 3, 2009 at 22:37, wrote:
> Author: ruwan
> Date: Tue Mar 3 21
See "Random Start Up Error" by kimhorn posted Feb 26
Its the complete output, and I attached a log here too
http://www.nabble.com/file/p22319212/synapse.log synapse.log
I re-build a new machine with virtually no software on it.
I get the same problems...can't use Synapse.
Ruwan Linton wrot
On Wed, Mar 4, 2009 at 2:04 AM, Asankha C. Perera wrote:
> Ruwan
>
>> True, so to avoid that risk we could introduce an attribute to the
>> sequence configuration to specify whether the user wants to expose this
>> sequence or not. And we can make them not exposed by default.
>>
> I am +1 for this
I am calling the vote closed!
This vote has been open more than 72 hours now and vote passes with 7
+1s and no -1s.
Congratulations Asankha! Can you post the release plan?
Thanks everyone,.. So far I have updated the Synapse trunk to build
against Axis2 1.5-beat-2, which soon will be a 1.5-
[
https://issues.apache.org/jira/browse/SYNAPSE-480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ruwan Linton updated SYNAPSE-480:
-
Affects Version/s: (was: FUTURE)
1.2
changed the affects version
> T
Ruwan
True, so to avoid that risk we could introduce an attribute to the
sequence configuration to specify whether the user wants to expose
this sequence or not. And we can make them not exposed by default.
I am +1 for this proposal.. also maybe the mandatory sequence could be
used to handle se
[
https://issues.apache.org/jira/browse/SYNAPSE-480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ruwan Linton resolved SYNAPSE-480.
--
Resolution: Fixed
Fix Version/s: (was: FUTURE)
1.3
Applied the p
True, so to avoid that risk we could introduce an attribute to the sequence
configuration to specify whether the user wants to expose this sequence or
not. And we can make them not exposed by default.
Thanks,
Ruwan
On Wed, Mar 4, 2009 at 1:47 AM, Andreas Veithen
wrote:
> Is there no security ris
[
https://issues.apache.org/jira/browse/SYNAPSE-480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ruwan Linton reopened SYNAPSE-480:
--
> Transaction mediator for synapse
>
>
> Key: SYN
[
https://issues.apache.org/jira/browse/SYNAPSE-480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ruwan Linton reassigned SYNAPSE-480:
Assignee: Ruwan Linton
> Transaction mediator for synapse
> --
Is there no security risk here? If I understand the proposal
correctly, it would be possible to invoke any named sequence, even if
it is not intended to be exposed. This could potentially be dangerous.
Andreas
On Tue, Mar 3, 2009 at 20:53, Ruwan Linton wrote:
> Hi devs,
>
> I would like to propo
Hi devs,
I would like to propose to implement the ability to dispatch messages
directly to sequences.
For the moment, all the messages which are coming in the message mediation
is going to be dispatched into the "main" sequence and if you want different
messages to be directed to different sequen
I am calling the vote closed!
This vote has been open more than 72 hours now and vote passes with 7 +1s
and no -1s.
Congratulations Asankha! Can you post the release plan?
Thanks,
Ruwan
On Mon, Mar 2, 2009 at 7:50 PM, Asanka Abeysinghe wrote:
> +1
> - Asanka
>
>
> Ruwan Linton wrote:
>
>> Hi
Can you please attach the complete log of the ESB when running this sample?
May be you could attach this to the JIRA issue after reopening the issue as
Asankha pointed.
Thanks,
Ruwan
On Tue, Mar 3, 2009 at 10:20 AM, kimhorn wrote:
>
> 1.2 Release. I removed all other sources of BSF and it
> ma
17 matches
Mail list logo