Production environment runs on my client's server. Development
environment runs on my computer.
My client has multiple users. He wants to change and add new printers
but he does not want to rebuild the application every time printer
details change.
What I am trying to do is to apply the same pattern which has been
applied in an older application running in cocoon-2.0. In that
application there is one Printers.xml file for all users and it
contains information about printers (for example which render to use:
pcl or postscript). User selects some processing parameters and a
printer and submits a batch job as a jms request. The request goes to
jms server which does the processing and prints the results on user's
printer.
The new cocoon-2.2.0 application is sending jms requests - this works
ok. Now I need to add printers. Of course I could put the printers
into the database but I prefer to stay with xml file.
Barbara
On 1 Jul, 2009, at 9:26 am, Bart Remmerie wrote:
Where is the server running ?
Are there multiple clients running on one server ? Or is the server
running @ the client ?
Bart
On Wed, Jul 1, 2009 at 9:21 AM, Barbara
Slupik<[email protected]> wrote:
Hello
I am using cocoon-2.2.0. I want to define an xml file with printers
configuration. This file should be outside application jar because
my client
will configure his own printers there. Printers defined in the xml
file will
be displayed on one of the application screens so that user can
select a
printer from the list. Is it possible to do? How?
Barbara
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
--
Bart Remmerie
+32 (0477) 78.88.76
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
