[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [smila-dev] SMILA Eclipse Run Configuration - Search Servelet not working
|
Hi again,
Here's my own solution to the problem so far:
after some hours I finally created a completely new Run Configuration
according to the [SMILA-install-dir]/configuration/config.ini file. Then
I removed the whole configuration folder from the integration
"SMILA.application" project (the search BPEL is using an old Lucene
pipelet that seems not to exist anymore in the distribution) and
replaced it by the complete configuration directory of the distribution.
Now everything seems to work so far from within Eclipse (let's wait for
the next hour taking issue).
Attached please find the new launch config. It does not contain any
<mapEntry>s as the SMILA.launch does - I don't know if they are
important. It should be tested and included into the integration
packages for SMILA 1.0. Also the configuration directory should be
replaced by the one from the distribution.
Best regards,
Christian
On 21.06.2012 10:49, Christian Weigel wrote:
Hi All,
I am setting up the dev environment for SMILA pipelets using
SMILA-1.0-win32.win32.x86 binary distribution and the
SMILA-1.0-integrator-examples. Almost everything is going well so far. I
can compile and deploy pipelet bundles at lease from within Eclipse (as
the osgi console tells me).
Running SMILA from within Eclipse also works. Creation of indexing job
via REST API etc. works BUT when run from Eclipse the search servelet
does NOT work correctly:
When running the SMILA.launch - configuration there are validation
errors (see attachment). Ignoring these SMILA still starts up and works
as describe above but a call to
http://localhost:8080/SMILA/search
ends up with:
+++++++++++++++++++++++++++
javax.servlet.UnavailableException: Servlet Not Initialized
at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:518)
at ...
+++++++++++++++++++++++++++
Resolving the Bundle validation errors by checking the required bundles
(after that there are 182 instead of 165 bundles) and Reloading the
target platform wihtin Eclipse the error changes to
+++++++++++++++++++++++++++
java.lang.NullPointerException
at
org.eclipse.smila.search.servlet.activator.Activator.getSolrCoreNames(Activator.java:74)
at
org.eclipse.smila.search.servlet.SMILASearchServlet.appendIndexList(SMILASearchServlet.java:278)
at
org.eclipse.smila.search.servlet.SMILASearchServlet.processRequest(SMILASearchServlet.java:179)
+++++++++++++++++++++++++++
So the servlet seems to work now but some of the required solr/lucene
bundles still seem to be missing. I tried to manually activate some of
them via OSGI console but with no success so far.
Could someone possibly provide a launch configuration that
a) resolves the validation errors
b) contains and starts up required bundles in order to use the search
servelet
when starting SMILA 1.0 from within Eclipse.
Thank you and best regards,
_______________________________________________
smila-dev mailing list
smila-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/smila-dev
--
Dipl.-Ing. Christian Weigel
Audio-visual Systems group
Fraunhofer Institute for Digital Media Technology IDMT
Ehrenbergstr. 31
98693 Ilmenau, Germany
Phone +49 3677 467-117
Fax +49 3677 467-467
mailto:christian.weigel@xxxxxxxxxxxxxxxxxx
http://www.idmt.fraunhofer.de
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<launchConfiguration type="org.eclipse.pde.ui.EquinoxLauncher">
<booleanAttribute key="append.args" value="true"/>
<booleanAttribute key="automaticAdd" value="true"/>
<booleanAttribute key="automaticValidate" value="false"/>
<stringAttribute key="bootstrap" value=""/>
<stringAttribute key="checked" value="[NONE]"/>
<booleanAttribute key="clearConfig" value="false"/>
<stringAttribute key="configLocation" value="${workspace_loc}/.metadata/.plugins/org.eclipse.pde.core/SMILA 1.0 new"/>
<booleanAttribute key="default" value="true"/>
<booleanAttribute key="default_auto_start" value="true"/>
<intAttribute key="default_start_level" value="4"/>
<stringAttribute key="deselected_workspace_plugins" value="org.eclipse.smila.integration.pipelet,org.eclipse.smila.integration.worker,org.eclipse.smila.integration.worker.test"/>
<booleanAttribute key="includeOptional" value="true"/>
<listAttribute key="org.eclipse.debug.ui.favoriteGroups">
<listEntry value="org.eclipse.debug.ui.launchGroup.debug"/>
<listEntry value="org.eclipse.debug.ui.launchGroup.run"/>
</listAttribute>
<stringAttribute key="org.eclipse.jdt.launching.PROGRAM_ARGUMENTS" value="-os ${target.os} -ws ${target.ws} -arch ${target.arch} -nl ${target.nl} -console -clean"/>
<stringAttribute key="org.eclipse.jdt.launching.SOURCE_PATH_PROVIDER" value="org.eclipse.pde.ui.workbenchClasspathProvider"/>
<stringAttribute key="org.eclipse.jdt.launching.VM_ARGUMENTS" value="-Declipse.ignoreApp=true -Dosgi.noShutdown=true -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Log4JLogger -Dlog4j.configuration=file:${workspace_loc:SMILA.application/log4j.properties} -Dosgi.requiredJavaVersion=1.6 -Xms40m -Xmx1024m -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.port=9004 -Dorg.eclipse.smila.utils.config.root=${workspace_loc:SMILA.application/configuration} -Dequinox.ds.print=true -Dequinox.ds.debug=false"/>
<stringAttribute key="org.eclipse.jdt.launching.WORKING_DIRECTORY" value="${workspace_loc:SMILA.application}"/>
<stringAttribute key="pde.version" value="3.3"/>
<booleanAttribute key="show_selected_only" value="true"/>
<stringAttribute key="target_bundles" value="javax.persistence@3:default,org.eclipse.core.runtime@1:true,org.eclipse.equinox.common@2:true,org.eclipse.equinox.ds@3:true,org.eclipse.equinox.util@2:default,org.eclipse.persistence.jpa@3:default,org.eclipse.smila.binarystorage.impl@4:default,org.eclipse.smila.blackboard@4:default,org.eclipse.smila.bulkbuilder@4:default,org.eclipse.smila.clusterconfig.simple@4:default,org.eclipse.smila.common.mimetype.impl@4:default,org.eclipse.smila.connectivity.bulkbuilder@4:default,org.eclipse.smila.connectivity.deltaindexing.jpa.impl@4:default,org.eclipse.smila.connectivity.framework.agent.feed@4:default,org.eclipse.smila.connectivity.framework.agent.jobfile@4:default,org.eclipse.smila.connectivity.framework.compound.zip@4:default,org.eclipse.smila.connectivity.framework.crawler.filesystem@4:default,org.eclipse.smila.connectivity.framework.crawler.jdbc@4:default,org.eclipse.smila.connectivity.framework.crawler.web@4:default,org.eclipse.smila.connectivity.framework.impl@4:default,org.eclipse.smila.connectivity.framework@4:default,org.eclipse.smila.http.server@5:default,org.eclipse.smila.importing.crawler.file@4:default,org.eclipse.smila.importing.crawler.web@4:default,org.eclipse.smila.importing.state.objectstore@4:default,org.eclipse.smila.importing@4:default,org.eclipse.smila.jobmanager.persistence.objectstore@4:default,org.eclipse.smila.jobmanager.persistence.zk@4:default,org.eclipse.smila.jobmanager@4:default,org.eclipse.smila.management.jmx.client@4:default,org.eclipse.smila.management.jmx@4:default,org.eclipse.smila.management@3:default,org.eclipse.smila.objectstore.filesystem@3:default,org.eclipse.smila.ontology@4:default,org.eclipse.smila.processing.bpel@4:default,org.eclipse.smila.processing.pipelets@4:default,org.eclipse.smila.processing.worker@4:default,org.eclipse.smila.processing@4:default,org.eclipse.smila.restapi@4:default,org.eclipse.smila.search.api@4:default,org.eclipse.smila.search.servlet@4:default,org.eclipse.smila.solr@4:default,org.eclipse.smila.taskmanager.persistence.zk@4:default,org.eclipse.smila.taskmanager@4:default,org.eclipse.smila.utils@3:default,org.eclipse.smila.workermanager@4:default,org.eclipse.smila.zookeeper@3:default,org.eclipse.update.configurator@3:true"/>
<booleanAttribute key="tracing" value="false"/>
<booleanAttribute key="useCustomFeatures" value="false"/>
<booleanAttribute key="useDefaultConfigArea" value="true"/>
</launchConfiguration>
