You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by viola lu <vi...@gmail.com> on 2010/09/22 04:29:17 UTC
[Discussion] WAB Deployment Way
>From https://issues.apache.org/jira/browse/GERONIMO-5588, currenlty WAB is
deployed via osgi: install, or packaged in EAB , then deployed via admin
console. If it's deployed via admin console, it's recognized as WAR, shall
we keep current way in future? Or will enable WBA deployment via admin
console and deployer tool?
Also there is another question here: WAB is a bundle, its classpath can be
set via bundle classpath or use default classpath( classes keep the same
level with WEB-INF:, but it's also a JavaEE application, whose default
classpath is "classes or lib are under the subfolder of WEB-INF, this is
defined in RFC 66. If as definition in RFC 66, osgi: install won't load
classes under WEB-INF in WAB. Or shall we support both?
Welcome comments!Thanks in advance!
--
viola
Re: [Discussion] WAB Deployment Way
Posted by viola lu <vi...@gmail.com>.
Any thoughts?
On Wed, Sep 22, 2010 at 10:29 AM, viola lu <vi...@gmail.com> wrote:
> From https://issues.apache.org/jira/browse/GERONIMO-5588, currenlty WAB is
> deployed via osgi: install, or packaged in EAB , then deployed via admin
> console. If it's deployed via admin console, it's recognized as WAR, shall
> we keep current way in future? Or will enable WBA deployment via admin
> console and deployer tool?
> Also there is another question here: WAB is a bundle, its classpath can be
> set via bundle classpath or use default classpath( classes keep the same
> level with WEB-INF:, but it's also a JavaEE application, whose default
> classpath is "classes or lib are under the subfolder of WEB-INF, this is
> defined in RFC 66. If as definition in RFC 66, osgi: install won't load
> classes under WEB-INF in WAB. Or shall we support both?
> Welcome comments!Thanks in advance!
>
> --
> viola
>
--
viola
Re: [Discussion] WAB Deployment Way
Posted by Shawn Jiang <ge...@gmail.com>.
Maybe It should not be called "support".
Geronimo does not have very good warning/error messages in some cases when
the user makes mistakes. "EAB deployment via admin console" problem could
be another example of that.
On Sun, Sep 26, 2010 at 5:19 PM, viola lu <vi...@gmail.com> wrote:
> But we support EAB deployment via admin console, it's strange and confusing
> for users if WAB deployment is not supported.
>
>
> On Sun, Sep 26, 2010 at 12:52 PM, Shawn Jiang <ge...@gmail.com> wrote:
>
>> At least, if we decide not to support WAB deployment there, we need to
>> give a meaning warning and reject the deployment when the users try to
>> deploy WAB with "console deployer" or "deploy deploy"
>>
>> On Sun, Sep 26, 2010 at 12:50 PM, Shawn Jiang <ge...@gmail.com>wrote:
>>
>>>
>>>
>>> On Wed, Sep 22, 2010 at 10:29 AM, viola lu <vi...@gmail.com> wrote:
>>>
>>>> From https://issues.apache.org/jira/browse/GERONIMO-5588, currenlty WAB
>>>> is deployed via osgi: install, or packaged in EAB , then deployed via admin
>>>> console. If it's deployed via admin console, it's recognized as WAR, shall
>>>> we keep current way in future? Or will enable WBA deployment via admin
>>>> console and deployer tool?
>>>>
>>>
>>> I think we should not support deploy WAB from "admin console depoyer" or
>>> "deploy deploy" command. Because the users need to know what's the real
>>> type of the application they want to deploy before deciding which deployment
>>> method to use.
>>>
>>> Just like the current differences between "deploy deploy" and "deploy
>>> install-plugin". Though, sometime, a plugin is also a kind of WAR. We
>>> need to use "deploy install-plugin" instead of "deploy deploy" to deploy a
>>> car.
>>>
>>> Maybe we could add an option "deploy install-wab" to the current deploy
>>> command, thoughts ?
>>>
>>>
>>>
>>>> Also there is another question here: WAB is a bundle, its classpath can
>>>> be set via bundle classpath or use default classpath( classes keep the same
>>>> level with WEB-INF:, but it's also a JavaEE application, whose default
>>>> classpath is "classes or lib are under the subfolder of WEB-INF, this is
>>>> defined in RFC 66. If as definition in RFC 66, osgi: install won't load
>>>> classes under WEB-INF in WAB. Or shall we support both?
>>>> Welcome comments!Thanks in advance!
>>>>
>>>> --
>>>> viola
>>>>
>>>
>>>
>>>
>>> --
>>> Shawn
>>>
>>
>>
>>
>> --
>> Shawn
>>
>
>
>
> --
> viola
>
--
Shawn
Re: [Discussion] WAB Deployment Way
Posted by viola lu <vi...@gmail.com>.
But we support EAB deployment via admin console, it's strange and confusing
for users if WAB deployment is not supported.
On Sun, Sep 26, 2010 at 12:52 PM, Shawn Jiang <ge...@gmail.com> wrote:
> At least, if we decide not to support WAB deployment there, we need to
> give a meaning warning and reject the deployment when the users try to
> deploy WAB with "console deployer" or "deploy deploy"
>
> On Sun, Sep 26, 2010 at 12:50 PM, Shawn Jiang <ge...@gmail.com> wrote:
>
>>
>>
>> On Wed, Sep 22, 2010 at 10:29 AM, viola lu <vi...@gmail.com> wrote:
>>
>>> From https://issues.apache.org/jira/browse/GERONIMO-5588, currenlty WAB
>>> is deployed via osgi: install, or packaged in EAB , then deployed via admin
>>> console. If it's deployed via admin console, it's recognized as WAR, shall
>>> we keep current way in future? Or will enable WBA deployment via admin
>>> console and deployer tool?
>>>
>>
>> I think we should not support deploy WAB from "admin console depoyer" or
>> "deploy deploy" command. Because the users need to know what's the real
>> type of the application they want to deploy before deciding which deployment
>> method to use.
>>
>> Just like the current differences between "deploy deploy" and "deploy
>> install-plugin". Though, sometime, a plugin is also a kind of WAR. We
>> need to use "deploy install-plugin" instead of "deploy deploy" to deploy a
>> car.
>>
>> Maybe we could add an option "deploy install-wab" to the current deploy
>> command, thoughts ?
>>
>>
>>
>>> Also there is another question here: WAB is a bundle, its classpath can
>>> be set via bundle classpath or use default classpath( classes keep the same
>>> level with WEB-INF:, but it's also a JavaEE application, whose default
>>> classpath is "classes or lib are under the subfolder of WEB-INF, this is
>>> defined in RFC 66. If as definition in RFC 66, osgi: install won't load
>>> classes under WEB-INF in WAB. Or shall we support both?
>>> Welcome comments!Thanks in advance!
>>>
>>> --
>>> viola
>>>
>>
>>
>>
>> --
>> Shawn
>>
>
>
>
> --
> Shawn
>
--
viola
Re: [Discussion] WAB Deployment Way
Posted by Shawn Jiang <ge...@gmail.com>.
At least, if we decide not to support WAB deployment there, we need to
give a meaning warning and reject the deployment when the users try to
deploy WAB with "console deployer" or "deploy deploy"
On Sun, Sep 26, 2010 at 12:50 PM, Shawn Jiang <ge...@gmail.com> wrote:
>
>
> On Wed, Sep 22, 2010 at 10:29 AM, viola lu <vi...@gmail.com> wrote:
>
>> From https://issues.apache.org/jira/browse/GERONIMO-5588, currenlty WAB
>> is deployed via osgi: install, or packaged in EAB , then deployed via admin
>> console. If it's deployed via admin console, it's recognized as WAR, shall
>> we keep current way in future? Or will enable WBA deployment via admin
>> console and deployer tool?
>>
>
> I think we should not support deploy WAB from "admin console depoyer" or
> "deploy deploy" command. Because the users need to know what's the real
> type of the application they want to deploy before deciding which deployment
> method to use.
>
> Just like the current differences between "deploy deploy" and "deploy
> install-plugin". Though, sometime, a plugin is also a kind of WAR. We
> need to use "deploy install-plugin" instead of "deploy deploy" to deploy a
> car.
>
> Maybe we could add an option "deploy install-wab" to the current deploy
> command, thoughts ?
>
>
>
>> Also there is another question here: WAB is a bundle, its classpath can be
>> set via bundle classpath or use default classpath( classes keep the same
>> level with WEB-INF:, but it's also a JavaEE application, whose default
>> classpath is "classes or lib are under the subfolder of WEB-INF, this is
>> defined in RFC 66. If as definition in RFC 66, osgi: install won't load
>> classes under WEB-INF in WAB. Or shall we support both?
>> Welcome comments!Thanks in advance!
>>
>> --
>> viola
>>
>
>
>
> --
> Shawn
>
--
Shawn
Re: [Discussion] WAB Deployment Way
Posted by Shawn Jiang <ge...@gmail.com>.
On Wed, Sep 22, 2010 at 10:29 AM, viola lu <vi...@gmail.com> wrote:
> From https://issues.apache.org/jira/browse/GERONIMO-5588, currenlty WAB is
> deployed via osgi: install, or packaged in EAB , then deployed via admin
> console. If it's deployed via admin console, it's recognized as WAR, shall
> we keep current way in future? Or will enable WBA deployment via admin
> console and deployer tool?
>
I think we should not support deploy WAB from "admin console depoyer" or
"deploy deploy" command. Because the users need to know what's the real
type of the application they want to deploy before deciding which deployment
method to use.
Just like the current differences between "deploy deploy" and "deploy
install-plugin". Though, sometime, a plugin is also a kind of WAR. We
need to use "deploy install-plugin" instead of "deploy deploy" to deploy a
car.
Maybe we could add an option "deploy install-wab" to the current deploy
command, thoughts ?
> Also there is another question here: WAB is a bundle, its classpath can be
> set via bundle classpath or use default classpath( classes keep the same
> level with WEB-INF:, but it's also a JavaEE application, whose default
> classpath is "classes or lib are under the subfolder of WEB-INF, this is
> defined in RFC 66. If as definition in RFC 66, osgi: install won't load
> classes under WEB-INF in WAB. Or shall we support both?
> Welcome comments!Thanks in advance!
>
> --
> viola
>
--
Shawn
Re: [Discussion] WAB Deployment Way
Posted by Shawn Jiang <ge...@gmail.com>.
We need to do more discuss with this thread.
On Mon, Sep 27, 2010 at 1:40 PM, Jarek Gawor <jg...@gmail.com> wrote:
> On Tue, Sep 21, 2010 at 10:29 PM, viola lu <vi...@gmail.com> wrote:
> > From https://issues.apache.org/jira/browse/GERONIMO-5588, currenlty WAB
> is
> > deployed via osgi: install, or packaged in EAB , then deployed via admin
> > console. If it's deployed via admin console, it's recognized as WAR,
> shall
> > we keep current way in future? Or will enable WBA deployment via admin
> > console and deployer tool?
>
> WAB is really just a bundle. What we should support is installation of
> a bundle through the admin console and/or command line tool. I think
> there might already be a JIRA open for that.
> What I'm not sure about is if WAB, EBA, and any other Java EE
> application installation should happen through the existing Deployer
> in the admin console or if we should have separate installers for
> OSGI-based archives (WAB, EBA) and Java EE applications (EAR, WAR,
> etc.)
>
> > Also there is another question here: WAB is a bundle, its classpath can
> be
> > set via bundle classpath or use default classpath( classes keep the same
> > level with WEB-INF:, but it's also a JavaEE application, whose default
> > classpath is "classes or lib are under the subfolder of WEB-INF, this is
> > defined in RFC 66. If as definition in RFC 66, osgi: install won't load
> > classes under WEB-INF in WAB. Or shall we support both?
>
> Yes, it will. The bundle classpath header just needs to be set correctly.
>
> Jarek
>
--
Shawn
Re: [Discussion] WAB Deployment Way
Posted by Jarek Gawor <jg...@gmail.com>.
On Tue, Sep 21, 2010 at 10:29 PM, viola lu <vi...@gmail.com> wrote:
> From https://issues.apache.org/jira/browse/GERONIMO-5588, currenlty WAB is
> deployed via osgi: install, or packaged in EAB , then deployed via admin
> console. If it's deployed via admin console, it's recognized as WAR, shall
> we keep current way in future? Or will enable WBA deployment via admin
> console and deployer tool?
WAB is really just a bundle. What we should support is installation of
a bundle through the admin console and/or command line tool. I think
there might already be a JIRA open for that.
What I'm not sure about is if WAB, EBA, and any other Java EE
application installation should happen through the existing Deployer
in the admin console or if we should have separate installers for
OSGI-based archives (WAB, EBA) and Java EE applications (EAR, WAR,
etc.)
> Also there is another question here: WAB is a bundle, its classpath can be
> set via bundle classpath or use default classpath( classes keep the same
> level with WEB-INF:, but it's also a JavaEE application, whose default
> classpath is "classes or lib are under the subfolder of WEB-INF, this is
> defined in RFC 66. If as definition in RFC 66, osgi: install won't load
> classes under WEB-INF in WAB. Or shall we support both?
Yes, it will. The bundle classpath header just needs to be set correctly.
Jarek