[jboss-dev-forums] [Design of Security on JBoss] - Re: Split of Security Project into SPI and JBossAS Implement

[anil.saldhana@jboss.com]

  | The Security module has been moved out of JBossAS *trunk* into jbossas/projects (similar to the microcontainer).
  | 
  | What does this mean?
  | -	There are two projects? artifacts downloaded from the third party repository.  One is the Security SPI  (security-spi) and the other is the JBossAS implementation (security)
  | -	Dependent projects in jbossas will make use of the artifacts from security.  If there are any projects that have an implementation of the SPI (like the ejb3 project), then they will make additional use of security-spi artifacts.
  | 
  | What is the motivation?
  | Having a SPI allows JEMS projects as well as service integrators to provide an alternative implementation (and not necessarily use the JBossAS implementation aka jbosssx.jar)
  | 
  | Did it screw up eclipse settings?
  | I have updated the .classpath file for projects in jbossas that make use of security.  Please verify.
  | 
  | Does it affect the branches (3.2 and 4.0)
  | No
  | 
  | Is the SPI fixed?
  | Not yet. It is evolving(http://www.jboss.com/index.html?module=bb&op=viewtopic&t=81097)
  | 
  | Troubleshooting:
  | a)	If workspace does not build, nuke third party folder and do a clean build.
  | b)	Tests are failing ? inform. (http://www.jboss.com/index.html?module=bb&op=viewtopic&t=90069)
  | 
  | 

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3970452#3970452

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3970452