|
|
|
| Re: container cannot be null exception [message #618614 is a reply to message #618613] |
Tue, 22 May 2007 06:23   |
 abhishek misra
Messages: 26
Registered: July 2009 |
Junior Member |
|
|
ServiceTracker.getService() line: 683
Activator.getDebugOptions() line: 118
Trace.shouldTrace0(String) line: 141
Trace.shouldTrace(String) line: 133
Trace.shouldTrace(String, String) line: 161
Trace.entering(String, String, Class, String, Object[]) line: 471
ContainerFactory.createContainer(ContainerTypeDescription, Object[])
line: 220
ContainerFactory.createContainer(String) line: 261
This is what the trace looks like. I will probably attach the source and
see if i can use that and debug.
Thanks,
abhi
abby wrote:
> :). I changed it still the same exception.
>
> Thanks,
> abby
>
> Scott Lewis wrote:
>> Hi Abby,
>>
>> abby wrote:
>>> I created a new action connect which spawns a new job and have a
>>> following in the run.
>>>
>>> protected IStatus run(IProgressMonitor monitor) {
>>> try {
>>> container =
>>> ContainerFactory.getDefault().createContainer("ecf.generic.channel ");
>>
>> I think you probably mean "ecf.generic.client"
>>
>> Scott
>>
|
|
|
| Re: container cannot be null exception [message #618615 is a reply to message #618614] |
Tue, 22 May 2007 14:26 |
Scott Lewis
Messages: 1038
Registered: July 2009 |
Senior Member |
|
|
Hi Abby,
Thanks for attaching the stack trace, but this one is not complete.
Could you run again and see if you get the same thing and attach the
entire stack trace? Thanks.
Did you install all of ECF plugins? Reason I ask...the classes for
"ecf.generic.client" are actually in plugin org.eclipse.ecf.provider and
if that plugin was not installed it would result in the situation you
are seeing. This seems to me like the most likely problem at the moment.
Thanks,
Scott
abby wrote:
> ServiceTracker.getService() line: 683
> Activator.getDebugOptions() line: 118
> Trace.shouldTrace0(String) line: 141
> Trace.shouldTrace(String) line: 133
> Trace.shouldTrace(String, String) line: 161
> Trace.entering(String, String, Class, String, Object[]) line: 471
> ContainerFactory.createContainer(ContainerTypeDescription, Object[])
> line: 220
> ContainerFactory.createContainer(String) line: 261
>
>
> This is what the trace looks like. I will probably attach the source and
> see if i can use that and debug.
>
> Thanks,
> abhi
>
> abby wrote:
>> :). I changed it still the same exception.
>>
>> Thanks,
>> abby
>>
>> Scott Lewis wrote:
>>> Hi Abby,
>>>
>>> abby wrote:
>>>> I created a new action connect which spawns a new job and have a
>>>> following in the run.
>>>>
>>>> protected IStatus run(IProgressMonitor monitor) {
>>>> try {
>>>> container =
>>>> ContainerFactory.getDefault().createContainer("ecf.generic.channel ");
>>>
>>> I think you probably mean "ecf.generic.client"
>>>
>>> Scott
>>>
|
|
|
| Re: container cannot be null exception [message #618676 is a reply to message #618615] |
Tue, 22 May 2007 20:28 |
abhishek misra
Messages: 26
Registered: July 2009 |
Junior Member |
|
|
Yup i think that was it. That plugin was not included in my dependencies
list. I had the core included and was not aware that provider needs to
be separately included. Also, i had selected the option to include all
dependencies and this was not included.
Thanks,
abhi
Scott Lewis wrote:
> Hi Abby,
>
> Thanks for attaching the stack trace, but this one is not complete.
> Could you run again and see if you get the same thing and attach the
> entire stack trace? Thanks.
>
> Did you install all of ECF plugins? Reason I ask...the classes for
> "ecf.generic.client" are actually in plugin org.eclipse.ecf.provider and
> if that plugin was not installed it would result in the situation you
> are seeing. This seems to me like the most likely problem at the moment.
>
> Thanks,
>
> Scott
>
>
> abby wrote:
>> ServiceTracker.getService() line: 683 Activator.getDebugOptions()
>> line: 118 Trace.shouldTrace0(String) line: 141
>> Trace.shouldTrace(String) line: 133 Trace.shouldTrace(String,
>> String) line: 161 Trace.entering(String, String, Class, String,
>> Object[]) line: 471
>> ContainerFactory.createContainer(ContainerTypeDescription, Object[])
>> line: 220 ContainerFactory.createContainer(String) line: 261
>>
>> This is what the trace looks like. I will probably attach the source
>> and see if i can use that and debug.
>>
>> Thanks,
>> abhi
>>
>> abby wrote:
>>> :). I changed it still the same exception.
>>>
>>> Thanks,
>>> abby
>>>
>>> Scott Lewis wrote:
>>>> Hi Abby,
>>>>
>>>> abby wrote:
>>>>> I created a new action connect which spawns a new job and have a
>>>>> following in the run.
>>>>>
>>>>> protected IStatus run(IProgressMonitor monitor) {
>>>>> try {
>>>>> container =
>>>>> ContainerFactory.getDefault().createContainer("ecf.generic.channel ");
>>>>
>>>> I think you probably mean "ecf.generic.client"
>>>>
>>>> Scott
>>>>
|
|
|
| Re: container cannot be null exception [message #618677 is a reply to message #618676] |
Wed, 23 May 2007 00:20 |
Scott Lewis
Messages: 1038
Registered: July 2009 |
Senior Member |
|
|
Hi Abby,
The ECF providers are dynamically loaded, and so won't appear in the
static dependencies list. The convention for provider plugin names (for
ECF team created providers) is:
org.eclipse.ecf.provider*
e.g.
org.eclipse.ecf.provider
org.eclipse.ecf.provider.xmpp
org.eclipse.ecf.provider.irc
etc.
Scott
abby wrote:
> Yup i think that was it. That plugin was not included in my dependencies
> list. I had the core included and was not aware that provider needs to
> be separately included. Also, i had selected the option to include all
> dependencies and this was not included.
>
> Thanks,
> abhi
>
> Scott Lewis wrote:
>> Hi Abby,
>>
>> Thanks for attaching the stack trace, but this one is not complete.
>> Could you run again and see if you get the same thing and attach the
>> entire stack trace? Thanks.
>>
>> Did you install all of ECF plugins? Reason I ask...the classes for
>> "ecf.generic.client" are actually in plugin org.eclipse.ecf.provider
>> and if that plugin was not installed it would result in the situation
>> you are seeing. This seems to me like the most likely problem at the
>> moment.
>>
>> Thanks,
>>
>> Scott
>>
>>
>> abby wrote:
>>> ServiceTracker.getService() line: 683 Activator.getDebugOptions()
>>> line: 118 Trace.shouldTrace0(String) line: 141
>>> Trace.shouldTrace(String) line: 133 Trace.shouldTrace(String,
>>> String) line: 161 Trace.entering(String, String, Class, String,
>>> Object[]) line: 471
>>> ContainerFactory.createContainer(ContainerTypeDescription, Object[])
>>> line: 220 ContainerFactory.createContainer(String) line: 261
>>> This is what the trace looks like. I will probably attach the source
>>> and see if i can use that and debug.
>>>
>>> Thanks,
>>> abhi
>>>
>>> abby wrote:
>>>> :). I changed it still the same exception.
>>>>
>>>> Thanks,
>>>> abby
>>>>
>>>> Scott Lewis wrote:
>>>>> Hi Abby,
>>>>>
>>>>> abby wrote:
>>>>>> I created a new action connect which spawns a new job and have a
>>>>>> following in the run.
>>>>>>
>>>>>> protected IStatus run(IProgressMonitor monitor) {
>>>>>> try {
>>>>>> container =
>>>>>> ContainerFactory.getDefault().createContainer("ecf.generic.channel ");
>>>>>
>>>>> I think you probably mean "ecf.generic.client"
>>>>>
>>>>> Scott
>>>>>
|
|
|
Powered by
FUDForum. Page generated in 5.04006 seconds
] 
Search
Help
Register
Login
Home
