Results 1 to 6 of 6

Thread: Acegi Rebranding??

  1. #1
    Join Date
    Sep 2006
    Location
    UK
    Posts
    8,424

    Default Acegi Rebranding??

    The Spring 2.0 article by Rod was quite interesting. I would be interested to know more about the Acegi rebranding however. What exactly is this going to entail? The name changes, ok fine. What about package names? What sort of timeframe are we looking at? Is this just going to be a name change, or is the product going to be more closely aligned with the other Spring projects? e.g. SpringWS, SpringLDAP, etc... Are we going to see more Spring like behaviour e.g. being able to inject MappingSqlQuery objects into JdbcDaoImpl instead of having to extend it.

    If anyone has any answers, it would be greatly appreciated!

    Many products build on Spring, and their configuration can become simpler using namespaces. A good example is Acegi Security for Spring (to be rebranded Spring Security in early 2007), which requires the definition of several collaborating beans to configure. A Spring 2.0 namespace will make this much simpler.-again, more clearly expressing the intent.
    http://www.infoq.com/articles/spring-2-intro

  2. #2

    Default

    thanks..I posted the question too as a comment on that article

  3. #3
    Join Date
    Sep 2006
    Location
    UK
    Posts
    8,424

    Default

    Ahhh indeed . I've only got half way through it so I hadn't read the comments, apologies. Atleast I wasn't the only one wondering what that statement actually means......... I also emailed the same question to the Acegi Developer Mailing List.

  4. #4
    Join Date
    Sep 2006
    Location
    UK
    Posts
    8,424

    Default

    For anyone that doesn't subscribe to the Acegi developer mailing list......
    Message: 5
    Date: Sun, 21 Jan 2007 12:01:44 -0600
    From: "Mark St.Godard" <markstgodard@gmail.com>
    Subject: Re: [Acegisecurity-developer] Acegi Rebranding??

    I asked the same question to Rod @ TSE, as well talked with Ben....and there is no immediate intention to change the source codepackaging, rather its an explicit rebranding to reflect that it is apart of the Spring portfolio. Also this keys into the "release train" concept discussed at TSE...basically a coordinated release among the Spring projects proper Ben can chime in as well.... if he would like to add to this..

    Cheers
    Mark

  5. #5

    Default

    nice thanks

  6. #6
    Join Date
    Sep 2006
    Location
    UK
    Posts
    8,424

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •