Java EE defines a set of roles, why not defining a set of staging so each
spec could take that into account ? I think introducing staging in JSF 2.0
was a very good idea, why not apply it to the entire platform ?
On Tue, Jun 7, 2011 at 12:13, Werner Keil <werner.keil_at_gmail.com> wrote:
> Antonio/Reza/all,
>
> Thanks a lot for the suggestions.
>
> In fact I am just in a (pre-EE6 but we use some Spring and e.g. JPA2)
> project where deployment to multiple stages of their own "cloud" plays a
> very important role, too.
>
> Just now giving tables based on JPA2 entities potentially different names
> in different environments is one interesting challenge. This is where
> strictly annotation-based configuration becomes hard to use in real life,
> although JPA is among the EE standards where still most of these attributes
> can still be configured in other places, XML files primarily.
>
> JSF is another area where the "ProjectStage" enum was a good idea in the
> right direction, but no Enterprise project I ever saw simply has these few
> stages, nor do they ever have the same names. Testing with so many different
> types only to be one example. If you multiply this with possible Cloud-based
> deployments and various stages, you'd easily understand, this is nowhere
> sufficient for a PaaS future of Java EE and JSF. I plan to raise an ER for
> future JSF releases, probably not for 2.2 as this is still in the scope of
> EE 6.
>
> Regards,
> Werner
>
>
> On Tue, Jun 7, 2011 at 5:31 AM, Reza Rahman <reza_rahman_at_lycos.com> wrote:
>
>> Antonio,
>>
>> FYI, we do have some of these details hashed out internally. If it saves
>> you time, I am happy to share those details.
>>
>> As I said, this has been on our radar, I'm just not entirely sure about
>> priorities for Java EE 7 vs Java EE 8, etc.
>>
>> Cheers,
>> Reza
>>
>>
>>
>> On 6/6/2011 6:01 PM, Linda DeMichiel wrote:
>>
>>> Antonio,
>>>
>>> Sounds interesting, tell us more....
>>>
>>> thanks,
>>>
>>> -Linda
>>>
>>>
>>> On 6/2/2011 10:47 AM, Antonio Goncalves wrote:
>>>
>>>> I would like to share some thoughts with you.
>>>>
>>>> I've used in the past Spring Config and latelly I've attended a
>>>> conference that talked about Seam Config. Clearly I can
>>>> see the benefit of having easy configuration on the entire platform. At
>>>> the moment we have ejb-jar.xml and environment
>>>> entries to configure our EJBs. We can also use the web.xml to pass some
>>>> parameters to our servlets and bits and pieces
>>>> in the application.xml file.
>>>>
>>>> Why not having a seperate spec that takes inspiration from Seam Config,
>>>> Spring Config and so on to be able to configure
>>>> the entire platform (a CDI bean as well as an EJB...). Configuration
>>>> will also be used for Paas purposes of course.
>>>>
>>>> Configuration is an important topic and developers never know where to
>>>> put it : property files, XML, database, JNDI. Why
>>>> not having a spec that specifies how configuration should work (I really
>>>> like the Seam Config approach) and each spec
>>>> could then use it to specify how to configure a specific component, as
>>>> well as batch processing or Paas/Saas
>>>> configuration...
>>>>
>>>> Again, my 2 cents
>>>>
>>>> --
>>>> Antonio Goncalves
>>>> Software architect and Java Champion
>>>>
>>>> Web site <http://www.antoniogoncalves.org> | Twitter <
>>>> http://twitter.com/agoncal> | Blog
>>>> <http://feeds.feedburner.com/AntonioGoncalves> | LinkedIn <
>>>> http://www.linkedin.com/in/agoncal> | Paris JUG
>>>> <http://www.parisjug.org>
>>>>
>>>
>>>
>>> -----
>>>
>>> No virus found in this message.
>>> Checked by AVG - www.avg.com
>>> Version: 10.0.1375 / Virus Database: 1511/3685 - Release Date: 06/06/11
>>>
>>>
>>>
>>
>
>
> --
>
> Werner Keil | UOMo Lead | Eclipse Foundation | Agile Coach, Principal
> Consultant | *emergn* limited
>
> 590 Madison Avenue. New York. NY 10022 | 68 Lombard Street. London EC3V 9LJ
> UK
>
> US Toll Free: +1-877.964.1981 | Worldwide Toll Free: +800.225.53482
> Twitter @wernerkeil | Skype: werner.keil | www.emergn.com | Reshaping IT
>
>
--
Antonio Goncalves
Software architect and Java Champion
Web site <http://www.antoniogoncalves.org> |
Twitter<http://twitter.com/agoncal>|
Blog <http://feeds.feedburner.com/AntonioGoncalves> |
LinkedIn<http://www.linkedin.com/in/agoncal>| Paris
JUG <http://www.parisjug.org>