Menu
▾
▴
[Openoss-devel] [Fwd: RE: Importing SID]
|
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. |
