[CONF] Apache CXF 2.0 Documentation: Configuration for Developers (page edited)

[confluence]

Page Edited : CXF20DOC : Configuration for Developers Configuration for Developers has been edited by Dan Diephouse (Feb 19, 2007). (View changes) Content: How Configuration works in CXF TODO Rules of Configuration Please follow the following guidelines when writing configuration related code in CXF. 1. Keep in mind all your users. We have three configuration scenarios that we worry about. 1. Spring 2.0 Configuration Files 2. API users 3. Configuration embedded in the WSDL 2. Don't hide configuration objects in private fields, make it available via the API Remember that a lot of users won't touch XML configuration. Example: a user creates a Client and they want to change the proxy server. We should make this as easy as possible instead of forcing them to use XML or navigate a bunch of objects. 3. Use new namespaces sparingly When users write configuration for a component they don't want to have to worry if its in one namespace or the other. For instance, instead of dividing JMS configuration into many different namespaces, use just one so users only need to add one namespace to their configuration file. 4. When writing XML schemas start elements and attributes with lower case letters Instead of "<Conduit ConnectionTimeout="300">" we prefer "<conduit connectionTimeout="300">" 5. Don't create redundant schema names If you are writing a JMS transport schema, don't name your type "jmsConduit". Instead name it just "conduit". The schema type will already be in the JMS namespace so "jmsConduit" is overly redundant. Example: <jms:conduit.../> and not <jms:jmsConduit.../> 6. If your component does not need to be configured via WSDL, write your component as a bean and then just write a Spring 2.0 schema for it.

Powered by Atlassian Confluence (Version: 2.2.9 Build:#527 Sep 07, 2006) - Bug/feature request

Unsubscribe or edit your notifications preferences