You don't add the jbossesb-properties.xml to an .esb package. There is only 1 and it goes in the jbossesb.sar. Tom Fennelly wrote: > Hi guys. > > I was having an issue which had all the hallmarks of the > PropertyManager not being able to find the jbossesb-properties.xml. > As it turned out, it was finding "one", but not the "one" in the .esb > archive (the TB uses the PropertyManager for properties). Instead, > it's picking up the jbossesb-properties.xml from the jbossesb.sar. > Any suggestions for a fix for this? I can hack it by getting the TB > deplyment to overwrite the jbossesb.sar version for the file, but > that's poo :-) I also tried scoping the .esb, but it didn't work (is > this disabled now Bill?). > > T. > _______________________________________________ > esb-dev mailing list > esb-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/esb-dev >

Well the TB adds some custom extentions. What if we add those extensions to a "trailblazer.properties" file? And then read just those? That be much cleaner. The jbossesb.properties.xml is really server wide. Tom Fennelly wrote: > Hmmmm, that's not a great solution really, is it?? It then means > that all ESB deployments that use the PropertyManager for > properties share the same config file. > > I'll work on the basis that this is a fact of life - the TB will > overwrite the .sar version (dodgy). > > T. > > > Kurt T Stam wrote: >> You don't add the jbossesb-properties.xml to an .esb package. >> There is >> only 1 and it goes in the jbossesb.sar. >> >> Tom Fennelly wrote: >> >>> Hi guys. >>> >>> I was having an issue which had all the hallmarks of the >>> PropertyManager not being able to find the jbossesb-properties.xml. >>> As it turned out, it was finding "one", but not the "one" in >>> the .esb >>> archive (the TB uses the PropertyManager for properties). Instead, >>> it's picking up the jbossesb-properties.xml from the jbossesb.sar. >>> Any suggestions for a fix for this? I can hack it by getting >>> the TB >>> deplyment to overwrite the jbossesb.sar version for the file, but >>> that's poo :-) I also tried scoping the .esb, but it didn't >>> work (is >>> this disabled now Bill?). >>> >>> T. >>> _______________________________________________ >>> esb-dev mailing list >>> esb-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/esb-dev >>> >> _______________________________________________ esb-dev mailing list esb-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/esb-dev

I agree with this strategy. The TB as an end-user example app shouldn't be taking advantage of ESB "internals" like the property manager used to keep the bus itself wired together properly. Kurt T Stam wrote: > Well the TB adds some custom extentions. What if we add those > extensions to a "trailblazer.properties" file? And then read just > those? > That be much cleaner. The jbossesb.properties.xml is really server > wide. > > Tom Fennelly wrote: >> Hmmmm, that's not a great solution really, is it?? It then means >> that all ESB deployments that use the PropertyManager for >> properties share the same config file. >> >> I'll work on the basis that this is a fact of life - the TB will >> overwrite the .sar version (dodgy). >> >> T. >> >> >> Kurt T Stam wrote: >>> You don't add the jbossesb-properties.xml to an .esb package. >>> There is >>> only 1 and it goes in the jbossesb.sar. >>> >>> Tom Fennelly wrote: >>> >>>> Hi guys. >>>> >>>> I was having an issue which had all the hallmarks of the >>>> PropertyManager not being able to find the jbossesb- >>>> properties.xml. As it turned out, it was finding "one", but not >>>> the "one" in the .esb >>>> archive (the TB uses the PropertyManager for properties). >>>> Instead, >>>> it's picking up the jbossesb-properties.xml from the jbossesb.sar. >>>> Any suggestions for a fix for this? I can hack it by getting >>>> the TB >>>> deplyment to overwrite the jbossesb.sar version for the file, but >>>> that's poo :-) I also tried scoping the .esb, but it didn't >>>> work (is >>>> this disabled now Bill?). >>>> >>>> T. >>>> _______________________________________________ >>>> esb-dev mailing list >>>> esb-dev(a)lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/esb-dev >>>> >>> >>> > --------------------------------------------------------------------- > --- > > _______________________________________________ > esb-dev mailing list > esb-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/esb-dev > _______________________________________________ esb-dev mailing list esb-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/esb-dev

