You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@synapse.apache.org by Ruwan Linton <ru...@gmail.com> on 2010/12/08 07:57:21 UTC

[VOTE] Release Synapse-2.0.0 (Take2)

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/
<http://people.apache.org/~ruwan/synapse/2.0.0/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: ruwan@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)

Posted by Ruwan Linton <ru...@gmail.com>.
These are my mistakes in building the source pack, Eric. Corrected now.
Thanks for pointing.

Thanks,
Ruwan

On Thu, Dec 9, 2010 at 10:17 PM, Hubert, Eric <Er...@foxmobile.com>wrote:

>  Ruwan, could you please have a glance on the source distribution folders
> modules/commons, modules/securevault. What is the purpose of the m2 repo
> folders “m2-repo-synapse-2.0.0”? This looks somehow strange. Additionally
> each maven root contains a pom.xml.orig.
>
>
>
> Thanks,
>
>    Eric
>
>
>   ------------------------------
>
> *From:* Ruwan Linton [mailto:ruwan.linton@gmail.com]
> *Sent:* Wednesday, December 08, 2010 7:57 AM
>
> *To:* dev@synapse.apache.org
> *Subject:* [VOTE] Release Synapse-2.0.0 (Take2)
>
>
>
> 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/
>
> <http://people.apache.org/~ruwan/synapse/2.0.0/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: ruwan@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: ruwan@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)

Posted by "Hubert, Eric" <Er...@foxmobile.com>.
Ruwan, could you please have a glance on the source distribution folders modules/commons, modules/securevault. What is the purpose of the m2 repo folders “m2-repo-synapse-2.0.0”? This looks somehow strange. Additionally each maven root contains a pom.xml.orig.

Thanks,
   Eric

________________________________
From: Ruwan Linton [mailto:ruwan.linton@gmail.com]
Sent: Wednesday, December 08, 2010 7:57 AM
To: dev@synapse.apache.org
Subject: [VOTE] Release Synapse-2.0.0 (Take2)

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/
<http://people.apache.org/~ruwan/synapse/2.0.0/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: ruwan@wso2.com<ma...@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)

Posted by Ruwan Linton <ru...@gmail.com>.
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 <ra...@wso2.com> 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]
> ------------------------------------------------------------------------
> [rajika@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 <ru...@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/<http://people.apache.org/%7Eruwan/synapse/2.0.0-RC2/artifacts/>
>>  <http://people.apache.org/%7Eruwan/synapse/2.0.0/artifacts/>
>> The m2 repository is available at:
>> http://people.apache.org/~ruwan/synapse/2.0.0-RC2/m2_repo/<http://people.apache.org/%7Eruwan/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/<http://people.apache.org/%7Eruwan/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: ruwan@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: ruwan@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)

Posted by Rajika Kumarasiri <ra...@wso2.com>.
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]
------------------------------------------------------------------------
[rajika@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 <ru...@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/<http://people.apache.org/%7Eruwan/synapse/2.0.0-RC2/artifacts/>
>  <http://people.apache.org/%7Eruwan/synapse/2.0.0/artifacts/>
> The m2 repository is available at:
> http://people.apache.org/~ruwan/synapse/2.0.0-RC2/m2_repo/<http://people.apache.org/%7Eruwan/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/<http://people.apache.org/%7Eruwan/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: ruwan@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)

Posted by Ruwan Linton <ru...@gmail.com>.
Hi Eric,

On Thu, Dec 9, 2010 at 4:13 PM, Hubert, Eric <Er...@foxmobile.com>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.
>     <code xmlns:tns="http://www.w3.org/2003/05/soap-envelope"
> value="tns:Receiver"/> à <syn:code 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 section in the documentation right from the front
> page. May under what’s new or so…
>

Well, my view is it is not so good to neglect the configurations either on
synapse.xml nor on the sequences dir and so forth, to me that is a user
error and we should fail to start if the failsafe mode is not set.


>
>
> 4) Usage of custom mediators / Site Documentation “Upgrading”
>
> - In the docu I could not quickly locate a document summarizing the steps
> which need to be done to upgrade custom mediators according to API changes
> (I received some AbstractMethodError). I did not check the mediator sources
> against the current libraries to find out what is no longer compiling….
> Anyway a quick summary of API changes would be nice. As long as I haven’t
> check the points which do not compile I cannot say for sure, whether those
> problems are due to the fact that public methods not considered to be part
> of the public API have been used on our end (which is not unlikely at all).
>
>
>
> I agree, will try to add more on the API changes, at least for the mediator
> API.
>

This is the second and the final task that is remaining...

Am trying to get the RC3 out by tomorrow my time, which is within the next
24 hours.

Thanks,
Ruwan


>  Great.
>
>
>
>
>   ------------------------------
>
> *From:* Ruwan Linton [mailto:ruwan.linton@gmail.com]
> *Sent:* Thursday, December 09, 2010 7:04 AM
>
>
> *To:* dev@synapse.apache.org
> *Subject:* Re: [VOTE] Release Synapse-2.0.0 (Take2)
>
>
>
> So the Sandesha module can be easily removed if you are not doing any
> reliable messaging stuff. Just need to delete the file from the
> repository/modules directory. I would even remove this error message from
> the custom build of Sandesha2 as we any way seem to go for the 3rd round of
> voting. :-)
>
>
>
> Eric, I would like to wait for your feedback to do the 3rd RC. So take your
> time, but report us any critical issue as soon as you get to them. May not
> need to be the complete list, you can report them one by one as and when you
> find those, so that we can fix them if needs to be and be ready for your
> next round of the feedback. BTW: must say that we really appreciate your
> feedback.
>
>
>
> Thanks,
>
> Ruwan
>
>
>
>
> --
> 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: ruwan@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: ruwan@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)

Posted by Ruwan Linton <ru...@gmail.com>.
Cool, I am planning to start the build shortly, it might extend to tomorrow
to get the artifacts published for the vote.

Thanks,
Ruwan

On Thu, Dec 16, 2010 at 6:32 PM, Hubert, Eric <Er...@foxmobile.com>wrote:

>  Hi Ruwan,
>
>
>
> there is not much to worry about. I have been able to rather easily fix all
> of those issues. I have been only a bit concerned about users which are not
> familiar with the Synapse code at all.
>
>
>
> As you said, the errors regarding SynapseArtifact.getDescription() came
> from custom mediator implementations directly implementing the mediator
> interface without using the abstract base implementation. I do not know how
> often people might have done this. For some of our mediators there was no
> need to extend from the base implementation as it offered nothing meaningful
> for those cases. I guess with Synapse 2.0 users are now strongly encouraged
> to extend the base implementation. Otherwise they have to implement some
> aspects they do not like to care about at all.
>
>
>
> Thanks for the explanation regarding the properties usage. Now it’s purpose
> is clear. Just from looking at the API and Unit-Tests (which is mostly a
> good start to understand something) I wasn’t able to get it.
>
>
>
> Thanks,
>
>    Eric
>
>
>
>
>   ------------------------------
>
> *From:* Ruwan Linton [mailto:ruwan.linton@gmail.com]
> *Sent:* Thursday, December 16, 2010 12:42 PM
>
> *To:* dev@synapse.apache.org
> *Subject:* Re: [VOTE] Release Synapse-2.0.0 (Take2)
>
>
>
> Hi Eric,
>
>
>
> Going through your documentation and trying to document/fix them... here
> are my comments/explanations. :-)
>
> On Fri, Dec 10, 2010 at 1:11 PM, Hubert, Eric <Er...@foxmobile.com>
> wrote:
>
> I found quite a bit of time to have a more detailed look at the
> incompatible changes and start with an upgrade process - comments inline.
>   ------------------------------
>
> *From:* Hubert, Eric [mailto:Eric.Hubert@foxmobile.com]
> *Sent:* Thursday, December 09, 2010 12:40 PM
>
>
> *To:* dev@synapse.apache.org
> *Subject:* RE: [VOTE] Release Synapse-2.0.0 (Take2)
>
>
>
> Here is a list of incompatibilities immediately found. Some are only from
> unit tests – not all will be considered as public API. To solve some tasks
> access was needed for different reasons…
>
> Somehow sorted by importance:
>
>
>
> The type XYZ must implement the inherited abstract method
> AbstractMediatorFactory.createSpecificMediator(OMElement, Properties)
>
>
>
> This has been documented on the upgrading guide
>
>
>
>   The type XYZ must implement the inherited abstract method
> SynapseArtifact.getDescription()
>
> The type XYZ must implement the inherited abstract method
> SynapseArtifact.setDescription(String)
>
>
>
> From where did you get these errors, you cannot get these errors if you are
> extending from the abstract classes, since it contains these
> implementations, and the description is automatically available for the
> programmer through the abstract class. This is one of the main ideas of the
> above API refactoring too.
>
>
>
>   Cannot override the final method from AbstractMediatorSerializer
>
>
>
> This is caused by the serializeSpecificMediator introduction just as in the
> factory, and you should use that instead of the final method. And yes this
> has been documented too.
>
>
>
>   The field AbstractMediatorFactory.log is not visible
>
>
>
> This seems to be mistakenly changed by Hiranya to package private from
> protected, I have reverted it to be protected so that you can use it now,
> sorry for the inconveniences.
>
>
>
>   The method createMediator(OMElement, Properties) in the type
> AbstractMediatorFactory is not applicable for the arguments (OMElement)
>
> The method createMediator(OMElement, Properties) in the type
> MediatorFactory is not applicable for the arguments (OMElement)
>
> The method createMediator(OMElement) of type XYZ must override or implement
> a supertype method
>
>
>
> The above 3 cases has already been taken into account in the documentation
> of AbstractMediatorFactory/Serializer change.
>
>
>
>
>
> All of the above is what I assume could/should be considered public API and
> all of the changes required to make custom mediator code compile again are
> trivial and quickly done. I did this for a couple of mediators.
>
> I have still one question: What has been the reason to add the Properties
> to the createSpecificMediator method in the AbstractMediatorFactory? I tried
> to answer this question myself and looked for usage of the properties in the
> source. I only checked a couple of implementation, but could nowhere find a
> use. Everywhere this parameter was ignored in the Factory implementations
> and callers passed in an empty Properties-Map.
>
>
>
> This is to resolve the coupling between the server startup with Axis2
> integration and Synapse configuration building. Those are two concerns and
> earlier the ServerConfigurationInformation class was a singleton and the
> rest of the synapse core code has mis used this singleton behavior to get
> the access to information like SYNAPSE_HOME and RESOLVE_ROOT. These
> information really are a set of arguments that needs to be passed into the
> configuration building framework, but I thought ahead a little bit about
> what if we have more parameters in the future, and introduced a generic
> properties map.
>
>
>
> See the Axis2SynapseController#createSynapseConfiguration method to see how
> we pass in these parameters to the configuration building framework removing
> the coupling.
>
>
>
>
>
>
>
> The method getMediator(OMElement, Properties) in the type
> MediatorFactoryFinder is not applicable for the arguments (OMElement)
>
> The method getMediator(OMElement, Properties) in the type
> MediatorFactoryFinder is not applicable for the arguments (OMElement)
>
>
>
> The method getInstance() is undefined for the type ServerManager
>
> DataSourceInformation cannot be resolved
>
> DataSourceRegistrar cannot be resolved
>
> JNDIBasedDataSourceRegistry cannot be resolved
>
> MiscellaneousUtil cannot be resolved
>
> RMIRegistryController
>
> The import org.apache.synapse.util.datasource
>
> The import org.apache.synapse.util.MiscellaneousUtil
>
> The import org.apache.synapse.util.RMIRegistryController
>
>
>
> These are documented generally under the API changes section.
>
>
>
> I am yet to carefully go through your other suggestions on the API changes,
> let me get back to you on that ASAP.
>
>
>
> Thanks,
>
> Ruwan
>
>
>
>
>
> All the above seems to be stuff which had never been designed for external
> usage. It should not be hard to figure out how to properly replace it. All
> but one compile errors are from test/mock code used for verification of
> correctness of mediator implementations (including factories/serializers).
>
>
>
> If you guys are not in hurry tomorrow I would like to:
>
> -       fix the remaining issues in our custom code
>
> -       use a fixed version of the migration tool to migrate a large
> configuration file (for my initial test I used something really small)
>
> -       do some runtime mediation tests
>
>
>
> Unfortunately I will not find time today.
>
>
>
> Regards,
>
>    Eric
>
>
>
>
>   ------------------------------
>
> *From:* Hubert, Eric [mailto:Eric.Hubert@foxmobile.com]
> *Sent:* Thursday, December 09, 2010 11:44 AM
> *To:* dev@synapse.apache.org
> *Subject:* RE: [VOTE] Release Synapse-2.0.0 (Take2)
>
>
>
> 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.
>
>
>
>   - 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.
>
>
>
> 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…
>
>
>
>   - 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.
>     <code xmlns:tns="http://www.w3.org/2003/05/soap-envelope"
> value="tns:Receiver"/> à <syn:code 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…
>
>
>
>   - 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…
>
>
>
>
>
> 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 section in the documentation right from the front
> page. May under what’s new or so…
>
>
>
> 4) Usage of custom mediators / Site Documentation “Upgrading”
>
> - In the docu I could not quickly locate a document summarizing the steps
> which need to be done to upgrade custom mediators according to API changes
> (I received some AbstractMethodError). I did not check the mediator sources
> against the current libraries to find out what is no longer compiling….
> Anyway a quick summary of API changes would be nice. As long as I haven’t
> check the points which do not compile I cannot say for sure, whether those
> problems are due to the fact that public methods not considered to be part
> of the public API have been used on our end (which is not unlikely at all).
>
>
>
> I agree, will try to add more on the API changes, at least for the mediator
> API.
>
>  Great.
>
>
>
>
>   ------------------------------
>
> *From:* Ruwan Linton [mailto:ruwan.linton@gmail.com]
> *Sent:* Thursday, December 09, 2010 7:04 AM
>
>
> *To:* dev@synapse.apache.org
> *Subject:* Re: [VOTE] Release Synapse-2.0.0 (Take2)
>
>
>
> So the Sandesha module can be easily removed if you are not doing any
> reliable messaging stuff. Just need to delete the file from the
> repository/modules directory. I would even remove this error message from
> the custom build of Sandesha2 as we any way seem to go for the 3rd round of
> voting. :-)
>
>
>
> Eric, I would like to wait for your feedback to do the 3rd RC. So take your
> time, but report us any critical issue as soon as you get to them. May not
> need to be the complete list, you can report them one by one as and when you
> find those, so that we can fix them if needs to be and be ready for your
> next round of the feedback. BTW: must say that we really appreciate your
> feedback.
>
>
>
> Thanks,
>
> Ruwan
>
>
>
>
> --
> 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: ruwan@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: ruwan@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: ruwan@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)

