Ok. Thanks a lot!
"[EMAIL PROTECTED]" wrote :
| The Seam policy is for the question "how do I know the user/password typed
in
| by the user is correct?". Your answer such be a real validation mechanism
| NOT "use what is already established on thread" which is most likely
nothing. :-)
|
On the application policy.
The datasource properties and the createConnection(user, password)
are ignored if you are using container managed security.
Confusing, but It's in the JCA spec. :-)
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4063840#4063840
Rep
I catch the policy question-answer thing, thanks:-) Good to hear that I'm step
further.
"[EMAIL PROTECTED]" wrote :
| You don't have a default user/password for such contexts..
|
Where can I set default user/password that can be used during deployment? In
the datasource file:
|
|
One "belt and braces" way to do it (if you want further guidance ask in the
security forum)
is to not deploy your application via hot deployment.
Instead you would deploy an mbean that does the deployment programmatically.
e.g. something like (pseudo code)
| public class DeployWebApp implemen
I'm going to bounce you around. ;-)
The problem you have is really a Seam problem.
That's because you already solved the problem you were trying to solve.
JCA SIDE
The configuration you have looks correct to me,
provided you are running in a context where somebody has logged in.
You don't have a
