Hi,

I'm interested in using Keel in an application I have to build. I am
currently in the research phase determining how best to do it. The
application will replace an old CRM app built in Filemaker for a small
stock broker / financial services provider. Custom (either expaning on the
current filemaker or rebuilding in Java) is the only choice as standard
CRM products are either too expensive, don't run on Mac and Windows or do
not have the customization capabilities that we need. Full J2EE is out of
the question due to high maintance costs and a swing client is a
requirement. Doing this as a web app is out of the question.

I will be using MySQL database + Hibernate for data persistence and Swing
GUI deployable via webstart for the client. Talking to the server
component via lightweight xml messaging and a bpm tool (my own soap
replacement).

Would keel be useable here? As far as I can see its JAAS authentication
might be very useful. I'm unfamiliar with security in general and
expecially on the swing client side. (First app to secure a swing
inteface) I need to be able to be able to secure certain fields in some
objects. For example:

class Client
 UID clientId
 String firstName
 String lastName
 Account account

I need one group to be able to view/edit/delete everything and another
group to only be able to view everything and edit everything except the
Account object. Etc etc etc.

This sort of task is easy in a webapp environment using ejb or straight
sql but I really have little idea about how to accomplish this in a
swing/hibernate architecture. I have a strong feeling that the Keel
security model might enable this?

I have searched through the wiki but have only found a couple of pages.
One saying I'd need to write my own swing module or something - how long
would this take? Does Keel have the security features I require?

Regards,
Willie Seabrook

http://keelframework.org/documentation
Keelgroup mailing list
[EMAIL PROTECTED]
http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com

Reply via email to