Posted by "Hubert, Eric" <Er...@foxmobile.com>.
Hi Ruwan,

there is not much to worry about. I have been able to rather easily fix all of those issues. I have been only a bit concerned about users which are not familiar with the Synapse code at all.

As you said, the errors regarding SynapseArtifact.getDescription() came from custom mediator implementations directly implementing the mediator interface without using the abstract base implementation. I do not know how often people might have done this. For some of our mediators there was no need to extend from the base implementation as it offered nothing meaningful for those cases. I guess with Synapse 2.0 users are now strongly encouraged to extend the base implementation. Otherwise they have to implement some aspects they do not like to care about at all.

Thanks for the explanation regarding the properties usage. Now it’s purpose is clear. Just from looking at the API and Unit-Tests (which is mostly a good start to understand something) I wasn’t able to get it.

Thanks,
   Eric


________________________________
From: Ruwan Linton [mailto:ruwan.linton@gmail.com]
Sent: Thursday, December 16, 2010 12:42 PM
To: dev@synapse.apache.org
Subject: Re: [VOTE] Release Synapse-2.0.0 (Take2)

Hi Eric,

Going through your documentation and trying to document/fix them... here are my comments/explanations. :-)
On Fri, Dec 10, 2010 at 1:11 PM, Hubert, Eric <Er...@foxmobile.com>> wrote:
I found quite a bit of time to have a more detailed look at the incompatible changes and start with an upgrade process - comments inline.
________________________________
From: Hubert, Eric [mailto:Eric.Hubert@foxmobile.com<ma...@foxmobile.com>]
Sent: Thursday, December 09, 2010 12:40 PM

To: dev@synapse.apache.org<ma...@synapse.apache.org>
Subject: RE: [VOTE] Release Synapse-2.0.0 (Take2)

Here is a list of incompatibilities immediately found. Some are only from unit tests – not all will be considered as public API. To solve some tasks access was needed for different reasons…
Somehow sorted by importance:

The type XYZ must implement the inherited abstract method AbstractMediatorFactory.createSpecificMediator(OMElement, Properties)

This has been documented on the upgrading guide

The type XYZ must implement the inherited abstract method SynapseArtifact.getDescription()
The type XYZ must implement the inherited abstract method SynapseArtifact.setDescription(String)

From where did you get these errors, you cannot get these errors if you are extending from the abstract classes, since it contains these implementations, and the description is automatically available for the programmer through the abstract class. This is one of the main ideas of the above API refactoring too.

Cannot override the final method from AbstractMediatorSerializer

This is caused by the serializeSpecificMediator introduction just as in the factory, and you should use that instead of the final method. And yes this has been documented too.

The field AbstractMediatorFactory.log is not visible

This seems to be mistakenly changed by Hiranya to package private from protected, I have reverted it to be protected so that you can use it now, sorry for the inconveniences.

The method createMediator(OMElement, Properties) in the type AbstractMediatorFactory is not applicable for the arguments (OMElement)
The method createMediator(OMElement, Properties) in the type MediatorFactory is not applicable for the arguments (OMElement)
The method createMediator(OMElement) of type XYZ must override or implement a supertype method

The above 3 cases has already been taken into account in the documentation of AbstractMediatorFactory/Serializer change.


All of the above is what I assume could/should be considered public API and all of the changes required to make custom mediator code compile again are trivial and quickly done. I did this for a couple of mediators.
I have still one question: What has been the reason to add the Properties to the createSpecificMediator method in the AbstractMediatorFactory? I tried to answer this question myself and looked for usage of the properties in the source. I only checked a couple of implementation, but could nowhere find a use. Everywhere this parameter was ignored in the Factory implementations and callers passed in an empty Properties-Map.

This is to resolve the coupling between the server startup with Axis2 integration and Synapse configuration building. Those are two concerns and earlier the ServerConfigurationInformation class was a singleton and the rest of the synapse core code has mis used this singleton behavior to get the access to information like SYNAPSE_HOME and RESOLVE_ROOT. These information really are a set of arguments that needs to be passed into the configuration building framework, but I thought ahead a little bit about what if we have more parameters in the future, and introduced a generic properties map.

See the Axis2SynapseController#createSynapseConfiguration method to see how we pass in these parameters to the configuration building framework removing the coupling.



The method getMediator(OMElement, Properties) in the type MediatorFactoryFinder is not applicable for the arguments (OMElement)
The method getMediator(OMElement, Properties) in the type MediatorFactoryFinder is not applicable for the arguments (OMElement)

The method getInstance() is undefined for the type ServerManager
DataSourceInformation cannot be resolved
DataSourceRegistrar cannot be resolved
JNDIBasedDataSourceRegistry cannot be resolved
MiscellaneousUtil cannot be resolved
RMIRegistryController
The import org.apache.synapse.util.datasource
The import org.apache.synapse.util.MiscellaneousUtil
The import org.apache.synapse.util.RMIRegistryController

These are documented generally under the API changes section.

I am yet to carefully go through your other suggestions on the API changes, let me get back to you on that ASAP.

Thanks,
Ruwan


All the above seems to be stuff which had never been designed for external usage. It should not be hard to figure out how to properly replace it. All but one compile errors are from test/mock code used for verification of correctness of mediator implementations (including factories/serializers).

If you guys are not in hurry tomorrow I would like to:
-       fix the remaining issues in our custom code
-       use a fixed version of the migration tool to migrate a large configuration file (for my initial test I used something really small)
-       do some runtime mediation tests

Unfortunately I will not find time today.

Regards,
   Eric


________________________________
From: Hubert, Eric [mailto:Eric.Hubert@foxmobile.com<ma...@foxmobile.com>]
Sent: Thursday, December 09, 2010 11:44 AM
To: dev@synapse.apache.org<ma...@synapse.apache.org>
Subject: RE: [VOTE] Release Synapse-2.0.0 (Take2)

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.


- 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.



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…


- 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.
    <code xmlns:tns="http://www.w3.org/2003/05/soap-envelope" value="tns:Receiver"/> --> <syn:code 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…


- 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…




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 section in the documentation right from the front page. May under what’s new or so…



4) Usage of custom mediators / Site Documentation “Upgrading”

- In the docu I could not quickly locate a document summarizing the steps which need to be done to upgrade custom mediators according to API changes (I received some AbstractMethodError). I did not check the mediator sources against the current libraries to find out what is no longer compiling…. Anyway a quick summary of API changes would be nice. As long as I haven’t check the points which do not compile I cannot say for sure, whether those problems are due to the fact that public methods not considered to be part of the public API have been used on our end (which is not unlikely at all).

