Synapse2: Question about XPath Expressions in SwitchMediator

[Benjamin Schmeling]

Hi,

I am using Apache Synapse 2.0-SNAPSHOT and I have a problem with XPATH
expressions.

I have defined the following configuration:

..
http://mytravelagency.com}searchFlights/{http://mytravelagency.com}destination";>
..

which should be a a valid XPATH expression.

Synapse throws the following exception:

ERROR SynapseServer - Error starting Apache Synapse, trying a clean shutdown...
org.apache.synapse.SynapseException: Invalid XPath for attribute
'source' : 
{http://mytravelagency.com}searchFlights/{http://mytravelagency.com}destination
at 
org.apache.synapse.config.xml.SwitchMediatorFactory.createSpecificMediator(SwitchMediatorFactory.java:71)
at 
org.apache.synapse.config.xml.AbstractMediatorFactory.createMediator(AbstractMediatorFactory.java:88)
..

I've also looked at the code and saw that the SwitchMediatorFactory
directly calls new SynapseXPath(xpathAttrib.getAttributeValue()),
whereas in your test cases you are rather using the
SynapseXPath.parseXPathString(XPATHString) method which does some
preprocessing especially with namespaces. Wouldn't it be better to use
that method in the Switch MediatorFactory instead ?

Thanks,

Benjamin

-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org

Synapse2: Question about XPath Expressions in SwitchMediator

[Benjamin Schmeling]

Hi,

I am using Apache Synapse 2.0-SNAPSHOT and I have a problem with XPATH
expressions.

I have defined the following configuration:

..
http://mytravelagency.com}searchFlights/{http://mytravelagency.com}destination";>
..

which should be a a valid XPATH expression.

Synapse throws the following exception:

ERROR SynapseServer - Error starting Apache Synapse, trying a clean shutdown...
org.apache.synapse.SynapseException: Invalid XPath for attribute
'source' : 
{http://mytravelagency.com}searchFlights/{http://mytravelagency.com}destination
       at 
org.apache.synapse.config.xml.SwitchMediatorFactory.createSpecificMediator(SwitchMediatorFactory.java:71)
       at 
org.apache.synapse.config.xml.AbstractMediatorFactory.createMediator(AbstractMediatorFactory.java:88)
       ..

I've also looked at the code and saw that the SwitchMediatorFactory
directly calls new SynapseXPath(xpathAttrib.getAttributeValue()),
whereas in your test cases you are rather using the
SynapseXPath.parseXPathString(XPATHString) method which does some
preprocessing especially with namespaces. Wouldn't it be better to use
that method in the Switch MediatorFactory instead ?

Thanks,

Benjamin

-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org

Re: [VOTE] Release Synapse-2.0.0 (Take2)

[Ruwan Linton]

Hi Eric,

Fixed the httpcore version on the 2.0 branch and removed the patch from the
2.0 branch too.

Also the migration tool has been fixed to copy the namespace declarations
when migrating the configuration.

Thanks,
Ruwan

On Sun, Dec 12, 2010 at 8:02 AM, Ruwan Linton wrote:

> Hi Eric,
>
> On Sat, Dec 11, 2010 at 9:40 PM, Hubert, Eric 
> wrote:
>
>>  I found another issue with the nhttp transports:
>>
>>
>>
>> I guess Synapse 2.0 release should not be shipped with http core / http
>> core nio 4.1 alpha 1 dependencies, but the final release version 4.1.
>>
>> I also think the patch for httpcore-193 is no longer needed and the binary
>> patch should not be in the patches directory.
>>
>
> Cool, I guess a good catch, will fix it.
>
>
>>
>>
>> Apart from that I finished the mediator migration and I’m now starting to
>> test including custom mediators. Unfortunately I will have to continue
>> tomorrow, as I have to take care of other things today.
>>
>
> Sure no problem.
>
>
>>
>>
>>
>>
>> Regards,
>>
>>Eric
>>
>>
>>
>> PS: Is there already an updated version of the migration tool to test?
>>
>
> Unfortunately not yet Eric, I didn't have time to work on that, planning to
> work on resolving all the issue today starting from now on. :-) Will post
> the tool once there is an update.
>
> Thanks,
> Ruwan
>
>
>>
>>   --
>>
>> *From:* Ruwan Linton [mailto:ruwan.lin...@gmail.com]
>> *Sent:* Thursday, December 09, 2010 11:08 AM
>>
>> *To:* dev@synapse.apache.org
>> *Subject:* Re: [VOTE] Release Synapse-2.0.0 (Take2)
>>
>>
>>
>> Hiranya,
>>
>>
>>
>> I've fixed this dependency issue, I expect you to do a build on the local
>> machine and check this, will wait for your comments to the next RC :-)
>>
>>
>>
>> Thanks,
>>
>> Ruwan
>>
>> On Thu, Dec 9, 2010 at 12:44 AM, Hiranya Jayathilaka <
>> hiranya...@gmail.com> wrote:
>>
>> I hate to be a PITA but I see another issue with this. The FIX
>> transport has been included in the latest binary. So that's good. But
>> I can see that Quickfix/J has also crept into the distro (about 9MB).
>> FIX transport also requires MINA and SLF4J which are not included in
>> the binary. So IMO either we should include all the required
>> dependencies or none of them. I think we should add an exclusion to
>> Quickfix/J and keep it out of the binary. WDYT?
>>
>> Thanks,
>> Hiranya
>>
>>
>> On Wed, Dec 8, 2010 at 12:27 PM, Ruwan Linton 
>> wrote:
>> > Hi Devs,
>> >
>> > This is take 2 call for votes to release Synapse-2.0.0.
>> >
>> > Please review the signed artifacts:
>> > http://people.apache.org/~ruwan/synapse/2.0.0-RC2/artifacts/
>> > The m2 repository is available at:
>> > http://people.apache.org/~ruwan/synapse/2.0.0-RC2/m2_repo/
>> > Site update for this release is available at:
>> > http://people.apache.org/~ruwan/synapse/2.0.0-RC2/site/
>> > SVN Info:
>> > revision is 1043322 on
>> > https://svn.apache.org/repos/asf/synapse/branches/2.0
>> > Here's my +1 to declaring the above dist as Synapse-2.0.0.
>> >
>> > Thanks,
>> > Ruwan
>> > PS: The KEYS file for signing these
>> > releases http://www.apache.org/dist/synapse/KEYS
>> > --
>> > Ruwan Linton
>> > Software Architect & Product Manager, WSO2 ESB; http://wso2.org/esb
>> > WSO2 Inc.; http://wso2.org
>> >
>> > Lean . Enterprise . Middleware
>> >
>> > phone: +1 408 754 7388 ext 51789
>> > email: ru...@wso2.com; cell: +94 77 341 3097
>> > blog: http://blog.ruwan.org
>> > linkedin: http://www.linkedin.com/in/ruwanlinton
>> > google: http://www.google.com/profiles/ruwan.linton
>> > tweet: http://twitter.com/ruwanlinton
>> >
>>
>>
>>   --
>> Hiranya Jayathilaka
>> Senior Software Engineer;
>>
>> WSO2 Inc.;  http://wso2.org
>>
>> E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
>> Blog: http://techfeast-hiranya.blogspot.com
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
>> For additional commands, e-mail: dev-h...@synapse.apache.org
>>
>>
>>
>>
>> --
>> Ruwan Linton
>> Software Architect & Product Manager, WSO2 ESB; http://wso2.org/esb
>> WSO2 Inc.; http://wso2.org
>>
>> Lean . Enterprise . Middleware
>>
>> phone: +1 408 754 7388 ext 51789
>> email: ru...@wso2.com; cell: +94 77 341 3097
>> blog: http://blog.ruwan.org
>> linkedin: http://www.linkedin.com/in/ruwanlinton
>> google: http://www.google.com/profiles/ruwan.linton
>> tweet: http://twitter.com/ruwanlinton
>>
>
>
>
> --
> Ruwan Linton
> Software Architect & Product Manager, WSO2 ESB; http://wso2.org/esb
> WSO2 Inc.; http://wso2.org
>
> Lean . Enterprise . Middleware
>
> phone: +1 408 754 7388 ext 51789
> email: ru...@wso2.com; cell: +94 77 341 3097
> blog: http://blog.ruwan.org
> linkedin: http://www.linkedin.com/in/ruwanlinton
> google: http://www.google.com/profiles/ruwan.linton
> tweet: http://twitter.com/ruwanlinton
>



