on ‎2006 Oct 04 9:00 AM
Hi all
I am making an application using CAF. My application has some properties which are used to control the application.
I can store these properties and their values in XML file and can use it in my application. Is there any other way to handle this in CAF?
Request clarification before answering.
Using Application Configuration functionality you can easily handle your properties in user safe way: Visual Admin -> Server -> Services -> Configuration Adapter -> Configurations -> apps -> sap.com -> <your_caf_app> -> appcfg -> Propertysheet application.global.properies. Also you can import/export configurations.
Using CAF entity for configuration storage requires additional implementation effort.
Also, main disadvantage of this approach in my view is default configuration values support. Surely, you can create additional project with type dbcontent but that is unjustified effort in comparison with Application Configuration functionality.
Finally, ejb usage for application configuration storage in the same application looks like a workaround but not a solution.
Best reagrds,
Aliaksei
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I think i need to explain my requirement little more. In my application, I have some set of rules which are used to control application. These rules can be changed over a time. So I need some way to maintain them easily.
Rules are like this:
Assume I have Three property say A,B and C.
now if A = X and B = Y then C = Z
I can make a database table with A and B as key fields. But I don't know whether it is an efficient way to handle this.
Yes, there are some disadvantages to using the Entity Service for this. One advantage of using an Entity Service over a properties file is that you can easily build a CAF ui pattern or VC UI on top of it (also the default service browser). This could be more user friendly than the J2EE Visual Admin and be incorporated into your application. True, you could build a custom UI on top of the j2ee properties, but this would be extra effort.
| User | Count |
|---|---|
| 8 | |
| 6 | |
| 4 | |
| 3 | |
| 3 | |
| 3 | |
| 3 | |
| 2 | |
| 2 | |
| 2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.