I agree, will try to add more on the API changes, at least for the mediator API.
 Great.




________________________________
From: Ruwan Linton [mailto:ruwan.linton@gmail.com<ma...@gmail.com>]
Sent: Thursday, December 09, 2010 7:04 AM

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

So the Sandesha module can be easily removed if you are not doing any reliable messaging stuff. Just need to delete the file from the repository/modules directory. I would even remove this error message from the custom build of Sandesha2 as we any way seem to go for the 3rd round of voting. :-)

Eric, I would like to wait for your feedback to do the 3rd RC. So take your time, but report us any critical issue as soon as you get to them. May not need to be the complete list, you can report them one by one as and when you find those, so that we can fix them if needs to be and be ready for your next round of the feedback. BTW: must say that we really appreciate your feedback.

Thanks,
Ruwan



--
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: ruwan@wso2.com<ma...@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: ruwan@wso2.com<ma...@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)

Posted by Ruwan Linton <ru...@gmail.com>.
Hi Eric,

Going through your documentation and trying to document/fix them... here are
my comments/explanations. :-)

On Fri, Dec 10, 2010 at 1:11 PM, Hubert, Eric <Er...@foxmobile.com>wrote:

>  I found quite a bit of time to have a more detailed look at the
> incompatible changes and start with an upgrade process - comments inline.
>   ------------------------------
>
> *From:* Hubert, Eric [mailto:Eric.Hubert@foxmobile.com]
> *Sent:* Thursday, December 09, 2010 12:40 PM
>
> *To:* dev@synapse.apache.org
> *Subject:* RE: [VOTE] Release Synapse-2.0.0 (Take2)
>
>
>
> Here is a list of incompatibilities immediately found. Some are only from
> unit tests – not all will be considered as public API. To solve some tasks
> access was needed for different reasons…
>
> Somehow sorted by importance:
>
>
>
> The type XYZ must implement the inherited abstract method
> AbstractMediatorFactory.createSpecificMediator(OMElement, Properties)
>

This has been documented on the upgrading guide


> The type XYZ must implement the inherited abstract method
> SynapseArtifact.getDescription()
>
> The type XYZ must implement the inherited abstract method
> SynapseArtifact.setDescription(String)
>

>From where did you get these errors, you cannot get these errors if you are
extending from the abstract classes, since it contains these
implementations, and the description is automatically available for the
programmer through the abstract class. This is one of the main ideas of the
above API refactoring too.


> Cannot override the final method from AbstractMediatorSerializer
>

This is caused by the serializeSpecificMediator introduction just as in the
factory, and you should use that instead of the final method. And yes this
has been documented too.


> The field AbstractMediatorFactory.log is not visible
>

This seems to be mistakenly changed by Hiranya to package private from
protected, I have reverted it to be protected so that you can use it now,
sorry for the inconveniences.


> The method createMediator(OMElement, Properties) in the type
> AbstractMediatorFactory is not applicable for the arguments (OMElement)
>
> The method createMediator(OMElement, Properties) in the type
> MediatorFactory is not applicable for the arguments (OMElement)
>
> The method createMediator(OMElement) of type XYZ must override or implement
> a supertype method
>

The above 3 cases has already been taken into account in the documentation
of AbstractMediatorFactory/Serializer change.


>
>
> All of the above is what I assume could/should be considered public API and
> all of the changes required to make custom mediator code compile again are
> trivial and quickly done. I did this for a couple of mediators.
>
> I have still one question: What has been the reason to add the Properties
> to the createSpecificMediator method in the AbstractMediatorFactory? I tried
> to answer this question myself and looked for usage of the properties in the
> source. I only checked a couple of implementation, but could nowhere find a
> use. Everywhere this parameter was ignored in the Factory implementations
> and callers passed in an empty Properties-Map.
>

This is to resolve the coupling between the server startup with Axis2
integration and Synapse configuration building. Those are two concerns and
earlier the ServerConfigurationInformation class was a singleton and the
rest of the synapse core code has mis used this singleton behavior to get
the access to information like SYNAPSE_HOME and RESOLVE_ROOT. These
information really are a set of arguments that needs to be passed into the
configuration building framework, but I thought ahead a little bit about
what if we have more parameters in the future, and introduced a generic
properties map.

See the Axis2SynapseController#createSynapseConfiguration method to see how
we pass in these parameters to the configuration building framework removing
the coupling.


>
>
>
>
> The method getMediator(OMElement, Properties) in the type
> MediatorFactoryFinder is not applicable for the arguments (OMElement)
>
> The method getMediator(OMElement, Properties) in the type
> MediatorFactoryFinder is not applicable for the arguments (OMElement)
>
>
>
> The method getInstance() is undefined for the type ServerManager
>
> DataSourceInformation cannot be resolved
>
> DataSourceRegistrar cannot be resolved
>
> JNDIBasedDataSourceRegistry cannot be resolved
>
> MiscellaneousUtil cannot be resolved
>
> RMIRegistryController
>
> The import org.apache.synapse.util.datasource
>
> The import org.apache.synapse.util.MiscellaneousUtil
>
> The import org.apache.synapse.util.RMIRegistryController
>

These are documented generally under the API changes section.

I am yet to carefully go through your other suggestions on the API changes,
let me get back to you on that ASAP.

Thanks,
Ruwan


>
>
> All the above seems to be stuff which had never been designed for external
> usage. It should not be hard to figure out how to properly replace it. All
> but one compile errors are from test/mock code used for verification of
> correctness of mediator implementations (including factories/serializers).
>
>
>
> If you guys are not in hurry tomorrow I would like to:
>
> -       fix the remaining issues in our custom code
>
> -       use a fixed version of the migration tool to migrate a large
> configuration file (for my initial test I used something really small)
>
> -       do some runtime mediation tests
>
>
>
> Unfortunately I will not find time today.
>
>
>
> Regards,
>
>    Eric
>
>
>
>
>   ------------------------------
>
> *From:* Hubert, Eric [mailto:Eric.Hubert@foxmobile.com]
> *Sent:* Thursday, December 09, 2010 11:44 AM
> *To:* dev@synapse.apache.org
> *Subject:* RE: [VOTE] Release Synapse-2.0.0 (Take2)
>
>
>
> 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.
>
>
>
>   - 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.
>
>
>
> 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…
>
>
>
>   - 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.
>     <code xmlns:tns="http://www.w3.org/2003/05/soap-envelope"
> value="tns:Receiver"/> à <syn:code 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…
>
>
>
>   - 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…
>
>
>
>
>
> 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 section in the documentation right from the front
> page. May under what’s new or so…
>
>
>
> 4) Usage of custom mediators / Site Documentation “Upgrading”
>
> - In the docu I could not quickly locate a document summarizing the steps
> which need to be done to upgrade custom mediators according to API changes
> (I received some AbstractMethodError). I did not check the mediator sources
> against the current libraries to find out what is no longer compiling….
> Anyway a quick summary of API changes would be nice. As long as I haven’t
> check the points which do not compile I cannot say for sure, whether those
> problems are due to the fact that public methods not considered to be part
> of the public API have been used on our end (which is not unlikely at all).
>
>
>
> I agree, will try to add more on the API changes, at least for the mediator
> API.
>
>  Great.
>
>
>
>
>   ------------------------------
>
> *From:* Ruwan Linton [mailto:ruwan.linton@gmail.com]
> *Sent:* Thursday, December 09, 2010 7:04 AM
>
>
> *To:* dev@synapse.apache.org
> *Subject:* Re: [VOTE] Release Synapse-2.0.0 (Take2)
>
>
>
> So the Sandesha module can be easily removed if you are not doing any
> reliable messaging stuff. Just need to delete the file from the
> repository/modules directory. I would even remove this error message from
> the custom build of Sandesha2 as we any way seem to go for the 3rd round of
> voting. :-)
>
>
>
> Eric, I would like to wait for your feedback to do the 3rd RC. So take your
> time, but report us any critical issue as soon as you get to them. May not
> need to be the complete list, you can report them one by one as and when you
> find those, so that we can fix them if needs to be and be ready for your
> next round of the feedback. BTW: must say that we really appreciate your
> feedback.
>
>
>
> Thanks,
>
> Ruwan
>
>
>
>
> --
> 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: ruwan@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: ruwan@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)

Posted by "Hubert, Eric" <Er...@foxmobile.com>.
I found quite a bit of time to have a more detailed look at the incompatible changes and start with an upgrade process - comments inline.
________________________________
From: Hubert, Eric [mailto:Eric.Hubert@foxmobile.com]
Sent: Thursday, December 09, 2010 12:40 PM
To: dev@synapse.apache.org
Subject: RE: [VOTE] Release Synapse-2.0.0 (Take2)

Here is a list of incompatibilities immediately found. Some are only from unit tests - not all will be considered as public API. To solve some tasks access was needed for different reasons...
Somehow sorted by importance:

The type XYZ must implement the inherited abstract method AbstractMediatorFactory.createSpecificMediator(OMElement, Properties)
The type XYZ must implement the inherited abstract method SynapseArtifact.getDescription()
The type XYZ must implement the inherited abstract method SynapseArtifact.setDescription(String)
Cannot override the final method from AbstractMediatorSerializer
The field AbstractMediatorFactory.log is not visible
The method createMediator(OMElement, Properties) in the type AbstractMediatorFactory is not applicable for the arguments (OMElement)
The method createMediator(OMElement, Properties) in the type MediatorFactory is not applicable for the arguments (OMElement)
The method createMediator(OMElement) of type XYZ must override or implement a supertype method

All of the above is what I assume could/should be considered public API and all of the changes required to make custom mediator code compile again are trivial and quickly done. I did this for a couple of mediators.
I have still one question: What has been the reason to add the Properties to the createSpecificMediator method in the AbstractMediatorFactory? I tried to answer this question myself and looked for usage of the properties in the source. I only checked a couple of implementation, but could nowhere find a use. Everywhere this parameter was ignored in the Factory implementations and callers passed in an empty Properties-Map.


The method getMediator(OMElement, Properties) in the type MediatorFactoryFinder is not applicable for the arguments (OMElement)
The method getMediator(OMElement, Properties) in the type MediatorFactoryFinder is not applicable for the arguments (OMElement)

The method getInstance() is undefined for the type ServerManager
DataSourceInformation cannot be resolved
DataSourceRegistrar cannot be resolved
JNDIBasedDataSourceRegistry cannot be resolved
MiscellaneousUtil cannot be resolved
RMIRegistryController
The import org.apache.synapse.util.datasource
The import org.apache.synapse.util.MiscellaneousUtil
The import org.apache.synapse.util.RMIRegistryController