-- 
Ruwan Linton
Software Architect & Product Manager, WSO2 ESB; http://wso2.org/esb
WSO2 Inc.; http://wso2.org

Lean . Enterprise . Midd

Re: [VOTE] Release Synapse-2.0.0 (Take2)

[Ruwan Linton]

Hi Eric,

On Thu, Dec 9, 2010 at 4:13 PM, Hubert, Eric wrote:

>  Answers inline. Not every statement was meant to describe a „problem“, I
> simply always described what I did and what happened. Unexpected behaviour
> is separately mentioned…
>   --
>
>
>
> 1) Synapse startup test with custom 1.2 config
>
> - config has been put into repository/conf/synapse-config as it seems to
> got ignored in repository/conf
>
>
>
> I think this is by design and we need to document this on the Upgrading
> guide.
>
> Agreed.
>

Documented this on the upgrading guide, as the first thing to read when
migrating from 1.2 to 2.0


>
>
>   - Synapse does not startup due to a problem in the config (e.g. missing
> registry implementation class on the classpath)
>
>
>
> I will have a look at this, I guess this needs to be fixed if there is an
> issue, can you please give me a small config bit to re-produce this issue?
> may be you are using a WSO2 ESB registry class shipped with WSO2 which of
> course is not available in synapse. :-(
>
> Yes, my aim was to test a failure case. So it was absolutely expected that
> this fails. No issue at all!
>
>
>
>   - Unexpected behaviour: Although Synapse detects the problems, tries to
> perform a clean shutdown, it “keeps hanging” and does not return to the
> shell with an error return value
>
>
>
> Can you please attach the log for this and steps to re-produce, this again
> I would like to fix depending on the complexity of the issue... and if this
> gets slipped from 2.0.0 I suggest immediately spinning a 2.0.1 to fix this
> and any other this sort of issues from the 2.0.0 branch. WDYT?
>
> Yes, I personally do not consider this critical – it is simply only not
> nice. By the way, the same condition can be reached with many different
> issues in a user’s config. Reproduction is easy. Just specify any class name
> non existing in the classpath e.g. as the registry provider implementation.
>

It was just a missing exit statement, it does the clean shutdown and just
that the thread is not existing. I have fixed this too, on the 2.0 branch,
though I was not planning to fix this for the release it happened to be an
easy fix.


>
>
> 2) Migration Tool
>
> - executing the migration tool expects a config in repository/conf (former
> config location)
>
>
>
> If you type help for the migration tool sh you will find that it is the
> default location the script looks for but you can specify your own location
> too.
>
> Maybe it would be slightly better if an no arg execution outputs a usage
> instead of assuming the default location and immediately starting to do
> something. But this is obviously a matter of taste…
>

