| [corona-dev] Even MORE -Corona M5 Requirements |
|
Eventing is still not working completely but it is getting
closer. Eventing Issues * ECF Configuration Item – a change needs to be made
to the ECF server.xml configuration file to add 2 server groups. First find the configuration file located at path below: <Eclipse_IDE_InstallationDirectory>\eclipse\plugins\org.eclipse.ecf.server_0.9.1\conf\server.xml
Edit the server.xml file so it contains something like this: <server> <connector
protocol="ecftcp" hostname="localhost"
port="3282" timeout="30000"> <group
name="server"/> <group
name="corona"/> </connector> </server> * Only Team Members get Events For a user to receive events for a ContextContainer
he/she must be listed as a user in that team member in the TeamMemberRepository
and they must have the ContextContainer open. To find your user name do: getprop
user.name in the osgi console of a Client Debug session to see
the Team Member Name that must be in the Team Member repository. * Collaboration Events only sends file change events
when the files are in Projects with a Collaboration Nature – you can look
in the .project file and search for “collaboration” to see if it
has the Collaboration Nature defined. *Server side bundles that must be started for
Eventing -
org.eclipse.ecf -
org.eclipse.ecf.server I
changed run level to 2 in SOA_ContainerManager debug configuration -
org.eclipse.ecf.discovery -
org.eclipse.ecf.provider -
org.eclipse.equinox.event
- I changed run level to 1 in SOA_ContainerManager debug configuration -
org.eclipse.corona.collaboration.ecf -
org.eclipse.corona.collaboration.ecf.container
- I changed run level to 3 in SOA_ContainerManager debug configuration -
org.eclipse.corona.collaboration.project *Client side bundles that must be started for
Eventing -
org.eclipse.equinox.event -
you DO NOT want
org.eclipse.corona.collaboration.ecf.container started on clients like
SOA_ContainerClient it is for Server side only -
org.eclipse.ecf -
org.eclipse.ecf.discovery -
org.eclipse.corona.collaboration.ecf -
org.eclipse.corona.collaboration.project Below
is the original set of requirements I’m trying to keep complete list: http://java.sun.com/javase/downloads/index.jsp Make sure that your Eclipse IDE contains the plugins org.eclipse.equinox.osgi org.eclipse.core.resources org.eclipse.core.resources.win32 org.eclipse.core.runtime.compatibility.registry http://download.eclipse.org/eclipse/equinox/drops/R-3.2-200606291905/index.php org.eclipse.equinox.http org.eclipse.equinox.event org.eclipse.osgi.services Not sure if this is required and not sure
if it comes with base Eclipse 3.2 org.eclipse.core.runtime.compatibility.registry From WTP you need: org.wsdl4j You also need these Apache items copied into the project
directories for building corona ./muse-osgi-soa-core/lib: muse-osgi-soa-core-2.0.0.jar ./org.apache.axis2/lib: activation-1.1.jar
annogen-0.1.0.jar
axiom-api-SNAPSHOT.jar
axiom-impl-SNAPSHOT.jar axis2-adb-SNAPSHOT.jar
axis2-java2wsdl-SNAPSHOT.jar axis2-kernel-SNAPSHOT.jar axis2-saaj-SNAPSHOT.jar commons-codec-1.3.jar commons-httpclient-3.0.1.jar mail-1.4.jar neethi-SNAPSHOT.jar stax-api-1.0.1.jar stax-utils-20060915.jar wstx-asl-2.9.3.jar XmlSchema-SNAPSHOT.jar ./org.apache.axis2.codegen/lib: axis2-codegen-SNAPSHOT.jar ./org.apache.axis2.security.tokenserver/lib: axis2-rahas-SNAPSHOT.jar ./org.apache.ws.security/lib: axis2-security-SNAPSHOT.jar wss4j-SNAPSHOT.jar xmlsec-1.3.0.jar ./org.eclipse.corona.repository.derby/lib: derbyclient.jar derby.jar
derbyLocale_de_DE.jar derbyLocale_es.jar derbyLocale_fr.jar derbyLocale_it.jar derbyLocale_ja_JP.jar derbyLocale_ko_KR.jar derbyLocale_pt_BR.jar derbyLocale_zh_CN.jar derbyLocale_zh_TW.jar derbynet.jar derbyTesting.jar derbytools.jar derby.war |
<server> <connector protocol="ecftcp" hostname="localhost" port="3282" timeout="30000"> <group name="server"/> <group name="corona"/> </connector> </server>