Skip to main content

Thread safety and pooling in JAX-WS and Metro

1 reply [Last post]
Anonymous

Hi,

Which JAX-WS components are safe to share between threads? A Service? A port
proxy? I'm interested in knowing both what the spec promises, and what Metro
actually delivers. I've dug up these discussions:

https://jax-ws.dev.java.net/servlets/BrowseList?list=dev&by=thread&from=...
https://jax-ws.dev.java.net/servlets/BrowseList?list=dev&by=thread&from=...
http://forums.java.net/jive/thread.jspa?threadID=18756

But none of them give a definite answer. Do i need to create a fresh Service
for each thread? Or can i share a service and create a fresh port/proxy for
each thread? Or can i just use a single global port/proxy?

If there are components which can't be shared, are there any facilities for
pooling them inside an application server? Either generic to all J2EE
appservers, or specific to JBoss, since that's what we're using. I've looked
through:

http://community.jboss.org/wiki/Jbossws-userguide
http://community.jboss.org/wiki/JBossWS-StackMetroUserGuide

And there's nothing about pooling.

Thanks in advance,
tom

--
Tom Anderson | e2x Ltd, 8 Elder Street, London E1 6BT
(e) tom.anderson@e2x.co.uk | (m) +44 (7960) 989794 | (f) +44 (20) 7194 8016

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@metro.dev.java.net
For additional commands, e-mail: users-help@metro.dev.java.net

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
markus_franke
Offline
Joined: 2007-10-10
Points: 0