I will fix this as this seems more appropriate.


>
>
>   - old copy copied there and restarted
>
> - migration tool modifies config
>
> - Unexpected behaviour:
>
> - after migration config stays in repository/conf and needs to be manually
> copied to repository/conf/synapse-conf to be recognized
>
>
>
> This again is the default location, assuming that you are running the
> migration tool for an old configuration, but you could of course give the
> new location to be saved after migrating the configuration. I guess we need
> a little bit more documentation around the migration tool.
>
>
>
>   - migration tool mistakenly removes namespaces (destroying the config),
> e.g.
> http://www.w3.org/2003/05/soap-envelope";
> value="tns:Receiver"/> à  resulting in
> startup issues
>
>
>
> This we need to fix for this release, I will work on this.
>
> Great, I’d also consider this to be a blocker as the migration tool can
> convert a working config into a non-working one. I have not checked whether
> a backup is saved somewhere…
>

It backs up the original file. I've also fixed this issue.


>
>
>   - migration tool removes indentation at the beginning of each xml
> element
>
>
>
> This is a known issue, but I agree needs to be fixed, since it is not
> critical I would live with this for the 2.0.0, but definitely a candidate
> for the next version, so we need to raise an issue ticket on the synapse
> JIRA for this.
>
>  Agreed, if no one beats me I can do this later today…
>

Will create an issue for this, but I looked for fixing this but couldn't
find a way to crack it :-(


>
>
>
>
> 3) Traditional config in single file versus multi file configuration
>
> - Unexpected behaviour:
>
>   - replacing dummy synapse.xml with old (converted) config is not enough,
> it results in errors if main and/or fault sequences are used (as the must
> exist only once), sequence files need to be removed
>
>   from subdirectories
>
>
>
> Yes, this I agree with, but cannot do much I guess again need to explain
> this on the Upgrading guide
>
> Is the reason for this, that no concept has precedence over the other? One
> can mix both approaches as desired? If so I fully understand, but
> documentation is the least we should do. I would also vote for a prominent
> link to the Upgrading sec

