JBoss 4.0.4-CR2
base class:
| package test.ws.a;
|
| public class BaseResponse {}
|
derived class (notice that it is in a different package):
| package test.ws.b;
| import test.ws.a.BaseResponse;
| public class StandardResponse extends BaseResponse {}
|
| package test.ws;
| env.setProperty(Context.SECURITY_CREDENTIALS, "userName");
| env.setProperty(Context.SECURITY_PRINCIPAL, "1");
|
yes, I am a tool :D
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3896801#3896801
Reply to the post :
http://www.jboss.com/index.html?m
I'm trying to configure JAAS for a remote client calling MBeans via RMIAdaptor
server. I'm using DatabaseServerLoginModule for authentication with a DB. This
module was tested and works fine for session beans (using LoginContext).
Looking through the logs, I can see that the correct security dom
Actually, it's not as bad as I'd presented in my prior post. Only the first
call (which I'm assuming triggers the bean construction step) takes unusually
long to complete. Once the stub has been acquired and at least one call made,
it's actually very fast. Obviosuly, that warrants some design c
What sort of round trip times should I expect from a simple call to a stateless
echo style bean?
Server
| @Stateless
| @Remote({Echo.class})
| public class EchoBean implements Echo, Serializable {
| public String echo(String value) {
| return value;
| }
| }
|
