JIRA MULE-714 in 1.3?

[Tomas Blohm]

Hi, I'm using the patch attached to MULE-714 for performing outbound read queries and in the snapshot version it works just fine. When I switched to 1.3 all the message properties gets lost. It seems quite natural since the code in the patch returns a new MuleMessage with the return value from the select query so it's a new instance of a message that doesn't know anything about the old properties but how could this work in the snapshot version? And how could I make this work in 1.3?
Normally I always go for snapshot version when I do projects but in this case I have to launch this at a customer in a production environment and it feels more serious to use a stable version, that's why I have to get this working with the 1.3 version.

/Tomas

[Holger Hoffstätte-2]

T.B wrote:
> Hi, I'm using the patch attached to MULE-714 for performing outbound read
> queries and in the snapshot version it works just fine. When I switched to

"The snapshot version" is 1.4-SNAPSHOT, published nightly. As far as I am
concerned, nothing else exists even if there are a few outdated
1.3-SNAPSHOTS still available. These should not be used and will cease to
exist soon. If you report a bug against them, chances are that nobody will
be able to look into the problem properly.
If you experience a bug in 1.3 final, please do file a bug but include
more precise information than just "properties get lost". It is impossible
to even begin looking at the problem with that information; please help us
a little better to be able to help you.

-h

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

[Tomas Blohm]

I understand. I solved it with just changing the return clause from:
return new MuleMessage(result);

to:

return new MuleMessage(result, event.getMessage().getAdapter());

Then all the properties from the old message gets past along and with the new payload.
I don't know if it's the way to go but it works for me.

Holger Hoffstätte-2 wrote:

T.B wrote:
> Hi, I'm using the patch attached to MULE-714 for performing outbound read
> queries and in the snapshot version it works just fine. When I switched to

"The snapshot version" is 1.4-SNAPSHOT, published nightly. As far as I am
concerned, nothing else exists even if there are a few outdated
1.3-SNAPSHOTS still available. These should not be used and will cease to
exist soon. If you report a bug against them, chances are that nobody will
be able to look into the problem properly.
If you experience a bug in 1.3 final, please do file a bug but include
more precise information than just "properties get lost". It is impossible
to even begin looking at the problem with that information; please help us
a little better to be able to help you.

-h

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

[Andrew Perepelytsya]

Tomas,

Another way to substitute a payload preserving the meta-info is to use the eventContext.rewriteEvent() method.

Andrew

On 10/30/06, Tomas Blohm <tomas.blohm@...> wrote:

I understand. I solved it with just changing the return clause from:
return new MuleMessage(result);

to:

return new MuleMessage(result, event.getMessage().getAdapter());

Then all the properties from the old message gets past along and with the
new payload.
I don't know if it's the way to go but it works for me.



Holger Hoffstätte-2 wrote:

>
> T.B wrote:
>> Hi, I'm using the patch attached to MULE-714 for performing outbound read
>> queries and in the snapshot version it works just fine. When I switched
>> to
>
> "The snapshot version" is 1.4-SNAPSHOT, published nightly. As far as I am
> concerned, nothing else exists even if there are a few outdated
> 1.3-SNAPSHOTS still available. These should not be used and will cease to
> exist soon. If you report a bug against them, chances are that nobody will
> be able to look into the problem properly.
> If you experience a bug in 1.3 final, please do file a bug but include
> more precise information than just "properties get lost". It is impossible
> to even begin looking at the problem with that information; please help us

> a little better to be able to help you.

>
> -h
>
> ---------------------------------------------------------------------
> To unsubscribe from this list please visit:
>
>     http://xircles.codehaus.org/manage_email
>
>
>

--
View this message in context: http://www.nabble.com/JIRA-MULE-714-in-1.3--tf2518925.html#a7070094
Sent from the Mule - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

[Tomas Blohm]

I can't see that method in the API's, that was exactly what I was looking for when I realized what was going wrong but couldn't find.

/Tomas

Andrew Perepelytsya wrote:

