[
https://issues.apache.org/jira/browse/OPENEJB-827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12616711#action_12616711
]
karan singh malhi commented on OPENEJB-827:
-------------------------------------------
Here are the ones users might care about from openejb-core:
openejb.authentication.realmName
openejb.base
openejb.configuration
openejb.deploymentId.format
openejb.deployments.classpath
openejb.deployments.classpath.ear
openejb.deployments.classpath.exclude
openejb.deployments.classpath.filter.descriptors
openejb.deployments.classpath.filter.systemapps
openejb.deployments.classpath.include
openejb.deployments.classpath.require.descriptor
openejb.deployments.classpath.ear
openejb.descriptors.output
openejb.embedded.remotable
openejb.home
openejb.jndiname.failoncollision
openejb.jndiname.format
openejb.jndiname.strategy.class
openejb.localcopy
openejb.log.factory
openejb.nobanner
openejb.provider.default
openejb.validation.output.level
openejb.validation.skip
openejb.version
> Extract all properties into a separate interface
> ------------------------------------------------
>
> Key: OPENEJB-827
> URL: https://issues.apache.org/jira/browse/OPENEJB-827
> Project: OpenEJB
> Issue Type: Improvement
> Components: general
> Reporter: karan singh malhi
> Assignee: karan singh malhi
> Attachments: openejb-options-report.txt
>
>
> Currently, all properties are scattered around in code. It would be nice to
> have one interface which contains ALL properties used in the code. If new
> properties need to be added, they should be added to this interface.
> David Blevins has a regular expressions based search which could list all
> place in code where properties are declared. Once that list is published we
> could start extracting properties into a separate class.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
