[
https://issues.apache.org/jira/browse/SYNAPSE-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12556596#action_12556596
]
Rajith Attapattu commented on SYNAPSE-223:
------------------------------------------
Asankha,
No worries and I think excluding from the branch is the best option.
For the repo issue I think the best is to do have as a revision.
>anyway, as Andreas has experienced, maven picks up whatever it finds as the
>latest for a SNAPSHOT artifact if it exists in multiple repos, so putting it
>on the >wso2 repo will not help, neither hosting it privately in your repo, as
>long as apache snapshots has a copy too..
I meant using a different name (same as having a different version), so u force
maven to pick it up.
But I think the revision build the accepted way of doing something like that.
Where do you host these revision builds? I assume you can't shove it in the
SNAPSHOT repo. So either I can put it in my private OR you could host it in
your wso2 repo. I prefer the later option as we can avoid specifying an extra
repo.
>Do you know why versions found there may differ from what you have in your
>private branch?
The qpid libs are built off trunk and as I said we (Qpid project) have no
proper policy of updating the snapshot repos.
Besides I am expecting some churn in the trunk as we are trying to reorg things
and also after the 0-10 spec is released we may change things around a bit.
This might become a real nuisance for Synapse as it might break our build. So
I like to work with Synapse based on a particular revision and upgrade in a
more sane way.
My expectation is we will do a release before Syanpse 1.2, so come release time
we have a permanent solution.
Regards,
Rajith
> AMQP Transport
> --------------
>
> Key: SYNAPSE-223
> URL: https://issues.apache.org/jira/browse/SYNAPSE-223
> Project: Synapse
> Issue Type: New Feature
> Reporter: Rajith Attapattu
> Assignee: Rajith Attapattu
> Fix For: 1.2
>
>
> The AMQP transport will be based on the Apache Qpid project.
> Apache Qpid has a JMS client implementation over AMQP. Since Synapse has a
> JMS transport, you could use that to get AMQP support as well.
> However a native client has the following advantages.
> * You can use any exchange, not just direct (JMS Queues) or topic (JMS
> Topics). Ex. fannout, headers or a custom exchange.
> * Ability to customise the exchange type, exchange name, routing key and
> other AMQP specific parameters.
> * More fine grained control of AMQP concepts
> * Possibility of streaming large attachments off the disk. (need to figure
> out how to leverage the AXIOM support here).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
