You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by Ruwan Linton <ru...@gmail.com> on 2010/02/20 15:59:46 UTC
Ability to have hidden services on Axis2
Devs,
WSO2 Carbon [http://wso2.org/projects/carbon] which depends on and uses
axis2 has a requirement to have hidden admin services, bu the
DeploymentEngine prints an INFO log message for all the service deployments,
in order to achieve the above requirement, how about filtering this log
statement by looking at a service group parameter named hiddenService.
If there is no objection I will get this implemented.
Thanks,
Ruwan
--
Ruwan Linton
Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
WSO2 Inc.; http://wso2.org
email: ruwan@wso2.com; cell: +94 77 341 3097
blog: http://ruwansblog.blogspot.com
Re: Ability to have hidden services on Axis2
Posted by Amila Suriarachchi <am...@gmail.com>.
On Sat, Feb 20, 2010 at 8:31 PM, Ruwan Linton <ru...@gmail.com>wrote:
> Also, Synapse has the same requirement where it adds a service named
> __SynapseService, but doesn't need to show that out to the users.
I think there are two types of users.
1. who uses the synapse server
2. who Admin the synapse server
I think you mean latter type of users. For them it is ok to show this info
message.
thanks,
Amila.
> I think others will also be beneficial with this feature.
>
> Thanks,
> Ruwan
>
>
> On Sat, Feb 20, 2010 at 8:29 PM, Ruwan Linton <ru...@gmail.com>wrote:
>
>> Devs,
>>
>> WSO2 Carbon [http://wso2.org/projects/carbon] which depends on and uses
>> axis2 has a requirement to have hidden admin services, bu the
>> DeploymentEngine prints an INFO log message for all the service deployments,
>> in order to achieve the above requirement, how about filtering this log
>> statement by looking at a service group parameter named hiddenService.
>>
>> If there is no objection I will get this implemented.
>>
>> Thanks,
>> Ruwan
>>
>> --
>> Ruwan Linton
>> Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
>> WSO2 Inc.; http://wso2.org
>> email: ruwan@wso2.com; cell: +94 77 341 3097
>> blog: http://ruwansblog.blogspot.com
>>
>
>
>
> --
> Ruwan Linton
> Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
> WSO2 Inc.; http://wso2.org
> email: ruwan@wso2.com; cell: +94 77 341 3097
> blog: http://ruwansblog.blogspot.com
>
--
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/
Re: Ability to have hidden services on Axis2
Posted by Ruwan Linton <ru...@gmail.com>.
Also, Synapse has the same requirement where it adds a service named
__SynapseService, but doesn't need to show that out to the users. I think
others will also be beneficial with this feature.
Thanks,
Ruwan
On Sat, Feb 20, 2010 at 8:29 PM, Ruwan Linton <ru...@gmail.com>wrote:
> Devs,
>
> WSO2 Carbon [http://wso2.org/projects/carbon] which depends on and uses
> axis2 has a requirement to have hidden admin services, bu the
> DeploymentEngine prints an INFO log message for all the service deployments,
> in order to achieve the above requirement, how about filtering this log
> statement by looking at a service group parameter named hiddenService.
>
> If there is no objection I will get this implemented.
>
> Thanks,
> Ruwan
>
> --
> Ruwan Linton
> Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
> WSO2 Inc.; http://wso2.org
> email: ruwan@wso2.com; cell: +94 77 341 3097
> blog: http://ruwansblog.blogspot.com
>
--
Ruwan Linton
Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
WSO2 Inc.; http://wso2.org
email: ruwan@wso2.com; cell: +94 77 341 3097
blog: http://ruwansblog.blogspot.com
Re: Ability to have hidden services on Axis2
Posted by Ruwan Linton <ru...@gmail.com>.
On Sat, Feb 20, 2010 at 8:44 PM, Deepal jayasinghe <de...@gmail.com>wrote:
> Ruwan Linton wrote:
> > No those are normal services,
> You are contradicting yourself.
>
Nope, I am not. Administrator services can exists as aar services, jar
service and osgi bundle based services.
> acting as admin services, to provide the server administration
> > framework. This cannot be solve with a deployer.
> of course you can, sometimes administrator services needs additional
> paramters than normal service, for example if you do not want to display
> them under list services, then you can customize them using the custom
> deployer.
>
AFAIK, in-order to do this, we need to at least put these services into a
different directory or has to have a different extension, please see my
above comment. They are normal aar, jar services which provides some server
administration operations.
> > Also I don't see this as a hack.
> Either way I have no problem, but I see long term advantage of having
> separate deployer for admin service, I bet you that you will soon have
> some other additional requirements.
>
Hhhmm, for now it is just this... and I don't see any near future
requirements, so I would add this param check before the INFO log, which
will have no harm at all.
Thanks,
Ruwan
> >
> > Thanks,
> > Ruwan
> >
> > On Sat, Feb 20, 2010 at 8:32 PM, Deepal jayasinghe <deepalk@gmail.com
> > <ma...@gmail.com>> wrote:
> >
> > How about adding a hidden service deployer ? I think that approach is
> > much cleaner than hacking the code.
> > > Devs,
> > >
> > > WSO2 Carbon [http://wso2.org/projects/carbon] which depends on and
> > > uses axis2 has a requirement to have hidden admin services, bu the
> > > DeploymentEngine prints an INFO log message for all the service
> > > deployments, in order to achieve the above requirement, how about
> > > filtering this log statement by looking at a service group
> parameter
> > > named hiddenService.
> > >
> > > If there is no objection I will get this implemented.
> > >
> > > Thanks,
> > > Ruwan
> > >
> > > --
> > > Ruwan Linton
> > > Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
> > > WSO2 Inc.; http://wso2.org
> > > email: ruwan@wso2.com <ma...@wso2.com>
> > <mailto:ruwan@wso2.com <ma...@wso2.com>>; cell: +94 77 341
> 3097
> > > blog: http://ruwansblog.blogspot.com
> >
> >
> > --
> > Thank you!
> >
> >
> > http://blogs.deepal.org
> > http://deepal.org
> >
> >
> >
> >
> > --
> > Ruwan Linton
> > Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
> > WSO2 Inc.; http://wso2.org
> > email: ruwan@wso2.com <ma...@wso2.com>; cell: +94 77 341 3097
> > blog: http://ruwansblog.blogspot.com
>
>
> --
> Thank you!
>
>
> http://blogs.deepal.org
> http://deepal.org
>
>
--
Ruwan Linton
Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
WSO2 Inc.; http://wso2.org
email: ruwan@wso2.com; cell: +94 77 341 3097
blog: http://ruwansblog.blogspot.com
Re: Ability to have hidden services on Axis2
Posted by Deepal jayasinghe <de...@gmail.com>.
Ruwan Linton wrote:
> No those are normal services,
You are contradicting yourself.
> acting as admin services, to provide the server administration
> framework. This cannot be solve with a deployer.
of course you can, sometimes administrator services needs additional
paramters than normal service, for example if you do not want to display
them under list services, then you can customize them using the custom
deployer.
> Also I don't see this as a hack.
Either way I have no problem, but I see long term advantage of having
separate deployer for admin service, I bet you that you will soon have
some other additional requirements.
>
> Thanks,
> Ruwan
>
> On Sat, Feb 20, 2010 at 8:32 PM, Deepal jayasinghe <deepalk@gmail.com
> <ma...@gmail.com>> wrote:
>
> How about adding a hidden service deployer ? I think that approach is
> much cleaner than hacking the code.
> > Devs,
> >
> > WSO2 Carbon [http://wso2.org/projects/carbon] which depends on and
> > uses axis2 has a requirement to have hidden admin services, bu the
> > DeploymentEngine prints an INFO log message for all the service
> > deployments, in order to achieve the above requirement, how about
> > filtering this log statement by looking at a service group parameter
> > named hiddenService.
> >
> > If there is no objection I will get this implemented.
> >
> > Thanks,
> > Ruwan
> >
> > --
> > Ruwan Linton
> > Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
> > WSO2 Inc.; http://wso2.org
> > email: ruwan@wso2.com <ma...@wso2.com>
> <mailto:ruwan@wso2.com <ma...@wso2.com>>; cell: +94 77 341 3097
> > blog: http://ruwansblog.blogspot.com
>
>
> --
> Thank you!
>
>
> http://blogs.deepal.org
> http://deepal.org
>
>
>
>
> --
> Ruwan Linton
> Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
> WSO2 Inc.; http://wso2.org
> email: ruwan@wso2.com <ma...@wso2.com>; cell: +94 77 341 3097
> blog: http://ruwansblog.blogspot.com
--
Thank you!
http://blogs.deepal.org
http://deepal.org
Re: Ability to have hidden services on Axis2
Posted by Ruwan Linton <ru...@gmail.com>.
No those are normal services, acting as admin services, to provide the
server administration framework. This cannot be solve with a deployer. Also
I don't see this as a hack.
Thanks,
Ruwan
On Sat, Feb 20, 2010 at 8:32 PM, Deepal jayasinghe <de...@gmail.com>wrote:
> How about adding a hidden service deployer ? I think that approach is
> much cleaner than hacking the code.
> > Devs,
> >
> > WSO2 Carbon [http://wso2.org/projects/carbon] which depends on and
> > uses axis2 has a requirement to have hidden admin services, bu the
> > DeploymentEngine prints an INFO log message for all the service
> > deployments, in order to achieve the above requirement, how about
> > filtering this log statement by looking at a service group parameter
> > named hiddenService.
> >
> > If there is no objection I will get this implemented.
> >
> > Thanks,
> > Ruwan
> >
> > --
> > Ruwan Linton
> > Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
> > WSO2 Inc.; http://wso2.org
> > email: ruwan@wso2.com <ma...@wso2.com>; cell: +94 77 341 3097
> > blog: http://ruwansblog.blogspot.com
>
>
> --
> Thank you!
>
>
> http://blogs.deepal.org
> http://deepal.org
>
>
--
Ruwan Linton
Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
WSO2 Inc.; http://wso2.org
email: ruwan@wso2.com; cell: +94 77 341 3097
blog: http://ruwansblog.blogspot.com
Re: Ability to have hidden services on Axis2
Posted by Deepal jayasinghe <de...@gmail.com>.
How about adding a hidden service deployer ? I think that approach is
much cleaner than hacking the code.
> Devs,
>
> WSO2 Carbon [http://wso2.org/projects/carbon] which depends on and
> uses axis2 has a requirement to have hidden admin services, bu the
> DeploymentEngine prints an INFO log message for all the service
> deployments, in order to achieve the above requirement, how about
> filtering this log statement by looking at a service group parameter
> named hiddenService.
>
> If there is no objection I will get this implemented.
>
> Thanks,
> Ruwan
>
> --
> Ruwan Linton
> Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
> WSO2 Inc.; http://wso2.org
> email: ruwan@wso2.com <ma...@wso2.com>; cell: +94 77 341 3097
> blog: http://ruwansblog.blogspot.com
--
Thank you!
http://blogs.deepal.org
http://deepal.org
Re: Ability to have hidden services on Axis2
Posted by Glen Daniels <gl...@thoughtcraft.com>.
Correct. Everyone who was on axis-dev@ws is now on java-dev@axis. We'll be
dropping the old lists soon, after all the other lists (rampart-dev, etc) are
fully merged in.
--Glen
On 2/20/2010 10:14 AM, Sanjiva Weerawarana wrote:
> I think we migrated all subscribers to the new list right? AFAIK there's
> no need to cc the old list!
>
> Glen can you confirm please?
>
> Sanjiva.
>
> On Sat, Feb 20, 2010 at 8:29 PM, Ruwan Linton <ruwan.linton@gmail.com
> <ma...@gmail.com>> wrote:
>
> Devs,
>
> WSO2 Carbon [http://wso2.org/projects/carbon] which depends on and
> uses axis2 has a requirement to have hidden admin services, bu the
> DeploymentEngine prints an INFO log message for all the service
> deployments, in order to achieve the above requirement, how about
> filtering this log statement by looking at a service group parameter
> named hiddenService.
>
> If there is no objection I will get this implemented.
>
> Thanks,
> Ruwan
>
> --
> Ruwan Linton
> Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
> WSO2 Inc.; http://wso2.org
> email: ruwan@wso2.com <ma...@wso2.com>; cell: +94 77 341 3097
> blog: http://ruwansblog.blogspot.com
>
>
>
>
> --
> Sanjiva Weerawarana, Ph.D.
> Founder, Director & Chief Scientist; Lanka Software Foundation;
> http://www.opensource.lk/
> Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
> Member; Apache Software Foundation; http://www.apache.org/
> Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/
>
> Blog: http://sanjiva.weerawarana.org/
Re: Ability to have hidden services on Axis2
Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
I think we migrated all subscribers to the new list right? AFAIK there's no
need to cc the old list!
Glen can you confirm please?
Sanjiva.
On Sat, Feb 20, 2010 at 8:29 PM, Ruwan Linton <ru...@gmail.com>wrote:
> Devs,
>
> WSO2 Carbon [http://wso2.org/projects/carbon] which depends on and uses
> axis2 has a requirement to have hidden admin services, bu the
> DeploymentEngine prints an INFO log message for all the service deployments,
> in order to achieve the above requirement, how about filtering this log
> statement by looking at a service group parameter named hiddenService.
>
> If there is no objection I will get this implemented.
>
> Thanks,
> Ruwan
>
> --
> Ruwan Linton
> Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
> WSO2 Inc.; http://wso2.org
> email: ruwan@wso2.com; cell: +94 77 341 3097
> blog: http://ruwansblog.blogspot.com
>
--
Sanjiva Weerawarana, Ph.D.
Founder, Director & Chief Scientist; Lanka Software Foundation;
http://www.opensource.lk/
Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
Member; Apache Software Foundation; http://www.apache.org/
Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/
Blog: http://sanjiva.weerawarana.org/
Re: Ability to have hidden services on Axis2
Posted by Ruwan Linton <ru...@gmail.com>.
Hi Glen,
On Sun, Feb 21, 2010 at 7:50 PM, Glen Daniels <gl...@thoughtcraft.com> wrote:
> Hi Ruwan, all,
>
> I'm afraid I don't get this change. Amila makes a good point I think; I
> can
> totally understand why you wouldn't want certain services showing up on the
> UI (although even then you would want admins to see them), but the INFO
> message is on the actual console of the server, which only admins should
> have
> access to anyway.
These services are used by the admins, but via a user interface. We have a
concept called controlled operations in axis2 right?? To me this is
something like that. If I get a service hosting environment, and I see
various services getting deployed on the console, except for my service,
doesn't it confuses the user?
> What do you gain from this change, aside from making it
> harder to tell if your services are coming up correctly or not? :)
>
Well, this is just for the INFO message, if the service deployment fails
then the user will see the errors.
BTW: I have already committed this change ;-), if the community thinks this
is not a valid requirement, I am happy to revert the commit :-)
Thanks,
Ruwan
>
> --Glen
>
> On 2/21/2010 5:18 AM, Amila Suriarachchi wrote:
> >
> >
> > On Sat, Feb 20, 2010 at 8:29 PM, Ruwan Linton <ruwan.linton@gmail.com
> > <ma...@gmail.com>> wrote:
> >
> > Devs,
> >
> > WSO2 Carbon [http://wso2.org/projects/carbon] which depends on and
> > uses axis2 has a requirement to have hidden admin services,
> >
> > I think a hidden service is a service which should not display in the
> > carbon Admin console.
> >
> >
> > bu the DeploymentEngine prints an INFO log message for all the
> > service deployments, in order to achieve the above requirement,
> >
> > What is the problem with this INFO message print in the command line or
> > a log file? I think those INFO messages are only visible to admin or who
> > ever access to deployments. Isn't it nice to know even these Admin
> > services get deployed properly?
> >
> > Thanks,
> > Amila.
> >
> > how about filtering this log statement by looking at a service group
> > parameter named hiddenService.
> >
> > If there is no objection I will get this implemented.
> >
> > Thanks,
> > Ruwan
> >
> > --
> > Ruwan Linton
> > Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
> > WSO2 Inc.; http://wso2.org
> > email: ruwan@wso2.com <ma...@wso2.com>; cell: +94 77 341 3097
> > blog: http://ruwansblog.blogspot.com
> >
> >
> >
> >
> > --
> > Amila Suriarachchi
> > WSO2 Inc.
> > blog: http://amilachinthaka.blogspot.com/
>
--
Ruwan Linton
Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
WSO2 Inc.; http://wso2.org
email: ruwan@wso2.com; cell: +94 77 341 3097
blog: http://ruwansblog.blogspot.com
unsubscribe
Posted by Jonathan Roberts <jr...@rjlg.com>.
Sent from my iPhone
On Feb 21, 2010, at 6:04 PM, "Ramaswamy, Pudur"
<pu...@paypal.com> wrote:
>
>
> Thanks,
> -Pudur
>
>
>> -----Original Message-----
>> From: Deepal jayasinghe [mailto:deepalk@gmail.com]
>> Sent: Sunday, February 21, 2010 7:01 AM
>> To: java-dev@axis.apache.org
>> Subject: Re: Ability to have hidden services on Axis2
>>
>>
>>>
>>> This is something questionable. If a service got deployed once
>>> successfully, can it fail at the next reboot? "without" any changes
>>> being done? If so, the deployment is not predictable.
>> Yes it can fail, what happen if you remove a module (mar)
>> file which the service needs, then it fails to start. Or
>> else, assume you store some information in a persistent
>> storage due to some reason trx fails, so service deployment
>> might fail. And I strongly suggested you to go and look at
>> some of the JIRA, they have mentioned those issues, and they
>> have mentioned issues regarding deployment failures after the
>> first deployment.
>>>
>>> I'm excluding the possibility of a service failing to deploy due to
>>> some issues in its implementation, which can change per each
>>> deployment made, which could cause such issues. This is because,
>>> managing such error situations should be a responsibility of the
>>> service author.
>>>
>>> Thanks,
>>> Senaka.
>>>
>>>
>>>> So, it would be great if this could be made something
>> optional (a
>>>> development time thing), where the default will be
>> not to print
>>>> anything unless something goes wrong in the deployment process
>>> (which
>>>> will print an error or warning, as it suits). This is IMHO.
>>>>
>>> For me change you guys have done is very simple, it
>> does not affect
>>> anything, no performance overhead.
>>>> WDYT?
>>>>
>>>> Thanks,
>>>> Senaka.
>>>>
>>>> On Sun, Feb 21, 2010 at 7:50 PM, Glen Daniels
>>> <glen@thoughtcraft.com <ma...@thoughtcraft.com>
>>>> <mailto:glen@thoughtcraft.com <ma...@thoughtcraft.com>>>
>>> wrote:
>>>>
>>>> Hi Ruwan, all,
>>>>
>>>> I'm afraid I don't get this change. Amila makes
>> a good point I
>>>> think; I can
>>>> totally understand why you wouldn't want certain services
>>> showing
>>>> up on the
>>>> UI (although even then you would want admins to see them),
>>> but the
>>>> INFO
>>>> message is on the actual console of the server, which only
>>> admins
>>>> should have
>>>> access to anyway. What do you gain from this
>> change, aside from
>>>> making it
>>>> harder to tell if your services are coming up correctly or
>>> not? :)
>>>>
>>>> --Glen
>>>>
>>>> On 2/21/2010 5:18 AM, Amila Suriarachchi wrote:
>>>>>
>>>>>
>>>>> On Sat, Feb 20, 2010 at 8:29 PM, Ruwan Linton
>>>> <ruwan.linton@gmail.com <ma...@gmail.com>
>>> <mailto:ruwan.linton@gmail.com <ma...@gmail.com>>
>>>>> <mailto:ruwan.linton@gmail.com
>>> <ma...@gmail.com> <mailto:ruwan.linton@gmail.com
>>> <ma...@gmail.com>>>>
>>>> wrote:
>>>>>
>>>>> Devs,
>>>>>
>>>>> WSO2 Carbon [http://wso2.org/projects/carbon] which
>>> depends
>>>> on and
>>>>> uses axis2 has a requirement to have hidden admin
>>> services,
>>>>>
>>>>> I think a hidden service is a service which
>> should not display
>>>> in the
>>>>> carbon Admin console.
>>>>>
>>>>>
>>>>> bu the DeploymentEngine prints an INFO log
>> message for
>>> all the
>>>>> service deployments, in order to achieve the above
>>> requirement,
>>>>>
>>>>> What is the problem with this INFO message print in the
>>> command
>>>> line or
>>>>> a log file? I think those INFO messages are
>> only visible to
>>>> admin or who
>>>>> ever access to deployments. Isn't it nice to know even
>>> these Admin
>>>>> services get deployed properly?
>>>>>
>>>>> Thanks,
>>>>> Amila.
>>>>>
>>>>> how about filtering this log statement by
>> looking at a
>>>> service group
>>>>> parameter named hiddenService.
>>>>>
>>>>> If there is no objection I will get this
>> implemented.
>>>>>
>>>>> Thanks,
>>>>> Ruwan
>>>>>
>>>>> --
>>>>> Ruwan Linton
>>>>> Technical Lead & Product Manager; WSO2 ESB;
>>> http://wso2.org/esb
>>>>> WSO2 Inc.; http://wso2.org
>>>>> email: ruwan@wso2.com <ma...@wso2.com>
>>> <mailto:ruwan@wso2.com <ma...@wso2.com>>
>>>> <mailto:ruwan@wso2.com <ma...@wso2.com>
>>> <mailto:ruwan@wso2.com <ma...@wso2.com>>>; cell:
>> +94 77 341
>>> 3097
>>>>> blog: http://ruwansblog.blogspot.com
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Amila Suriarachchi
>>>>> WSO2 Inc.
>>>>> blog: http://amilachinthaka.blogspot.com/
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Senaka Fernando
>>>> Software Engineer
>>>> WSO2 Inc.
>>>> E-mail: senaka AT wso2.com <http://wso2.com>
>> <http://wso2.com>;
>>> Mobile: +94 77 322 1818
>>>>
>>>> http://www.wso2.com/ - "Lean . Enterprise . Middleware"
>>>
>>>
>>> --
>>> Thank you!
>>>
>>>
>>> http://blogs.deepal.org
>>> http://deepal.org
>>>
>>>
>>>
>>>
>>> --
>>> Senaka Fernando
>>> Software Engineer
>>> WSO2 Inc.
>>> E-mail: senaka AT wso2.com <http://wso2.com>; Mobile: +94
>> 77 322 1818
>>>
>>> http://www.wso2.com/ - "Lean . Enterprise . Middleware"
>>
>>
>> --
>> Thank you!
>>
>>
>> http://blogs.deepal.org
>> http://deepal.org
>>
>>
unsubscribe
Posted by "Capilla Castillo, Esther" <ec...@indra.es>.
Unsubscribe.
Thanks!
unsubscribe
Posted by "Ramaswamy, Pudur" <pu...@paypal.com>.
Thanks,
-Pudur
> -----Original Message-----
> From: Deepal jayasinghe [mailto:deepalk@gmail.com]
> Sent: Sunday, February 21, 2010 7:01 AM
> To: java-dev@axis.apache.org
> Subject: Re: Ability to have hidden services on Axis2
>
>
> >
> > This is something questionable. If a service got deployed once
> > successfully, can it fail at the next reboot? "without" any changes
> > being done? If so, the deployment is not predictable.
> Yes it can fail, what happen if you remove a module (mar)
> file which the service needs, then it fails to start. Or
> else, assume you store some information in a persistent
> storage due to some reason trx fails, so service deployment
> might fail. And I strongly suggested you to go and look at
> some of the JIRA, they have mentioned those issues, and they
> have mentioned issues regarding deployment failures after the
> first deployment.
> >
> > I'm excluding the possibility of a service failing to deploy due to
> > some issues in its implementation, which can change per each
> > deployment made, which could cause such issues. This is because,
> > managing such error situations should be a responsibility of the
> > service author.
> >
> > Thanks,
> > Senaka.
> >
> >
> > > So, it would be great if this could be made something
> optional (a
> > > development time thing), where the default will be
> not to print
> > > anything unless something goes wrong in the deployment process
> > (which
> > > will print an error or warning, as it suits). This is IMHO.
> > >
> > For me change you guys have done is very simple, it
> does not affect
> > anything, no performance overhead.
> > > WDYT?
> > >
> > > Thanks,
> > > Senaka.
> > >
> > > On Sun, Feb 21, 2010 at 7:50 PM, Glen Daniels
> > <glen@thoughtcraft.com <ma...@thoughtcraft.com>
> > > <mailto:glen@thoughtcraft.com <ma...@thoughtcraft.com>>>
> > wrote:
> > >
> > > Hi Ruwan, all,
> > >
> > > I'm afraid I don't get this change. Amila makes
> a good point I
> > > think; I can
> > > totally understand why you wouldn't want certain services
> > showing
> > > up on the
> > > UI (although even then you would want admins to see them),
> > but the
> > > INFO
> > > message is on the actual console of the server, which only
> > admins
> > > should have
> > > access to anyway. What do you gain from this
> change, aside from
> > > making it
> > > harder to tell if your services are coming up correctly or
> > not? :)
> > >
> > > --Glen
> > >
> > > On 2/21/2010 5:18 AM, Amila Suriarachchi wrote:
> > > >
> > > >
> > > > On Sat, Feb 20, 2010 at 8:29 PM, Ruwan Linton
> > > <ruwan.linton@gmail.com <ma...@gmail.com>
> > <mailto:ruwan.linton@gmail.com <ma...@gmail.com>>
> > > > <mailto:ruwan.linton@gmail.com
> > <ma...@gmail.com> <mailto:ruwan.linton@gmail.com
> > <ma...@gmail.com>>>>
> > > wrote:
> > > >
> > > > Devs,
> > > >
> > > > WSO2 Carbon [http://wso2.org/projects/carbon] which
> > depends
> > > on and
> > > > uses axis2 has a requirement to have hidden admin
> > services,
> > > >
> > > > I think a hidden service is a service which
> should not display
> > > in the
> > > > carbon Admin console.
> > > >
> > > >
> > > > bu the DeploymentEngine prints an INFO log
> message for
> > all the
> > > > service deployments, in order to achieve the above
> > requirement,
> > > >
> > > > What is the problem with this INFO message print in the
> > command
> > > line or
> > > > a log file? I think those INFO messages are
> only visible to
> > > admin or who
> > > > ever access to deployments. Isn't it nice to know even
> > these Admin
> > > > services get deployed properly?
> > > >
> > > > Thanks,
> > > > Amila.
> > > >
> > > > how about filtering this log statement by
> looking at a
> > > service group
> > > > parameter named hiddenService.
> > > >
> > > > If there is no objection I will get this
> implemented.
> > > >
> > > > Thanks,
> > > > Ruwan
> > > >
> > > > --
> > > > Ruwan Linton
> > > > Technical Lead & Product Manager; WSO2 ESB;
> > http://wso2.org/esb
> > > > WSO2 Inc.; http://wso2.org
> > > > email: ruwan@wso2.com <ma...@wso2.com>
> > <mailto:ruwan@wso2.com <ma...@wso2.com>>
> > > <mailto:ruwan@wso2.com <ma...@wso2.com>
> > <mailto:ruwan@wso2.com <ma...@wso2.com>>>; cell:
> +94 77 341
> > 3097
> > > > blog: http://ruwansblog.blogspot.com
> > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Amila Suriarachchi
> > > > WSO2 Inc.
> > > > blog: http://amilachinthaka.blogspot.com/
> > >
> > >
> > >
> > >
> > > --
> > > Senaka Fernando
> > > Software Engineer
> > > WSO2 Inc.
> > > E-mail: senaka AT wso2.com <http://wso2.com>
> <http://wso2.com>;
> > Mobile: +94 77 322 1818
> > >
> > > http://www.wso2.com/ - "Lean . Enterprise . Middleware"
> >
> >
> > --
> > Thank you!
> >
> >
> > http://blogs.deepal.org
> > http://deepal.org
> >
> >
> >
> >
> > --
> > Senaka Fernando
> > Software Engineer
> > WSO2 Inc.
> > E-mail: senaka AT wso2.com <http://wso2.com>; Mobile: +94
> 77 322 1818
> >
> > http://www.wso2.com/ - "Lean . Enterprise . Middleware"
>
>
> --
> Thank you!
>
>
> http://blogs.deepal.org
> http://deepal.org
>
>
Re: Ability to have hidden services on Axis2
Posted by Deepal jayasinghe <de...@gmail.com>.
>
> This is something questionable. If a service got deployed once
> successfully, can it fail at the next reboot? "without" any changes
> being done? If so, the deployment is not predictable.
Yes it can fail, what happen if you remove a module (mar) file which the
service needs, then it fails to start. Or else, assume you store some
information in a persistent storage due to some reason trx fails, so
service deployment might fail. And I strongly suggested you to go and
look at some of the JIRA, they have mentioned those issues, and they
have mentioned issues regarding deployment failures after the first
deployment.
>
> I'm excluding the possibility of a service failing to deploy due to
> some issues in its implementation, which can change per each
> deployment made, which could cause such issues. This is because,
> managing such error situations should be a responsibility of the
> service author.
>
> Thanks,
> Senaka.
>
>
> > So, it would be great if this could be made something optional (a
> > development time thing), where the default will be not to print
> > anything unless something goes wrong in the deployment process
> (which
> > will print an error or warning, as it suits). This is IMHO.
> >
> For me change you guys have done is very simple, it does not affect
> anything, no performance overhead.
> > WDYT?
> >
> > Thanks,
> > Senaka.
> >
> > On Sun, Feb 21, 2010 at 7:50 PM, Glen Daniels
> <glen@thoughtcraft.com <ma...@thoughtcraft.com>
> > <mailto:glen@thoughtcraft.com <ma...@thoughtcraft.com>>>
> wrote:
> >
> > Hi Ruwan, all,
> >
> > I'm afraid I don't get this change. Amila makes a good point I
> > think; I can
> > totally understand why you wouldn't want certain services
> showing
> > up on the
> > UI (although even then you would want admins to see them),
> but the
> > INFO
> > message is on the actual console of the server, which only
> admins
> > should have
> > access to anyway. What do you gain from this change, aside from
> > making it
> > harder to tell if your services are coming up correctly or
> not? :)
> >
> > --Glen
> >
> > On 2/21/2010 5:18 AM, Amila Suriarachchi wrote:
> > >
> > >
> > > On Sat, Feb 20, 2010 at 8:29 PM, Ruwan Linton
> > <ruwan.linton@gmail.com <ma...@gmail.com>
> <mailto:ruwan.linton@gmail.com <ma...@gmail.com>>
> > > <mailto:ruwan.linton@gmail.com
> <ma...@gmail.com> <mailto:ruwan.linton@gmail.com
> <ma...@gmail.com>>>>
> > wrote:
> > >
> > > Devs,
> > >
> > > WSO2 Carbon [http://wso2.org/projects/carbon] which
> depends
> > on and
> > > uses axis2 has a requirement to have hidden admin
> services,
> > >
> > > I think a hidden service is a service which should not display
> > in the
> > > carbon Admin console.
> > >
> > >
> > > bu the DeploymentEngine prints an INFO log message for
> all the
> > > service deployments, in order to achieve the above
> requirement,
> > >
> > > What is the problem with this INFO message print in the
> command
> > line or
> > > a log file? I think those INFO messages are only visible to
> > admin or who
> > > ever access to deployments. Isn't it nice to know even
> these Admin
> > > services get deployed properly?
> > >
> > > Thanks,
> > > Amila.
> > >
> > > how about filtering this log statement by looking at a
> > service group
> > > parameter named hiddenService.
> > >
> > > If there is no objection I will get this implemented.
> > >
> > > Thanks,
> > > Ruwan
> > >
> > > --
> > > Ruwan Linton
> > > Technical Lead & Product Manager; WSO2 ESB;
> http://wso2.org/esb
> > > WSO2 Inc.; http://wso2.org
> > > email: ruwan@wso2.com <ma...@wso2.com>
> <mailto:ruwan@wso2.com <ma...@wso2.com>>
> > <mailto:ruwan@wso2.com <ma...@wso2.com>
> <mailto:ruwan@wso2.com <ma...@wso2.com>>>; cell: +94 77 341
> 3097
> > > blog: http://ruwansblog.blogspot.com
> > >
> > >
> > >
> > >
> > > --
> > > Amila Suriarachchi
> > > WSO2 Inc.
> > > blog: http://amilachinthaka.blogspot.com/
> >
> >
> >
> >
> > --
> > Senaka Fernando
> > Software Engineer
> > WSO2 Inc.
> > E-mail: senaka AT wso2.com <http://wso2.com> <http://wso2.com>;
> Mobile: +94 77 322 1818
> >
> > http://www.wso2.com/ - "Lean . Enterprise . Middleware"
>
>
> --
> Thank you!
>
>
> http://blogs.deepal.org
> http://deepal.org
>
>
>
>
> --
> Senaka Fernando
> Software Engineer
> WSO2 Inc.
> E-mail: senaka AT wso2.com <http://wso2.com>; Mobile: +94 77 322 1818
>
> http://www.wso2.com/ - "Lean . Enterprise . Middleware"
--
Thank you!
http://blogs.deepal.org
http://deepal.org
Re: Ability to have hidden services on Axis2
Posted by Senaka Fernando <se...@wso2.com>.
Hi Deepal,
On Sun, Feb 21, 2010 at 8:16 PM, Deepal jayasinghe <de...@gmail.com>wrote:
>
> >
> > Regarding the INFO message that gets logged per service, at
> > deployment. The better side of this is that you get a confirmation to
> > whether your service got deployed. But, the bad side of it is that, if
> > there are 1000+ services hosted (for example), we'll be printing 1000s
> > of such messages.
> Practically speaking it is not good idea to put 1000+ services in one
> Web service server and it is extremely hard to manage. That is why we
> have something called service compositions and ESBs.
>
I just took a nasty example.. :-)...
> > Also, once a person is certain that a particular service is deployed
> > successfully, a confirmation would not be required per each server
> > reboot, unless he did some change.
> I think this is wrong assumption, working a service one time does not
> mean it is going to work forever. So it is required to validate service
> deployment after each system reboot.
>
This is something questionable. If a service got deployed once successfully,
can it fail at the next reboot? "without" any changes being done? If so, the
deployment is not predictable.
I'm excluding the possibility of a service failing to deploy due to some
issues in its implementation, which can change per each deployment made,
which could cause such issues. This is because, managing such error
situations should be a responsibility of the service author.
Thanks,
Senaka.
> > So, it would be great if this could be made something optional (a
> > development time thing), where the default will be not to print
> > anything unless something goes wrong in the deployment process (which
> > will print an error or warning, as it suits). This is IMHO.
> >
> For me change you guys have done is very simple, it does not affect
> anything, no performance overhead.
> > WDYT?
> >
> > Thanks,
> > Senaka.
> >
> > On Sun, Feb 21, 2010 at 7:50 PM, Glen Daniels <glen@thoughtcraft.com
> > <ma...@thoughtcraft.com>> wrote:
> >
> > Hi Ruwan, all,
> >
> > I'm afraid I don't get this change. Amila makes a good point I
> > think; I can
> > totally understand why you wouldn't want certain services showing
> > up on the
> > UI (although even then you would want admins to see them), but the
> > INFO
> > message is on the actual console of the server, which only admins
> > should have
> > access to anyway. What do you gain from this change, aside from
> > making it
> > harder to tell if your services are coming up correctly or not? :)
> >
> > --Glen
> >
> > On 2/21/2010 5:18 AM, Amila Suriarachchi wrote:
> > >
> > >
> > > On Sat, Feb 20, 2010 at 8:29 PM, Ruwan Linton
> > <ruwan.linton@gmail.com <ma...@gmail.com>
> > > <mailto:ruwan.linton@gmail.com <ma...@gmail.com>>>
> > wrote:
> > >
> > > Devs,
> > >
> > > WSO2 Carbon [http://wso2.org/projects/carbon] which depends
> > on and
> > > uses axis2 has a requirement to have hidden admin services,
> > >
> > > I think a hidden service is a service which should not display
> > in the
> > > carbon Admin console.
> > >
> > >
> > > bu the DeploymentEngine prints an INFO log message for all the
> > > service deployments, in order to achieve the above requirement,
> > >
> > > What is the problem with this INFO message print in the command
> > line or
> > > a log file? I think those INFO messages are only visible to
> > admin or who
> > > ever access to deployments. Isn't it nice to know even these Admin
> > > services get deployed properly?
> > >
> > > Thanks,
> > > Amila.
> > >
> > > how about filtering this log statement by looking at a
> > service group
> > > parameter named hiddenService.
> > >
> > > If there is no objection I will get this implemented.
> > >
> > > Thanks,
> > > Ruwan
> > >
> > > --
> > > Ruwan Linton
> > > Technical Lead & Product Manager; WSO2 ESB;
> http://wso2.org/esb
> > > WSO2 Inc.; http://wso2.org
> > > email: ruwan@wso2.com <ma...@wso2.com>
> > <mailto:ruwan@wso2.com <ma...@wso2.com>>; cell: +94 77 341
> 3097
> > > blog: http://ruwansblog.blogspot.com
> > >
> > >
> > >
> > >
> > > --
> > > Amila Suriarachchi
> > > WSO2 Inc.
> > > blog: http://amilachinthaka.blogspot.com/
> >
> >
> >
> >
> > --
> > Senaka Fernando
> > Software Engineer
> > WSO2 Inc.
> > E-mail: senaka AT wso2.com <http://wso2.com>; Mobile: +94 77 322 1818
> >
> > http://www.wso2.com/ - "Lean . Enterprise . Middleware"
>
>
> --
> Thank you!
>
>
> http://blogs.deepal.org
> http://deepal.org
>
>
--
Senaka Fernando
Software Engineer
WSO2 Inc.
E-mail: senaka AT wso2.com; Mobile: +94 77 322 1818
http://www.wso2.com/ - "Lean . Enterprise . Middleware"
Re: Ability to have hidden services on Axis2
Posted by Deepal jayasinghe <de...@gmail.com>.
>
> Regarding the INFO message that gets logged per service, at
> deployment. The better side of this is that you get a confirmation to
> whether your service got deployed. But, the bad side of it is that, if
> there are 1000+ services hosted (for example), we'll be printing 1000s
> of such messages.
Practically speaking it is not good idea to put 1000+ services in one
Web service server and it is extremely hard to manage. That is why we
have something called service compositions and ESBs.
> Also, once a person is certain that a particular service is deployed
> successfully, a confirmation would not be required per each server
> reboot, unless he did some change.
I think this is wrong assumption, working a service one time does not
mean it is going to work forever. So it is required to validate service
deployment after each system reboot.
> So, it would be great if this could be made something optional (a
> development time thing), where the default will be not to print
> anything unless something goes wrong in the deployment process (which
> will print an error or warning, as it suits). This is IMHO.
>
For me change you guys have done is very simple, it does not affect
anything, no performance overhead.
> WDYT?
>
> Thanks,
> Senaka.
>
> On Sun, Feb 21, 2010 at 7:50 PM, Glen Daniels <glen@thoughtcraft.com
> <ma...@thoughtcraft.com>> wrote:
>
> Hi Ruwan, all,
>
> I'm afraid I don't get this change. Amila makes a good point I
> think; I can
> totally understand why you wouldn't want certain services showing
> up on the
> UI (although even then you would want admins to see them), but the
> INFO
> message is on the actual console of the server, which only admins
> should have
> access to anyway. What do you gain from this change, aside from
> making it
> harder to tell if your services are coming up correctly or not? :)
>
> --Glen
>
> On 2/21/2010 5:18 AM, Amila Suriarachchi wrote:
> >
> >
> > On Sat, Feb 20, 2010 at 8:29 PM, Ruwan Linton
> <ruwan.linton@gmail.com <ma...@gmail.com>
> > <mailto:ruwan.linton@gmail.com <ma...@gmail.com>>>
> wrote:
> >
> > Devs,
> >
> > WSO2 Carbon [http://wso2.org/projects/carbon] which depends
> on and
> > uses axis2 has a requirement to have hidden admin services,
> >
> > I think a hidden service is a service which should not display
> in the
> > carbon Admin console.
> >
> >
> > bu the DeploymentEngine prints an INFO log message for all the
> > service deployments, in order to achieve the above requirement,
> >
> > What is the problem with this INFO message print in the command
> line or
> > a log file? I think those INFO messages are only visible to
> admin or who
> > ever access to deployments. Isn't it nice to know even these Admin
> > services get deployed properly?
> >
> > Thanks,
> > Amila.
> >
> > how about filtering this log statement by looking at a
> service group
> > parameter named hiddenService.
> >
> > If there is no objection I will get this implemented.
> >
> > Thanks,
> > Ruwan
> >
> > --
> > Ruwan Linton
> > Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
> > WSO2 Inc.; http://wso2.org
> > email: ruwan@wso2.com <ma...@wso2.com>
> <mailto:ruwan@wso2.com <ma...@wso2.com>>; cell: +94 77 341 3097
> > blog: http://ruwansblog.blogspot.com
> >
> >
> >
> >
> > --
> > Amila Suriarachchi
> > WSO2 Inc.
> > blog: http://amilachinthaka.blogspot.com/
>
>
>
>
> --
> Senaka Fernando
> Software Engineer
> WSO2 Inc.
> E-mail: senaka AT wso2.com <http://wso2.com>; Mobile: +94 77 322 1818
>
> http://www.wso2.com/ - "Lean . Enterprise . Middleware"
--
Thank you!
http://blogs.deepal.org
http://deepal.org
Re: Ability to have hidden services on Axis2
Posted by Senaka Fernando <se...@apache.org>.
Hi all,
Regarding the INFO message that gets logged per service, at deployment. The
better side of this is that you get a confirmation to whether your service
got deployed. But, the bad side of it is that, if there are 1000+ services
hosted (for example), we'll be printing 1000s of such messages. Also, once a
person is certain that a particular service is deployed successfully, a
confirmation would not be required per each server reboot, unless he did
some change. So, it would be great if this could be made something optional
(a development time thing), where the default will be not to print anything
unless something goes wrong in the deployment process (which will print an
error or warning, as it suits). This is IMHO.
WDYT?
Thanks,
Senaka.
On Sun, Feb 21, 2010 at 7:50 PM, Glen Daniels <gl...@thoughtcraft.com> wrote:
> Hi Ruwan, all,
>
> I'm afraid I don't get this change. Amila makes a good point I think; I
> can
> totally understand why you wouldn't want certain services showing up on the
> UI (although even then you would want admins to see them), but the INFO
> message is on the actual console of the server, which only admins should
> have
> access to anyway. What do you gain from this change, aside from making it
> harder to tell if your services are coming up correctly or not? :)
>
> --Glen
>
> On 2/21/2010 5:18 AM, Amila Suriarachchi wrote:
> >
> >
> > On Sat, Feb 20, 2010 at 8:29 PM, Ruwan Linton <ruwan.linton@gmail.com
> > <ma...@gmail.com>> wrote:
> >
> > Devs,
> >
> > WSO2 Carbon [http://wso2.org/projects/carbon] which depends on and
> > uses axis2 has a requirement to have hidden admin services,
> >
> > I think a hidden service is a service which should not display in the
> > carbon Admin console.
> >
> >
> > bu the DeploymentEngine prints an INFO log message for all the
> > service deployments, in order to achieve the above requirement,
> >
> > What is the problem with this INFO message print in the command line or
> > a log file? I think those INFO messages are only visible to admin or who
> > ever access to deployments. Isn't it nice to know even these Admin
> > services get deployed properly?
> >
> > Thanks,
> > Amila.
> >
> > how about filtering this log statement by looking at a service group
> > parameter named hiddenService.
> >
> > If there is no objection I will get this implemented.
> >
> > Thanks,
> > Ruwan
> >
> > --
> > Ruwan Linton
> > Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
> > WSO2 Inc.; http://wso2.org
> > email: ruwan@wso2.com <ma...@wso2.com>; cell: +94 77 341 3097
> > blog: http://ruwansblog.blogspot.com
> >
> >
> >
> >
> > --
> > Amila Suriarachchi
> > WSO2 Inc.
> > blog: http://amilachinthaka.blogspot.com/
>
--
Senaka Fernando
Software Engineer
WSO2 Inc.
E-mail: senaka AT wso2.com; Mobile: +94 77 322 1818
http://www.wso2.com/ - "Lean . Enterprise . Middleware"
Re: Ability to have hidden services on Axis2
Posted by Glen Daniels <gl...@thoughtcraft.com>.
Hi Ruwan, all,
I'm afraid I don't get this change. Amila makes a good point I think; I can
totally understand why you wouldn't want certain services showing up on the
UI (although even then you would want admins to see them), but the INFO
message is on the actual console of the server, which only admins should have
access to anyway. What do you gain from this change, aside from making it
harder to tell if your services are coming up correctly or not? :)
--Glen
On 2/21/2010 5:18 AM, Amila Suriarachchi wrote:
>
>
> On Sat, Feb 20, 2010 at 8:29 PM, Ruwan Linton <ruwan.linton@gmail.com
> <ma...@gmail.com>> wrote:
>
> Devs,
>
> WSO2 Carbon [http://wso2.org/projects/carbon] which depends on and
> uses axis2 has a requirement to have hidden admin services,
>
> I think a hidden service is a service which should not display in the
> carbon Admin console.
>
>
> bu the DeploymentEngine prints an INFO log message for all the
> service deployments, in order to achieve the above requirement,
>
> What is the problem with this INFO message print in the command line or
> a log file? I think those INFO messages are only visible to admin or who
> ever access to deployments. Isn't it nice to know even these Admin
> services get deployed properly?
>
> Thanks,
> Amila.
>
> how about filtering this log statement by looking at a service group
> parameter named hiddenService.
>
> If there is no objection I will get this implemented.
>
> Thanks,
> Ruwan
>
> --
> Ruwan Linton
> Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
> WSO2 Inc.; http://wso2.org
> email: ruwan@wso2.com <ma...@wso2.com>; cell: +94 77 341 3097
> blog: http://ruwansblog.blogspot.com
>
>
>
>
> --
> Amila Suriarachchi
> WSO2 Inc.
> blog: http://amilachinthaka.blogspot.com/
Re: Ability to have hidden services on Axis2
Posted by Amila Suriarachchi <am...@gmail.com>.
On Sat, Feb 20, 2010 at 8:29 PM, Ruwan Linton <ru...@gmail.com>wrote:
> Devs,
>
> WSO2 Carbon [http://wso2.org/projects/carbon] which depends on and uses
> axis2 has a requirement to have hidden admin services,
I think a hidden service is a service which should not display in the carbon
Admin console.
> bu the DeploymentEngine prints an INFO log message for all the service
> deployments, in order to achieve the above requirement,
>
What is the problem with this INFO message print in the command line or a
log file? I think those INFO messages are only visible to admin or who ever
access to deployments. Isn't it nice to know even these Admin services get
deployed properly?
Thanks,
Amila.
> how about filtering this log statement by looking at a service group
> parameter named hiddenService.
>
> If there is no objection I will get this implemented.
>
> Thanks,
> Ruwan
>
> --
> Ruwan Linton
> Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
> WSO2 Inc.; http://wso2.org
> email: ruwan@wso2.com; cell: +94 77 341 3097
> blog: http://ruwansblog.blogspot.com
>
--
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/