You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomee.apache.org by David Blevins <da...@visi.com> on 2012/01/31 01:41:56 UTC
Various TomEE improvements
Thought these might be some good discussion points/improvements for TomEE.
- TOMEE-130: Improve openejb webapp console to match current site look and feel
- TOMEE-131: The openejb.xml file should be called tomee.xml in TomEE
- TOMEE-132: Make it easier to use command line deployer in TomEE
- TOMEE-133: TomEE logs/openejb.log should be merged with the rest of Tomcat logging
- TOMEE-134: Rename openejb.war to tomee.war
General idea is to blend in a bit more and modernize the naming.
Thoughts?
-David
Re: Various TomEE improvements
Posted by David Blevins <da...@gmail.com>.
On Feb 1, 2012, at 9:59 AM, Romain Manni-Bucau wrote:
> i didnt find it in VmDeploymentManager.
That's fine. Did you try running a few TCK tests to verify the changes?
-David
>
> - Romain
>
>
> 2012/2/1 David Blevins <da...@gmail.com>
>
>> We'll definitely want to make sure we update the tck setup as well. It
>> had quite a lot of references to the "openejb" webapp.
>>
>> There's a bunch in the groovy classes for setting up classpaths and some
>> in the VmDeploymentManager.
>>
>>
>> -David
>>
>> On Jan 31, 2012, at 12:36 AM, Romain Manni-Bucau wrote:
>>
>>> just as a reminder for TOMEE-130 i started
>>>
>> http://code.google.com/p/rmannibucau/source/browse#hg%2Fopenejb%2Ftomee-webapp-ng
>>> but
>>> it needs some jsf love.
>>>
>>> for tomee-132: karafee has such a command and tomee maven plugin too, +1
>>> for tomee.sh
>>> tomee-133: should already be done
>>> +1 for tomee-134
>>>
>>> - Romain
>>>
>>>
>>> 2012/1/31 Jean-Louis MONTEIRO <je...@gmail.com>
>>>
>>>> +1 as soon as the old style still works.
>>>> I mean, if we can still deliver an openejb.xml file, an openejb war and
>> so.
>>>>
>>>> May be I can go back and help in one of them.
>>>>
>>>> Jean-Louis
>>>>
>>>> 2012/1/31 David Blevins <da...@visi.com>
>>>>
>>>>> Thought these might be some good discussion points/improvements for
>>>> TomEE.
>>>>>
>>>>> - TOMEE-130: Improve openejb webapp console to match current site look
>>>>> and feel
>>>>> - TOMEE-131: The openejb.xml file should be called tomee.xml in TomEE
>>>>> - TOMEE-132: Make it easier to use command line deployer in TomEE
>>>>> - TOMEE-133: TomEE logs/openejb.log should be merged with the rest of
>>>>> Tomcat logging
>>>>> - TOMEE-134: Rename openejb.war to tomee.war
>>>>>
>>>>> General idea is to blend in a bit more and modernize the naming.
>>>>>
>>>>> Thoughts?
>>>>>
>>>>>
>>>>> -David
>>>>>
>>>>>
>>>>
>>
>>
Re: Various TomEE improvements
Posted by Romain Manni-Bucau <rm...@gmail.com>.
i didnt find it in VmDeploymentManager.
- Romain
2012/2/1 David Blevins <da...@gmail.com>
> We'll definitely want to make sure we update the tck setup as well. It
> had quite a lot of references to the "openejb" webapp.
>
> There's a bunch in the groovy classes for setting up classpaths and some
> in the VmDeploymentManager.
>
>
> -David
>
> On Jan 31, 2012, at 12:36 AM, Romain Manni-Bucau wrote:
>
> > just as a reminder for TOMEE-130 i started
> >
> http://code.google.com/p/rmannibucau/source/browse#hg%2Fopenejb%2Ftomee-webapp-ng
> > but
> > it needs some jsf love.
> >
> > for tomee-132: karafee has such a command and tomee maven plugin too, +1
> > for tomee.sh
> > tomee-133: should already be done
> > +1 for tomee-134
> >
> > - Romain
> >
> >
> > 2012/1/31 Jean-Louis MONTEIRO <je...@gmail.com>
> >
> >> +1 as soon as the old style still works.
> >> I mean, if we can still deliver an openejb.xml file, an openejb war and
> so.
> >>
> >> May be I can go back and help in one of them.
> >>
> >> Jean-Louis
> >>
> >> 2012/1/31 David Blevins <da...@visi.com>
> >>
> >>> Thought these might be some good discussion points/improvements for
> >> TomEE.
> >>>
> >>> - TOMEE-130: Improve openejb webapp console to match current site look
> >>> and feel
> >>> - TOMEE-131: The openejb.xml file should be called tomee.xml in TomEE
> >>> - TOMEE-132: Make it easier to use command line deployer in TomEE
> >>> - TOMEE-133: TomEE logs/openejb.log should be merged with the rest of
> >>> Tomcat logging
> >>> - TOMEE-134: Rename openejb.war to tomee.war
> >>>
> >>> General idea is to blend in a bit more and modernize the naming.
> >>>
> >>> Thoughts?
> >>>
> >>>
> >>> -David
> >>>
> >>>
> >>
>
>
Re: Various TomEE improvements
Posted by David Blevins <da...@gmail.com>.
We'll definitely want to make sure we update the tck setup as well. It had quite a lot of references to the "openejb" webapp.
There's a bunch in the groovy classes for setting up classpaths and some in the VmDeploymentManager.
-David
On Jan 31, 2012, at 12:36 AM, Romain Manni-Bucau wrote:
> just as a reminder for TOMEE-130 i started
> http://code.google.com/p/rmannibucau/source/browse#hg%2Fopenejb%2Ftomee-webapp-ng
> but
> it needs some jsf love.
>
> for tomee-132: karafee has such a command and tomee maven plugin too, +1
> for tomee.sh
> tomee-133: should already be done
> +1 for tomee-134
>
> - Romain
>
>
> 2012/1/31 Jean-Louis MONTEIRO <je...@gmail.com>
>
>> +1 as soon as the old style still works.
>> I mean, if we can still deliver an openejb.xml file, an openejb war and so.
>>
>> May be I can go back and help in one of them.
>>
>> Jean-Louis
>>
>> 2012/1/31 David Blevins <da...@visi.com>
>>
>>> Thought these might be some good discussion points/improvements for
>> TomEE.
>>>
>>> - TOMEE-130: Improve openejb webapp console to match current site look
>>> and feel
>>> - TOMEE-131: The openejb.xml file should be called tomee.xml in TomEE
>>> - TOMEE-132: Make it easier to use command line deployer in TomEE
>>> - TOMEE-133: TomEE logs/openejb.log should be merged with the rest of
>>> Tomcat logging
>>> - TOMEE-134: Rename openejb.war to tomee.war
>>>
>>> General idea is to blend in a bit more and modernize the naming.
>>>
>>> Thoughts?
>>>
>>>
>>> -David
>>>
>>>
>>
Re: Various TomEE improvements
Posted by Romain Manni-Bucau <rm...@gmail.com>.
just as a reminder for TOMEE-130 i started
http://code.google.com/p/rmannibucau/source/browse#hg%2Fopenejb%2Ftomee-webapp-ng
but
it needs some jsf love.
for tomee-132: karafee has such a command and tomee maven plugin too, +1
for tomee.sh
tomee-133: should already be done
+1 for tomee-134
- Romain
2012/1/31 Jean-Louis MONTEIRO <je...@gmail.com>
> +1 as soon as the old style still works.
> I mean, if we can still deliver an openejb.xml file, an openejb war and so.
>
> May be I can go back and help in one of them.
>
> Jean-Louis
>
> 2012/1/31 David Blevins <da...@visi.com>
>
> > Thought these might be some good discussion points/improvements for
> TomEE.
> >
> > - TOMEE-130: Improve openejb webapp console to match current site look
> > and feel
> > - TOMEE-131: The openejb.xml file should be called tomee.xml in TomEE
> > - TOMEE-132: Make it easier to use command line deployer in TomEE
> > - TOMEE-133: TomEE logs/openejb.log should be merged with the rest of
> > Tomcat logging
> > - TOMEE-134: Rename openejb.war to tomee.war
> >
> > General idea is to blend in a bit more and modernize the naming.
> >
> > Thoughts?
> >
> >
> > -David
> >
> >
>
Re: Various TomEE improvements
Posted by Jean-Louis MONTEIRO <je...@gmail.com>.
+1 as soon as the old style still works.
I mean, if we can still deliver an openejb.xml file, an openejb war and so.
May be I can go back and help in one of them.
Jean-Louis
2012/1/31 David Blevins <da...@visi.com>
> Thought these might be some good discussion points/improvements for TomEE.
>
> - TOMEE-130: Improve openejb webapp console to match current site look
> and feel
> - TOMEE-131: The openejb.xml file should be called tomee.xml in TomEE
> - TOMEE-132: Make it easier to use command line deployer in TomEE
> - TOMEE-133: TomEE logs/openejb.log should be merged with the rest of
> Tomcat logging
> - TOMEE-134: Rename openejb.war to tomee.war
>
> General idea is to blend in a bit more and modernize the naming.
>
> Thoughts?
>
>
> -David
>
>
Re: Various TomEE improvements
Posted by David Blevins <da...@gmail.com>.
On Feb 14, 2012, at 9:22 AM, Thiago Veronezi wrote:
> Is anyone actively working on the "TOMEE-130: Improve openejb webapp
> console to match current site look and feel"? I just figured out how to use
> the current look and feel in the current application.
Go for it!
-David
>
> On Thu, Feb 9, 2012 at 5:47 AM, Romain Manni-Bucau <rm...@gmail.com>wrote:
>
>> +1 for the idea if it doesn't bring another web framework (vaadin,
>> tapestry, ...)...
>>
>> we can easily export information through JAX-RS services.
>>
>> Well, for me the point is still the same "anyone is good in web design"?
>>
>> - Romain
>>
>>
>> 2012/2/9 Thiago Veronezi <th...@veronezi.org>
>>
>>> I like it. In fact I don't use JSF and JSP for the last 4 years, only
>>> javascript and json.
>>> I think the JSON approach is the reality in web applications now, and it
>>> would be cool to see the openejb webapp using it. We need to verify if we
>>> can use jquery (or any other js library) in our project, but I think MIT
>> is
>>> fine for Apache 2.0 projects.
>>>
>>> +1
>>>
>>> []s,
>>> Thiago
>>>
>>> On Wed, Feb 8, 2012 at 5:06 PM, dsh <da...@googlemail.com>
>> wrote:
>>>
>>>> Concerning TOMEE-130 - Would it make sense to decouple the UI from the
>>>> remaining webapp logic? For example it could just emit JSON data
>>>> accesible through a REST API. That way we could have a 2nd webapp that
>>>> only does the UI or have an OpenSocial container such as Apache
>>>> Shinding that would consume the JSON data from the 1t webapp and
>>>> afterwards renders the UI using its own rendering engine. We could
>>>> even have KDE or Win 7 widgets accesing the 1st webapp and thus TomEE
>>>> instances could be managed from the desktop...
>>>>
>>>> Cheers
>>>> Daniel
>>>>
>>>> On Tue, Jan 31, 2012 at 1:41 AM, David Blevins <david.blevins@visi.com
>>>
>>>> wrote:
>>>>> Thought these might be some good discussion points/improvements for
>>>> TomEE.
>>>>>
>>>>> - TOMEE-130: Improve openejb webapp console to match current site
>> look
>>>> and feel
>>>>> - TOMEE-131: The openejb.xml file should be called tomee.xml in
>> TomEE
>>>>> - TOMEE-132: Make it easier to use command line deployer in TomEE
>>>>> - TOMEE-133: TomEE logs/openejb.log should be merged with the rest
>> of
>>>> Tomcat logging
>>>>> - TOMEE-134: Rename openejb.war to tomee.war
>>>>>
>>>>> General idea is to blend in a bit more and modernize the naming.
>>>>>
>>>>> Thoughts?
>>>>>
>>>>>
>>>>> -David
>>>>>
>>>>
>>>
>>
Re: Various TomEE improvements
Posted by Thiago Veronezi <th...@veronezi.org>.
Is anyone actively working on the "TOMEE-130: Improve openejb webapp
console to match current site look and feel"? I just figured out how to use
the current look and feel in the current application.
[]s,
Thiago.
On Thu, Feb 9, 2012 at 5:47 AM, Romain Manni-Bucau <rm...@gmail.com>wrote:
> +1 for the idea if it doesn't bring another web framework (vaadin,
> tapestry, ...)...
>
> we can easily export information through JAX-RS services.
>
> Well, for me the point is still the same "anyone is good in web design"?
>
> - Romain
>
>
> 2012/2/9 Thiago Veronezi <th...@veronezi.org>
>
> > I like it. In fact I don't use JSF and JSP for the last 4 years, only
> > javascript and json.
> > I think the JSON approach is the reality in web applications now, and it
> > would be cool to see the openejb webapp using it. We need to verify if we
> > can use jquery (or any other js library) in our project, but I think MIT
> is
> > fine for Apache 2.0 projects.
> >
> > +1
> >
> > []s,
> > Thiago
> >
> > On Wed, Feb 8, 2012 at 5:06 PM, dsh <da...@googlemail.com>
> wrote:
> >
> > > Concerning TOMEE-130 - Would it make sense to decouple the UI from the
> > > remaining webapp logic? For example it could just emit JSON data
> > > accesible through a REST API. That way we could have a 2nd webapp that
> > > only does the UI or have an OpenSocial container such as Apache
> > > Shinding that would consume the JSON data from the 1t webapp and
> > > afterwards renders the UI using its own rendering engine. We could
> > > even have KDE or Win 7 widgets accesing the 1st webapp and thus TomEE
> > > instances could be managed from the desktop...
> > >
> > > Cheers
> > > Daniel
> > >
> > > On Tue, Jan 31, 2012 at 1:41 AM, David Blevins <david.blevins@visi.com
> >
> > > wrote:
> > > > Thought these might be some good discussion points/improvements for
> > > TomEE.
> > > >
> > > > - TOMEE-130: Improve openejb webapp console to match current site
> look
> > > and feel
> > > > - TOMEE-131: The openejb.xml file should be called tomee.xml in
> TomEE
> > > > - TOMEE-132: Make it easier to use command line deployer in TomEE
> > > > - TOMEE-133: TomEE logs/openejb.log should be merged with the rest
> of
> > > Tomcat logging
> > > > - TOMEE-134: Rename openejb.war to tomee.war
> > > >
> > > > General idea is to blend in a bit more and modernize the naming.
> > > >
> > > > Thoughts?
> > > >
> > > >
> > > > -David
> > > >
> > >
> >
>
Re: Various TomEE improvements
Posted by Romain Manni-Bucau <rm...@gmail.com>.
+1 for the idea if it doesn't bring another web framework (vaadin,
tapestry, ...)...
we can easily export information through JAX-RS services.
Well, for me the point is still the same "anyone is good in web design"?
- Romain
2012/2/9 Thiago Veronezi <th...@veronezi.org>
> I like it. In fact I don't use JSF and JSP for the last 4 years, only
> javascript and json.
> I think the JSON approach is the reality in web applications now, and it
> would be cool to see the openejb webapp using it. We need to verify if we
> can use jquery (or any other js library) in our project, but I think MIT is
> fine for Apache 2.0 projects.
>
> +1
>
> []s,
> Thiago
>
> On Wed, Feb 8, 2012 at 5:06 PM, dsh <da...@googlemail.com> wrote:
>
> > Concerning TOMEE-130 - Would it make sense to decouple the UI from the
> > remaining webapp logic? For example it could just emit JSON data
> > accesible through a REST API. That way we could have a 2nd webapp that
> > only does the UI or have an OpenSocial container such as Apache
> > Shinding that would consume the JSON data from the 1t webapp and
> > afterwards renders the UI using its own rendering engine. We could
> > even have KDE or Win 7 widgets accesing the 1st webapp and thus TomEE
> > instances could be managed from the desktop...
> >
> > Cheers
> > Daniel
> >
> > On Tue, Jan 31, 2012 at 1:41 AM, David Blevins <da...@visi.com>
> > wrote:
> > > Thought these might be some good discussion points/improvements for
> > TomEE.
> > >
> > > - TOMEE-130: Improve openejb webapp console to match current site look
> > and feel
> > > - TOMEE-131: The openejb.xml file should be called tomee.xml in TomEE
> > > - TOMEE-132: Make it easier to use command line deployer in TomEE
> > > - TOMEE-133: TomEE logs/openejb.log should be merged with the rest of
> > Tomcat logging
> > > - TOMEE-134: Rename openejb.war to tomee.war
> > >
> > > General idea is to blend in a bit more and modernize the naming.
> > >
> > > Thoughts?
> > >
> > >
> > > -David
> > >
> >
>
Re: Various TomEE improvements
Posted by Thiago Veronezi <th...@veronezi.org>.
I like it. In fact I don't use JSF and JSP for the last 4 years, only
javascript and json.
I think the JSON approach is the reality in web applications now, and it
would be cool to see the openejb webapp using it. We need to verify if we
can use jquery (or any other js library) in our project, but I think MIT is
fine for Apache 2.0 projects.
+1
[]s,
Thiago
On Wed, Feb 8, 2012 at 5:06 PM, dsh <da...@googlemail.com> wrote:
> Concerning TOMEE-130 - Would it make sense to decouple the UI from the
> remaining webapp logic? For example it could just emit JSON data
> accesible through a REST API. That way we could have a 2nd webapp that
> only does the UI or have an OpenSocial container such as Apache
> Shinding that would consume the JSON data from the 1t webapp and
> afterwards renders the UI using its own rendering engine. We could
> even have KDE or Win 7 widgets accesing the 1st webapp and thus TomEE
> instances could be managed from the desktop...
>
> Cheers
> Daniel
>
> On Tue, Jan 31, 2012 at 1:41 AM, David Blevins <da...@visi.com>
> wrote:
> > Thought these might be some good discussion points/improvements for
> TomEE.
> >
> > - TOMEE-130: Improve openejb webapp console to match current site look
> and feel
> > - TOMEE-131: The openejb.xml file should be called tomee.xml in TomEE
> > - TOMEE-132: Make it easier to use command line deployer in TomEE
> > - TOMEE-133: TomEE logs/openejb.log should be merged with the rest of
> Tomcat logging
> > - TOMEE-134: Rename openejb.war to tomee.war
> >
> > General idea is to blend in a bit more and modernize the naming.
> >
> > Thoughts?
> >
> >
> > -David
> >
>
Re: Various TomEE improvements
Posted by dsh <da...@googlemail.com>.
Concerning TOMEE-130 - Would it make sense to decouple the UI from the
remaining webapp logic? For example it could just emit JSON data
accesible through a REST API. That way we could have a 2nd webapp that
only does the UI or have an OpenSocial container such as Apache
Shinding that would consume the JSON data from the 1t webapp and
afterwards renders the UI using its own rendering engine. We could
even have KDE or Win 7 widgets accesing the 1st webapp and thus TomEE
instances could be managed from the desktop...
Cheers
Daniel
On Tue, Jan 31, 2012 at 1:41 AM, David Blevins <da...@visi.com> wrote:
> Thought these might be some good discussion points/improvements for TomEE.
>
> - TOMEE-130: Improve openejb webapp console to match current site look and feel
> - TOMEE-131: The openejb.xml file should be called tomee.xml in TomEE
> - TOMEE-132: Make it easier to use command line deployer in TomEE
> - TOMEE-133: TomEE logs/openejb.log should be merged with the rest of Tomcat logging
> - TOMEE-134: Rename openejb.war to tomee.war
>
> General idea is to blend in a bit more and modernize the naming.
>
> Thoughts?
>
>
> -David
>