[Design of OSGi Integration] - Re: Facade Questions
by johnbailey
"alesj" wrote :
| Can you post javadoc?
| Not that I don't trust you, but just lazy to do own lookup. ;-)
|
| public static final int INSTALLED
|
| The bundle is installed but not yet resolved.
|
| A bundle is in the INSTALLED state when it has been installed in the Framework but is not or cannot be resolved.
|
| This state is visible if the bundle's code dependencies are not resolved. The Framework may attempt to resolve an INSTALLED bundle's code dependencies and move the bundle to the RESOLVED state.
|
Should we thrown an Exception instead? From the possible states (UNINSTALLED,INSTALLED,RESOLVED, STARTING, STOPPING, ACTIVE), INSTALLED seems to be the default. I was origionally thinking UNINSTALLED, but it is valid only after the Bundle has been uninstalled.
| public static final int UNINSTALLED
|
| The bundle is uninstalled and may not be used.
|
| The UNINSTALLED state is only visible after a bundle is uninstalled; the bundle is in an unusable state but references to the Bundle object may still be available and used for introspection.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4131908#4131908
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4131908
18 years, 1 month
[Design of JBoss Build System] - Re: JBossAS CR1 build plan
by dimitris@jboss.org
I had an interesting discussion with Brian, after the call. He made the very simple observation that until all EJB3 dependencies are identified and externalized (by introducing proper SPIs) what we are having now is a fake independent ejb3 project that complicates thing and doesn't add any real value.
1) Break ejb3 into multiple modules inside the AS codebase (i.e. as per their new ejb3 subprojects). That is, let ejb3 refactor itself into components the way they want.
2) For every other AS module EJB3 depends on, break out the portion that is API/SPI into a separate project like I did with the cluster module. Once that's done, ejb3's dependency on that module is gone.
3) Once each module dependency is gone, *then* ejb3 is really independent; that's when you pull the ejb3 modules out of the AS source tree into their own independent project.
Or else, until the dependency graph for EJB3 is properly mavenized, the project should not move outside AS, causing all this trouble and jumping through hoops.
It really boils down to priorities here (AS5 CR1 vs EJB3 externalization) in which case that looks like a sensible plan C to me.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4131903#4131903
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4131903
18 years, 1 month
[Design of JBoss ESB] - Timeboxed development schedule
by Kevin.Conner@jboss.com
We are now entering a timeboxed release process. Starting from next week we will be adhering to the following schedule
3rd March - 14th March (2 weeks)
JIRA issues will be assigned to the 4.3 release of the project. At this stage we will consider requests for new functionality.
17th March - 25th April (6 weeks)
Development work continues through this period. We will only consider additional JIRA tasks if they are definitely bug fixes, new functionality will be assigned to the next release
28th April - 9 May (2 weeks)
This period covers the final testing of the project, in readiness for the release.
If there is anything you wish to see in the next version of the project then please let us know *before* March 14th.
Thanks,
Kev
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4131902#4131902
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4131902
18 years, 1 month