Details

  • Type: Sub-task Sub-task
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 2.0.0-RC1
  • Fix Version/s: 2.0.0-RC2
  • Component/s: Core: Configuration
  • Labels:
    None
  • User impact:
    Medium
  • Similar Issues:
    None

Description

There is not schema for jms: endpoints so I can't do -

<jms:inbound-endpoint queue="myQueue">
<jms:selector expression="Priority > 5"/>
<jms:transaction action="ALWAYS_BEGIN"/>
</jms:inbound-endpoint>

Issue Links

Activity

Hide
Andrew Cooke added a comment -

i've added basic endpoint support - that means that you can define global, inbound and outbound endpoints, with either a queue or a topic (topic prefixes the name with "topic:"). the standard endpoint attributes (eg connector-ref) are also supported.

transactions are already supported, but the example above includes a "selector". i've searched existing configs for bother "selector" and "priority", but i can't find anything that seems relevant. can you give more details, please?

jms also has support for connector factories etc, but if there is anything that should be in the endpoint element itself (eg common endpoint properties), please can you also suggest them? again, i've gone through existing configs, but found nothing.

Show
Andrew Cooke added a comment - i've added basic endpoint support - that means that you can define global, inbound and outbound endpoints, with either a queue or a topic (topic prefixes the name with "topic:"). the standard endpoint attributes (eg connector-ref) are also supported. transactions are already supported, but the example above includes a "selector". i've searched existing configs for bother "selector" and "priority", but i can't find anything that seems relevant. can you give more details, please? jms also has support for connector factories etc, but if there is anything that should be in the endpoint element itself (eg common endpoint properties), please can you also suggest them? again, i've gone through existing configs, but found nothing.
Hide
Andrew Cooke added a comment -

"connector factories" above should be "connection factories". sorry.

basically there was a bunch of stuff defined for jms support already, it may be that just the endpoints were missing.

Show
Andrew Cooke added a comment - "connector factories" above should be "connection factories". sorry. basically there was a bunch of stuff defined for jms support already, it may be that just the endpoints were missing.
Hide
Ross Mason added a comment -

Excellent Andrew, I'll take a look tomorrow.
Regarding the selector, it is actually the JMSSelectorFilter that I'm referring to.

Show
Ross Mason added a comment - Excellent Andrew, I'll take a look tomorrow. Regarding the selector, it is actually the JMSSelectorFilter that I'm referring to.
Hide
Andrew Cooke added a comment -

ah thanks - i'll add both the jms filters this afternoon (they're currently unsupported as far as i can see).

Show
Andrew Cooke added a comment - ah thanks - i'll add both the jms filters this afternoon (they're currently unsupported as far as i can see).
Hide
Andrew Cooke added a comment -

ok, the jms namespace test now includes

{xml}
<jms:endpoint name="endpoint1" queue="blah" connector-ref="jmsConnectorDefaults">
<jms:selector expression="foo"/>
</jms:endpoint>{xml}

and transactions are tested elsewhere.

Show
Andrew Cooke added a comment - ok, the jms namespace test now includes {xml} <jms:endpoint name="endpoint1" queue="blah" connector-ref="jmsConnectorDefaults"> <jms:selector expression="foo"/> </jms:endpoint>{xml} and transactions are tested elsewhere.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: