Community
Participate
Working Groups
Details to follow.
org.eclipse.cosmos.dc.cmdbf.ws: - cmdbf-ws.jar org.eclipse.cosmos.dc.broker.ws: - web service: - broker/org/.../*.classes from src and src-datamodel directories - broker/META-INF/services.xml - client jar: (broker-client.jar) - include classes from src-datamodel and src-client src folders org.eclipse.cosmos.dc.service.finder: - web service, classes from src - client jar: classes from src-client (servicefinder-client.jar) org.eclipse.cosmos.example.mdr.ws: - web service: - ExampleMdr/org/.../*.class class files from src directory - ExampleMdr/META-INF/services.xml - ExampleMDR/lib/ <- include cmdbf-ws.jar, and the following jars: CMDBfCommon.jar CMDBfMetadata.jar CMDBfQueryService.jar CMDBfQueryTransformation.jar CMDBfRegistrationService.jar CMDBfRegistrationTransformation.jar CMDBfservices.jar org.eclipse.cosmos.common_1.0.0.*.jar These jars were already packaged with the example MDR in i9. Jars files from Axis2 version 1.3 need to be included in the class path before compiling the source. Build output: The 3 directories for the 3 web services are put in the webapps directory of the demo zip file. (the original data manager directories can be removed.) Put broker-client.jar and servicefinder-client.jar for the broker in cosmos-demo\cosmos-client\lib. The broker-client.jar will also be packaged with the UI. Details to follow.
For the Statistical DataManager, org.eclipse.cosmos.dc.stat.datamgr.ws: - web service: - StatisticalDataManager/org/eclipse/cosmos/dc/stat/datamgr/axis/StatisticalDataManager.class - StatisticalDataManager/META-INF/services.xml - StatisticalDataManager/lib/ <- include the following jars: org.apache.derby_10.1.2.1_v200711021015.jar org.eclipse.cosmos.common.jar org.eclipse.cosmos.dc.stat.datamgr.common.jar stay tuned for CBE Datamanager info, it will look fairly similar. - John
For the CBE Datamanager, org.eclipse.cosmos.dc.logging.datamgr.ws: - web service: - CBEServices/org/eclipse/cosmos/dc/logging/datamgr/axis/CBEServices.class - CBEServices/logs/* (file.list, access_log.cbe.xml and windows_app_log.cbe.xml) - CBEServices/lib/ -> include the following jars: org.eclipse.cosmos.common.jar
Created attachment 95441 [details] Zipped patch file Please apply this patch. Jagmit : This functionality requires "axis2-1.3" should be available in expanded form in "dependencies" folder.
Add new sample federating CMDB to the build: module: org.eclipse.cosmos/examples/org.eclipse.cosmos.example.mdr.registration.ws Directory structure: TestFederatingCMDB\lib\ TestFederatingCMDB\META-INF TestFederatingCMDB\org content of lib: CMDBfCommon.jar CMDBfMetadata.jar CMDBfQueryService.jar CMDBfQueryTransformation.jar CMDBfRegistrationService.jar CMDBfRegistrationTransformation.jar CMDBfservices.jar cmdbf-ws.jar datamanager.jar org.eclipse.cosmos.common_1.0.0.v200803291200.jar org.eclipse.osgi_3.4.0.v20071207.jar content of META-INF: MANIFEST.MF QueryService.wsdl RegistrationService.wsdl services.xml xsd0.xsd Content of org: all class files. The resulting TestFederatingCMDB is to be copied to the webapps directory of the demo zip.
Saurabh: I applied this patch in the latest build (COSMOS-1.0.0-200804102009). The build is failing with following compilation errors. javac] Compiling 51 source files to /shared/technology/cosmos/workspace/COSMOSUI/WEB-INF/classes [javac] /shared/technology/cosmos/workspace/plugins/org.eclipse.cosmos.dr.drs.service.handler/src/org/eclipse/cosmos/internal/dr/drs/service/outputter/BrokerOutputter.java:17: package org.eclipse.cosmos.dc.broker.ws.client does not exist [javac] import org.eclipse.cosmos.dc.broker.ws.client.BrokerClient; [javac] ^ [javac] /shared/technology/cosmos/workspace/plugins/org.eclipse.cosmos.dr.drs.service.handler/src/org/eclipse/cosmos/internal/dr/drs/service/outputter/BrokerOutputter.java:18: package org.eclipse.cosmos.dc.broker.ws.client does not exist [javac] import org.eclipse.cosmos.dc.broker.ws.client.DataManager; [javac] ^ [javac] /shared/technology/cosmos/workspace/plugins/org.eclipse.cosmos.dr.drs.service.handler/src/org/eclipse/cosmos/internal/dr/drs/service/outputter/BrokerOutputter.java:19: package org.eclipse.cosmos.dc.broker.ws.datamodel does not exist [javac] import org.eclipse.cosmos.dc.broker.ws.datamodel.Service;
(In reply to comment #6) > Saurabh: > I applied this patch in the latest build (COSMOS-1.0.0-200804102009). The build > is failing with following compilation errors. > javac] Compiling 51 source files to > /shared/technology/cosmos/workspace/COSMOSUI/WEB-INF/classes > [javac] > /shared/technology/cosmos/workspace/plugins/org.eclipse.cosmos.dr.drs.service.handler/src/org/eclipse/cosmos/internal/dr/drs/service/outputter/BrokerOutputter.java:17: > package org.eclipse.cosmos.dc.broker.ws.client does not exist > [javac] import org.eclipse.cosmos.dc.broker.ws.client.BrokerClient; > [javac] ^ > [javac] > /shared/technology/cosmos/workspace/plugins/org.eclipse.cosmos.dr.drs.service.handler/src/org/eclipse/cosmos/internal/dr/drs/service/outputter/BrokerOutputter.java:18: > package org.eclipse.cosmos.dc.broker.ws.client does not exist > [javac] import org.eclipse.cosmos.dc.broker.ws.client.DataManager; > [javac] ^ > [javac] > /shared/technology/cosmos/workspace/plugins/org.eclipse.cosmos.dr.drs.service.handler/src/org/eclipse/cosmos/internal/dr/drs/service/outputter/BrokerOutputter.java:19: > package org.eclipse.cosmos.dc.broker.ws.datamodel does not exist > [javac] import org.eclipse.cosmos.dc.broker.ws.datamodel.Service; Compilation errors are seems to be coming from data reporting project and patch did not touch any of the data reporting project. Could this be because of some other reason ?
(In reply to comment #7) > > package org.eclipse.cosmos.dc.broker.ws.datamodel does not exist > > [javac] import org.eclipse.cosmos.dc.broker.ws.datamodel.Service; > Compilation errors are seems to be coming from data reporting project and patch > did not touch any of the data reporting project. Could this be because of some > other reason ? The reason is that the org.eclipse.cosmos.dc.broker.ws is not a plugin and the org.eclipse.cosmos.dr.drs.service.handler plugin depends on this non-plugin. Hubert, Can we move out the common code from org.eclipse.cosmos.dc.broker.ws into a plugin so that we don't have this problem?
(In reply to comment #2) > For the Statistical DataManager, > org.eclipse.cosmos.dc.stat.datamgr.ws: > - web service: > - > StatisticalDataManager/org/eclipse/cosmos/dc/stat/datamgr/axis/StatisticalDataManager.class > - StatisticalDataManager/META-INF/services.xml > - StatisticalDataManager/lib/ <- include the following jars: > org.apache.derby_10.1.2.1_v200711021015.jar > org.eclipse.cosmos.common.jar > org.eclipse.cosmos.dc.stat.datamgr.common.jar > stay tuned for CBE Datamanager info, it will look fairly similar. > - John Hi John, Can you please answer these questions. (1) Do we need compiled classes of "org.eclipse.cosmos.dc.stat.datamgr.ws.common" project as jar into StatisticalDataManager/lib folder. (2) Do we have to copy the jar of the classes of "org.eclipse.cosmos.dc.stat.datamgr.ws.common" project into cosmos-client/lib project. (3) Do we have approval to bundle "org.apache.derby" plugin.
1) yes, we need org.eclipse.cosmos.dc.stat.datamgr.ws.common.jar in StatisticalDataManager/lib 2) no, I don't think we need org.eclipse.cosmos.dc.stat.datamgr.ws.common.jar in cosmos-client/lib 3) I'm assuming we do, this is not new, as the old stat datamanager uses it, so the new one needs to as well and can operate under the same approvals as the old one has.
Just one more question right now I am compiling the classes of "org.eclipse.cosmos.dc.stat.datamgr.ws.client" and "org.eclipse.cosmos.dc.logging.datamgr.ws.client" and then I am placing it in cosmos-client/lib directory. Do we need this to do.
I changed my mind about #2 from above, I think that to be safe, we might as well have org.eclipse.cosmos.dc.stat.datamgr.ws.common in cosmos-client/lib So you can add org.eclipse.cosmos.dc.stat.datamgr.ws.client and org.eclipse.cosmos.dc.logging.datamgr.ws.client to cosmos-client/lib - John
Hi Hubert, Do we need to place "cmdbf-ws.jar and datamanager.jar" file in "cosmos-client/lib" folder.
Created attachment 95734 [details] Patch for stat and logging data manager
in the cosmos-demo/webapps/COSMOSReportViewer/WEB-INF/lib the birt jar needs to be replaced with org.eclipse.cosmos.examples.e2e.dc.birt.helper and org.eclipse.cosmos.dc.logging.datamgr.client needs to be replaced with org.eclipse.cosmos.dc.logging.datamgr.ws.client org.eclipse.cosmos.dc.stat.datamgr.client needs to be replaced with org.eclipse.cosmos.dc.stat.datamgr.ws.client org.eclipse.cosmos.dc.stat.datamgr.common needs to be replaced with org.eclipse.cosmos.dc.stat.datamgr.ws.common
(In reply to comment #10) > 3) I'm assuming we do, this is not new, as the old stat datamanager uses it, so > the new one needs to as well and can operate under the same approvals as the > old one has. Who contributed derby, JT? Was it you or someone from IBM?
When is the target for completing this? This defect is blocking me from completing bug 224215.
That stat datamanager has needed derby since its inception, if this is a problem, why is this just coming up now? And what is the proposed resolution? - John
Trying to work on work item listed in comment#13. The org.eclipse.cosmos.examples.e2e.dc.birt.helper is not packaged as plugin. Also this plugin, should be under which feature.
(In reply to comment #19) > Trying to work on work item listed in comment#13. The > org.eclipse.cosmos.examples.e2e.dc.birt.helper is not packaged as plugin. > > Also this plugin, should be under which feature. > Discussed with Jagmit: I made org.eclipse.cosmos.examples.e2e.dc.birt.helper a plugin.
We have a new SML MDR to be included in the build. The build is similar to the example mdr. module: org.eclipse.cosmos/resource-modeling/org.eclipse.cosmos.rm.sml.mdr.ws Web service: SMLMDR/ /lib <- list of dependencies, see list below /META-INF <- 4 files: MANIFEST.MF,QueryService.wsdl,cmdbfQuery.wsdl,services.xml /org <- all class files /sml-repository <- copied from org.eclipse.cosmos.rm.sml.mdr.ws/sml-repository Jar files to be included in the lib directory: CMDBfCommon.jar CMDBfMetadata.jar CMDBfQueryService.jar CMDBfQueryTransformation.jar CMDBfRegistrationService.jar CMDBfRegistrationTransformation.jar cmdbf-ws.jar datamanager.jar org.eclipse.ant.core_3.1.300.v20071212.jar org.eclipse.core.contenttype_3.2.200.v20070910.jar org.eclipse.core.expressions_3.4.0.v20071212-1800.jar org.eclipse.core.filesystem_1.2.0.v20071207.jar org.eclipse.core.jobs_3.3.100.v20071207.jar org.eclipse.core.resources_3.4.0.v20071210.jar org.eclipse.core.runtime.compatibility.auth_3.2.100.v20070502.jar org.eclipse.core.runtime_3.4.0.v20071207.jar org.eclipse.core.variables_3.2.0.v20070910.jar org.eclipse.cosmos.common_1.0.0.v200803291200.jar org.eclipse.cosmos.rm.repository_1.0.0.v200804011834.jar org.eclipse.equinox.app_1.0.100.v20071207.jar org.eclipse.equinox.common_3.4.0.v20071207.jar org.eclipse.equinox.preferences_3.2.200.v20070827.jar org.eclipse.equinox.registry_3.4.0.v20071203.jar org.eclipse.osgi.services_3.1.200.v20071203.jar org.eclipse.osgi_3.4.0.v20071207.jar validation.jar The resulting SMLDMR directory will be packaged in the webapps directory of the demo jar file.
Created attachment 96162 [details] Patch to build sml mdr webservice
As part of this defect, please package org.eclipse.cosmos.dc.datamanager.ws to be a plugin. The work being done for bug 224215 requires this change. Thanks!!!
My Datamanagers, org.eclipse.cosmos.dc.logging.datamgr.ws and org.eclipse.cosmos.dc.stat.datamgr.ws In the new framework now have a dependency on org.eclipse.cosmos.dc.datamanager.ws which needs to included in the lib directory of the webservice (referenced as datamanager.jar in previous comments about other datamanagers) - John
Hubert will provide a list of plugins that can be removed from the build. The build is currently including unused and obsolete plugins. Also, any of the new plugins that have been created need their version # changed to include the ".qualifier" suffix. Also please be sure to check the Name and Provider fields for consistency with other COSMOS plugins. The names should all have the "COSMOS" prefix in them, and the Provider should be "Eclipse.org". Just a check of a couple of the *.ws plugins suggests we aren't being consistent in our conventions there.
The plugin org.eclipse.cosmos.dc.datamanager.ws needs to be renamed and repackaged. The "M" should be capitalized so that it's written org.eclipse.cosmos.dc.dataManager.ws following the naming of other similar plugins. Also, the request was for this to be a plugin folder instead of a plugin jar, containing a file named datamanager.jar (see John Todd's comments on this defect). Also, the initial comment on this defect indicated that the org.eclipse.cosmos.dc.cmdbf.ws plugin should be packaged as folder containing a jar named cmdbf-ws.jar.
Regarding datamanager.jar, I'm just following Hubert's lead as to how he packaged the other Datamanagers (ExampleMdr and SMLMdr) but yes, I think the contents of datamanager.jar comes from org.eclipse.cosmos.dc.datamanager.ws - John
demo packaging changes: We don't need to package the "old" data managers in the webapps directory of the demo. You can remove: cosmos examplemdr logging smlmdr stat Please rename the following directories: broker => Broker ExampleMdrWs => ExampleMdr loggingws => >LoggingDataManager servicefinder => ServiceFinder smlmdrws => SMLMDR statws => StatDataManager (Axis2 uses these directory name as service group names, so I want them to look better. The UI also depends on these names as they are hardcoded somewhere.)
fixed this above issue in the latest build (COSMOS-1.0.0-200804162108). Please verify the fix
(In reply to comment #29) > fixed this above issue in the latest build (COSMOS-1.0.0-200804162108). Please > verify the fix Looks great overall. I see that those plugins have been turned into folders, and the manifests have been cleaned up. One minor detail that doesn't really bother me, but I don't know if it affects anyone else, is that the new data manager jar file is named datamanager-ws.jar instead of datamanager.jar in the build. I am fine with either name, so someone else will have to indicate if that's a problem.
(In reply to comment #28) > demo packaging changes: > We don't need to package the "old" data managers in the webapps directory of > the demo. Thanks for the list of items that can be removed from the demo download, Hubert. Do you have a list of items that can be removed from the COSMOS SDK download? I am assuming the Muse stuff is one example of something that can be removed.
The new CLI client CosmosCLI in org.eclipse.cosmos.example.end2endTestClient introduces the following project dependencies on the end2endTestClient project org.eclipse.cosmos.dc.broker.core org.eclipse.cosmos.dc.cmdbf.ws org.eclipse.cosmos.dc.service.finder - John
Fixed this above issue and other remaining issue in the latest build (COSMOS-1.0.0-200804171030). Please verify the build and let me know the results. So that I can announce the candidate driver.
Please package the web services under a "services" directory under cosmos-demo directory. The webapps directory will contain the two directories for the UI. The directory structure for the cosmos-demo zip looks like this: cosmos-demo\bin \cosmos-client \database \webapps \services \installGuide.txt
Please remove the following files from the demo zip file: from this directory: cosmos-demo\cosmos-client\lib\ Remove the following files: muse-complete-2.2.0.jar org.apache.xerces_2.8.0.v200704181622.jar org.eclipse.cosmos.dc.broker.client_1.0.0.v200803291200.jar org.eclipse.cosmos.dc.dataManager.client_1.0.0.v200803291200.jar org.eclipse.cosmos.dc.dataManager.common_1.0.0.v200803291200.jar org.eclipse.cosmos.dc.logging.datamgr.client_1.0.0.v200804011200.jar org.eclipse.cosmos.dc.logging.datamgr.common_1.0.0.v200804011200.jar org.eclipse.cosmos.dc.management.domain.client_1.0.0.HEAD.jar org.eclipse.cosmos.dc.mdr.client_1.0.0.v200803291200.jar org.eclipse.cosmos.dc.mdr.common_1.0.0.v200803291200.jar org.eclipse.cosmos.dc.stat.datamgr.client_1.0.0.v200804011200.jar org.eclipse.cosmos.dc.stat.datamgr.common_1.0.0.v200804011200.jar org.eclipse.cosmos.me.management.common_1.0.0.v200804011200.jar org.eclipse.cosmos.me.management.wsdm_1.0.0.v200804011200.jar org.w3c.dom_1.3.3.v200704190547.jar
There is a problem with the SMLMDR service. In the lib directory, remove CMDBfservices.jar, and add validation.jar. validation.jar comes from org.eclipse.cosmos.rm.validation.
made the fix required in comment# 34, 35, 36 in the latest driver COSMOS-1.0.0-200804171615. Please verify the fix and let me know the results
Please add the Aperi MDR to the distribution. It should have a similar directory structure as the ExampleMDR, as follows: Web service: AperiMdr/ /META-INF <- 4 files from the org.eclipse.cosmos.aperi.mdr.ws/WebContent/WEB-INF/services/AperiMDR/META-INF directory: cmdbfDataModel.xsd, QueryService.wsdl,cmdbfQuery.wsdl,services.xml /org <- all class files from the org.eclipse.cosmos.aperi.mdr.ws/WebContent/WEB-INF/services/AperiMDR/org directory /lib <- list of dependencies (similar to the ExampleMDR, plus derbyclient.jar from org.eclipse.cosmos.aperi.mdr.ws/WebContent/WEB-INF/services/AperiMDR/lib/derbyclient.jar): CMDBfCommon.jar CMDBfMetadata.jar CMDBfQueryService.jar CMDBfQueryTransformation.jar CMDBfRegistrationService.jar CMDBfRegistrationTransformation.jar cmdbf-ws.jar datamanager.jar org.eclipse.cosmos.common_1.0.0.v200803291200.jar Also include the AperiMdr directory in the webapps directory of the demo jar file. Thanks, Bill
(In reply to comment #38) > Please add the Aperi MDR to the distribution. It should have a similar > directory structure as the ExampleMDR, as follows: Bill: Are you sure you don't want to add this new bundle to "cosmos-demo/services" ?
(In reply to comment #39) > (In reply to comment #38) > > Please add the Aperi MDR to the distribution. It should have a similar > > directory structure as the ExampleMDR, as follows: > Bill: > Are you sure you don't want to add this new bundle to "cosmos-demo/services" ? Oops, you are correct. It should be "cosmos-demo/services". Thanks!
the cosmos-demo/cosmos-client/lib directory needs some axis2 jars specifically axis2-kernel-1.3.jar axis2-api-1.2.5.jar axiom-impl-1.2.5.jar commons-codec-1.3.jar commons-httpclient-3.0.1.jar commons-logging-1.1.jar XmlSchema-1.3.2.jar wsdl4j-1.6.2.jar stax-api-1.0.1.jar wstx-asl-3.2.1.jar - John
There is apparently legal mumbo jumbo about axis2, so hold off on comment #41 ruth said she going update here with more details. - John
Guys, before we check in anything can you check with Eclipse Legal, please? For comment #41, John, our approval for Axis2 was based on it being a prereq, not redistributed. Please read IPZilla [CQ 2219] axis2 Version: 1.3 http://dev.eclipse.org/ipzilla/show_bug.cgi?id=2219 for details. Can you add yourself to that IPZilla and explain that you now want it to be a redistribution, not a prereq, and does that change anything? Also please ask them how to package the Axis2 licenses given that they're not being redistributed in an Eclipse plug-in? For comment #38, Bill, we have permission to redistribute Derby from Orbit. Please read IPZilla https://dev.eclipse.org/ipzilla/show_bug.cgi?id=2123 for details. I don't know if that approval allows us to modify the Orbit bundle. Can you add yourself to that IPZilla and ask if we can modify the bundle, please? From what I know the build pulls that bundle directly from Orbit, which means that if we need to change it then you'd probably need to check it into CVS, which may mean that we need a separate IPZilla for that check-in.
There is no need for axis2 jars to be treated differently for the cosmosclient than the other components that need it...it can go with the flow. Sorry to cause confusion. - John
Created attachment 96656 [details] Patch to include AperiMdr web-service
Marking bug as fixed.
