Update: solved! :-)

On Tue, Aug 18, 2009 at 3:45 PM, Will
Scheidegger<[email protected]> wrote:
> Looks to me like you don't have a public instance installed in the first
> place.

Right. Do I really need "magnoliaAuthor" or it can be just "magnolia"?
So far it works, but will I step on some kind of rake in a future?

> So what you'll need to do: Take the magnolia-bundeled-4.1.war (or whatever
> its exact name is), rename it to magnoliaPublic.war, place it in the webapps
> folder and launch Glassfish. At this time (when called "magnoliaPublic")
> this instance will be installed as magnoliaPublic instance. Check the log
> for additional info.

Thanks, Will! Yes, you were right: all I needed to do, is just deploy
it as "magnoliaPublic" one more time. Now everything FUBAR. :-)
So Magnolia now works for me great (so far). Just for a record:

— OpenSolaris 2009.06
— Sun Java 1.6.13
— GlassFish v2.1

That specific login module is kinda strange thing and it has to be
optional, IMO. In GlassFish you have a full-blown login infra that in
my case works with OpenDS (LDAP). Would be nice to say Magnolia use
other than its own login modules. Maybe it is even possible already, I
just don't know yet...

So far just works fine on setup above. Thanks again, Will!

-- 
Kind regards, BM

Things, that are stupid at the beginning, rarely ends up wisely.

----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------

Reply via email to