Tomas,

Another way to substitute a payload preserving the meta-info is to use the
eventContext.rewriteEvent() method.

Andrew

On 10/30/06, Tomas Blohm <[e-mail]> wrote:
>
>
> I understand. I solved it with just changing the return clause from:
> return new MuleMessage(result);
>
> to:
>
> return new MuleMessage(result, event.getMessage().getAdapter());
>
> Then all the properties from the old message gets past along and with the
> new payload.
> I don't know if it's the way to go but it works for me.
>
>
>
> Holger Hoffstätte-2 wrote:
> >
> > T.B wrote:
> >> Hi, I'm using the patch attached to MULE-714 for performing outbound
> read
> >> queries and in the snapshot version it works just fine. When I switched
> >> to
> >
> > "The snapshot version" is 1.4-SNAPSHOT, published nightly. As far as I
> am
> > concerned, nothing else exists even if there are a few outdated
> > 1.3-SNAPSHOTS still available. These should not be used and will cease
> to
> > exist soon. If you report a bug against them, chances are that nobody
> will
> > be able to look into the problem properly.
> > If you experience a bug in 1.3 final, please do file a bug but include
> > more precise information than just "properties get lost". It is
> impossible
> > to even begin looking at the problem with that information; please help
> us
> > a little better to be able to help you.
> >
> > -h
> >
> > ---------------------------------------------------------------------
> > To unsubscribe from this list please visit:
> >
> >     http://xircles.codehaus.org/manage_email
> >
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/JIRA-MULE-714-in-1.3--tf2518925.html#a7070094
> Sent from the Mule - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list please visit:
>
>     http://xircles.codehaus.org/manage_email
>
>

[Andrew Perepelytsya]

It's either obtainable through a static RequestContext.getEventContext() call, or if your component implements Callable, it is passed in to your implementation.

More details available on the Mule site.

Andrew

On 10/30/06, Tomas Blohm <tomas.blohm@...> wrote:

I can't see that method in the API's, that was exactly what I was looking for
when I realized what was going wrong but couldn't find.

/Tomas



Andrew Perepelytsya wrote:
>
> Tomas,
>

> Another way to substitute a payload preserving the meta-info is to use the
> eventContext.rewriteEvent() method.
>
> Andrew
>
> On 10/30/06, Tomas Blohm <tomas.blohm@...> wrote:
>>
>>
>> I understand. I solved it with just changing the return clause from:
>> return new MuleMessage(result);
>>
>> to:
>>
>> return new MuleMessage(result, event.getMessage().getAdapter());
>>
>> Then all the properties from the old message gets past along and with the
>> new payload.
>> I don't know if it's the way to go but it works for me.
>>
>>
>>
>> Holger Hoffstätte-2 wrote:
>> >
>> > T.B wrote:
>> >> Hi, I'm using the patch attached to MULE-714 for performing outbound
>> read
>> >> queries and in the snapshot version it works just fine. When I
>> switched
>> >> to
>> >
>> > "The snapshot version" is 1.4-SNAPSHOT, published nightly. As far as I
>> am
>> > concerned, nothing else exists even if there are a few outdated
>> > 1.3-SNAPSHOTS still available. These should not be used and will cease
>> to
>> > exist soon. If you report a bug against them, chances are that nobody
>> will
>> > be able to look into the problem properly.
>> > If you experience a bug in 1.3 final, please do file a bug but include
>> > more precise information than just "properties get lost". It is
>> impossible
>> > to even begin looking at the problem with that information; please help
>> us
>> > a little better to be able to help you.
>> >
>> > -h
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe from this list please visit:
>> >
>> >     http://xircles.codehaus.org/manage_email
>> >
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/JIRA-MULE-714-in-1.3--tf2518925.html#a7070094
>> Sent from the Mule - User mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list please visit:
>>
>>     http://xircles.codehaus.org/manage_email
>>
>>
>
>

