Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Destination properties not injected via JNDI in Jetty #102

Open
erm410 opened this issue Apr 5, 2015 · 0 comments
Open

Destination properties not injected via JNDI in Jetty #102

erm410 opened this issue Apr 5, 2015 · 0 comments

Comments

@erm410
Copy link

erm410 commented Apr 5, 2015

When referencing a JNDI injected destination in a Jetty servlet, only the name property is honored.

For example when a queue is created using

...
<New id="jmsConnectionFactory" class="org.eclipse.jetty.plus.jndi.Resource">
    <Arg><Ref id="wac" /></Arg>
    <Arg>jms/destination1</Arg>
    <Arg>
        <New class="org.skyscreamer.nevado.jms.destination.NevadoQueue">
            <Arg>destination1</Arg>
            <Set name="queueUrl">https://sqs.us-east-1.amazonaws.com/xxx/destination1</Set>
        </New>
    </Arg>
</New>
...

in jetty-env.xml, the looked-up resource has a null queueUrl.

This make it impossible to fully configure your destinations in jetty-env.xml and then inject them into a JMS provider agnostic existing application (since setting the lost properties requires a downcast to a Nevado specific type).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant