Re: SCR : Unsatisfied ComponentFactory

2017-04-17 Thread Dave Smith
I have read over the spec and I would suggest it is unclear if we should be returning the factory instance or the instances that the factory created. Either way knowing why a factory is not started is useful and should be somehow worked into the spec. Right now I had to hack around the limitation

Re: SCR : Unsatisfied ComponentFactory

2017-03-31 Thread David Jencks
> On Mar 31, 2017, at 2:20 PM, Dave Smith wrote: > > The model controls the UI. When a service becomes unavailable the > deactivate is called which then tells the UI that is is not available. In > reality this never happens , so it is not an issue. it might be here :-)

Re: SCR : Unsatisfied ComponentFactory

2017-03-31 Thread David Jencks
> On Mar 31, 2017, at 1:02 PM, David Jencks wrote: > >> >> On Mar 31, 2017, at 11:03 AM, Dave Smith > > wrote: >> >> See below >> >> On Fri, Mar 31, 2017 at 1:51 PM, David Jencks >

Re: SCR : Unsatisfied ComponentFactory

2017-03-31 Thread David Jencks
> On Mar 31, 2017, at 11:03 AM, Dave Smith wrote: > > See below > > On Fri, Mar 31, 2017 at 1:51 PM, David Jencks > > wrote: > >> I think scr:info shows you instances of the factory component you’ve >>

Re: SCR : Unsatisfied ComponentFactory

2017-03-31 Thread Dave Smith
See below On Fri, Mar 31, 2017 at 1:51 PM, David Jencks wrote: > I think scr:info shows you instances of the factory component you’ve > created with newInstance on the ComponentFactory service. If you list > services do you see the ComponentFactory service registered

Re: SCR : Unsatisfied ComponentFactory

2017-03-31 Thread Dave Smith
No, It still has to resolve to know if it is available to activate and then register a facade. Otherwise non DS services that might use it would not see it. Dave On Fri, Mar 31, 2017 at 11:41 AM, Raymond Auge wrote: > On Fri, Mar 31, 2017 at 11:22 AM, Dave Smith

Re: SCR : Unsatisfied ComponentFactory

2017-03-31 Thread Raymond Auge
On Fri, Mar 31, 2017 at 11:22 AM, Dave Smith wrote: > It is ugly (long story) > > scr:info com.candata.b3.client.bbx.TRACK01 > *** Bundle: com.candata.b3.client.jnj (7) > Component Description: > Name: com.candata.b3.client.bbx.TRACK01 > Implementation Class:

Re: SCR : Unsatisfied ComponentFactory

2017-03-31 Thread Dave Smith
It is ugly (long story) scr:info com.candata.b3.client.bbx.TRACK01 *** Bundle: com.candata.b3.client.jnj (7) Component Description: Name: com.candata.b3.client.bbx.TRACK01 Implementation Class: com.candata.b3.client.bbx.TRACK01 Default State: enabled Activation: delayed Configuration

Re: SCR : Unsatisfied ComponentFactory

2017-03-31 Thread Raymond Auge
On Fri, Mar 31, 2017 at 11:13 AM, Dave Smith wrote: > com.candata.b3.client.bbx.TRACK01 > please do scr:info com.candata.b3.client.bbx.TRACK01 -- *Raymond Augé* (@rotty3000) Senior Software Architect *Liferay, Inc.*

Re: SCR : Unsatisfied ComponentFactory

2017-03-31 Thread Dave Smith
scr:list gives .. [ 7] com.candata.b3.client.bbx.TRACK01 enabled Where 7 is the bundle id. scr:info com.candata.b3.client.bbx.TRACK01 just lists the services it uses but not if they are resolved. There is no service id assigned to it Dave On Fri, Mar 31, 2017 at 11:06 AM, Raymond Auge

Re: SCR : Unsatisfied ComponentFactory

2017-03-31 Thread Raymond Auge
It might help to show the dump of the scr:info command here so we can try to figure out the issue. Sincerely, - Ray On Fri, Mar 31, 2017 at 10:41 AM, Dave Smith wrote: > We have some ComponentFactory's that are not starting. However in the GOGO > shell console and the