Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Message-ID: <1305637656.1222719404405.JavaMail.jira@brutus>
Date: Mon, 29 Sep 2008 13:16:44 -0700 (PDT)
From: "Christian Schneider (JIRA)" <jira@apache.org>
To: issues@cxf.apache.org
Subject: [jira] Resolved: (CXF-1774) JMS Transport: Remove JNDI lookups for
 ConnectionFactory, targetDestination and replyDestination
In-Reply-To: <1965910569.1220057864297.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/CXF-1774?page=3Dcom.atlassian.=
jira.plugin.system.issuetabpanels:all-tabpanel ]

Christian Schneider resolved CXF-1774.
--------------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 2.2)
                   2.1.3

> JMS Transport: Remove JNDI lookups for ConnectionFactory, targetDestinati=
on and replyDestination
> -------------------------------------------------------------------------=
-----------------------
>
>                 Key: CXF-1774
>                 URL: https://issues.apache.org/jira/browse/CXF-1774
>             Project: CXF
>          Issue Type: Improvement
>          Components: Transports
>    Affects Versions: 2.1.2
>            Reporter: Christian Schneider
>             Fix For: 2.1.3
>
>
> Currently you have to configure all jms settings via JNDI. targetDestinat=
ion is the only config property that already can additionally be configured=
 as a string.
> I think the JNDI stuff does not belong into the JMS transport.=20
> ConnectionFactory should simply be configured as a refrence to a bean of =
type jms ConnectionFactory. So the user of cxf is free to either setup the =
ConnectionFactory locally or look it up via Spring=C2=B4s great JNDI suppor=
t.
> The same is true for targetDestination and replyDestination. They should =
simply be injected. The JNDI logic should be deleted from JMS transport. Ad=
ditionally it should be possible for targetDestination and replyDestination=
 to set them as simple strings as this is the most common way they will be =
used by people.=20
> Fixing this will make the JMS Transport code simpler and at the same time=
 the CXF users will get greater flexibility in the configuration.

--=20
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.