Skip to main content

deployment type osgi

14 replies [Last post]
Anonymous

When I deploy a bundle, with --type osgi, it is started and immediately restarted, why?

[#|2009-04-09T09:46:06.609-0700|INFO|glassfish|org.jvnet.hk2.osgiadapter|_ThreadID=20;_ThreadName=Thread-1;org.glassfish.openesb.simple-jndi [318];|Started bundle org.glassfish.openesb.simple-jndi [318]|#]

[#|2009-04-09T09:46:06.611-0700|INFO|glassfish|org.jvnet.hk2.osgiadapter|_ThreadID=20;_ThreadName=Thread-1;org.glassfish.openesb.simple-jndi [318];|Stopped bundle = org.glassfish.openesb.simple-jndi [318]|#]

[#|2009-04-09T09:46:06.612-0700|INFO|glassfish|org.jvnet.hk2.osgiadapter|_ThreadID=20;_ThreadName=Thread-1;org.glassfish.openesb.simple-jndi [318];|Started bundle org.glassfish.openesb.simple-jndi [318]|#]

[#|2009-04-09T09:46:06.629-0700|INFO|glassfish|javax.enterprise.system.tools.admin.org.glassfish.server|_ThreadID=20;_ThreadName=Thread-1;|Deployment of simple-jndi done is 82 ms|#]

Thanks
Annies

[att1.html]

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Jerome Dochez

On Apr 9, 2009, at 1:07 PM, Sahoo wrote:

> What exact command are you using to deploy? I can provide you an
> alternative way to deploy OSGi bundles in GFv3 if you use the latest
> nightly build. Just do the following:
>
> copy this attached cfg file to glassfish/modules dir and then
> copy your OSGi bundles to domains/domain1/autodeploy-modules dir.
yeah but it is not a managed operation, meaning you cannot "undeploy"
them by removing them without again having to go to the directory
structure.

jerome

>
> Thanks,
> Sahoo
>
> Annies wrote:
>>
>> When I deploy a bundle, with --type osgi, it is started and
>> immediately restarted, why?
>>
>> [#|2009-04-09T09:46:06.609-0700|INFO|glassfish|
>> org.jvnet.hk2.osgiadapter|
>> _ThreadID=20;_ThreadName=Thread-1;org.glassfish.openesb.simple-jndi
>> [318];|Started bundle org.glassfish.openesb.simple-jndi [318]|#]
>>
>> [#|2009-04-09T09:46:06.611-0700|INFO|glassfish|
>> org.jvnet.hk2.osgiadapter|
>> _ThreadID=20;_ThreadName=Thread-1;org.glassfish.openesb.simple-jndi
>> [318];|Stopped bundle = org.glassfish.openesb.simple-jndi [318]|#]
>>
>> [#|2009-04-09T09:46:06.612-0700|INFO|glassfish|
>> org.jvnet.hk2.osgiadapter|
>> _ThreadID=20;_ThreadName=Thread-1;org.glassfish.openesb.simple-jndi
>> [318];|Started bundle org.glassfish.openesb.simple-jndi [318]|#]
>>
>> [#|2009-04-09T09:46:06.629-0700|INFO|glassfish|
>> javax.enterprise.system.tools.admin.org.glassfish.server|
>> _ThreadID=20;_ThreadName=Thread-1;|Deployment of simple-jndi done
>> is 82 ms|#]
>>
>>
>> Thanks
>> Annies
>>
>>
>>
> #
> # Copyright 2009 Sun Microsystems, Inc. All rights reserved.
> # Use is subject to license terms.
> #
>
> # This configuration file is used by org.apache.felix.fileinstall
> bundle.
> # Author: Sahoo@Sun.COM
>
> # Directory being watched by fileinstall.
> felix.fileinstall.dir=${com.sun.aas.instanceRoot}/autodeploy-modules/
> # Time period fileinstaller thread in ms.
> felix.fileinstall.poll=5000
> # debug level
> felix.fileinstall.debug=1
> # should new bundles be started or installed only? true => start,
> false => only install
> felix.fileinstall.bundles.new.start=true
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
> For additional commands, e-mail: users-help@glassfish.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
For additional commands, e-mail: users-help@glassfish.dev.java.net

Sahoo

Jerome Dochez wrote:
>
> On Apr 9, 2009, at 1:07 PM, Sahoo wrote:
>
>> What exact command are you using to deploy? I can provide you an
>> alternative way to deploy OSGi bundles in GFv3 if you use the latest
>> nightly build. Just do the following:
>>
>> copy this attached cfg file to glassfish/modules dir and then
>> copy your OSGi bundles to domains/domain1/autodeploy-modules dir.
> yeah but it is not a managed operation, meaning you cannot "undeploy"
> them by removing them without again having to go to the directory
> structure.
That's the whole idea of using fileinstall to work as a management
agent. autodeploy-modules works like autodeploy dir. You drop a bundle,
it gets deployed; you remove the bundle and it gets undeployed.

Thanks,
Sahoo
>
> jerome
>
>>
>> Thanks,
>> Sahoo
>>
>> Annies wrote:
>>>
>>> When I deploy a bundle, with --type osgi, it is started and
>>> immediately restarted, why?
>>>
>>> [#|2009-04-09T09:46:06.609-0700|INFO|glassfish|org.jvnet.hk2.osgiadapter|_ThreadID=20;_ThreadName=Thread-1;org.glassfish.openesb.simple-jndi
>>> [318];|Started bundle org.glassfish.openesb.simple-jndi [318]|#]
>>>
>>> [#|2009-04-09T09:46:06.611-0700|INFO|glassfish|org.jvnet.hk2.osgiadapter|_ThreadID=20;_ThreadName=Thread-1;org.glassfish.openesb.simple-jndi
>>> [318];|Stopped bundle = org.glassfish.openesb.simple-jndi [318]|#]
>>>
>>> [#|2009-04-09T09:46:06.612-0700|INFO|glassfish|org.jvnet.hk2.osgiadapter|_ThreadID=20;_ThreadName=Thread-1;org.glassfish.openesb.simple-jndi
>>> [318];|Started bundle org.glassfish.openesb.simple-jndi [318]|#]
>>>
>>> [#|2009-04-09T09:46:06.629-0700|INFO|glassfish|javax.enterprise.system.tools.admin.org.glassfish.server|_ThreadID=20;_ThreadName=Thread-1;|Deployment
>>> of simple-jndi done is 82 ms|#]
>>>
>>>
>>> Thanks
>>> Annies
>>>
>>>
>>>
>> #
>> # Copyright 2009 Sun Microsystems, Inc. All rights reserved.
>> # Use is subject to license terms.
>> #
>>
>> # This configuration file is used by org.apache.felix.fileinstall
>> bundle.
>> # Author: Sahoo@Sun.COM
>>
>> # Directory being watched by fileinstall.
>> felix.fileinstall.dir=${com.sun.aas.instanceRoot}/autodeploy-modules/
>> # Time period fileinstaller thread in ms.
>> felix.fileinstall.poll=5000
>> # debug level
>> felix.fileinstall.debug=1
>> # should new bundles be started or installed only? true => start,
>> false => only install
>> felix.fileinstall.bundles.new.start=true
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
>> For additional commands, e-mail: users-help@glassfish.dev.java.net
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
> For additional commands, e-mail: users-help@glassfish.dev.java.net
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
For additional commands, e-mail: users-help@glassfish.dev.java.net

Jerome Dochez

On Apr 9, 2009, at 9:15 PM, Sahoo wrote:

> Jerome Dochez wrote:
>>
>> On Apr 9, 2009, at 1:07 PM, Sahoo wrote:
>>
>>> What exact command are you using to deploy? I can provide you an
>>> alternative way to deploy OSGi bundles in GFv3 if you use the
>>> latest nightly build. Just do the following:
>>>
>>> copy this attached cfg file to glassfish/modules dir and then
>>> copy your OSGi bundles to domains/domain1/autodeploy-modules dir.
>> yeah but it is not a managed operation, meaning you cannot
>> "undeploy" them by removing them without again having to go to the
>> directory structure.
> That's the whole idea of using fileinstall to work as a management
> agent. autodeploy-modules works like autodeploy dir. You drop a
> bundle, it gets deployed; you remove the bundle and it gets
> undeployed.

and we have autodeploy-modules working today ?

In any case, I am not arguing against it, more choices, the better. I
still think we need to have it through a normal administration
command...

>
> Thanks,
> Sahoo
>>
>> jerome
>>
>>>
>>> Thanks,
>>> Sahoo
>>>
>>> Annies wrote:
>>>>
>>>> When I deploy a bundle, with --type osgi, it is started and
>>>> immediately restarted, why?
>>>>
>>>> [#|2009-04-09T09:46:06.609-0700|INFO|glassfish|
>>>> org.jvnet.hk2.osgiadapter|
>>>> _ThreadID=20;_ThreadName=Thread-1;org.glassfish.openesb.simple-
>>>> jndi [318];|Started bundle org.glassfish.openesb.simple-jndi
>>>> [318]|#]
>>>>
>>>> [#|2009-04-09T09:46:06.611-0700|INFO|glassfish|
>>>> org.jvnet.hk2.osgiadapter|
>>>> _ThreadID=20;_ThreadName=Thread-1;org.glassfish.openesb.simple-
>>>> jndi [318];|Stopped bundle = org.glassfish.openesb.simple-jndi
>>>> [318]|#]
>>>>
>>>> [#|2009-04-09T09:46:06.612-0700|INFO|glassfish|
>>>> org.jvnet.hk2.osgiadapter|
>>>> _ThreadID=20;_ThreadName=Thread-1;org.glassfish.openesb.simple-
>>>> jndi [318];|Started bundle org.glassfish.openesb.simple-jndi
>>>> [318]|#]
>>>>
>>>> [#|2009-04-09T09:46:06.629-0700|INFO|glassfish|
>>>> javax.enterprise.system.tools.admin.org.glassfish.server|
>>>> _ThreadID=20;_ThreadName=Thread-1;|Deployment of simple-jndi done
>>>> is 82 ms|#]
>>>>
>>>>
>>>> Thanks
>>>> Annies
>>>>
>>>>
>>>>
>>> #
>>> # Copyright 2009 Sun Microsystems, Inc. All rights reserved.
>>> # Use is subject to license terms.
>>> #
>>>
>>> # This configuration file is used by org.apache.felix.fileinstall
>>> bundle.
>>> # Author: Sahoo@Sun.COM
>>>
>>> # Directory being watched by fileinstall.
>>> felix.fileinstall.dir=${com.sun.aas.instanceRoot}/autodeploy-
>>> modules/
>>> # Time period fileinstaller thread in ms.
>>> felix.fileinstall.poll=5000
>>> # debug level
>>> felix.fileinstall.debug=1
>>> # should new bundles be started or installed only? true => start,
>>> false => only install
>>> felix.fileinstall.bundles.new.start=true
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
>>> For additional commands, e-mail: users-help@glassfish.dev.java.net
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
>> For additional commands, e-mail: users-help@glassfish.dev.java.net
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
> For additional commands, e-mail: users-help@glassfish.dev.java.net
>

[att1.html]

Sahoo

Jerome Dochez wrote:
>
> On Apr 9, 2009, at 9:15 PM, Sahoo wrote:
>
>> Jerome Dochez wrote:
>>>
>>> On Apr 9, 2009, at 1:07 PM, Sahoo wrote:
>>>
>>>> What exact command are you using to deploy? I can provide you an
>>>> alternative way to deploy OSGi bundles in GFv3 if you use the
>>>> latest nightly build. Just do the following:
>>>>
>>>> copy this attached cfg file to glassfish/modules dir and then
>>>> copy your OSGi bundles to domains/domain1/autodeploy-modules dir.
>>> yeah but it is not a managed operation, meaning you cannot
>>> "undeploy" them by removing them without again having to go to the
>>> directory structure.
>> That's the whole idea of using fileinstall to work as a management
>> agent. autodeploy-modules works like autodeploy dir. You drop a
>> bundle, it gets deployed; you remove the bundle and it gets undeployed.
>
> and we have autodeploy-modules working today ?
User can configure it by adding a cfg file in modules dir.
>
> In any case, I am not arguing against it, more choices, the better. I
> still think we need to have it through a normal administration command...
Yes, I agree.

Thanks,
Sahoo

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
For additional commands, e-mail: users-help@glassfish.dev.java.net

Annies

Sahoo,

I filed an issue - https://glassfish.dev.java.net/issues/show_bug.cgi?id=8126

I chose deployment as the subcomponent. Please feel free to change that as needed.

Thanks
Annies

________________________________
From: Annies
To: users@glassfish.dev.java.net
Sent: Tuesday, April 21, 2009 12:14:31 PM
Subject: Re: deployment type osgi

Yes. Looks like a bug.
When the config file and modules are present before the server is started everything works as expected.
But if the modules are installed by File Install when the domain is running the services are not picked up.
This will be a problem if we want to use this in an update center module. I will file an issue.

Thanks
Annies

________________________________
From: Sahoo
To: users@glassfish.dev.java.net
Sent: Tuesday, April 21, 2009 11:18:11 AM
Subject: Re: deployment type osgi

Annies wrote:
> Thanks Sahoo and Jerome.
>
> Apache Felix File Install Service works nicely. But the HK2 services in those modules are not discovered by V3.
> I had to restart the server to make V3 core get the services. Is this something that could be fixed?
Seems like a bug to me. It should be working.

Thanks,
Sahoo

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
For additional commands, e-mail: users-help@glassfish.dev.java.net

[att1.html]

Annies

Thanks Sahoo and Jerome.

Apache Felix File Install Service works nicely. But the HK2 services in those modules are not discovered by V3.
I had to restart the server to make V3 core get the services. Is this something that could be fixed?
If this works fine, I am planning to create an update center module that could setup our container the same way.

Here is my setup:

1)I am using b44, latest-glassfish.zip from http://download.java.net/glassfish/v3/nightly/latest-glassfish.zip
2)I am creating a new instance of FileInstall by copying org.apache.felix.fileinstall-fuji.cfg (contents below).
3)The modules in installRoot/fuji get installed and started fine.
4)One of those modules implements HK2 container services.
5)When I deploy an application I get

$ ./asadmin deploy ~/packages/sun-wsdl-library.jar
remote failure: There is no installed container capable of handling this application com.sun.enterprise.deploy.shared.FileArchive@108227d5
Command deploy failed.

6)I restart the domain and do the same deployment

$ ./asadmin deploy ~/packages/sun-wsdl-library.jar
Command deploy executed successfully.

$ cat ../modules/org.apache.felix.fileinstall-fuji.cfg
felix.fileinstall.dir=${com.sun.aas.installRoot}/fuji
felix.fileinstall.poll=5000
felix.fileinstall.debug=1
felix.fileinstall.bundles.new.start=true

Thanks
Annies

________________________________
From: Annies
To: users@glassfish.dev.java.net
Sent: Thursday, April 9, 2009 2:17:55 PM
Subject: Re: deployment type osgi

I am using "asadmin deploy --type osgi simple-jndi.jar".

But the Felix File Install feature looks cool. If a bundle is installed this way, will this addition percolate to the HK2 Module Resigtry?

Thanks
Annies

________________________________
From: Sahoo
To: users@glassfish.dev.java.net
Sent: Thursday, April 9, 2009 1:07:18 PM
Subject: Re: deployment type osgi

What exact command are you using to deploy? I can provide you an alternative way to deploy OSGi bundles in GFv3 if you use the latest nightly build. Just do the following:

copy this attached cfg file to glassfish/modules dir and then
copy your OSGi bundles to domains/domain1/autodeploy-modules dir.

Thanks,
Sahoo

Annies wrote:
>
> When I deploy a bundle, with --type osgi, it is started and immediately restarted, why?
>
> [#|2009-04-09T09:46:06.609-0700|INFO|glassfish|org.jvnet.hk2.osgiadapter|_ThreadID=20;_ThreadName=Thread-1;org.glassfish.openesb.simple-jndi [318];|Started bundle org.glassfish.openesb.simple-jndi [318]|#]
>
> [#|2009-04-09T09:46:06.611-0700|INFO|glassfish|org.jvnet.hk2.osgiadapter|_ThreadID=20;_ThreadName=Thread-1;org.glassfish.openesb.simple-jndi [318];|Stopped bundle = org.glassfish.openesb.simple-jndi [318]|#]
>
> [#|2009-04-09T09:46:06.612-0700|INFO|glassfish|org.jvnet.hk2.osgiadapter|_ThreadID=20;_ThreadName=Thread-1;org.glassfish.openesb.simple-jndi [318];|Started bundle org.glassfish.openesb.simple-jndi [318]|#]
>
> [#|2009-04-09T09:46:06.629-0700|INFO|glassfish|javax.enterprise.system.tools.admin.org.glassfish.server|_ThreadID=20;_ThreadName=Thread-1;|Deployment of simple-jndi done is 82 ms|#]
>
>
> Thanks
> Annies
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
For additional commands, e-mail: users-help@glassfish.dev.java.net

[att1.html]

Sahoo

Annies wrote:
> Thanks Sahoo and Jerome.
>
> Apache Felix File Install Service works nicely. But the HK2 services
> in those modules are not discovered by V3.
> I had to restart the server to make V3 core get the services. Is this
> something that could be fixed?
Seems like a bug to me. It should be working.

Thanks,
Sahoo

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
For additional commands, e-mail: users-help@glassfish.dev.java.net

Annies

Yes. Looks like a bug.
When the config file and modules are present before the server is started everything works as expected.
But if the modules are installed by File Install when the domain is running the services are not picked up.
This will be a problem if we want to use this in an update center module. I will file an issue.

Thanks
Annies

________________________________
From: Sahoo
To: users@glassfish.dev.java.net
Sent: Tuesday, April 21, 2009 11:18:11 AM
Subject: Re: deployment type osgi

Annies wrote:
> Thanks Sahoo and Jerome.
>
> Apache Felix File Install Service works nicely. But the HK2 services in those modules are not discovered by V3.
> I had to restart the server to make V3 core get the services. Is this something that could be fixed?
Seems like a bug to me. It should be working.

Thanks,
Sahoo

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
For additional commands, e-mail: users-help@glassfish.dev.java.net

[att1.html]

Sahoo

attach a test case that can be used to reproduce the issue.

Annies wrote:
> Yes. Looks like a bug.
> When the config file and modules are present before the server is
> started everything works as expected.
> But if the modules are installed by File Install when the domain is
> running the services are not picked up.
> This will be a problem if we want to use this in an update center
> module. I will file an issue.
>
> Thanks
> Annies
>
>
>
> ------------------------------------------------------------------------
> *From:* Sahoo
> *To:* users@glassfish.dev.java.net
> *Sent:* Tuesday, April 21, 2009 11:18:11 AM
> *Subject:* Re: deployment type osgi
>
>
>
> Annies wrote:
> > Thanks Sahoo and Jerome.
> >
> > Apache Felix File Install Service works nicely. But the HK2 services
> in those modules are not discovered by V3.
> > I had to restart the server to make V3 core get the services. Is
> this something that could be fixed?
> Seems like a bug to me. It should be working.
>
> Thanks,
> Sahoo
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
>
> For additional commands, e-mail: users-help@glassfish.dev.java.net
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
For additional commands, e-mail: users-help@glassfish.dev.java.net

Jerome Dochez

it's a side effect of the current implementation, you can ignore it
for now if that's not too much trouble...

jerome

On Apr 9, 2009, at 12:57 PM, Annies wrote:

>
> When I deploy a bundle, with --type osgi, it is started and
> immediately restarted, why?
>
> [#|2009-04-09T09:46:06.609-0700|INFO|glassfish|
> org.jvnet.hk2.osgiadapter|
> _ThreadID=20;_ThreadName=Thread-1;org.glassfish.openesb.simple-jndi
> [318];|Started bundle org.glassfish.openesb.simple-jndi [318]|#]
>
> [#|2009-04-09T09:46:06.611-0700|INFO|glassfish|
> org.jvnet.hk2.osgiadapter|
> _ThreadID=20;_ThreadName=Thread-1;org.glassfish.openesb.simple-jndi
> [318];|Stopped bundle = org.glassfish.openesb.simple-jndi [318]|#]
>
> [#|2009-04-09T09:46:06.612-0700|INFO|glassfish|
> org.jvnet.hk2.osgiadapter|
> _ThreadID=20;_ThreadName=Thread-1;org.glassfish.openesb.simple-jndi
> [318];|Started bundle org.glassfish.openesb.simple-jndi [318]|#]
>
> [#|2009-04-09T09:46:06.629-0700|INFO|glassfish|
> javax.enterprise.system.tools.admin.org.glassfish.server|
> _ThreadID=20;_ThreadName=Thread-1;|Deployment of simple-jndi done is
> 82 ms|#]
>
>
> Thanks
> Annies
>
>
>
>

[att1.html]

Annies

Okay. Thanks. I will create an issue to track this.

-Annies

________________________________
From: Jerome Dochez
To: users@glassfish.dev.java.net
Sent: Thursday, April 9, 2009 2:38:08 PM
Subject: Re: deployment type osgi

it's a side effect of the current implementation, you can ignore it for now if that's not too much trouble...

jerome

On Apr 9, 2009, at 12:57 PM, Annies wrote:

When I deploy a bundle, with --type osgi, it is started and immediately restarted, why?

[#|2009-04-09T09:46:06.609-0700|INFO|glassfish|org.jvnet.hk2.osgiadapter|_ThreadID=20;_ThreadName=Thread-1;org.glassfish.openesb.simple-jndi [318];|Started bundle org.glassfish.openesb.simple-jndi [318]|#]

[#|2009-04-09T09:46:06.611-0700|INFO|glassfish|org.jvnet.hk2.osgiadapter|_ThreadID=20;_ThreadName=Thread-1;org.glassfish.openesb.simple-jndi [318];|Stopped bundle = org.glassfish.openesb.simple-jndi [318]|#]

[#|2009-04-09T09:46:06.612-0700|INFO|glassfish|org.jvnet.hk2.osgiadapter|_ThreadID=20;_ThreadName=Thread-1;org.glassfish.openesb.simple-jndi [318];|Started bundle org.glassfish.openesb.simple-jndi [318]|#]

[#|2009-04-09T09:46:06.629-0700|INFO|glassfish|javax.enterprise.system.tools.admin.org.glassfish.server|_ThreadID=20;_ThreadName=Thread-1;|Deployment of simple-jndi done is 82 ms|#]

Thanks
Annies

[att1.html]

Sahoo

What exact command are you using to deploy? I can provide you an
alternative way to deploy OSGi bundles in GFv3 if you use the latest
nightly build. Just do the following:

copy this attached cfg file to glassfish/modules dir and then
copy your OSGi bundles to domains/domain1/autodeploy-modules dir.

Thanks,
Sahoo

Annies wrote:
>
> When I deploy a bundle, with --type osgi, it is started and
> immediately restarted, why?
>
> [#|2009-04-09T09:46:06.609-0700|INFO|glassfish|org.jvnet.hk2.osgiadapter|_ThreadID=20;_ThreadName=Thread-1;org.glassfish.openesb.simple-jndi
> [318];|Started bundle org.glassfish.openesb.simple-jndi [318]|#]
>
> [#|2009-04-09T09:46:06.611-0700|INFO|glassfish|org.jvnet.hk2.osgiadapter|_ThreadID=20;_ThreadName=Thread-1;org.glassfish.openesb.simple-jndi
> [318];|Stopped bundle = org.glassfish.openesb.simple-jndi [318]|#]
>
> [#|2009-04-09T09:46:06.612-0700|INFO|glassfish|org.jvnet.hk2.osgiadapter|_ThreadID=20;_ThreadName=Thread-1;org.glassfish.openesb.simple-jndi
> [318];|Started bundle org.glassfish.openesb.simple-jndi [318]|#]
>
> [#|2009-04-09T09:46:06.629-0700|INFO|glassfish|javax.enterprise.system.tools.admin.org.glassfish.server|_ThreadID=20;_ThreadName=Thread-1;|Deployment
> of simple-jndi done is 82 ms|#]
>
>
> Thanks
> Annies
>
>
>
#
# Copyright 2009 Sun Microsystems, Inc. All rights reserved.
# Use is subject to license terms.
#

# This configuration file is used by org.apache.felix.fileinstall bundle.
# Author: Sahoo@Sun.COM

# Directory being watched by fileinstall.
felix.fileinstall.dir=${com.sun.aas.instanceRoot}/autodeploy-modules/
# Time period fileinstaller thread in ms.
felix.fileinstall.poll=5000
# debug level
felix.fileinstall.debug=1
# should new bundles be started or installed only? true => start, false => only install
felix.fileinstall.bundles.new.start=true

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
For additional commands, e-mail: users-help@glassfish.dev.java.net

Annies

I am using "asadmin deploy --type osgi simple-jndi.jar".

But the Felix File Install feature looks cool. If a bundle is installed this way, will this addition percolate to the HK2 Module Resigtry?

Thanks
Annies

________________________________
From: Sahoo
To: users@glassfish.dev.java.net
Sent: Thursday, April 9, 2009 1:07:18 PM
Subject: Re: deployment type osgi

What exact command are you using to deploy? I can provide you an alternative way to deploy OSGi bundles in GFv3 if you use the latest nightly build. Just do the following:

copy this attached cfg file to glassfish/modules dir and then
copy your OSGi bundles to domains/domain1/autodeploy-modules dir.

Thanks,
Sahoo

Annies wrote:
>
> When I deploy a bundle, with --type osgi, it is started and immediately restarted, why?
>
> [#|2009-04-09T09:46:06.609-0700|INFO|glassfish|org.jvnet.hk2.osgiadapter|_ThreadID=20;_ThreadName=Thread-1;org.glassfish.openesb.simple-jndi [318];|Started bundle org.glassfish.openesb.simple-jndi [318]|#]
>
> [#|2009-04-09T09:46:06.611-0700|INFO|glassfish|org.jvnet.hk2.osgiadapter|_ThreadID=20;_ThreadName=Thread-1;org.glassfish.openesb.simple-jndi [318];|Stopped bundle = org.glassfish.openesb.simple-jndi [318]|#]
>
> [#|2009-04-09T09:46:06.612-0700|INFO|glassfish|org.jvnet.hk2.osgiadapter|_ThreadID=20;_ThreadName=Thread-1;org.glassfish.openesb.simple-jndi [318];|Started bundle org.glassfish.openesb.simple-jndi [318]|#]
>
> [#|2009-04-09T09:46:06.629-0700|INFO|glassfish|javax.enterprise.system.tools.admin.org.glassfish.server|_ThreadID=20;_ThreadName=Thread-1;|Deployment of simple-jndi done is 82 ms|#]
>
>
> Thanks
> Annies
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
For additional commands, e-mail: users-help@glassfish.dev.java.net

[att1.html]

Sahoo

Yes, it will. The HK2 extender will take care of reading the HK2
metadata from an OSGi bundle irrespective of how it is installed.

Sahoo

Annies wrote:
> I am using "asadmin deploy --type osgi simple-jndi.jar".
>
> But the Felix File Install feature looks cool. If a bundle is
> installed this way, will this addition percolate to the HK2 Module
> Resigtry?
>
>
> Thanks
> Annies
>
>
> ------------------------------------------------------------------------
> *From:* Sahoo
> *To:* users@glassfish.dev.java.net
> *Sent:* Thursday, April 9, 2009 1:07:18 PM
> *Subject:* Re: deployment type osgi
>
> What exact command are you using to deploy? I can provide you an
> alternative way to deploy OSGi bundles in GFv3 if you use the latest
> nightly build. Just do the following:
>
> copy this attached cfg file to glassfish/modules dir and then
> copy your OSGi bundles to domains/domain1/autodeploy-modules dir.
>
> Thanks,
> Sahoo
>
> Annies wrote:
> >
> > When I deploy a bundle, with --type osgi, it is started and
> immediately restarted, why?
> >
> >
> [#|2009-04-09T09:46:06.609-0700|INFO|glassfish|org.jvnet.hk2.osgiadapter|_ThreadID=20;_ThreadName=Thread-1;org.glassfish.openesb.simple-jndi
> [318];|Started bundle org.glassfish.openesb.simple-jndi [318]|#]
> >
> >
> [#|2009-04-09T09:46:06.611-0700|INFO|glassfish|org.jvnet.hk2.osgiadapter|_ThreadID=20;_ThreadName=Thread-1;org.glassfish.openesb.simple-jndi
> [318];|Stopped bundle = org.glassfish.openesb.simple-jndi [318]|#]
> >
> >
> [#|2009-04-09T09:46:06.612-0700|INFO|glassfish|org.jvnet.hk2.osgiadapter|_ThreadID=20;_ThreadName=Thread-1;org.glassfish.openesb.simple-jndi
> [318];|Started bundle org.glassfish.openesb.simple-jndi [318]|#]
> >
> >
> [#|2009-04-09T09:46:06.629-0700|INFO|glassfish|javax.enterprise.system.tools.admin.org.glassfish.server|_ThreadID=20;_ThreadName=Thread-1;|Deployment
> of simple-jndi done is 82 ms|#]
> >
> >
> > Thanks
> > Annies
> >
> >
> >
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
>
> For additional commands, e-mail: users-help@glassfish.dev.java.net
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
For additional commands, e-mail: users-help@glassfish.dev.java.net