[JBoss Cache: Core Edition] - Re: Has anyone used JBC 2.x series with JBossAS 4.2.x series
by jorgemoralespou_2
This is a pity, since probably there are lots of projects in which isolating the classloaders is not desirable, and seems that introducing JBC2 breaks it all.
If I set up Class Isolation for every app I deploy, I have to bundle common core classes and model, which are stored in cache, and also start a cache for every application. This scenario for me can't work because of lots of factors, being one of them memory consumption and network traffic.
Probably it would have been beter not to keep compatibility at all, and created new package structure, that could have enabled deploying JBC2 in a probably large JBossAS 4.x base.
Now if I want to keep on with JBC, I have to stick with JBC1.4, which is not very performant for me, or wait till JBossAS 5, and migrate all my apps, which is very costy.
I wish this had been taken into account when you decided to make api incompatible JBossCache releases 1 and 2. Hope you think more on this for latter updates, seeing there is a chance that JBC3 don't make it into JBossAS 5.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4171054#4171054
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4171054
17 years, 10 months
[Security & JAAS/JBoss] - AbstractServerLogin module.logout and cached principals
by maggu
Hi all,
I am implementing a very simple web application and adding a custom class extending from the DatabaseLoginModule. All it does is extend initialize() by adding a few more variables, and extend login() by adding some checking logic before and after a call to super.login(). So, I have not modifed login() in any other way.
One thing I am doing is: 1) I log in with proper credentials (eg: john/1234), the credentials get stored in cache.
2) I login without proper password (eg: john/qqqqqq), the login method throws a FailedLoginException.
3) During this failed login exception, I am trying to remove the previously authenticated entry from the cache. I was calling AbstactServerLogin's logout() method, thinking this should do the trick, but realize that the principals Set the method looks up is different (?) from the one used in commit method.
How then , can I get back to the cached principal and remove it from the cache?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4171050#4171050
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4171050
17 years, 10 months
failure notice
by postmaster@lists.jboss.org
Hi. This is the smtp delivery program.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.
<vlad(a)quest4data.com>, sorry, no mailbox here by that name.
--- Below this line is a copy of the message.
Received: from avgw.enternet.hu ([62.68.172.229])
(envelope-sender <jboss-user(a)lists.jboss.org>)
by 207.168.43.140 with ESMTP
for <vlad(a)quest4data.com>; Mon, 18 Aug 2008 06:14:34 -0700
Received: from [192.168.48.20] ([192.168.48.20]) by 62.68.172.229 with Microsoft SMTPSVC(6.0.3790.1830)
18 Aug 2008 14:03:30 +0100
From: =?windows-1251?B?zejq7uvg6Q==?= <jboss-user(a)lists.jboss.org>
To: <vlad(a)quest4data.com>
Subject: =?windows-1251?B?z/Du8fDu9+Xt++kg7eDi7ucg8fLg6yDv8Oj36O3u6SDt5eHi4Ovu4w==?=
=?windows-1251?B?7iDz8O7m4P8g?=
Date: 18 Aug 2008 14:03:30 +0100
MIME-Version: 1.0
Content-Type: text/plain;
charset="windows-1251"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MimeOLE: Produced By Microsoft Exchange V6.5
X-SpamTest-Version: SMTP-Filter Version 3.0.0 [0274], KAS30/Release
X-SpamTest-Info: Not protected
X-Spam: Not detected
17 years, 10 months