Once an OSGi bundle is deployed, it can be activated or deactivated
using regular asadmin enable/disable commands. In that respect, it is no
different from any other kind of application deployment.
Sahoo
On Monday 09 July 2012 08:40 PM, Tom Mueller wrote:
> Earlier in the thread, Tang had said, "In addition, I also want to
> investigate how to add "load" wab bundle on admin-gui, because nowaday,
> once wab is deployed, on admin-gui, the wab can not be launched
> directly." I thought that this was what your URI reference was about.
>
> At this point I don't think I have enough context to be able to give any
> opinion about usage of the CLI in one way or another.
>
> Tom
>
>
>
> On 7/9/2012 10:08 AM, Sahoo wrote:
>> Hi Tom,
>>
>> Could you please explain what you mean by a launch link?
>>
>> What I mean by server resolving the URI is that server would obtain an
>> InputStream for the resource referenced by the URI using something like
>> URI.toURL().openConnection(). That way, any registered URL handler in
>> the server runtime can intercept to decorate the InputStream.
>>
>> Thanks,
>> Sahoo
>> On Monday 09 July 2012 07:59 PM, Tom Mueller wrote:
>>> Sahoo,
>>> Would the purpose of the URI be to just provide a launch link in the
>>> console? I don't see how the server would be resolving the URI in that
>>> case.
>>> This can just be a deployment property. Of course, the GUI would need to
>>> pick up that property.
>>>
>>> Tom
>>>