Skip navigation
Currently Being Moderated

Adobe Drive not connecting to hello world sample launched via Eclipse

Nov 18, 2013 1:38 AM

Tags: #eclipse #sdk #drive #osgi

I'm trying to get the hello world sample running with Drive SDK 5. I got:

 

  • Adobe Drive 5.0.1
  • AdobeDriveSDK-5.0.0.398770.zip
  • latest Java JRE 1.6
  • Eclipes 4.3.1 (Kepler SR 1)
  • Windows 7 64bit

 

I configured the hello world project as described in the getting started guide. I double checked that AD4ServiceManager.exe is not running. After starting the project in Eclipse and waiting about 15 seconds, all bundles are active:

osgi> ss

Framework is launched.

id     State       Bundle
0     ACTIVE      org.eclipse.osgi_3.5.0.v20090520
1     ACTIVE      com.adobe.csi.ncomm_2.0.0.28
2     ACTIVE      com.adobe.drive.core_2.0.0.28
3     ACTIVE      org.eclipse.equinox.cm_1.0.100.v20090520-1800
4     ACTIVE      org.eclipse.equinox.preferences_3.2.300.v20090520-1800
5     ACTIVE      org.eclipse.equinox.app_1.2.0.v20090520-1800
6     ACTIVE      com.adobe.drive.biz.filesystem_2.0.0.28
7     ACTIVE      javax.servlet_2.5.0.v200806031605
8     ACTIVE      org.eclipse.equinox.launcher_1.0.200.v20090520
9     ACTIVE      com.adobe.drive.manager.executor_1.0.0.28
10     ACTIVE      com.adobe.drive.connector.cmis_2.0.0.28
11     ACTIVE      com.adobe.drive.ui_2.0.0.28
                 Fragments=27
12     ACTIVE      org.hsqldb_2.2.9
13     ACTIVE      com.adobe.drive.model.synchronization_2.0.0.28
14     ACTIVE      com.adobe.drive.data.persistence.api_2.0.0.28
15     ACTIVE      org.eclipse.equinox.ds_1.1.0.v20090601
16     ACTIVE      org.eclipse.update.configurator_3.3.0.v20090312
17     ACTIVE      org.hibernate_3.2.5
18     ACTIVE      com.adobe.csi.core_2.0.0.28
19     ACTIVE      com.adobe.drive.connector.service_2.0.0.28
20     ACTIVE      com.adobe.drive.model_2.0.0.28
21     ACTIVE      com.adobe.drive.data.provider_2.0.0.28
22     ACTIVE      com.adobe.csi.auth.keystore_2.0.0.28
23     ACTIVE      com.adobe.drive.connector.api_2.0.0.28
24     ACTIVE      com.adobe.drive.data.persistence.hsqldb_2.0.0.28
25     ACTIVE      com.adobe.drive.data.cache_2.0.0.28
26     ACTIVE      org.apache.commons.codec_1.0.0.28
27     RESOLVED    com.adobe.drive.ui.scripting_2.0.0.28
                 Master=11
28     ACTIVE      org.apache.commons.net_1.4.1
29     ACTIVE      sample.helloworld_2.0.0
30     ACTIVE      com.adobe.csi.bootstrap_2.0.0.28
31     ACTIVE      com.adobe.drive.data.manager_2.0.0.28
32     ACTIVE      org.apache.commons.logging_1.0.4
33     ACTIVE      com.adobe.versioncue.nativecomm_4.0.1.28
34     ACTIVE      com.adobe.drive.biz.versioncue.api_2.0.0.28
35     ACTIVE      org.eclipse.equinox.common_3.5.0.v20090520-1800
36     ACTIVE      com.adobe.csi.pipes_2.0.0
37     ACTIVE      com.adobe.drive.data.model_2.0.0.28
38     ACTIVE      com.adobe.drive.data.persistence_2.0.0.28
39     ACTIVE      com.adobe.drive.processinfo_2.0.0.28
40     ACTIVE      com.adobe.drive.connector.cmis.client_2.0.0.28
41     ACTIVE      com.adobe.drive.ncomm.filesystem_2.0.0.28
42     ACTIVE      org.eclipse.equinox.registry_3.4.100.v20090520-1800
43     ACTIVE      org.apache.commons.httpclient_3.1.0
44     ACTIVE      com.adobe.drive.vcdetector_2.0.0
45     ACTIVE      com.adobe.drive.ncomm.versioncue_2.0.0.28
46     ACTIVE      com.adobe.drive.connector.cqdam_4.0.0.28
47     ACTIVE      com.adobe.csi.core.preferences_2.0.0.28
48     ACTIVE      org.eclipse.equinox.util_1.0.100.v20090520-1800
49     ACTIVE      com.adobe.csi.utils_2.0.0.28
50     ACTIVE      com.adobe.drive.biz.automount_2.0.0.28
51     ACTIVE      com.adobe.csi.core.logging_2.0.0.28
52     ACTIVE      com.adobe.drive.manager.interests_2.0.0.28
53     ACTIVE      org.apache.log4j_1.2.15
54     ACTIVE      com.adobe.drive.ifs_2.0.0.28
55     ACTIVE      com.adobe.drive.core.jobs_2.0.0.28
56     ACTIVE      org.eclipse.osgi.services_3.2.0.v20090520-1800
57     ACTIVE      com.adobe.drive.biz.versioncue_2.0.0.28
58     ACTIVE      com.adobe.csi.auth_2.0.0.28

