"org.eclipse.equinox.http" contains a slimmed down Http Service implementation 
that we use in embedded use cases. Relevant to your case this implementation is 
not able to support the Eclipse Help systems Servlet and JSP needs.

You want the implementation in org.eclipse.equinox.http.jetty as well as it's 
dependencies.

HTH
-Simon



----- Original Message ----- 
  From: Carlos M 
  To: equinox-dev@eclipse.org 
  Sent: Friday, August 28, 2009 7:49 AM
  Subject: [equinox-dev] Problem with help contents in RCP application(embebed 
http server)


  Hi.

  I have some configuration problems in RCP product related with help system.
  "Help contents" option works fine if it's executed inside eclipse workbench, 
but if I export the product to other localization, the help doesn't work.

  It throws the next exception: java.lang.NoClassDefFoundError: 
org/eclipse/equinox/http/jetty/JettyConfigurator
  (This is very uncommon because the plugin that contains that class is in the 
list for product dependencies)

  I suppose that help contents run on http server (jetty) and by any reason, 
this server is needed to be configurated in any way.
  I have tried to change the config.ini file in the installation, appending the 
next:

                            org.eclipse.equinox.h...@3:start, 
org.eclipse.equinox.http.regis...@start" 

  for the property "osgi.bundles".
  Before that I have included a dependency in my plugin: 
"org.eclipse.equinox.http.registry".

  However, it produces a error with org.eclipse.equinox.h...@3:start

  I don't know how I can configurate equinox for that RCP workbench.

  Thanks in advance,
  Carlos.














------------------------------------------------------------------------------


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

Reply via email to