| Author |
Message
|
| juanantoniomosquera |
 Posted: Tue Jun 07, 2016 7:43 am Post subject: DELETE POST |
 |
|
Novice
Joined: 28 Apr 2016
Posts: 11
|
DELETE POST
Last edited by juanantoniomosquera on Mon Jun 13, 2016 7:01 am; edited 1 time in total |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Tue Jun 07, 2016 7:47 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Possible? Yes.
Remotely anywhere near a good idea? No.
_________________
chmod -R ugo-wx / |
|
| Back to top |
|
|
| juanantoniomosquera |
| Posted: Tue Jun 07, 2016 7:53 am Post subject: ok |
|
|
Novice
Joined: 28 Apr 2016
Posts: 11
|
OK, thanks... but... Does anyone have an idea?
Thanks! |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Jun 07, 2016 8:01 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
It's a very very bad idea to do this.
Please use normal Broker methods or a database to hold configuration information.
If you want some idea of the difficulties and issues and methods of using a file like this, do a search here for JMX.
_________________
chmod -R ugo-wx / |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Jun 07, 2016 9:18 am Post subject: Re: ok |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| juanantoniomosquera wrote: |
| OK, thanks... but... Does anyone have an idea? |
Yes. Don't do it.
IIB is not WAS.
IIB flows do not read (or should not read) configuration files like Java running under WAS do.
IIB has it's own mechanisms for holding configuration information, as my most worthy associate points out. If these are insufficient for your needs use a database, again as my most worthy associate points out.
The path you've chosen leads only to pain, misery and unsupportable applications.
Just because you've put an XML file in the BAR doesn't mean it's going to get deployed anywhere to the server. A BAR is not an EAR and doesn't simply get unpacked & registered. IIB deployment is more about configuring IIB (a flow with a SOAPInput node doesn't have any code that listens on a port, just a configuration instruction for the relevant IIB listener to route traffic for that URL a certain way).
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| juanantoniomosquera |
| Posted: Tue Jun 07, 2016 11:13 pm Post subject: ok |
|
|
Novice
Joined: 28 Apr 2016
Posts: 11
|
| ok, thanks for your help. |
|
| Back to top |
|
|
| juanantoniomosquera |
| Posted: Tue Jun 07, 2016 11:55 pm Post subject: |
|
|
Novice
Joined: 28 Apr 2016
Posts: 11
|
I want to have an XML configuration file accessible from the flows, but not having to save it to an FTP or database. What own methods of broker Do you referees to UDP ?. I want to have an XML configuration file xml project and a common configuration file.
Greetings. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Jun 08, 2016 4:43 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| juanantoniomosquera wrote: |
| Do you referees to UDP ?. |
And bar file overrides. And (to some extent) user configurable services.
| juanantoniomosquera wrote: |
| I want to have an XML configuration file accessible from the flows, but not having to save it to an FTP or database ... I want to have an XML configuration file xml project and a common configuration file. |
I want an income of $100m a year and sufficient charisma to have young women flocking to me in paroxysms of lust and desire. (In fairness, with $100m a year, I may not need that much charisma).
We're both likely to be disappointed. Also your desire for an XML configuration file is about as sound as my desire for young women filled with lust & desire. Even if my dodgy heart could stand it, my wife couldn't.
What requirement are you trying to meet with this XML file. An answer along the lines of "I was told to use a common XML file for configuration" is not acceptable - what's the actual, technical requirement?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| juanantoniomosquera |
| Posted: Wed Jun 08, 2016 5:03 am Post subject: |
|
|
Novice
Joined: 28 Apr 2016
Posts: 11
|
|
| Back to top |
|
|
| juanantoniomosquera |
| Posted: Wed Jun 08, 2016 7:01 am Post subject: |
|
|
Novice
Joined: 28 Apr 2016
Posts: 11
|
| Quote: |
What requirement are you trying to meet with this XML file. An answer along the lines of "I was told to use a common XML file for configuration" is not acceptable - what's the actual, technical requirement?
|
XML configuration file for project. And configuration file common.
This file contais values of variables of functional devs for specific projects.
Thanks. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Jun 08, 2016 8:18 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
"XML Configuration file" is an implementation detail, not a technical requirement.
"A common configuration store for multiple specific projects" is a technical requirement.
Anything you deploy - *anything* - in a Bar file will go to a deeply nested location under the broker private file system locations.
These will be protected by security requirements to ensure that they can only be accessed by broker administrators.
If you want "A common configuration store for multiple specific projects that can be updated from outside the broker runtime", then you *do not want* an XML file.
_________________
chmod -R ugo-wx / |
|
| Back to top |
|
|
|
|