Also, the output of csstat looks fine:

osgi> csstat
Registered connector factories (schema : reference):
cmis : {org.osgi.service.component.ComponentFactory}={component.factory=com.adobe.drive.connector.handlerfactory, component.name=com.adobe.drive.connector.cmis#cmis, service.id=48}
cq : {org.osgi.service.component.ComponentFactory}={component.factory=com.adobe.drive.connector.handlerfactory, component.name=cq#cq, service.id=75}
helloworld : {org.osgi.service.component.ComponentFactory}={component.factory=com.adobe.drive.connector.handlerfactory, component.name=sample.helloworld#helloworld, service.id=70}

Instantiated connector factories (uuid : factory):

Afterwards, I start Adobe Drive (32bit version). The UI hangs with the message "Adobe Drive is starting. Please wait.". From task manager I can see that not just Adobe Drive was started, but also AD4ServiceManager.exe. I guess, this should not happen, because Adobe Drive should discover the one launched via Eclipse.

 

So what's going wrong here? How does Adobe Drive discover the one launched via Eclipse? What could block discovery?

 

Here more details in case that helps debugging the problem. MANIFEST.MF:

 

Manifest-Version: 1.0
Bundle-ManifestVersion: 2
Bundle-Name: HelloWorld Plug-in
Bundle-SymbolicName: sample.helloworld
Bundle-Version: 2.0.0
Bundle-Vendor: Adobe Systems
Adobe-AutoStart: true
Require-Bundle: com.adobe.drive.connector.api,
 com.adobe.drive.core,
 com.adobe.drive.model,
 com.adobe.csi.utils
Service-Component: OSGI-INF/HelloWorldHandlerFactory.xml

build.properties

source.. = src/
output.. = bin/
bin.includes = META-INF/,\
               .,\
               OSGI-INF/

HelloWorldHandlerFactory.xml:

<?xml version="1.0"?>
     <component name="sample.helloworld#helloworld"
     factory="com.adobe.drive.connector.handlerfactory">
     <implementation class="sample.helloworld.HelloWorldHandlerFactory"/>
</component>

Here the Eclipse run configuration settings:

eclipse-run1.jpg

eclipse-run2.jpg

eclipse-run3.jpg

 
Replies
  • Currently Being Moderated
    Nov 18, 2013 2:42 AM   in reply to Sebastian Stein

    Do you use the 32Bit Version of eclipse? I've had similar issues when trying to use the Drive SDK with a 64Bit version of eclipse

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 18, 2013 2:51 AM   in reply to Sebastian Stein

    I've read your post again: you write you check that AD4Servicemanager.exe is not running. The exe needs to run before starting the project in eclipse. So you just execute the AD4Servicemanager.exe installed on your harddrive, ensure via the taskmanager that it is running (it should take about 1-2 megs of ram), and then start your HelloWorldSample in eclipse. Eclipse "injects" your code to the running AD4ServiceManager.exe.

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 18, 2013 3:56 AM   in reply to Sebastian Stein

    Tip: always start Drive in Windows as administrator, this solved a lot of problems for me.

     

    > In Eclipse, should I configure the 32bit or 64bit version of AD4ServiceManager as plugin execution environment? Currently, I'm using the 32bit version.

     

    I'm using only 32bit versions of all the programs, that is Eclipse, AD4Servicemanager and Drive. But I'm still developing with Drive 4.2; I don't know how things have changed with the new 64bit version in 5.0.1

     

    > Why isn't the step of manually launching AD4ServiceManager.exe not mentioned in the getting started guide?

     

    Good question, I don't remember how I came up with this; I think I found it here in the forums

     
    |
    Mark as:

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points