NachrichtFirst I am using JBoss version 3.0.6.
I have created a service in JBoss.NET and a Java client
works fine with Basic Auth. However an MS Client fails.
After searching all groups etc. I read something that
MS .NET must receive an HTTP 401 auth failed, first
and then on all calls after
What is the best way to secure an MBean by
each operation. I want to restrict some users to
read only ops and allow some to do write/mod ops.
I read through the spec and did some research
and most of the security is at the agent.
I would like to have security at the MBean.
My idea was to use a
I know this most likely doesn't sound like the best idea.
But I need to support paging of results sets.
I was asked to allow a call to a session bean
that ends up being a jdbc query only return 100 rows
at a time.
So my first thought was to return a session bean
that implements an
Try just "ConnectionFactory".
Use JndiView from jmx console to see the new
name.
jcl.
- Original Message -
From:
G.L. Grobe
To: [EMAIL PROTECTED]
Sent: Wednesday, August 14, 2002 4:34
PM
Subject: [JBoss-user]
QueueConnectionFactory not bound
I'm getting