All the above seems to be stuff which had never been designed for external usage. It should not be hard to figure out how to properly replace it. All but one compile errors are from test/mock code used for verification of correctness of mediator implementations (including factories/serializers).

If you guys are not in hurry tomorrow I would like to:
-       fix the remaining issues in our custom code
-       use a fixed version of the migration tool to migrate a large configuration file (for my initial test I used something really small)
-       do some runtime mediation tests

Unfortunately I will not find time today.

Regards,
   Eric


________________________________
From: Hubert, Eric [mailto:Eric.Hubert@foxmobile.com]
Sent: Thursday, December 09, 2010 11:44 AM
To: dev@synapse.apache.org
Subject: RE: [VOTE] Release Synapse-2.0.0 (Take2)

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.


- 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.



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...


- 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.
    <code xmlns:tns="http://www.w3.org/2003/05/soap-envelope" value="tns:Receiver"/> --> <syn:code 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...


- 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...




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 section in the documentation right from the front page. May under what's new or so...



4) Usage of custom mediators / Site Documentation "Upgrading"

- In the docu I could not quickly locate a document summarizing the steps which need to be done to upgrade custom mediators according to API changes (I received some AbstractMethodError). I did not check the mediator sources against the current libraries to find out what is no longer compiling.... Anyway a quick summary of API changes would be nice. As long as I haven't check the points which do not compile I cannot say for sure, whether those problems are due to the fact that public methods not considered to be part of the public API have been used on our end (which is not unlikely at all).

I agree, will try to add more on the API changes, at least for the mediator API.
 Great.




________________________________
From: Ruwan Linton [mailto:ruwan.linton@gmail.com<ma...@gmail.com>]
Sent: Thursday, December 09, 2010 7:04 AM

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

So the Sandesha module can be easily removed if you are not doing any reliable messaging stuff. Just need to delete the file from the repository/modules directory. I would even remove this error message from the custom build of Sandesha2 as we any way seem to go for the 3rd round of voting. :-)

Eric, I would like to wait for your feedback to do the 3rd RC. So take your time, but report us any critical issue as soon as you get to them. May not need to be the complete list, you can report them one by one as and when you find those, so that we can fix them if needs to be and be ready for your next round of the feedback. BTW: must say that we really appreciate your feedback.

Thanks,
Ruwan



--
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: ruwan@wso2.com<ma...@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)

Posted by "Hubert, Eric" <Er...@foxmobile.com>.
Here is a list of incompatibilities immediately found. Some are only from unit tests – not all will be considered as public API. To solve some tasks access was needed for different reasons…
Somehow sorted by importance:

The type XYZ must implement the inherited abstract method AbstractMediatorFactory.createSpecificMediator(OMElement, Properties)
The type XYZ must implement the inherited abstract method SynapseArtifact.getDescription()
The type XYZ must implement the inherited abstract method SynapseArtifact.setDescription(String)
Cannot override the final method from AbstractMediatorSerializer
The field AbstractMediatorFactory.log is not visible
The method createMediator(OMElement, Properties) in the type AbstractMediatorFactory is not applicable for the arguments (OMElement)
The method createMediator(OMElement, Properties) in the type MediatorFactory is not applicable for the arguments (OMElement)
The method createMediator(OMElement) of type XYZ must override or implement a supertype method


The method getMediator(OMElement, Properties) in the type MediatorFactoryFinder is not applicable for the arguments (OMElement)
The method getMediator(OMElement, Properties) in the type MediatorFactoryFinder is not applicable for the arguments (OMElement)
The method getInstance() is undefined for the type ServerManager
DataSourceInformation cannot be resolved
DataSourceRegistrar cannot be resolved
JNDIBasedDataSourceRegistry cannot be resolved
MiscellaneousUtil cannot be resolved
RMIRegistryController
The import org.apache.synapse.util.datasource
The import org.apache.synapse.util.MiscellaneousUtil
The import org.apache.synapse.util.RMIRegistryController

Maybe this helps for the documentation task… Others of course may find different incompatibilities. This is only taken from a very few custom mediators.
I would not consider it takes long to do the upgrade. Anyway I have currently not much time to try this out and prove it. Maybe later today, but no promise…
In any case one has to tell the user that no existing mediator will work without a few tweaks…

Regards,
   Eric


________________________________
From: Hubert, Eric [mailto:Eric.Hubert@foxmobile.com]
Sent: Thursday, December 09, 2010 11:44 AM
To: dev@synapse.apache.org
Subject: RE: [VOTE] Release Synapse-2.0.0 (Take2)

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.


- 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.



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…


- 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.
    <code xmlns:tns="http://www.w3.org/2003/05/soap-envelope" value="tns:Receiver"/> --> <syn:code 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…


- 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…




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 section in the documentation right from the front page. May under what’s new or so…



4) Usage of custom mediators / Site Documentation “Upgrading”

- In the docu I could not quickly locate a document summarizing the steps which need to be done to upgrade custom mediators according to API changes (I received some AbstractMethodError). I did not check the mediator sources against the current libraries to find out what is no longer compiling…. Anyway a quick summary of API changes would be nice. As long as I haven’t check the points which do not compile I cannot say for sure, whether those problems are due to the fact that public methods not considered to be part of the public API have been used on our end (which is not unlikely at all).

I agree, will try to add more on the API changes, at least for the mediator API.
 Great.




________________________________
From: Ruwan Linton [mailto:ruwan.linton@gmail.com<ma...@gmail.com>]
Sent: Thursday, December 09, 2010 7:04 AM

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

So the Sandesha module can be easily removed if you are not doing any reliable messaging stuff. Just need to delete the file from the repository/modules directory. I would even remove this error message from the custom build of Sandesha2 as we any way seem to go for the 3rd round of voting. :-)

Eric, I would like to wait for your feedback to do the 3rd RC. So take your time, but report us any critical issue as soon as you get to them. May not need to be the complete list, you can report them one by one as and when you find those, so that we can fix them if needs to be and be ready for your next round of the feedback. BTW: must say that we really appreciate your feedback.

Thanks,
Ruwan



--
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: ruwan@wso2.com<ma...@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)

Posted by "Hubert, Eric" <Er...@foxmobile.com>.
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.


- 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.



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…


- 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.
    <code xmlns:tns="http://www.w3.org/2003/05/soap-envelope" value="tns:Receiver"/> --> <syn:code 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…


- 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…




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 section in the documentation right from the front page. May under what’s new or so…



4) Usage of custom mediators / Site Documentation “Upgrading”

- In the docu I could not quickly locate a document summarizing the steps which need to be done to upgrade custom mediators according to API changes (I received some AbstractMethodError). I did not check the mediator sources against the current libraries to find out what is no longer compiling…. Anyway a quick summary of API changes would be nice. As long as I haven’t check the points which do not compile I cannot say for sure, whether those problems are due to the fact that public methods not considered to be part of the public API have been used on our end (which is not unlikely at all).

I agree, will try to add more on the API changes, at least for the mediator API.
 Great.




________________________________
From: Ruwan Linton [mailto:ruwan.linton@gmail.com<ma...@gmail.com>]
Sent: Thursday, December 09, 2010 7:04 AM

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

So the Sandesha module can be easily removed if you are not doing any reliable messaging stuff. Just need to delete the file from the repository/modules directory. I would even remove this error message from the custom build of Sandesha2 as we any way seem to go for the 3rd round of voting. :-)

Eric, I would like to wait for your feedback to do the 3rd RC. So take your time, but report us any critical issue as soon as you get to them. May not need to be the complete list, you can report them one by one as and when you find those, so that we can fix them if needs to be and be ready for your next round of the feedback. BTW: must say that we really appreciate your feedback.

Thanks,
Ruwan



--
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: ruwan@wso2.com<ma...@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)

Posted by Ruwan Linton <ru...@gmail.com>.
HI Eric,

First of all thanks a lot. See my comments inline.

On Thu, Dec 9, 2010 at 2:46 PM, Hubert, Eric <Er...@foxmobile.com>wrote:

>   Hi all,
>
>
>
> here are my first test observations – let’s state it like that. So far I
> think it is best to simply bring them up to the list, so we can sort out
> which of those are to be considered expected behaviour and are somewhere
> documented and which are issues which should be fixed according to their
> priority (which also needs to be determined).
>

+1


>
>
> 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.


> - 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. :-(


> - 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?


>
>
> 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.


> - 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.
>     <code xmlns:tns="http://www.w3.org/2003/05/soap-envelope"
> value="tns:Receiver"/> à <syn:code value="tns:Receiver" /> resulting in
> startup issues
>

This we need to fix for this release, I will work on this.


> - 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.


>
>
> 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


>
>
> 4) Usage of custom mediators / Site Documentation “Upgrading”
>
> - In the docu I could not quickly locate a document summarizing the steps
> which need to be done to upgrade custom mediators according to API changes
> (I received some AbstractMethodError). I did not check the mediator sources
> against the current libraries to find out what is no longer compiling….
> Anyway a quick summary of API changes would be nice. As long as I haven’t
> check the points which do not compile I cannot say for sure, whether those
> problems are due to the fact that public methods not considered to be part
> of the public API have been used on our end (which is not unlikely at all).
>

I agree, will try to add more on the API changes, at least for the mediator
API.


>
>
> Once I find the time, I will move on with my tests (probably this late
> evening, CET)…
>

+1

Ruwan


>
>
> Hope the feedback is still of help…
>
>
>
> Regards,
>
>    Eric
>
>
>
>
>   ------------------------------
>
> *From:* Ruwan Linton [mailto:ruwan.linton@gmail.com]
> *Sent:* Thursday, December 09, 2010 7:04 AM
>
> *To:* dev@synapse.apache.org
> *Subject:* Re: [VOTE] Release Synapse-2.0.0 (Take2)
>
>
>
> So the Sandesha module can be easily removed if you are not doing any
> reliable messaging stuff. Just need to delete the file from the
> repository/modules directory. I would even remove this error message from
> the custom build of Sandesha2 as we any way seem to go for the 3rd round of
> voting. :-)
>
>
>
> Eric, I would like to wait for your feedback to do the 3rd RC. So take your
> time, but report us any critical issue as soon as you get to them. May not
> need to be the complete list, you can report them one by one as and when you
> find those, so that we can fix them if needs to be and be ready for your
> next round of the feedback. BTW: must say that we really appreciate your
> feedback.
>
>
>
> Thanks,
>
> Ruwan
>



