Menu
▾
▴
openoss-devel — OpenOSS Developer Mailing List
You can subscribe to this list here.
| 2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(53) |
Aug
(86) |
Sep
(55) |
Oct
(19) |
Nov
(12) |
Dec
(9) |
| 2010 |
Jan
(8) |
Feb
(32) |
Mar
(31) |
Apr
(70) |
May
(67) |
Jun
(71) |
Jul
(26) |
Aug
(47) |
Sep
(25) |
Oct
(16) |
Nov
(11) |
Dec
(16) |
| 2011 |
Jan
(30) |
Feb
(31) |
Mar
(71) |
Apr
(64) |
May
(55) |
Jun
(25) |
Jul
(3) |
Aug
(24) |
Sep
(20) |
Oct
(18) |
Nov
(21) |
Dec
(1) |
| 2012 |
Jan
(9) |
Feb
(21) |
Mar
(29) |
Apr
(9) |
May
(9) |
Jun
(54) |
Jul
(37) |
Aug
(24) |
Sep
(43) |
Oct
(34) |
Nov
(25) |
Dec
(27) |
| 2013 |
Jan
(5) |
Feb
(13) |
Mar
(23) |
Apr
(9) |
May
(11) |
Jun
|
Jul
(2) |
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2014 |
Jan
(1) |
Feb
|
Mar
(3) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Pierre G. <pga...@tm...> - 2013-04-02 13:15:45
|
Hi Craig, Have you done your changes can I start the merge with the SOAP generator now ? Pierre On 2013-03-20, at 7:29 AM, Craig Gallen (opennms) <cg...@op...> wrote: > Sorry forget what I said about .settings. Its OK to check in for soap > generator. However I do need to know status of trunk version of soap > generator > > thanks > > On 20/03/2013 11:09, Craig Gallen (opennms) wrote: >> Hi, >> >> It looks like a lot of work is being done to finish the soap generator I >> want to fix the build system etc to work with it. I'm trying to >> rationalise the versions of the soap generator and the build. >> >> Firstly it looks like people are checking in .settings folders with the >> soap generator. These contain all of the subversion history and should >> never be checked in (should be set to subversion:ignore). I will try and >> remove these and set the subversion flags appropriately. Please make >> sure you aren't checking in .settings folders. >> >> Secondly, we need to update the version numbers on the soap generator to >> 1.2 and update the build system etc appropriately. I can do this work if >> I know i am working with the correct version of hted soap generator. can >> somebody tell me if all of the changes are checked into the trunk >> version of the soap generator so that we can change it's working number. >> What is the purpose of the RELEASE_EXTERNAL_XSDS release compared with >> trunk? It cant be a release if it is 1.1 as it will upset all of the >> existing model project configurations for projects which have not been >> updated to use the latest soap plugin >> >> thanks >> Craig >> > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_d2d_mar > _______________________________________________ > Openoss-devel mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openoss-devel > |
|
From: Pierre G. <pga...@tm...> - 2013-04-02 13:14:30
|
Hi Xose, Can you take a look at this ? This is a blocking issue. This seems to be related to the change that we made to the package name for common. Regards Pierre On 2013-03-27, at 12:37 PM, Craig Gallen (opennms) <cg...@op...> wrote: > Hi, > I have generated a new issue with soap generator > https://openoss.atlassian.net/browse/JOS-49 and repeated it below. This > problem shows up in the generated xsd's of the RAM model. I have > committed new tigerstripe.xml files for the RAM Model and RAM Dependency > models so that the 1.2 soap plugin can be used. (the previous 1.1 > configuration is still present but set to a disabled state). > > The problem is as described below; > > Using the latest trunk revision 2729 version 1.2 Soap Generator, I have > generated common and internal models with no problem. However the RAM > model generates incorrect namespace references to file locations. This > is repeatable when generating the TIP_RAM_MODEL. In the generated filed > I have the following; > > In file ram_resource_trouble_alarm.xsd we have a reference > <xsd:import namespace="http://www.tmforum.org/xml/tip/resource/res/nrb" > schemaLocation="dep_resource_res_nrb.xsd"/> > this throws an error because the file dep_resource_res_nrb.xsd does not > exist > > However the generated common_cbe_job.xsd does give the correct reference > <xsd:import namespace="http://www.tmforum.org/xml/tip/resource/res/nrb" > schemaLocation="common_resource_res_nrb.xsd"/> > > Craig > > <ram_resource_trouble_alarm.xsd><common_resource_res_nrb.xsd> |
|
From: Flauw, M. <Mar...@hp...> - 2013-03-27 16:58:55
|
Hi Craig, Resource_res_nrb should not be a dep file but a common file, so the prefix for it should be common_ and not dep_ Best regards, Marc -----Original Message----- From: Craig Gallen [mailto:gal...@go...] On Behalf Of Craig Gallen (opennms) Sent: Wednesday, March 27, 2013 5:37 PM To: openoss-devel; Craig Gallen (OpenNMS); Pierre Gauthier; Xose Ramon Sousa Vazquez; Flauw, Marc Subject: JOS-49 incorrect reference to XSD files in generated model Hi, I have generated a new issue with soap generator https://openoss.atlassian.net/browse/JOS-49 and repeated it below. This problem shows up in the generated xsd's of the RAM model. I have committed new tigerstripe.xml files for the RAM Model and RAM Dependency models so that the 1.2 soap plugin can be used. (the previous 1.1 configuration is still present but set to a disabled state). The problem is as described below; Using the latest trunk revision 2729 version 1.2 Soap Generator, I have generated common and internal models with no problem. However the RAM model generates incorrect namespace references to file locations. This is repeatable when generating the TIP_RAM_MODEL. In the generated filed I have the following; In file ram_resource_trouble_alarm.xsd we have a reference <xsd:import namespace="http://www.tmforum.org/xml/tip/resource/res/nrb" schemaLocation="dep_resource_res_nrb.xsd"/> this throws an error because the file dep_resource_res_nrb.xsd does not exist However the generated common_cbe_job.xsd does give the correct reference <xsd:import namespace="http://www.tmforum.org/xml/tip/resource/res/nrb" schemaLocation="common_resource_res_nrb.xsd"/> Craig |
|
From: Craig G. (opennms) <cg...@op...> - 2013-03-27 16:37:42
|
Hi, I have generated a new issue with soap generator https://openoss.atlassian.net/browse/JOS-49 and repeated it below. This problem shows up in the generated xsd's of the RAM model. I have committed new tigerstripe.xml files for the RAM Model and RAM Dependency models so that the 1.2 soap plugin can be used. (the previous 1.1 configuration is still present but set to a disabled state). The problem is as described below; Using the latest trunk revision 2729 version 1.2 Soap Generator, I have generated common and internal models with no problem. However the RAM model generates incorrect namespace references to file locations. This is repeatable when generating the TIP_RAM_MODEL. In the generated filed I have the following; In file ram_resource_trouble_alarm.xsd we have a reference <xsd:import namespace="http://www.tmforum.org/xml/tip/resource/res/nrb" schemaLocation="dep_resource_res_nrb.xsd"/> this throws an error because the file dep_resource_res_nrb.xsd does not exist However the generated common_cbe_job.xsd does give the correct reference <xsd:import namespace="http://www.tmforum.org/xml/tip/resource/res/nrb" schemaLocation="common_resource_res_nrb.xsd"/> Craig |
|
From: Craig G. (opennms) <cg...@op...> - 2013-03-20 11:29:27
|
Sorry forget what I said about .settings. Its OK to check in for soap generator. However I do need to know status of trunk version of soap generator thanks On 20/03/2013 11:09, Craig Gallen (opennms) wrote: > Hi, > > It looks like a lot of work is being done to finish the soap generator I > want to fix the build system etc to work with it. I'm trying to > rationalise the versions of the soap generator and the build. > > Firstly it looks like people are checking in .settings folders with the > soap generator. These contain all of the subversion history and should > never be checked in (should be set to subversion:ignore). I will try and > remove these and set the subversion flags appropriately. Please make > sure you aren't checking in .settings folders. > > Secondly, we need to update the version numbers on the soap generator to > 1.2 and update the build system etc appropriately. I can do this work if > I know i am working with the correct version of hted soap generator. can > somebody tell me if all of the changes are checked into the trunk > version of the soap generator so that we can change it's working number. > What is the purpose of the RELEASE_EXTERNAL_XSDS release compared with > trunk? It cant be a release if it is 1.1 as it will upset all of the > existing model project configurations for projects which have not been > updated to use the latest soap plugin > > thanks > Craig > |
|
From: Craig G. (opennms) <cg...@op...> - 2013-03-20 11:09:58
|
Hi, It looks like a lot of work is being done to finish the soap generator I want to fix the build system etc to work with it. I'm trying to rationalise the versions of the soap generator and the build. Firstly it looks like people are checking in .settings folders with the soap generator. These contain all of the subversion history and should never be checked in (should be set to subversion:ignore). I will try and remove these and set the subversion flags appropriately. Please make sure you aren't checking in .settings folders. Secondly, we need to update the version numbers on the soap generator to 1.2 and update the build system etc appropriately. I can do this work if I know i am working with the correct version of hted soap generator. can somebody tell me if all of the changes are checked into the trunk version of the soap generator so that we can change it's working number. What is the purpose of the RELEASE_EXTERNAL_XSDS release compared with trunk? It cant be a release if it is 1.1 as it will upset all of the existing model project configurations for projects which have not been updated to use the latest soap plugin thanks Craig |
|
From: Xose R. S. V. <xr...@op...> - 2013-03-19 18:10:02
|
I have uploaded the Soap generator in trunk. Please test it to see if it solve the problem. When we avoid the generation of dep files for common packages we put the restriction in all the model and not only in the dependencies part. Regards El 19/03/2013 12:55, Flauw, Marc escribió: > > Xose, > > The fact that common_entity only is generated is valid for all > interfaces. I have this problem also when building RAM and it is > show-stopper for RAM as I cannot issue a kit where xsd do not validate. > > I have filled an issue for this problem already. > > > Best regards > > Marc > > *From:*Xose Ramon Sousa Vazquez [mailto:xr...@op...] > *Sent:* Tuesday, March 19, 2013 12:49 PM > *To:* Flauw, Marc > *Cc:* Pierre Gauthier; openoss-devel; Craig Gallen (opennms) > *Subject:* Re: [Openoss-devel] problems with internal model > > Sorry for the delayed response but I am in a production phase in these > two weeks and it is difficult to me to get time. I think that perhaps > the modification related with the definition as dep_ files in the > common model has problems with the internal project that has elements > that usually is taken as dependency and in this case it takes part > from the model. > > I will review the code as soon as possible and then publish the > changes to the repository. > > Regards > El 14/03/2013 8:55, Flauw, Marc escribió: > > Dear all, > > > > I had a look at the Internal model and the attributes of entityBase had a tipAttribute present with notificationDefinition set to true. > > I changed those to NA and the internal model now compiles correctly and has no dependency on the common model. > > > > This is quite strange because I didn't touch the tipAttribute stereotype in my recent changes, so it seems there was some code to prevent looping by ignoring those attributes that has been disabled. > > > > I have committed those changes, but I haven't checked yet if they have any other impact on other specifications, like RAM or PM > > > > I tried also recompiling the Common Model and I still have the same blocking problem that I reported as JOS-46: only common_entity.xsd is generated. The rest of the common files are not. The build id failing at the end as it does not find files, but I don't see any error in the SOAP Gen part. > > > > I am attaching the log of the common model build on my machine. > > > > Best regards > > > > Marc > > -----Original Message----- > > From: Pierre Gauthier [mailto:pga...@tm...] > > Sent: Wednesday, March 13, 2013 7:28 PM > > To: Xose Ramon Sousa Vazquez > > Cc: openoss-devel; Flauw, Marc; Craig Gallen (opennms) > > Subject: Re: [Openoss-devel] problems with internal model > > > > Xi Xose, > > > > Can you look into this and let us know ? > > > > Pierre > > On 2013-03-13, at 2:13 PM, "Craig Gallen (opennms)"<cg...@op...> <mailto:cg...@op...> > > wrote: > > > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > Marc, > > > > I looked at the internal model build problems and the issues appears > > to be in the generated xsd's. > > It appears that the internal model will not build because there are > > circular dependencies on the common model > > > > in the generated entity identifier.xsd, there is an import for the > > common_notifications.xsd which doesn't get generated except in the > > common model which had dependencies on the internal model :) > > > > <xsd:import > > namespace="http://www.tmforum.org/xml/tip/common/notifications" <http://www.tmforum.org/xml/tip/common/notifications> > > schemaLocation="common_notifications.xsd > > > > > > Craig > > -----BEGIN PGP SIGNATURE----- > > Version: GnuPG v2.0.17 (MingW32) > > Comment: Using GnuPG with Thunderbird -http://www.enigmail.net/ > > > > iQEcBAEBAgAGBQJRQMG1AAoJEATefL4tbU2QleUH/R45TYYHwO6Ofy9F4NVVonLN > > Yj1TgmiwIjsqqlsrkKT+IjUjje4eUHlr0zvLrDlyLXV23jdwNTzutsLD6O/LTBKw > > 0Xx1+CBlNBz1Pg9QBD9cEhpYvIlEV/id62lA0xTVbHGpYuywVF3wjGm8OM0Wy7/3 > > FUYCeLXlBr9Cp4MXzD3w7n4jMZL4Ivh7JufyMAzazyPKh0T4lhs7SRBnDeTgIWQB > > gyVVfkbKiVWP78LUlnBWENTZXWBgaEu3eee98SEJK0PruIhOxVg4rOz7OblEBWXb > > DxebdQNj9uy4IBZn4nvzzuahD5FvxfBKhhaVzsAq9lPX1aL2zblLOcml/5IWrmo= > > =Wp32 > > -----END PGP SIGNATURE----- > > > > ---------------------------------------------------------------------- > > -------- Everyone hates slow websites. So do we. > > Make your web apps faster with AppDynamics Download AppDynamics Lite > > for free today: > > http://p.sf.net/sfu/appdyn_d2d_mar > > _______________________________________________ > > Openoss-devel mailing list > > Ope...@li... <mailto:Ope...@li...> > > https://lists.sourceforge.net/lists/listinfo/openoss-devel > > > > > > > > > > ------------------------------------------------------------------------------ > > Everyone hates slow websites. So do we. > > Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: > > http://p.sf.net/sfu/appdyn_d2d_mar > > _______________________________________________ > > Openoss-devel mailing list > > Ope...@li... <mailto:Ope...@li...> > > https://lists.sourceforge.net/lists/listinfo/openoss-devel > > -- > > *Xose Ramon Sousa Vazquez*| Director OSS Technologies, Director I+D > T/ + 34 986 410 091 (ext) 206 | M/ +34 675 550 029 > www.optaresolutions.com > <http://www.optaresolutions.com> > Optare Solutions <http://optarecoolvendor.com> > -- *Xose Ramon Sousa Vazquez* | Director OSS Technologies, Director I+D T/ + 34 986 410 091 (ext) 206 | M/ +34 675 550 029 www.optaresolutions.com <http://www.optaresolutions.com> Optare Solutions <http://optarecoolvendor.com> |
|
From: Xose R. S. V. <xr...@op...> - 2013-03-19 13:18:14
|
I will test the RAM and PM projects to see if the patch solves the problem Regards El 19/03/2013 12:55, Flauw, Marc escribió: > > Xose, > > The fact that common_entity only is generated is valid for all > interfaces. I have this problem also when building RAM and it is > show-stopper for RAM as I cannot issue a kit where xsd do not validate. > > I have filled an issue for this problem already. > > > Best regards > > Marc > > *From:*Xose Ramon Sousa Vazquez [mailto:xr...@op...] > *Sent:* Tuesday, March 19, 2013 12:49 PM > *To:* Flauw, Marc > *Cc:* Pierre Gauthier; openoss-devel; Craig Gallen (opennms) > *Subject:* Re: [Openoss-devel] problems with internal model > > Sorry for the delayed response but I am in a production phase in these > two weeks and it is difficult to me to get time. I think that perhaps > the modification related with the definition as dep_ files in the > common model has problems with the internal project that has elements > that usually is taken as dependency and in this case it takes part > from the model. > > I will review the code as soon as possible and then publish the > changes to the repository. > > Regards > El 14/03/2013 8:55, Flauw, Marc escribió: > > Dear all, > > > > I had a look at the Internal model and the attributes of entityBase had a tipAttribute present with notificationDefinition set to true. > > I changed those to NA and the internal model now compiles correctly and has no dependency on the common model. > > > > This is quite strange because I didn't touch the tipAttribute stereotype in my recent changes, so it seems there was some code to prevent looping by ignoring those attributes that has been disabled. > > > > I have committed those changes, but I haven't checked yet if they have any other impact on other specifications, like RAM or PM > > > > I tried also recompiling the Common Model and I still have the same blocking problem that I reported as JOS-46: only common_entity.xsd is generated. The rest of the common files are not. The build id failing at the end as it does not find files, but I don't see any error in the SOAP Gen part. > > > > I am attaching the log of the common model build on my machine. > > > > Best regards > > > > Marc > > -----Original Message----- > > From: Pierre Gauthier [mailto:pga...@tm...] > > Sent: Wednesday, March 13, 2013 7:28 PM > > To: Xose Ramon Sousa Vazquez > > Cc: openoss-devel; Flauw, Marc; Craig Gallen (opennms) > > Subject: Re: [Openoss-devel] problems with internal model > > > > Xi Xose, > > > > Can you look into this and let us know ? > > > > Pierre > > On 2013-03-13, at 2:13 PM, "Craig Gallen (opennms)"<cg...@op...> <mailto:cg...@op...> > > wrote: > > > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > Marc, > > > > I looked at the internal model build problems and the issues appears > > to be in the generated xsd's. > > It appears that the internal model will not build because there are > > circular dependencies on the common model > > > > in the generated entity identifier.xsd, there is an import for the > > common_notifications.xsd which doesn't get generated except in the > > common model which had dependencies on the internal model :) > > > > <xsd:import > > namespace="http://www.tmforum.org/xml/tip/common/notifications" <http://www.tmforum.org/xml/tip/common/notifications> > > schemaLocation="common_notifications.xsd > > > > > > Craig > > -----BEGIN PGP SIGNATURE----- > > Version: GnuPG v2.0.17 (MingW32) > > Comment: Using GnuPG with Thunderbird -http://www.enigmail.net/ > > > > iQEcBAEBAgAGBQJRQMG1AAoJEATefL4tbU2QleUH/R45TYYHwO6Ofy9F4NVVonLN > > Yj1TgmiwIjsqqlsrkKT+IjUjje4eUHlr0zvLrDlyLXV23jdwNTzutsLD6O/LTBKw > > 0Xx1+CBlNBz1Pg9QBD9cEhpYvIlEV/id62lA0xTVbHGpYuywVF3wjGm8OM0Wy7/3 > > FUYCeLXlBr9Cp4MXzD3w7n4jMZL4Ivh7JufyMAzazyPKh0T4lhs7SRBnDeTgIWQB > > gyVVfkbKiVWP78LUlnBWENTZXWBgaEu3eee98SEJK0PruIhOxVg4rOz7OblEBWXb > > DxebdQNj9uy4IBZn4nvzzuahD5FvxfBKhhaVzsAq9lPX1aL2zblLOcml/5IWrmo= > > =Wp32 > > -----END PGP SIGNATURE----- > > > > ---------------------------------------------------------------------- > > -------- Everyone hates slow websites. So do we. > > Make your web apps faster with AppDynamics Download AppDynamics Lite > > for free today: > > http://p.sf.net/sfu/appdyn_d2d_mar > > _______________________________________________ > > Openoss-devel mailing list > > Ope...@li... <mailto:Ope...@li...> > > https://lists.sourceforge.net/lists/listinfo/openoss-devel > > > > > > > > > > ------------------------------------------------------------------------------ > > Everyone hates slow websites. So do we. > > Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: > > http://p.sf.net/sfu/appdyn_d2d_mar > > _______________________________________________ > > Openoss-devel mailing list > > Ope...@li... <mailto:Ope...@li...> > > https://lists.sourceforge.net/lists/listinfo/openoss-devel > > -- > > *Xose Ramon Sousa Vazquez*| Director OSS Technologies, Director I+D > T/ + 34 986 410 091 (ext) 206 | M/ +34 675 550 029 > www.optaresolutions.com > <http://www.optaresolutions.com> > Optare Solutions <http://optarecoolvendor.com> > -- *Xose Ramon Sousa Vazquez* | Director OSS Technologies, Director I+D T/ + 34 986 410 091 (ext) 206 | M/ +34 675 550 029 www.optaresolutions.com <http://www.optaresolutions.com> Optare Solutions <http://optarecoolvendor.com> |
|
From: Xose R. S. V. <xr...@op...> - 2013-03-19 12:18:23
|
Sorry for the delayed response but I am in a production phase in these two weeks and it is difficult to me to get time. I think that perhaps the modification related with the definition as dep_ files in the common model has problems with the internal project that has elements that usually is taken as dependency and in this case it takes part from the model. I will review the code as soon as possible and then publish the changes to the repository. Regards El 14/03/2013 8:55, Flauw, Marc escribió: > Dear all, > > I had a look at the Internal model and the attributes of entityBase had a tipAttribute present with notificationDefinition set to true. > I changed those to NA and the internal model now compiles correctly and has no dependency on the common model. > > This is quite strange because I didn't touch the tipAttribute stereotype in my recent changes, so it seems there was some code to prevent looping by ignoring those attributes that has been disabled. > > I have committed those changes, but I haven't checked yet if they have any other impact on other specifications, like RAM or PM > > I tried also recompiling the Common Model and I still have the same blocking problem that I reported as JOS-46: only common_entity.xsd is generated. The rest of the common files are not. The build id failing at the end as it does not find files, but I don't see any error in the SOAP Gen part. > > I am attaching the log of the common model build on my machine. > > Best regards > > Marc > -----Original Message----- > From: Pierre Gauthier [mailto:pga...@tm...] > Sent: Wednesday, March 13, 2013 7:28 PM > To: Xose Ramon Sousa Vazquez > Cc: openoss-devel; Flauw, Marc; Craig Gallen (opennms) > Subject: Re: [Openoss-devel] problems with internal model > > Xi Xose, > > Can you look into this and let us know ? > > Pierre > On 2013-03-13, at 2:13 PM, "Craig Gallen (opennms)" <cg...@op...> > wrote: > >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> Marc, >> >> I looked at the internal model build problems and the issues appears >> to be in the generated xsd's. >> It appears that the internal model will not build because there are >> circular dependencies on the common model >> >> in the generated entity identifier.xsd, there is an import for the >> common_notifications.xsd which doesn't get generated except in the >> common model which had dependencies on the internal model :) >> >> <xsd:import >> namespace="http://www.tmforum.org/xml/tip/common/notifications" >> schemaLocation="common_notifications.xsd >> >> >> Craig >> -----BEGIN PGP SIGNATURE----- >> Version: GnuPG v2.0.17 (MingW32) >> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ >> >> iQEcBAEBAgAGBQJRQMG1AAoJEATefL4tbU2QleUH/R45TYYHwO6Ofy9F4NVVonLN >> Yj1TgmiwIjsqqlsrkKT+IjUjje4eUHlr0zvLrDlyLXV23jdwNTzutsLD6O/LTBKw >> 0Xx1+CBlNBz1Pg9QBD9cEhpYvIlEV/id62lA0xTVbHGpYuywVF3wjGm8OM0Wy7/3 >> FUYCeLXlBr9Cp4MXzD3w7n4jMZL4Ivh7JufyMAzazyPKh0T4lhs7SRBnDeTgIWQB >> gyVVfkbKiVWP78LUlnBWENTZXWBgaEu3eee98SEJK0PruIhOxVg4rOz7OblEBWXb >> DxebdQNj9uy4IBZn4nvzzuahD5FvxfBKhhaVzsAq9lPX1aL2zblLOcml/5IWrmo= >> =Wp32 >> -----END PGP SIGNATURE----- >> >> ---------------------------------------------------------------------- >> -------- Everyone hates slow websites. So do we. >> Make your web apps faster with AppDynamics Download AppDynamics Lite >> for free today: >> http://p.sf.net/sfu/appdyn_d2d_mar >> _______________________________________________ >> Openoss-devel mailing list >> Ope...@li... >> https://lists.sourceforge.net/lists/listinfo/openoss-devel >> > > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_d2d_mar > _______________________________________________ > Openoss-devel mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openoss-devel -- *Xose Ramon Sousa Vazquez* | Director OSS Technologies, Director I+D T/ + 34 986 410 091 (ext) 206 | M/ +34 675 550 029 www.optaresolutions.com <http://www.optaresolutions.com> Optare Solutions <http://optarecoolvendor.com> |
|
From: Flauw, M. <Mar...@hp...> - 2013-03-14 07:57:38
|
Dear all, I had a look at the Internal model and the attributes of entityBase had a tipAttribute present with notificationDefinition set to true. I changed those to NA and the internal model now compiles correctly and has no dependency on the common model. This is quite strange because I didn't touch the tipAttribute stereotype in my recent changes, so it seems there was some code to prevent looping by ignoring those attributes that has been disabled. I have committed those changes, but I haven't checked yet if they have any other impact on other specifications, like RAM or PM I tried also recompiling the Common Model and I still have the same blocking problem that I reported as JOS-46: only common_entity.xsd is generated. The rest of the common files are not. The build id failing at the end as it does not find files, but I don't see any error in the SOAP Gen part. I am attaching the log of the common model build on my machine. Best regards Marc -----Original Message----- From: Pierre Gauthier [mailto:pga...@tm...] Sent: Wednesday, March 13, 2013 7:28 PM To: Xose Ramon Sousa Vazquez Cc: openoss-devel; Flauw, Marc; Craig Gallen (opennms) Subject: Re: [Openoss-devel] problems with internal model Xi Xose, Can you look into this and let us know ? Pierre On 2013-03-13, at 2:13 PM, "Craig Gallen (opennms)" <cg...@op...> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Marc, > > I looked at the internal model build problems and the issues appears > to be in the generated xsd's. > It appears that the internal model will not build because there are > circular dependencies on the common model > > in the generated entity identifier.xsd, there is an import for the > common_notifications.xsd which doesn't get generated except in the > common model which had dependencies on the internal model :) > > <xsd:import > namespace="http://www.tmforum.org/xml/tip/common/notifications" > schemaLocation="common_notifications.xsd > > > Craig > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.17 (MingW32) > Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ > > iQEcBAEBAgAGBQJRQMG1AAoJEATefL4tbU2QleUH/R45TYYHwO6Ofy9F4NVVonLN > Yj1TgmiwIjsqqlsrkKT+IjUjje4eUHlr0zvLrDlyLXV23jdwNTzutsLD6O/LTBKw > 0Xx1+CBlNBz1Pg9QBD9cEhpYvIlEV/id62lA0xTVbHGpYuywVF3wjGm8OM0Wy7/3 > FUYCeLXlBr9Cp4MXzD3w7n4jMZL4Ivh7JufyMAzazyPKh0T4lhs7SRBnDeTgIWQB > gyVVfkbKiVWP78LUlnBWENTZXWBgaEu3eee98SEJK0PruIhOxVg4rOz7OblEBWXb > DxebdQNj9uy4IBZn4nvzzuahD5FvxfBKhhaVzsAq9lPX1aL2zblLOcml/5IWrmo= > =Wp32 > -----END PGP SIGNATURE----- > > ---------------------------------------------------------------------- > -------- Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics Download AppDynamics Lite > for free today: > http://p.sf.net/sfu/appdyn_d2d_mar > _______________________________________________ > Openoss-devel mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openoss-devel > ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_mar _______________________________________________ Openoss-devel mailing list Ope...@li... https://lists.sourceforge.net/lists/listinfo/openoss-devel |
|
From: Pierre G. <pga...@tm...> - 2013-03-13 18:28:24
|
Xi Xose, Can you look into this and let us know ? Pierre On 2013-03-13, at 2:13 PM, "Craig Gallen (opennms)" <cg...@op...> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Marc, > > I looked at the internal model build problems and the issues appears to > be in the generated xsd's. > It appears that the internal model will not build because there are > circular dependencies on the common model > > in the generated entity identifier.xsd, there is an import for the > common_notifications.xsd which doesn't get generated except in the > common model which had dependencies on the internal model :) > > <xsd:import > namespace="http://www.tmforum.org/xml/tip/common/notifications" > schemaLocation="common_notifications.xsd > > > Craig > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.17 (MingW32) > Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ > > iQEcBAEBAgAGBQJRQMG1AAoJEATefL4tbU2QleUH/R45TYYHwO6Ofy9F4NVVonLN > Yj1TgmiwIjsqqlsrkKT+IjUjje4eUHlr0zvLrDlyLXV23jdwNTzutsLD6O/LTBKw > 0Xx1+CBlNBz1Pg9QBD9cEhpYvIlEV/id62lA0xTVbHGpYuywVF3wjGm8OM0Wy7/3 > FUYCeLXlBr9Cp4MXzD3w7n4jMZL4Ivh7JufyMAzazyPKh0T4lhs7SRBnDeTgIWQB > gyVVfkbKiVWP78LUlnBWENTZXWBgaEu3eee98SEJK0PruIhOxVg4rOz7OblEBWXb > DxebdQNj9uy4IBZn4nvzzuahD5FvxfBKhhaVzsAq9lPX1aL2zblLOcml/5IWrmo= > =Wp32 > -----END PGP SIGNATURE----- > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_d2d_mar > _______________________________________________ > Openoss-devel mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openoss-devel > |
|
From: Craig G. (opennms) <cg...@op...> - 2013-03-13 18:13:27
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Marc, I looked at the internal model build problems and the issues appears to be in the generated xsd's. It appears that the internal model will not build because there are circular dependencies on the common model in the generated entity identifier.xsd, there is an import for the common_notifications.xsd which doesn't get generated except in the common model which had dependencies on the internal model :) <xsd:import namespace="http://www.tmforum.org/xml/tip/common/notifications" schemaLocation="common_notifications.xsd Craig -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJRQMG1AAoJEATefL4tbU2QleUH/R45TYYHwO6Ofy9F4NVVonLN Yj1TgmiwIjsqqlsrkKT+IjUjje4eUHlr0zvLrDlyLXV23jdwNTzutsLD6O/LTBKw 0Xx1+CBlNBz1Pg9QBD9cEhpYvIlEV/id62lA0xTVbHGpYuywVF3wjGm8OM0Wy7/3 FUYCeLXlBr9Cp4MXzD3w7n4jMZL4Ivh7JufyMAzazyPKh0T4lhs7SRBnDeTgIWQB gyVVfkbKiVWP78LUlnBWENTZXWBgaEu3eee98SEJK0PruIhOxVg4rOz7OblEBWXb DxebdQNj9uy4IBZn4nvzzuahD5FvxfBKhhaVzsAq9lPX1aL2zblLOcml/5IWrmo= =Wp32 -----END PGP SIGNATURE----- |
|
From: <sit...@nm...> - 2013-03-13 09:50:25
|
Apologies, missed output, attaching herewith. Sitaraman ---------------------------- Original Message ---------------------------- Subject: [Fwd: RE: Importing SID] From: sit...@nm... Date: Wed, March 13, 2013 3:12 pm To: ope...@li... -------------------------------------------------------------------------- Hi, Another issue i need help with. Thanks Sitaraman ---------------------------- Original Message ---------------------------- Subject: RE: Importing SID From: "Flauw, Marc" <Mar...@hp...> Date: Wed, March 13, 2013 12:14 pm To: "sit...@nm..." <sit...@nm...> -------------------------------------------------------------------------- Yes, please -----Original Message----- From: sit...@nm... [mailto:sit...@nm...] Sent: Wednesday, March 13, 2013 7:26 AM To: Flauw, Marc Subject: RE: Importing SID Hi Marc, Getting erros with the Common Model too output attached....post to OSS list ? Sitaraman > Hi Sitaraman, > > The error is in SOAP Impl generator. Likely because it has not been > aligned with the latest changes in Internal model. > > Post it to the openoss list. > > If you have done the common model after, then it should be sufficient > for you to operate. > > Best regards > > Marc > > -----Original Message----- > From: sit...@nm... [mailto:sit...@nm...] > Sent: Saturday, March 09, 2013 1:02 PM > To: Flauw, Marc > Subject: RE: Importing SID > > Hi Marc, > With the internal model, i get error during mvn clean install. > Output and Tigerstipe-build.properties is attached. > Since this project you mentioned was from your folder i though i will > ping you first, if you want me to post it in the newsgroup do let me > know. > Thanks Marc, i owe you a Beer....:) > Sitaraman > >> I forgot to mention: >> For the generators, once checked out, >> - undeploy the old one: Tigerstripe menu, Deployed Generators, then >> select the generator and rigt-click Undeploy >> - then Open the ts-plugin.xml then do a "package and deploy this >> generator" (blue link under Testing) >> >> -----Original Message----- >> From: Flauw, Marc >> Sent: Tuesday, March 05, 2013 10:46 AM >> To: 'sit...@nm...' >> Subject: RE: Importing SID >> >> Hi Sitaraman >> >> For updating the generators, I would recommend a separate workspace >> where all the generators can be put. >> Then check them out one by one. >> The SOAP one is at: >> https://openoss.svn.sourceforge.net/svnroot/openoss/tip/framework/TIP >> _ Soap_Generator/trunk/TIP_Soap_Generator >> replace SOAP by Doc for the Doc Generator. >> The implementation ones are under platform instead of framework. >> >> For common and internal models, create new workspaces for them. >> Pick them from SVN: >> - >> https://openoss.svn.sourceforge.net/svnroot/openoss/tip/framework/TIP >> _ >> Generator_Internal_Model/trunk >> - >> https://openoss.svn.sourceforge.net/svnroot/openoss/tip/framework/TIP >> _ >> Common_Model/trunk >> >> And then build them like a standard interface: env variables, mvn >> eclipse:eclipse, mvn clean install Build internal first and only >> then build common. >> >> Then you should be all set. >> >> Best regards >> >> Marc >> >> -----Original Message----- >> From: sit...@nm... [mailto:sit...@nm...] >> Sent: Tuesday, March 05, 2013 10:35 AM >> To: Flauw, Marc >> Subject: RE: Importing SID >> >> My apologies Marc for bothering you on this.. >> Could you give the link where the procedure and sitenames are available. >> Thanks much.. >> Sitaaman >>> Hi Sitaraman, >>> >>> Known issue (JOS-6) fixed in trunk. >>> You will need to: >>> - get latest version of SOAP Gen from trunk >>> - rebuild Internal and common model (in this order) >>> >>> Best regards >>> >>> Marc >>> >>> -----Original Message----- >>> From: sit...@nm... [mailto:sit...@nm...] >>> Sent: Tuesday, March 05, 2013 9:56 AM >>> To: Flauw, Marc >>> Subject: RE: Importing SID >>> >>> Hi Marc, >>> I am trying to generate Texo JPA annotations and when i do that i >>> get the following error... >>> >>> Click the details button for more information, and check the Error >>> Log view for any exceptions....is it an error that can be fixed at >>> TMF end... >>> Thanks >>> Sitaraman >>> java.lang.IllegalStateException: >>> file:/D:/Users/Sitaraman/EclipseVersions/EclipseForEMF/workspace/Tex >>> o >>> T >>> est1/Model/Interface_Implementation_Specifications/WSDL/sid_enterpri >>> s >>> e >>> _risk_sec_vuln.xsd >>> (254:17):XSD: Type reference >>> 'http://www.tmforum.org/xml/tip/internal/primitives#ArrayOfAnyURI' >>> is unresolved >>> file:/D:/Users/Sitaraman/EclipseVersions/EclipseForEMF/workspace/Tex >>> o >>> T >>> est1/Model/Interface_Implementation_Specifications/WSDL/sid_enterpri >>> s >>> e >>> _risk_sec_threat.xsd >>> (279:17):XSD: Type reference >>> 'http://www.tmforum.org/xml/tip/internal/primitives#ArrayOfAnyURI' >>> is unresolved >>> file:/D:/Users/Sitaraman/EclipseVersions/EclipseForEMF/workspace/Tex >>> o >>> T >>> est1/Model/Interface_Implementation_Specifications/WSDL/sid_enterpri >>> s >>> e >>> _risk_sec_threat.xsd >>> (480:17):XSD: Type reference >>> 'http://www.tmforum.org/xml/tip/internal/primitives#ArrayOfAnyURI' >>> is unresolved >>>> Hi Marc, >>>> These look fine....the one in the link i mentioned has only a >>>> limited number of XSDs it seems to be a competely different version >>>> that what you just forwarded. Is the one you forwarded availble for >>>> the community in general then...just to avoid having using your >>>> time for these issues that are alreay been fixed by you.... >>>> Thanks >>>> Sitaraman >>>>> Hi Sitaraman, >>>>> >>>>> Here is the one I have in my project directory. >>>>> Is it showing the same errors? >>>>> >>>>> Best regards >>>>> >>>>> Marc >>>>> >>>>> -----Original Message----- >>>>> From: sit...@nm... [mailto:sit...@nm...] >>>>> Sent: Monday, March 04, 2013 2:57 PM >>>>> To: Flauw, Marc >>>>> Subject: RE: Importing SID >>>>> >>>>> A couple of them are as follows (In SID BusinessView Service) I >>>>> just moused over the red marks in eclipse and cut and paste...if >>>>> there is a way to list all the errors in a given file please let >>>>> me know i will send across all of them.. >>>>> The following are all the errors in SIDBusinessViewSErvice..... >>>>> Thanks for prompt guidance and willingness to look into it Marc, >>>>> much appreciated. >>>>> Sitaraman >>>>> >>>>> annotations found at this line: >>>>> - sch-props-correct.2: A schema cannot contain two global >>>>> components with the same name; this schema contains two >>>>> occurrences of 'http://www.tmforum.org/Frameworx/SID/ >>>>> Business/12.0/Service,Customer'. >>>>> - Start tag of element <xs:complexType> >>>>> >>>>> >>>>> sch-props-correct.2: A schema cannot contain two global components >>>>> with the same name; this schema contains two occurrences of >>>>> 'http://www.tmforum.org/Frameworx/SID/Business/12.0/Service,Equipment'. >>>>> >>>>> Multiple annotations found at this line: >>>>> - Start tag of element <xs:complexType> >>>>> - sch-props-correct.2: A schema cannot contain two global >>>>> components with the same name; this schema contains two >>>>> occurrences of 'http://www.tmforum.org/Frameworx/SID/ >>>>> Business/12.0/Service,Resource'. >>>>> >>>>> Multiple annotations found at this line: >>>>> - sch-props-correct.2: A schema cannot contain two global >>>>> components with the same name; this schema contains two >>>>> occurrences of 'http://www.tmforum.org/Frameworx/SID/Business/12.0/ >>>>> Service,State'. >>>>> - Start tag of element <xs:simpleType> >>>>> >>>>>> Hi Sitaraman, >>>>>> >>>>>> It should be the right place. I did fix a number of errors. >>>>>> Which ones do you have? >>>>>> >>>>>> Best regards >>>>>> >>>>>> Marc >>>>>> >>>>>> -----Original Message----- >>>>>> From: sit...@nm... [mailto:sit...@nm...] >>>>>> Sent: Monday, March 04, 2013 2:36 PM >>>>>> To: Flauw, Marc >>>>>> Subject: RE: Importing SID >>>>>> >>>>>> Hi Marc, >>>>>> I took the 12.5 XSDs from >>>>>> http://www.tmforum.org/DownloadRelease125/14240/home.html Is this >>>>>> the correct place....for eclipse throws errors on the XSDs when i >>>>>> open them... >>>>>> Sitaraman >>>>>>> Hi Sitaraman, >>>>>>> >>>>>>> I didn't commit the SID version I used as the only master is the >>>>>>> SID. >>>>>>> >>>>>>> For UML pick a SID branch and then generate For xsd and wsdl, >>>>>>> those were published with SID 12.5 >>>>>>> >>>>>>> Best regards >>>>>>> >>>>>>> Marc >>>>>>> >>>>>>> -----Original Message----- >>>>>>> From: sit...@nm... [mailto:sit...@nm...] >>>>>>> Sent: Monday, March 04, 2013 12:38 PM >>>>>>> To: Flauw, Marc >>>>>>> Subject: Importing SID >>>>>>> >>>>>>> Hi Marc, >>>>>>> You had earlier fixed several issues in the SID (duplicates >>>>>>> being one of them). Could you let me know where i should take >>>>>>> the UML, XSDs and WSDLs from to try and import them into a >>>>>>> project created using JOSIF generators... >>>>>>> Thanks >>>>>>> Sitaraman >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> This message has been scanned for viruses and dangerous content >>>>>>> by MailScanner, and is believed to be clean. >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> This message has been scanned for viruses and dangerous content >>>>>>> by MailScanner, and is believed to be clean. >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> This message has been scanned for viruses and dangerous content >>>>>> by MailScanner, and is believed to be clean. >>>>>> >>>>>> >>>>>> -- >>>>>> This message has been scanned for viruses and dangerous content >>>>>> by MailScanner, and is believed to be clean. >>>>>> >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> This message has been scanned for viruses and dangerous content by >>>>> MailScanner, and is believed to be clean. >>>>> >>>>> >>>>> -- >>>>> This message has been scanned for viruses and dangerous content by >>>>> MailScanner, and is believed to be clean. >>>>> >>>>> >>>> >>>> >>> >>> >>> >>> -- >>> This message has been scanned for viruses and dangerous content by >>> MailScanner, and is believed to be clean. >>> >>> >>> -- >>> This message has been scanned for viruses and dangerous content by >>> MailScanner, and is believed to be clean. >>> >>> >> >> >> >> -- >> This message has been scanned for viruses and dangerous content by >> MailScanner, and is believed to be clean. >> >> >> -- >> This message has been scanned for viruses and dangerous content by >> MailScanner, and is believed to be clean. >> >> > > -- > This message has been scanned for viruses and dangerous content by > MailScanner, and is believed to be clean. > > > -- > This message has been scanned for viruses and dangerous content by > MailScanner, and is believed to be clean. > > -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. |
|
From: <sit...@nm...> - 2013-03-13 09:46:42
|
Hi, Another issue i need help with. Thanks Sitaraman ---------------------------- Original Message ---------------------------- Subject: RE: Importing SID From: "Flauw, Marc" <Mar...@hp...> Date: Wed, March 13, 2013 12:14 pm To: "sit...@nm..." <sit...@nm...> -------------------------------------------------------------------------- Yes, please -----Original Message----- From: sit...@nm... [mailto:sit...@nm...] Sent: Wednesday, March 13, 2013 7:26 AM To: Flauw, Marc Subject: RE: Importing SID Hi Marc, Getting erros with the Common Model too output attached....post to OSS list ? Sitaraman > Hi Sitaraman, > > The error is in SOAP Impl generator. Likely because it has not been > aligned with the latest changes in Internal model. > > Post it to the openoss list. > > If you have done the common model after, then it should be sufficient > for you to operate. > > Best regards > > Marc > > -----Original Message----- > From: sit...@nm... [mailto:sit...@nm...] > Sent: Saturday, March 09, 2013 1:02 PM > To: Flauw, Marc > Subject: RE: Importing SID > > Hi Marc, > With the internal model, i get error during mvn clean install. > Output and Tigerstipe-build.properties is attached. > Since this project you mentioned was from your folder i though i will > ping you first, if you want me to post it in the newsgroup do let me > know. > Thanks Marc, i owe you a Beer....:) > Sitaraman > >> I forgot to mention: >> For the generators, once checked out, >> - undeploy the old one: Tigerstripe menu, Deployed Generators, then >> select the generator and rigt-click Undeploy >> - then Open the ts-plugin.xml then do a "package and deploy this >> generator" (blue link under Testing) >> >> -----Original Message----- >> From: Flauw, Marc >> Sent: Tuesday, March 05, 2013 10:46 AM >> To: 'sit...@nm...' >> Subject: RE: Importing SID >> >> Hi Sitaraman >> >> For updating the generators, I would recommend a separate workspace >> where all the generators can be put. >> Then check them out one by one. >> The SOAP one is at: >> https://openoss.svn.sourceforge.net/svnroot/openoss/tip/framework/TIP >> _ Soap_Generator/trunk/TIP_Soap_Generator >> replace SOAP by Doc for the Doc Generator. >> The implementation ones are under platform instead of framework. >> >> For common and internal models, create new workspaces for them. >> Pick them from SVN: >> - >> https://openoss.svn.sourceforge.net/svnroot/openoss/tip/framework/TIP >> _ >> Generator_Internal_Model/trunk >> - >> https://openoss.svn.sourceforge.net/svnroot/openoss/tip/framework/TIP >> _ >> Common_Model/trunk >> >> And then build them like a standard interface: env variables, mvn >> eclipse:eclipse, mvn clean install Build internal first and only >> then build common. >> >> Then you should be all set. >> >> Best regards >> >> Marc >> >> -----Original Message----- >> From: sit...@nm... [mailto:sit...@nm...] >> Sent: Tuesday, March 05, 2013 10:35 AM >> To: Flauw, Marc >> Subject: RE: Importing SID >> >> My apologies Marc for bothering you on this.. >> Could you give the link where the procedure and sitenames are available. >> Thanks much.. >> Sitaaman >>> Hi Sitaraman, >>> >>> Known issue (JOS-6) fixed in trunk. >>> You will need to: >>> - get latest version of SOAP Gen from trunk >>> - rebuild Internal and common model (in this order) >>> >>> Best regards >>> >>> Marc >>> >>> -----Original Message----- >>> From: sit...@nm... [mailto:sit...@nm...] >>> Sent: Tuesday, March 05, 2013 9:56 AM >>> To: Flauw, Marc >>> Subject: RE: Importing SID >>> >>> Hi Marc, >>> I am trying to generate Texo JPA annotations and when i do that i >>> get the following error... >>> >>> Click the details button for more information, and check the Error >>> Log view for any exceptions....is it an error that can be fixed at >>> TMF end... >>> Thanks >>> Sitaraman >>> java.lang.IllegalStateException: >>> file:/D:/Users/Sitaraman/EclipseVersions/EclipseForEMF/workspace/Tex >>> o >>> T >>> est1/Model/Interface_Implementation_Specifications/WSDL/sid_enterpri >>> s >>> e >>> _risk_sec_vuln.xsd >>> (254:17):XSD: Type reference >>> 'http://www.tmforum.org/xml/tip/internal/primitives#ArrayOfAnyURI' >>> is unresolved >>> file:/D:/Users/Sitaraman/EclipseVersions/EclipseForEMF/workspace/Tex >>> o >>> T >>> est1/Model/Interface_Implementation_Specifications/WSDL/sid_enterpri >>> s >>> e >>> _risk_sec_threat.xsd >>> (279:17):XSD: Type reference >>> 'http://www.tmforum.org/xml/tip/internal/primitives#ArrayOfAnyURI' >>> is unresolved >>> file:/D:/Users/Sitaraman/EclipseVersions/EclipseForEMF/workspace/Tex >>> o >>> T >>> est1/Model/Interface_Implementation_Specifications/WSDL/sid_enterpri >>> s >>> e >>> _risk_sec_threat.xsd >>> (480:17):XSD: Type reference >>> 'http://www.tmforum.org/xml/tip/internal/primitives#ArrayOfAnyURI' >>> is unresolved >>>> Hi Marc, >>>> These look fine....the one in the link i mentioned has only a >>>> limited number of XSDs it seems to be a competely different version >>>> that what you just forwarded. Is the one you forwarded availble for >>>> the community in general then...just to avoid having using your >>>> time for these issues that are alreay been fixed by you.... >>>> Thanks >>>> Sitaraman >>>>> Hi Sitaraman, >>>>> >>>>> Here is the one I have in my project directory. >>>>> Is it showing the same errors? >>>>> >>>>> Best regards >>>>> >>>>> Marc >>>>> >>>>> -----Original Message----- >>>>> From: sit...@nm... [mailto:sit...@nm...] >>>>> Sent: Monday, March 04, 2013 2:57 PM >>>>> To: Flauw, Marc >>>>> Subject: RE: Importing SID >>>>> >>>>> A couple of them are as follows (In SID BusinessView Service) I >>>>> just moused over the red marks in eclipse and cut and paste...if >>>>> there is a way to list all the errors in a given file please let >>>>> me know i will send across all of them.. >>>>> The following are all the errors in SIDBusinessViewSErvice..... >>>>> Thanks for prompt guidance and willingness to look into it Marc, >>>>> much appreciated. >>>>> Sitaraman >>>>> >>>>> annotations found at this line: >>>>> - sch-props-correct.2: A schema cannot contain two global >>>>> components with the same name; this schema contains two >>>>> occurrences of 'http://www.tmforum.org/Frameworx/SID/ >>>>> Business/12.0/Service,Customer'. >>>>> - Start tag of element <xs:complexType> >>>>> >>>>> >>>>> sch-props-correct.2: A schema cannot contain two global components >>>>> with the same name; this schema contains two occurrences of >>>>> 'http://www.tmforum.org/Frameworx/SID/Business/12.0/Service,Equipment'. >>>>> >>>>> Multiple annotations found at this line: >>>>> - Start tag of element <xs:complexType> >>>>> - sch-props-correct.2: A schema cannot contain two global >>>>> components with the same name; this schema contains two >>>>> occurrences of 'http://www.tmforum.org/Frameworx/SID/ >>>>> Business/12.0/Service,Resource'. >>>>> >>>>> Multiple annotations found at this line: >>>>> - sch-props-correct.2: A schema cannot contain two global >>>>> components with the same name; this schema contains two >>>>> occurrences of 'http://www.tmforum.org/Frameworx/SID/Business/12.0/ >>>>> Service,State'. >>>>> - Start tag of element <xs:simpleType> >>>>> >>>>>> Hi Sitaraman, >>>>>> >>>>>> It should be the right place. I did fix a number of errors. >>>>>> Which ones do you have? >>>>>> >>>>>> Best regards >>>>>> >>>>>> Marc >>>>>> >>>>>> -----Original Message----- >>>>>> From: sit...@nm... [mailto:sit...@nm...] >>>>>> Sent: Monday, March 04, 2013 2:36 PM >>>>>> To: Flauw, Marc >>>>>> Subject: RE: Importing SID >>>>>> >>>>>> Hi Marc, >>>>>> I took the 12.5 XSDs from >>>>>> http://www.tmforum.org/DownloadRelease125/14240/home.html Is this >>>>>> the correct place....for eclipse throws errors on the XSDs when i >>>>>> open them... >>>>>> Sitaraman >>>>>>> Hi Sitaraman, >>>>>>> >>>>>>> I didn't commit the SID version I used as the only master is the >>>>>>> SID. >>>>>>> >>>>>>> For UML pick a SID branch and then generate For xsd and wsdl, >>>>>>> those were published with SID 12.5 >>>>>>> >>>>>>> Best regards >>>>>>> >>>>>>> Marc >>>>>>> >>>>>>> -----Original Message----- >>>>>>> From: sit...@nm... [mailto:sit...@nm...] >>>>>>> Sent: Monday, March 04, 2013 12:38 PM >>>>>>> To: Flauw, Marc >>>>>>> Subject: Importing SID >>>>>>> >>>>>>> Hi Marc, >>>>>>> You had earlier fixed several issues in the SID (duplicates >>>>>>> being one of them). Could you let me know where i should take >>>>>>> the UML, XSDs and WSDLs from to try and import them into a >>>>>>> project created using JOSIF generators... >>>>>>> Thanks >>>>>>> Sitaraman >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> This message has been scanned for viruses and dangerous content >>>>>>> by MailScanner, and is believed to be clean. >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> This message has been scanned for viruses and dangerous content >>>>>>> by MailScanner, and is believed to be clean. >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> This message has been scanned for viruses and dangerous content >>>>>> by MailScanner, and is believed to be clean. >>>>>> >>>>>> >>>>>> -- >>>>>> This message has been scanned for viruses and dangerous content >>>>>> by MailScanner, and is believed to be clean. >>>>>> >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> This message has been scanned for viruses and dangerous content by >>>>> MailScanner, and is believed to be clean. >>>>> >>>>> >>>>> -- >>>>> This message has been scanned for viruses and dangerous content by >>>>> MailScanner, and is believed to be clean. >>>>> >>>>> >>>> >>>> >>> >>> >>> >>> -- >>> This message has been scanned for viruses and dangerous content by >>> MailScanner, and is believed to be clean. >>> >>> >>> -- >>> This message has been scanned for viruses and dangerous content by >>> MailScanner, and is believed to be clean. >>> >>> >> >> >> >> -- >> This message has been scanned for viruses and dangerous content by >> MailScanner, and is believed to be clean. >> >> >> -- >> This message has been scanned for viruses and dangerous content by >> MailScanner, and is believed to be clean. >> >> > > -- > This message has been scanned for viruses and dangerous content by > MailScanner, and is believed to be clean. > > > -- > This message has been scanned for viruses and dangerous content by > MailScanner, and is believed to be clean. > > -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. |
|
From: Craig G. (opennms) <cg...@op...> - 2013-03-12 13:51:14
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, video intros to most things are at bottom of this page https://openoss.atlassian.net/wiki/display/JOSIFDOC1/Release+Plan+1.1.2 in section OSIF Developer On-Ramp Training Schedule Craig On 12/03/2013 12:25, Pierre Gauthier wrote: > Hi Sita, > > Please ask Craig. > > Pierre > On 2013-03-12, at 8:13 AM, sit...@nm... wrote: > >> Hi, >> Would appreciate any pointers to getting familiar with the SOAP >> Generator... >> Thanks >> Sitaraman >> >> >> -- >> This message has been scanned for viruses and >> dangerous content by MailScanner, and is >> believed to be clean. >> >> >> ------------------------------------------------------------------------------ >> Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester >> Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the >> endpoint security space. For insight on selecting the right partner to >> tackle endpoint security challenges, access the full report. >> http://p.sf.net/sfu/symantec-dev2dev >> _______________________________________________ >> Openoss-devel mailing list >> Ope...@li... >> https://lists.sourceforge.net/lists/listinfo/openoss-devel >> > > > > ------------------------------------------------------------------------------ > Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester > Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the > endpoint security space. For insight on selecting the right partner to > tackle endpoint security challenges, access the full report. > http://p.sf.net/sfu/symantec-dev2dev > _______________________________________________ > Openoss-devel mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openoss-devel > -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJRPzLFAAoJEATefL4tbU2Qs6kH/RMuh3cyw1qExwR3qVL3LjL8 J29MT/XePgY8tJtVpEZD4DOREH4J2TxYBTH4wgJXrGoC3e0DtBY2YePJG88ExjN+ e1nVbgQFdQ2yLiGhC7/uaK5FIHACsIFARInwMnZl4F4x7ZYMbK7ayX5/7RNjaofd c9jHQoIKnA9RCnQm7sFeJLYi4AJdoAC9tN3hGhG+l2px/6lM6arfrcPWF0VIS4JF tovUmRl621XpSQKisC1jntRncrD6kal6S+VkYSou4zLIvQSE7IyFfLwT9BFFGFMz q5Wv63gUA9E42eXj3sKs6wyZ+V5960+Cnffvw7lTpPMXqXIJ0LaEd7MYiL60BIQ= =rdIh -----END PGP SIGNATURE----- |
|
From: Pierre G. <pga...@tm...> - 2013-03-12 12:26:06
|
Hi Sita, Please ask Craig. Pierre On 2013-03-12, at 8:13 AM, sit...@nm... wrote: > Hi, > Would appreciate any pointers to getting familiar with the SOAP > Generator... > Thanks > Sitaraman > > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > > > ------------------------------------------------------------------------------ > Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester > Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the > endpoint security space. For insight on selecting the right partner to > tackle endpoint security challenges, access the full report. > http://p.sf.net/sfu/symantec-dev2dev > _______________________________________________ > Openoss-devel mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openoss-devel > |
|
From: pierre g. <pie...@os...> - 2013-03-12 12:25:13
|
Thanks Sita. Can your take a look at SOA Impl Generator code and try to fix it ? Pierre On 2013-03-12, at 7:58 AM, ope...@li... wrote: > Send Openoss-devel mailing list submissions to > ope...@li... > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.sourceforge.net/lists/listinfo/openoss-devel > or, via email, send a message with subject or body 'help' to > ope...@li... > > You can reach the person managing the list at > ope...@li... > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Openoss-devel digest..." > > > Today's Topics: > > 1. SOAPImpl Generator Issue.. (sit...@nm...) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 12 Mar 2013 16:59:01 +0530 (IST) > From: sit...@nm... > Subject: [Openoss-devel] SOAPImpl Generator Issue.. > To: ope...@li... > Message-ID: > <529...@ww...> > Content-Type: text/plain; charset="iso-8859-1" > > Hi, > Marc has been helping me with the following issue...Marc suggests i post > it here...any help is appreciated. > Sitaraman > > Hi Sitaraman, > > The error is in SOAP Impl generator. Likely because it has not been > aligned with the > latest changes in Internal model. > > Post it to the openoss list. > > If you have done the common model after, then it should be sufficient for > you to > operate. > > Best regards > > Marc > > -----Original Message----- > From: sit...@nm... [mailto:sit...@nm...] > Sent: Saturday, March 09, 2013 1:02 PM > To: Flauw, Marc > Subject: RE: Importing SID > > Hi Marc, > With the internal model, i get error during mvn clean install. > Output and Tigerstipe-build.properties is attached. > Since this project you mentioned was from your folder i though i will > ping you > first, if you want me to post it in the newsgroup do let me know. > Thanks Marc, i owe you a Beer....:) > Sitaraman > >> I forgot to mention: >> For the generators, once checked out, >> - undeploy the old one: Tigerstripe menu, Deployed Generators, then >> select the generator and rigt-click Undeploy >> - then Open the ts-plugin.xml then do a "package and deploy this >> generator" (blue link under Testing) >> >> -----Original Message----- >> From: Flauw, Marc >> Sent: Tuesday, March 05, 2013 10:46 AM >> To: 'sit...@nm...' >> Subject: RE: Importing SID >> >> Hi Sitaraman >> >> For updating the generators, I would recommend a separate workspace >> where all the generators can be put. >> Then check them out one by one. >> The SOAP one is at: >> https://openoss.svn.sourceforge.net/svnroot/openoss/tip/framework/TIP_ >> Soap_Generator/trunk/TIP_Soap_Generator >> replace SOAP by Doc for the Doc Generator. >> The implementation ones are under platform instead of framework. >> >> For common and internal models, create new workspaces for them. >> Pick them from SVN: >> - >> https://openoss.svn.sourceforge.net/svnroot/openoss/tip/framework/TIP_ >> Generator_Internal_Model/trunk >> - >> https://openoss.svn.sourceforge.net/svnroot/openoss/tip/framework/TIP_ >> Common_Model/trunk >> >> And then build them like a standard interface: env variables, mvn >> eclipse:eclipse, mvn clean install Build internal first and only then >> build common. >> >> Then you should be all set. >> >> Best regards >> >> Marc >> >> -----Original Message----- >> From: sit...@nm... [mailto:sit...@nm...] >> Sent: Tuesday, March 05, 2013 10:35 AM >> To: Flauw, Marc >> Subject: RE: Importing SID >> >> My apologies Marc for bothering you on this.. >> Could you give the link where the procedure and sitenames are available. >> Thanks much.. >> Sitaaman >>> Hi Sitaraman, >>> >>> Known issue (JOS-6) fixed in trunk. >>> You will need to: >>> - get latest version of SOAP Gen from trunk >>> - rebuild Internal and common model (in this order) >>> >>> Best regards >>> >>> Marc >>> >>> -----Original Message----- >>> From: sit...@nm... [mailto:sit...@nm...] >>> Sent: Tuesday, March 05, 2013 9:56 AM >>> To: Flauw, Marc >>> Subject: RE: Importing SID >>> >>> Hi Marc, >>> I am trying to generate Texo JPA annotations and when i do that i >>> get the following error... >>> >>> Click the details button for more information, and check the Error >>> Log view for any exceptions....is it an error that can be fixed at >>> TMF end... >>> Thanks >>> Sitaraman >>> java.lang.IllegalStateException: >>> file:/D:/Users/Sitaraman/EclipseVersions/EclipseForEMF/workspace/Texo >>> T >>> est1/Model/Interface_Implementation_Specifications/WSDL/sid_enterpris >>> e >>> _risk_sec_vuln.xsd >>> (254:17):XSD: Type reference >>> 'http://www.tmforum.org/xml/tip/internal/primitives#ArrayOfAnyURI' is >>> unresolved >>> file:/D:/Users/Sitaraman/EclipseVersions/EclipseForEMF/workspace/Texo >>> T >>> est1/Model/Interface_Implementation_Specifications/WSDL/sid_enterpris >>> e >>> _risk_sec_threat.xsd >>> (279:17):XSD: Type reference >>> 'http://www.tmforum.org/xml/tip/internal/primitives#ArrayOfAnyURI' is >>> unresolved >>> file:/D:/Users/Sitaraman/EclipseVersions/EclipseForEMF/workspace/Texo >>> T >>> est1/Model/Interface_Implementation_Specifications/WSDL/sid_enterpris >>> e >>> _risk_sec_threat.xsd >>> (480:17):XSD: Type reference >>> 'http://www.tmforum.org/xml/tip/internal/primitives#ArrayOfAnyURI' is >>> unresolved >>>> Hi Marc, >>>> These look fine....the one in the link i mentioned has only a >>>> limited number of XSDs it seems to be a competely different version >>>> that what you just forwarded. Is the one you forwarded availble for >>>> the community in general then...just to avoid having using your time >>>> for these issues that are alreay been fixed by you.... >>>> Thanks >>>> Sitaraman >>>>> Hi Sitaraman, >>>>> >>>>> Here is the one I have in my project directory. >>>>> Is it showing the same errors? >>>>> >>>>> Best regards >>>>> >>>>> Marc >>>>> >>>>> -----Original Message----- >>>>> From: sit...@nm... [mailto:sit...@nm...] >>>>> Sent: Monday, March 04, 2013 2:57 PM >>>>> To: Flauw, Marc >>>>> Subject: RE: Importing SID >>>>> >>>>> A couple of them are as follows (In SID BusinessView Service) I >>>>> just moused over the red marks in eclipse and cut and paste...if >>>>> there is a way to list all the errors in a given file please let me >>>>> know i will send across all of them.. >>>>> The following are all the errors in SIDBusinessViewSErvice..... >>>>> Thanks for prompt guidance and willingness to look into it Marc, >>>>> much appreciated. >>>>> Sitaraman >>>>> >>>>> annotations found at this line: >>>>> - sch-props-correct.2: A schema cannot contain two global >>>>> components with the same name; this schema contains two occurrences >>>>> of 'http://www.tmforum.org/Frameworx/SID/ >>>>> Business/12.0/Service,Customer'. >>>>> - Start tag of element <xs:complexType> >>>>> >>>>> >>>>> sch-props-correct.2: A schema cannot contain two global components >>>>> with the same name; this schema contains two occurrences of >>>>> 'http://www.tmforum.org/Frameworx/SID/Business/12.0/Service,Equipment'. >>>>> >>>>> Multiple annotations found at this line: >>>>> - Start tag of element <xs:complexType> >>>>> - sch-props-correct.2: A schema cannot contain two global >>>>> components with the same name; this schema contains two occurrences >>>>> of 'http://www.tmforum.org/Frameworx/SID/ >>>>> Business/12.0/Service,Resource'. >>>>> >>>>> Multiple annotations found at this line: >>>>> - sch-props-correct.2: A schema cannot contain two global >>>>> components with the same name; this schema contains two occurrences >>>>> of 'http://www.tmforum.org/Frameworx/SID/Business/12.0/ >>>>> Service,State'. >>>>> - Start tag of element <xs:simpleType> >>>>> >>>>>> Hi Sitaraman, >>>>>> >>>>>> It should be the right place. I did fix a number of errors. >>>>>> Which ones do you have? >>>>>> >>>>>> Best regards >>>>>> >>>>>> Marc >>>>>> >>>>>> -----Original Message----- >>>>>> From: sit...@nm... [mailto:sit...@nm...] >>>>>> Sent: Monday, March 04, 2013 2:36 PM >>>>>> To: Flauw, Marc >>>>>> Subject: RE: Importing SID >>>>>> >>>>>> Hi Marc, >>>>>> I took the 12.5 XSDs from >>>>>> http://www.tmforum.org/DownloadRelease125/14240/home.html Is this >>>>>> the correct place....for eclipse throws errors on the XSDs when i >>>>>> open them... >>>>>> Sitaraman >>>>>>> Hi Sitaraman, >>>>>>> >>>>>>> I didn't commit the SID version I used as the only master is the >>>>>>> SID. >>>>>>> >>>>>>> For UML pick a SID branch and then generate For xsd and wsdl, >>>>>>> those were published with SID 12.5 >>>>>>> >>>>>>> Best regards >>>>>>> >>>>>>> Marc >>>>>>> >>>>>>> -----Original Message----- >>>>>>> From: sit...@nm... [mailto:sit...@nm...] >>>>>>> Sent: Monday, March 04, 2013 12:38 PM >>>>>>> To: Flauw, Marc >>>>>>> Subject: Importing SID >>>>>>> >>>>>>> Hi Marc, >>>>>>> You had earlier fixed several issues in the SID (duplicates >>>>>>> being one of them). Could you let me know where i should take the >>>>>>> UML, XSDs and WSDLs from to try and import them into a project >>>>>>> created using JOSIF generators... >>>>>>> Thanks >>>>>>> Sitaraman >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> This message has been scanned for viruses and dangerous content >>>>>>> by MailScanner, and is believed to be clean. >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> This message has been scanned for viruses and dangerous content >>>>>>> by MailScanner, and is believed to be clean. >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> This message has been scanned for viruses and dangerous content by >>>>>> MailScanner, and is believed to be clean. >>>>>> >>>>>> >>>>>> -- >>>>>> This message has been scanned for viruses and dangerous content by >>>>>> MailScanner, and is believed to be clean. >>>>>> >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> This message has been scanned for viruses and dangerous content by >>>>> MailScanner, and is believed to be clean. >>>>> >>>>> >>>>> -- >>>>> This message has been scanned for viruses and dangerous content by >>>>> MailScanner, and is believed to be clean. >>>>> >>>>> >>>> >>>> >>> >>> >>> >>> -- >>> This message has been scanned for viruses and dangerous content by >>> MailScanner, and is believed to be clean. >>> >>> >>> -- >>> This message has been scanned for viruses and dangerous content by >>> MailScanner, and is believed to be clean. >>> >>> >> >> >> >> -- >> This message has been scanned for viruses and dangerous content by >> MailScanner, and is believed to be clean. >> >> >> -- >> This message has been scanned for viruses and dangerous content by >> MailScanner, and is believed to be clean. >> >> > > -- > This message has been scanned for viruses and dangerous content by > MailScanner, and > is believed to be clean. > > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > > > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > > -------------- next part -------------- > An embedded and charset-unspecified text was scrubbed... > Name: output > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: tigerstripe-build.properties > Type: application/octet-stream > Size: 944 bytes > Desc: not available > > ------------------------------ > > ------------------------------------------------------------------------------ > Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester > Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the > endpoint security space. For insight on selecting the right partner to > tackle endpoint security challenges, access the full report. > http://p.sf.net/sfu/symantec-dev2dev > > ------------------------------ > > _______________________________________________ > Openoss-devel mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openoss-devel > > > End of Openoss-devel Digest, Vol 45, Issue 2 > ******************************************** |
|
From: <sit...@nm...> - 2013-03-12 12:17:12
|
Hi, Would appreciate any pointers to getting familiar with the SOAP Generator... Thanks Sitaraman -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. |
|
From: <sit...@nm...> - 2013-03-12 11:58:45
|
Hi, Marc has been helping me with the following issue...Marc suggests i post it here...any help is appreciated. Sitaraman Hi Sitaraman, The error is in SOAP Impl generator. Likely because it has not been aligned with the latest changes in Internal model. Post it to the openoss list. If you have done the common model after, then it should be sufficient for you to operate. Best regards Marc -----Original Message----- From: sit...@nm... [mailto:sit...@nm...] Sent: Saturday, March 09, 2013 1:02 PM To: Flauw, Marc Subject: RE: Importing SID Hi Marc, With the internal model, i get error during mvn clean install. Output and Tigerstipe-build.properties is attached. Since this project you mentioned was from your folder i though i will ping you first, if you want me to post it in the newsgroup do let me know. Thanks Marc, i owe you a Beer....:) Sitaraman > I forgot to mention: > For the generators, once checked out, > - undeploy the old one: Tigerstripe menu, Deployed Generators, then > select the generator and rigt-click Undeploy > - then Open the ts-plugin.xml then do a "package and deploy this > generator" (blue link under Testing) > > -----Original Message----- > From: Flauw, Marc > Sent: Tuesday, March 05, 2013 10:46 AM > To: 'sit...@nm...' > Subject: RE: Importing SID > > Hi Sitaraman > > For updating the generators, I would recommend a separate workspace > where all the generators can be put. > Then check them out one by one. > The SOAP one is at: > https://openoss.svn.sourceforge.net/svnroot/openoss/tip/framework/TIP_ > Soap_Generator/trunk/TIP_Soap_Generator > replace SOAP by Doc for the Doc Generator. > The implementation ones are under platform instead of framework. > > For common and internal models, create new workspaces for them. > Pick them from SVN: > - > https://openoss.svn.sourceforge.net/svnroot/openoss/tip/framework/TIP_ > Generator_Internal_Model/trunk > - > https://openoss.svn.sourceforge.net/svnroot/openoss/tip/framework/TIP_ > Common_Model/trunk > > And then build them like a standard interface: env variables, mvn > eclipse:eclipse, mvn clean install Build internal first and only then > build common. > > Then you should be all set. > > Best regards > > Marc > > -----Original Message----- > From: sit...@nm... [mailto:sit...@nm...] > Sent: Tuesday, March 05, 2013 10:35 AM > To: Flauw, Marc > Subject: RE: Importing SID > > My apologies Marc for bothering you on this.. > Could you give the link where the procedure and sitenames are available. > Thanks much.. > Sitaaman >> Hi Sitaraman, >> >> Known issue (JOS-6) fixed in trunk. >> You will need to: >> - get latest version of SOAP Gen from trunk >> - rebuild Internal and common model (in this order) >> >> Best regards >> >> Marc >> >> -----Original Message----- >> From: sit...@nm... [mailto:sit...@nm...] >> Sent: Tuesday, March 05, 2013 9:56 AM >> To: Flauw, Marc >> Subject: RE: Importing SID >> >> Hi Marc, >> I am trying to generate Texo JPA annotations and when i do that i >> get the following error... >> >> Click the details button for more information, and check the Error >> Log view for any exceptions....is it an error that can be fixed at >> TMF end... >> Thanks >> Sitaraman >> java.lang.IllegalStateException: >> file:/D:/Users/Sitaraman/EclipseVersions/EclipseForEMF/workspace/Texo >> T >> est1/Model/Interface_Implementation_Specifications/WSDL/sid_enterpris >> e >> _risk_sec_vuln.xsd >> (254:17):XSD: Type reference >> 'http://www.tmforum.org/xml/tip/internal/primitives#ArrayOfAnyURI' is >> unresolved >> file:/D:/Users/Sitaraman/EclipseVersions/EclipseForEMF/workspace/Texo >> T >> est1/Model/Interface_Implementation_Specifications/WSDL/sid_enterpris >> e >> _risk_sec_threat.xsd >> (279:17):XSD: Type reference >> 'http://www.tmforum.org/xml/tip/internal/primitives#ArrayOfAnyURI' is >> unresolved >> file:/D:/Users/Sitaraman/EclipseVersions/EclipseForEMF/workspace/Texo >> T >> est1/Model/Interface_Implementation_Specifications/WSDL/sid_enterpris >> e >> _risk_sec_threat.xsd >> (480:17):XSD: Type reference >> 'http://www.tmforum.org/xml/tip/internal/primitives#ArrayOfAnyURI' is >> unresolved >>> Hi Marc, >>> These look fine....the one in the link i mentioned has only a >>> limited number of XSDs it seems to be a competely different version >>> that what you just forwarded. Is the one you forwarded availble for >>> the community in general then...just to avoid having using your time >>> for these issues that are alreay been fixed by you.... >>> Thanks >>> Sitaraman >>>> Hi Sitaraman, >>>> >>>> Here is the one I have in my project directory. >>>> Is it showing the same errors? >>>> >>>> Best regards >>>> >>>> Marc >>>> >>>> -----Original Message----- >>>> From: sit...@nm... [mailto:sit...@nm...] >>>> Sent: Monday, March 04, 2013 2:57 PM >>>> To: Flauw, Marc >>>> Subject: RE: Importing SID >>>> >>>> A couple of them are as follows (In SID BusinessView Service) I >>>> just moused over the red marks in eclipse and cut and paste...if >>>> there is a way to list all the errors in a given file please let me >>>> know i will send across all of them.. >>>> The following are all the errors in SIDBusinessViewSErvice..... >>>> Thanks for prompt guidance and willingness to look into it Marc, >>>> much appreciated. >>>> Sitaraman >>>> >>>> annotations found at this line: >>>> - sch-props-correct.2: A schema cannot contain two global >>>> components with the same name; this schema contains two occurrences >>>> of 'http://www.tmforum.org/Frameworx/SID/ >>>> Business/12.0/Service,Customer'. >>>> - Start tag of element <xs:complexType> >>>> >>>> >>>> sch-props-correct.2: A schema cannot contain two global components >>>> with the same name; this schema contains two occurrences of >>>> 'http://www.tmforum.org/Frameworx/SID/Business/12.0/Service,Equipment'. >>>> >>>> Multiple annotations found at this line: >>>> - Start tag of element <xs:complexType> >>>> - sch-props-correct.2: A schema cannot contain two global >>>> components with the same name; this schema contains two occurrences >>>> of 'http://www.tmforum.org/Frameworx/SID/ >>>> Business/12.0/Service,Resource'. >>>> >>>> Multiple annotations found at this line: >>>> - sch-props-correct.2: A schema cannot contain two global >>>> components with the same name; this schema contains two occurrences >>>> of 'http://www.tmforum.org/Frameworx/SID/Business/12.0/ >>>> Service,State'. >>>> - Start tag of element <xs:simpleType> >>>> >>>>> Hi Sitaraman, >>>>> >>>>> It should be the right place. I did fix a number of errors. >>>>> Which ones do you have? >>>>> >>>>> Best regards >>>>> >>>>> Marc >>>>> >>>>> -----Original Message----- >>>>> From: sit...@nm... [mailto:sit...@nm...] >>>>> Sent: Monday, March 04, 2013 2:36 PM >>>>> To: Flauw, Marc >>>>> Subject: RE: Importing SID >>>>> >>>>> Hi Marc, >>>>> I took the 12.5 XSDs from >>>>> http://www.tmforum.org/DownloadRelease125/14240/home.html Is this >>>>> the correct place....for eclipse throws errors on the XSDs when i >>>>> open them... >>>>> Sitaraman >>>>>> Hi Sitaraman, >>>>>> >>>>>> I didn't commit the SID version I used as the only master is the >>>>>> SID. >>>>>> >>>>>> For UML pick a SID branch and then generate For xsd and wsdl, >>>>>> those were published with SID 12.5 >>>>>> >>>>>> Best regards >>>>>> >>>>>> Marc >>>>>> >>>>>> -----Original Message----- >>>>>> From: sit...@nm... [mailto:sit...@nm...] >>>>>> Sent: Monday, March 04, 2013 12:38 PM >>>>>> To: Flauw, Marc >>>>>> Subject: Importing SID >>>>>> >>>>>> Hi Marc, >>>>>> You had earlier fixed several issues in the SID (duplicates >>>>>> being one of them). Could you let me know where i should take the >>>>>> UML, XSDs and WSDLs from to try and import them into a project >>>>>> created using JOSIF generators... >>>>>> Thanks >>>>>> Sitaraman >>>>>> >>>>>> >>>>>> -- >>>>>> This message has been scanned for viruses and dangerous content >>>>>> by MailScanner, and is believed to be clean. >>>>>> >>>>>> >>>>>> -- >>>>>> This message has been scanned for viruses and dangerous content >>>>>> by MailScanner, and is believed to be clean. >>>>>> >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> This message has been scanned for viruses and dangerous content by >>>>> MailScanner, and is believed to be clean. >>>>> >>>>> >>>>> -- >>>>> This message has been scanned for viruses and dangerous content by >>>>> MailScanner, and is believed to be clean. >>>>> >>>>> >>>> >>>> >>>> >>>> -- >>>> This message has been scanned for viruses and dangerous content by >>>> MailScanner, and is believed to be clean. >>>> >>>> >>>> -- >>>> This message has been scanned for viruses and dangerous content by >>>> MailScanner, and is believed to be clean. >>>> >>>> >>> >>> >> >> >> >> -- >> This message has been scanned for viruses and dangerous content by >> MailScanner, and is believed to be clean. >> >> >> -- >> This message has been scanned for viruses and dangerous content by >> MailScanner, and is believed to be clean. >> >> > > > > -- > This message has been scanned for viruses and dangerous content by > MailScanner, and is believed to be clean. > > > -- > This message has been scanned for viruses and dangerous content by > MailScanner, and is believed to be clean. > > -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. |
|
From: SB M. <sbm...@tm...> - 2013-03-05 08:53:20
|
TMF Collab ID is mentioned in the mail below and mentioned here again. hemantg3 Thanks and Regds, SB -----Original Message----- From: Craig Gallen [mailto:gal...@go...] On Behalf Of Craig Gallen (opennms) Sent: 05 March 2013 13:59 To: SB Mahapatra Cc: hem...@in...; Pierre Gauthier; openoss-devel Subject: Re: Access to Sourceforge site -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Folks, You keep sending me UserID's for TMF Collab Site to allow access to sourceforge. This has nothing to do with the user ids for sourceforge. To allow access to sourceforge, each user must create a sourceforge user account, Then they can be granted access. Hermant, could you join sourceforge and send me your sourceforge user id. Then I can allow access to https://openoss.svn.sourceforge.net/svnroot/openoss/tip Also please join the lists at https://sourceforge.net/mail/?group_id=122678 Thanks Craig On 05/03/2013 06:50, SB Mahapatra wrote: > Hi Craig, > > Please provide access to Hamant Gour from IBM. > > Email ID : hem...@in...<mailto:hem...@in...<mailto:hem...@in...%3cmailto:hem...@in...>> > > UserID for TMF Collab Site : hemantg3 > > https://openoss.svn.sourceforge.net/svnroot/openoss/tip > > Thanks and Regds, > SB > -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJRNayxAAoJEATefL4tbU2QNKEH/2Q7yFEsyrWYqJSEdJZvQiuu FvhclKAHqWeDMMIlv7QImcFUDJpZ7D+buVLuhr9rWliL1rNLDDqNbSsaCeIZ0j4X Jwdb1CMw0E+SVu845KDImkyn4i0F0EocvFPfYn0AIqcpIB3a+4DfBjAtjaroADCw esQlrp+hJs6bz8/U9cFypTRPdw4I40LEuFYbeBOvC8Zz8zzNakQUf6P3wGE1ZoLB zSUOmZP+9qmhwCCUwP2J46UWIz6HJxop9KiwS2gUY8icV5FW/ct6IlQQ+cX/0q72 wzxsG/ClHT0jSvluZYm45av5nKkGZRKKE/7/O+HrWNn3soILI+gVuwEPnfbWyEw= =wwB3 -----END PGP SIGNATURE----- |
|
From: Craig G. (opennms) <cg...@op...> - 2013-03-05 08:48:22
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Yes I know but the TMF Collab ID hemantg3 is NOT a user name in sourceforge :) It is for the TMF collab site which will not give access to https://openoss.svn.sourceforge.net/svnroot/openoss/tip Hermant needs to create a user account on sourceforge, send me his sourceforge user id and then we can allow access. Craig On 05/03/2013 08:37, SB Mahapatra wrote: > TMF Collab ID is mentioned in the mail below and mentioned here again. > > > > hemantg3 > > > > Thanks and Regds, > > SB > > -----Original Message----- > From: Craig Gallen [mailto:gal...@go...] On Behalf Of Craig Gallen (opennms) > Sent: 05 March 2013 13:59 > To: SB Mahapatra > Cc: hem...@in...; Pierre Gauthier; openoss-devel > Subject: Re: Access to Sourceforge site > > > > Hash: SHA1 > > > > Folks, > > > > You keep sending me UserID's for TMF Collab Site to allow access to sourceforge. This has nothing to do with the user ids for sourceforge. > > > > To allow access to sourceforge, each user must create a sourceforge user account, Then they can be granted access. > > > > Hermant, > > could you join sourceforge and send me your sourceforge user id. Then I can allow access to https://openoss.svn.sourceforge.net/svnroot/openoss/tip > > > > Also please join the lists at https://sourceforge.net/mail/?group_id=122678 > > > > Thanks > > > > Craig > > > > On 05/03/2013 06:50, SB Mahapatra wrote: > >> Hi Craig, > > > >> Please provide access to Hamant Gour from IBM. > > > >> Email ID : hem...@in...<mailto:hem...@in...<mailto:hem...@in...%3cmailto:hem...@in...>> > > > >> UserID for TMF Collab Site : hemantg3 > > > >> https://openoss.svn.sourceforge.net/svnroot/openoss/tip > > > >> Thanks and Regds, > >> SB > > > > > > -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJRNbFLAAoJEATefL4tbU2Q4X4IAIV9CODd+Q5GvNqQ438pipF4 +UdLJ+FJUfycMAHEJUyfvlbfbnELCnEP3s3M01zkrXAq2qoZ/fNPCMTYRHFR0OpO k3pC7Cl2mNgv7sePJEdRHuw4VnfM3XjOswZLnI19uTbf28bnQyS4qaRGx1EieDXr Ok/LDd2Kqm1kHRt1MUfDRf410cjSXZetY+hZaFPSOKiH0qzKsw//Ys7Bx6Ee0HWy AoNCFEIdQ+PIHlkzxOL+APBM5zwI1fITbvb0PcOxrb/D6n/2YBIBmXAmW6NCsex8 uMstuIPGcxoBX0Lmsd5QWAtdGBa5dBKmlVM2qawkBMX5QzDRz38SAtuqsejMNkw= =r6+o -----END PGP SIGNATURE----- |
|
From: Craig G. (opennms) <cg...@op...> - 2013-03-05 08:28:50
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Folks, You keep sending me UserID's for TMF Collab Site to allow access to sourceforge. This has nothing to do with the user ids for sourceforge. To allow access to sourceforge, each user must create a sourceforge user account, Then they can be granted access. Hermant, could you join sourceforge and send me your sourceforge user id. Then I can allow access to https://openoss.svn.sourceforge.net/svnroot/openoss/tip Also please join the lists at https://sourceforge.net/mail/?group_id=122678 Thanks Craig On 05/03/2013 06:50, SB Mahapatra wrote: > Hi Craig, > > Please provide access to Hamant Gour from IBM. > > Email ID : hem...@in...<mailto:hem...@in...> > > UserID for TMF Collab Site : hemantg3 > > https://openoss.svn.sourceforge.net/svnroot/openoss/tip > > Thanks and Regds, > SB > -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJRNayxAAoJEATefL4tbU2QNKEH/2Q7yFEsyrWYqJSEdJZvQiuu FvhclKAHqWeDMMIlv7QImcFUDJpZ7D+buVLuhr9rWliL1rNLDDqNbSsaCeIZ0j4X Jwdb1CMw0E+SVu845KDImkyn4i0F0EocvFPfYn0AIqcpIB3a+4DfBjAtjaroADCw esQlrp+hJs6bz8/U9cFypTRPdw4I40LEuFYbeBOvC8Zz8zzNakQUf6P3wGE1ZoLB zSUOmZP+9qmhwCCUwP2J46UWIz6HJxop9KiwS2gUY8icV5FW/ct6IlQQ+cX/0q72 wzxsG/ClHT0jSvluZYm45av5nKkGZRKKE/7/O+HrWNn3soILI+gVuwEPnfbWyEw= =wwB3 -----END PGP SIGNATURE----- |
|
From: Joe F. <Joe...@op...> - 2013-03-05 01:04:18
|
Hi I'm looking at the Interfaces page: https://openoss.atlassian.net/wiki/display/JOSIFDOC1/TIP+Interfaces I realise it is still a Work In Progress, but want to check since I have lost track. The only child pages shown are for RAM and SPM. Has Generic Query for Inventory been developed using JOSIF? Thanks Joe |
|
From: Flauw, M. <Mar...@hp...> - 2013-02-13 10:42:56
|
Hi Craig, I scan the guidebook and the framework parts and all my changes seem present. So it is ok for me, thanks. Best regards Marc -----Original Message----- From: Craig Gallen [mailto:gal...@go...] On Behalf Of Craig Gallen (opennms) Sent: Tuesday, February 12, 2013 7:52 PM To: Flauw, Marc Cc: openoss-devel; Craig Gallen (OpenNMS) Subject: Re: work on confluence -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Folks I have started a 'Front Page' space for JOSIF to contain all of the project news and links to relevant underlying projects. http://openoss.atlassian.net/wiki/display/JOS/Welcome Other spaces can still be found from the dashboard but this gives a simple entry to the project. I will be pointing to this page from the main site if all is OK. Could we all now only use the JOSIF Documentation V1 space for the imported release documentation. The 'Import' and 'Working Documentation' spaces should not be edited or referenced going forwards. http://openoss.atlassian.net/wiki/display/JOSIFDOC1/ Marc, As far as I can tell I have applied all of your changes to my work in the JOSIF Documentation V1 space. Please check if this is substantially correct. If all is OK I will remove other copies of the import from the Media Wiki so that we can use only this space. In general there is still more work to do. Over time all of the non release specific content in the JOSIF Documentation V1 space should be moved to the JOSIF welcome space (developer info, news, links to general documentation and project overviews etc). This will be the landing page for the project and should then reference other projects as necessary. We will then want to get into the practice of creating a clone of the JOSIF Documentation V1 space for each release. That way we will have a record of the documentation of each release. (This is how Atlassian document their own releases of confluence 3.5, 4.0 etc.) Hope this makes sense Craig On 08/02/2013 12:04, Flauw, Marc wrote: > Hi Craig, > > I checked your revised pages compared to the work I did on the WD pages. > You would need to pick all of JOSIF Guidebook and Framework from WD, as there is quite some additional work not present in your branch, like adding new pages to get better TOC, reparenting pages. I also fixed a few other problems along. There are still a few red pointers in your pages like the test projects under fmk. > > Best regards > > Marc > > -----Original Message----- > From: Craig Gallen [mailto:gal...@go...] On Behalf Of > Craig Gallen (opennms) > Sent: Friday, February 08, 2013 2:06 AM > To: openoss-devel; Flauw, Marc > Subject: work on confluence > > Marc, > > I have done a lot of work to sort out the confluence wiki. > > Please see the revised pages at > https://openoss.atlassian.net/wiki/display/JOSIFDOC1 > > Still work to do but moving in the right direction i think > > What do you think > > Craig > -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJRGo86AAoJEATefL4tbU2QtlwH/1oMobFTJh9lbyNB1S2IFEoY NuaCkvppMQCHc6MipZA/7ZLNt8Wqc/3lPOsuYbkTsx8YUpCwP6wE3IuQm1w9wRko aeelVBT3xa9y/Rpsz6mfepAggiG1FLCz2zmZL5Dcth7bKDhzWLtKP3CdHa+C4bmu 3wAqm/e4Bwi0b+rLq2r1cROpdCBXiclEPu16NV83hgLn7gxlVxW6dL453+sdbwhX MT+afiycBgICcXayJ71i8VXlQ4HIbGTlTheNZP7pwQjAVUdIFAhCzoddIQ4vTnP5 9zIEhMZsT+zPmWWtgIMJKrEZj83F+KQUaULtZrJyAh/yFKDMOhs9hcCLdf05MJQ= =ZaMP -----END PGP SIGNATURE----- |
|
From: Craig G. (opennms) <cg...@op...> - 2013-02-12 18:51:51
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Folks I have started a 'Front Page' space for JOSIF to contain all of the project news and links to relevant underlying projects. http://openoss.atlassian.net/wiki/display/JOS/Welcome Other spaces can still be found from the dashboard but this gives a simple entry to the project. I will be pointing to this page from the main site if all is OK. Could we all now only use the JOSIF Documentation V1 space for the imported release documentation. The 'Import' and 'Working Documentation' spaces should not be edited or referenced going forwards. http://openoss.atlassian.net/wiki/display/JOSIFDOC1/ Marc, As far as I can tell I have applied all of your changes to my work in the JOSIF Documentation V1 space. Please check if this is substantially correct. If all is OK I will remove other copies of the import from the Media Wiki so that we can use only this space. In general there is still more work to do. Over time all of the non release specific content in the JOSIF Documentation V1 space should be moved to the JOSIF welcome space (developer info, news, links to general documentation and project overviews etc). This will be the landing page for the project and should then reference other projects as necessary. We will then want to get into the practice of creating a clone of the JOSIF Documentation V1 space for each release. That way we will have a record of the documentation of each release. (This is how Atlassian document their own releases of confluence 3.5, 4.0 etc.) Hope this makes sense Craig On 08/02/2013 12:04, Flauw, Marc wrote: > Hi Craig, > > I checked your revised pages compared to the work I did on the WD pages. > You would need to pick all of JOSIF Guidebook and Framework from WD, as there is quite some additional work not present in your branch, like adding new pages to get better TOC, reparenting pages. I also fixed a few other problems along. There are still a few red pointers in your pages like the test projects under fmk. > > Best regards > > Marc > > -----Original Message----- > From: Craig Gallen [mailto:gal...@go...] On Behalf Of Craig Gallen (opennms) > Sent: Friday, February 08, 2013 2:06 AM > To: openoss-devel; Flauw, Marc > Subject: work on confluence > > Marc, > > I have done a lot of work to sort out the confluence wiki. > > Please see the revised pages at > https://openoss.atlassian.net/wiki/display/JOSIFDOC1 > > Still work to do but moving in the right direction i think > > What do you think > > Craig > -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJRGo86AAoJEATefL4tbU2QtlwH/1oMobFTJh9lbyNB1S2IFEoY NuaCkvppMQCHc6MipZA/7ZLNt8Wqc/3lPOsuYbkTsx8YUpCwP6wE3IuQm1w9wRko aeelVBT3xa9y/Rpsz6mfepAggiG1FLCz2zmZL5Dcth7bKDhzWLtKP3CdHa+C4bmu 3wAqm/e4Bwi0b+rLq2r1cROpdCBXiclEPu16NV83hgLn7gxlVxW6dL453+sdbwhX MT+afiycBgICcXayJ71i8VXlQ4HIbGTlTheNZP7pwQjAVUdIFAhCzoddIQ4vTnP5 9zIEhMZsT+zPmWWtgIMJKrEZj83F+KQUaULtZrJyAh/yFKDMOhs9hcCLdf05MJQ= =ZaMP -----END PGP SIGNATURE----- |
197 messages has been excluded from this view by a project administrator.