Re: Synapse2: Question about XPath Expressions in SwitchMediator

[Ruwan Linton]

I think you are correct, let me have a look at using the parseXPathString
instead of the current one.

Thanks,
Ruwan

On Wed, Dec 15, 2010 at 5:21 PM, Benjamin Schmeling <
benjamin.schmel...@googlemail.com> wrote:

> Hi,
>
> I am using Apache Synapse 2.0-SNAPSHOT and I have a problem with XPATH
> expressions.
>
> I have defined the following configuration:
>
> ..
>  source="{http://mytravelagency.com}searchFlights/{
> http://mytravelagency.com}destination";>
> ..
>
> which should be a a valid XPATH expression.
>
> Synapse throws the following exception:
>
> ERROR SynapseServer - Error starting Apache Synapse, trying a clean
> shutdown...
> org.apache.synapse.SynapseException: Invalid XPath for attribute
> 'source' : {http://mytravelagency.com}searchFlights/{
> http://mytravelagency.com}destination
>at
> org.apache.synapse.config.xml.SwitchMediatorFactory.createSpecificMediator(SwitchMediatorFactory.java:71)
>at
> org.apache.synapse.config.xml.AbstractMediatorFactory.createMediator(AbstractMediatorFactory.java:88)
>..
>
> I've also looked at the code and saw that the SwitchMediatorFactory
> directly calls new SynapseXPath(xpathAttrib.getAttributeValue()),
> whereas in your test cases you are rather using the
> SynapseXPath.parseXPathString(XPATHString) method which does some
> preprocessing especially with namespaces. Wouldn't it be better to use
> that method in the Switch MediatorFactory instead ?
>
> Thanks,
>
> Benjamin
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
> For additional commands, e-mail: dev-h...@synapse.apache.org
>
>


-- 
Ruwan Linton
Software Architect & Product Manager, WSO2 ESB; http://wso2.org/esb
WSO2 Inc.; http://wso2.org

Lean . Enterprise . Middleware

phone: +1 408 754 7388 ext 51789
email: ru...@wso2.com; cell: +94 77 341 3097
blog: http://blog.ruwan.org
linkedin: http://www.linkedin.com/in/ruwanlinton
google: http://www.google.com/profiles/ruwan.linton
tweet: http://twitter.com/ruwanlinton

RE: [VOTE] Release Synapse-2.0.0 (Take2)

[Hubert, Eric]

Hi Ruwan,

Thanks for fixing the issues. Meanwhile I tested the updated migration template 
definition from the 2.0 branch and it worked without problems.
Sorry, I completely forgot to create an issue for the minor indentation problem.

Once you go through the API changes, some of my earlier mails to this list 
might be of help. While you are at it, it would be nice if you could also check 
my question regarding the visibility of the createSpecificMediator method.


Regards,
   Eric



From: Ruwan Linton [mailto:ruwan.lin...@gmail.com]
Sent: Wednesday, December 15, 2010 3:03 PM
To: dev@synapse.apache.org
Subject: Re: [VOTE] Release Synapse-2.0.0 (Take2)

Hi Eric,

Fixed the httpcore version on the 2.0 branch and removed the patch from the 2.0 
branch too.

Also the migration tool has been fixed to copy the namespace declarations when 
migrating the configuration.

Thanks,
Ruwan
On Sun, Dec 12, 2010 at 8:02 AM, Ruwan Linton 
mailto:ruwan.lin...@gmail.com>> wrote:
Hi Eric,
On Sat, Dec 11, 2010 at 9:40 PM, Hubert, Eric 
mailto:eric.hub...@foxmobile.com>> wrote:
I found another issue with the nhttp transports:

I guess Synapse 2.0 release should not be shipped with http core / http core 
nio 4.1 alpha 1 dependencies, but the final release version 4.1.
I also think the patch for httpcore-193 is no longer needed and the binary 
patch should not be in the patches directory.

Cool, I guess a good catch, will fix it.



Apart from that I finished the mediator migration and I’m now starting to test 
including custom mediators. Unfortunately I will have to continue tomorrow, as 
I have to take care of other things today.

Sure no problem.






Regards,

   Eric



PS: Is there already an updated version of the migration tool to test?

Unfortunately not yet Eric, I didn't have time to work on that, planning to 
work on resolving all the issue today starting from now on. :-) Will post the 
tool once there is an update.