-- 
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: ruwan@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)

Posted by "Hubert, Eric" <Er...@foxmobile.com>.
Hi all,



here are my first test observations – let’s state it like that. So far I think it is best to simply bring them up to the list, so we can sort out which of those are to be considered expected behaviour and are somewhere documented and which are issues which should be fixed according to their priority (which also needs to be determined).



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

- Synapse does not startup due to a problem in the config (e.g. missing registry implementation class on the classpath)

- 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



2) Migration Tool

- executing the migration tool expects a config in repository/conf (former config location)

- 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

- migration tool mistakenly removes namespaces (destroying the config), e.g.
    <code xmlns:tns="http://www.w3.org/2003/05/soap-envelope" value="tns:Receiver"/> --> <syn:code value="tns:Receiver" /> resulting in startup issues

- migration tool removes indentation at the beginning of each xml element



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



4) Usage of custom mediators / Site Documentation “Upgrading”

- In the docu I could not quickly locate a document summarizing the steps which need to be done to upgrade custom mediators according to API changes (I received some AbstractMethodError). I did not check the mediator sources against the current libraries to find out what is no longer compiling…. Anyway a quick summary of API changes would be nice. As long as I haven’t check the points which do not compile I cannot say for sure, whether those problems are due to the fact that public methods not considered to be part of the public API have been used on our end (which is not unlikely at all).



Once I find the time, I will move on with my tests (probably this late evening, CET)…



Hope the feedback is still of help…



Regards,

   Eric





________________________________
From: Ruwan Linton [mailto:ruwan.linton@gmail.com]
Sent: Thursday, December 09, 2010 7:04 AM
To: dev@synapse.apache.org
Subject: Re: [VOTE] Release Synapse-2.0.0 (Take2)

So the Sandesha module can be easily removed if you are not doing any reliable messaging stuff. Just need to delete the file from the repository/modules directory. I would even remove this error message from the custom build of Sandesha2 as we any way seem to go for the 3rd round of voting. :-)

Eric, I would like to wait for your feedback to do the 3rd RC. So take your time, but report us any critical issue as soon as you get to them. May not need to be the complete list, you can report them one by one as and when you find those, so that we can fix them if needs to be and be ready for your next round of the feedback. BTW: must say that we really appreciate your feedback.

Thanks,
Ruwan

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

Posted by Ruwan Linton <ru...@gmail.com>.
So the Sandesha module can be easily removed if you are not doing any
reliable messaging stuff. Just need to delete the file from the
repository/modules directory. I would even remove this error message from
the custom build of Sandesha2 as we any way seem to go for the 3rd round of
voting. :-)

Eric, I would like to wait for your feedback to do the 3rd RC. So take your
time, but report us any critical issue as soon as you get to them. May not
need to be the complete list, you can report them one by one as and when you
find those, so that we can fix them if needs to be and be ready for your
next round of the feedback. BTW: must say that we really appreciate your
feedback.

Thanks,
Ruwan

On Thu, Dec 9, 2010 at 5:24 AM, Hiranya Jayathilaka <hi...@gmail.com>wrote:

> On Thu, Dec 9, 2010 at 5:12 AM, Hubert, Eric <Er...@foxmobile.com>
> wrote:
> >> > Sorry, but I'm not yet ready to post something concrete, except for
> one
> >> obvious and non critical observation. I find it quite strange that a
> stock
> >> installation starts up with a log message on ERROR level:
> >> > ERROR SandeshaModule Could not load module policies. Using default
> >> values.
> >>
> >> Well this is very much a Sandesha problem. But since we are on a
> >> custom Sandesha branch we might be able to fix this.
> > Should the custom build of the Sandesha module be used by default at all
> or is this some optional functionality a user should configure, if he needs
> it?
>
> It is needed only if you are doing any RM scenarios
>
> Thanks,
> Hiranya
>
> >
> > Regards,
> >   Eric
> >
>
>
>
> --
> Hiranya Jayathilaka
> Senior Software Engineer;
> WSO2 Inc.;  http://wso2.org
> E-mail: hiranya@wso2.com;  Mobile: +94 77 633 3491
> Blog: http://techfeast-hiranya.blogspot.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
> For additional commands, e-mail: dev-help@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: ruwan@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)

Posted by Hiranya Jayathilaka <hi...@gmail.com>.
On Thu, Dec 9, 2010 at 5:12 AM, Hubert, Eric <Er...@foxmobile.com> wrote:
>> > Sorry, but I'm not yet ready to post something concrete, except for one
>> obvious and non critical observation. I find it quite strange that a stock
>> installation starts up with a log message on ERROR level:
>> > ERROR SandeshaModule Could not load module policies. Using default
>> values.
>>
>> Well this is very much a Sandesha problem. But since we are on a
>> custom Sandesha branch we might be able to fix this.
> Should the custom build of the Sandesha module be used by default at all or is this some optional functionality a user should configure, if he needs it?

It is needed only if you are doing any RM scenarios

Thanks,
Hiranya

>
> Regards,
>   Eric
>



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

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

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

Posted by Ruwan Linton <ru...@gmail.com>.
I've changed that log to WARN, as it is not so good to get rid of this log,
obviously it is not ERROR.

Thanks,
Ruwan

On Thu, Dec 9, 2010 at 5:12 AM, Hubert, Eric <Er...@foxmobile.com>wrote:

> > > Sorry, but I'm not yet ready to post something concrete, except for one
> > obvious and non critical observation. I find it quite strange that a
> stock
> > installation starts up with a log message on ERROR level:
> > > ERROR SandeshaModule Could not load module policies. Using default
> > values.
> >
> > Well this is very much a Sandesha problem. But since we are on a
> > custom Sandesha branch we might be able to fix this.
> Should the custom build of the Sandesha module be used by default at all or
> is this some optional functionality a user should configure, if he needs it?
>
> Regards,
>    Eric
>



-- 
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: ruwan@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)

Posted by "Hubert, Eric" <Er...@foxmobile.com>.
> > Sorry, but I'm not yet ready to post something concrete, except for one
> obvious and non critical observation. I find it quite strange that a stock
> installation starts up with a log message on ERROR level:
> > ERROR SandeshaModule Could not load module policies. Using default
> values.
> 
> Well this is very much a Sandesha problem. But since we are on a
> custom Sandesha branch we might be able to fix this.
Should the custom build of the Sandesha module be used by default at all or is this some optional functionality a user should configure, if he needs it?

Regards,
   Eric

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

Posted by Hiranya Jayathilaka <hi...@gmail.com>.
On Thu, Dec 9, 2010 at 4:55 AM, Hubert, Eric <Er...@foxmobile.com> wrote:
> Unfortunately I will also have to throw in a couple of issues.
> So far I'm still collecting them... Not sure when I will have reached the end as I'm currently somehow in a process of finding a problem, resolving it, moving on, finding next problem, resolving it... Hope to break out of this loop soon and find some time tomorrow to post a summary upon which you can decide whether those issues shall hold up the release process or be fixed afterwards.
> Of course I need to mention that I'm not starting from scratch, but rather test the migration path...
>
> Sorry, but I'm not yet ready to post something concrete, except for one obvious and non critical observation. I find it quite strange that a stock installation starts up with a log message on ERROR level:
> ERROR SandeshaModule Could not load module policies. Using default values.

Well this is very much a Sandesha problem. But since we are on a
custom Sandesha branch we might be able to fix this.

Thanks,
Hiranya

>
> To me this reads more like a warning...
>
> Regards,
>   Eric
>
>> -----Original Message-----
>> From: Hiranya Jayathilaka [mailto:hiranya911@gmail.com]
>> Sent: Wednesday, December 08, 2010 8:14 PM
>> To: dev@synapse.apache.org
>> Subject: Re: [VOTE] Release Synapse-2.0.0 (Take2)
>>
>> 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 <ru...@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: ruwan@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: hiranya@wso2.com;  Mobile: +94 77 633 3491
>> Blog: http://techfeast-hiranya.blogspot.com
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
>> For additional commands, e-mail: dev-help@synapse.apache.org
>
>



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

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

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

Posted by "Hubert, Eric" <Er...@foxmobile.com>.
Unfortunately I will also have to throw in a couple of issues.
So far I'm still collecting them... Not sure when I will have reached the end as I'm currently somehow in a process of finding a problem, resolving it, moving on, finding next problem, resolving it... Hope to break out of this loop soon and find some time tomorrow to post a summary upon which you can decide whether those issues shall hold up the release process or be fixed afterwards. 
Of course I need to mention that I'm not starting from scratch, but rather test the migration path...

Sorry, but I'm not yet ready to post something concrete, except for one obvious and non critical observation. I find it quite strange that a stock installation starts up with a log message on ERROR level:
ERROR SandeshaModule Could not load module policies. Using default values.

To me this reads more like a warning... 

Regards,
   Eric

> -----Original Message-----
> From: Hiranya Jayathilaka [mailto:hiranya911@gmail.com]
> Sent: Wednesday, December 08, 2010 8:14 PM
> To: dev@synapse.apache.org
> Subject: Re: [VOTE] Release Synapse-2.0.0 (Take2)
> 
> 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 <ru...@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: ruwan@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: hiranya@wso2.com;  Mobile: +94 77 633 3491
> Blog: http://techfeast-hiranya.blogspot.com
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
> For additional commands, e-mail: dev-help@synapse.apache.org

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

Posted by Hiranya Jayathilaka <hi...@gmail.com>.
On Thu, Dec 9, 2010 at 3:38 PM, Ruwan Linton <ru...@gmail.com> wrote:
> 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 :-)

Looks good now

Thanks,
Hiranya

> Thanks,
> Ruwan
>
> On Thu, Dec 9, 2010 at 12:44 AM, Hiranya Jayathilaka <hi...@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 <ru...@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: ruwan@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: hiranya@wso2.com;  Mobile: +94 77 633 3491
>> Blog: http://techfeast-hiranya.blogspot.com
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
>> For additional commands, e-mail: dev-help@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: ruwan@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: hiranya@wso2.com;  Mobile: +94 77 633 3491
Blog: http://techfeast-hiranya.blogspot.com

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

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

Posted by Ruwan Linton <ru...@gmail.com>.
HI Eric,

On Wed, Dec 15, 2010 at 9:24 PM, Hubert, Eric <Er...@foxmobile.com>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.linton@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 <ru...@gmail.com>
> wrote:
>
> Hi Eric,
>
> On Sat, Dec 11, 2010 at 9:40 PM, Hubert, Eric <Er...@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.linton@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 <hi...@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 <ru...@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: ruwan@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: hiranya@wso2.com;  Mobile: +94 77 633 3491
> Blog: http://techfeast-hiranya.blogspot.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
> For additional commands, e-mail: dev-help@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: ruwan@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: ruwan@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: ruwan@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: ruwan@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)