Let's work on your current assumption for this release. The file is located via the classloader, so presumably because the lookup is occurring within code in the jbossesb.sar, it'll bind to that file to the exclusion of all others. Mark. On 22 Mar 2007, at 17:54, Tom Fennelly wrote: > Hmmmm, that's not a great solution really, is it?? It then means that > all ESB deployments that use the PropertyManager for properties share > the same config file. > > I'll work on the basis that this is a fact of life - the TB will > overwrite the .sar version (dodgy). > > T. > > > Kurt T Stam wrote: >> You don't add the jbossesb-properties.xml to an .esb package. There is >> only 1 and it goes in the jbossesb.sar. >> >> Tom Fennelly wrote: >> >>> Hi guys. >>> >>> I was having an issue which had all the hallmarks of the >>> PropertyManager not being able to find the jbossesb-properties.xml. >>> As it turned out, it was finding "one", but not the "one" in the .esb >>> archive (the TB uses the PropertyManager for properties). Instead, >>> it's picking up the jbossesb-properties.xml from the jbossesb.sar. >>> Any suggestions for a fix for this? I can hack it by getting the TB >>> deplyment to overwrite the jbossesb.sar version for the file, but >>> that's poo :-) I also tried scoping the .esb, but it didn't work (is >>> this disabled now Bill?). >>> >>> T. >>> _______________________________________________ >>> esb-dev mailing list >>> esb-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/esb-dev >>> >> > _______________________________________________ > esb-dev mailing list > esb-dev(a)lists.jboss.org <mailto:esb-dev@lists.jboss.org> > https://lists.jboss.org/mailman/listinfo/esb-dev ------------------------------------------------------------------------ _______________________________________________ esb-dev mailing list esb-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/esb-dev

ESB deployments should *not* be using a properties file for configuration, IMO. Tom Fennelly wrote: > Hmmmm, that's not a great solution really, is it?? It then means > that all ESB deployments that use the PropertyManager for properties > share the same config file. > > I'll work on the basis that this is a fact of life - the TB will > overwrite the .sar version (dodgy). > > T. > > > Kurt T Stam wrote: >> You don't add the jbossesb-properties.xml to an .esb package. There is >> only 1 and it goes in the jbossesb.sar. >> >> Tom Fennelly wrote: >> >>> Hi guys. >>> >>> I was having an issue which had all the hallmarks of the >>> PropertyManager not being able to find the jbossesb-properties.xml. >>> As it turned out, it was finding "one", but not the "one" in the .esb >>> archive (the TB uses the PropertyManager for properties). Instead, >>> it's picking up the jbossesb-properties.xml from the jbossesb.sar. >>> Any suggestions for a fix for this? I can hack it by getting the TB >>> deplyment to overwrite the jbossesb.sar version for the file, but >>> that's poo :-) I also tried scoping the .esb, but it didn't work (is >>> this disabled now Bill?). >>> >>> T. >>> _______________________________________________ >>> esb-dev mailing list >>> esb-dev(a)lists.jboss.org <mailto:esb-dev@lists.jboss.org> >>> https://lists.jboss.org/mailman/listinfo/esb-dev >>> >> > > ------------------------------------------------------------------------ > > _______________________________________________ > esb-dev mailing list > esb-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/esb-dev

TB is? Well, switch it to use a regular properties file. BTW, I can't stand these Arjuna property files to begin with. WE need to junk them accross the board. Tom Fennelly wrote: > I agree, but the TB is already written to use it. > > Bill Burke wrote: >> ESB deployments should *not* be using a properties file for >> configuration, IMO. >> >> Tom Fennelly wrote: >>> Hmmmm, that's not a great solution really, is it?? It then means >>> that all ESB deployments that use the PropertyManager for >>> properties share the same config file. >>> >>> I'll work on the basis that this is a fact of life - the TB will >>> overwrite the .sar version (dodgy). >>> >>> T. >>> >>> >>> Kurt T Stam wrote: >>>> You don't add the jbossesb-properties.xml to an .esb package. >>>> There is >>>> only 1 and it goes in the jbossesb.sar. >>>> >>>> Tom Fennelly wrote: >>>> >>>>> Hi guys. >>>>> >>>>> I was having an issue which had all the hallmarks of the >>>>> PropertyManager not being able to find the >>>>> jbossesb-properties.xml. As it turned out, it was finding "one", >>>>> but not the "one" in the .esb >>>>> archive (the TB uses the PropertyManager for properties). Instead, >>>>> it's picking up the jbossesb-properties.xml from the jbossesb.sar. >>>>> Any suggestions for a fix for this? I can hack it by getting the TB >>>>> deplyment to overwrite the jbossesb.sar version for the file, but >>>>> that's poo :-) I also tried scoping the .esb, but it didn't work >>>>> (is >>>>> this disabled now Bill?). >>>>> >>>>> T. >>>>> _______________________________________________ >>>>> esb-dev mailing list >>>>> esb-dev(a)lists.jboss.org <mailto:esb-dev@lists.jboss.org> >>>>> https://lists.jboss.org/mailman/listinfo/esb-dev >>>>> >>>> >>> >>> ------------------------------------------------------------------------ >>> >>> >>> _______________________________________________ >>> esb-dev mailing list >>> esb-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/esb-dev >>

