You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@servicemix.apache.org by netflexity <mf...@netflexity.com> on 2007/08/24 17:12:07 UTC
Externalizing configurations to JNDI for http-su and jms-su does
not work.
Hello.
I am using Spring propertyPlaceholder to externalize various component
configurations and successful if they are in the same src/main/resources
directory. Moreover, I have no problems doing the same with config resources
in JNDI (sample below), except for http-su and jms-su that complain about
JNDI factory.initial System properties during Maven build. Any ideas?
<bean id="propertyPlaceholder"
class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
<property name="location">
<bean
class="org.springframework.core.io.FileSystemResource">
<constructor-arg>
<bean
class="org.springframework.jndi.JndiObjectFactoryBean">
<property name="jndiName"
value="external/config/somedir/product.properties"/>
</bean>
</constructor-arg>
</bean>
</property>
</bean>
--
View this message in context: http://www.nabble.com/Externalizing-configurations-to-JNDI-for-http-su-and-jms-su-does-not-work.-tf4324128s12049.html#a12314292
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: Externalizing configurations to JNDI for http-su and jms-su does not work.
Posted by Bruce Snyder <br...@gmail.com>.
On 9/4/07, netflexity <mf...@netflexity.com> wrote:
>
> Sorry, I tried to figure this plugin thing on my own and not bug you, but I
> cannot find a single sample of how to use this custom jbi plugin in pom.xml.
>
> Thanks a lot.
>
>
> gnodet wrote:
> >
> > You need to disable the SU jbi descriptor generation.
> > There is property to configure on the plugin to do so:
> > see http://incubator.apache.org/servicemix/dist/servicemix-3.1-
> > incubating/site/tooling/jbi-maven-plugin/generate-jbi-service-unit-
> > descriptor-mojo.html
> >
> > Just configure the generateJbiDescriptor to false on the plugin
> > configuration
> > in your pom.
Below is an example:
<build>
<plugins>
<plugin>
<groupId>org.apache.servicemix.tooling</groupId>
<artifactId>jbi-maven-plugin</artifactId>
<version>${servicemix-version}</version>
<extensions>true</extensions>
<configuration>
<generateJbiDescriptor>false</generateJbiDescriptor>
</configuration>
</plugin>
</plugins>
</build>
Bruce
--
perl -e 'print unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
);'
Apache ActiveMQ - http://activemq.org/
Apache ServiceMix - http://servicemix.org/
Apache Geronimo - http://geronimo.apache.org/
Castor - http://castor.org/
Re: Externalizing configurations to JNDI for http-su and jms-su
does not work.
Posted by netflexity <mf...@netflexity.com>.
Sorry, I tried to figure this plugin thing on my own and not bug you, but I
cannot find a single sample of how to use this custom jbi plugin in pom.xml.
Thanks a lot.
gnodet wrote:
>
> You need to disable the SU jbi descriptor generation.
> There is property to configure on the plugin to do so:
> see http://incubator.apache.org/servicemix/dist/servicemix-3.1-
> incubating/site/tooling/jbi-maven-plugin/generate-jbi-service-unit-
> descriptor-mojo.html
>
> Just configure the generateJbiDescriptor to false on the plugin
> configuration
> in your pom.
>
> Cheers,
> Guillaume Nodet
>
> On Aug 24, 2007, at 7:57 PM, netflexity wrote:
>
>>
>> [propertyPlaceholder,org.apache.servicemix.http.HttpEndpoint,org.apach
>> e.servicemix.http.H
>> ttpEndpoint#1,org.apache.servicemix.http.HttpEndpoint#2,org.apache.ser
>> vicemix.http.HttpEndpoint#3,org.apache.servicemix.http.HttpEndpoint#4,
>> org.apache.servicemix.http.HttpEndpoint#5,org.apache.servicemix.http.H
>> ttpEndpoint#6];
>> root of BeanFactory hierarchy}
>> [INFO]
>> ----------------------------------------------------------------------
>> --
>> [ERROR] BUILD ERROR
>> [INFO]
>> ----------------------------------------------------------------------
>> --
>> [INFO] Failed to generate jbi.xml
>>
>> Embedded error: Unable to generate service unit descriptor!
>> Need to specify class name in environment or system property, or as an
>> applet parameter, or in an application resource file:
>> java.naming.factory.initial
>>
>>
>>
>> bsnyder wrote:
>>>
>>> On 8/24/07, netflexity <mf...@netflexity.com> wrote:
>>>>
>>>> Hello.
>>>> I am using Spring propertyPlaceholder to externalize various
>>>> component
>>>> configurations and successful if they are in the same src/main/
>>>> resources
>>>> directory. Moreover, I have no problems doing the same with config
>>>> resources
>>>> in JNDI (sample below), except for http-su and jms-su that
>>>> complain about
>>>> JNDI factory.initial System properties during Maven build. Any
>>>> ideas?
>>>
>>> Can you post the error you're seeing regarding this?
>>>
>>> Bruce
>>> --
>>> perl -e 'print
>>> unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
>>> );'
>>>
>>> Apache ActiveMQ - http://activemq.org/
>>> Apache ServiceMix - http://servicemix.org/
>>> Apache Geronimo - http://geronimo.apache.org/
>>> Castor - http://castor.org/
>>>
>>>
>>
>> --
>> View this message in context: http://www.nabble.com/Externalizing-
>> configurations-to-JNDI-for-http-su-and-jms-su-does-not-work.-
>> tf4324128s12049.html#a12317129
>> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>>
>
>
>
--
View this message in context: http://www.nabble.com/Externalizing-configurations-to-JNDI-for-http-su-and-jms-su-does-not-work.-tf4324128s12049.html#a12478763
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: Externalizing configurations to JNDI for http-su and jms-su
does not work.
Posted by netflexity <mf...@netflexity.com>.
Thanks a lot!!!
gnodet wrote:
>
> You need to disable the SU jbi descriptor generation.
> There is property to configure on the plugin to do so:
> see http://incubator.apache.org/servicemix/dist/servicemix-3.1-
> incubating/site/tooling/jbi-maven-plugin/generate-jbi-service-unit-
> descriptor-mojo.html
>
> Just configure the generateJbiDescriptor to false on the plugin
> configuration
> in your pom.
>
> Cheers,
> Guillaume Nodet
>
> On Aug 24, 2007, at 7:57 PM, netflexity wrote:
>
>>
>> [propertyPlaceholder,org.apache.servicemix.http.HttpEndpoint,org.apach
>> e.servicemix.http.H
>> ttpEndpoint#1,org.apache.servicemix.http.HttpEndpoint#2,org.apache.ser
>> vicemix.http.HttpEndpoint#3,org.apache.servicemix.http.HttpEndpoint#4,
>> org.apache.servicemix.http.HttpEndpoint#5,org.apache.servicemix.http.H
>> ttpEndpoint#6];
>> root of BeanFactory hierarchy}
>> [INFO]
>> ----------------------------------------------------------------------
>> --
>> [ERROR] BUILD ERROR
>> [INFO]
>> ----------------------------------------------------------------------
>> --
>> [INFO] Failed to generate jbi.xml
>>
>> Embedded error: Unable to generate service unit descriptor!
>> Need to specify class name in environment or system property, or as an
>> applet parameter, or in an application resource file:
>> java.naming.factory.initial
>>
>>
>>
>> bsnyder wrote:
>>>
>>> On 8/24/07, netflexity <mf...@netflexity.com> wrote:
>>>>
>>>> Hello.
>>>> I am using Spring propertyPlaceholder to externalize various
>>>> component
>>>> configurations and successful if they are in the same src/main/
>>>> resources
>>>> directory. Moreover, I have no problems doing the same with config
>>>> resources
>>>> in JNDI (sample below), except for http-su and jms-su that
>>>> complain about
>>>> JNDI factory.initial System properties during Maven build. Any
>>>> ideas?
>>>
>>> Can you post the error you're seeing regarding this?
>>>
>>> Bruce
>>> --
>>> perl -e 'print
>>> unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
>>> );'
>>>
>>> Apache ActiveMQ - http://activemq.org/
>>> Apache ServiceMix - http://servicemix.org/
>>> Apache Geronimo - http://geronimo.apache.org/
>>> Castor - http://castor.org/
>>>
>>>
>>
>> --
>> View this message in context: http://www.nabble.com/Externalizing-
>> configurations-to-JNDI-for-http-su-and-jms-su-does-not-work.-
>> tf4324128s12049.html#a12317129
>> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>>
>
>
>
--
View this message in context: http://www.nabble.com/Externalizing-configurations-to-JNDI-for-http-su-and-jms-su-does-not-work.-tf4324128s12049.html#a12317757
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: Externalizing configurations to JNDI for http-su and jms-su does not work.
Posted by Nodet Guillaume <gn...@gmail.com>.
You need to disable the SU jbi descriptor generation.
There is property to configure on the plugin to do so:
see http://incubator.apache.org/servicemix/dist/servicemix-3.1-
incubating/site/tooling/jbi-maven-plugin/generate-jbi-service-unit-
descriptor-mojo.html
Just configure the generateJbiDescriptor to false on the plugin
configuration
in your pom.
Cheers,
Guillaume Nodet
On Aug 24, 2007, at 7:57 PM, netflexity wrote:
>
> [propertyPlaceholder,org.apache.servicemix.http.HttpEndpoint,org.apach
> e.servicemix.http.H
> ttpEndpoint#1,org.apache.servicemix.http.HttpEndpoint#2,org.apache.ser
> vicemix.http.HttpEndpoint#3,org.apache.servicemix.http.HttpEndpoint#4,
> org.apache.servicemix.http.HttpEndpoint#5,org.apache.servicemix.http.H
> ttpEndpoint#6];
> root of BeanFactory hierarchy}
> [INFO]
> ----------------------------------------------------------------------
> --
> [ERROR] BUILD ERROR
> [INFO]
> ----------------------------------------------------------------------
> --
> [INFO] Failed to generate jbi.xml
>
> Embedded error: Unable to generate service unit descriptor!
> Need to specify class name in environment or system property, or as an
> applet parameter, or in an application resource file:
> java.naming.factory.initial
>
>
>
> bsnyder wrote:
>>
>> On 8/24/07, netflexity <mf...@netflexity.com> wrote:
>>>
>>> Hello.
>>> I am using Spring propertyPlaceholder to externalize various
>>> component
>>> configurations and successful if they are in the same src/main/
>>> resources
>>> directory. Moreover, I have no problems doing the same with config
>>> resources
>>> in JNDI (sample below), except for http-su and jms-su that
>>> complain about
>>> JNDI factory.initial System properties during Maven build. Any
>>> ideas?
>>
>> Can you post the error you're seeing regarding this?
>>
>> Bruce
>> --
>> perl -e 'print
>> unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
>> );'
>>
>> Apache ActiveMQ - http://activemq.org/
>> Apache ServiceMix - http://servicemix.org/
>> Apache Geronimo - http://geronimo.apache.org/
>> Castor - http://castor.org/
>>
>>
>
> --
> View this message in context: http://www.nabble.com/Externalizing-
> configurations-to-JNDI-for-http-su-and-jms-su-does-not-work.-
> tf4324128s12049.html#a12317129
> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>
Re: Externalizing configurations to JNDI for http-su and jms-su
does not work.
Posted by netflexity <mf...@netflexity.com>.
[propertyPlaceholder,org.apache.servicemix.http.HttpEndpoint,org.apache.servicemix.http.H
ttpEndpoint#1,org.apache.servicemix.http.HttpEndpoint#2,org.apache.servicemix.http.HttpEndpoint#3,org.apache.servicemix.http.HttpEndpoint#4,
org.apache.servicemix.http.HttpEndpoint#5,org.apache.servicemix.http.HttpEndpoint#6];
root of BeanFactory hierarchy}
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Failed to generate jbi.xml
Embedded error: Unable to generate service unit descriptor!
Need to specify class name in environment or system property, or as an
applet parameter, or in an application resource file:
java.naming.factory.initial
bsnyder wrote:
>
> On 8/24/07, netflexity <mf...@netflexity.com> wrote:
>>
>> Hello.
>> I am using Spring propertyPlaceholder to externalize various component
>> configurations and successful if they are in the same src/main/resources
>> directory. Moreover, I have no problems doing the same with config
>> resources
>> in JNDI (sample below), except for http-su and jms-su that complain about
>> JNDI factory.initial System properties during Maven build. Any ideas?
>
> Can you post the error you're seeing regarding this?
>
> Bruce
> --
> perl -e 'print
> unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
> );'
>
> Apache ActiveMQ - http://activemq.org/
> Apache ServiceMix - http://servicemix.org/
> Apache Geronimo - http://geronimo.apache.org/
> Castor - http://castor.org/
>
>
--
View this message in context: http://www.nabble.com/Externalizing-configurations-to-JNDI-for-http-su-and-jms-su-does-not-work.-tf4324128s12049.html#a12317129
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: Externalizing configurations to JNDI for http-su and jms-su does not work.
Posted by Bruce Snyder <br...@gmail.com>.
On 8/24/07, netflexity <mf...@netflexity.com> wrote:
>
> Hello.
> I am using Spring propertyPlaceholder to externalize various component
> configurations and successful if they are in the same src/main/resources
> directory. Moreover, I have no problems doing the same with config resources
> in JNDI (sample below), except for http-su and jms-su that complain about
> JNDI factory.initial System properties during Maven build. Any ideas?
Can you post the error you're seeing regarding this?
Bruce
--
perl -e 'print unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
);'
Apache ActiveMQ - http://activemq.org/
Apache ServiceMix - http://servicemix.org/
Apache Geronimo - http://geronimo.apache.org/
Castor - http://castor.org/