Thanks,
Ruwan





From: Ruwan Linton 
[mailto:ruwan.lin...@gmail.com]
Sent: Thursday, December 09, 2010 11:08 AM

To: dev@synapse.apache.org
Subject: Re: [VOTE] Release Synapse-2.0.0 (Take2)

Hiranya,

I've fixed this dependency issue, I expect you to do a build on the local 
machine and check this, will wait for your comments to the next RC :-)

Thanks,
Ruwan
On Thu, Dec 9, 2010 at 12:44 AM, Hiranya Jayathilaka 
mailto:hiranya...@gmail.com>> wrote:
I hate to be a PITA but I see another issue with this. The FIX
transport has been included in the latest binary. So that's good. But
I can see that Quickfix/J has also crept into the distro (about 9MB).
FIX transport also requires MINA and SLF4J which are not included in
the binary. So IMO either we should include all the required
dependencies or none of them. I think we should add an exclusion to
Quickfix/J and keep it out of the binary. WDYT?

Thanks,
Hiranya

On Wed, Dec 8, 2010 at 12:27 PM, Ruwan Linton 
mailto:ruwan.lin...@gmail.com>> wrote:
> Hi Devs,
>
> This is take 2 call for votes to release Synapse-2.0.0.
>
> Please review the signed artifacts:
> http://people.apache.org/~ruwan/synapse/2.0.0-RC2/artifacts/
> The m2 repository is available at:
> http://people.apache.org/~ruwan/synapse/2.0.0-RC2/m2_repo/
> Site update for this release is available at:
> http://people.apache.org/~ruwan/synapse/2.0.0-RC2/site/
> SVN Info:
> revision is 1043322 on
> https://svn.apache.org/repos/asf/synapse/branches/2.0
> Here's my +1 to declaring the above dist as Synapse-2.0.0.
>
> Thanks,
> Ruwan
> PS: The KEYS file for signing these
> releases http://www.apache.org/dist/synapse/KEYS
> --
> Ruwan Linton
> Software Architect & Product Manager, WSO2 ESB; http://wso2.org/esb
> WSO2 Inc.; http://wso2.org
>
> Lean . Enterprise . Middleware
>
> phone: +1 408 754 7388 ext 51789
> email: ru...@wso2.com; cell: +94 77 341 3097
> blog: http://blog.ruwan.org
> linkedin: http://www.linkedin.com/in/ruwanlinton
> google: http://www.google.com/profiles/ruwan.linton
> tweet: http://twitter.com/ruwanlinton
>

--
Hiranya Jayathilaka
Senior Software Engineer;
WSO2 Inc.;  http://wso2.org
E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
Blog: http://techfeast-hiranya.blogspot.com

-
To unsubscribe, e-mail: 
dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: 
dev-h...@synapse.apache.org



--
Ruwan Linton
Software Architect & Product Manager, WSO2 ESB; http://wso2.org/esb
WSO2 Inc.; http://wso2.org

Lean . Enterprise . Middleware

phone: +1 408 754 7388 ext 51789
email: ru...@wso2.com; cell: +94 77 341 3097
blog: http://blog.ruwan.org
linkedin: http://www.linkedin.com/in/ruwanlinton
google: http://www.google.com/profiles/ruwan.lint

Re: [VOTE] Release Synapse-2.0.0 (Take2)

[Ruwan Linton]

HI Eric,

On Wed, Dec 15, 2010 at 9:24 PM, Hubert, Eric wrote:

>  Hi Ruwan,
>
>
>
> Thanks for fixing the issues. Meanwhile I tested the updated migration
> template definition from the 2.0 branch and it worked without problems.
>
> Sorry, I completely forgot to create an issue for the minor indentation
> problem.
>

No that is OK.


>
>
> Once you go through the API changes, some of my earlier mails to this list
> might be of help. While you are at it, it would be nice if you could also
> check my question regarding the visibility of the createSpecificMediator
> method.
>

Of course I am attending to the stuff in a FCFS manner, resolved all the
other stuff which came in for the build, and since this is the last one,
handling it now.

If you see the commit messages I am done with the migration tool returning
without assuming config file location if the file location is not provided
fix too. So just the API changes documentation and your analysis on the
MediatorFactory API to be cracked. :-)

Hoping to do the RC3 as planned for tomorrow.

Thanks,
Ruwan


