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: Craig G. (opennms) <cg...@op...> - 2012-06-26 14:59:14
|
Hi, We need to generate the wsdl for the abstract ManagementJobInterface because the rest of the build of the common model marshalling and unmarshalling for hte RI/CTK expects there to be jaxb classes generated from the ManagementJobInterface. These will be abstract classes which the later concrete classes extend Cheers Craig On 26/06/2012 06:43, Flauw, Marc wrote: > Craig, > > I think you refer to the ManagementJobInterface. It is true this is an abstract interface and it will be inherited by concrete ones in the interfaces using it. > > I am not sure to understand why we need to generate the wsdl for it. > > Best regards > > Marc > > -----Original Message----- > From: Craig Gallen [mailto:cg...@we...] > Sent: Tuesday, June 26, 2012 3:56 AM > To: Flauw, Marc; openoss-devel > Subject: Abstract Facades in common model > > Hi, > > > The Common model contains an abstract facade but the soap generator does not generate this if there is no super facade. We should be generating the abstract faecal as abstract WSDL otherwise the Common model does not compile correctly. > > Craig |
|
From: Xose R. S. V. <xr...@op...> - 2012-06-26 08:40:30
|
Thanks Craig. I have performed some test and I can see an error in the Default Velocity context contents. When the $allPackage variable is used in the dependencyAnalyzer.vm template, it is expected that all artifacts, including the dependences, are included in that collection. In my tests I've got this behaivour: Old version of tigerstripe( Tigerstripe Core (Incubation) 0.6.935.201102010903 org.eclipse.tigerstripe.base.feature.group) %%%Calculate the dependencies/closure with [org.tmforum.tip.resource.trouble.alarm(370509597), org.tmforum.tip.resource.trouble(428889018), org.tmforum.tip.resource(240211633), org.tmforum.tip.cbe.perf(1039318676), org.tmforum.tip.common.notifications(23492680), org.tmforum.tip.resource.res(1133197283), org.tmforum.tip.cbe.root(1039387789), org.tmforum.tip(-660924437), org.tmforum.tip.cbe.root._char(-1449023596), org.tmforum(1644248382), org(110308), org.tmforum.tip.common(442435918), org.tmforum.tip.cbe.party(-2140978021), org.tmforum.tip.cbe.problem(292836116), org.tmforum.tip.cbe.root.tip.fmk(693071952), org.tmforum.tip.internal.filter(-1708340282), org.tmforum.tip.internal.extensibility(-1665414181), org.tmforum.tip.internal(1151687008), org.tmforum.tip.cbe.root.tip(1325885370), org.tmforum.tip.internal.notifications(-1680981798), org.tmforum.tip.common.exceptions(234099364), org.tmforum.tip.cbe.party.role(1514413545), org.tmforum.tip.internal.entity(-1732123599), org.tmforum.tip.resource.res.tip(-1716701168), org.tmforum.tip.internal.exceptions(-367434926), org.tmforum.tip.cbe(1681757027), org.tmforum.tip.internal.iterator(866200892), org.tmforum.tip.resource.res.tip.nrb(290014272)] [2012-06-26 10:21:29.996+0200] New version og tigerstripe( Tigerstripe Core (Incubation) 0.7.0.201206181258 org.eclipse.tigerstripe.base.feature.group): %%%Calculate the dependencies/closure with [org.tmforum.tip.resource.trouble.alarm(370509597), org.tmforum.tip.resource.trouble(428889018), org.tmforum.tip.resource(240211633)] [2012-06-26 10:28:54.989+0200] So it seems that this is root cause for the missed files. I will create a bug in Tigerstripe. Regards El 25/06/2012 18:35, Craig Gallen (entimoss) escribió: > Hi > From eclipse, Soap generator subversion; > https://openoss.svn.sourceforge.net/svnroot/openoss/tip/framework/TIP_Soap_Generator/trunk/TIP_Soap_Generator > Revision 3453 > (last change revision 3444 last commit author xrsousa) > > Craig > > On 25/06/2012 15:57, Xose Ramon Sousa Vazquez wrote: >> Hi Craig, when you talk about the updated Soap Plugin, which version >> (in svn url) are using?, because the two first issues seems to be >> solved in the trunk with the other Tigerstripe version. >> >> >> >> >> Regards >> El 25/06/2012 16:54, Craig Gallen (entimoss) escribió: >>> Hi Xose, >>> >>> I just updated my tigerstripe to the latest release >>> 0.7.0.20120618258 but Ialso updated the Soap plug-in and have found >>> multiple problems but I am not sure if they are all related to the >>> tigerstripe upgrade or to the current state of the soap plugin. >>> Could you build the RAM project and check the generated XSD's to see >>> the problem. >>> >>> 1. when you build the RAM project there is a problem with model >>> closure. None of the Dependency XSD's get generated in the >>> RAM_Model project >>> >>> 2. TrackingRecordResultWithIterator referenced as >>> 'problem:TrackingRecordResultWithIterator' in >>> ram_resource_trouble_alarm_resourcealarmretrievalservice_msg.xsd is >>> never generated. >>> >>> 3. Tigerstripe 0.7.0.20120618258. handles primitive.string >>> differently and generates type 'String' instead of >>> 'java.lang.String' this results in type :String instead of >>> xsd:string. I did a quick fix given in the following patch adding >>> || "String".equalsIgnoreCase(refType.getFullyQualifiedName())) >>> >>> to >>> || "java.lang.String".equalsIgnoreCase(refType.getFullyQualifiedName()) >>> this means that old and new versions of tigerstipe will work >>> >>> There is a patch below but havent checked this in because I was not >>> sure that else you were doing to the Soap plugin >>> >>> Craig >>> >>> >>> >>> ### Eclipse Workspace Patch 1.0 >>> #P TIP_Soap_Generator >>> Index: >>> src/org/eclipse/tigerstripe/generators/xml/helpers/XmlSchemaHelpers.java >>> =================================================================== >>> --- >>> src/org/eclipse/tigerstripe/generators/xml/helpers/XmlSchemaHelpers.java >>> (revision 3453) >>> +++ >>> src/org/eclipse/tigerstripe/generators/xml/helpers/XmlSchemaHelpers.java >>> (working copy) >>> @@ -510,8 +510,8 @@ >>> */ >>> if (refType.isPrimitive() >>> || refType.getPackage().equalsIgnoreCase("primitive") >>> - || "java.lang.String".equalsIgnoreCase(refType >>> - .getFullyQualifiedName())) { >>> + || >>> "java.lang.String".equalsIgnoreCase(refType.getFullyQualifiedName()) >>> + || >>> "String".equalsIgnoreCase(refType.getFullyQualifiedName())) { // >>> tigerstripe 1.7.0 now generates String and not java.lang.String >>> PluginLog.logDebug("\'" + refTypeFullName >>> + "\' is a primitive type in current TIP >>> profile."); >>> type = mapPrimitivesToXsdType(refType.getName(), >>> isArray(refType), >>> @@ -519,7 +519,7 @@ >>> } >>> >>> /** >>> - * Map datatyeps and enumerations >>> + * Map datatypes and enumerations >>> */ >>> // if (refType.isDatatype() || refType.isEnum() >>> else if (isDatatype(refType) || isEnumeration(refType)) { >>> Index: >>> src/org/eclipse/tigerstripe/generators/xml/helpers/XsdReferencesMgr.java >>> =================================================================== >>> --- >>> src/org/eclipse/tigerstripe/generators/xml/helpers/XsdReferencesMgr.java >>> (revision 3453) >>> +++ >>> src/org/eclipse/tigerstripe/generators/xml/helpers/XsdReferencesMgr.java >>> (working copy) >>> @@ -170,8 +170,9 @@ >>> private void addReferencedPackage(IType type) { >>> >>> if (type.isPrimitive() >>> - || "primitive".equalsIgnoreCase(type.getPackage()) || >>> - >>> "java.lang.String".equalsIgnoreCase(type.getFullyQualifiedName())) { >>> + || "primitive".equalsIgnoreCase(type.getPackage()) >>> + || >>> "java.lang.String".equalsIgnoreCase(type.getFullyQualifiedName()) >>> + || >>> "String".equalsIgnoreCase(type.getFullyQualifiedName())) { // >>> tigerstripe 1.7.0 now generates String and not java.lang.String >>> //will map objectName to EntityIdentifier or >>> ArrayOfEntityIdentifier >>> if ("objectName".equalsIgnoreCase(type.getName())){ >>> PluginLog.logDebug("type \'" + type >>> @@ -378,8 +379,8 @@ >>> */ >>> if (refType.isPrimitive() >>> || refType.getPackage().equalsIgnoreCase("primitive") >>> - || "java.lang.String".equalsIgnoreCase(refType >>> - .getFullyQualifiedName())) { >>> + || >>> "java.lang.String".equalsIgnoreCase(refType.getFullyQualifiedName()) >>> + || >>> "String".equalsIgnoreCase(refType.getFullyQualifiedName())) { // >>> tigerstripe 1.7.0 now generates String and not java.lang.String >>> PluginLog.logDebug("\'" + typeName >>> + "\' is a primitive type in current TIP >>> profile."); >>> >>> >>> >>> >>> >>> >>> >>> On 11/06/2012 12:35, Xose Ramon Sousa Vazquez wrote: >>>> Hi all. I think that I have found the error and I will try to fix >>>> it as soon as possible. There are some related issues, one error in >>>> the codification of a method and a forgetted evaluation of >>>> filtering in the velocity template and also a case related with >>>> primitive type filter not supported in the build of the closure >>>> outside the interfaces. >>>> >>>> In the interfaces build the search is performed as follows(this >>>> works fine as reported Marc): >>>> >>>> if ("objectName".equalsIgnoreCase(argType.getName())) { >>>> /* >>>> * This data type 'objectName' defines >>>> the protocol >>>> * neutral unique name of an object. >>>> This data type will >>>> * be replaced by the generators by an >>>> EntityIdentifier >>>> */ >>>> String pkg = PluginConstants >>>> >>>> .getPropVal(PluginConstants.KEY_INTERNAL_MODEL_PKG); >>>> if (!this.map.containsKey(pkg)) { >>>> // >>>> // New package - add new pkg=prefix >>>> mapping >>>> // assignment >>>> // >>>> String prefix = >>>> XmlSchemaHelpers.generateXmlPrefix( >>>> pkg, this.map); >>>> this.map.put(pkg, prefix); >>>> } >>>> } else if >>>> ("filter".equalsIgnoreCase(argType.getName())) { >>>> /* >>>> * This data type 'filter'. This data >>>> type will >>>> * be replaced by the generator to >>>> */ >>>> String pkg = PluginConstants >>>> >>>> .getPropVal(PluginConstants.KEY_INTERNAL_FILTER_PKG); >>>> if (!this.map.containsKey(pkg)) { >>>> // >>>> // New package - add new pkg=prefix >>>> mapping >>>> // assignment >>>> // >>>> String prefix = >>>> XmlSchemaHelpers.generateXmlPrefix( >>>> pkg, this.map); >>>> this.map.put(pkg, prefix); >>>> } >>>> } else if >>>> (XmlSchemaHelpers.isUnbounded(argType)) { >>>> String pkg = PluginConstants >>>> >>>> .getPropVal(PluginConstants.KEY_INTERNAL_MODEL_PRIMITIVES_PKG); >>>> if (!this.map.containsKey(pkg)) { >>>> // >>>> // New package - add new pkg=prefix >>>> mapping >>>> // assignment >>>> // >>>> String prefix = >>>> XmlSchemaHelpers.generateXmlPrefix( >>>> pkg, this.map); >>>> this.map.put(pkg, prefix); >>>> } >>>> } else { >>>> // XSD default namespace is enough >>>> } >>>> >>>> and in the build of the closure we have got (this fails as reported >>>> Craig): >>>> >>>> if ("objectName".equalsIgnoreCase(type.getName())){ >>>> PluginLog.logDebug("type \'" + type >>>> + "\' is an array of primitive."); >>>> addReferencedPackage(PluginConstants >>>> >>>> .getPropVal(PluginConstants.KEY_INTERNAL_MODEL_PKG)); >>>> }else if (XmlSchemaHelpers.isUnbounded(type)){ >>>> //will map to array of primitive >>>> addReferencedPackage(PluginConstants >>>> >>>> .getPropVal(PluginConstants.KEY_INTERNAL_MODEL_PRIMITIVES_PKG)); >>>> } else { >>>> //normal primtive like xsd:int >>>> } >>>> >>>> so the filtering never is considered. >>>> >>>> I will perform clean tests because was very difficult to find the >>>> real cause of the problem, the log file is not very clear in debug >>>> scenarios ( a lot of similar log text, no log from the templates >>>> and also cannot put the line number in the log file (tigerstripe >>>> issue)) and these problems have delayed my response. >>>> If the test go ok I will check out the changes to the trunk >>>> >>>> https://openoss.svn.sourceforge.net/svnroot/openoss/tip/framework/TIP_Soap_Generator/trunk/TIP_Soap_Generator >>>> >>>> Best regards >>>> >>>> >>>> El 01/06/2012 16:58, Craig Gallen escribió: >>>>> Hi, >>>>> >>>>> I agree it is defined in internal_filter.xsd but it doesn't seem to be >>>>> referenced properly from dep_cbe_perf_spec.xsd in the PM project. WSDL2Java >>>>> throws an error and when you open dep_cbe_perf_spec.xsd in eclipse it also >>>>> shows an error. >>>>> >>>>> I think Xose is looking into it >>>>> >>>>> Craig >>>>> >>>>> -----Original Message----- >>>>> From: Flauw, Marc [mailto:Mar...@hp...] >>>>> Sent: 01 June 2012 10:25 >>>>> To: Craig Gallen (opennms); openoss-devel; Xose Ramon Sousa Vazquez; pierre >>>>> gauthier >>>>> Subject: RE: Problems with PM XSD generation >>>>> >>>>> Craig, >>>>> >>>>> There is one same filter in the getReosurceAlarms operation, filter >>>>> argument. >>>>> The XPathFilter is defined in the internal_filter.xsd >>>>> >>>>> Best regards >>>>> >>>>> Marc >>>>> >>>>> -----Original Message----- >>>>> From: Craig Gallen [mailto:gal...@go...] On Behalf Of Craig >>>>> Gallen (opennms) >>>>> Sent: Thursday, May 31, 2012 11:58 PM >>>>> To: openoss-devel; Flauw, Marc; Xose Ramon Sousa Vazquez; pierre gauthier >>>>> Subject: Problems with PM XSD generation >>>>> >>>>> Hi, >>>>> >>>>> I have been testing the TIP_PM_Col project model and have found that the >>>>> dep_cbe_perf_spec.xsd (attached) file is generated with errors >>>>> >>>>> in line 62 we have >>>>> <xsd:element name="objectInstanceFilter" type="filter:XPathQueryFilter" >>>>> minOccurs="0" maxOccurs="1"> >>>>> >>>>> filter:XPathQueryFilter is not defined and if you open the file in eclipse >>>>> it reports this error as: >>>>> >>>>> 's4s-att-invalid-value: Invalid attribute value for 'type' in element >>>>> 'element'. Recorded reason: >>>>> UndeclaredPrefix: Cannot resolve 'filter:XPathQueryFilter' as a QName: >>>>> the prefix 'filter' is not >>>>> declared'. >>>>> >>>>> Is this a known problem or a new bug? >>>>> >>>>> Craig >>>>> >>>> >>>> >>>> -- >>>> >>>> *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><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><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><http://optarecoolvendor.com> |
|
From: Flauw, M. <Mar...@hp...> - 2012-06-26 05:56:25
|
Craig, I made the change in the Common Model (and in RSA) and committed it. Note also that there is a (small) change in Schedule, 2 attributes changing names in Monthly schedule. Best regards Marc -----Original Message----- From: Craig Gallen [mailto:gal...@go...] On Behalf Of Craig Gallen (opennms) Sent: Tuesday, June 26, 2012 1:56 AM To: Flauw, Marc; openoss-devel Subject: NA value in TransmissionParameterList in Common Model Marc, A quick question about the Common Model. You have defined the following type: org.tmforum.tip.resource.res.nrb.TransmissionParameterList with variable layerRate of type org.tmforum.tip.resource.res.nrb.LayerRate layerRate set to default value = NA which is not a valid value. The default value should be left empty or set to a constant or a string value if it is a String. This also applies to transmissionParameterList Can we change default value back to and empty value. Cheers Craig |
|
From: Flauw, M. <Mar...@hp...> - 2012-06-26 05:44:36
|
Craig, I think you refer to the ManagementJobInterface. It is true this is an abstract interface and it will be inherited by concrete ones in the interfaces using it. I am not sure to understand why we need to generate the wsdl for it. Best regards Marc -----Original Message----- From: Craig Gallen [mailto:cg...@we...] Sent: Tuesday, June 26, 2012 3:56 AM To: Flauw, Marc; openoss-devel Subject: Abstract Facades in common model Hi, The Common model contains an abstract facade but the soap generator does not generate this if there is no super facade. We should be generating the abstract faecal as abstract WSDL otherwise the Common model does not compile correctly. Craig |
|
From: Flauw, M. <Mar...@hp...> - 2012-06-26 05:42:47
|
Craig, This is a convention coming from MTOSI. I have removed quite a few already when doing MPAC. I will remove it as I have some uncommitted changes in the Common Model (doc mainly), but I need to update the SID also. Best regards Marc -----Original Message----- From: Craig Gallen [mailto:gal...@go...] On Behalf Of Craig Gallen (opennms) Sent: Tuesday, June 26, 2012 1:56 AM To: Flauw, Marc; openoss-devel Subject: NA value in TransmissionParameterList in Common Model Marc, A quick question about the Common Model. You have defined the following type: org.tmforum.tip.resource.res.nrb.TransmissionParameterList with variable layerRate of type org.tmforum.tip.resource.res.nrb.LayerRate layerRate set to default value = NA which is not a valid value. The default value should be left empty or set to a constant or a string value if it is a String. This also applies to transmissionParameterList Can we change default value back to and empty value. Cheers Craig |
|
From: Craig G. <cg...@we...> - 2012-06-26 02:16:37
|
Hi, The Common model contains an abstract facade but the soap generator does not generate this if there is no super facade. We should be generating the abstract faecal as abstract WSDL otherwise the Common model does not compile correctly. Craig |
|
From: Craig G. (opennms) <cg...@op...> - 2012-06-25 23:56:34
|
Marc, A quick question about the Common Model. You have defined the following type: org.tmforum.tip.resource.res.nrb.TransmissionParameterList with variable layerRate of type org.tmforum.tip.resource.res.nrb.LayerRate layerRate set to default value = NA which is not a valid value. The default value should be left empty or set to a constant or a string value if it is a String. This also applies to transmissionParameterList Can we change default value back to and empty value. Cheers Craig |
|
From: Craig G. (opennms) <cg...@op...> - 2012-06-25 16:39:19
|
Hi
Great. Update to latest JVT plugin in trunk and JVT should work with String.
Thanks,
Craig
On 25/06/2012 17:03, Flauw, Marc wrote:
>
> Craig,
>
> I managed to build RAM kit but it failed in JVT spec with String.
>
> I have Tigerstripe I50 with generators from 2 weeks ago and common
> model with job and schedule
>
> Best regards
>
> Marc
>
> *From:*Craig Gallen [mailto:gal...@go...] *On Behalf Of
> *Craig Gallen (entimoss)
> *Sent:* Monday, June 25, 2012 4:55 PM
> *To:* Xose Ramon Sousa Vazquez
> *Cc:* Flauw, Marc; 'Craig Gallen (opennms)'; 'openoss-devel'; 'pierre
> gauthier'
> *Subject:* Re: Problems with PM XSD generation
>
> Hi Xose,
>
> I just updated my tigerstripe to the latest release 0.7.0.20120618258
> but Ialso updated the Soap plug-in and have found multiple problems
> but I am not sure if they are all related to the tigerstripe upgrade
> or to the current state of the soap plugin. Could you build the RAM
> project and check the generated XSD's to see the problem.
>
> 1. when you build the RAM project there is a problem with model
> closure. None of the Dependency XSD's get generated in the RAM_Model
> project
>
> 2. TrackingRecordResultWithIterator referenced as
> 'problem:TrackingRecordResultWithIterator' in
> ram_resource_trouble_alarm_resourcealarmretrievalservice_msg.xsd is
> never generated.
>
> 3. Tigerstripe 0.7.0.20120618258. handles primitive.string differently
> and generates type 'String' instead of 'java.lang.String' this results
> in type :String instead of xsd:string. I did a quick fix given in the
> following patch adding
> || "String".equalsIgnoreCase(refType.getFullyQualifiedName()))
>
> to
> || "java.lang.String".equalsIgnoreCase(refType.getFullyQualifiedName())
> this means that old and new versions of tigerstipe will work
>
> There is a patch below but havent checked this in because I was not
> sure that else you were doing to the Soap plugin
>
> Craig
>
>
>
> ### Eclipse Workspace Patch 1.0
> #P TIP_Soap_Generator
> Index:
> src/org/eclipse/tigerstripe/generators/xml/helpers/XmlSchemaHelpers.java
> ===================================================================
> ---
> src/org/eclipse/tigerstripe/generators/xml/helpers/XmlSchemaHelpers.java
> (revision 3453)
> +++
> src/org/eclipse/tigerstripe/generators/xml/helpers/XmlSchemaHelpers.java
> (working copy)
> @@ -510,8 +510,8 @@
> */
> if (refType.isPrimitive()
> || refType.getPackage().equalsIgnoreCase("primitive")
> - || "java.lang.String".equalsIgnoreCase(refType
> - .getFullyQualifiedName())) {
> + ||
> "java.lang.String".equalsIgnoreCase(refType.getFullyQualifiedName())
> + ||
> "String".equalsIgnoreCase(refType.getFullyQualifiedName())) { //
> tigerstripe 1.7.0 now generates String and not java.lang.String
> PluginLog.logDebug("\'" + refTypeFullName
> + "\' is a primitive type in current TIP profile.");
> type = mapPrimitivesToXsdType(refType.getName(),
> isArray(refType),
> @@ -519,7 +519,7 @@
> }
>
> /**
> - * Map datatyeps and enumerations
> + * Map datatypes and enumerations
> */
> // if (refType.isDatatype() || refType.isEnum()
> else if (isDatatype(refType) || isEnumeration(refType)) {
> Index:
> src/org/eclipse/tigerstripe/generators/xml/helpers/XsdReferencesMgr.java
> ===================================================================
> ---
> src/org/eclipse/tigerstripe/generators/xml/helpers/XsdReferencesMgr.java
> (revision 3453)
> +++
> src/org/eclipse/tigerstripe/generators/xml/helpers/XsdReferencesMgr.java
> (working copy)
> @@ -170,8 +170,9 @@
> private void addReferencedPackage(IType type) {
>
> if (type.isPrimitive()
> - || "primitive".equalsIgnoreCase(type.getPackage()) ||
> -
> "java.lang.String".equalsIgnoreCase(type.getFullyQualifiedName())) {
> + || "primitive".equalsIgnoreCase(type.getPackage())
> + ||
> "java.lang.String".equalsIgnoreCase(type.getFullyQualifiedName())
> + ||
> "String".equalsIgnoreCase(type.getFullyQualifiedName())) { //
> tigerstripe 1.7.0 now generates String and not java.lang.String
> //will map objectName to EntityIdentifier or
> ArrayOfEntityIdentifier
> if ("objectName".equalsIgnoreCase(type.getName())){
> PluginLog.logDebug("type \'" + type
> @@ -378,8 +379,8 @@
> */
> if (refType.isPrimitive()
> || refType.getPackage().equalsIgnoreCase("primitive")
> - || "java.lang.String".equalsIgnoreCase(refType
> - .getFullyQualifiedName())) {
> + ||
> "java.lang.String".equalsIgnoreCase(refType.getFullyQualifiedName())
> + ||
> "String".equalsIgnoreCase(refType.getFullyQualifiedName())) { //
> tigerstripe 1.7.0 now generates String and not java.lang.String
> PluginLog.logDebug("\'" + typeName
> + "\' is a primitive type in current TIP profile.");
>
>
>
>
>
>
>
> On 11/06/2012 12:35, Xose Ramon Sousa Vazquez wrote:
>
> Hi all. I think that I have found the error and I will try to fix it
> as soon as possible. There are some related issues, one error in the
> codification of a method and a forgetted evaluation of filtering in
> the velocity template and also a case related with primitive type
> filter not supported in the build of the closure outside the interfaces.
>
> In the interfaces build the search is performed as follows(this works
> fine as reported Marc):
>
> if ("objectName".equalsIgnoreCase(argType.getName())) {
> /*
> * This data type 'objectName' defines the
> protocol
> * neutral unique name of an object. This data
> type will
> * be replaced by the generators by an
> EntityIdentifier
> */
> String pkg = PluginConstants
>
> .getPropVal(PluginConstants.KEY_INTERNAL_MODEL_PKG);
> if (!this.map.containsKey(pkg)) {
> //
> // New package - add new pkg=prefix mapping
> // assignment
> //
> String prefix =
> XmlSchemaHelpers.generateXmlPrefix(
> pkg, this.map);
> this.map.put(pkg, prefix);
> }
> } else if
> ("filter".equalsIgnoreCase(argType.getName())) {
> /*
> * This data type 'filter'. This data type will
> * be replaced by the generator to
> */
> String pkg = PluginConstants
>
> .getPropVal(PluginConstants.KEY_INTERNAL_FILTER_PKG);
> if (!this.map.containsKey(pkg)) {
> //
> // New package - add new pkg=prefix mapping
> // assignment
> //
> String prefix =
> XmlSchemaHelpers.generateXmlPrefix(
> pkg, this.map);
> this.map.put(pkg, prefix);
> }
> } else if (XmlSchemaHelpers.isUnbounded(argType)) {
> String pkg = PluginConstants
>
> .getPropVal(PluginConstants.KEY_INTERNAL_MODEL_PRIMITIVES_PKG);
> if (!this.map.containsKey(pkg)) {
> //
> // New package - add new pkg=prefix mapping
> // assignment
> //
> String prefix =
> XmlSchemaHelpers.generateXmlPrefix(
> pkg, this.map);
> this.map.put(pkg, prefix);
> }
> } else {
> // XSD default namespace is enough
> }
>
> and in the build of the closure we have got (this fails as reported
> Craig):
>
> if ("objectName".equalsIgnoreCase(type.getName())){
> PluginLog.logDebug("type \'" + type
> + "\' is an array of primitive.");
> addReferencedPackage(PluginConstants
> .getPropVal(PluginConstants.KEY_INTERNAL_MODEL_PKG));
> }else if (XmlSchemaHelpers.isUnbounded(type)){
> //will map to array of primitive
> addReferencedPackage(PluginConstants
>
> .getPropVal(PluginConstants.KEY_INTERNAL_MODEL_PRIMITIVES_PKG));
> } else {
> //normal primtive like xsd:int
> }
>
> so the filtering never is considered.
>
> I will perform clean tests because was very difficult to find the real
> cause of the problem, the log file is not very clear in debug
> scenarios ( a lot of similar log text, no log from the templates and
> also cannot put the line number in the log file (tigerstripe issue))
> and these problems have delayed my response.
> If the test go ok I will check out the changes to the trunk
>
> https://openoss.svn.sourceforge.net/svnroot/openoss/tip/framework/TIP_Soap_Generator/trunk/TIP_Soap_Generator
>
> Best regards
>
>
> El 01/06/2012 16:58, Craig Gallen escribió:
>
> Hi,
>
> I agree it is defined in internal_filter.xsd but it doesn't seem to be
> referenced properly from dep_cbe_perf_spec.xsd in the PM project. WSDL2Java
> throws an error and when you open dep_cbe_perf_spec.xsd in eclipse it also
> shows an error.
>
> I think Xose is looking into it
>
> Craig
>
> -----Original Message-----
> From: Flauw, Marc [mailto:Mar...@hp...]
> Sent: 01 June 2012 10:25
> To: Craig Gallen (opennms); openoss-devel; Xose Ramon Sousa Vazquez; pierre
> gauthier
> Subject: RE: Problems with PM XSD generation
>
> Craig,
>
> There is one same filter in the getReosurceAlarms operation, filter
> argument.
> The XPathFilter is defined in the internal_filter.xsd
>
> Best regards
>
> Marc
>
> -----Original Message-----
> From: Craig Gallen [mailto:gal...@go...] On Behalf Of Craig
> Gallen (opennms)
> Sent: Thursday, May 31, 2012 11:58 PM
> To: openoss-devel; Flauw, Marc; Xose Ramon Sousa Vazquez; pierre gauthier
> Subject: Problems with PM XSD generation
>
> Hi,
>
> I have been testing the TIP_PM_Col project model and have found that the
> dep_cbe_perf_spec.xsd (attached) file is generated with errors
>
> in line 62 we have
> <xsd:element name="objectInstanceFilter" type="filter:XPathQueryFilter"
> minOccurs="0" maxOccurs="1">
>
> filter:XPathQueryFilter is not defined and if you open the file in eclipse
> it reports this error as:
>
> 's4s-att-invalid-value: Invalid attribute value for 'type' in element
> 'element'. Recorded reason:
> UndeclaredPrefix: Cannot resolve 'filter:XPathQueryFilter' as a QName:
> the prefix 'filter' is not
> declared'.
>
> Is this a known problem or a new bug?
>
> Craig
>
>
> --
>
> *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: Craig G. (opennms) <cg...@op...> - 2012-06-25 15:51:47
|
-------- Original Message --------
Subject: Re: Problems with PM XSD generation
Date: Mon, 25 Jun 2012 15:54:32 +0100
From: Craig Gallen (entimoss) <cra...@en...>
Organisation: Entmoss Ltd
To: Xose Ramon Sousa Vazquez <xr...@op...>
CC: 'Flauw, Marc' <Mar...@hp...>, 'Craig Gallen (opennms)'
<cg...@op...>, 'openoss-devel'
<ope...@li...>, 'pierre gauthier'
<pie...@os...>
Hi Xose,
I just updated my tigerstripe to the latest release 0.7.0.20120618258
but Ialso updated the Soap plug-in and have found multiple problems but
I am not sure if they are all related to the tigerstripe upgrade or to
the current state of the soap plugin. Could you build the RAM project
and check the generated XSD's to see the problem.
1. when you build the RAM project there is a problem with model
closure. None of the Dependency XSD's get generated in the RAM_Model
project
2. TrackingRecordResultWithIterator referenced as
'problem:TrackingRecordResultWithIterator' in
ram_resource_trouble_alarm_resourcealarmretrievalservice_msg.xsd is
never generated.
3. Tigerstripe 0.7.0.20120618258. handles primitive.string differently
and generates type 'String' instead of 'java.lang.String' this results
in type :String instead of xsd:string. I did a quick fix given in the
following patch adding
|| "String".equalsIgnoreCase(refType.getFullyQualifiedName()))
to
|| "java.lang.String".equalsIgnoreCase(refType.getFullyQualifiedName())
this means that old and new versions of tigerstipe will work
There is a patch below but havent checked this in because I was not
sure that else you were doing to the Soap plugin
Craig
### Eclipse Workspace Patch 1.0
#P TIP_Soap_Generator
Index:
src/org/eclipse/tigerstripe/generators/xml/helpers/XmlSchemaHelpers.java
===================================================================
---
src/org/eclipse/tigerstripe/generators/xml/helpers/XmlSchemaHelpers.java
(revision 3453)
+++
src/org/eclipse/tigerstripe/generators/xml/helpers/XmlSchemaHelpers.java
(working copy)
@@ -510,8 +510,8 @@
*/
if (refType.isPrimitive()
|| refType.getPackage().equalsIgnoreCase("primitive")
- || "java.lang.String".equalsIgnoreCase(refType
- .getFullyQualifiedName())) {
+ ||
"java.lang.String".equalsIgnoreCase(refType.getFullyQualifiedName())
+ ||
"String".equalsIgnoreCase(refType.getFullyQualifiedName())) { //
tigerstripe 1.7.0 now generates String and not java.lang.String
PluginLog.logDebug("\'" + refTypeFullName
+ "\' is a primitive type in current TIP profile.");
type = mapPrimitivesToXsdType(refType.getName(),
isArray(refType),
@@ -519,7 +519,7 @@
}
/**
- * Map datatyeps and enumerations
+ * Map datatypes and enumerations
*/
// if (refType.isDatatype() || refType.isEnum()
else if (isDatatype(refType) || isEnumeration(refType)) {
Index:
src/org/eclipse/tigerstripe/generators/xml/helpers/XsdReferencesMgr.java
===================================================================
---
src/org/eclipse/tigerstripe/generators/xml/helpers/XsdReferencesMgr.java
(revision 3453)
+++
src/org/eclipse/tigerstripe/generators/xml/helpers/XsdReferencesMgr.java
(working copy)
@@ -170,8 +170,9 @@
private void addReferencedPackage(IType type) {
if (type.isPrimitive()
- || "primitive".equalsIgnoreCase(type.getPackage()) ||
-
"java.lang.String".equalsIgnoreCase(type.getFullyQualifiedName())) {
+ || "primitive".equalsIgnoreCase(type.getPackage())
+ ||
"java.lang.String".equalsIgnoreCase(type.getFullyQualifiedName())
+ ||
"String".equalsIgnoreCase(type.getFullyQualifiedName())) { //
tigerstripe 1.7.0 now generates String and not java.lang.String
//will map objectName to EntityIdentifier or
ArrayOfEntityIdentifier
if ("objectName".equalsIgnoreCase(type.getName())){
PluginLog.logDebug("type \'" + type
@@ -378,8 +379,8 @@
*/
if (refType.isPrimitive()
|| refType.getPackage().equalsIgnoreCase("primitive")
- || "java.lang.String".equalsIgnoreCase(refType
- .getFullyQualifiedName())) {
+ ||
"java.lang.String".equalsIgnoreCase(refType.getFullyQualifiedName())
+ ||
"String".equalsIgnoreCase(refType.getFullyQualifiedName())) { //
tigerstripe 1.7.0 now generates String and not java.lang.String
PluginLog.logDebug("\'" + typeName
+ "\' is a primitive type in current TIP profile.");
On 11/06/2012 12:35, Xose Ramon Sousa Vazquez wrote:
> Hi all. I think that I have found the error and I will try to fix it
> as soon as possible. There are some related issues, one error in the
> codification of a method and a forgetted evaluation of filtering in
> the velocity template and also a case related with primitive type
> filter not supported in the build of the closure outside the interfaces.
>
> In the interfaces build the search is performed as follows(this works
> fine as reported Marc):
>
> if ("objectName".equalsIgnoreCase(argType.getName())) {
> /*
> * This data type 'objectName' defines the
> protocol
> * neutral unique name of an object. This
> data type will
> * be replaced by the generators by an
> EntityIdentifier
> */
> String pkg = PluginConstants
>
> .getPropVal(PluginConstants.KEY_INTERNAL_MODEL_PKG);
> if (!this.map.containsKey(pkg)) {
> //
> // New package - add new pkg=prefix
> mapping
> // assignment
> //
> String prefix =
> XmlSchemaHelpers.generateXmlPrefix(
> pkg, this.map);
> this.map.put(pkg, prefix);
> }
> } else if
> ("filter".equalsIgnoreCase(argType.getName())) {
> /*
> * This data type 'filter'. This data type
> will
> * be replaced by the generator to
> */
> String pkg = PluginConstants
>
> .getPropVal(PluginConstants.KEY_INTERNAL_FILTER_PKG);
> if (!this.map.containsKey(pkg)) {
> //
> // New package - add new pkg=prefix
> mapping
> // assignment
> //
> String prefix =
> XmlSchemaHelpers.generateXmlPrefix(
> pkg, this.map);
> this.map.put(pkg, prefix);
> }
> } else if
> (XmlSchemaHelpers.isUnbounded(argType)) {
> String pkg = PluginConstants
>
> .getPropVal(PluginConstants.KEY_INTERNAL_MODEL_PRIMITIVES_PKG);
> if (!this.map.containsKey(pkg)) {
> //
> // New package - add new pkg=prefix
> mapping
> // assignment
> //
> String prefix =
> XmlSchemaHelpers.generateXmlPrefix(
> pkg, this.map);
> this.map.put(pkg, prefix);
> }
> } else {
> // XSD default namespace is enough
> }
>
> and in the build of the closure we have got (this fails as reported
> Craig):
>
> if ("objectName".equalsIgnoreCase(type.getName())){
> PluginLog.logDebug("type \'" + type
> + "\' is an array of primitive.");
> addReferencedPackage(PluginConstants
>
> .getPropVal(PluginConstants.KEY_INTERNAL_MODEL_PKG));
> }else if (XmlSchemaHelpers.isUnbounded(type)){
> //will map to array of primitive
> addReferencedPackage(PluginConstants
>
> .getPropVal(PluginConstants.KEY_INTERNAL_MODEL_PRIMITIVES_PKG));
> } else {
> //normal primtive like xsd:int
> }
>
> so the filtering never is considered.
>
> I will perform clean tests because was very difficult to find the real
> cause of the problem, the log file is not very clear in debug
> scenarios ( a lot of similar log text, no log from the templates and
> also cannot put the line number in the log file (tigerstripe issue))
> and these problems have delayed my response.
> If the test go ok I will check out the changes to the trunk
>
> https://openoss.svn.sourceforge.net/svnroot/openoss/tip/framework/TIP_Soap_Generator/trunk/TIP_Soap_Generator
>
> Best regards
>
>
> El 01/06/2012 16:58, Craig Gallen escribió:
>> Hi,
>>
>> I agree it is defined in internal_filter.xsd but it doesn't seem to be
>> referenced properly from dep_cbe_perf_spec.xsd in the PM project. WSDL2Java
>> throws an error and when you open dep_cbe_perf_spec.xsd in eclipse it also
>> shows an error.
>>
>> I think Xose is looking into it
>>
>> Craig
>>
>> -----Original Message-----
>> From: Flauw, Marc [mailto:Mar...@hp...]
>> Sent: 01 June 2012 10:25
>> To: Craig Gallen (opennms); openoss-devel; Xose Ramon Sousa Vazquez; pierre
>> gauthier
>> Subject: RE: Problems with PM XSD generation
>>
>> Craig,
>>
>> There is one same filter in the getReosurceAlarms operation, filter
>> argument.
>> The XPathFilter is defined in the internal_filter.xsd
>>
>> Best regards
>>
>> Marc
>>
>> -----Original Message-----
>> From: Craig Gallen [mailto:gal...@go...] On Behalf Of Craig
>> Gallen (opennms)
>> Sent: Thursday, May 31, 2012 11:58 PM
>> To: openoss-devel; Flauw, Marc; Xose Ramon Sousa Vazquez; pierre gauthier
>> Subject: Problems with PM XSD generation
>>
>> Hi,
>>
>> I have been testing the TIP_PM_Col project model and have found that the
>> dep_cbe_perf_spec.xsd (attached) file is generated with errors
>>
>> in line 62 we have
>> <xsd:element name="objectInstanceFilter" type="filter:XPathQueryFilter"
>> minOccurs="0" maxOccurs="1">
>>
>> filter:XPathQueryFilter is not defined and if you open the file in eclipse
>> it reports this error as:
>>
>> 's4s-att-invalid-value: Invalid attribute value for 'type' in element
>> 'element'. Recorded reason:
>> UndeclaredPrefix: Cannot resolve 'filter:XPathQueryFilter' as a QName:
>> the prefix 'filter' is not
>> declared'.
>>
>> Is this a known problem or a new bug?
>>
>> Craig
>>
>
>
> --
>
> *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><http://optarecoolvendor.com>
>
|
|
From: Xose R. S. V. <xr...@op...> - 2012-06-25 15:03:50
|
Hi Craig, when you talk about the updated Soap Plugin, which version (in
svn url) are using?, because the two first issues seems to be solved in
the trunk with the other Tigerstripe version.
Regards
El 25/06/2012 16:54, Craig Gallen (entimoss) escribió:
> Hi Xose,
>
> I just updated my tigerstripe to the latest release 0.7.0.20120618258
> but Ialso updated the Soap plug-in and have found multiple problems
> but I am not sure if they are all related to the tigerstripe upgrade
> or to the current state of the soap plugin. Could you build the RAM
> project and check the generated XSD's to see the problem.
>
> 1. when you build the RAM project there is a problem with model
> closure. None of the Dependency XSD's get generated in the RAM_Model
> project
>
> 2. TrackingRecordResultWithIterator referenced as
> 'problem:TrackingRecordResultWithIterator' in
> ram_resource_trouble_alarm_resourcealarmretrievalservice_msg.xsd is
> never generated.
>
> 3. Tigerstripe 0.7.0.20120618258. handles primitive.string differently
> and generates type 'String' instead of 'java.lang.String' this results
> in type :String instead of xsd:string. I did a quick fix given in the
> following patch adding
> || "String".equalsIgnoreCase(refType.getFullyQualifiedName()))
>
> to
> || "java.lang.String".equalsIgnoreCase(refType.getFullyQualifiedName())
> this means that old and new versions of tigerstipe will work
>
> There is a patch below but havent checked this in because I was not
> sure that else you were doing to the Soap plugin
>
> Craig
>
>
>
> ### Eclipse Workspace Patch 1.0
> #P TIP_Soap_Generator
> Index:
> src/org/eclipse/tigerstripe/generators/xml/helpers/XmlSchemaHelpers.java
> ===================================================================
> ---
> src/org/eclipse/tigerstripe/generators/xml/helpers/XmlSchemaHelpers.java
> (revision 3453)
> +++
> src/org/eclipse/tigerstripe/generators/xml/helpers/XmlSchemaHelpers.java
> (working copy)
> @@ -510,8 +510,8 @@
> */
> if (refType.isPrimitive()
> || refType.getPackage().equalsIgnoreCase("primitive")
> - || "java.lang.String".equalsIgnoreCase(refType
> - .getFullyQualifiedName())) {
> + ||
> "java.lang.String".equalsIgnoreCase(refType.getFullyQualifiedName())
> + ||
> "String".equalsIgnoreCase(refType.getFullyQualifiedName())) { //
> tigerstripe 1.7.0 now generates String and not java.lang.String
> PluginLog.logDebug("\'" + refTypeFullName
> + "\' is a primitive type in current TIP profile.");
> type = mapPrimitivesToXsdType(refType.getName(),
> isArray(refType),
> @@ -519,7 +519,7 @@
> }
>
> /**
> - * Map datatyeps and enumerations
> + * Map datatypes and enumerations
> */
> // if (refType.isDatatype() || refType.isEnum()
> else if (isDatatype(refType) || isEnumeration(refType)) {
> Index:
> src/org/eclipse/tigerstripe/generators/xml/helpers/XsdReferencesMgr.java
> ===================================================================
> ---
> src/org/eclipse/tigerstripe/generators/xml/helpers/XsdReferencesMgr.java
> (revision 3453)
> +++
> src/org/eclipse/tigerstripe/generators/xml/helpers/XsdReferencesMgr.java
> (working copy)
> @@ -170,8 +170,9 @@
> private void addReferencedPackage(IType type) {
>
> if (type.isPrimitive()
> - || "primitive".equalsIgnoreCase(type.getPackage()) ||
> -
> "java.lang.String".equalsIgnoreCase(type.getFullyQualifiedName())) {
> + || "primitive".equalsIgnoreCase(type.getPackage())
> + ||
> "java.lang.String".equalsIgnoreCase(type.getFullyQualifiedName())
> + ||
> "String".equalsIgnoreCase(type.getFullyQualifiedName())) { //
> tigerstripe 1.7.0 now generates String and not java.lang.String
> //will map objectName to EntityIdentifier or
> ArrayOfEntityIdentifier
> if ("objectName".equalsIgnoreCase(type.getName())){
> PluginLog.logDebug("type \'" + type
> @@ -378,8 +379,8 @@
> */
> if (refType.isPrimitive()
> || refType.getPackage().equalsIgnoreCase("primitive")
> - || "java.lang.String".equalsIgnoreCase(refType
> - .getFullyQualifiedName())) {
> + ||
> "java.lang.String".equalsIgnoreCase(refType.getFullyQualifiedName())
> + ||
> "String".equalsIgnoreCase(refType.getFullyQualifiedName())) { //
> tigerstripe 1.7.0 now generates String and not java.lang.String
> PluginLog.logDebug("\'" + typeName
> + "\' is a primitive type in current TIP profile.");
>
>
>
>
>
>
>
> On 11/06/2012 12:35, Xose Ramon Sousa Vazquez wrote:
>> Hi all. I think that I have found the error and I will try to fix it
>> as soon as possible. There are some related issues, one error in the
>> codification of a method and a forgetted evaluation of filtering in
>> the velocity template and also a case related with primitive type
>> filter not supported in the build of the closure outside the interfaces.
>>
>> In the interfaces build the search is performed as follows(this works
>> fine as reported Marc):
>>
>> if ("objectName".equalsIgnoreCase(argType.getName())) {
>> /*
>> * This data type 'objectName' defines
>> the protocol
>> * neutral unique name of an object. This
>> data type will
>> * be replaced by the generators by an
>> EntityIdentifier
>> */
>> String pkg = PluginConstants
>>
>> .getPropVal(PluginConstants.KEY_INTERNAL_MODEL_PKG);
>> if (!this.map.containsKey(pkg)) {
>> //
>> // New package - add new pkg=prefix
>> mapping
>> // assignment
>> //
>> String prefix =
>> XmlSchemaHelpers.generateXmlPrefix(
>> pkg, this.map);
>> this.map.put(pkg, prefix);
>> }
>> } else if
>> ("filter".equalsIgnoreCase(argType.getName())) {
>> /*
>> * This data type 'filter'. This data
>> type will
>> * be replaced by the generator to
>> */
>> String pkg = PluginConstants
>>
>> .getPropVal(PluginConstants.KEY_INTERNAL_FILTER_PKG);
>> if (!this.map.containsKey(pkg)) {
>> //
>> // New package - add new pkg=prefix
>> mapping
>> // assignment
>> //
>> String prefix =
>> XmlSchemaHelpers.generateXmlPrefix(
>> pkg, this.map);
>> this.map.put(pkg, prefix);
>> }
>> } else if
>> (XmlSchemaHelpers.isUnbounded(argType)) {
>> String pkg = PluginConstants
>>
>> .getPropVal(PluginConstants.KEY_INTERNAL_MODEL_PRIMITIVES_PKG);
>> if (!this.map.containsKey(pkg)) {
>> //
>> // New package - add new pkg=prefix
>> mapping
>> // assignment
>> //
>> String prefix =
>> XmlSchemaHelpers.generateXmlPrefix(
>> pkg, this.map);
>> this.map.put(pkg, prefix);
>> }
>> } else {
>> // XSD default namespace is enough
>> }
>>
>> and in the build of the closure we have got (this fails as reported
>> Craig):
>>
>> if ("objectName".equalsIgnoreCase(type.getName())){
>> PluginLog.logDebug("type \'" + type
>> + "\' is an array of primitive.");
>> addReferencedPackage(PluginConstants
>>
>> .getPropVal(PluginConstants.KEY_INTERNAL_MODEL_PKG));
>> }else if (XmlSchemaHelpers.isUnbounded(type)){
>> //will map to array of primitive
>> addReferencedPackage(PluginConstants
>>
>> .getPropVal(PluginConstants.KEY_INTERNAL_MODEL_PRIMITIVES_PKG));
>> } else {
>> //normal primtive like xsd:int
>> }
>>
>> so the filtering never is considered.
>>
>> I will perform clean tests because was very difficult to find the
>> real cause of the problem, the log file is not very clear in debug
>> scenarios ( a lot of similar log text, no log from the templates and
>> also cannot put the line number in the log file (tigerstripe issue))
>> and these problems have delayed my response.
>> If the test go ok I will check out the changes to the trunk
>>
>> https://openoss.svn.sourceforge.net/svnroot/openoss/tip/framework/TIP_Soap_Generator/trunk/TIP_Soap_Generator
>>
>> Best regards
>>
>>
>> El 01/06/2012 16:58, Craig Gallen escribió:
>>> Hi,
>>>
>>> I agree it is defined in internal_filter.xsd but it doesn't seem to be
>>> referenced properly from dep_cbe_perf_spec.xsd in the PM project. WSDL2Java
>>> throws an error and when you open dep_cbe_perf_spec.xsd in eclipse it also
>>> shows an error.
>>>
>>> I think Xose is looking into it
>>>
>>> Craig
>>>
>>> -----Original Message-----
>>> From: Flauw, Marc [mailto:Mar...@hp...]
>>> Sent: 01 June 2012 10:25
>>> To: Craig Gallen (opennms); openoss-devel; Xose Ramon Sousa Vazquez; pierre
>>> gauthier
>>> Subject: RE: Problems with PM XSD generation
>>>
>>> Craig,
>>>
>>> There is one same filter in the getReosurceAlarms operation, filter
>>> argument.
>>> The XPathFilter is defined in the internal_filter.xsd
>>>
>>> Best regards
>>>
>>> Marc
>>>
>>> -----Original Message-----
>>> From: Craig Gallen [mailto:gal...@go...] On Behalf Of Craig
>>> Gallen (opennms)
>>> Sent: Thursday, May 31, 2012 11:58 PM
>>> To: openoss-devel; Flauw, Marc; Xose Ramon Sousa Vazquez; pierre gauthier
>>> Subject: Problems with PM XSD generation
>>>
>>> Hi,
>>>
>>> I have been testing the TIP_PM_Col project model and have found that the
>>> dep_cbe_perf_spec.xsd (attached) file is generated with errors
>>>
>>> in line 62 we have
>>> <xsd:element name="objectInstanceFilter" type="filter:XPathQueryFilter"
>>> minOccurs="0" maxOccurs="1">
>>>
>>> filter:XPathQueryFilter is not defined and if you open the file in eclipse
>>> it reports this error as:
>>>
>>> 's4s-att-invalid-value: Invalid attribute value for 'type' in element
>>> 'element'. Recorded reason:
>>> UndeclaredPrefix: Cannot resolve 'filter:XPathQueryFilter' as a QName:
>>> the prefix 'filter' is not
>>> declared'.
>>>
>>> Is this a known problem or a new bug?
>>>
>>> Craig
>>>
>>
>>
>> --
>>
>> *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><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><http://optarecoolvendor.com>
|
|
From: Flauw, M. <Mar...@hp...> - 2012-06-22 16:52:47
|
_______________________________________________ tigerstripe-dev mailing list tig...@ec... https://dev.eclipse.org/mailman/listinfo/tigerstripe-dev |
|
From: Flauw, M. <Mar...@hp...> - 2012-06-21 10:02:37
|
_______________________________________________ tigerstripe-dev mailing list tig...@ec... https://dev.eclipse.org/mailman/listinfo/tigerstripe-dev |
|
From: Flauw, M. <Mar...@hp...> - 2012-06-21 06:10:01
|
Hi Amshu, I know that you have been working also on these regression tests. Can you help Kumar? Thanks Marc From: man...@gm... [mailto:man...@gm...] On Behalf Of Manikumar Reddy Sent: Thursday, June 21, 2012 7:50 AM To: Flauw, Marc Cc: Pierre Gauthier; Craig Gallen (entimoss); Tina O Sullivan; Craig Gallen (OpenNMS); openoss-devel Subject: Re: [Openoss-devel] TIP Build Task updates and regression Hi Marc, I tried to build the Test projects again. I have not done any changes to these modules. Just checked out modules and gave maven commands. I used latest TIP Workbench Installer 1.1.1 to create workspace. Results are given below: Test1: Build is failing during TIP_Fmk_Test1_Model Stage. Pl find attached logs. Errors are coming during TigerStripe run. Do I need to recreate module with latest project creator? Test2: Build was successful with few errors. pl find attached logs. Test3: Errors are coming during TigerStripe run. pl find attached logs. Test4 and Test5: Yet to be done. And also, workspace is getting corrupted for some Tigerstripe exceptions and builds are failing. Regards, Kumar On Thu, Jun 14, 2012 at 11:23 AM, Flauw, Marc <Mar...@hp...<mailto:Mar...@hp...>> wrote: Hi Kumar, Thanks for the message. On Test1, were you doing the eclipse:eclipse or the clean install? Try doing the latter and usually, it goes away. On Test2, sometimes the build blocks in Tigerstripe. Usually what I do is the following: 1) remove velocity.log.* in Dependencies and model projects 2) remove the .lock and .snap in metadata. There is a an eclipse article on that, but if you cannot find it, I can dig detailed instructions. 3) do the mvn clean first 4) then do the mvn install. This way if the build blocks, you might restart it without to redo the clean steps, just doing steps 1 and 2 On Test3, it would be good to have the log. This is a test with unknown datatype, so the build should fail, but the error message is surprising. On Test4, it looks like the pom file has not been updated and it is looking for an old version of the generator. Aligning pom files with the latest ones from project creator should solve that. On Test5, you need to ask Xose. For me, it is still work in progress, so I won't worry about this one for time being. Best regards Marc From: man...@gm...<mailto:man...@gm...> [mailto:man...@gm...<mailto:man...@gm...>] On Behalf Of Manikumar Reddy Sent: Wednesday, June 13, 2012 9:39 PM To: Pierre Gauthier; Craig Gallen (entimoss) Cc: Tina O Sullivan; openoss-devel; Flauw, Marc; Craig Gallen (OpenNMS) Subject: Re: TIP Build Task updates and regression Hi > > For instance all the TIP_Fmk_Test1 project modules are all in https://openoss.svn.sourceforge.net/svnroot/openoss/tip/framework/TIP_Fmk_TestProjects/TIP_Fmk_Test1/trunk/ > > You may want to and do a manual tigerstripe generation of the model and dependency projects from the desktop. > Follow the getting started instructions to do a maven build. There are total five Framework Test projects. I tried to do maven build for these projects. But all these builds failed. The following errors occurred. TIP_Fmk_Test1: Missing: ---------- 1) org.tmforum.tip:TIP_Fmk_Test1_JvtSpecPackage:jar:1.1.2-SNAPSHOT TIP_Fmk_Test2: Build process is not responding. TIP_Fmk_Test3: [exec] Tigerstripe Workbench Base Plug-in (Incubation) (v0.6.935.2011020109 [exec] Active Profile: TIP_Profile 1.1.1 [exec] null [exec] java.lang.NullPointerException [exec] at org.eclipse.tigerstripe.workbench.internal.core.project.Tiger stripeProject.addDependency(TigerstripeProject.java:674) TIP_Fmk_Test4: [INFO] Unable to find artifact. Embedded error: Unable to download the artifact from any repository org.tmforum.tip:TIP_Doc_Generator_Package:jar:1.0.2 TIP_Fmk_Test5: [exec] [Fatal Error] :1:1: Premature end of file. [exec] Tigerstripe Workbench Base Plug-in (Incubation) (v0.6.935.2011020 [exec] Active Profile: TIP_Profile 1.1.1 [exec] null [exec] java.util.ConcurrentModificationException [exec] at java.util.AbstractList$Itr.checkForComodification(Unknown source) Details logs attached. > If this fails, we will need to find out what is wrong with the model relative to the new generators. I need your help in fixing above problems. > > Regardless of any problems with the generators you should still update the project build files as describe below I was able to create Fmk_Test1 project using project creator. > 6. compare and bring up to date each module in your main project > - update the project pom.xml to match the misc pom.xml I have merged pom files of all modules. Some conflicting lines i just copied to trunk project. > - update any resources / java file which are changed in the misc project > - remove any resources / java files or packages from the trunk which don't exist in the new 'misc' project > - add any new resources / java files or packages which don't exist in the 'trunk' project After updating all the projects, i ran maven build ( Without Java modules). Maven build process is not responding after some time, Below is the log trace. Any clue? [INFO] [antrun:run {execution: run-tigerstripe}] [INFO] Executing tasks [echo] MODEL_POM: eclipse_home: D:\eclipsets [echo] MODEL_POM: model_project_basedir: D:\ws-ts\TIP_Fmk_Test1_Model [echo] MODEL_POM: model_project__directory_name: TIP_Fmk_Test1_Model [echo] MODEL_POM: tigerstripe_workspace: D:\ws-ts [echo] MODEL_POM: referenced_project1: TIP_Fmk_Test1_Model [echo] MODEL_POM: tigerstripe_generation_project: TIP_Fmk_Test1_Model [echo] MODEL_POM: tigerstripe_arg_string: -nosplash -data D:\ws-ts -applica tion org.eclipse.tigerstripe.workbench.headless.tigerstripe D:\ws-ts\TIP_Fmk_Tes t1_Model GENERATION_PROJECT=D:\ws-ts\TIP_Fmk_Test1_Model [echo] MODEL_POM: D:\ws-ts\TIP_Fmk_Test1_Model\target\CODE_GENERATED_FLAG.t xt does not exist. Will run Tigerstripe Regards Kumar NMSWorks Software Pvt Ltd. +919840241620 ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Openoss-devel mailing list Ope...@li...<mailto:Ope...@li...> https://lists.sourceforge.net/lists/listinfo/openoss-devel |
|
From: Manikumar R. <ku...@nm...> - 2012-06-21 05:50:27
|
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] TIP_Fmk_Test1_BaseProject
[INFO] TIP_Fmk_Test1_Dependencies
[INFO] TIP_Fmk_Test1_Model
[INFO] TIP_Fmk_Test1_JvtSpecPackage
[INFO] TIP_Fmk_Test1_EjbImplGenSrcPackage
[INFO] ------------------------------------------------------------------------
[INFO] Building TIP_Fmk_Test1_BaseProject
[INFO] task-segment: [clean, install]
[INFO] ------------------------------------------------------------------------
[INFO] [clean:clean {execution: default-clean}]
[INFO] [site:attach-descriptor {execution: default-attach-descriptor}]
[INFO] [install:install {execution: default-install}]
[INFO] Installing C:\ws-tsnew\TIP_Fmk_Test1_BaseProject\pom.xml to C:\Users\kumar\.m2\repository\org\openoss\tip\TIP_Fmk_Test1_BaseProject\1.1.2-SNAPSHOT\TIP_Fmk_Test1_BaseProject-1.1.2-SNAPSHOT.pom
[INFO] ------------------------------------------------------------------------
[INFO] Building TIP_Fmk_Test1_Dependencies
[INFO] task-segment: [clean, install]
[INFO] ------------------------------------------------------------------------
[INFO] [clean:clean {execution: default-clean}]
[INFO] Deleting directory C:\ws-tsnew\TIP_Fmk_Test1_Dependencies\target
[INFO] [properties:read-project-properties {execution: default}]
[INFO] [dependency:unpack {execution: download model dependencies and tigerstripe plugins}]
[INFO] Configured Artifact: org.tmforum.tip:TIP_Doc_Generator_Package:?:jar
[INFO] Configured Artifact: org.tmforum.tip:TIP_Soap_Generator_Package:?:jar
[INFO] Configured Artifact: org.tmforum.tip:TIP_Profile_Package:?:jar
[INFO] Configured Artifact: org.tmforum.tip:TIP_JvtSpec_Generator_Package:?:jar
[INFO] Configured Artifact: org.openoss.tip:TIP_EjbImpl_Generator_Package:?:jar
[INFO] Configured Artifact: org.tmforum.tip:TIP_Common_Model_Package:?:jar
[INFO] Unpacking C:\Users\kumar\.m2\repository\org\tmforum\tip\TIP_Doc_Generator_Package\1.1.2-SNAPSHOT\TIP_Doc_Generator_Package-1.1.2-SNAPSHOT.jarto
C:\ws-tsnew\TIP_Fmk_Test1_Dependencies\TigerstripeGenerators
with Includes null and excludes:null
[INFO] Unpacking C:\Users\kumar\.m2\repository\org\tmforum\tip\TIP_Soap_Generator_Package\1.1.2-SNAPSHOT\TIP_Soap_Generator_Package-1.1.2-SNAPSHOT.jarto
C:\ws-tsnew\TIP_Fmk_Test1_Dependencies\TigerstripeGenerators
with Includes null and excludes:null
[INFO] Unpacking C:\Users\kumar\.m2\repository\org\tmforum\tip\TIP_Profile_Package\1.1.2-SNAPSHOT\TIP_Profile_Package-1.1.2-SNAPSHOT.jarto
C:\ws-tsnew\TIP_Fmk_Test1_Dependencies\TigerstripeGenerators
with Includes null and excludes:null
[INFO] Unpacking C:\Users\kumar\.m2\repository\org\tmforum\tip\TIP_JvtSpec_Generator_Package\1.1.2-SNAPSHOT\TIP_JvtSpec_Generator_Package-1.1.2-SNAPSHOT.jarto
C:\ws-tsnew\TIP_Fmk_Test1_Dependencies\TigerstripeGenerators
with Includes null and excludes:null
[INFO] Unpacking C:\Users\kumar\.m2\repository\org\openoss\tip\TIP_EjbImpl_Generator_Package\1.1.2-SNAPSHOT\TIP_EjbImpl_Generator_Package-1.1.2-SNAPSHOT.jarto
C:\ws-tsnew\TIP_Fmk_Test1_Dependencies\TigerstripeGenerators
with Includes null and excludes:null
[INFO] Unpacking C:\Users\kumar\.m2\repository\org\tmforum\tip\TIP_Common_Model_Package\1.1.2-SNAPSHOT\TIP_Common_Model_Package-1.1.2-SNAPSHOT.jarto
C:\ws-tsnew\TIP_Fmk_Test1_Dependencies
with Includes null and excludes:null
[INFO] [dependency:copy {execution: copy maven ant tasks jar from repo}]
[INFO] Configured Artifact: org.apache.maven:maven-ant-tasks:2.0.10:jar
[INFO] Copying maven-ant-tasks-2.0.10.jar to C:\ws-tsnew\TIP_Fmk_Test1_Dependencies\libs\maven-ant-tasks-2.0.10.jar
[INFO] [antrun:run {execution: run-tigerstripe}]
[INFO] Executing tasks
[echo] MODEL_POM: eclipse_home: C:\eclipsetsnew
[echo] MODEL_POM: model_project_basedir: C:\ws-tsnew\TIP_Fmk_Test1_Dependencies
[echo] MODEL_POM: model_project__directory_name: TIP_Fmk_Test1_Dependencies
[echo] MODEL_POM: tigerstripe_workspace: C:\ws-tsnew
[echo] MODEL_POM: referenced_project1: TIP_Fmk_Test1_Dependencies
[echo] MODEL_POM: tigerstripe_generation_project: TIP_Fmk_Test1_Dependencies
[echo] MODEL_POM: tigerstripe_arg_string: -nosplash -data C:\ws-tsnew -application org.eclipse.tigerstripe.workbench.headless.tigerstripe C:\ws-tsnew\TIP_Fmk_Test1_Dependencies GENERATION_PROJECT=C:\ws-tsnew\TIP_Fmk_Test1_Dependencies
[echo] MODEL_POM: C:\ws-tsnew\TIP_Fmk_Test1_Dependencies\target\CODE_GENERATED_FLAG.txt does not exist. Will run Tigerstripe
[exec] Tigerstripe Workbench Base Plug-in (Incubation) (v0.6.935.201102010903)
[exec] Active Profile: TIP_Profile 1.1.1
[exec] file:/C:/eclipsetsnew/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/classes/
[exec] file:/C:/eclipsetsnew/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/avalon-framework-4.2.0.jar
[exec] file:/C:/eclipsetsnew/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/batik-bridge.jar
[exec] file:/C:/eclipsetsnew/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/batik-css.jar
[exec] file:/C:/eclipsetsnew/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/batik-dom.jar
[exec] file:/C:/eclipsetsnew/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/batik-ext.jar
[exec] file:/C:/eclipsetsnew/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/batik-gui-util.jar
[exec] file:/C:/eclipsetsnew/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/batik-gvt.jar
[exec] file:/C:/eclipsetsnew/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/batik-svg-dom.jar
[exec] file:/C:/eclipsetsnew/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/batik-svggen.jar
[exec] file:/C:/eclipsetsnew/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/batik-util.jar
[exec] file:/C:/eclipsetsnew/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/batik-xml.jar
[exec] file:/C:/eclipsetsnew/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/commons-io-1.3.1.jar
[exec] file:/C:/eclipsetsnew/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/commons-lang-2.4_simplified.jar
[exec] file:/C:/eclipsetsnew/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/commons-logging-1.0.4.jar
[exec] file:/C:/eclipsetsnew/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/fop.jar
[exec] file:/C:/eclipsetsnew/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/iText-5.0.1.jar
[exec] file:/C:/eclipsetsnew/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/serializer-2.7.1.jar
[exec] file:/C:/eclipsetsnew/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/xalan-2.7.1.jar
[exec] file:/C:/eclipsetsnew/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/xml-apis-ext.jar
[exec] file:/C:/eclipsetsnew/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/xmlgraphics-commons-1.3.1.jar
[exec] file:/C:/eclipsetsnew/tigerstripe/plugins/.TIP_JvtSpec_Generator-1.1_temp/classes/
[exec] file:/C:/eclipsetsnew/tigerstripe/plugins/.TIP_EjbImpl_Generator-1.1_temp/classes/
[exec] [Project: org.tmforum.tip.fmk.test1.dep version=1.1, Plugin: TIP_Doc_Generator(1.1) version=1.1]
[exec] Generation Successful.
[exec]
[exec] [Project: org.tmforum.tip.fmk.test1.dep version=1.1, Plugin: TIP_JvtSpec_Generator(1.1) version=1.1]
[exec] Notice: None of the artifact(s) match the specified rule(s) 'javaBasicExceptionRule'.
[exec] Notice: None of the artifact(s) match the specified rule(s) 'javaBasicEventSpecRule'.
[exec] Notice: None of the artifact(s) match the specified rule(s) 'javaBasicFacadeSpecRule'.
[exec] Notice: None of the artifact(s) match the specified rule(s) 'javaBasicAssociationClassSpecRule'.
[exec] Generation Successful.
[exec]
[exec] [Project: org.tmforum.tip.fmk.test1.dep version=1.1, Plugin: TIP_EjbImpl_Generator(1.1) version=1.1]
[exec] Notice: None of the artifact(s) match the specified rule(s) 'javaBasicAssociationClassPersistanceTestRule'.
[exec] Notice: None of the artifact(s) match the specified rule(s) 'javaBasicAssociationClassPersistanceDaoImplRule'.
[exec] Notice: None of the artifact(s) match the specified rule(s) 'javaBasicAssociationClassPersistanceDaoSpecRule'.
[exec] Notice: None of the artifact(s) match the specified rule(s) 'javaBasicEventRule'.
[exec] Notice: None of the artifact(s) match the specified rule(s) 'javaBasicFacadeRule'.
[exec] Notice: None of the artifact(s) match the specified rule(s) 'javaBasicAssociationClassRule'.
[exec] Notice: None of the artifact(s) match the specified rule(s) 'javaBasicFacadeTestRule'.
[exec] Notice: None of the artifact(s) match the specified rule(s) 'javaBasicMockFacadeRule'.
[exec] Generation Successful.
[exec]
[exec] Generation complete. Took 5004 milliseconds.
[INFO] Executed tasks
[INFO] [antrun:run {execution: move generated sources to jars}]
[INFO] Executing tasks
[echo] MODEL_POM: Creating transitory jars of tigerstripe generated code
[echo] MODEL_POM: tigerstripe_generation_dir: C:\ws-tsnew\TIP_Fmk_Test1_Dependencies\target\tigerstripe.gen
[echo] MODEL_POM: C:\ws-tsnew\TIP_Fmk_Test1_Dependencies\target\CODE_GENERATED_FLAG.txt does not exist. Will install transient dependencies
[echo] MODEL_POM: directory of code generated by plugin: C:\ws-tsnew\TIP_Fmk_Test1_Dependencies\target\tigerstripe.gen\TIP_Fmk_Test1_Dependencies_DocSpecPackageTransientDependency
[echo] MODEL_POM: name of jar containing code generated by plugin: TIP_Fmk_Test1_Dependencies_DocSpecPackageTransientDependency.jar
[jar] Building jar: C:\ws-tsnew\TIP_Fmk_Test1_Dependencies\target\tigerstripe.gen\TIP_Fmk_Test1_Dependencies_DocSpecPackageTransientDependency.jar
[echo] MODEL_POM: name of pom expected from plugin: TIP_Fmk_Test1_Dependencies_DocSpecPackageTransientDependencyPom.xml
bootstrap.maven.tasks:
run-if-pom-exists:
[echo] POM-BUILD: Processing generated project: C:\ws-tsnew\TIP_Fmk_Test1_Dependencies\target\tigerstripe.gen\TIP_Fmk_Test1_Dependencies_DocSpecPackageTransientDependency.jar
[echo] POM-BUILD: Generated project Pom file exists: C:\ws-tsnew\TIP_Fmk_Test1_Dependencies\target\tigerstripe.gen\TIP_Fmk_Test1_Dependencies_DocSpecPackageTransientDependencyPom.xml. Installing jar in local .m2 repository
[INFO] Installing C:\ws-tsnew\TIP_Fmk_Test1_Dependencies\target\tigerstripe.gen\TIP_Fmk_Test1_Dependencies_DocSpecPackageTransientDependency.jar to C:\Users\kumar\.m2\repository\org\tmforum\tip\TIP_Fmk_Test1_Dependencies_DocSpecPackageTransientDependency\1.1.2-SNAPSHOT\TIP_Fmk_Test1_Dependencies_DocSpecPackageTransientDependency-1.1.2-SNAPSHOT.jar
run-if-pom-missing:
install-jar:
[echo] MODEL_POM: directory of code generated by plugin: C:\ws-tsnew\TIP_Fmk_Test1_Dependencies\target\tigerstripe.gen\TIP_Fmk_Test1_Dependencies_EjbImplGenSrcPackageTransientDependency
[echo] MODEL_POM: name of jar containing code generated by plugin: TIP_Fmk_Test1_Dependencies_EjbImplGenSrcPackageTransientDependency.jar
[jar] Building jar: C:\ws-tsnew\TIP_Fmk_Test1_Dependencies\target\tigerstripe.gen\TIP_Fmk_Test1_Dependencies_EjbImplGenSrcPackageTransientDependency.jar
[echo] MODEL_POM: name of pom expected from plugin: TIP_Fmk_Test1_Dependencies_EjbImplGenSrcPackageTransientDependencyPom.xml
bootstrap.maven.tasks:
run-if-pom-exists:
[echo] POM-BUILD: Processing generated project: C:\ws-tsnew\TIP_Fmk_Test1_Dependencies\target\tigerstripe.gen\TIP_Fmk_Test1_Dependencies_EjbImplGenSrcPackageTransientDependency.jar
[echo] POM-BUILD: Generated project Pom file exists: C:\ws-tsnew\TIP_Fmk_Test1_Dependencies\target\tigerstripe.gen\TIP_Fmk_Test1_Dependencies_EjbImplGenSrcPackageTransientDependencyPom.xml. Installing jar in local .m2 repository
[INFO] Installing C:\ws-tsnew\TIP_Fmk_Test1_Dependencies\target\tigerstripe.gen\TIP_Fmk_Test1_Dependencies_EjbImplGenSrcPackageTransientDependency.jar to C:\Users\kumar\.m2\repository\org\openoss\tip\TIP_Fmk_Test1_Dependencies_EjbImplGenSrcPackageTransientDependency\1.1.2-SNAPSHOT\TIP_Fmk_Test1_Dependencies_EjbImplGenSrcPackageTransientDependency-1.1.2-SNAPSHOT.jar
run-if-pom-missing:
install-jar:
[echo] MODEL_POM: directory of code generated by plugin: C:\ws-tsnew\TIP_Fmk_Test1_Dependencies\target\tigerstripe.gen\TIP_Fmk_Test1_Dependencies_JvtSpecPackageTransientDependency
[echo] MODEL_POM: name of jar containing code generated by plugin: TIP_Fmk_Test1_Dependencies_JvtSpecPackageTransientDependency.jar
[jar] Building jar: C:\ws-tsnew\TIP_Fmk_Test1_Dependencies\target\tigerstripe.gen\TIP_Fmk_Test1_Dependencies_JvtSpecPackageTransientDependency.jar
[echo] MODEL_POM: name of pom expected from plugin: TIP_Fmk_Test1_Dependencies_JvtSpecPackageTransientDependencyPom.xml
bootstrap.maven.tasks:
run-if-pom-exists:
[echo] POM-BUILD: Processing generated project: C:\ws-tsnew\TIP_Fmk_Test1_Dependencies\target\tigerstripe.gen\TIP_Fmk_Test1_Dependencies_JvtSpecPackageTransientDependency.jar
[echo] POM-BUILD: Generated project Pom file exists: C:\ws-tsnew\TIP_Fmk_Test1_Dependencies\target\tigerstripe.gen\TIP_Fmk_Test1_Dependencies_JvtSpecPackageTransientDependencyPom.xml. Installing jar in local .m2 repository
[INFO] Installing C:\ws-tsnew\TIP_Fmk_Test1_Dependencies\target\tigerstripe.gen\TIP_Fmk_Test1_Dependencies_JvtSpecPackageTransientDependency.jar to C:\Users\kumar\.m2\repository\org\tmforum\tip\TIP_Fmk_Test1_Dependencies_JvtSpecPackageTransientDependency\1.1.2-SNAPSHOT\TIP_Fmk_Test1_Dependencies_JvtSpecPackageTransientDependency-1.1.2-SNAPSHOT.jar
run-if-pom-missing:
install-jar:
[echo] MODEL_POM: Writing CODE_GENERATED_FLAG.txt to prevent further model code generation in this build
[INFO] Executed tasks
[INFO] [site:attach-descriptor {execution: default-attach-descriptor}]
[INFO] [install:install {execution: default-install}]
[INFO] Installing C:\ws-tsnew\TIP_Fmk_Test1_Dependencies\pom.xml to C:\Users\kumar\.m2\repository\org\tmforum\tip\TIP_Fmk_Test1_Dependencies\1.1.2-SNAPSHOT\TIP_Fmk_Test1_Dependencies-1.1.2-SNAPSHOT.pom
[INFO] ------------------------------------------------------------------------
[INFO] Building TIP_Fmk_Test1_Model
[INFO] task-segment: [clean, install]
[INFO] ------------------------------------------------------------------------
[INFO] [clean:clean {execution: default-clean}]
[INFO] Deleting directory C:\ws-tsnew\TIP_Fmk_Test1_Model\target
[INFO] [properties:read-project-properties {execution: default}]
[INFO] [dependency:unpack {execution: download tigerstripe plugins}]
[INFO] Configured Artifact: org.tmforum.tip:TIP_Doc_Generator_Package:?:jar
[INFO] Configured Artifact: org.tmforum.tip:TIP_Soap_Generator_Package:?:jar
[INFO] Configured Artifact: org.tmforum.tip:TIP_Profile_Package:?:jar
[INFO] Configured Artifact: org.tmforum.tip:TIP_JvtSpec_Generator_Package:?:jar
[INFO] Configured Artifact: org.openoss.tip:TIP_EjbImpl_Generator_Package:?:jar
[INFO] Configured Artifact: org.tmforum.tip:TIP_Common_Model_Package:?:jar
[INFO] Unpacking C:\Users\kumar\.m2\repository\org\tmforum\tip\TIP_Doc_Generator_Package\1.1.2-SNAPSHOT\TIP_Doc_Generator_Package-1.1.2-SNAPSHOT.jarto
C:\ws-tsnew\TIP_Fmk_Test1_Model\TigerstripeGenerators
with Includes null and excludes:null
[INFO] Unpacking C:\Users\kumar\.m2\repository\org\tmforum\tip\TIP_Soap_Generator_Package\1.1.2-SNAPSHOT\TIP_Soap_Generator_Package-1.1.2-SNAPSHOT.jarto
C:\ws-tsnew\TIP_Fmk_Test1_Model\TigerstripeGenerators
with Includes null and excludes:null
[INFO] Unpacking C:\Users\kumar\.m2\repository\org\tmforum\tip\TIP_Profile_Package\1.1.2-SNAPSHOT\TIP_Profile_Package-1.1.2-SNAPSHOT.jarto
C:\ws-tsnew\TIP_Fmk_Test1_Model\TigerstripeGenerators
with Includes null and excludes:null
[INFO] Unpacking C:\Users\kumar\.m2\repository\org\tmforum\tip\TIP_JvtSpec_Generator_Package\1.1.2-SNAPSHOT\TIP_JvtSpec_Generator_Package-1.1.2-SNAPSHOT.jarto
C:\ws-tsnew\TIP_Fmk_Test1_Model\TigerstripeGenerators
with Includes null and excludes:null
[INFO] Unpacking C:\Users\kumar\.m2\repository\org\openoss\tip\TIP_EjbImpl_Generator_Package\1.1.2-SNAPSHOT\TIP_EjbImpl_Generator_Package-1.1.2-SNAPSHOT.jarto
C:\ws-tsnew\TIP_Fmk_Test1_Model\TigerstripeGenerators
with Includes null and excludes:null
[INFO] Unpacking C:\Users\kumar\.m2\repository\org\tmforum\tip\TIP_Common_Model_Package\1.1.2-SNAPSHOT\TIP_Common_Model_Package-1.1.2-SNAPSHOT.jarto
C:\ws-tsnew\TIP_Fmk_Test1_Model
with Includes null and excludes:null
[INFO] [dependency:copy {execution: copy maven ant tasks jar from repo}]
[INFO] Configured Artifact: org.apache.maven:maven-ant-tasks:2.0.10:jar
[INFO] Copying maven-ant-tasks-2.0.10.jar to C:\ws-tsnew\TIP_Fmk_Test1_Model\libs\maven-ant-tasks-2.0.10.jar
[INFO] [antrun:run {execution: run-tigerstripe}]
[INFO] Executing tasks
[echo] MODEL_POM: eclipse_home: C:\eclipsetsnew
[echo] MODEL_POM: model_project_basedir: C:\ws-tsnew\TIP_Fmk_Test1_Model
[echo] MODEL_POM: model_project__directory_name: TIP_Fmk_Test1_Model
[echo] MODEL_POM: tigerstripe_workspace: C:\ws-tsnew
[echo] MODEL_POM: referenced_project1: TIP_Fmk_Test1_Model
[echo] MODEL_POM: tigerstripe_generation_project: TIP_Fmk_Test1_Model
[echo] MODEL_POM: tigerstripe_arg_string: -nosplash -data C:\ws-tsnew -application org.eclipse.tigerstripe.workbench.headless.tigerstripe C:\ws-tsnew\TIP_Fmk_Test1_Model GENERATION_PROJECT=C:\ws-tsnew\TIP_Fmk_Test1_Model
[echo] MODEL_POM: C:\ws-tsnew\TIP_Fmk_Test1_Model\target\CODE_GENERATED_FLAG.txt does not exist. Will run Tigerstripe
[exec] Tigerstripe Workbench Base Plug-in (Incubation) (v0.6.935.201102010903)
[exec] Active Profile: TIP_Profile 1.1.1
[exec] file:/C:/eclipsetsnew/tigerstripe/plugins/.TIP_Soap_Generator-1.1_temp/classes/
[exec] file:/C:/eclipsetsnew/tigerstripe/plugins/.TIP_Soap_Generator-1.1_temp/commons-lang-2.4_simplified.jar
[exec] file:/C:/eclipsetsnew/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/classes/
[exec] file:/C:/eclipsetsnew/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/avalon-framework-4.2.0.jar
[exec] file:/C:/eclipsetsnew/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/batik-bridge.jar
[exec] file:/C:/eclipsetsnew/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/batik-css.jar
[exec] file:/C:/eclipsetsnew/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/batik-dom.jar
[exec] file:/C:/eclipsetsnew/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/batik-ext.jar
[exec] file:/C:/eclipsetsnew/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/batik-gui-util.jar
[exec] file:/C:/eclipsetsnew/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/batik-gvt.jar
[exec] file:/C:/eclipsetsnew/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/batik-svg-dom.jar
[exec] file:/C:/eclipsetsnew/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/batik-svggen.jar
[exec] file:/C:/eclipsetsnew/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/batik-util.jar
[exec] file:/C:/eclipsetsnew/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/batik-xml.jar
[exec] file:/C:/eclipsetsnew/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/commons-io-1.3.1.jar
[exec] file:/C:/eclipsetsnew/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/commons-lang-2.4_simplified.jar
[exec] file:/C:/eclipsetsnew/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/commons-logging-1.0.4.jar
[exec] file:/C:/eclipsetsnew/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/fop.jar
[exec] file:/C:/eclipsetsnew/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/iText-5.0.1.jar
[exec] file:/C:/eclipsetsnew/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/serializer-2.7.1.jar
[exec] file:/C:/eclipsetsnew/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/xalan-2.7.1.jar
[exec] file:/C:/eclipsetsnew/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/xml-apis-ext.jar
[exec] file:/C:/eclipsetsnew/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/xmlgraphics-commons-1.3.1.jar
[exec] file:/C:/eclipsetsnew/tigerstripe/plugins/.TIP_JvtSpec_Generator-1.1_temp/classes/
[exec] file:/C:/eclipsetsnew/tigerstripe/plugins/.TIP_EjbImpl_Generator-1.1_temp/classes/
[exec] [Project: org.tmforum.tip.fmk.test1 version=1.1, Plugin: TIP_Soap_Generator(1.1) version=1.1]
[exec] Generation Successful.
[exec]
[exec] [Project: org.tmforum.tip.fmk.test1 version=1.1, Plugin: TIP_Doc_Generator(1.1) version=1.1]
[exec] Generation Successful.
[exec]
[exec] [Project: org.tmforum.tip.fmk.test1 version=1.1, Plugin: TIP_JvtSpec_Generator(1.1) version=1.1]
[exec] Error: Unexpected error while merging 'templates/javaBasicFacadeSpecTemplate-1.0.vm' template: Invocation of method 'getAttributeValue' in class org.eclipse.tigerstripe.workbench.internal.core.profile.stereotype.StereotypeInstance threw exception org.eclipse.tigerstripe.workbench.TigerstripeException: Unknown attribute 'getType'. @ templates/javaBasicFacadeSpecTemplate-1.0.vm[415,83], current artifact: org.tmforum.tip.service.trouble.ServiceAlarmInterface. Generation may be incomplete.
[exec] org.apache.velocity.exception.MethodInvocationException: Invocation of method 'getAttributeValue' in class org.eclipse.tigerstripe.workbench.internal.core.profile.stereotype.StereotypeInstance threw exception org.eclipse.tigerstripe.workbench.TigerstripeException: Unknown attribute 'getType'. @ templates/javaBasicFacadeSpecTemplate-1.0.vm[415,83]
[exec] at org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:286)
[exec] at org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:203)
[exec] at org.apache.velocity.runtime.parser.node.ASTReference.value(ASTReference.java:419)
[exec] at org.apache.velocity.runtime.parser.node.ASTAddNode.value(ASTAddNode.java:86)
[exec] at org.apache.velocity.runtime.parser.node.ASTAddNode.value(ASTAddNode.java:85)
[exec] at org.apache.velocity.runtime.parser.node.ASTExpression.value(ASTExpression.java:73)
[exec] at org.apache.velocity.runtime.parser.node.ASTSetDirective.render(ASTSetDirective.java:125)
[exec] at org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:74)
[exec] at org.apache.velocity.runtime.parser.node.ASTIfStatement.render(ASTIfStatement.java:88)
[exec] at org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:74)
[exec] at org.apache.velocity.runtime.directive.Foreach.render(Foreach.java:448)
[exec] at org.apache.velocity.runtime.parser.node.ASTDirective.render(ASTDirective.java:170)
[exec] at org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:74)
[exec] at org.apache.velocity.runtime.directive.Foreach.render(Foreach.java:448)
[exec] at org.apache.velocity.runtime.parser.node.ASTDirective.render(ASTDirective.java:170)
[exec] at org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:74)
[exec] at org.apache.velocity.runtime.parser.node.ASTIfStatement.render(ASTIfStatement.java:88)
[exec] at org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:318)
[exec] at org.apache.velocity.runtime.directive.VelocimacroProxy.render(VelocimacroProxy.java:194)
[exec] at org.apache.velocity.runtime.parser.node.ASTDirective.render(ASTDirective.java:170)
[exec] at org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:318)
[exec] at org.apache.velocity.runtime.directive.VelocimacroProxy.render(VelocimacroProxy.java:194)
[exec] at org.apache.velocity.runtime.parser.node.ASTDirective.render(ASTDirective.java:170)
[exec] at org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:318)
[exec] at org.apache.velocity.Template.merge(Template.java:254)
[exec] at org.eclipse.tigerstripe.workbench.internal.core.project.pluggable.rules.ArtifactBasedTemplateRule.trigger(ArtifactBasedTemplateRule.java:254)
[exec] at org.eclipse.tigerstripe.workbench.internal.core.plugin.pluggable.PluginRuleExecutor.trigger(PluginRuleExecutor.java:102)
[exec] at org.eclipse.tigerstripe.workbench.internal.core.plugin.pluggable.PluggablePlugin.trigger(PluggablePlugin.java:151)
[exec] at org.eclipse.tigerstripe.workbench.internal.core.plugin.PluginHousing.trigger(PluginHousing.java:35)
[exec] at org.eclipse.tigerstripe.workbench.internal.core.plugin.PluginConfig.trigger(PluginConfig.java:256)
[exec] at org.eclipse.tigerstripe.workbench.internal.core.generation.M1Generator.internalPluginLoop(M1Generator.java:620)
[exec] at org.eclipse.tigerstripe.workbench.internal.core.generation.M1Generator.internalRun(M1Generator.java:563)
[exec] at org.eclipse.tigerstripe.workbench.internal.core.generation.M1Generator.run(M1Generator.java:360)
[exec] at org.eclipse.tigerstripe.workbench.internal.core.generation.M1Generator.run(M1Generator.java:84)
[exec] at org.eclipse.tigerstripe.workbench.internal.api.impl.TigerstripeProjectHandle.generate(TigerstripeProjectHandle.java:489)
[exec] at org.eclipse.tigerstripe.workbench.headless.Tigerstripe.generateTigerstripeOutput(Tigerstripe.java:195)
[exec] at org.eclipse.tigerstripe.workbench.headless.Tigerstripe.start(Tigerstripe.java:78)
[exec] at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
[exec] at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
[exec] at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
[exec] at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369)
[exec] at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
[exec] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[exec] at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
[exec] at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
[exec] at java.lang.reflect.Method.invoke(Unknown Source)
[exec] at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:619)
[exec] at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574)
[exec] at org.eclipse.equinox.launcher.Main.run(Main.java:1407)
[exec] Caused by: org.eclipse.tigerstripe.workbench.TigerstripeException: Unknown attribute 'getType'.
[exec] at org.eclipse.tigerstripe.workbench.internal.core.profile.stereotype.StereotypeInstance.getAttributeValue(StereotypeInstance.java:91)
[exec] at sun.reflect.GeneratedMethodAccessor114.invoke(Unknown Source)
[exec] at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
[exec] at java.lang.reflect.Method.invoke(Unknown Source)
[exec] at org.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:295)
[exec] at org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:245)
[exec] ... 48 more
[exec]
[exec]
[exec] [Project: org.tmforum.tip.fmk.test1 version=1.1, Plugin: TIP_EjbImpl_Generator(1.1) version=1.1]
[exec] Error: Unexpected error while merging 'templates/springBasicApplicationContextTemplate-1.0.vm' template: Invocation of method 'getAttributeValue' in class org.eclipse.tigerstripe.workbench.internal.core.profile.stereotype.StereotypeInstance threw exception org.eclipse.tigerstripe.workbench.TigerstripeException: Unknown attribute 'getType'. @ templates/springBasicApplicationContextTemplate-1.0.vm[415,83]. Generation may be incomplete.
[exec] org.apache.velocity.exception.MethodInvocationException: Invocation of method 'getAttributeValue' in class org.eclipse.tigerstripe.workbench.internal.core.profile.stereotype.StereotypeInstance threw exception org.eclipse.tigerstripe.workbench.TigerstripeException: Unknown attribute 'getType'. @ templates/springBasicApplicationContextTemplate-1.0.vm[415,83]
[exec] at org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:286)
[exec] at org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:203)
[exec] Generation is failed.
[exec] org.eclipse.tigerstripe.workbench.TigerstripeException: Generation is failed.
[exec] at org.apache.velocity.runtime.parser.node.ASTReference.value(ASTReference.java:419)
[exec] at org.apache.velocity.runtime.parser.node.ASTAddNode.value(ASTAddNode.java:86)
[exec] at org.apache.velocity.runtime.parser.node.ASTAddNode.value(ASTAddNode.java:85)
[exec] at org.eclipse.tigerstripe.workbench.headless.Tigerstripe.generateTigerstripeOutput(Tigerstripe.java:206)
[exec] at org.apache.velocity.runtime.parser.node.ASTExpression.value(ASTExpression.java:73)
[exec] at org.apache.velocity.runtime.parser.node.ASTSetDirective.render(ASTSetDirective.java:125)
[exec] at org.eclipse.tigerstripe.workbench.headless.Tigerstripe.start(Tigerstripe.java:78)
[exec] at org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:74)
[exec] at org.apache.velocity.runtime.parser.node.ASTIfStatement.render(ASTIfStatement.java:88)
[exec] at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
[exec] at org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:74)
[exec] at org.apache.velocity.runtime.directive.Foreach.render(Foreach.java:448)
[exec] at org.apache.velocity.runtime.parser.node.ASTDirective.render(ASTDirective.java:170)
[exec] at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
[exec] at org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:74)
[exec] at org.apache.velocity.runtime.directive.Foreach.render(Foreach.java:448)
[exec] at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
[exec] at org.apache.velocity.runtime.parser.node.ASTDirective.render(ASTDirective.java:170)
[exec] at org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:74)
[exec] at org.apache.velocity.runtime.parser.node.ASTIfStatement.render(ASTIfStatement.java:88)
[exec] at org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:318)
[exec] at org.apache.velocity.runtime.directive.VelocimacroProxy.render(VelocimacroProxy.java:194)
[exec] at org.apache.velocity.runtime.parser.node.ASTDirective.render(ASTDirective.java:170)
[exec] at org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:74)
[exec] at org.apache.velocity.runtime.directive.Foreach.render(Foreach.java:448)
[exec] at org.apache.velocity.runtime.parser.node.ASTDirective.render(ASTDirective.java:170)
[exec] at org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:318)
[exec] at org.apache.velocity.runtime.directive.VelocimacroProxy.render(VelocimacroProxy.java:194)
[exec] at org.apache.velocity.runtime.parser.node.ASTDirective.render(ASTDirective.java:170)
[exec] at org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:318)
[exec] at org.apache.velocity.Template.merge(Template.java:254)
[exec] at org.eclipse.tigerstripe.workbench.internal.core.project.pluggable.rules.GlobalTemplateRule.trigger(GlobalTemplateRule.java:135)
[exec] at org.eclipse.tigerstripe.workbench.internal.core.plugin.pluggable.PluginRuleExecutor.trigger(PluginRuleExecutor.java:79)
[exec] at org.eclipse.tigerstripe.workbench.internal.core.plugin.pluggable.PluggablePlugin.trigger(PluggablePlugin.java:151)
[exec] at org.eclipse.tigerstripe.workbench.internal.core.plugin.PluginHousing.trigger(PluginHousing.java:35)
[exec] at org.eclipse.tigerstripe.workbench.internal.core.plugin.PluginConfig.trigger(PluginConfig.java:256)
[exec] at org.eclipse.tigerstripe.workbench.internal.core.generation.M1Generator.internalPluginLoop(M1Generator.java:620)
[exec] at org.eclipse.tigerstripe.workbench.internal.core.generation.M1Generator.internalRun(M1Generator.java:563)
[exec] at org.eclipse.tigerstripe.workbench.internal.core.generation.M1Generator.run(M1Generator.java:360)
[exec] at org.eclipse.tigerstripe.workbench.internal.core.generation.M1Generator.run(M1Generator.java:84)
[exec] at org.eclipse.tigerstripe.workbench.internal.api.impl.TigerstripeProjectHandle.generate(TigerstripeProjectHandle.java:489)
[exec] at org.eclipse.tigerstripe.workbench.headless.Tigerstripe.generateTigerstripeOutput(Tigerstripe.java:195)
[exec] at org.eclipse.tigerstripe.workbench.headless.Tigerstripe.start(Tigerstripe.java:78)
[exec] at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
[exec] at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
[exec] at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
[exec] at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369)
[exec] at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
[exec] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[exec] at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
[exec] at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
[exec] at java.lang.reflect.Method.invoke(Unknown Source)
[exec] at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:619)
[exec] at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574)
[exec] at org.eclipse.equinox.launcher.Main.run(Main.java:1407)
[exec] Caused by: org.eclipse.tigerstripe.workbench.TigerstripeException: Unknown attribute 'getType'.
[exec] at org.eclipse.tigerstripe.workbench.internal.core.profile.stereotype.StereotypeInstance.getAttributeValue(StereotypeInstance.java:91)
[exec] at sun.reflect.GeneratedMethodAccessor114.invoke(Unknown Source)
[exec] at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
[exec] at java.lang.reflect.Method.invoke(Unknown Source)
[exec] at org.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:295)
[exec] at org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:245)
[exec] ... 51 more
[exec]
[exec]
[exec] at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369)
[exec] at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
[exec] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[exec] at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
[exec] at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
[exec] at java.lang.reflect.Method.invoke(Unknown Source)
[exec] at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:619)
[exec] at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574)
[exec] at org.eclipse.equinox.launcher.Main.run(Main.java:1407)
[INFO] Executed tasks
[INFO] [antrun:run {execution: move generated sources to jars}]
[INFO] Executing tasks
[echo] MODEL_POM: Creating transitory jars of tigerstripe generated code
[echo] MODEL_POM: tigerstripe_generation_dir: C:\ws-tsnew\TIP_Fmk_Test1_Model\target\tigerstripe.gen
[echo] MODEL_POM: C:\ws-tsnew\TIP_Fmk_Test1_Model\target\CODE_GENERATED_FLAG.txt does not exist. Will install transient dependencies
[echo] MODEL_POM: directory of code generated by plugin: C:\ws-tsnew\TIP_Fmk_Test1_Model\target\tigerstripe.gen\TIP_Fmk_Test1_DocSpecPackageTransientDependency
[echo] MODEL_POM: name of jar containing code generated by plugin: TIP_Fmk_Test1_DocSpecPackageTransientDependency.jar
[jar] Building jar: C:\ws-tsnew\TIP_Fmk_Test1_Model\target\tigerstripe.gen\TIP_Fmk_Test1_DocSpecPackageTransientDependency.jar
[echo] MODEL_POM: name of pom expected from plugin: TIP_Fmk_Test1_DocSpecPackageTransientDependencyPom.xml
bootstrap.maven.tasks:
run-if-pom-exists:
[echo] POM-BUILD: Processing generated project: C:\ws-tsnew\TIP_Fmk_Test1_Model\target\tigerstripe.gen\TIP_Fmk_Test1_DocSpecPackageTransientDependency.jar
[echo] POM-BUILD: Generated project Pom file exists: C:\ws-tsnew\TIP_Fmk_Test1_Model\target\tigerstripe.gen\TIP_Fmk_Test1_DocSpecPackageTransientDependencyPom.xml. Installing jar in local .m2 repository
[INFO] Installing C:\ws-tsnew\TIP_Fmk_Test1_Model\target\tigerstripe.gen\TIP_Fmk_Test1_DocSpecPackageTransientDependency.jar to C:\Users\kumar\.m2\repository\org\tmforum\tip\TIP_Fmk_Test1_DocSpecPackageTransientDependency\1.1.2-SNAPSHOT\TIP_Fmk_Test1_DocSpecPackageTransientDependency-1.1.2-SNAPSHOT.jar
run-if-pom-missing:
install-jar:
[echo] MODEL_POM: directory of code generated by plugin: C:\ws-tsnew\TIP_Fmk_Test1_Model\target\tigerstripe.gen\TIP_Fmk_Test1_EjbImplGenSrcPackageTransientDependency
[echo] MODEL_POM: name of jar containing code generated by plugin: TIP_Fmk_Test1_EjbImplGenSrcPackageTransientDependency.jar
[jar] Building jar: C:\ws-tsnew\TIP_Fmk_Test1_Model\target\tigerstripe.gen\TIP_Fmk_Test1_EjbImplGenSrcPackageTransientDependency.jar
[echo] MODEL_POM: name of pom expected from plugin: TIP_Fmk_Test1_EjbImplGenSrcPackageTransientDependencyPom.xml
bootstrap.maven.tasks:
run-if-pom-exists:
[echo] POM-BUILD: Processing generated project: C:\ws-tsnew\TIP_Fmk_Test1_Model\target\tigerstripe.gen\TIP_Fmk_Test1_EjbImplGenSrcPackageTransientDependency.jar
[echo] POM-BUILD: Generated project Pom file exists: C:\ws-tsnew\TIP_Fmk_Test1_Model\target\tigerstripe.gen\TIP_Fmk_Test1_EjbImplGenSrcPackageTransientDependencyPom.xml. Installing jar in local .m2 repository
[INFO] Installing C:\ws-tsnew\TIP_Fmk_Test1_Model\target\tigerstripe.gen\TIP_Fmk_Test1_EjbImplGenSrcPackageTransientDependency.jar to C:\Users\kumar\.m2\repository\org\openoss\tip\TIP_Fmk_Test1_EjbImplGenSrcPackageTransientDependency\1.1.2-SNAPSHOT\TIP_Fmk_Test1_EjbImplGenSrcPackageTransientDependency-1.1.2-SNAPSHOT.jar
run-if-pom-missing:
install-jar:
[echo] MODEL_POM: directory of code generated by plugin: C:\ws-tsnew\TIP_Fmk_Test1_Model\target\tigerstripe.gen\TIP_Fmk_Test1_JvtSpecPackageTransientDependency
[echo] MODEL_POM: name of jar containing code generated by plugin: TIP_Fmk_Test1_JvtSpecPackageTransientDependency.jar
[jar] Building jar: C:\ws-tsnew\TIP_Fmk_Test1_Model\target\tigerstripe.gen\TIP_Fmk_Test1_JvtSpecPackageTransientDependency.jar
[echo] MODEL_POM: name of pom expected from plugin: TIP_Fmk_Test1_JvtSpecPackageTransientDependencyPom.xml
bootstrap.maven.tasks:
run-if-pom-exists:
[echo] POM-BUILD: Processing generated project: C:\ws-tsnew\TIP_Fmk_Test1_Model\target\tigerstripe.gen\TIP_Fmk_Test1_JvtSpecPackageTransientDependency.jar
[echo] POM-BUILD: Generated project Pom file exists: C:\ws-tsnew\TIP_Fmk_Test1_Model\target\tigerstripe.gen\TIP_Fmk_Test1_JvtSpecPackageTransientDependencyPom.xml. Installing jar in local .m2 repository
[INFO] Installing C:\ws-tsnew\TIP_Fmk_Test1_Model\target\tigerstripe.gen\TIP_Fmk_Test1_JvtSpecPackageTransientDependency.jar to C:\Users\kumar\.m2\repository\org\tmforum\tip\TIP_Fmk_Test1_JvtSpecPackageTransientDependency\1.1.2-SNAPSHOT\TIP_Fmk_Test1_JvtSpecPackageTransientDependency-1.1.2-SNAPSHOT.jar
run-if-pom-missing:
install-jar:
[echo] MODEL_POM: directory of code generated by plugin: C:\ws-tsnew\TIP_Fmk_Test1_Model\target\tigerstripe.gen\TIP_Fmk_Test1_SoapSpecPackageTransientDependency
[echo] MODEL_POM: name of jar containing code generated by plugin: TIP_Fmk_Test1_SoapSpecPackageTransientDependency.jar
[jar] Building jar: C:\ws-tsnew\TIP_Fmk_Test1_Model\target\tigerstripe.gen\TIP_Fmk_Test1_SoapSpecPackageTransientDependency.jar
[echo] MODEL_POM: name of pom expected from plugin: TIP_Fmk_Test1_SoapSpecPackageTransientDependencyPom.xml
bootstrap.maven.tasks:
run-if-pom-exists:
[echo] POM-BUILD: Processing generated project: C:\ws-tsnew\TIP_Fmk_Test1_Model\target\tigerstripe.gen\TIP_Fmk_Test1_SoapSpecPackageTransientDependency.jar
[echo] POM-BUILD: Generated project Pom file exists: C:\ws-tsnew\TIP_Fmk_Test1_Model\target\tigerstripe.gen\TIP_Fmk_Test1_SoapSpecPackageTransientDependencyPom.xml. Installing jar in local .m2 repository
[INFO] Installing C:\ws-tsnew\TIP_Fmk_Test1_Model\target\tigerstripe.gen\TIP_Fmk_Test1_SoapSpecPackageTransientDependency.jar to C:\Users\kumar\.m2\repository\org\tmforum\tip\TIP_Fmk_Test1_SoapSpecPackageTransientDependency\1.1.2-SNAPSHOT\TIP_Fmk_Test1_SoapSpecPackageTransientDependency-1.1.2-SNAPSHOT.jar
run-if-pom-missing:
install-jar:
[echo] MODEL_POM: Writing CODE_GENERATED_FLAG.txt to prevent further model code generation in this build
[INFO] Executed tasks
[INFO] [site:attach-descriptor {execution: default-attach-descriptor}]
[INFO] [install:install {execution: default-install}]
[INFO] Installing C:\ws-tsnew\TIP_Fmk_Test1_Model\pom.xml to C:\Users\kumar\.m2\repository\org\tmforum\tip\TIP_Fmk_Test1_Model\1.1.2-SNAPSHOT\TIP_Fmk_Test1_Model-1.1.2-SNAPSHOT.pom
[INFO] ------------------------------------------------------------------------
[INFO] Building TIP_Fmk_Test1_JvtSpecPackage
[INFO] task-segment: [clean, install]
[INFO] ------------------------------------------------------------------------
[INFO] [clean:clean {execution: default-clean}]
[INFO] Deleting directory C:\ws-tsnew\TIP_Fmk_Test1_JvtSpecPackage\target
[INFO] [dependency:unpack {execution: unpack}]
[INFO] Configured Artifact: org.tmforum.tip:TIP_Fmk_Test1_JvtSpecPackageTransientDependency:1.1.2-SNAPSHOT:jar
[INFO] Configured Artifact: org.tmforum.tip:TIP_Fmk_Test1_Dependencies_JvtSpecPackageTransientDependency:1.1.2-SNAPSHOT:jar
[INFO] Unpacking C:\Users\kumar\.m2\repository\org\tmforum\tip\TIP_Fmk_Test1_JvtSpecPackageTransientDependency\1.1.2-SNAPSHOT\TIP_Fmk_Test1_JvtSpecPackageTransientDependency-1.1.2-SNAPSHOT.jarto
C:\ws-tsnew\TIP_Fmk_Test1_JvtSpecPackage\target\generated-sources
with Includes null and excludes:null
[INFO] Unpacking C:\Users\kumar\.m2\repository\org\tmforum\tip\TIP_Fmk_Test1_Dependencies_JvtSpecPackageTransientDependency\1.1.2-SNAPSHOT\TIP_Fmk_Test1_Dependencies_JvtSpecPackageTransientDependency-1.1.2-SNAPSHOT.jarto
C:\ws-tsnew\TIP_Fmk_Test1_JvtSpecPackage\target\generated-sources
with Includes null and excludes:null
[INFO] [build-helper:add-source {execution: add-source}]
[INFO] Source directory: C:\ws-tsnew\TIP_Fmk_Test1_JvtSpecPackage\target\generated-sources\src\main\java added.
[INFO] [properties:read-project-properties {execution: default}]
[INFO] [resources:resources {execution: default-resources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 1 resource
[INFO] [compiler:compile {execution: default-compile}]
[INFO] Compiling 34 source files to C:\ws-tsnew\TIP_Fmk_Test1_JvtSpecPackage\target\classes
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Compilation failure
C:\ws-tsnew\TIP_Fmk_Test1_JvtSpecPackage\target\generated-sources\src\main\java\org\tmforum\tip\org\tmforum\tip\cbe\test\Test.java:[68,68] cannot find symbol
symbol : class TestAssociatedWithTestProblem
location: package org.tmforum.tip.org.tmforum.tip.cbe.test
C:\ws-tsnew\TIP_Fmk_Test1_JvtSpecPackage\target\generated-sources\src\main\java\org\tmforum\tip\org\tmforum\tip\cbe\test\Test.java:[75,88] cannot find symbol
symbol : class TestAssociatedWithTestProblem
location: package org.tmforum.tip.org.tmforum.tip.cbe.test
C:\ws-tsnew\TIP_Fmk_Test1_JvtSpecPackage\target\generated-sources\src\main\java\org\tmforum\tip\org\tmforum\tip\cbe\test\Test.java:[82,57] cannot find symbol
symbol : class TestAssociatedWithServiceTestProblem
location: package org.tmforum.tip.org.tmforum.tip.service.test
C:\ws-tsnew\TIP_Fmk_Test1_JvtSpecPackage\target\generated-sources\src\main\java\org\tmforum\tip\org\tmforum\tip\cbe\test\Test.java:[89,84] cannot find symbol
symbol : class TestAssociatedWithServiceTestProblem
location: package org.tmforum.tip.org.tmforum.tip.service.test
C:\ws-tsnew\TIP_Fmk_Test1_JvtSpecPackage\target\generated-sources\src\main\java\org\tmforum\tip\org\tmforum\tip\service\test\ServiceTestProblem.java:[135,57] cannot find symbol
symbol : class TestAssociatedWithServiceTestProblem
location: package org.tmforum.tip.org.tmforum.tip.service.test
C:\ws-tsnew\TIP_Fmk_Test1_JvtSpecPackage\target\generated-sources\src\main\java\org\tmforum\tip\org\tmforum\tip\service\test\ServiceTestProblem.java:[142,77] cannot find symbol
symbol : class TestAssociatedWithServiceTestProblem
location: package org.tmforum.tip.org.tmforum.tip.service.test
C:\ws-tsnew\TIP_Fmk_Test1_JvtSpecPackage\target\generated-sources\src\main\java\org\tmforum\tip\org\tmforum\tip\service\test\ServiceTestProblem.java:[156,38] package org.tmforum.tip.java.lang does not exist
C:\ws-tsnew\TIP_Fmk_Test1_JvtSpecPackage\target\generated-sources\src\main\java\org\tmforum\tip\org\tmforum\tip\service\test\ServiceTestProblem.java:[165,63] package org.tmforum.tip.java.lang does not exist
C:\ws-tsnew\TIP_Fmk_Test1_JvtSpecPackage\target\generated-sources\src\main\java\org\tmforum\tip\org\tmforum\tip\cbe\test\TestProblem.java:[153,53] cannot find symbol
symbol : class TestAssociatedWithTestProblem
location: package org.tmforum.tip.org.tmforum.tip.cbe.test
C:\ws-tsnew\TIP_Fmk_Test1_JvtSpecPackage\target\generated-sources\src\main\java\org\tmforum\tip\org\tmforum\tip\cbe\test\TestProblem.java:[160,66] cannot find symbol
symbol : class TestAssociatedWithTestProblem
location: package org.tmforum.tip.org.tmforum.tip.cbe.test
C:\ws-tsnew\TIP_Fmk_Test1_JvtSpecPackage\target\generated-sources\src\main\java\org\tmforum\tip\org\tmforum\tip\service\test\TestEvent.java:[64,52] cannot find symbol
symbol : class TestAssociatedWithTestProblem
location: package org.tmforum.tip.org.tmforum.tip.cbe.test
C:\ws-tsnew\TIP_Fmk_Test1_JvtSpecPackage\target\generated-sources\src\main\java\org\tmforum\tip\org\tmforum\tip\service\test\TestEvent.java:[124,53] cannot find symbol
symbol : class TestAssociatedWithTestProblem
location: package org.tmforum.tip.org.tmforum.tip.cbe.test
C:\ws-tsnew\TIP_Fmk_Test1_JvtSpecPackage\target\generated-sources\src\main\java\org\tmforum\tip\org\tmforum\tip\service\test\TestEvent.java:[133,72] cannot find symbol
symbol : class TestAssociatedWithTestProblem
location: package org.tmforum.tip.org.tmforum.tip.cbe.test
[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 25 minutes 12 seconds
[INFO] Finished at: Wed Jun 20 21:18:21 IST 2012
[INFO] Final Memory: 36M/87M
[INFO] ------------------------------------------------------------------------ |
|
From: Xose R. S. V. <xr...@op...> - 2012-06-19 08:53:46
|
For me is not clear if a new feature must be added. I have performed
tests and I can see documentation about String enumeration in the
schema, for example:
<xsd:simpleType name="EquipmentSwitchReason">
<xsd:annotation>
<xsd:documentation>
<p>This enumeration reflects the reason why a switch occurred.</p>
</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="NOT_APPLICABLE">
<xsd:annotation>
<xsd:documentation>
<p>NOT_APPLICABLE is used, if a more precise value is not
available.</p>
<p>This literal has value "NOT_APPLICABLE"</p>
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="MANUAL">
<xsd:annotation>
<xsd:documentation>
<p>MANUAL indicates a switch that was requested by the operator
and includes forced switches.</p>
<p>This literal has value "MANUAL"</p>
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="EQUIPMENT_FAILURE">
<xsd:annotation>
<xsd:documentation>
<p>EQUIPMENT_FAILURE is used when an instance of equipment has
failed.</p>
<p>This literal has value "EQUIPMENT_FAILURE"</p>
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
</xsd:restriction>
</xsd:simpleType>
As I understand the allowed enumerations is the String.
So please, could you me clarify the requirement to perform the task?
Thanks in advance
El 18/06/2012 8:22, Flauw, Marc escribió:
> Craig,
>
> This is a specificity of X.721 as some enum are state with a single value and some can have multiple values.
> Availability status has always been a set of. It is possible to have multiple values, like { Degraded, Log_Full}
>
> So it is not a model problem.
>
> On the SOAP generator, initially only String based enum were allowed and it was late in the game that int-based were allowed. I remember we had this discussion on whether we should use the int or the corresponding string value and the result was that the string value was more useful. But I agree the mapping between the string and the enum should be provided in the doc.
>
> The Doc Generator gives both (see picture).
>
> Best regards
>
> Marc
>
> -----Original Message-----
> From: Craig Gallen [mailto:gal...@go...] On Behalf Of Craig Gallen (opennms)
> Sent: Sunday, June 17, 2012 9:59 AM
> To: openoss-devel; Flauw, Marc; Pierre Gauthier; Xose Ramon Sousa Vazquez
> Cc: Craig Gallen (OpenNMS)
> Subject: Problems with Tigerstripe enum definition
>
> Hi,
>
> I have been trying to fix the java generation of Tigerstripe enum values and have a few questions about how the Soap generator is working which might be bugs. I also have some questions about the MPAC model.
> Craig
>
> 1. Firstly MPAC
> The following int enum variables in ItuStateAndStatusList are set to multiplicity * which does not make sense since the other enum variables in ItuStateAndStatusList are set to multiplicity 0..1 I don't understand why these are multiplicity *, Should they not be 0..1?.
>
> org.tmforum.tip.resource.res.tip.nrb.ItuStateAndStatusList.X721_AVAILABILITY_STATUS
> org.tmforum.tip.resource.res.tip.nrb.ItuStateAndStatusList.X721_CONTROL_STATUS
> org.tmforum.tip.resource.res.tip.nrb.ItuStateAndStatusList.X721_STATE
> org.tmforum.tip.resource.res.tip.nrb.ItuStateAndStatusList.X721_CONTROL_STATUS
> org.tmforum.tip.resource.res.tip.nrb.ItuStateAndStatusList.X721_CONTROL_STATUS
>
> It doest seem to make sense to have an array of constants like X721_AVAILABILITY_STATUS in this context.
>
>
> 2. Soap generator
> a) When the soap generator generates an enumeration Base Type 'int' in
> MPAC it generates the following example from
> tip_mpac_resource_res_tip_nrb.xsd. Why is the restriction base given as
> <xsd:restriction base="xsd:string"> rather than<xsd:restriction
> base="xsd:int"> for a tigerstripe Base Type 'int'.
> Should we not be generating<xsd:restriction base="xsd:int">?
>
> b) in the generated documentation all we get is something like 'This
> literal has value 0'. There is no mention of the name of the value in
> the xsd. Should we not be generating documentation in the xsd which says
> LOCKED=0, UNLOCKED=2. This is a minimum requirement but In fact, there
> is an argument that we should be generating constant values which
> include the named definition.
>
> <xsd:simpleType name="AdministrativeState">
> <xsd:annotation>
> <xsd:documentation>
> <p></p>
> </xsd:documentation>
> </xsd:annotation>
> <xsd:restriction base="xsd:string">
> <xsd:enumeration value="0">
> <xsd:annotation>
> <xsd:documentation>
> <p></p>
> <p>This literal has value 0</p>
> </xsd:documentation>
> </xsd:annotation>
> </xsd:enumeration>
> <xsd:enumeration value="2">
> <xsd:annotation>
> <xsd:documentation>
> <p></p>
> <p>This literal has value 2</p>
> </xsd:documentation>
> </xsd:annotation>
> </xsd:enumeration>
> <xsd:enumeration value="1">
> <xsd:annotation>
> <xsd:documentation>
> <p></p>
> <p>This literal has value 1</p>
> </xsd:documentation>
> </xsd:annotation>
> </xsd:enumeration>
> </xsd:restriction>
> </xsd:simpleType>
> <xsd:complexType name="ArrayOfAdministrativeState">
> <xsd:sequence>
> <xsd:element name="item" type="tns:AdministrativeState" minOccurs="0"
> maxOccurs="unbounded"/>
> </xsd:sequence>
> </xsd:complexType>
>
--
*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><http://optarecoolvendor.com>
|
|
From: Flauw, M. <Mar...@hp...> - 2012-06-18 06:23:48
|
Craig,
This is a specificity of X.721 as some enum are state with a single value and some can have multiple values.
Availability status has always been a set of. It is possible to have multiple values, like { Degraded, Log_Full}
So it is not a model problem.
On the SOAP generator, initially only String based enum were allowed and it was late in the game that int-based were allowed. I remember we had this discussion on whether we should use the int or the corresponding string value and the result was that the string value was more useful. But I agree the mapping between the string and the enum should be provided in the doc.
The Doc Generator gives both (see picture).
Best regards
Marc
-----Original Message-----
From: Craig Gallen [mailto:gal...@go...] On Behalf Of Craig Gallen (opennms)
Sent: Sunday, June 17, 2012 9:59 AM
To: openoss-devel; Flauw, Marc; Pierre Gauthier; Xose Ramon Sousa Vazquez
Cc: Craig Gallen (OpenNMS)
Subject: Problems with Tigerstripe enum definition
Hi,
I have been trying to fix the java generation of Tigerstripe enum values and have a few questions about how the Soap generator is working which might be bugs. I also have some questions about the MPAC model.
Craig
1. Firstly MPAC
The following int enum variables in ItuStateAndStatusList are set to multiplicity * which does not make sense since the other enum variables in ItuStateAndStatusList are set to multiplicity 0..1 I don't understand why these are multiplicity *, Should they not be 0..1?.
org.tmforum.tip.resource.res.tip.nrb.ItuStateAndStatusList.X721_AVAILABILITY_STATUS
org.tmforum.tip.resource.res.tip.nrb.ItuStateAndStatusList.X721_CONTROL_STATUS
org.tmforum.tip.resource.res.tip.nrb.ItuStateAndStatusList.X721_STATE
org.tmforum.tip.resource.res.tip.nrb.ItuStateAndStatusList.X721_CONTROL_STATUS
org.tmforum.tip.resource.res.tip.nrb.ItuStateAndStatusList.X721_CONTROL_STATUS
It doest seem to make sense to have an array of constants like X721_AVAILABILITY_STATUS in this context.
2. Soap generator
a) When the soap generator generates an enumeration Base Type 'int' in
MPAC it generates the following example from
tip_mpac_resource_res_tip_nrb.xsd. Why is the restriction base given as
<xsd:restriction base="xsd:string"> rather than <xsd:restriction
base="xsd:int"> for a tigerstripe Base Type 'int'.
Should we not be generating <xsd:restriction base="xsd:int">?
b) in the generated documentation all we get is something like 'This
literal has value 0'. There is no mention of the name of the value in
the xsd. Should we not be generating documentation in the xsd which says
LOCKED=0, UNLOCKED=2. This is a minimum requirement but In fact, there
is an argument that we should be generating constant values which
include the named definition.
<xsd:simpleType name="AdministrativeState">
<xsd:annotation>
<xsd:documentation>
<p></p>
</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="0">
<xsd:annotation>
<xsd:documentation>
<p></p>
<p>This literal has value 0</p>
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="2">
<xsd:annotation>
<xsd:documentation>
<p></p>
<p>This literal has value 2</p>
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="1">
<xsd:annotation>
<xsd:documentation>
<p></p>
<p>This literal has value 1</p>
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
</xsd:restriction>
</xsd:simpleType>
<xsd:complexType name="ArrayOfAdministrativeState">
<xsd:sequence>
<xsd:element name="item" type="tns:AdministrativeState" minOccurs="0"
maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
|
|
From: Craig G. (opennms) <cg...@op...> - 2012-06-17 07:59:41
|
Hi, I have been trying to fix the java generation of Tigerstripe enum values and have a few questions about how the Soap generator is working which might be bugs. I also have some questions about the MPAC model. Craig 1. Firstly MPAC The following int enum variables in ItuStateAndStatusList are set to multiplicity * which does not make sense since the other enum variables in ItuStateAndStatusList are set to multiplicity 0..1 I don't understand why these are multiplicity *, Should they not be 0..1?. org.tmforum.tip.resource.res.tip.nrb.ItuStateAndStatusList.X721_AVAILABILITY_STATUS org.tmforum.tip.resource.res.tip.nrb.ItuStateAndStatusList.X721_CONTROL_STATUS org.tmforum.tip.resource.res.tip.nrb.ItuStateAndStatusList.X721_STATE org.tmforum.tip.resource.res.tip.nrb.ItuStateAndStatusList.X721_CONTROL_STATUS org.tmforum.tip.resource.res.tip.nrb.ItuStateAndStatusList.X721_CONTROL_STATUS It doest seem to make sense to have an array of constants like X721_AVAILABILITY_STATUS in this context. 2. Soap generator a) When the soap generator generates an enumeration Base Type 'int' in MPAC it generates the following example from tip_mpac_resource_res_tip_nrb.xsd. Why is the restriction base given as <xsd:restriction base="xsd:string"> rather than <xsd:restriction base="xsd:int"> for a tigerstripe Base Type 'int'. Should we not be generating <xsd:restriction base="xsd:int">? b) in the generated documentation all we get is something like 'This literal has value 0'. There is no mention of the name of the value in the xsd. Should we not be generating documentation in the xsd which says LOCKED=0, UNLOCKED=2. This is a minimum requirement but In fact, there is an argument that we should be generating constant values which include the named definition. <xsd:simpleType name="AdministrativeState"> <xsd:annotation> <xsd:documentation> <p></p> </xsd:documentation> </xsd:annotation> <xsd:restriction base="xsd:string"> <xsd:enumeration value="0"> <xsd:annotation> <xsd:documentation> <p></p> <p>This literal has value 0</p> </xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="2"> <xsd:annotation> <xsd:documentation> <p></p> <p>This literal has value 2</p> </xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value="1"> <xsd:annotation> <xsd:documentation> <p></p> <p>This literal has value 1</p> </xsd:documentation> </xsd:annotation> </xsd:enumeration> </xsd:restriction> </xsd:simpleType> <xsd:complexType name="ArrayOfAdministrativeState"> <xsd:sequence> <xsd:element name="item" type="tns:AdministrativeState" minOccurs="0" maxOccurs="unbounded"/> </xsd:sequence> </xsd:complexType> |
|
From: Flauw, M. <Mar...@hp...> - 2012-06-14 05:55:35
|
Hi Kumar, Thanks for the message. On Test1, were you doing the eclipse:eclipse or the clean install? Try doing the latter and usually, it goes away. On Test2, sometimes the build blocks in Tigerstripe. Usually what I do is the following: 1) remove velocity.log.* in Dependencies and model projects 2) remove the .lock and .snap in metadata. There is a an eclipse article on that, but if you cannot find it, I can dig detailed instructions. 3) do the mvn clean first 4) then do the mvn install. This way if the build blocks, you might restart it without to redo the clean steps, just doing steps 1 and 2 On Test3, it would be good to have the log. This is a test with unknown datatype, so the build should fail, but the error message is surprising. On Test4, it looks like the pom file has not been updated and it is looking for an old version of the generator. Aligning pom files with the latest ones from project creator should solve that. On Test5, you need to ask Xose. For me, it is still work in progress, so I won't worry about this one for time being. Best regards Marc From: man...@gm... [mailto:man...@gm...] On Behalf Of Manikumar Reddy Sent: Wednesday, June 13, 2012 9:39 PM To: Pierre Gauthier; Craig Gallen (entimoss) Cc: Tina O Sullivan; openoss-devel; Flauw, Marc; Craig Gallen (OpenNMS) Subject: Re: TIP Build Task updates and regression Hi > > For instance all the TIP_Fmk_Test1 project modules are all in https://openoss.svn.sourceforge.net/svnroot/openoss/tip/framework/TIP_Fmk_TestProjects/TIP_Fmk_Test1/trunk/ > > You may want to and do a manual tigerstripe generation of the model and dependency projects from the desktop. > Follow the getting started instructions to do a maven build. There are total five Framework Test projects. I tried to do maven build for these projects. But all these builds failed. The following errors occurred. TIP_Fmk_Test1: Missing: ---------- 1) org.tmforum.tip:TIP_Fmk_Test1_JvtSpecPackage:jar:1.1.2-SNAPSHOT TIP_Fmk_Test2: Build process is not responding. TIP_Fmk_Test3: [exec] Tigerstripe Workbench Base Plug-in (Incubation) (v0.6.935.2011020109 [exec] Active Profile: TIP_Profile 1.1.1 [exec] null [exec] java.lang.NullPointerException [exec] at org.eclipse.tigerstripe.workbench.internal.core.project.Tiger stripeProject.addDependency(TigerstripeProject.java:674) TIP_Fmk_Test4: [INFO] Unable to find artifact. Embedded error: Unable to download the artifact from any repository org.tmforum.tip:TIP_Doc_Generator_Package:jar:1.0.2 TIP_Fmk_Test5: [exec] [Fatal Error] :1:1: Premature end of file. [exec] Tigerstripe Workbench Base Plug-in (Incubation) (v0.6.935.2011020 [exec] Active Profile: TIP_Profile 1.1.1 [exec] null [exec] java.util.ConcurrentModificationException [exec] at java.util.AbstractList$Itr.checkForComodification(Unknown source) Details logs attached. > If this fails, we will need to find out what is wrong with the model relative to the new generators. I need your help in fixing above problems. > > Regardless of any problems with the generators you should still update the project build files as describe below I was able to create Fmk_Test1 project using project creator. > 6. compare and bring up to date each module in your main project > - update the project pom.xml to match the misc pom.xml I have merged pom files of all modules. Some conflicting lines i just copied to trunk project. > - update any resources / java file which are changed in the misc project > - remove any resources / java files or packages from the trunk which don't exist in the new 'misc' project > - add any new resources / java files or packages which don't exist in the 'trunk' project After updating all the projects, i ran maven build ( Without Java modules). Maven build process is not responding after some time, Below is the log trace. Any clue? [INFO] [antrun:run {execution: run-tigerstripe}] [INFO] Executing tasks [echo] MODEL_POM: eclipse_home: D:\eclipsets [echo] MODEL_POM: model_project_basedir: D:\ws-ts\TIP_Fmk_Test1_Model [echo] MODEL_POM: model_project__directory_name: TIP_Fmk_Test1_Model [echo] MODEL_POM: tigerstripe_workspace: D:\ws-ts [echo] MODEL_POM: referenced_project1: TIP_Fmk_Test1_Model [echo] MODEL_POM: tigerstripe_generation_project: TIP_Fmk_Test1_Model [echo] MODEL_POM: tigerstripe_arg_string: -nosplash -data D:\ws-ts -applica tion org.eclipse.tigerstripe.workbench.headless.tigerstripe D:\ws-ts\TIP_Fmk_Tes t1_Model GENERATION_PROJECT=D:\ws-ts\TIP_Fmk_Test1_Model [echo] MODEL_POM: D:\ws-ts\TIP_Fmk_Test1_Model\target\CODE_GENERATED_FLAG.t xt does not exist. Will run Tigerstripe Regards Kumar NMSWorks Software Pvt Ltd. +919840241620 |
|
From: Manikumar R. <ku...@nm...> - 2012-06-13 19:38:54
|
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Failed to resolve artifact.
Missing:
----------
1) org.tmforum.tip:TIP_Fmk_Test1_JvtSpecPackage:jar:1.1.2-SNAPSHOT
Try downloading the file manually from:
http://prdownloads.sourceforge.net/openoss
Then, install it using the command:
mvn install:install-file -DgroupId=org.tmforum.tip -DartifactId=TIP_Fmk_Te
st1_JvtSpecPackage -Dversion=1.1.2-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file there:
mvn deploy:deploy-file -DgroupId=org.tmforum.tip -DartifactId=TIP_Fmk_Test
1_JvtSpecPackage -Dversion=1.1.2-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -
Durl=[url] -DrepositoryId=[id]
Path to dependency:
1) org.openoss.tip:TIP_Fmk_Test1_EjbImplGenSrcPackage:jar:1.1.2-SNAPSHOT
2) org.tmforum.tip:TIP_Fmk_Test1_JvtSpecPackage:jar:1.1.2-SNAPSHOT
----------
1 required artifact is missing.
for artifact:
org.openoss.tip:TIP_Fmk_Test1_EjbImplGenSrcPackage:jar:1.1.2-SNAPSHOT
from the specified remote repositories:
openoss-tip.releases (http://openoss.myzen.co.uk/TIP/m2repo),
central (http://repo1.maven.org/maven2),
ibiblio-repo (http://www.ibiblio.org/maven2),
openoss-tip.snapshots (http://openoss.myzen.co.uk/TIP/m2repo-snapshots),
apache-repo (https://repository.apache.org/content/repositories/releases/)
|
|
From: Flauw, M. <Mar...@hp...> - 2012-06-12 09:49:07
|
Dear all, What is the status of the support of the 2 new primitive datatypes: uri and url? Uri is now used in the Common Model and this creates exception in the build for both the SOAP generator and the JVTSpec generator. Best regards Marc |
|
From: Xose R. S. V. <xr...@op...> - 2012-06-11 14:12:32
|
I've performed the checkin in the TRUNK for the *Soap Generator *and
the*Soap Generator Packag*e to support for internal filter in creation
of closure as in service interface
Best regards
El 11/06/2012 13:35, Xose Ramon Sousa Vazquez escribió:
> Hi all. I think that I have found the error and I will try to fix it
> as soon as possible. There are some related issues, one error in the
> codification of a method and a forgetted evaluation of filtering in
> the velocity template and also a case related with primitive type
> filter not supported in the build of the closure outside the interfaces.
>
> In the interfaces build the search is performed as follows(this works
> fine as reported Marc):
>
> if ("objectName".equalsIgnoreCase(argType.getName())) {
> /*
> * This data type 'objectName' defines the
> protocol
> * neutral unique name of an object. This
> data type will
> * be replaced by the generators by an
> EntityIdentifier
> */
> String pkg = PluginConstants
>
> .getPropVal(PluginConstants.KEY_INTERNAL_MODEL_PKG);
> if (!this.map.containsKey(pkg)) {
> //
> // New package - add new pkg=prefix
> mapping
> // assignment
> //
> String prefix =
> XmlSchemaHelpers.generateXmlPrefix(
> pkg, this.map);
> this.map.put(pkg, prefix);
> }
> } else if
> ("filter".equalsIgnoreCase(argType.getName())) {
> /*
> * This data type 'filter'. This data type
> will
> * be replaced by the generator to
> */
> String pkg = PluginConstants
>
> .getPropVal(PluginConstants.KEY_INTERNAL_FILTER_PKG);
> if (!this.map.containsKey(pkg)) {
> //
> // New package - add new pkg=prefix
> mapping
> // assignment
> //
> String prefix =
> XmlSchemaHelpers.generateXmlPrefix(
> pkg, this.map);
> this.map.put(pkg, prefix);
> }
> } else if
> (XmlSchemaHelpers.isUnbounded(argType)) {
> String pkg = PluginConstants
>
> .getPropVal(PluginConstants.KEY_INTERNAL_MODEL_PRIMITIVES_PKG);
> if (!this.map.containsKey(pkg)) {
> //
> // New package - add new pkg=prefix
> mapping
> // assignment
> //
> String prefix =
> XmlSchemaHelpers.generateXmlPrefix(
> pkg, this.map);
> this.map.put(pkg, prefix);
> }
> } else {
> // XSD default namespace is enough
> }
>
> and in the build of the closure we have got (this fails as reported
> Craig):
>
> if ("objectName".equalsIgnoreCase(type.getName())){
> PluginLog.logDebug("type \'" + type
> + "\' is an array of primitive.");
> addReferencedPackage(PluginConstants
>
> .getPropVal(PluginConstants.KEY_INTERNAL_MODEL_PKG));
> }else if (XmlSchemaHelpers.isUnbounded(type)){
> //will map to array of primitive
> addReferencedPackage(PluginConstants
>
> .getPropVal(PluginConstants.KEY_INTERNAL_MODEL_PRIMITIVES_PKG));
> } else {
> //normal primtive like xsd:int
> }
>
> so the filtering never is considered.
>
> I will perform clean tests because was very difficult to find the real
> cause of the problem, the log file is not very clear in debug
> scenarios ( a lot of similar log text, no log from the templates and
> also cannot put the line number in the log file (tigerstripe issue))
> and these problems have delayed my response.
> If the test go ok I will check out the changes to the trunk
>
> https://openoss.svn.sourceforge.net/svnroot/openoss/tip/framework/TIP_Soap_Generator/trunk/TIP_Soap_Generator
>
> Best regards
>
>
> El 01/06/2012 16:58, Craig Gallen escribió:
>> Hi,
>>
>> I agree it is defined in internal_filter.xsd but it doesn't seem to be
>> referenced properly from dep_cbe_perf_spec.xsd in the PM project. WSDL2Java
>> throws an error and when you open dep_cbe_perf_spec.xsd in eclipse it also
>> shows an error.
>>
>> I think Xose is looking into it
>>
>> Craig
>>
>> -----Original Message-----
>> From: Flauw, Marc [mailto:Mar...@hp...]
>> Sent: 01 June 2012 10:25
>> To: Craig Gallen (opennms); openoss-devel; Xose Ramon Sousa Vazquez; pierre
>> gauthier
>> Subject: RE: Problems with PM XSD generation
>>
>> Craig,
>>
>> There is one same filter in the getReosurceAlarms operation, filter
>> argument.
>> The XPathFilter is defined in the internal_filter.xsd
>>
>> Best regards
>>
>> Marc
>>
>> -----Original Message-----
>> From: Craig Gallen [mailto:gal...@go...] On Behalf Of Craig
>> Gallen (opennms)
>> Sent: Thursday, May 31, 2012 11:58 PM
>> To: openoss-devel; Flauw, Marc; Xose Ramon Sousa Vazquez; pierre gauthier
>> Subject: Problems with PM XSD generation
>>
>> Hi,
>>
>> I have been testing the TIP_PM_Col project model and have found that the
>> dep_cbe_perf_spec.xsd (attached) file is generated with errors
>>
>> in line 62 we have
>> <xsd:element name="objectInstanceFilter" type="filter:XPathQueryFilter"
>> minOccurs="0" maxOccurs="1">
>>
>> filter:XPathQueryFilter is not defined and if you open the file in eclipse
>> it reports this error as:
>>
>> 's4s-att-invalid-value: Invalid attribute value for 'type' in element
>> 'element'. Recorded reason:
>> UndeclaredPrefix: Cannot resolve 'filter:XPathQueryFilter' as a QName:
>> the prefix 'filter' is not
>> declared'.
>>
>> Is this a known problem or a new bug?
>>
>> Craig
>>
>
>
> --
>
> *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><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><http://optarecoolvendor.com>
|
|
From: Xose R. S. V. <xr...@op...> - 2012-06-11 11:42:54
|
Hi all. I think that I have found the error and I will try to fix it as
soon as possible. There are some related issues, one error in the
codification of a method and a forgetted evaluation of filtering in the
velocity template and also a case related with primitive type filter not
supported in the build of the closure outside the interfaces.
In the interfaces build the search is performed as follows(this works
fine as reported Marc):
if ("objectName".equalsIgnoreCase(argType.getName())) {
/*
* This data type 'objectName' defines the
protocol
* neutral unique name of an object. This
data type will
* be replaced by the generators by an
EntityIdentifier
*/
String pkg = PluginConstants
.getPropVal(PluginConstants.KEY_INTERNAL_MODEL_PKG);
if (!this.map.containsKey(pkg)) {
//
// New package - add new pkg=prefix mapping
// assignment
//
String prefix =
XmlSchemaHelpers.generateXmlPrefix(
pkg, this.map);
this.map.put(pkg, prefix);
}
} else if
("filter".equalsIgnoreCase(argType.getName())) {
/*
* This data type 'filter'. This data type will
* be replaced by the generator to
*/
String pkg = PluginConstants
.getPropVal(PluginConstants.KEY_INTERNAL_FILTER_PKG);
if (!this.map.containsKey(pkg)) {
//
// New package - add new pkg=prefix mapping
// assignment
//
String prefix =
XmlSchemaHelpers.generateXmlPrefix(
pkg, this.map);
this.map.put(pkg, prefix);
}
} else if (XmlSchemaHelpers.isUnbounded(argType)) {
String pkg = PluginConstants
.getPropVal(PluginConstants.KEY_INTERNAL_MODEL_PRIMITIVES_PKG);
if (!this.map.containsKey(pkg)) {
//
// New package - add new pkg=prefix mapping
// assignment
//
String prefix =
XmlSchemaHelpers.generateXmlPrefix(
pkg, this.map);
this.map.put(pkg, prefix);
}
} else {
// XSD default namespace is enough
}
and in the build of the closure we have got (this fails as reported Craig):
if ("objectName".equalsIgnoreCase(type.getName())){
PluginLog.logDebug("type \'" + type
+ "\' is an array of primitive.");
addReferencedPackage(PluginConstants
.getPropVal(PluginConstants.KEY_INTERNAL_MODEL_PKG));
}else if (XmlSchemaHelpers.isUnbounded(type)){
//will map to array of primitive
addReferencedPackage(PluginConstants
.getPropVal(PluginConstants.KEY_INTERNAL_MODEL_PRIMITIVES_PKG));
} else {
//normal primtive like xsd:int
}
so the filtering never is considered.
I will perform clean tests because was very difficult to find the real
cause of the problem, the log file is not very clear in debug scenarios
( a lot of similar log text, no log from the templates and also cannot
put the line number in the log file (tigerstripe issue)) and these
problems have delayed my response.
If the test go ok I will check out the changes to the trunk
https://openoss.svn.sourceforge.net/svnroot/openoss/tip/framework/TIP_Soap_Generator/trunk/TIP_Soap_Generator
Best regards
El 01/06/2012 16:58, Craig Gallen escribió:
> Hi,
>
> I agree it is defined in internal_filter.xsd but it doesn't seem to be
> referenced properly from dep_cbe_perf_spec.xsd in the PM project. WSDL2Java
> throws an error and when you open dep_cbe_perf_spec.xsd in eclipse it also
> shows an error.
>
> I think Xose is looking into it
>
> Craig
>
> -----Original Message-----
> From: Flauw, Marc [mailto:Mar...@hp...]
> Sent: 01 June 2012 10:25
> To: Craig Gallen (opennms); openoss-devel; Xose Ramon Sousa Vazquez; pierre
> gauthier
> Subject: RE: Problems with PM XSD generation
>
> Craig,
>
> There is one same filter in the getReosurceAlarms operation, filter
> argument.
> The XPathFilter is defined in the internal_filter.xsd
>
> Best regards
>
> Marc
>
> -----Original Message-----
> From: Craig Gallen [mailto:gal...@go...] On Behalf Of Craig
> Gallen (opennms)
> Sent: Thursday, May 31, 2012 11:58 PM
> To: openoss-devel; Flauw, Marc; Xose Ramon Sousa Vazquez; pierre gauthier
> Subject: Problems with PM XSD generation
>
> Hi,
>
> I have been testing the TIP_PM_Col project model and have found that the
> dep_cbe_perf_spec.xsd (attached) file is generated with errors
>
> in line 62 we have
> <xsd:element name="objectInstanceFilter" type="filter:XPathQueryFilter"
> minOccurs="0" maxOccurs="1">
>
> filter:XPathQueryFilter is not defined and if you open the file in eclipse
> it reports this error as:
>
> 's4s-att-invalid-value: Invalid attribute value for 'type' in element
> 'element'. Recorded reason:
> UndeclaredPrefix: Cannot resolve 'filter:XPathQueryFilter' as a QName:
> the prefix 'filter' is not
> declared'.
>
> Is this a known problem or a new bug?
>
> Craig
>
--
*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><http://optarecoolvendor.com>
|
|
From: Pierre G. <pga...@tm...> - 2012-06-04 12:36:29
|
Hi Craig, Yes this looks good. Kumar with follow up with you. Pierre Le 2012-06-04 à 4:44, "Craig Gallen (entimoss)" <cra...@en...> a écrit : > Hi, > > For regression, we need to bring the build scripts of all of the test projects up to the latest level and then build the models and check that everything works OK. I have already done this with RAM, MPAC and PM. To do this we need to use the Project Creator to create a new version of the project with the latest build files and resources and then use these as a template to compare with and update the trunk version of the test project you are updating. > > First check out the tigerstripe modules you need; > > Check out and install the latest tigerstripe profile > https://openoss.svn.sourceforge.net/svnroot/openoss/tip/framework/TIP_Profile/trunk/TIP_Profile_Model > > Check out and install the latest tigerstripe generators ( remember to remove installed generators first ) > https://openoss.svn.sourceforge.net/svnroot/openoss/tip/framework/TIP_Soap_Generator/trunk/TIP_Soap_Generator > https://openoss.svn.sourceforge.net/svnroot/openoss/tip/framework/TIP_Doc_Generator/trunk/TIP_Doc_Generator > https://openoss.svn.sourceforge.net/svnroot/openoss/tip/platform/TIP_EjbImpl_Generator/trunk/TIP_EjbImpl_Generator > https://openoss.svn.sourceforge.net/svnroot/openoss/tip/platform/TIP_JvtSpec_Generator/trunk/TIP_JvtSpec_Generator > https://openoss.svn.sourceforge.net/svnroot/openoss/tip/platform/TIP_SoapImpl_Generator/trunk/TIP_SoapImpl_Generator > > Check out all modules of the latest version of the test project following the process in > http://sourceforge.net/apps/mediawiki/openoss/index.php?title=Getting_Started > > For instance all the TIP_Fmk_Test1 project modules are all in https://openoss.svn.sourceforge.net/svnroot/openoss/tip/framework/TIP_Fmk_TestProjects/TIP_Fmk_Test1/trunk/ > > You may want to and do a manual tigerstripe generation of the model and dependency projects from the desktop. > Follow the getting started instructions to do a maven build. > If this fails, we will need to find out what is wrong with the model relative to the new generators. > > Regardless of any problems with the generators you should still update the project build files as describe below. > > We now need to update the project build files > > 1. obtain the latest snapshot project creator this can be found at > http://openoss.myzen.co.uk/TIP/m2repo-snapshots/org/openoss/tip/TIP_Project_Creator/1.1.2-SNAPSHOT/ > the latest project creator will be contained in a jar named like TIP_Project_Creator-1.1.2-20120604.074637-1-standard.jar where the middle numbers are the date and time of upload. Use the most recent snapshot. > > 2. create a new empty project in your workspace called something like 'misc' > > 3. move the project creator jar into this 'misc' folder in widows explorer > > 4. double click on the project creator jar to start it. > > 5. Fill in the following details; > a) in the first panel replace the name TIP_ArchetypeProject with the name of the project you are updating > b) replace the version numbers with the version number of the project you are updating > c) open the MODEL tigerstripe.xml and find modelId. place this in the model id line of the first panel > d) click through the rest of the panels and create the project in your misc directory > you should now have a project with the same naming as the project your are updating. > > 6. compare and bring up to date each module in your main project > a) refresh 'misc' in eclipse to see the project modules. > b) for each module in the project you are updating , click to select the module then use 'control click' to select the same module in 'misc'. This should select ONLY the two modules you are comparing. > c) right click on one of the modules and select Compare With>eachother > d) eclipse should give you a diff between the modules. You then need to update the following in the trunk project > - update the project pom.xml to match the misc pom.xml > - update any resources / java file which are changed in the misc project > - remove any resources / java files or packages from the trunk which don't exist in the new 'misc' project > - add any new resources / java files or packages which don't exist in the 'trunk' project > > 7. New modules may have been added to the misc project created by the project creator which don't exist in the test project. If this is the cases, they need to be added to the /trunk subversion repository and checked out > > once you have successfully updated the project build , check it in - even if it doesn't completely work. We may have problems with the generators which are causing the build to fail. This is why we do regression tests. > > Note - very important; > a) do not update or change the /src model classes in the MODEL or DEPENCENCIES projects . These are the one thing which carries over between the update > b) do not replace or change the .classpath, .project, . properties which exist in your checked out project. These will not exist in the 'misc' modules > c) by default the project creator create a BaseProject pom.xml with the java build modules disabled and only builds the specification and doumentation. Get these working first for all of the the projects before trying to get the java modules to work. > > I hope this is enough to get you going > > Craig > > On 31/05/2012 19:02, Pierre Gauthier wrote: >> Hi, >> >> I would like to setup a meeting to discuss Kumar first task. >> >> Craig can you prepare a quick presentation highlighting what is required from >> Kumar precisely ? A simple power point. >> >> I would like to go over the requirements with you and Kumar to make sure >> that we both understand them and fix a schedule for the deliverables. >> >> >> Are you both available tomorrow Morning Eastern Time Canada 10:00 AM ? >> >> Regards Pierre >> >> >> > |
|
From: Manikumar R. <ku...@nm...> - 2012-06-04 12:26:10
|
Hi Craig, Thanks for the directions. I will start working on this and let you know the status. Regards Kumar On Mon, Jun 4, 2012 at 5:51 PM, Pierre Gauthier <pga...@tm...>wrote: > Hi Craig, > > Yes this looks good. > > Kumar with follow up with you. > > Pierre > > > > Le 2012-06-04 à 4:44, "Craig Gallen (entimoss)" <cra...@en...> > a écrit : > > > Hi, > > > > For regression, we need to bring the build scripts of all of the test > projects up to the latest level and then build the models and check that > everything works OK. I have already done this with RAM, MPAC and PM. To do > this we need to use the Project Creator to create a new version of the > project with the latest build files and resources and then use these as a > template to compare with and update the trunk version of the test project > you are updating. > > > > First check out the tigerstripe modules you need; > > > > Check out and install the latest tigerstripe profile > > > https://openoss.svn.sourceforge.net/svnroot/openoss/tip/framework/TIP_Profile/trunk/TIP_Profile_Model > > > > Check out and install the latest tigerstripe generators ( remember to > remove installed generators first ) > > > https://openoss.svn.sourceforge.net/svnroot/openoss/tip/framework/TIP_Soap_Generator/trunk/TIP_Soap_Generator > > > https://openoss.svn.sourceforge.net/svnroot/openoss/tip/framework/TIP_Doc_Generator/trunk/TIP_Doc_Generator > > > https://openoss.svn.sourceforge.net/svnroot/openoss/tip/platform/TIP_EjbImpl_Generator/trunk/TIP_EjbImpl_Generator > > > https://openoss.svn.sourceforge.net/svnroot/openoss/tip/platform/TIP_JvtSpec_Generator/trunk/TIP_JvtSpec_Generator > > > https://openoss.svn.sourceforge.net/svnroot/openoss/tip/platform/TIP_SoapImpl_Generator/trunk/TIP_SoapImpl_Generator > > > > Check out all modules of the latest version of the test project > following the process in > > > http://sourceforge.net/apps/mediawiki/openoss/index.php?title=Getting_Started > > > > For instance all the TIP_Fmk_Test1 project modules are all in > https://openoss.svn.sourceforge.net/svnroot/openoss/tip/framework/TIP_Fmk_TestProjects/TIP_Fmk_Test1/trunk/ > > > > You may want to and do a manual tigerstripe generation of the model and > dependency projects from the desktop. > > Follow the getting started instructions to do a maven build. > > If this fails, we will need to find out what is wrong with the model > relative to the new generators. > > > > Regardless of any problems with the generators you should still update > the project build files as describe below. > > > > We now need to update the project build files > > > > 1. obtain the latest snapshot project creator this can be found at > > > http://openoss.myzen.co.uk/TIP/m2repo-snapshots/org/openoss/tip/TIP_Project_Creator/1.1.2-SNAPSHOT/ > > the latest project creator will be contained in a jar named like > TIP_Project_Creator-1.1.2-20120604.074637-1-standard.jar where the middle > numbers are the date and time of upload. Use the most recent snapshot. > > > > 2. create a new empty project in your workspace called something like > 'misc' > > > > 3. move the project creator jar into this 'misc' folder in widows > explorer > > > > 4. double click on the project creator jar to start it. > > > > 5. Fill in the following details; > > a) in the first panel replace the name TIP_ArchetypeProject with the > name of the project you are updating > > b) replace the version numbers with the version number of the project > you are updating > > c) open the MODEL tigerstripe.xml and find modelId. place this in the > model id line of the first panel > > d) click through the rest of the panels and create the project in your > misc directory > > you should now have a project with the same naming as the project your > are updating. > > > > 6. compare and bring up to date each module in your main project > > a) refresh 'misc' in eclipse to see the project modules. > > b) for each module in the project you are updating , click to select the > module then use 'control click' to select the same module in 'misc'. This > should select ONLY the two modules you are comparing. > > c) right click on one of the modules and select Compare With>eachother > > d) eclipse should give you a diff between the modules. You then need to > update the following in the trunk project > > - update the project pom.xml to match the misc pom.xml > > - update any resources / java file which are changed in the misc project > > - remove any resources / java files or packages from the trunk which > don't exist in the new 'misc' project > > - add any new resources / java files or packages which don't exist in > the 'trunk' project > > > > 7. New modules may have been added to the misc project created by the > project creator which don't exist in the test project. If this is the > cases, they need to be added to the /trunk subversion repository and > checked out > > > > once you have successfully updated the project build , check it in - > even if it doesn't completely work. We may have problems with the > generators which are causing the build to fail. This is why we do > regression tests. > > > > Note - very important; > > a) do not update or change the /src model classes in the MODEL or > DEPENCENCIES projects . These are the one thing which carries over between > the update > > b) do not replace or change the .classpath, .project, . properties which > exist in your checked out project. These will not exist in the 'misc' > modules > > c) by default the project creator create a BaseProject pom.xml with the > java build modules disabled and only builds the specification and > doumentation. Get these working first for all of the the projects before > trying to get the java modules to work. > > > > I hope this is enough to get you going > > > > Craig > > > > On 31/05/2012 19:02, Pierre Gauthier wrote: > >> Hi, > >> > >> I would like to setup a meeting to discuss Kumar first task. > >> > >> Craig can you prepare a quick presentation highlighting what is > required from > >> Kumar precisely ? A simple power point. > >> > >> I would like to go over the requirements with you and Kumar to make > sure > >> that we both understand them and fix a schedule for the deliverables. > >> > >> > >> Are you both available tomorrow Morning Eastern Time Canada 10:00 AM ? > >> > >> Regards Pierre > >> > >> > >> > > > > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > > |
|
From: Craig G. (opennms) <cg...@op...> - 2012-06-04 08:47:37
|
Hi, For regression, we need to bring the build scripts of all of the test projects up to the latest level and then build the models and check that everything works OK. I have already done this with RAM, MPAC and PM. To do this we need to use the Project Creator to create a new version of the project with the latest build files and resources and then use these as a template to compare with and update the trunk version of the test project you are updating. First check out the tigerstripe modules you need; Check out and install the latest tigerstripe profile https://openoss.svn.sourceforge.net/svnroot/openoss/tip/framework/TIP_Profile/trunk/TIP_Profile_Model Check out and install the latest tigerstripe generators ( remember to remove installed generators first ) https://openoss.svn.sourceforge.net/svnroot/openoss/tip/framework/TIP_Soap_Generator/trunk/TIP_Soap_Generator https://openoss.svn.sourceforge.net/svnroot/openoss/tip/framework/TIP_Doc_Generator/trunk/TIP_Doc_Generator https://openoss.svn.sourceforge.net/svnroot/openoss/tip/platform/TIP_EjbImpl_Generator/trunk/TIP_EjbImpl_Generator https://openoss.svn.sourceforge.net/svnroot/openoss/tip/platform/TIP_JvtSpec_Generator/trunk/TIP_JvtSpec_Generator https://openoss.svn.sourceforge.net/svnroot/openoss/tip/platform/TIP_SoapImpl_Generator/trunk/TIP_SoapImpl_Generator Check out all modules of the latest version of the test project following the process in http://sourceforge.net/apps/mediawiki/openoss/index.php?title=Getting_Started For instance all the TIP_Fmk_Test1 project modules are all in https://openoss.svn.sourceforge.net/svnroot/openoss/tip/framework/TIP_Fmk_TestProjects/TIP_Fmk_Test1/trunk/ You may want to and do a manual tigerstripe generation of the model and dependency projects from the desktop. Follow the getting started instructions to do a maven build. If this fails, we will need to find out what is wrong with the model relative to the new generators. Regardless of any problems with the generators you should still update the project build files as describe below. We now need to update the project build files 1. obtain the latest snapshot project creator this can be found at http://openoss.myzen.co.uk/TIP/m2repo-snapshots/org/openoss/tip/TIP_Project_Creator/1.1.2-SNAPSHOT/ the latest project creator will be contained in a jar named like TIP_Project_Creator-1.1.2-20120604.074637-1-standard.jar where the middle numbers are the date and time of upload. Use the most recent snapshot. 2. create a new empty project in your workspace called something like 'misc' 3. move the project creator jar into this 'misc' folder in widows explorer 4. double click on the project creator jar to start it. 5. Fill in the following details; a) in the first panel replace the name TIP_ArchetypeProject with the name of the project you are updating b) replace the version numbers with the version number of the project you are updating c) open the MODEL tigerstripe.xml and find modelId. place this in the model id line of the first panel d) click through the rest of the panels and create the project in your misc directory you should now have a project with the same naming as the project your are updating. 6. compare and bring up to date each module in your main project a) refresh 'misc' in eclipse to see the project modules. b) for each module in the project you are updating , click to select the module then use 'control click' to select the same module in 'misc'. This should select ONLY the two modules you are comparing. c) right click on one of the modules and select Compare With>eachother d) eclipse should give you a diff between the modules. You then need to update the following in the trunk project - update the project pom.xml to match the misc pom.xml - update any resources / java file which are changed in the misc project - remove any resources / java files or packages from the trunk which don't exist in the new 'misc' project - add any new resources / java files or packages which don't exist in the 'trunk' project 7. New modules may have been added to the misc project created by the project creator which don't exist in the test project. If this is the cases, they need to be added to the /trunk subversion repository and checked out once you have successfully updated the project build , check it in - even if it doesn't completely work. We may have problems with the generators which are causing the build to fail. This is why we do regression tests. Note - very important; a) do not update or change the /src model classes in the MODEL or DEPENCENCIES projects . These are the one thing which carries over between the update b) do not replace or change the .classpath, .project, . properties which exist in your checked out project. These will not exist in the 'misc' modules c) by default the project creator create a BaseProject pom.xml with the java build modules disabled and only builds the specification and doumentation. Get these working first for all of the the projects before trying to get the java modules to work. I hope this is enough to get you going Craig On 31/05/2012 19:02, Pierre Gauthier wrote: > Hi, > > I would like to setup a meeting to discuss Kumar first task. > > Craig can you prepare a quick presentation highlighting what is required from > Kumar precisely ? A simple power point. > > I would like to go over the requirements with you and Kumar to make sure > that we both understand them and fix a schedule for the deliverables. > > > Are you both available tomorrow Morning Eastern Time Canada 10:00 AM ? > > Regards Pierre > > > |