I don't understand why people still put their container behind apache.
Unless you are using mod_rewrite or something like that, you don't need to
do that. It isn't like apache somehow 'protects' resin from evil doers. If
you need a load balancer, get a load balancer.
jon
On Fri, Jan 15, 2010 at
Daniel López wrote:
Hi there,
Nobody uses Resin's JMS from external applications? Do people use
other JMS solutions inside Resin?
I'll stick with OpenJMS for now, but as we already have Resin nodes
installed, I thought it would have been intesting to use them and
remove one service.
I was looking at the lastest 4.0.3 docs and it seems to indicate that
I should do this for my configuration:
web-app ... xmlns:queue=urn:my-package-path
...
jms:JmsConnectionFactory /
jms:FileQueue queue:DeliveryQueue/ Nameddelivery/Named /jms:FileQueue
queue:DeliveryListener
You may want to double check if you really have UTF-8 in your environment in
all circumstances.
Here you also depend on the character set of the source file, which is
unnecessary.
And your code could be simpler.
char[] urlset3a = {0xc0,\u00c1, // either numeric literals or unicode
escapes