>
>
>
>
> Regards,
>
>Eric
>
>
>
>
>   --
>
> *From:* Ruwan Linton [mailto:ruwan.lin...@gmail.com]
> *Sent:* Wednesday, December 15, 2010 3:03 PM
>
> *To:* dev@synapse.apache.org
> *Subject:* Re: [VOTE] Release Synapse-2.0.0 (Take2)
>
>
>
> Hi Eric,
>
>
>
> Fixed the httpcore version on the 2.0 branch and removed the patch from the
> 2.0 branch too.
>
>
>
> Also the migration tool has been fixed to copy the namespace declarations
> when migrating the configuration.
>
>
>
> Thanks,
>
> Ruwan
>
> On Sun, Dec 12, 2010 at 8:02 AM, Ruwan Linton 
> wrote:
>
> Hi Eric,
>
> On Sat, Dec 11, 2010 at 9:40 PM, Hubert, Eric 
> wrote:
>
> I found another issue with the nhttp transports:
>
>
>
> I guess Synapse 2.0 release should not be shipped with http core / http
> core nio 4.1 alpha 1 dependencies, but the final release version 4.1.
>
> I also think the patch for httpcore-193 is no longer needed and the binary
> patch should not be in the patches directory.
>
>
>
> Cool, I guess a good catch, will fix it.
>
>
>
>
>
> Apart from that I finished the mediator migration and I’m now starting to
> test including custom mediators. Unfortunately I will have to continue
> tomorrow, as I have to take care of other things today.
>
>
>
> Sure no problem.
>
>
>
>
>
>
>
> Regards,
>
>Eric
>
>
>
> PS: Is there already an updated version of the migration tool to test?
>
>
>
> Unfortunately not yet Eric, I didn't have time to work on that, planning to
> work on resolving all the issue today starting from now on. :-) Will post
> the tool once there is an update.
>
>
>
> Thanks,
>
> Ruwan
>
>
>
>
>   --
>
> *From:* Ruwan Linton [mailto:ruwan.lin...@gmail.com]
> *Sent:* Thursday, December 09, 2010 11:08 AM
>
>
> *To:* dev@synapse.apache.org
> *Subject:* Re: [VOTE] Release Synapse-2.0.0 (Take2)
>
>
>
> Hiranya,
>
>
>
> I've fixed this dependency issue, I expect you to do a build on the local
> machine and check this, will wait for your comments to the next RC :-)
>
>
>
> Thanks,
>
> Ruwan
>
> On Thu, Dec 9, 2010 at 12:44 AM, Hiranya Jayathilaka 
> wrote:
>
> I hate to be a PITA but I see another issue with this. The FIX
> transport has been included in the latest binary. So that's good. But
> I can see that Quickfix/J has also crept into the distro (about 9MB).
> FIX transport also requires MINA and SLF4J which are not included in
> the binary. So IMO either we should include all the required
> dependencies or none of them. I think we should add an exclusion to
> Quickfix/J and keep it out of the binary. WDYT?
>
> Thanks,
> Hiranya
>
>
> On Wed, Dec 8, 2010 at 12:27 PM, Ruwan Linton 
> wrote:
> > Hi Devs,
> >
> > This is take 2 call for votes to release Synapse-2.0.0.
> >
> > Please review the signed artifacts:
> > http://people.apache.org/~ruwan/synapse/2.0.0-RC2/artifacts/
> > The m2 repository is available at:
> > http://people.apache.org/~ruwan/synapse/2.0.0-RC2/m2_repo/
> > Site update for this release is available at:
> > http://people.apache.org/~ruwan/synapse/2.0.0-RC2/site/
> > SVN Info:
> > revision is 1043322 on
> > https://svn.apache.org/repos/asf/synapse/branches/2.0
> > Here's my +1 to declaring the above dist as Synapse-2.0.0.
> >
> > Thanks,
> > Ruwan
> > PS: The KEYS file for signing these
> > releases http://www.apache.org/dist/synapse/KEYS
> > --
> > Ruwan Linton
> > Software Architect & Product Manager, WSO2 ESB; http://wso2.org/esb
> > WSO2 Inc.; http://wso2.org
> >
> > Lean . Enterprise . Middleware
> >
> > phone: +1 408 754 7388 ext 51789
> > email: ru...@wso2.com; cell: +94 77 341 3097
> > blog: http://blog.ruwan.org
> > linkedin: http://www.linkedin.com/in/ruwanlinton
> > google: http://www.google.com/profiles/ruwan.linton
> > tweet: http://twitter.com/ruwanlinton
> >
>
>   --
> Hiranya Jayathilaka
> Senior Software Engineer;
>
> WSO2 Inc.;  http://wso2.org
>
> E-mail: hira...@wso2.com;  Mobile: +94 

