[
https://issues.apache.org/jira/browse/OWB-126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gurkan Erdogdu closed OWB-126.
------------------------------
Resolution: Fixed
Fix Version/s: (was: M3)
M4
Now we have two types of XML configuration. OWB Specific and spec. defined.
> remove old rules and formattings for handling of beans.xml
> ----------------------------------------------------------
>
> Key: OWB-126
> URL: https://issues.apache.org/jira/browse/OWB-126
> Project: OpenWebBeans
> Issue Type: Bug
> Affects Versions: M2
> Reporter: Mark Struberg
> Assignee: Mark Struberg
> Fix For: M4
>
>
> In the 'old' spec version, the XML based configuration was defined down to a
> very detailed level.
> Since then the spec has been changed heavily and now doesn't say much about
> XML configuration in general. There is no explicit XML section and beans.xml
> is only mentioned a few times:
> 1. policies
> {noformat}
> <beans>
> <policies>
> <class>org.mycompany.mock.MockAsynchronousService</class>
> <stereotype>org.mycompany.myfwk.Mock</stereotype>
> <stereotype>org.mycompany.site.Australian</stereotype>
> </policies>
> </beans>
> {noformat}
> 2. decorators
> {noformat}
> <beans>
> <decorators>
> <class>org.mycompany.myfwk.TimestampLogger</class>
> <class>org.mycompany.myfwk.IdentityLogger</class>
> </decorators>
> </beans>
> {noformat}
> 3. interceptors
> {noformat}
> <beans>
> <interceptors>
> <class>org.mycompany.myfwk.TransactionInterceptor</class>
> <class>org.mycompany.myfwk.LoggingInterceptor</class>
> </interceptors>
> </beans>
> {noformat}
> There is obviously no forced namespace anymore, which currently breaks most
> of the TCK tests.
> But I expect a lot more things need to be rewritten.
> My personal opinion is that we should _not_ remove the whole XML
> configuration stuff which we already have. It is not in the spec anymore, but
> it is a feature one needs in praxis. Anyway it has no high priority and we
> have to find our own syntax until a homogenic XML configuration will be
> aggreed upon in the next webbeans spec.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
