[jboss-dev] MC+VDF Bootstrap

[Carlo de Wolf]

On 12/16/2009 10:14 PM, Bill Burke wrote:
> 1) You should be able to reuse the deployment framework to build Reloaded.
>    
In essence Reloaded is nothing more than some definition files to bring 
up VDF.
> 2) "Reloaded" purpose should be for unit testing.
>    
I disagree. Reloaded should replace JBoss AS minimal.
> 3) EJB without JPA and JNDI is useless.
>    
And JTA and Datasources. For this very reason we're splitting everything 
up. But we need a proper way to bring them back in and right now profile 
definitions aren't available yet.

On 12/16/2009 10:43 PM, Andrew Lee Rubinger wrote:
> IMO nearly everything should be reused.  Which means that if we need
> something for EJB3 Embeddable that's provided by AS, we'd first stop to
> extract it and refactor to bring in as a dependency.
>    
By that very statement Reloaded should be reused. Thus becoming the 
underlying framework for AS. This is also important for EJB 3 
Embeddable, because that one has to function within AS itself.

Carlo
> Brian Stansberry wrote:
>    
>> AIUI, the purpose of Reloaded is to support lightweight runtimes for
>> things like EJB3 standalone, right? If that's the case what you describe
>> makes perfect sense to me.
>>
>> The big concern would be that as you "grow incrementally" and add
>> functionality you'll end up redoing work that's done in the AS,
>> reinventing the wheel, etc. So in the future, don't do that! ;) What you
>> described in your first post isn't that; you're reusing stuff.
>>
>> On 12/16/2009 09:42 AM, Andrew Lee Rubinger wrote:
>>      
>>> It's this "rebuilding from scratch" approach I want to take, though I
>>> don't think it'll be a replacement for AS.  More along the lines of a
>>> parallel project.
>>>
>>> AS, for many, has come to imply:
>>>
>>> * $JBOSS_HOME file structure/layout
>>> * Standalone Distribution
>>> * Filesystem and runscript-based interface
>>>
>>> Also AS is the upstream path towards our platform/product.
>>>
>>> With a new name (Reloaded?) we can more easily shed all backwards-compat
>>> that AS has provided and grow incrementally in a community setting.
>>>
>>> S,
>>> ALR
>>>
>>> On 12/16/2009 10:30 AM, Bill Burke wrote:
>>>        
>>>> Maybe this could be done with the entire AS.  Define a new profile
>>>> slowly with the fat trimmed.  Slowly add stuff that is blessed as "main
>>>> stream".   When its done, you have AS 6.
>>>>
>>>> Carlo de Wolf wrote:
>>>>          
>>>>> My only concern is that we loose the link with AS and thus make it close
>>>>> to impossible to reintegrate. In effect it'll mean we'll have to
>>>>> refactor AS itself more extensively.
>>>>>
>>>>> Apart from that the slimmer, the better.
>>>>>
>>>>> Carlo
>>>>>
>>>>> On 12/16/2009 06:50 AM, Andrew Lee Rubinger wrote:
>>>>>            
>>>>>> @see https://jira.jboss.org/jira/browse/RELOADED-10
>>>>>>
>>>>>> In the last design call I noted one approach to building slimmer
>>>>>> runtimes was to take Carlo's notion of Reloaded, but instead of taking
>>>>>> from the AS configs get things as trim as possible and only bring up
>>>>>> what's needed for VDF/MainDeployer.  Ales was kind enough to point me to
>>>>>> some precanned stuff already used in the jboss-deployers testsuite, so I
>>>>>> stole a bunch of that and coupled it with jboss-bootstrap-impl-mc.
>>>>>>
>>>>>> The basic test is able to install a new Deployer to the chain and ensure
>>>>>> it's used when a new Deployment is deployed via MainDeployer.  Takes
>>>>>> about 1.9 seconds on my machine from JVM start to shutdown.
>>>>>>
>>>>>> http://anonsvn.jboss.org/repos/jbossas/projects/reloaded/trunk/vdf-bootstrap-minimal/src/test/java/MainDeployerUnitTest.java
>>>>>>
>>>>>> I think the next steps are as we've already discussed:
>>>>>>
>>>>>> 1) Make this into an extensible component which can be
>>>>>> reused/extended/composed
>>>>>> 2) Bring up ProfileService in another extension
>>>>>>
>>>>>> Thoughts?
>>>>>>
>>>>>> S,
>>>>>> ALR
>>>>>>
>>>>>>
>>>>>>              
>>>>> _______________________________________________
>>>>> jboss-development mailing list
>>>>> jboss-development at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/jboss-development
>>>>>            
>>
>>      
>