Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [cosmos-dev] problem withusingautowireandComposableManagedCapabilitySet together withnew annotation

Never mind – I’m able to reproduce this now. Hopefully I’ll have something for you shortly.

 

-----Original Message-----
From: cosmos-dev-bounces@xxxxxxxxxxx [mailto:cosmos-dev-bounces@xxxxxxxxxxx] On Behalf Of Hawkins, Joel
Sent:
Friday, February 01, 2008 12:46 PM
To: Cosmos Dev
Subject: RE: [cosmos-dev] problem withusingautowireandComposableManagedCapabilitySet together withnew annotation

 

Hubert,

 

Can you send me a launch configuration to test with? We should probably check some of these to make life easier for adoptors…

 

Thanks,

Joel

 

-----Original Message-----
From: cosmos-dev-bounces@xxxxxxxxxxx [mailto:cosmos-dev-bounces@xxxxxxxxxxx] On Behalf Of Hubert H Leung
Sent:
Friday, February 01, 2008 11:26 AM
To: Cosmos Dev
Subject: RE: [cosmos-dev] problem with usingautowireandComposableManagedCapabilitySet together with new annotation

 


I found a new clue about the problem, but I don't have a solution yet.  

The program fails at line 193 of org.eclipse.cosmos.me.management.common.util.ManagementProxyFactory.  Here is the stacktrace:
Failed to register data manager with contribution manager.
java.lang.IllegalArgumentException: interface org.eclipse.cosmos.me.management.provisional.wsdm.capabilities.DescriptionCapability is not visible from class loader
        at java.lang.reflect.Proxy.getProxyClass(Proxy.java:353)
        at java.lang.reflect.Proxy.newProxyInstance(Proxy.java:581)
        at org.eclipse.cosmos.me.management.common.util.ManagementProxyFactory.getManagedProxy(ManagementProxyFactory.java:193)
        at org.eclipse.cosmos.me.management.osgi.ContributionManagerImpl.manage(ContributionManagerImpl.java:73)
        at org.eclipse.cosmos.dc.dataManager.impl.AbstractDataManagerActivator.serviceChanged(AbstractDataManagerActivator.java:92)

The DescriptionCapability class is in management.wsdm bundle, which is not a dependency of the management.common bundle, where the code fails.  


Any help would be appreciated.  

Thanks,
_________________________
Hubert Leung
IBM Toronto Lab
hkyleung@xxxxxxxxxx
905-413-3382


Hubert H Leung/Toronto/IBM@IBMCA
Sent by: cosmos-dev-bounces@xxxxxxxxxxx

02/01/2008 10:29 AM

Please respond to
Cosmos Dev <cosmos-dev@xxxxxxxxxxx>

To

Cosmos Dev <cosmos-dev@xxxxxxxxxxx>

cc

 

Subject

RE: [cosmos-dev] problem with using        autowireandComposableManagedCapabilitySet together with new annotation

 

 

 





Thanks Bill for the suggestion.  I checked my environment, but I only have the new annotations in my workspace now.


If you run the latest code from CVS, you will be able to invoke APIs of the data managers, but the data managers can't register with the broker.  


Joel, I attached a project set file for getting the minimum number of required projects into your workspace.  Only the example MDR is included.  




Thanks,
_________________________
Hubert Leung
IBM Toronto Lab
hkyleung@xxxxxxxxxx
905-413-3382

"Muldoon, William H" <William.Muldoon@xxxxxx>
Sent by: cosmos-dev-bounces@xxxxxxxxxxx

02/01/2008 09:31 AM

Please respond to
Cosmos Dev <cosmos-dev@xxxxxxxxxxx>

To

"Cosmos Dev" <cosmos-dev@xxxxxxxxxxx>

cc

 

Subject

RE: [cosmos-dev] problem with using        autowireandComposableManagedCapabilitySet together with new annotation

 

 

 





Hubert

 
           FYI: I ran into the same NullPointerException on the exact same line yesterday (along with other problems). The problems were related to the fact that I was running with both the old and new annotations in my test environment. When I removed the old annotations from my environment, all the problems disappeared. So FWIW, double check that your environment has not mixed the old annotations with the new annotations.

 
Regards

Bill

 

 




From:
cosmos-dev-bounces@xxxxxxxxxxx [mailto:cosmos-dev-bounces@xxxxxxxxxxx] On Behalf Of Hawkins, Joel
Sent:
Friday, February 01, 2008 8:48 AM
To:
Cosmos Dev
Subject:
RE: [cosmos-dev] problem with using autowireandComposableManagedCapabilitySet together with new annotation

 
Hubert,

 
I’ve created test cases for this scenario, and they run fine, so apparently something else is going on. I will try this with the actual class instead. Is everything I need in CVS at this point, or can you supply a patch that I can use to reproduce this?

 
I’ll check my test cases in as well so that you can see them once I get out of my morning set of meetings.
 
Thanks,

Joel

 
-----Original Message-----
From:
cosmos-dev-bounces@xxxxxxxxxxx [mailto:cosmos-dev-bounces@xxxxxxxxxxx] On Behalf Of Hawkins, Joel
Sent:
Thursday, January 31, 2008 5:17 PM
To:
Cosmos Dev
Subject:
RE: [cosmos-dev] problem with using autowire andComposableManagedCapabilitySet together with new annotation

 
Hi Hubert,

 
Yes, I’ll take a look at it. I don’t think I’ve got a testcase for the combination of composition and autowire… apparent oversight on my part.

 
Thanks,

Joel

 

The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it
.

From:
cosmos-dev-bounces@xxxxxxxxxxx [mailto:cosmos-dev-bounces@xxxxxxxxxxx] On Behalf Of Hubert H Leung
Sent:
Thursday, January 31, 2008 5:07 PM
To:
cosmos-dev@xxxxxxxxxxx
Subject:
[cosmos-dev] problem with using autowire and ComposableManagedCapabilitySet together with new annotation

 

Hi Joel,


I'm having a problem withe the new annotation code.  I added the description capability by jusing the new composability feature like this:

@ComposableManagedCapabilitySet
(set={DescriptionImpl.class})
public
abstract class AbstractDataManager implements IDataManager {

After adding the annotation above, the variable that's annotated with
@ManagedFrameworkAutowire(name="WSDM") becomes null.  

@ManagedFrameworkAutowire
(name="WSDM")
  private Binding wsdmBinding;


  public void setWsdmBinding(Binding wsdmBinding){

          this.wsdmBinding = wsdmBinding;

  }


      Object resourceObject = wsdmBinding.getBindingForObject(this);
 <-- NPE here, wsdmBinding is null.  

If I remove the
@ComposableManagedCapabilitySet annotation, the wsdmBinding variable gets the WSDMBinding object.  

Can you help me with this problem?  You can see the code in the AbstractDataManager.java file.  


Thanks,
_________________________
Hubert Leung
IBM Toronto Lab
hkyleung@xxxxxxxxxx
905-413-3382

_______________________________________________
cosmos-dev mailing list
cosmos-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cosmos-dev

[attachment "cosmos_dc_i9.psf" deleted by Hubert H Leung/Toronto/IBM] _______________________________________________
cosmos-dev mailing list
cosmos-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cosmos-dev


Back to the top