Posted by "Hubert, Eric" <Er...@foxmobile.com>.
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.linton@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 <ru...@gmail.com>> wrote:
Hi Eric,
On Sat, Dec 11, 2010 at 9:40 PM, Hubert, Eric <Er...@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.linton@gmail.com<ma...@gmail.com>]
Sent: Thursday, December 09, 2010 11:08 AM

To: dev@synapse.apache.org<ma...@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 <hi...@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 <ru...@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: ruwan@wso2.com<ma...@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: hiranya@wso2.com<ma...@wso2.com>;  Mobile: +94 77 633 3491
Blog: http://techfeast-hiranya.blogspot.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org<ma...@synapse.apache.org>
For additional commands, e-mail: dev-help@synapse.apache.org<ma...@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: ruwan@wso2.com<ma...@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: ruwan@wso2.com<ma...@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: ruwan@wso2.com<ma...@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)

Posted by Ruwan Linton <ru...@gmail.com>.
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 <ru...@gmail.com>wrote:

> Hi Eric,
>
> On Sat, Dec 11, 2010 at 9:40 PM, Hubert, Eric <Er...@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.linton@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 <
>> hiranya911@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 <ru...@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: ruwan@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: hiranya@wso2.com;  Mobile: +94 77 633 3491
>> Blog: http://techfeast-hiranya.blogspot.com
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
>> For additional commands, e-mail: dev-help@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: ruwan@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: ruwan@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: ruwan@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)

Posted by Ruwan Linton <ru...@gmail.com>.
Thanks Indika.

Ruwan

On Mon, Dec 13, 2010 at 9:11 AM, indika kumara <in...@gmail.com>wrote:

> Done.
>
> Thanks,
>
> Indika
>
>
>
> On Sun, Dec 12, 2010 at 11:40 PM, Hubert, Eric <Er...@foxmobile.com>wrote:
>
>>  +1 to also do this before a final release!
>>   ------------------------------
>>
>> *From:* indika kumara [mailto:indika.kuma@gmail.com]
>> *Sent:* Sunday, December 12, 2010 6:34 PM
>>
>> *To:* dev@synapse.apache.org
>> *Subject:* Re: [VOTE] Release Synapse-2.0.0 (Take2)
>>
>>
>>
>> Hi Devs,
>>
>>
>> There is a statement in the
>> '/java/org/apache/synapse/securevault/SecretResolver.java' which I had added
>> for testing but forgot to remove.
>>
>> Statement :  log.info("Secret : " + encryptedPassword + " PlainText : " +
>> plainText);
>>
>> Shall I remove it ?
>>
>> Thanks,
>>
>> Indika
>>
>>
>


-- 
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: ruwan@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)

Posted by indika kumara <in...@gmail.com>.
Done.

Thanks,

Indika


On Sun, Dec 12, 2010 at 11:40 PM, Hubert, Eric <Er...@foxmobile.com>wrote:

>  +1 to also do this before a final release!
>   ------------------------------
>
> *From:* indika kumara [mailto:indika.kuma@gmail.com]
> *Sent:* Sunday, December 12, 2010 6:34 PM
>
> *To:* dev@synapse.apache.org
> *Subject:* Re: [VOTE] Release Synapse-2.0.0 (Take2)
>
>
>
> Hi Devs,
>
>
> There is a statement in the
> '/java/org/apache/synapse/securevault/SecretResolver.java' which I had added
> for testing but forgot to remove.
>
> Statement :  log.info("Secret : " + encryptedPassword + " PlainText : " +
> plainText);
>
> Shall I remove it ?
>
> Thanks,
>
> Indika
>

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

Posted by "Hubert, Eric" <Er...@foxmobile.com>.
+1 to also do this before a final release!
________________________________
From: indika kumara [mailto:indika.kuma@gmail.com]
Sent: Sunday, December 12, 2010 6:34 PM
To: dev@synapse.apache.org
Subject: Re: [VOTE] Release Synapse-2.0.0 (Take2)

Hi Devs,

There is a statement in the '/java/org/apache/synapse/securevault/SecretResolver.java' which I had added for testing but forgot to remove.

Statement :  log.info<http://log.info>("Secret : " + encryptedPassword + " PlainText : " + plainText);

Shall I remove it ?

Thanks,

Indika

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

Posted by indika kumara <in...@gmail.com>.
Hi Devs,

There is a statement in the
'/java/org/apache/synapse/securevault/SecretResolver.java' which I had added
for testing but forgot to remove.

Statement :  log.info("Secret : " + encryptedPassword + " PlainText : " +
plainText);

Shall I remove it ?

Thanks,

Indika

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

Posted by Ruwan Linton <ru...@gmail.com>.
Hi Charith,

Thanks a lot and it is not too late. :-) will get this path into the 2.0
branch.

Thanks,
Ruwan

On Sun, Dec 19, 2010 at 6:50 PM, Charith Wickramarachchi <
charith.dhanushka@gmail.com> wrote:

> Hi,
>
> I have attached the patches for fix this problem to [1]
> patch to fix the problem with the sites sample documentation can be found
> at[2] and changes to the sample 700 configuration file can be found at [3]
>
> [1]https://issues.apache.org/jira/browse/SYNAPSE-618
> [2]
> https://issues.apache.org/jira/secure/attachment/12466572/synapse-sample-700-site.diff
> [3]
> https://issues.apache.org/jira/secure/attachment/12466571/synapse-sample-700-xml.diff
>
>
> thanks,
> Charith
>
>
> On Sun, Dec 19, 2010 at 6:27 PM, Charith Wickramarachchi <
> charith.dhanushka@gmail.com> wrote:
>
>> Hi ,
>>
>> Sorry if i m too late. I ran few tests with the synapse samples and Found
>> a issue with the Sample 700 (Synapse Message Store).
>> The Sample documentation in [1] and synapse_sample_700.xml is bit diffrent
>> from the patch i attached in [2]
>> I think its because that patch was given for the new synapse xml schema
>> and getting it back to the old schema again caused this error.
>>
>> Current synapse_sample_700.xml does not work since global endpoint
>> definition and sequence definition is in side the main sequence.
>> I'm attaching the current version of the synapse_sample_700.xml with this
>> mail.
>>
>>
>>
>> [1]http://people.apache.org/~ruwan/synapse/2.0.0-RC2/site/<http://people.apache.org/%7Eruwan/synapse/2.0.0-RC2/site/>
>> [2]https://issues.apache.org/jira/secure/attachment/12452096/messagestore_patch_6.diff
>>
>> thanks,
>> Charith
>>
>>
>>
>>
>>
>>
>> On Fri, Dec 17, 2010 at 10:31 PM, Ruwan Linton <ru...@gmail.com>wrote:
>>
>>> Folks, sorry to let you know that the build is taking another day, as the
>>> source pack building issue is still there. Trying to figure out what was
>>> wrong, some times on a clean repo the build gets the same exception of a
>>> corrupted jar but is not really corrupted.
>>>
>>> Thanks,
>>> Ruwan
>>>
>>>
>>> On Thu, Dec 16, 2010 at 10:27 PM, Ruwan Linton <ru...@gmail.com>wrote:
>>>
>>>> Hi Eric,
>>>>
>>>> On Sun, Dec 12, 2010 at 5:22 PM, Hubert, Eric <
>>>> Eric.Hubert@foxmobile.com> wrote:
>>>>
>>>>>  Doing the mediator API related changes I asked myself whether
>>>>> concrete mediators like FaultMediator should really widen the visibility of
>>>>> AbstractMediatorFactory#createSpecificMediator. At least some of Synapse
>>>>> built-in mediators change the visibility from protected to public. I did not
>>>>> check all of them. I don’t think this is generally a good idea as to my
>>>>> understanding “users” of any MediatorFactory implementation should always
>>>>> only call createMediator (which internally delegates to
>>>>> createSpecificMediator). Otherwise functionality from the
>>>>> AbstractMediatorFactory might be mistakenly bypassed.
>>>>>
>>>>
>>>> Of course that is the design, some how by mistake they left as public
>>>> and now I have fixed that.
>>>>
>>>>
>>>>>
>>>>>
>>>>> Another small side-note AbstractMediatorFactory#createMediator’s
>>>>> JavaDoc has not been adjusted to the added parameter “Properties” which use
>>>>> is still unclear to me.
>>>>>
>>>>
>>>> Added properties param to the JavaDoc.
>>>>
>>>> Thanks,
>>>> Ruwan
>>>>
>>>>
>>>>>
>>>>>
>>>>> Apart from that I have positive feedback regarding my tests with simple
>>>>> mediation and usage of the nhttp transports. I could not spot any problem so
>>>>> far. I also did a couple of small load tests against one small instance
>>>>> reaching about 2500 requests per second and letting it run on that level for
>>>>> a few hours.
>>>>>
>>>>>
>>>>>
>>>>> Regards,
>>>>>
>>>>>    Eric
>>>>>
>>>>>
>>>>>   ------------------------------
>>>>>
>>>>> *From:* Ruwan Linton [mailto:ruwan.linton@gmail.com]
>>>>> *Sent:* Sunday, December 12, 2010 3:33 AM
>>>>>
>>>>> *To:* dev@synapse.apache.org
>>>>> *Subject:* Re: [VOTE] Release Synapse-2.0.0 (Take2)
>>>>>
>>>>>
>>>>>
>>>>> Hi Eric,
>>>>>
>>>>> On Sat, Dec 11, 2010 at 9:40 PM, Hubert, Eric <
>>>>> Eric.Hubert@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.linton@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 <
>>>>> hiranya911@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 <ru...@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/<http://people.apache.org/%7Eruwan/synapse/2.0.0-RC2/artifacts/>
>>>>> > The m2 repository is available at:
>>>>> > http://people.apache.org/~ruwan/synapse/2.0.0-RC2/m2_repo/<http://people.apache.org/%7Eruwan/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/<http://people.apache.org/%7Eruwan/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: ruwan@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: hiranya@wso2.com;  Mobile: +94 77 633 3491
>>>>> Blog: http://techfeast-hiranya.blogspot.com
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
>>>>> For additional commands, e-mail: dev-help@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: ruwan@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: ruwan@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: ruwan@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: ruwan@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
>>>
>>
>>
>>
>> --
>> Charith Dhanushka Wickramarachchi
>> http://charithwiki.blogspot.com/
>>
>>
>
>
> --
> Charith Dhanushka Wickramarachchi
> http://charithwiki.blogspot.com/
>
>


