-
15. Re: Pulling security out as a separate module
anil.saldhana Apr 22, 2008 10:09 AM (in response to anil.saldhana)http://wiki.jboss.org/wiki/DevEJB3RunningUnitTests
Does this wiki page still hold true for running the ejb3 unit tests? -
16. Re: Pulling security out as a separate module
alrubinger Apr 22, 2008 10:13 AM (in response to anil.saldhana)"anil.saldhana@jboss.com" wrote:
It was added to core/jboss-ejb3-client.xml. I am not creating a separate jar with 2-3 classes, even if it means an imperfect world.
That's fine, but in the future we cannot assume that the classes marked for inclusion are checked out alongside core. ie:<fileSet> <directory>../security/target/classes</directory>
I'll take that task this time around, FYI. :)
http://jira.jboss.com/jira/browse/EJBTHREE-1308
S,
ALR -
17. Re: Pulling security out as a separate module
alrubinger Apr 22, 2008 10:47 AM (in response to anil.saldhana)"anil.saldhana@jboss.com" wrote:
http://wiki.jboss.org/wiki/DevEJB3RunningUnitTests
Does this wiki page still hold true for running the ejb3 unit tests?
Yes.
S,
ALR -
18. Re: Pulling security out as a separate module
anil.saldhana Apr 22, 2008 1:48 PM (in response to anil.saldhana)Additionally, in the poms and .classpath, security should be referencing org.jboss.security.jboss-security-spi and org.jboss.security.jbosssx and not their components (identity-spi, identity-impl, jboss-security-spi-bare etc).
-
19. Re: Pulling security out as a separate module
anil.saldhana Apr 22, 2008 11:15 PM (in response to anil.saldhana)"jesper.pedersen" wrote:
I have committed an update version, since inner interfaces and inner classes wasn't included.
Can you go through it and see which are actually needed ?
Jesper, I think the helpers folder that contains an EJBContextHelper is not needed. That is server side. -
20. Re: Pulling security out as a separate module
jesper.pedersen Apr 23, 2008 4:05 AM (in response to anil.saldhana)I've removed the helpers from the jboss-ejb3-core-client file.
-
21. Re: Pulling security out as a separate module
anil.saldhana May 5, 2008 9:58 AM (in response to anil.saldhana)The EJB3 Security Layer in AS5 does not (should not) make use of the old aspects/security code base. What this means is that all the deleted classes in aspects/security need to be brought back (as Kabir said there may be users using the classes).
http://wiki.jboss.org/wiki/AOPSecurity
The moral of the story is I did not write these aspect classes and I do not want to support them going forward. The AOP team should handle any questions on the aspects/security package from a support perspective. -
22. Re: Pulling security out as a separate module
starksm64 May 5, 2008 5:09 PM (in response to anil.saldhana)Then we need to create a security aspects project in the security set of projects and do drop these obsolete classes. The only users would be aop remoting users that are including these into the proxy configurations. There is a trivial usage in the profileservice proxy that can be updated once a suitable replacement is available.