--
View this message in context: http://www.nabble.com/JIRA-MULE-714-in-1.3--tf2518925.html#a7076222
Sent from the Mule - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe from this list please visit:

     http://xircles.codehaus.org/manage_email

[Tomas Blohm]

Sorry, I might been a bit unclear, I sure know how to get the eventContext but I can't see any method called rewriteEvent().

Andrew Perepelytsya wrote:

It's either obtainable through a static RequestContext.getEventContext()
call, or if your component implements Callable, it is passed in to your
implementation.

More details available on the Mule site.

Andrew

On 10/30/06, Tomas Blohm <[e-mail]> wrote:
>
>
> I can't see that method in the API's, that was exactly what I was looking
> for
> when I realized what was going wrong but couldn't find.
>
> /Tomas
>
>
>
> Andrew Perepelytsya wrote:
> >
> > Tomas,
> >
> > Another way to substitute a payload preserving the meta-info is to use
> the
> > eventContext.rewriteEvent() method.
> >
> > Andrew
> >
> > On 10/30/06, Tomas Blohm <[e-mail]> wrote:
> >>
> >>
> >> I understand. I solved it with just changing the return clause from:
> >> return new MuleMessage(result);
> >>
> >> to:
> >>
> >> return new MuleMessage(result, event.getMessage().getAdapter());
> >>
> >> Then all the properties from the old message gets past along and with
> the
> >> new payload.
> >> I don't know if it's the way to go but it works for me.
> >>
> >>
> >>
> >> Holger Hoffstätte-2 wrote:
> >> >
> >> > T.B wrote:
> >> >> Hi, I'm using the patch attached to MULE-714 for performing outbound
> >> read
> >> >> queries and in the snapshot version it works just fine. When I
> >> switched
> >> >> to
> >> >
> >> > "The snapshot version" is 1.4-SNAPSHOT, published nightly. As far as
> I
> >> am
> >> > concerned, nothing else exists even if there are a few outdated
> >> > 1.3-SNAPSHOTS still available. These should not be used and will
> cease
> >> to
> >> > exist soon. If you report a bug against them, chances are that nobody
> >> will
> >> > be able to look into the problem properly.
> >> > If you experience a bug in 1.3 final, please do file a bug but
> include
> >> > more precise information than just "properties get lost". It is
> >> impossible
> >> > to even begin looking at the problem with that information; please
> help
> >> us
> >> > a little better to be able to help you.
> >> >
> >> > -h
> >> >
> >> > ---------------------------------------------------------------------
> >> > To unsubscribe from this list please visit:
> >> >
> >> >     http://xircles.codehaus.org/manage_email
> >> >
> >> >
> >> >
> >>
> >> --
> >> View this message in context:
> >> http://www.nabble.com/JIRA-MULE-714-in-1.3--tf2518925.html#a7070094
> >> Sent from the Mule - User mailing list archive at Nabble.com.
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe from this list please visit:
> >>
> >>     http://xircles.codehaus.org/manage_email
> >>
> >>
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/JIRA-MULE-714-in-1.3--tf2518925.html#a7076222
> Sent from the Mule - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list please visit:
>
>     http://xircles.codehaus.org/manage_email
>
>

[Andrew Perepelytsya]

Sorry for the confusion, the method is available directly on RequestContext.

Andrew

On 10/30/06, Tomas Blohm <tomas.blohm@...> wrote:

Sorry, I might been a bit unclear, I sure know how to get the eventContext
but I can't see any method called rewriteEvent().

[Tomas Blohm]

Yes, thank you. I've actually missed that method but it's exactly what I've been looking for. When I made my own LDAP connector I ended up changing messages back and forward just to achieve just the thing this method is doing. So thanks for the information!

Andrew Perepelytsya wrote:

Sorry for the confusion, the method is available directly on RequestContext.

Andrew

On 10/30/06, Tomas Blohm <[e-mail]> wrote:
>
>
> Sorry, I might been a bit unclear, I sure know how to get the eventContext
> but I can't see any method called rewriteEvent().
>
>