-- 
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: ruwan@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)

Posted by Charith Wickramarachchi <ch...@gmail.com>.
Hi,

I have attached the patches for fix this problem to [1]
patch to fix the problem with the sites sample documentation can be found
at[2] and changes to the sample 700 configuration file can be found at [3]

[1]https://issues.apache.org/jira/browse/SYNAPSE-618
[2]
https://issues.apache.org/jira/secure/attachment/12466572/synapse-sample-700-site.diff
[3]
https://issues.apache.org/jira/secure/attachment/12466571/synapse-sample-700-xml.diff


thanks,
Charith

On Sun, Dec 19, 2010 at 6:27 PM, Charith Wickramarachchi <
charith.dhanushka@gmail.com> wrote:

> Hi ,
>
> Sorry if i m too late. I ran few tests with the synapse samples and Found a
> issue with the Sample 700 (Synapse Message Store).
> The Sample documentation in [1] and synapse_sample_700.xml is bit diffrent
> from the patch i attached in [2]
> I think its because that patch was given for the new synapse xml schema and
> getting it back to the old schema again caused this error.
>
> Current synapse_sample_700.xml does not work since global endpoint
> definition and sequence definition is in side the main sequence.
> I'm attaching the current version of the synapse_sample_700.xml with this
> mail.
>
>
>
> [1]http://people.apache.org/~ruwan/synapse/2.0.0-RC2/site/<http://people.apache.org/%7Eruwan/synapse/2.0.0-RC2/site/>
> [2]https://issues.apache.org/jira/secure/attachment/12452096/messagestore_patch_6.diff
>
> thanks,
> Charith
>
>
>
>
>
>
> On Fri, Dec 17, 2010 at 10:31 PM, Ruwan Linton <ru...@gmail.com>wrote:
>
>> Folks, sorry to let you know that the build is taking another day, as the
>> source pack building issue is still there. Trying to figure out what was
>> wrong, some times on a clean repo the build gets the same exception of a
>> corrupted jar but is not really corrupted.
>>
>> Thanks,
>> Ruwan
>>
>>
>> On Thu, Dec 16, 2010 at 10:27 PM, Ruwan Linton <ru...@gmail.com>wrote:
>>
>>> Hi Eric,
>>>
>>> On Sun, Dec 12, 2010 at 5:22 PM, Hubert, Eric <Eric.Hubert@foxmobile.com
>>> > wrote:
>>>
>>>>  Doing the mediator API related changes I asked myself whether concrete
>>>> mediators like FaultMediator should really widen the visibility of
>>>> AbstractMediatorFactory#createSpecificMediator. At least some of Synapse
>>>> built-in mediators change the visibility from protected to public. I did not
>>>> check all of them. I don’t think this is generally a good idea as to my
>>>> understanding “users” of any MediatorFactory implementation should always
>>>> only call createMediator (which internally delegates to
>>>> createSpecificMediator). Otherwise functionality from the
>>>> AbstractMediatorFactory might be mistakenly bypassed.
>>>>
>>>
>>> Of course that is the design, some how by mistake they left as public and
>>> now I have fixed that.
>>>
>>>
>>>>
>>>>
>>>> Another small side-note AbstractMediatorFactory#createMediator’s JavaDoc
>>>> has not been adjusted to the added parameter “Properties” which use is still
>>>> unclear to me.
>>>>
>>>
>>> Added properties param to the JavaDoc.
>>>
>>> Thanks,
>>> Ruwan
>>>
>>>
>>>>
>>>>
>>>> Apart from that I have positive feedback regarding my tests with simple
>>>> mediation and usage of the nhttp transports. I could not spot any problem so
>>>> far. I also did a couple of small load tests against one small instance
>>>> reaching about 2500 requests per second and letting it run on that level for
>>>> a few hours.
>>>>
>>>>
>>>>
>>>> Regards,
>>>>
>>>>    Eric
>>>>
>>>>
>>>>   ------------------------------
>>>>
>>>> *From:* Ruwan Linton [mailto:ruwan.linton@gmail.com]
>>>> *Sent:* Sunday, December 12, 2010 3:33 AM
>>>>
>>>> *To:* dev@synapse.apache.org
>>>> *Subject:* Re: [VOTE] Release Synapse-2.0.0 (Take2)
>>>>
>>>>
>>>>
>>>> Hi Eric,
>>>>
>>>> On Sat, Dec 11, 2010 at 9:40 PM, Hubert, Eric <
>>>> Eric.Hubert@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.linton@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 <
>>>> hiranya911@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 <ru...@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/<http://people.apache.org/%7Eruwan/synapse/2.0.0-RC2/artifacts/>
>>>> > The m2 repository is available at:
>>>> > http://people.apache.org/~ruwan/synapse/2.0.0-RC2/m2_repo/<http://people.apache.org/%7Eruwan/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/<http://people.apache.org/%7Eruwan/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: ruwan@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: hiranya@wso2.com;  Mobile: +94 77 633 3491
>>>> Blog: http://techfeast-hiranya.blogspot.com
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
>>>> For additional commands, e-mail: dev-help@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: ruwan@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: ruwan@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: ruwan@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: ruwan@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
>>
>
>
>
> --
> Charith Dhanushka Wickramarachchi
> http://charithwiki.blogspot.com/
>
>


-- 
Charith Dhanushka Wickramarachchi
http://charithwiki.blogspot.com/

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

Posted by Charith Wickramarachchi <ch...@gmail.com>.
Hi ,

Sorry if i m too late. I ran few tests with the synapse samples and Found a
issue with the Sample 700 (Synapse Message Store).
The Sample documentation in [1] and synapse_sample_700.xml is bit diffrent
from the patch i attached in [2]
I think its because that patch was given for the new synapse xml schema and
getting it back to the old schema again caused this error.

Current synapse_sample_700.xml does not work since global endpoint
definition and sequence definition is in side the main sequence.
I'm attaching the current version of the synapse_sample_700.xml with this
mail.



[1]http://people.apache.org/~ruwan/synapse/2.0.0-RC2/site/<http://people.apache.org/%7Eruwan/synapse/2.0.0-RC2/site/>
[2]https://issues.apache.org/jira/secure/attachment/12452096/messagestore_patch_6.diff

thanks,
Charith





On Fri, Dec 17, 2010 at 10:31 PM, Ruwan Linton <ru...@gmail.com>wrote:

> Folks, sorry to let you know that the build is taking another day, as the
> source pack building issue is still there. Trying to figure out what was
> wrong, some times on a clean repo the build gets the same exception of a
> corrupted jar but is not really corrupted.
>
> Thanks,
> Ruwan
>
>
> On Thu, Dec 16, 2010 at 10:27 PM, Ruwan Linton <ru...@gmail.com>wrote:
>
>> Hi Eric,
>>
>> On Sun, Dec 12, 2010 at 5:22 PM, Hubert, Eric <Er...@foxmobile.com>wrote:
>>
>>>  Doing the mediator API related changes I asked myself whether concrete
>>> mediators like FaultMediator should really widen the visibility of
>>> AbstractMediatorFactory#createSpecificMediator. At least some of Synapse
>>> built-in mediators change the visibility from protected to public. I did not
>>> check all of them. I don’t think this is generally a good idea as to my
>>> understanding “users” of any MediatorFactory implementation should always
>>> only call createMediator (which internally delegates to
>>> createSpecificMediator). Otherwise functionality from the
>>> AbstractMediatorFactory might be mistakenly bypassed.
>>>
>>
>> Of course that is the design, some how by mistake they left as public and
>> now I have fixed that.
>>
>>
>>>
>>>
>>> Another small side-note AbstractMediatorFactory#createMediator’s JavaDoc
>>> has not been adjusted to the added parameter “Properties” which use is still
>>> unclear to me.
>>>
>>
>> Added properties param to the JavaDoc.
>>
>> Thanks,
>> Ruwan
>>
>>
>>>
>>>
>>> Apart from that I have positive feedback regarding my tests with simple
>>> mediation and usage of the nhttp transports. I could not spot any problem so
>>> far. I also did a couple of small load tests against one small instance
>>> reaching about 2500 requests per second and letting it run on that level for
>>> a few hours.
>>>
>>>
>>>
>>> Regards,
>>>
>>>    Eric
>>>
>>>
>>>   ------------------------------
>>>
>>> *From:* Ruwan Linton [mailto:ruwan.linton@gmail.com]
>>> *Sent:* Sunday, December 12, 2010 3:33 AM
>>>
>>> *To:* dev@synapse.apache.org
>>> *Subject:* Re: [VOTE] Release Synapse-2.0.0 (Take2)
>>>
>>>
>>>
>>> Hi Eric,
>>>
>>> On Sat, Dec 11, 2010 at 9:40 PM, Hubert, Eric <Er...@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.linton@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 <
>>> hiranya911@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 <ru...@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/<http://people.apache.org/%7Eruwan/synapse/2.0.0-RC2/artifacts/>
>>> > The m2 repository is available at:
>>> > http://people.apache.org/~ruwan/synapse/2.0.0-RC2/m2_repo/<http://people.apache.org/%7Eruwan/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/<http://people.apache.org/%7Eruwan/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: ruwan@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: hiranya@wso2.com;  Mobile: +94 77 633 3491
>>> Blog: http://techfeast-hiranya.blogspot.com
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
>>> For additional commands, e-mail: dev-help@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: ruwan@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: ruwan@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: ruwan@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: ruwan@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
>



-- 
Charith Dhanushka Wickramarachchi
http://charithwiki.blogspot.com/

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

Posted by Ruwan Linton <ru...@gmail.com>.
Folks, sorry to let you know that the build is taking another day, as the
source pack building issue is still there. Trying to figure out what was
wrong, some times on a clean repo the build gets the same exception of a
corrupted jar but is not really corrupted.

Thanks,
Ruwan

On Thu, Dec 16, 2010 at 10:27 PM, Ruwan Linton <ru...@gmail.com>wrote:

