[
https://issues.apache.org/activemq/browse/SM-1085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Koehler updated SM-1085:
-
Attachment: another-patch.patch
this is a problem with the geronimo version, i think.
in the to
> I also meant that if there is not, it should be added :-)
Ok... ;-)
On 10/18/07, Kristian Köhler <[EMAIL PROTECTED]> wrote:
> Hi
>
> > Anyway, I think you're on the right track. There's no reason why the
> > camel SE would set the jbi.operation property when going from jbi to
> > camel, but not use it when going from camel to jbi. In addition, we
> > could make t
[
https://issues.apache.org/activemq/browse/SM-1085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Koehler updated SM-1085:
-
Attachment: geronimo-servicemix-deployer-patch.patch
here is the new version.
the new files are
Hi
> Anyway, I think you're on the right track. There's no reason why the
> camel SE would set the jbi.operation property when going from jbi to
> camel, but not use it when going from camel to jbi. In addition, we
> could make the operation also configurable on the endpoint (to be
> consistent
[
https://issues.apache.org/activemq/browse/SM-1085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40410
]
Guillaume Nodet commented on SM-1085:
-
I've tried to apply your patch, but it seems to have become out of sync with
The attachment was removed from your mail i suppose.
Maybe just raise a jira and attach it there.
Anyway, I think you're on the right track. There's no reason why the
camel SE would set the jbi.operation property when going from jbi to
camel, but not use it when going from camel to jbi. In addit