Re: [VOTE] Release Synapse-2.0.0 (Take2)

[Ruwan Linton]

Rajika,

Fixed the README file. Source distro has already been fixed.

Having a look at the source build issue, I also got the same error once when
doing the clean repo build, I guess one of the repos has a corrupted jar
file.

Thanks,
Ruwan

On Fri, Dec 10, 2010 at 8:38 AM, Rajika Kumarasiri  wrote:

> Ruwan,
> I hope I am not late for comments.
>
> 1. I just downloaded the synapse-2.0.0-src.tar.gz and the README.txt says
> Sepetember 2010 build. I am not sure if it should be change to December
> 2010.
>
> 2. I noticed what Eric has noticed and each folder in the source
> distribution(synapse-2.0.0-src.tar.gz) contains an additional pom.xml.orig
> file.
>
> 3. I also tried to build the source distribution (synapse-2.0.0-src.tar.gz)
> and ended up with the following error. I am building on Fedora with mvn
> option: mvn clean install
>
> Compiling 81 source files to
> /home/rajika/projects/synapse/rc/2.0/synapse-2.0.0-src/modules/commons/target/classes
> [INFO]
> 
>
> [ERROR] BUILD FAILURE
> [INFO]
> 
> [INFO] Compilation failure
>
> error: error reading
> /home/rajika/.m2/repository/org/apache/sandesha2/sandesha2-core/1.3-1041287/sandesha2-core-1.3-1041287.jar;
> error in opening zip file
>
> [INFO]
> 
> [INFO] For more information, run Maven with the -e switch
> [INFO]
> 
> [INFO] Total time: 43 seconds
> [INFO] Finished at: Fri Dec 10 08:33:41 IST 2010
> [INFO] Final Memory: 56M/245M
> [INFO]
> 
> [raj...@localhost synapse-2.0.0-src]$
>
>
> 4. I also tested the binary distribution (synapse-2.0.0-bin.tar.gz), ran
> couple of samples picked randomly and they work as expected.
>
> Rajika
>
>
> On Wed, Dec 8, 2010 at 12:27 PM, Ruwan Linton wrote:
>
>> Hi Devs,
>>
>> This is take 2 call for votes to release Synapse-2.0.0.
>>
>> Please review the signed artifacts:
>> http://people.apache.org/~ruwan/synapse/2.0.0-RC2/artifacts/
>>  
>> The m2 repository is available at:
>> http://people.apache.org/~ruwan/synapse/2.0.0-RC2/m2_repo/
>>
>> Site update for this release is available at:
>> http://people.apache.org/~ruwan/synapse/2.0.0-RC2/site/
>>
>> SVN Info:
>> revision is 1043322 on
>> https://svn.apache.org/repos/asf/synapse/branches/2.0
>>
>> Here's my +1 to declaring the above dist as Synapse-2.0.0.
>>
>> Thanks,
>> Ruwan
>>
>> PS: The KEYS file for signing these releases
>> http://www.apache.org/dist/synapse/KEYS
>>
>> --
>> Ruwan Linton
>> Software Architect & Product Manager, WSO2 ESB; http://wso2.org/esb
>> WSO2 Inc.; http://wso2.org
>>
>> Lean . Enterprise . Middleware
>>
>> phone: +1 408 754 7388 ext 51789
>> email: ru...@wso2.com; cell: +94 77 341 3097
>> blog: http://blog.ruwan.org
>> linkedin: http://www.linkedin.com/in/ruwanlinton
>> google: http://www.google.com/profiles/ruwan.linton
>> tweet: http://twitter.com/ruwanlinton
>>
>
>


-- 
Ruwan Linton
Software Architect & Product Manager, WSO2 ESB; http://wso2.org/esb
WSO2 Inc.; http://wso2.org

Lean . Enterprise . Middleware

phone: +1 408 754 7388 ext 51789
email: ru...@wso2.com; cell: +94 77 341 3097
blog: http://blog.ruwan.org
linkedin: http://www.linkedin.com/in/ruwanlinton
google: http://www.google.com/profiles/ruwan.linton
tweet: http://twitter.com/ruwanlinton