> Hi Eric,
>
> On Sun, Dec 12, 2010 at 5:22 PM, Hubert, Eric <Er...@foxmobile.com>wrote:
>
>>  Doing the mediator API related changes I asked myself whether concrete
>> mediators like FaultMediator should really widen the visibility of
>> AbstractMediatorFactory#createSpecificMediator. At least some of Synapse
>> built-in mediators change the visibility from protected to public. I did not
>> check all of them. I don’t think this is generally a good idea as to my
>> understanding “users” of any MediatorFactory implementation should always
>> only call createMediator (which internally delegates to
>> createSpecificMediator). Otherwise functionality from the
>> AbstractMediatorFactory might be mistakenly bypassed.
>>
>
> Of course that is the design, some how by mistake they left as public and
> now I have fixed that.
>
>
>>
>>
>> Another small side-note AbstractMediatorFactory#createMediator’s JavaDoc
>> has not been adjusted to the added parameter “Properties” which use is still
>> unclear to me.
>>
>
> Added properties param to the JavaDoc.
>
> Thanks,
> Ruwan
>
>
>>
>>
>> Apart from that I have positive feedback regarding my tests with simple
>> mediation and usage of the nhttp transports. I could not spot any problem so
>> far. I also did a couple of small load tests against one small instance
>> reaching about 2500 requests per second and letting it run on that level for
>> a few hours.
>>
>>
>>
>> Regards,
>>
>>    Eric
>>
>>
>>   ------------------------------
>>
>> *From:* Ruwan Linton [mailto:ruwan.linton@gmail.com]
>> *Sent:* Sunday, December 12, 2010 3:33 AM
>>
>> *To:* dev@synapse.apache.org
>> *Subject:* Re: [VOTE] Release Synapse-2.0.0 (Take2)
>>
>>
>>
>> Hi Eric,
>>
>> On Sat, Dec 11, 2010 at 9:40 PM, Hubert, Eric <Er...@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.linton@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 <
>> hiranya911@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 <ru...@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: ruwan@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: hiranya@wso2.com;  Mobile: +94 77 633 3491
>> Blog: http://techfeast-hiranya.blogspot.com
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
>> For additional commands, e-mail: dev-help@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: ruwan@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: ruwan@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: ruwan@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: ruwan@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)

Posted by Ruwan Linton <ru...@gmail.com>.
Hi Eric,

On Sun, Dec 12, 2010 at 5:22 PM, Hubert, Eric <Er...@foxmobile.com>wrote:

>  Doing the mediator API related changes I asked myself whether concrete
> mediators like FaultMediator should really widen the visibility of
> AbstractMediatorFactory#createSpecificMediator. At least some of Synapse
> built-in mediators change the visibility from protected to public. I did not
> check all of them. I don’t think this is generally a good idea as to my
> understanding “users” of any MediatorFactory implementation should always
> only call createMediator (which internally delegates to
> createSpecificMediator). Otherwise functionality from the
> AbstractMediatorFactory might be mistakenly bypassed.
>

Of course that is the design, some how by mistake they left as public and
now I have fixed that.


>
>
> Another small side-note AbstractMediatorFactory#createMediator’s JavaDoc
> has not been adjusted to the added parameter “Properties” which use is still
> unclear to me.
>

Added properties param to the JavaDoc.

Thanks,
Ruwan


>
>
> Apart from that I have positive feedback regarding my tests with simple
> mediation and usage of the nhttp transports. I could not spot any problem so
> far. I also did a couple of small load tests against one small instance
> reaching about 2500 requests per second and letting it run on that level for
> a few hours.
>
>
>
> Regards,
>
>    Eric
>
>
>   ------------------------------
>
> *From:* Ruwan Linton [mailto:ruwan.linton@gmail.com]
> *Sent:* Sunday, December 12, 2010 3:33 AM
>
> *To:* dev@synapse.apache.org
> *Subject:* Re: [VOTE] Release Synapse-2.0.0 (Take2)
>
>
>
> Hi Eric,
>
> On Sat, Dec 11, 2010 at 9:40 PM, Hubert, Eric <Er...@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.linton@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 <hi...@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 <ru...@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: ruwan@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: hiranya@wso2.com;  Mobile: +94 77 633 3491
> Blog: http://techfeast-hiranya.blogspot.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
> For additional commands, e-mail: dev-help@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: ruwan@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: ruwan@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: ruwan@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)

Posted by "Hubert, Eric" <Er...@foxmobile.com>.
Doing the mediator API related changes I asked myself whether concrete mediators like FaultMediator should really widen the visibility of AbstractMediatorFactory#createSpecificMediator. At least some of Synapse built-in mediators change the visibility from protected to public. I did not check all of them. I don’t think this is generally a good idea as to my understanding “users” of any MediatorFactory implementation should always only call createMediator (which internally delegates to createSpecificMediator). Otherwise functionality from the AbstractMediatorFactory might be mistakenly bypassed.

Another small side-note AbstractMediatorFactory#createMediator’s JavaDoc has not been adjusted to the added parameter “Properties” which use is still unclear to me.

Apart from that I have positive feedback regarding my tests with simple mediation and usage of the nhttp transports. I could not spot any problem so far. I also did a couple of small load tests against one small instance reaching about 2500 requests per second and letting it run on that level for a few hours.

Regards,
   Eric

________________________________
From: Ruwan Linton [mailto:ruwan.linton@gmail.com]
Sent: Sunday, December 12, 2010 3:33 AM
To: dev@synapse.apache.org
Subject: Re: [VOTE] Release Synapse-2.0.0 (Take2)

Hi Eric,
On Sat, Dec 11, 2010 at 9:40 PM, Hubert, Eric <Er...@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.linton@gmail.com<ma...@gmail.com>]
Sent: Thursday, December 09, 2010 11:08 AM

To: dev@synapse.apache.org<ma...@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 <hi...@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 <ru...@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: ruwan@wso2.com<ma...@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: hiranya@wso2.com<ma...@wso2.com>;  Mobile: +94 77 633 3491
Blog: http://techfeast-hiranya.blogspot.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org<ma...@synapse.apache.org>
For additional commands, e-mail: dev-help@synapse.apache.org<ma...@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: ruwan@wso2.com<ma...@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: ruwan@wso2.com<ma...@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)

Posted by Ruwan Linton <ru...@gmail.com>.
Hi Eric,

On Sat, Dec 11, 2010 at 9:40 PM, Hubert, Eric <Er...@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.linton@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 <hi...@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 <ru...@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: ruwan@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: hiranya@wso2.com;  Mobile: +94 77 633 3491
> Blog: http://techfeast-hiranya.blogspot.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
> For additional commands, e-mail: dev-help@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: ruwan@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: ruwan@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)

Posted by "Hubert, Eric" <Er...@foxmobile.com>.
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.


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.





Regards,

   Eric



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



________________________________
From: Ruwan Linton [mailto:ruwan.linton@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 <hi...@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 <ru...@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: ruwan@wso2.com<ma...@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: hiranya@wso2.com<ma...@wso2.com>;  Mobile: +94 77 633 3491
Blog: http://techfeast-hiranya.blogspot.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org<ma...@synapse.apache.org>
For additional commands, e-mail: dev-help@synapse.apache.org<ma...@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: ruwan@wso2.com<ma...@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)

Posted by Ruwan Linton <ru...@gmail.com>.
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
<hi...@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 <ru...@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: ruwan@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: hiranya@wso2.com;  Mobile: +94 77 633 3491
> Blog: http://techfeast-hiranya.blogspot.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
> For additional commands, e-mail: dev-help@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: ruwan@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)

Posted by Hiranya Jayathilaka <hi...@gmail.com>.
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 <ru...@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: ruwan@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: hiranya@wso2.com;  Mobile: +94 77 633 3491
Blog: http://techfeast-hiranya.blogspot.com

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

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

Posted by "Hubert, Eric" <Er...@foxmobile.com>.
I tried to build from the RC2 source zip under Windows with Maven 2.0.9, but receive the following error message:

Downloading: http://dist.wso2.org/maven2//org/apache/sandesha2/sandesha2-core/1.3-1041287/sandesha2-core-1.3-1041287.jar
370K downloaded
[WARNING] *** CHECKSUM FAILED - Error retrieving checksum file for org/apache/sandesha2/sandesha2-core/1.3-1041287/sandesha2-core-1.3-1041287.jar - IGNORING
…
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Compilation failure

error: error reading D:\projects\m2-repo\org\apache\sandesha2\sandesha2-core\1.3-1041287\sandesha2-core-1.3-1041287.jar; error in opening zip file

I verified the file to be in my local repo. I’m also able to extract the file with jar –xvf without problems…
It should not be a big issue that the library in the WSO2 repo has been deployed without a checksum file, or? With my settings Maven simply ignores this fact (although it is obviously not nice). But what is the issue with this archive? As I have never run into such an issue before has someone an idea how to quickly resolve this?

Am I the only person having this issue?

Regards,
   Eric



________________________________
From: Ruwan Linton [mailto:ruwan.linton@gmail.com]
Sent: Wednesday, December 08, 2010 7:57 AM
To: dev@synapse.apache.org
Subject: [VOTE] Release Synapse-2.0.0 (Take2)

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/
<http://people.apache.org/~ruwan/synapse/2.0.0/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: ruwan@wso2.com<ma...@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)

Posted by Ruwan Linton <ru...@gmail.com>.
First of all, you should start a separate thread on this, as this is a
separate concern.

Sample documentation can be found on the samples guide, (not yet released)
[1]

The JMS client code is there on samples/client/src directory of the
distribution planned to release. [2]

The JMS transport source is under the axis2 transports project of which you
can find information from [3].

Thanks,
Ruwan

[1] -
http://people.apache.org/~ruwan/synapse/2.0.0-RC2/site/Synapse_Samples.html#Sample264
[2] -
http://people.apache.org/~ruwan/synapse/2.0.0-RC2/artifacts/synapse-2.0.0-bin.zip
<http://people.apache.org/~ruwan/synapse/2.0.0-RC2/artifacts/synapse-2.0.0-bin.zip>[3]
- http://axis.apache.org/axis2/java/transports/jms.html


On Sat, Dec 11, 2010 at 10:11 PM, ilango <il...@gmail.com> wrote:

> Where can I get the source for the JMS examples of request/response with
> asynchronous callback.
> Is it inside the WSO2 trunk or the Synapse trunk?
>
> I am looking for an order processing or order fulfillment example or
> something approximately similar that highlights the use of JMS queues with
> asynchronous callback.
>
> thanks
> ilango
>
>
>
> On Wed, Dec 8, 2010 at 12:57 AM, Ruwan Linton <ru...@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/
>>  <http://people.apache.org/~ruwan/synapse/2.0.0/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: ruwan@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: ruwan@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)

Posted by ilango <il...@gmail.com>.
Where can I get the source for the JMS examples of request/response with
asynchronous callback.
Is it inside the WSO2 trunk or the Synapse trunk?

I am looking for an order processing or order fulfillment example or
something approximately similar that highlights the use of JMS queues with
asynchronous callback.

thanks
ilango



On Wed, Dec 8, 2010 at 12:57 AM, Ruwan Linton <ru...@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/
>  <http://people.apache.org/~ruwan/synapse/2.0.0/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: ruwan@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
>