TB is? Well, switch it to use a regular properties file. BTW, I can't stand these Arjuna property files to begin with. WE need to junk them accross the board. Tom Fennelly wrote: > I agree, but the TB is already written to use it. > Bill Burke wrote: >> ESB deployments should *not* be using a properties file for >> configuration, IMO. >> >> Tom Fennelly wrote: >>> Hmmmm, that's not a great solution really, is it?? It then >>> means that all ESB deployments that use the PropertyManager for >>> properties share the same config file. >>> >>> I'll work on the basis that this is a fact of life - the TB will >>> overwrite the .sar version (dodgy). >>> >>> T. >>> >>> >>> Kurt T Stam wrote: >>>> You don't add the jbossesb-properties.xml to an .esb package. >>>> There is >>>> only 1 and it goes in the jbossesb.sar. >>>> >>>> Tom Fennelly wrote: >>>> >>>>> Hi guys. >>>>> >>>>> I was having an issue which had all the hallmarks of the >>>>> PropertyManager not being able to find the jbossesb- >>>>> properties.xml. As it turned out, it was finding "one", but >>>>> not the "one" in the .esb >>>>> archive (the TB uses the PropertyManager for properties). >>>>> Instead, >>>>> it's picking up the jbossesb-properties.xml from the >>>>> jbossesb.sar. >>>>> Any suggestions for a fix for this? I can hack it by getting >>>>> the TB >>>>> deplyment to overwrite the jbossesb.sar version for the file, but >>>>> that's poo :-) I also tried scoping the .esb, but it didn't >>>>> work (is >>>>> this disabled now Bill?). >>>>> >>>>> T. >>>>> _______________________________________________ >>>>> esb-dev mailing list >>>>> esb-dev(a)lists.jboss.org <mailto:esb-dev@lists.jboss.org> >>>>> https://lists.jboss.org/mailman/listinfo/esb-dev >>>>> >>>> >>> >>> ------------------------------------------------------------------- >>> ----- >>> >>> _______________________________________________ >>> esb-dev mailing list >>> esb-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/esb-dev >> -- Bill Burke JBoss, a division of Red Hat Inc. _______________________________________________ esb-dev mailing list esb-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/esb-dev

I'm going to check in what I have with the TB using the PropertyManager (as it always has). Will then look at changing it over to use a good old .properties file :-) I'd hoped I wouldn't have to make changes right across its codebase, but ... T. Mark Little wrote: > Property files? There's only one. Introducing it into the current > codebase simplified a lot of stuff at the time, but it was just a > stop-gap until we have better service configuration via the > microcontainer and friends. > > Mark. > > > On 22 Mar 2007, at 18:07, Bill Burke wrote: > >> TB is? Well, switch it to use a regular properties file. BTW, I >> can't stand these Arjuna property files to begin with. WE need >> to junk them accross the board. >> >> Tom Fennelly wrote: >>> I agree, but the TB is already written to use it. >>> Bill Burke wrote: >>>> ESB deployments should *not* be using a properties file for >>>> configuration, IMO. >>>> >>>> Tom Fennelly wrote: >>>>> Hmmmm, that's not a great solution really, is it?? It then >>>>> means that all ESB deployments that use the PropertyManager >>>>> for properties share the same config file. >>>>> >>>>> I'll work on the basis that this is a fact of life - the TB >>>>> will overwrite the .sar version (dodgy). >>>>> >>>>> T. >>>>> >>>>> >>>>> Kurt T Stam wrote: >>>>>> You don't add the jbossesb-properties.xml to an .esb package. >>>>>> There is >>>>>> only 1 and it goes in the jbossesb.sar. >>>>>> >>>>>> Tom Fennelly wrote: >>>>>> >>>>>>> Hi guys. >>>>>>> >>>>>>> I was having an issue which had all the hallmarks of the >>>>>>> PropertyManager not being able to find the jbossesb- >>>>>>> properties.xml. As it turned out, it was finding "one", but >>>>>>> not the "one" in the .esb >>>>>>> archive (the TB uses the PropertyManager for properties). >>>>>>> Instead, >>>>>>> it's picking up the jbossesb-properties.xml from the >>>>>>> jbossesb.sar. >>>>>>> Any suggestions for a fix for this? I can hack it by >>>>>>> getting the TB >>>>>>> deplyment to overwrite the jbossesb.sar version for the >>>>>>> file, but >>>>>>> that's poo :-) I also tried scoping the .esb, but it didn't >>>>>>> work (is >>>>>>> this disabled now Bill?). >>>>>>> >>>>>>> T. >>>>>>> _______________________________________________ >>>>>>> esb-dev mailing list >>>>>>> esb-dev(a)lists.jboss.org <mailto:esb-dev@lists.jboss.org> >>>>>>> https://lists.jboss.org/mailman/listinfo/esb-dev >>>>>>> >>>>>> >>>>> >>>>> ----------------------------------------------------------------- >>>>> ------- >>>>> >>>>> _______________________________________________ >>>>> esb-dev mailing list >>>>> esb-dev(a)lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/esb-dev >>>> >> >> --Bill Burke >> JBoss, a division of Red Hat Inc. >> _______________________________________________ >> esb-dev mailing list >> esb-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/esb-dev >