[JBoss JIRA] Moved: (SOLDER-30) Split module into API and impl
by Pete Muir (JIRA)
[ https://jira.jboss.org/browse/SOLDER-30?page=com.atlassian.jira.plugin.sy... ]
Pete Muir moved WELDX-182 to SOLDER-30:
---------------------------------------
Project: Seam Solder (was: Weld Extensions)
Key: SOLDER-30 (was: WELDX-182)
Affects Version/s: (was: 1.0.0.Beta1)
Fix Version/s: TBC
(was: TBC)
> Split module into API and impl
> ------------------------------
>
> Key: SOLDER-30
> URL: https://jira.jboss.org/browse/SOLDER-30
> Project: Seam Solder
> Issue Type: Feature Request
> Reporter: Dan Allen
> Fix For: TBC
>
>
> Before putting the seal on the first release of Weld Extensions, I think it's important to provide a clear distinction between API and impl. Especially since we have classes mentioned in the reference guide which are in the impl source tree. We can still consider shipping a shaded JAR, but the API would be the only part that has a published API doc.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months
[JBoss JIRA] Moved: (SOLDER-16) Java based DSL configuration of BeanDeploymentArchive
by Pete Muir (JIRA)
[ https://jira.jboss.org/browse/SOLDER-16?page=com.atlassian.jira.plugin.sy... ]
Pete Muir moved WELDX-37 to SOLDER-16:
--------------------------------------
Project: Seam Solder (was: Weld Extensions)
Key: SOLDER-16 (was: WELDX-37)
Assignee: (was: Takeshi Kondo)
> Java based DSL configuration of BeanDeploymentArchive
> -----------------------------------------------------
>
> Key: SOLDER-16
> URL: https://jira.jboss.org/browse/SOLDER-16
> Project: Seam Solder
> Issue Type: Feature Request
> Reporter: Takeshi Kondo
> Priority: Minor
> Attachments: dsl-configuration-impl-testcase.patch, dsl-configuration-impl.patch, dsl-configuration-interface.patch, dsl-configuration-test-case.patch, dsl-test.patch, dsl.patch
>
>
> In test environment ,I frequently change configuration.
> ClssLoader scan is convenience , but it is laggardly and not flexible.
> Alternatively , I'd created new BeanDeploymentArchive which loads Java based DSL configuration.
> sample is as follows.
> -------
> > Java based DSL Configuration
> class TestBeanModule extends BeanModuleBase
> {
> @Override
> protected void configure()
> {
> bean(TestBean.class);
> }
> }
> -------
> > TestCase
> @Test(groups = "bootstrap")
> public void testBeanModule()
> {
> new ModuleTest(new TestBeanModule())
> {
> @Override
> protected void test()
> {
> BeanManagerImpl manager = CurrentManager.rootManager();
> assert manager.getInstanceByType(TestBean.class) != null;
> }
> };
> }
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months