Hi Jeremy,
My bad... I just realized that the default behavior in the new JMS
endpoints is to copy all properties without checking for valid Java
identifier syntax. This is switched on via the DefaultProviderMarshaler,
which is used by default but you will have to manually create a bean in
xbean.xml to override the needJavaIdentifiers value.
So using your example:
<jms:provider service="tut:jms"
endpoint="myQueue"
connectionFactory="#mqConnectionFactory"
...
marshaler="#marshaler" />
<bean id="marshaler"
class="org.apache.servicemix.jms.endpoints.DefaultConsumerMarshaler">
<property name="needJavaIdentifiers" value="true" />
</bean>
HTH,
Chris
--
Chris Custine
FUSESource :: http://fusesource.com
My Blog :: http://blog.organicelement.com
Apache ServiceMix :: http://servicemix.apache.org
Apache Directory Server :: http://directory.apache.org
On Tue, Aug 25, 2009 at 3:22 PM, Chris Custine <[email protected]>wrote:
> This property comes from the file poller, but the jms endpoint should be
> stripping this property out because it is not a valid Java identifier
> (required by the JMS spec). What version of SMX and the components are you
> using?
>
> Chris
> --
> Chris Custine
> FUSESource :: http://fusesource.com
> My Blog :: http://blog.organicelement.com
> Apache ServiceMix :: http://servicemix.apache.org
> Apache Directory Server :: http://directory.apache.org
>
>
> On Tue, Aug 25, 2009 at 1:22 PM, jrrosel <[email protected]>wrote:
>
>>
>> My mq admin had me change the java channel I was using. I am once again
>> getting another error.
>>
>> org.springframework.jms.MessageFormatException: MQJMS1058: Invalid message
>> prope
>> rty name: org.apache.servicemix.file.name; nested exception is
>> javax.jms.Message
>> FormatException: MQJMS1058: Invalid message property name:
>> org.apache.servicemix
>> .file.name
>>
>> I don't have anything set for org.apache.servicemix.file.name so I am not
>> sure where that is coming from.
>>
>> Thanks,
>> Jeremy
>>
>>
>> Chris Custine wrote:
>> >
>> > Your config looks fine to me, so I don't see the problem being the
>> client
>> > connection properties since they look exactly like a config that I have
>> > which is known to work. Do you have other client code attaching to this
>> > QM
>> > and SVRCONN? If this is a new setup, I suspect firewall, nat issues, or
>> > even a bad channel def.
>> >
>> > HTH
>> >
>> > Chris
>> >
>> > --
>> > Chris Custine
>> > FUSESource :: http://fusesource.com
>> > My Blog :: http://blog.organicelement.com
>> > Apache ServiceMix :: http://servicemix.apache.org
>> > Apache Directory Server :: http://directory.apache.org
>> >
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Servicemix-JMS-and-Websphere-MQ-tp25082012p25140593.html
>> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>>
>>
>
