Menu
▾
▴
openoss-devel — OpenOSS Developer Mailing List
You can subscribe to this list here.
| 2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(53) |
Aug
(86) |
Sep
(55) |
Oct
(19) |
Nov
(12) |
Dec
(9) |
| 2010 |
Jan
(8) |
Feb
(32) |
Mar
(31) |
Apr
(70) |
May
(67) |
Jun
(71) |
Jul
(26) |
Aug
(47) |
Sep
(25) |
Oct
(16) |
Nov
(11) |
Dec
(16) |
| 2011 |
Jan
(30) |
Feb
(31) |
Mar
(71) |
Apr
(64) |
May
(55) |
Jun
(25) |
Jul
(3) |
Aug
(24) |
Sep
(20) |
Oct
(18) |
Nov
(21) |
Dec
(1) |
| 2012 |
Jan
(9) |
Feb
(21) |
Mar
(29) |
Apr
(9) |
May
(9) |
Jun
(54) |
Jul
(37) |
Aug
(24) |
Sep
(43) |
Oct
(34) |
Nov
(25) |
Dec
(27) |
| 2013 |
Jan
(5) |
Feb
(13) |
Mar
(23) |
Apr
(9) |
May
(11) |
Jun
|
Jul
(2) |
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2014 |
Jan
(1) |
Feb
|
Mar
(3) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: pierre g. <pie...@os...> - 2012-08-22 20:57:29
|
Hi Craig, Marc
We would like to freeze 12.5 but I'm getting the following error building RAM
Loading DataBinding jaxb ...
[java] wsdl2java -xjc-b,C:\ws-tsempty\TIP_RAM_SoapImplGenSrcPackage\src\test\resources\xjb-binding.xjb -verbose -b C:\ws-tsempty\TIP_RAM_SoapImplGenSrcPackage\target\test-classes\async_binding.xml -catalog C:\ws-tsempty\TIP_RAM_SoapImplGenSrcPackage\target\wsdl-dependencies\tip-wsdl-dependencies-catalog.xml -d C:\ws-tsempty\TIP_RAM_SoapImplGenSrcPackage\target\temp-generated-cxf-sources\src\main\java C:\ws-tsempty\TIP_RAM_SoapImplGenSrcPackage\target\generated-cxf-sources\src\main\resources\wsdl\wsn_bindings_http.wsdl
[java] wsdl2java - Apache CXF 2.2.10
[java]
[java]
[java] WSDLToJava Error: Could not find any node with the XPath expression: //wsdl:definitions/wsdl:types/xsd:schema
[java]
[java] org.apache.cxf.tools.common.ToolException: Could not find any node with the XPath expression: //wsdl:definitions/wsdl:types/xsd:schema
[java] at org.apache.cxf.tools.wsdlto.frontend.jaxws.customization.CustomizationParser.internalizeBinding(CustomizationParser.java:354)
[java] at org.apache.cxf.tools.wsdlto.frontend.jaxws.customization.CustomizationParser.internalizeBinding(CustomizationParser.java:371)
[java] at org.apache.cxf.tools.wsdlto.frontend.jaxws.customization.CustomizationParser.parse(CustomizationParser.java:125)
[java] at org.apache.cxf.tools.wsdlto.frontend.jaxws.wsdl11.JAXWSDefinitionBuilder.customize(JAXWSDefinitionBuilder.java:114)
[java] at org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.processWsdl(WSDLToJavaContainer.java:162)
[java] at org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.execute(WSDLToJavaContainer.java:128)
[java] at org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.execute(WSDLToJavaContainer.java:271)
[java] at org.apache.cxf.tools.common.toolspec.ToolRunner.runTool(ToolRunner.java:103)
[java] at org.apache.cxf.tools.wsdlto.WSDLToJava.run(WSDLToJava.java:113)
[java] at org.apache.cxf.tools.wsdlto.WSDLToJava.run(WSDLToJava.java:86)
[java] at org.apache.cxf.tools.wsdlto.WSDLToJava.main(WSDLToJava.java:184)
[echo] WSDL2JAVA: processing object factories for this run
[echo] PROCESSING-SOURCES: absoluteofpaths:
[echo] WSDL2JAVA: of-paths:
Please advise.
Pierre
|
|
From: Flauw, M. <Mar...@hp...> - 2012-08-21 14:02:11
|
Dear all, I have updated the Common model. I used the latest version from SVN as basis. The changes are - Update to IA documentation - Some changes in cardinality in Schedule datatypes - In ScheduleDefinitionExcludedDates, the excludedDates attribute is now a primitive.date, as it is date (just the day part) really and not dateTime (day + time). The primitive.date is translated in xsd as <xsd:element name="excludedDates" type="primitives:ArrayOfDate" minOccurs="0"> Best regards Marc |
|
From: Xose R. S. V. <xr...@op...> - 2012-08-21 13:03:04
|
I have found the errors and now I am fixing. I have selected the name
org_tmforum_tip as the name for the root package entities. If anothe is
desired I will change quickly.
Best regards
El 15/08/2012 17:40, Craig Gallen (opennms) escribió:
> Xose,
> Further to my previous post and perhaps more worrying. I find I get
> the same error if I create any artifacts in the 'root package'.
>
> to recreate;
> 1. create a new tigerstripe model
> 2. enable the soap generator
> 3. in the soap generator settings in tigerstripe.xml ensure root
> package is set
> <property name="ROOT_PKG">org.tmforum.tip</property>
> 4. in tigerstripe model create an entity in package org.tmforum.tip
> 5. generate model
>
> you get the following error
> ERROR ? [15-Aug-2012 16:28:22.760] - Unexpected error while merging
> 'templates/dependencyAnalyzer.vm' template: Invocation of method
> 'constructClosure' in class
> org.eclipse.tigerstripe.generators.xml.filters.DependencyAnalyzer
> threw exception java.lang.StringIndexOutOfBoundsException: String
> index out of range: -1 @ templates/dependencyAnalyzer.vm[7,21].
> Generation may be incomplete. [2012-08-15 16:28:21.976+0100]
> ...
> Caused by: java.lang.StringIndexOutOfBoundsException: String index out
> of range: -1
> at java.lang.String.substring(Unknown Source)
> at java.lang.String.substring(Unknown Source)
> at
> org.eclipse.tigerstripe.generators.xml.helpers.XmlSchemaHelpers.mapPackageToSchemaLocation(XmlSchemaHelpers.java:141)
> at
> org.eclipse.tigerstripe.generators.xml.helpers.XsdReferencesMgr.<init>(XsdReferencesMgr.java:67)
>
> this is caused by the following code at XmlSchemaHelpers.java line141
> when pkgOrSession='org.tmforum.tip' and root='org.tmforum.tip'
>
> if (pkgOrSession.startsWith(root)) {
> loc = pkgOrSession.substring(root.length() + 1);
> }
>
> Cheers
> Craig
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> On 15/08/2012 15:20, Craig Gallen (opennms) wrote:
>> Xose,
>>
>> This is a minor bug which may cause confusion when people start using
>> tigerstripe.
>>
>> When I run the Soap Generator against an empty model project I get
>> the following error;
>>
>> Unexpected error while merging 'templates/dependencyAnalyzer.vm'
>> template: Invocation of method 'getPackagesFromArtifacts' in class
>> org.eclipse.tigerstripe.generators.xml.helpers.ModelHelpers threw
>> exception java.lang.ClassCastException: $Proxy12 cannot be cast to
>> org.eclipse.tigerstripe.workbench.internal.core.model.AbstractArtifact @
>> templates/dependencyAnalyzer.vm[4,43]. Generation may be incomplete.
>>
>> Details;
>> org.eclipse.tigerstripe.workbench.TigerstripeException: Unexpected
>> error while merging 'templates/dependencyAnalyzer.vm' template:
>> Invocation of method 'getPackagesFromArtifacts' in class
>> org.eclipse.tigerstripe.generators.xml.helpers.ModelHelpers threw
>> exception java.lang.ClassCastException: $Proxy12 cannot be cast to
>> org.eclipse.tigerstripe.workbench.internal.core.model.AbstractArtifact @
>> templates/dependencyAnalyzer.vm[4,43]
>> at
>> org.eclipse.tigerstripe.workbench.internal.core.project.pluggable.rules.GlobalTemplateRule.trigger(GlobalTemplateRule.java:183)
>> at
>> org.eclipse.tigerstripe.workbench.internal.core.plugin.pluggable.PluginRuleExecutor.trigger(PluginRuleExecutor.java:80)
>> at
>> org.eclipse.tigerstripe.workbench.internal.core.plugin.pluggable.PluggablePlugin.trigger(PluggablePlugin.java:158)
>> at
>> org.eclipse.tigerstripe.workbench.internal.core.plugin.PluginHousing.trigger(PluginHousing.java:35)
>> at
>> org.eclipse.tigerstripe.workbench.internal.core.plugin.PluginConfig.trigger(PluginConfig.java:259)
>> at
>> org.eclipse.tigerstripe.workbench.internal.core.generation.M1Generator.internalPluginLoop(M1Generator.java:671)
>> at
>> org.eclipse.tigerstripe.workbench.internal.core.generation.M1Generator.internalRun(M1Generator.java:613)
>> at
>> org.eclipse.tigerstripe.workbench.internal.core.generation.M1Generator.run(M1Generator.java:349)
>> at
>> org.eclipse.tigerstripe.workbench.internal.api.impl.TigerstripeProjectHandle.generate(TigerstripeProjectHandle.java:514)
>> at
>> org.eclipse.tigerstripe.workbench.ui.internal.wizards.generate.NewTigerstripeRunWizard.finishPage(NewTigerstripeRunWizard.java:95)
>> at
>> org.eclipse.tigerstripe.workbench.ui.internal.wizards.NewTSElementWizard$2.run(NewTSElementWizard.java:154)
>> at
>> org.eclipse.jdt.internal.core.BatchOperation.executeOperation(BatchOperation.java:39)
>> at
>> org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaModelOperation.java:728)
>> at
>> org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1975)
>> at org.eclipse.jdt.core.JavaCore.run(JavaCore.java:4777)
>> at
>> org.eclipse.jdt.internal.ui.actions.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:106)
>> at
>> org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
>> org.apache.velocity.exception.MethodInvocationException: Invocation
>> of method 'getPackagesFromArtifacts' in class
>> org.eclipse.tigerstripe.generators.xml.helpers.ModelHelpers threw
>> exception java.lang.ClassCastException: $Proxy12 cannot be cast to
>> org.eclipse.tigerstripe.workbench.internal.core.model.AbstractArtifact @
>> templates/dependencyAnalyzer.vm[4,43]
>> at
>> org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:286)
>> at
>> org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:203)
>> at
>> org.apache.velocity.runtime.parser.node.ASTReference.value(ASTReference.java:419)
>> at
>> org.apache.velocity.runtime.parser.node.ASTExpression.value(ASTExpression.java:73)
>> at
>> org.apache.velocity.runtime.parser.node.ASTSetDirective.render(ASTSetDirective.java:125)
>> at
>> org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:318)
>> at org.apache.velocity.Template.merge(Template.java:254)
>> at
>> org.eclipse.tigerstripe.workbench.internal.core.project.pluggable.rules.GlobalTemplateRule.trigger(GlobalTemplateRule.java:162)
>> at
>> org.eclipse.tigerstripe.workbench.internal.core.plugin.pluggable.PluginRuleExecutor.trigger(PluginRuleExecutor.java:80)
>> at
>> org.eclipse.tigerstripe.workbench.internal.core.plugin.pluggable.PluggablePlugin.trigger(PluggablePlugin.java:158)
>> at
>> org.eclipse.tigerstripe.workbench.internal.core.plugin.PluginHousing.trigger(PluginHousing.java:35)
>> at
>> org.eclipse.tigerstripe.workbench.internal.core.plugin.PluginConfig.trigger(PluginConfig.java:259)
>> at
>> org.eclipse.tigerstripe.workbench.internal.core.generation.M1Generator.internalPluginLoop(M1Generator.java:671)
>> at
>> org.eclipse.tigerstripe.workbench.internal.core.generation.M1Generator.internalRun(M1Generator.java:613)
>> at
>> org.eclipse.tigerstripe.workbench.internal.core.generation.M1Generator.run(M1Generator.java:349)
>> at
>> org.eclipse.tigerstripe.workbench.internal.api.impl.TigerstripeProjectHandle.generate(TigerstripeProjectHandle.java:514)
>> at
>> org.eclipse.tigerstripe.workbench.ui.internal.wizards.generate.NewTigerstripeRunWizard.finishPage(NewTigerstripeRunWizard.java:95)
>> at
>> org.eclipse.tigerstripe.workbench.ui.internal.wizards.NewTSElementWizard$2.run(NewTSElementWizard.java:154)
>> at
>> org.eclipse.jdt.internal.core.BatchOperation.executeOperation(BatchOperation.java:39)
>> at
>> org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaModelOperation.java:728)
>> at
>> org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1975)
>> at org.eclipse.jdt.core.JavaCore.run(JavaCore.java:4777)
>> at
>> org.eclipse.jdt.internal.ui.actions.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:106)
>> at
>> org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
>> Caused by: java.lang.ClassCastException: $Proxy12 cannot be cast to
>> org.eclipse.tigerstripe.workbench.internal.core.model.AbstractArtifact
>> at
>> org.eclipse.tigerstripe.generators.xml.helpers.ModelHelpers.getPackagesFromArtifacts(ModelHelpers.java:235)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
>> at java.lang.reflect.Method.invoke(Unknown Source)
>> at
>> org.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:295)
>> at
>> org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:245)
>> ... 23 more
>>
>>
>> To reproduce
>> 1. In Eclipse select New>tigerstripe Project and create a new project
>> 2. in tigerstripe.xml enable Soap Generator
>> 3. generate model in work space
>>
>> If there is an entity in the model, this problem disappears.
>> It looks like having no artifacts in an empty model causes the soap
>> generator to fail. You may want to check that the dependencyAnalyser
>> can cope with empty models as this will be the default state for new
>> projects created by the project creator.
>>
>> Cheers
>> 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: Flauw, M. <Mar...@hp...> - 2012-08-20 12:05:07
|
Craig,
You are correct, the implementation is not correct.
The association class is mainly a way to add some attributes to an association, so handling it as a true entity is not the best choice in my view.
Today for associations, we create an attribute in the source class with EntityIdentifier datatype.
The PerformanceIndicatorSpecRelationship is a bit special as it associates a class with itself.
Now, if we assume an association class C between A and B, with 2 attributes c1 and c2.
In theory we would need 2 datatypes:
C_AEND and C_ZEND
C_AEND would contain a pointer to A (entity identifier) and c1 and c2
C_ZEND would contain a pointer to B (entity identifier) and c1 and c2
If the association is navigable in both directions, then A would contain an attribute of type C_ZEND and B would contain an attribute of type C_AEND
If there is only 1 direction for navigability (like A-> B), then A would contain an attribute of type C_ZEND and the datatype C_AEND won't be needed.
Question: given that in both cases the pointer will be an entity identifier, would it be possible to simplify and only create C containing an entity identifier + c1 +c2 and use C for the attributes present in A and/or B. This would make things simpler.
Best regards
Marc
-----Original Message-----
From: Craig Gallen [mailto:gal...@go...] On Behalf Of Craig Gallen (opennms)
Sent: Wednesday, August 15, 2012 9:09 PM
To: openoss-devel; Flauw, Marc; Xose Ramon Sousa Vazquez; Craig Gallen (OpenNMS); Pierre Gauthier
Subject: Question About Association Classes in PM Dependency model
Hi,
In the PM dependencies model we have to return to the problem of how do we deal with association classes. It appears that we never satisfactory resolved this issue in the past because we didn't need association classes in our models. It is now returning to haunt us. I have looked carefully at the generated XSD's and it is clear that the present solution in the Soap generator does not work in a useful way. In the JVT generated code I have an alternative solution but it does not match the SOAP generator (see attached Java classes).
The PM Dependency model contains one association class called the PerformanceIndicatorSpecRelationship.
This has one attribute; String relationshipType. This generates the following XSD which has no reference to either end of the relationship.
<xsd:element name="performanceIndicatorSpecRelationship"
type="tns:PerformanceIndicatorSpecRelationship"/>
<xsd:complexType name="PerformanceIndicatorSpecRelationship">
<xsd:annotation>
<xsd:documentation>
<p>An association between two PerformanceIndicatorSpecifications, such as one indicator derived from another.</p>
<p>This association class is optional</p>
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="relationshipType" type="xsd:string"
minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>
<p>A categorization of the relationship, such as derived from, composite/atomic, and so forth.</p>
<p>This element is generated from an attribute.</p>
<p>This attribute is optional</p>
<p>This attribute is AVC enabled</p>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
Similarly the generated PerformanceIndicatorSpecification entities which
are linked by this association class do not reference the association
class. In fact, it appears that the the association class between PerformanceIndicatorSpecification entities is not generated at all.
<xsd:complexType name="PerformanceIndicatorSpecification">
<xsd:annotation>
<xsd:documentation>
<p>A measure of a specific aspect of the performance of an entity, such as a lost packets or average jitter, defined for a PeformanceSpecification that may trigger the creation of a PerformanceConsequence.</p>
<p>This entity is optional</p>
<p>This entity is extendable</p>
<p>This entity does not generate Object Creation
notifications (NA)</p>
<p>This entity does not generate Object Deletion
notifications (NA)</p>
<p>This entity does not generate Object Discovery
notifications (NA)</p>
<p>This entity generates Attribute Value Change notifications.</p>
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="entity:EntityBase">
<xsd:sequence>
<xsd:element name="name" type="xsd:string" minOccurs="1"
maxOccurs="1">
<xsd:annotation>
<xsd:documentation>
<p>A word, term, or phrase by which a PerformanceIndicatorSpecification is known and distinguished from other PerformanceIndicatorSpecifications.</p>
<p>This element is generated from an attribute.</p>
<p>This attribute is mandatory</p>
<p>This attribute is AVC enabled</p>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="description" type="xsd:string"
minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>
<p>A narrative that explains in detail what the PerformanceIndicatorSpecification is.</p>
<p>This element is generated from an attribute.</p>
<p>This attribute is optional</p>
<p>This attribute is AVC enabled</p>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="perspective" type="xsd:string"
minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>
<p>The point of view for the PerformanceIndicatorSpecification, such as a single user instance or an aggregation.</p>
<p>This element is generated from an attribute.</p>
<p>This attribute is optional</p>
<p>This attribute is AVC enabled</p>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="indicatorCategory" type="xsd:string"
minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>
<p>A grouping or set of PerformanceIndicatorSpecifications that are classified together because of common characteristics, such as technology specific, service specific, or technology/service independent.</p>
<p>This element is generated from an attribute.</p>
<p>This attribute is optional</p>
<p>This attribute is AVC enabled</p>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="indicatorType"
type="perf:IndicatorType" minOccurs="1" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>
<p>A kind of value that the PerformanceIndicator can take on, such as numeric, text, and so forth.</p>
<p>This element is generated from an attribute.</p>
<p>This attribute is mandatory</p>
<p>This attribute is AVC enabled</p>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="derivationAlgorithm"
type="xsd:string" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>
<p>A step-by-step procedure used to calculate the value of the PerformanceIndicator.</p>
<p>This element is generated from an attribute.</p>
<p>This attribute is optional</p>
<p>This attribute is AVC enabled</p>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="derivationMethod" type="xsd:string"
minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>
<p>For simple calculations, the method used to calculate the value of a PerformanceIndicator, such as average, minimum, maximum, sum, and so forth.</p>
<p>This element is generated from an attribute.</p>
<p>This attribute is optional</p>
<p>This attribute is AVC enabled</p>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="collectionType"
type="perf:CollectionType" minOccurs="1" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>
<p>The type of the collection such as: gauge, commulative, status inspection. Indicators can be produced using these methods.</p>
<p>This element is generated from an attribute.</p>
<p>This attribute is mandatory</p>
<p>This attribute is AVC enabled</p>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="indicatorUnit" type="xsd:string"
minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>
<p>The unit by which the indicator is measured.
For example: seconds, KBs, rate per second, etc.</p>
<p>This element is generated from an attribute.</p>
<p>This attribute is optional</p>
<p>This attribute is AVC enabled</p>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="ArrayOfPerformanceIndicatorSpecification">
<xsd:sequence>
<xsd:element name="item"
type="tns:PerformanceIndicatorSpecification" minOccurs="0"
maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
In short, we are generating an XSD for an assocation class in the model which is not referenced by any entity and which cannot be retrieved across the interface which seems fairly useless.
So my question is;
What is the PerformanceIndicatorSpecRelationship for?
Should association classes actually be treated as Entities so that they can be referenced through entity identifiers and be used for indirection between A and Z end's ( that way when an association changes, it makes sense to send an association value change event) .
Or or should they be treated a data types which are embedded in entities and contain the entity identifier of the other end artefact. Whatever the answer is, we aren't doing anything useful at the moment.
Please see the generated Java implementation attached for some ideas.
This is a blocking issue for completing the RI/CTK code for PM
Craig
|
|
From: SB M. <sbm...@tm...> - 2012-08-20 08:52:26
|
+ Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] TIP_RAM_BaseProject
[INFO] TIP_RAM_Dependencies
[INFO] TIP_RAM_Model
[INFO] TIP_RAM_SoapSpecPackage
[INFO] TIP_RAM_DocSpecPackage
[INFO] TIP_RAM_Model_Package
[INFO] TIP_RAM_Spec_Release_Package
[INFO] TIP_RAM_JvtSpecPackage
[INFO] TIP_RAM_EjbImplGenSrcPackage
[INFO] TIP_RAM_SoapImplGenSrcPackage
[INFO] TIP_RAM_EjbImplProject
[INFO] TIP_RAM_WSImplProject
[INFO] TIP_RAM_CTKProject
[INFO] ------------------------------------------------------------------------
[INFO] Building TIP_RAM_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-ts\TIP_RAM_BaseProject\pom.xml to C:\Users\SB\.m2\repository\org\openoss\tip\TIP_RAM_BaseProject\1.0.2-SNAPSHOT\TIP_RAM_BaseProject-1.0.2-SNAPSHOT.pom
[INFO] ------------------------------------------------------------------------
[INFO] Building TIP_RAM_Dependencies
[INFO] task-segment: [clean, install]
[INFO] ------------------------------------------------------------------------
[INFO] [clean:clean {execution: default-clean}]
[INFO] Deleting directory C:\ws-ts\TIP_RAM_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\SB\.m2\repository\org\tmforum\tip\TIP_Doc_Generator_Package\1.1.2-SNAPSHOT\TIP_Doc_Generator_Package-1.1.2-SNAPSHOT.jarto
C:\ws-ts\TIP_RAM_Dependencies\TigerstripeGenerators
with Includes null and excludes:null
[INFO] Unpacking C:\Users\SB\.m2\repository\org\tmforum\tip\TIP_Soap_Generator_Package\1.1.2-SNAPSHOT\TIP_Soap_Generator_Package-1.1.2-SNAPSHOT.jarto
C:\ws-ts\TIP_RAM_Dependencies\TigerstripeGenerators
with Includes null and excludes:null
[INFO] Unpacking C:\Users\SB\.m2\repository\org\tmforum\tip\TIP_Profile_Package\1.1.2-SNAPSHOT\TIP_Profile_Package-1.1.2-SNAPSHOT.jarto
C:\ws-ts\TIP_RAM_Dependencies\TigerstripeGenerators
with Includes null and excludes:null
[INFO] Unpacking C:\Users\SB\.m2\repository\org\tmforum\tip\TIP_JvtSpec_Generator_Package\1.1.2-SNAPSHOT\TIP_JvtSpec_Generator_Package-1.1.2-SNAPSHOT.jarto
C:\ws-ts\TIP_RAM_Dependencies\TigerstripeGenerators
with Includes null and excludes:null
[INFO] Unpacking C:\Users\SB\.m2\repository\org\openoss\tip\TIP_EjbImpl_Generator_Package\1.1.2-SNAPSHOT\TIP_EjbImpl_Generator_Package-1.1.2-SNAPSHOT.jarto
C:\ws-ts\TIP_RAM_Dependencies\TigerstripeGenerators
with Includes null and excludes:null
[INFO] Unpacking C:\Users\SB\.m2\repository\org\tmforum\tip\TIP_Common_Model_Package\1.1.2-SNAPSHOT\TIP_Common_Model_Package-1.1.2-SNAPSHOT.jarto
C:\ws-ts\TIP_RAM_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-ts\TIP_RAM_Dependencies\libs\maven-ant-tasks-2.0.10.jar
[INFO] [antrun:run {execution: run-tigerstripe}]
[INFO] Executing tasks
[echo] MODEL_POM: eclipse_home: C:\eclipsets
[echo] MODEL_POM: model_project_basedir: C:\ws-ts\TIP_RAM_Dependencies
[echo] MODEL_POM: model_project__directory_name: TIP_RAM_Dependencies
[echo] MODEL_POM: tigerstripe_workspace: C:\ws-ts
[echo] MODEL_POM: referenced_project1: TIP_RAM_Dependencies
[echo] MODEL_POM: tigerstripe_generation_project: TIP_RAM_Dependencies
[echo] MODEL_POM: tigerstripe_arg_string: -nosplash -data C:\ws-ts -application org.eclipse.tigerstripe.workbench.headless.tigerstripe C:\ws-ts\TIP_RAM_Dependencies GENERATION_PROJECT=C:\ws-ts\TIP_RAM_Dependencies
[echo] MODEL_POM: C:\ws-ts\TIP_RAM_Dependencies\target\CODE_GENERATED_FLAG.txt does not exist. Will run Tigerstripe
[exec] Tigerstripe Workbench Base Plug-in (Incubation) (v0.7.0.201206291233)
[exec] Active Profile: TIP_Profile 1.1.2
[exec] file:/C:/eclipsets/tigerstripe/plugins/.TIP_Soap_Generator-1.1_temp/classes/
[exec] file:/C:/eclipsets/tigerstripe/plugins/.TIP_Soap_Generator-1.1_temp/commons-lang-2.4_simplified.jar
[exec] file:/C:/eclipsets/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/classes/
[exec] file:/C:/eclipsets/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/avalon-framework-4.2.0.jar
[exec] file:/C:/eclipsets/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/batik-bridge.jar
[exec] file:/C:/eclipsets/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/batik-css.jar
[exec] file:/C:/eclipsets/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/batik-dom.jar
[exec] file:/C:/eclipsets/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/batik-ext.jar
[exec] file:/C:/eclipsets/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/batik-gui-util.jar
[exec] file:/C:/eclipsets/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/batik-gvt.jar
[exec] file:/C:/eclipsets/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/batik-svg-dom.jar
[exec] file:/C:/eclipsets/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/batik-svggen.jar
[exec] file:/C:/eclipsets/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/batik-util.jar
[exec] file:/C:/eclipsets/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/batik-xml.jar
[exec] file:/C:/eclipsets/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/commons-io-1.3.1.jar
[exec] file:/C:/eclipsets/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/commons-lang-2.4_simplified.jar
[exec] file:/C:/eclipsets/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/commons-logging-1.0.4.jar
[exec] file:/C:/eclipsets/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/fop.jar
[exec] file:/C:/eclipsets/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/iText-5.0.1.jar
[exec] file:/C:/eclipsets/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/serializer-2.7.1.jar
[exec] file:/C:/eclipsets/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/xalan-2.7.1.jar
[exec] file:/C:/eclipsets/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/xml-apis-ext.jar
[exec] file:/C:/eclipsets/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/xmlgraphics-commons-1.3.1.jar
[exec] ERROR [main] (FixedLength.java:148) - Unknown length unit 'ptcm'
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 122/225)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 122/521)
[exec] file:/C:/eclipsets/tigerstripe/plugins/.TIP_JvtSpec_Generator-1.1_temp/classes/
[exec] file:/C:/eclipsets/tigerstripe/plugins/.TIP_EjbImpl_Generator-1.1_temp/classes/
[exec] file:/C:/eclipsets/tigerstripe/plugins/.TIP_SoapImpl_Generator-1.1_temp/classes/
[exec] [TIP_Soap_Generator(1.1)Project: org.tmforum.tip.ram.dep version=1.0, Plugin: TIP_Soap_Generator(1.1) version=1.1]
[exec] Error: Unexpected error while merging 'templates/dependencyAnalyzer.vm' template: Invocation of method 'choose' in class org.eclipse.tigerstripe.generators.xml.filters.DependencyAnalyzer threw exception java.lang.IncompatibleClassChangeError: Found interface org.eclipse.tigerstripe.workbench.internal.core.model.ArtifactManager, but class was expected @ templates/dependencyAnalyzer.vm[7,58]. Generation may be incomplete.
[exec] org.eclipse.tigerstripe.workbench.TigerstripeException: Unexpected error while merging 'templates/dependencyAnalyzer.vm' template: Invocation of method 'choose' in class org.eclipse.tigerstripe.generators.xml.filters.DependencyAnalyzer threw exception java.lang.IncompatibleClassChangeError: Found interface org.eclipse.tigerstripe.workbench.internal.core.model.ArtifactManager, but class was expected @ templates/dependencyAnalyzer.vm[7,58]
[exec] at org.eclipse.tigerstripe.workbench.internal.core.project.pluggable.rules.GlobalTemplateRule.trigger(GlobalTemplateRule.java:183)
[exec] at org.eclipse.tigerstripe.workbench.internal.core.plugin.pluggable.PluginRuleExecutor.trigger(PluginRuleExecutor.java:80)
[exec] at org.eclipse.tigerstripe.workbench.internal.core.plugin.pluggable.PluggablePlugin.trigger(PluggablePlugin.java:158)
[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:259)
[exec] at org.eclipse.tigerstripe.workbench.internal.core.generation.M1Generator.internalPluginLoop(M1Generator.java:671)
[exec] at org.eclipse.tigerstripe.workbench.internal.core.generation.M1Generator.internalRun(M1Generator.java:613)
[exec] at org.eclipse.tigerstripe.workbench.internal.core.generation.M1Generator.run(M1Generator.java:349)
[exec] at org.eclipse.tigerstripe.workbench.internal.core.generation.M1Generator.run(M1Generator.java:89)
[exec] at org.eclipse.tigerstripe.workbench.internal.api.impl.TigerstripeProjectHandle.generate(TigerstripeProjectHandle.java:512)
[exec] at org.eclipse.tigerstripe.workbench.headless.Tigerstripe.generateTigerstripeOutput(Tigerstripe.java:197)
[exec] at org.eclipse.tigerstripe.workbench.headless.Tigerstripe.start(Tigerstripe.java:80)
[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] org.apache.velocity.exception.MethodInvocationException: Invocation of method 'choose' in class org.eclipse.tigerstripe.generators.xml.filters.DependencyAnalyzer threw exception java.lang.IncompatibleClassChangeError: Found interface org.eclipse.tigerstripe.workbench.internal.core.model.ArtifactManager, but class was expected @ templates/dependencyAnalyzer.vm[7,58]
[exec] at org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:300)
[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.ASTMethod.execute(ASTMethod.java:147)
[exec] at org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:203)
[exec] at org.apache.velocity.runtime.parser.node.ASTReference.render(ASTReference.java:294)
[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:162)
[exec] at org.eclipse.tigerstripe.workbench.internal.core.plugin.pluggable.PluginRuleExecutor.trigger(PluginRuleExecutor.java:80)
[exec] at org.eclipse.tigerstripe.workbench.internal.core.plugin.pluggable.PluggablePlugin.trigger(PluggablePlugin.java:158)
[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:259)
[exec] at org.eclipse.tigerstripe.workbench.internal.core.generation.M1Generator.internalPluginLoop(M1Generator.java:671)
[exec] at org.eclipse.tigerstripe.workbench.internal.core.generation.M1Generator.internalRun(M1Generator.java:613)
[exec] at org.eclipse.tigerstripe.workbench.internal.core.generation.M1Generator.run(M1Generator.java:349)
[exec] at org.eclipse.tigerstripe.workbench.internal.core.generation.M1Generator.run(M1Generator.java:89)
[exec] at org.eclipse.tigerstripe.workbench.internal.api.impl.TigerstripeProjectHandle.generate(TigerstripeProjectHandle.java:512)
[exec] at org.eclipse.tigerstripe.workbench.headless.Tigerstripe.generateTigerstripeOutput(Tigerstripe.java:197)
[exec] at org.eclipse.tigerstripe.workbench.headless.Tigerstripe.start(Tigerstripe.java:80)
[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: java.lang.IncompatibleClassChangeError: Found interface org.eclipse.tigerstripe.workbench.internal.core.model.ArtifactManager, but class was expected
[exec] at org.eclipse.tigerstripe.generators.models.PackageModel.getDirectlyOwnedIAbstractArtifacts(PackageModel.java:131)
[exec] at org.eclipse.tigerstripe.generators.xml.helpers.ModelHelpers.isContainingIAbstractArtifact(ModelHelpers.java:191)
[exec] at org.eclipse.tigerstripe.generators.xml.helpers.ModelHelpers.isContainingIAbstractArtifact(ModelHelpers.java:230)
[exec] at org.eclipse.tigerstripe.generators.xml.filters.DependencyAnalyzer.choose(DependencyAnalyzer.java:107)
[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.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:295)
[exec] at org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:245)
[exec] ... 31 more
[exec]
[exec]
[exec] [TIP_Doc_Generator(1.1)Project: org.tmforum.tip.ram.dep version=1.0, Plugin: TIP_Doc_Generator(1.1) version=1.1]
[exec] Generation Successful.
[exec]
[exec] [TIP_JvtSpec_Generator(1.1)Project: org.tmforum.tip.ram.dep version=1.0, 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] [TIP_EjbImpl_Generator(1.1)Project: org.tmforum.tip.ram.dep version=1.0, 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] [TIP_SoapImpl_Generator(1.1)Project: org.tmforum.tip.ram.dep version=1.0, Plugin: TIP_SoapImpl_Generator(1.1) version=1.1]
[exec] Notice: None of the artifact(s) match the specified rule(s) 'javaBasicEventJaxbRule'.
[exec] Notice: None of the artifact(s) match the specified rule(s) 'javaBasicExceptionJaxbRule'.
[exec] Notice: None of the artifact(s) match the specified rule(s) 'javaBasicFacadeWsdlJaxbRule'.
[exec] Notice: None of the artifact(s) match the specified rule(s) 'javaBasicAssociationClassJaxbRule'.
[exec] Notice: None of the artifact(s) match the specified rule(s) 'javaBasicClientFacadeWsdlJaxbRule'.
[exec] Notice: None of the artifact(s) match the specified rule(s) 'javaBasicFacadeJaxbTestRule'.
[exec] Generation Successful.
[exec]
[exec] Generation is failed.
[exec] org.eclipse.tigerstripe.workbench.TigerstripeException: Generation is failed.
[exec] at org.eclipse.tigerstripe.workbench.headless.Tigerstripe.generateTigerstripeOutput(Tigerstripe.java:208)
[exec] at org.eclipse.tigerstripe.workbench.headless.Tigerstripe.start(Tigerstripe.java:80)
[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)
[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-ts\TIP_RAM_Dependencies\target\tigerstripe.gen
[echo] MODEL_POM: C:\ws-ts\TIP_RAM_Dependencies\target\CODE_GENERATED_FLAG.txt does not exist. Will install transient dependencies
[echo] MODEL_POM: directory of code generated by plugin: C:\ws-ts\TIP_RAM_Dependencies\target\tigerstripe.gen\TIP_RAM_Dependencies_DocSpecPackageTransientDependency
[echo] MODEL_POM: name of jar containing code generated by plugin: TIP_RAM_Dependencies_DocSpecPackageTransientDependency.jar
[jar] Building jar: C:\ws-ts\TIP_RAM_Dependencies\target\tigerstripe.gen\TIP_RAM_Dependencies_DocSpecPackageTransientDependency.jar
[echo] MODEL_POM: name of pom expected from plugin: TIP_RAM_Dependencies_DocSpecPackageTransientDependencyPom.xml
bootstrap.maven.tasks:
run-if-pom-exists:
[echo] POM-BUILD: Processing generated project: C:\ws-ts\TIP_RAM_Dependencies\target\tigerstripe.gen\TIP_RAM_Dependencies_DocSpecPackageTransientDependency.jar
[echo] POM-BUILD: Generated project Pom file exists: C:\ws-ts\TIP_RAM_Dependencies\target\tigerstripe.gen\TIP_RAM_Dependencies_DocSpecPackageTransientDependencyPom.xml. Installing jar in local .m2 repository
[INFO] Installing C:\ws-ts\TIP_RAM_Dependencies\target\tigerstripe.gen\TIP_RAM_Dependencies_DocSpecPackageTransientDependency.jar to C:\Users\SB\.m2\repository\org\tmforum\tip\TIP_RAM_Dependencies_DocSpecPackageTransientDependency\1.0.2-SNAPSHOT\TIP_RAM_Dependencies_DocSpecPackageTransientDependency-1.0.2-SNAPSHOT.jar
run-if-pom-missing:
install-jar:
[echo] MODEL_POM: directory of code generated by plugin: C:\ws-ts\TIP_RAM_Dependencies\target\tigerstripe.gen\TIP_RAM_Dependencies_EjbImplGenSrcPackageTransientDependency
[echo] MODEL_POM: name of jar containing code generated by plugin: TIP_RAM_Dependencies_EjbImplGenSrcPackageTransientDependency.jar
[jar] Building jar: C:\ws-ts\TIP_RAM_Dependencies\target\tigerstripe.gen\TIP_RAM_Dependencies_EjbImplGenSrcPackageTransientDependency.jar
[echo] MODEL_POM: name of pom expected from plugin: TIP_RAM_Dependencies_EjbImplGenSrcPackageTransientDependencyPom.xml
bootstrap.maven.tasks:
run-if-pom-exists:
[echo] POM-BUILD: Processing generated project: C:\ws-ts\TIP_RAM_Dependencies\target\tigerstripe.gen\TIP_RAM_Dependencies_EjbImplGenSrcPackageTransientDependency.jar
[echo] POM-BUILD: Generated project Pom file exists: C:\ws-ts\TIP_RAM_Dependencies\target\tigerstripe.gen\TIP_RAM_Dependencies_EjbImplGenSrcPackageTransientDependencyPom.xml. Installing jar in local .m2 repository
[INFO] Installing C:\ws-ts\TIP_RAM_Dependencies\target\tigerstripe.gen\TIP_RAM_Dependencies_EjbImplGenSrcPackageTransientDependency.jar to C:\Users\SB\.m2\repository\org\openoss\tip\TIP_RAM_Dependencies_EjbImplGenSrcPackageTransientDependency\1.0.2-SNAPSHOT\TIP_RAM_Dependencies_EjbImplGenSrcPackageTransientDependency-1.0.2-SNAPSHOT.jar
run-if-pom-missing:
install-jar:
[echo] MODEL_POM: directory of code generated by plugin: C:\ws-ts\TIP_RAM_Dependencies\target\tigerstripe.gen\TIP_RAM_Dependencies_JvtSpecPackageTransientDependency
[echo] MODEL_POM: name of jar containing code generated by plugin: TIP_RAM_Dependencies_JvtSpecPackageTransientDependency.jar
[jar] Building jar: C:\ws-ts\TIP_RAM_Dependencies\target\tigerstripe.gen\TIP_RAM_Dependencies_JvtSpecPackageTransientDependency.jar
[echo] MODEL_POM: name of pom expected from plugin: TIP_RAM_Dependencies_JvtSpecPackageTransientDependencyPom.xml
bootstrap.maven.tasks:
run-if-pom-exists:
[echo] POM-BUILD: Processing generated project: C:\ws-ts\TIP_RAM_Dependencies\target\tigerstripe.gen\TIP_RAM_Dependencies_JvtSpecPackageTransientDependency.jar
[echo] POM-BUILD: Generated project Pom file exists: C:\ws-ts\TIP_RAM_Dependencies\target\tigerstripe.gen\TIP_RAM_Dependencies_JvtSpecPackageTransientDependencyPom.xml. Installing jar in local .m2 repository
[INFO] Installing C:\ws-ts\TIP_RAM_Dependencies\target\tigerstripe.gen\TIP_RAM_Dependencies_JvtSpecPackageTransientDependency.jar to C:\Users\SB\.m2\repository\org\tmforum\tip\TIP_RAM_Dependencies_JvtSpecPackageTransientDependency\1.0.2-SNAPSHOT\TIP_RAM_Dependencies_JvtSpecPackageTransientDependency-1.0.2-SNAPSHOT.jar
run-if-pom-missing:
install-jar:
[echo] MODEL_POM: directory of code generated by plugin: C:\ws-ts\TIP_RAM_Dependencies\target\tigerstripe.gen\TIP_RAM_Dependencies_SoapImplGenSrcPackageTransientDependency
[echo] MODEL_POM: name of jar containing code generated by plugin: TIP_RAM_Dependencies_SoapImplGenSrcPackageTransientDependency.jar
[jar] Building jar: C:\ws-ts\TIP_RAM_Dependencies\target\tigerstripe.gen\TIP_RAM_Dependencies_SoapImplGenSrcPackageTransientDependency.jar
[echo] MODEL_POM: name of pom expected from plugin: TIP_RAM_Dependencies_SoapImplGenSrcPackageTransientDependencyPom.xml
bootstrap.maven.tasks:
run-if-pom-exists:
[echo] POM-BUILD: Processing generated project: C:\ws-ts\TIP_RAM_Dependencies\target\tigerstripe.gen\TIP_RAM_Dependencies_SoapImplGenSrcPackageTransientDependency.jar
[echo] POM-BUILD: Generated project Pom file exists: C:\ws-ts\TIP_RAM_Dependencies\target\tigerstripe.gen\TIP_RAM_Dependencies_SoapImplGenSrcPackageTransientDependencyPom.xml. Installing jar in local .m2 repository
[INFO] Installing C:\ws-ts\TIP_RAM_Dependencies\target\tigerstripe.gen\TIP_RAM_Dependencies_SoapImplGenSrcPackageTransientDependency.jar to C:\Users\SB\.m2\repository\org\openoss\tip\TIP_RAM_Dependencies_SoapImplGenSrcPackageTransientDependency\1.0.2-SNAPSHOT\TIP_RAM_Dependencies_SoapImplGenSrcPackageTransientDependency-1.0.2-SNAPSHOT.jar
run-if-pom-missing:
install-jar:
[echo] MODEL_POM: directory of code generated by plugin: C:\ws-ts\TIP_RAM_Dependencies\target\tigerstripe.gen\TIP_RAM_Dependencies_SoapSpecPackageTransientDependency
[echo] MODEL_POM: name of jar containing code generated by plugin: TIP_RAM_Dependencies_SoapSpecPackageTransientDependency.jar
[jar] Building jar: C:\ws-ts\TIP_RAM_Dependencies\target\tigerstripe.gen\TIP_RAM_Dependencies_SoapSpecPackageTransientDependency.jar
[echo] MODEL_POM: name of pom expected from plugin: TIP_RAM_Dependencies_SoapSpecPackageTransientDependencyPom.xml
bootstrap.maven.tasks:
run-if-pom-exists:
[echo] POM-BUILD: Processing generated project: C:\ws-ts\TIP_RAM_Dependencies\target\tigerstripe.gen\TIP_RAM_Dependencies_SoapSpecPackageTransientDependency.jar
[echo] POM-BUILD: Generated project Pom file exists: C:\ws-ts\TIP_RAM_Dependencies\target\tigerstripe.gen\TIP_RAM_Dependencies_SoapSpecPackageTransientDependencyPom.xml. Installing jar in local .m2 repository
[INFO] Installing C:\ws-ts\TIP_RAM_Dependencies\target\tigerstripe.gen\TIP_RAM_Dependencies_SoapSpecPackageTransientDependency.jar to C:\Users\SB\.m2\repository\org\tmforum\tip\TIP_RAM_Dependencies_SoapSpecPackageTransientDependency\1.0.2-SNAPSHOT\TIP_RAM_Dependencies_SoapSpecPackageTransientDependency-1.0.2-SNAPSHOT.jar
run-if-pom-missing:
install-jar:
[echo] MODEL_POM: directory of code generated by plugin: C:\ws-ts\TIP_RAM_Dependencies\target\tigerstripe.gen\logs
[echo] MODEL_POM: name of jar containing code generated by plugin: logs.jar
[jar] Building jar: C:\ws-ts\TIP_RAM_Dependencies\target\tigerstripe.gen\logs.jar
[echo] MODEL_POM: name of pom expected from plugin: logsPom.xml
bootstrap.maven.tasks:
run-if-pom-exists:
run-if-pom-missing:
[echo] POM-BUILD: Processing generated project: C:\ws-ts\TIP_RAM_Dependencies\target\tigerstripe.gen\logs.jar
[echo] POM-BUILD: Generated project Pom file does not exist: C:\ws-ts\TIP_RAM_Dependencies\target\tigerstripe.gen\logsPom.xml. Not Installing jar
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-ts\TIP_RAM_Dependencies\pom.xml to C:\Users\SB\.m2\repository\org\tmforum\tip\TIP_RAM_Dependencies\1.0.2-SNAPSHOT\TIP_RAM_Dependencies-1.0.2-SNAPSHOT.pom
[INFO] ------------------------------------------------------------------------
[INFO] Building TIP_RAM_Model
[INFO] task-segment: [clean, install]
[INFO] ------------------------------------------------------------------------
[INFO] [clean:clean {execution: default-clean}]
[INFO] Deleting directory C:\ws-ts\TIP_RAM_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\SB\.m2\repository\org\tmforum\tip\TIP_Doc_Generator_Package\1.1.2-SNAPSHOT\TIP_Doc_Generator_Package-1.1.2-SNAPSHOT.jarto
C:\ws-ts\TIP_RAM_Model\TigerstripeGenerators
with Includes null and excludes:null
[INFO] Unpacking C:\Users\SB\.m2\repository\org\tmforum\tip\TIP_Soap_Generator_Package\1.1.2-SNAPSHOT\TIP_Soap_Generator_Package-1.1.2-SNAPSHOT.jarto
C:\ws-ts\TIP_RAM_Model\TigerstripeGenerators
with Includes null and excludes:null
[INFO] Unpacking C:\Users\SB\.m2\repository\org\tmforum\tip\TIP_Profile_Package\1.1.2-SNAPSHOT\TIP_Profile_Package-1.1.2-SNAPSHOT.jarto
C:\ws-ts\TIP_RAM_Model\TigerstripeGenerators
with Includes null and excludes:null
[INFO] Unpacking C:\Users\SB\.m2\repository\org\tmforum\tip\TIP_JvtSpec_Generator_Package\1.1.2-SNAPSHOT\TIP_JvtSpec_Generator_Package-1.1.2-SNAPSHOT.jarto
C:\ws-ts\TIP_RAM_Model\TigerstripeGenerators
with Includes null and excludes:null
[INFO] Unpacking C:\Users\SB\.m2\repository\org\openoss\tip\TIP_EjbImpl_Generator_Package\1.1.2-SNAPSHOT\TIP_EjbImpl_Generator_Package-1.1.2-SNAPSHOT.jarto
C:\ws-ts\TIP_RAM_Model\TigerstripeGenerators
with Includes null and excludes:null
[INFO] Unpacking C:\Users\SB\.m2\repository\org\tmforum\tip\TIP_Common_Model_Package\1.1.2-SNAPSHOT\TIP_Common_Model_Package-1.1.2-SNAPSHOT.jarto
C:\ws-ts\TIP_RAM_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-ts\TIP_RAM_Model\libs\maven-ant-tasks-2.0.10.jar
[INFO] [antrun:run {execution: run-tigerstripe}]
[INFO] Executing tasks
[echo] MODEL_POM: eclipse_home: C:\eclipsets
[echo] MODEL_POM: model_project_basedir: C:\ws-ts\TIP_RAM_Model
[echo] MODEL_POM: model_project__directory_name: TIP_RAM_Model
[echo] MODEL_POM: tigerstripe_workspace: C:\ws-ts
[echo] MODEL_POM: referenced_project1: TIP_RAM_Model
[echo] MODEL_POM: tigerstripe_generation_project: TIP_RAM_Model
[echo] MODEL_POM: tigerstripe_arg_string: -nosplash -data C:\ws-ts -application org.eclipse.tigerstripe.workbench.headless.tigerstripe C:\ws-ts\TIP_RAM_Model GENERATION_PROJECT=C:\ws-ts\TIP_RAM_Model
[echo] MODEL_POM: C:\ws-ts\TIP_RAM_Model\target\CODE_GENERATED_FLAG.txt does not exist. Will run Tigerstripe
[exec] Tigerstripe Workbench Base Plug-in (Incubation) (v0.7.0.201206291233)
[exec] Active Profile: TIP_Profile 1.1.2
[exec] file:/C:/eclipsets/tigerstripe/plugins/.TIP_Soap_Generator-1.1_temp/classes/
[exec] file:/C:/eclipsets/tigerstripe/plugins/.TIP_Soap_Generator-1.1_temp/commons-lang-2.4_simplified.jar
[exec] file:/C:/eclipsets/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/classes/
[exec] file:/C:/eclipsets/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/avalon-framework-4.2.0.jar
[exec] file:/C:/eclipsets/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/batik-bridge.jar
[exec] file:/C:/eclipsets/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/batik-css.jar
[exec] file:/C:/eclipsets/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/batik-dom.jar
[exec] file:/C:/eclipsets/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/batik-ext.jar
[exec] file:/C:/eclipsets/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/batik-gui-util.jar
[exec] file:/C:/eclipsets/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/batik-gvt.jar
[exec] file:/C:/eclipsets/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/batik-svg-dom.jar
[exec] file:/C:/eclipsets/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/batik-svggen.jar
[exec] file:/C:/eclipsets/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/batik-util.jar
[exec] file:/C:/eclipsets/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/batik-xml.jar
[exec] file:/C:/eclipsets/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/commons-io-1.3.1.jar
[exec] file:/C:/eclipsets/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/commons-lang-2.4_simplified.jar
[exec] file:/C:/eclipsets/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/commons-logging-1.0.4.jar
[exec] file:/C:/eclipsets/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/fop.jar
[exec] file:/C:/eclipsets/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/iText-5.0.1.jar
[exec] file:/C:/eclipsets/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/serializer-2.7.1.jar
[exec] file:/C:/eclipsets/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/xalan-2.7.1.jar
[exec] file:/C:/eclipsets/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/xml-apis-ext.jar
[exec] file:/C:/eclipsets/tigerstripe/plugins/.TIP_Doc_Generator-1.1_temp/xmlgraphics-commons-1.3.1.jar
[exec] ERROR [main] (FixedLength.java:148) - Unknown length unit 'ptcm'
[exec] ERROR [main] (FixedLength.java:148) - Unknown length unit 'ptcm'
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 144/225)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 144/569)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 144/932)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 144/1302)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 152/225)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 152/579)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 152/940)
[exec] ERROR [main] (FixedLength.java:148) - Unknown length unit 'ptcm'
[exec] ERROR [main] (FixedLength.java:148) - Unknown length unit 'ptcm'
[exec] ERROR [main] (FixedLength.java:148) - Unknown length unit 'ptcm'
[exec] ERROR [main] (FixedLength.java:148) - Unknown length unit 'ptcm'
[exec] ERROR [main] (FixedLength.java:148) - Unknown length unit 'ptcm'
[exec] ERROR [main] (FixedLength.java:148) - Unknown length unit 'ptcm'
[exec] ERROR [main] (FixedLength.java:148) - Unknown length unit 'ptcm'
[exec] ERROR [main] (FixedLength.java:148) - Unknown length unit 'ptcm'
[exec] ERROR [main] (FixedLength.java:148) - Unknown length unit 'ptcm'
[exec] ERROR [main] (FixedLength.java:148) - Unknown length unit 'ptcm'
[exec] ERROR [main] (FixedLength.java:148) - Unknown length unit 'ptcm'
[exec] ERROR [main] (FixedLength.java:148) - Unknown length unit 'ptcm'
[exec] ERROR [main] (FixedLength.java:148) - Unknown length unit 'ptcm'
[exec] ERROR [main] (FixedLength.java:148) - Unknown length unit 'ptcm'
[exec] ERROR [main] (FixedLength.java:148) - Unknown length unit 'ptcm'
[exec] ERROR [main] (FixedLength.java:148) - Unknown length unit 'ptcm'
[exec] ERROR [main] (FixedLength.java:148) - Unknown length unit 'ptcm'
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 152/225)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 154/190)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 155/208)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 157/189)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 158/191)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 161/172)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 164/191)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 180/225)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 184/225)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 185/180)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 227/225)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 227/624)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 227/1090)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 227/1528)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 230/225)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 230/560)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 230/882)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 230/1212)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 230/1540)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 231/203)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 246/225)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 246/583)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 247/168)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 248/149)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 249/167)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 250/169)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 251/187)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 263/225)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 263/540)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 263/863)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 263/1182)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 263/1503)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 263/1827)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 263/2154)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 280/225)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 280/592)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 281/161)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 282/161)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 282/591)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 282/994)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 282/1365)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 282/1723)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 305/225)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 305/561)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 305/889)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 319/225)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 319/538)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 319/853)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 319/1176)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 319/1495)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 319/1816)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 319/2140)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 319/2467)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 319/2788)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 319/3110)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 319/3443)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 319/3769)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 325/225)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 327/156)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 327/485)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 327/813)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 333/225)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 352/225)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 352/540)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 352/859)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 352/1181)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 355/225)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 355/550)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 355/879)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 355/1207)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 355/1538)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 355/1872)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 355/2212)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 370/225)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 370/540)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 370/859)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 370/1181)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 370/1515)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 370/1838)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 370/2159)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 370/2485)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 370/2805)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 370/3125)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 370/3443)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 374/225)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 374/550)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 374/879)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 374/1208)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 374/1539)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 374/1873)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 374/2213)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 27mpt. (fo:block, location: 386/225)
[exec] WARN [main] (LineLayoutManager.java:388) - Line 1 of a paragraph overflows the available area by 12000mpt. (fo:block, location: 401/30)
[exec] file:/C:/eclipsets/tigerstripe/plugins/.TIP_JvtSpec_Generator-1.1_temp/classes/
[exec] file:/C:/eclipsets/tigerstripe/plugins/.TIP_EjbImpl_Generator-1.1_temp/classes/
[exec] file:/C:/eclipsets/tigerstripe/plugins/.TIP_SoapImpl_Generator-1.1_temp/classes/
[exec] [TIP_Soap_Generator(1.1)Project: org.tmforum.tip.ram version=1.0, Plugin: TIP_Soap_Generator(1.1) version=1.1]
[exec] Error: Unexpected error while merging 'templates/dependencyAnalyzer.vm' template: Invocation of method 'choose' in class org.eclipse.tigerstripe.generators.xml.filters.DependencyAnalyzer threw exception java.lang.IncompatibleClassChangeError: Found interface org.eclipse.tigerstripe.workbench.internal.core.model.ArtifactManager, but class was expected @ templates/dependencyAnalyzer.vm[7,58]. Generation may be incomplete.
[exec] org.eclipse.tigerstripe.workbench.TigerstripeException: Unexpected error while merging 'templates/dependencyAnalyzer.vm' template: Invocation of method 'choose' in class org.eclipse.tigerstripe.generators.xml.filters.DependencyAnalyzer threw exception java.lang.IncompatibleClassChangeError: Found interface org.eclipse.tigerstripe.workbench.internal.core.model.ArtifactManager, but class was expected @ templates/dependencyAnalyzer.vm[7,58]
[exec] at org.eclipse.tigerstripe.workbench.internal.core.project.pluggable.rules.GlobalTemplateRule.trigger(GlobalTemplateRule.java:183)
[exec] at org.eclipse.tigerstripe.workbench.internal.core.plugin.pluggable.PluginRuleExecutor.trigger(PluginRuleExecutor.java:80)
[exec] at org.eclipse.tigerstripe.workbench.internal.core.plugin.pluggable.PluggablePlugin.trigger(PluggablePlugin.java:158)
[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:259)
[exec] at org.eclipse.tigerstripe.workbench.internal.core.generation.M1Generator.internalPluginLoop(M1Generator.java:671)
[exec] at org.eclipse.tigerstripe.workbench.internal.core.generation.M1Generator.internalRun(M1Generator.java:613)
[exec] at org.eclipse.tigerstripe.workbench.internal.core.generation.M1Generator.run(M1Generator.java:349)
[exec] at org.eclipse.tigerstripe.workbench.internal.core.generation.M1Generator.run(M1Generator.java:89)
[exec] at org.eclipse.tigerstripe.workbench.internal.api.impl.TigerstripeProjectHandle.generate(TigerstripeProjectHandle.java:512)
[exec] at org.eclipse.tigerstripe.workbench.headless.Tigerstripe.generateTigerstripeOutput(Tigerstripe.java:197)
[exec] at org.eclipse.tigerstripe.workbench.headless.Tigerstripe.start(Tigerstripe.java:80)
[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] org.apache.velocity.exception.MethodInvocationException: Invocation of method 'choose' in class org.eclipse.tigerstripe.generators.xml.filters.DependencyAnalyzer threw exception java.lang.IncompatibleClassChangeError: Found interface org.eclipse.tigerstripe.workbench.internal.core.model.ArtifactManager, but class was expected @ templates/dependencyAnalyzer.vm[7,58]
[exec] at org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:300)
[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.ASTMethod.execute(ASTMethod.java:147)
[exec] at org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:203)
[exec] at org.apache.velocity.runtime.parser.node.ASTReference.render(ASTReference.java:294)
[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:162)
[exec] at org.eclipse.tigerstripe.workbench.internal.core.plugin.pluggable.PluginRuleExecutor.trigger(PluginRuleExecutor.java:80)
[exec] at org.eclipse.tigerstripe.workbench.internal.core.plugin.pluggable.PluggablePlugin.trigger(PluggablePlugin.java:158)
[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:259)
[exec] at org.eclipse.tigerstripe.workbench.internal.core.generation.M1Generator.internalPluginLoop(M1Generator.java:671)
[exec] at org.eclipse.tigerstripe.workbench.internal.core.generation.M1Generator.internalRun(M1Generator.java:613)
[exec] at org.eclipse.tigerstripe.workbench.internal.core.generation.M1Generator.run(M1Generator.java:349)
[exec] at org.eclipse.tigerstripe.workbench.internal.core.generation.M1Generator.run(M1Generator.java:89)
[exec] at org.eclipse.tigerstripe.workbench.internal.api.impl.TigerstripeProjectHandle.generate(TigerstripeProjectHandle.java:512)
[exec] at org.eclipse.tigerstripe.workbench.headless.Tigerstripe.generateTigerstripeOutput(Tigerstripe.java:197)
[exec] at org.eclipse.tigerstripe.workbench.headless.Tigerstripe.start(Tigerstripe.java:80)
[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: java.lang.IncompatibleClassChangeError: Found interface org.eclipse.tigerstripe.workbench.internal.core.model.ArtifactManager, but class was expected
[exec] at org.eclipse.tigerstripe.generators.models.PackageModel.getDirectlyOwnedIAbstractArtifacts(PackageModel.java:131)
[exec] at org.eclipse.tigerstripe.generators.xml.helpers.ModelHelpers.isContainingIAbstractArtifact(ModelHelpers.java:191)
[exec] at org.eclipse.tigerstripe.generators.xml.helpers.ModelHelpers.isContainingIAbstractArtifact(ModelHelpers.java:230)
[exec] at org.eclipse.tigerstripe.generators.xml.filters.DependencyAnalyzer.choose(DependencyAnalyzer.java:107)
[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.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:295)
[exec] at org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:245)
[exec] ... 31 more
[exec]
[exec]
[exec] [TIP_Doc_Generator(1.1)Project: org.tmforum.tip.ram version=1.0, Plugin: TIP_Doc_Generator(1.1) version=1.1]
[exec] Generation Successful.
[exec]
[exec] [TIP_JvtSpec_Generator(1.1)Project: org.tmforum.tip.ram version=1.0, 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) 'javaBasicAssociationClassSpecRule'.
[exec] Generation is failed.
[exec] Generation Successful.
[exec]
[exec] [TIP_EjbImpl_Generator(1.1)Project: org.tmforum.tip.ram version=1.0, Plugin: TIP_EjbImpl_Generator(1.1) version=1.1]
[exec] org.eclipse.tigerstripe.workbench.TigerstripeException: Generation is failed.
[exec] Notice: None of the artifact(s) match the specified rule(s) 'javaBasicAssociationClassPersistanceTestRule'.
[exec] at org.eclipse.tigerstripe.workbench.headless.Tigerstripe.generateTigerstripeOutput(Tigerstripe.java:208)
[exec] Notice: None of the artifact(s) match the specified rule(s) 'javaBasicAssociationClassPersistanceDaoImplRule'.
[exec] at org.eclipse.tigerstripe.workbench.headless.Tigerstripe.start(Tigerstripe.java:80)
[exec] Notice: None of the arti...
[truncated message content] |
|
From: Craig G. (opennms) <cg...@op...> - 2012-08-15 19:09:04
|
Hi,
In the PM dependencies model we have to return to the problem of how do
we deal with association classes. It appears that we never satisfactory
resolved this issue in the past because we didn't need association
classes in our models. It is now returning to haunt us. I have looked
carefully at the generated XSD's and it is clear that the present
solution in the Soap generator does not work in a useful way. In the JVT
generated code I have an alternative solution but it does not match the
SOAP generator (see attached Java classes).
The PM Dependency model contains one association class called the
PerformanceIndicatorSpecRelationship.
This has one attribute; String relationshipType. This generates the
following XSD which has no reference to either end of the relationship.
<xsd:element name="performanceIndicatorSpecRelationship"
type="tns:PerformanceIndicatorSpecRelationship"/>
<xsd:complexType name="PerformanceIndicatorSpecRelationship">
<xsd:annotation>
<xsd:documentation>
<p>An association between two
PerformanceIndicatorSpecifications, such as one indicator derived from
another.</p>
<p>This association class is optional</p>
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="relationshipType" type="xsd:string"
minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>
<p>A categorization of the relationship, such as
derived from, composite/atomic, and so forth.</p>
<p>This element is generated from an attribute.</p>
<p>This attribute is optional</p>
<p>This attribute is AVC enabled</p>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
Similarly the generated PerformanceIndicatorSpecification entities which
are linked by this association class do not reference the association
class. In fact, it appears that the the association class between
PerformanceIndicatorSpecification entities is not generated at all.
<xsd:complexType name="PerformanceIndicatorSpecification">
<xsd:annotation>
<xsd:documentation>
<p>A measure of a specific aspect of the performance of an
entity, such as a lost packets or average jitter, defined for a
PeformanceSpecification that may trigger the creation of a
PerformanceConsequence.</p>
<p>This entity is optional</p>
<p>This entity is extendable</p>
<p>This entity does not generate Object Creation
notifications (NA)</p>
<p>This entity does not generate Object Deletion
notifications (NA)</p>
<p>This entity does not generate Object Discovery
notifications (NA)</p>
<p>This entity generates Attribute Value Change
notifications.</p>
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="entity:EntityBase">
<xsd:sequence>
<xsd:element name="name" type="xsd:string" minOccurs="1"
maxOccurs="1">
<xsd:annotation>
<xsd:documentation>
<p>A word, term, or phrase by which a
PerformanceIndicatorSpecification is known and distinguished from other
PerformanceIndicatorSpecifications.</p>
<p>This element is generated from an attribute.</p>
<p>This attribute is mandatory</p>
<p>This attribute is AVC enabled</p>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="description" type="xsd:string"
minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>
<p>A narrative that explains in detail what the
PerformanceIndicatorSpecification is.</p>
<p>This element is generated from an attribute.</p>
<p>This attribute is optional</p>
<p>This attribute is AVC enabled</p>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="perspective" type="xsd:string"
minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>
<p>The point of view for the
PerformanceIndicatorSpecification, such as a single user instance or an
aggregation.</p>
<p>This element is generated from an attribute.</p>
<p>This attribute is optional</p>
<p>This attribute is AVC enabled</p>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="indicatorCategory" type="xsd:string"
minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>
<p>A grouping or set of
PerformanceIndicatorSpecifications that are classified together because
of common characteristics, such as technology specific, service
specific, or technology/service independent.</p>
<p>This element is generated from an attribute.</p>
<p>This attribute is optional</p>
<p>This attribute is AVC enabled</p>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="indicatorType"
type="perf:IndicatorType" minOccurs="1" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>
<p>A kind of value that the
PerformanceIndicator can take on, such as numeric, text, and so forth.</p>
<p>This element is generated from an attribute.</p>
<p>This attribute is mandatory</p>
<p>This attribute is AVC enabled</p>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="derivationAlgorithm"
type="xsd:string" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>
<p>A step-by-step procedure used to calculate
the value of the PerformanceIndicator.</p>
<p>This element is generated from an attribute.</p>
<p>This attribute is optional</p>
<p>This attribute is AVC enabled</p>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="derivationMethod" type="xsd:string"
minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>
<p>For simple calculations, the method used to
calculate the value of a PerformanceIndicator, such as average, minimum,
maximum, sum, and so forth.</p>
<p>This element is generated from an attribute.</p>
<p>This attribute is optional</p>
<p>This attribute is AVC enabled</p>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="collectionType"
type="perf:CollectionType" minOccurs="1" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>
<p>The type of the collection such as: gauge,
commulative, status inspection. Indicators can be produced using these
methods.</p>
<p>This element is generated from an attribute.</p>
<p>This attribute is mandatory</p>
<p>This attribute is AVC enabled</p>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="indicatorUnit" type="xsd:string"
minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>
<p>The unit by which the indicator is measured.
For example: seconds, KBs, rate per second, etc.</p>
<p>This element is generated from an attribute.</p>
<p>This attribute is optional</p>
<p>This attribute is AVC enabled</p>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="ArrayOfPerformanceIndicatorSpecification">
<xsd:sequence>
<xsd:element name="item"
type="tns:PerformanceIndicatorSpecification" minOccurs="0"
maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
In short, we are generating an XSD for an assocation class in the
model which is not referenced by any entity and which cannot be
retrieved across the interface which seems fairly useless.
So my question is;
What is the PerformanceIndicatorSpecRelationship for?
Should association classes actually be treated as Entities so that they
can be referenced through entity identifiers and be used for indirection
between A and Z end's ( that way when an association changes, it makes
sense to send an association value change event) .
Or or should they be treated a data types which are embedded in entities
and contain the entity identifier of the other end artefact. Whatever
the answer is, we aren't doing anything useful at the moment.
Please see the generated Java implementation attached for some ideas.
This is a blocking issue for completing the RI/CTK code for PM
Craig
|
|
From: Craig G. (opennms) <cg...@op...> - 2012-08-15 15:40:16
|
Xose,
Further to my previous post and perhaps more worrying. I find I get the
same error if I create any artifacts in the 'root package'.
to recreate;
1. create a new tigerstripe model
2. enable the soap generator
3. in the soap generator settings in tigerstripe.xml ensure root package
is set
<property name="ROOT_PKG">org.tmforum.tip</property>
4. in tigerstripe model create an entity in package org.tmforum.tip
5. generate model
you get the following error
ERROR ? [15-Aug-2012 16:28:22.760] - Unexpected error while merging
'templates/dependencyAnalyzer.vm' template: Invocation of method
'constructClosure' in class
org.eclipse.tigerstripe.generators.xml.filters.DependencyAnalyzer threw
exception java.lang.StringIndexOutOfBoundsException: String index out of
range: -1 @ templates/dependencyAnalyzer.vm[7,21]. Generation may be
incomplete. [2012-08-15 16:28:21.976+0100]
...
Caused by: java.lang.StringIndexOutOfBoundsException: String index out
of range: -1
at java.lang.String.substring(Unknown Source)
at java.lang.String.substring(Unknown Source)
at
org.eclipse.tigerstripe.generators.xml.helpers.XmlSchemaHelpers.mapPackageToSchemaLocation(XmlSchemaHelpers.java:141)
at
org.eclipse.tigerstripe.generators.xml.helpers.XsdReferencesMgr.<init>(XsdReferencesMgr.java:67)
this is caused by the following code at XmlSchemaHelpers.java line141
when pkgOrSession='org.tmforum.tip' and root='org.tmforum.tip'
if (pkgOrSession.startsWith(root)) {
loc = pkgOrSession.substring(root.length() + 1);
}
Cheers
Craig
On 15/08/2012 15:20, Craig Gallen (opennms) wrote:
> Xose,
>
> This is a minor bug which may cause confusion when people start using
> tigerstripe.
>
> When I run the Soap Generator against an empty model project I get the
> following error;
>
> Unexpected error while merging 'templates/dependencyAnalyzer.vm'
> template: Invocation of method 'getPackagesFromArtifacts' in class
> org.eclipse.tigerstripe.generators.xml.helpers.ModelHelpers threw
> exception java.lang.ClassCastException: $Proxy12 cannot be cast to
> org.eclipse.tigerstripe.workbench.internal.core.model.AbstractArtifact
> @ templates/dependencyAnalyzer.vm[4,43]. Generation may be incomplete.
>
> Details;
> org.eclipse.tigerstripe.workbench.TigerstripeException: Unexpected
> error while merging 'templates/dependencyAnalyzer.vm' template:
> Invocation of method 'getPackagesFromArtifacts' in class
> org.eclipse.tigerstripe.generators.xml.helpers.ModelHelpers threw
> exception java.lang.ClassCastException: $Proxy12 cannot be cast to
> org.eclipse.tigerstripe.workbench.internal.core.model.AbstractArtifact
> @ templates/dependencyAnalyzer.vm[4,43]
> at
> org.eclipse.tigerstripe.workbench.internal.core.project.pluggable.rules.GlobalTemplateRule.trigger(GlobalTemplateRule.java:183)
> at
> org.eclipse.tigerstripe.workbench.internal.core.plugin.pluggable.PluginRuleExecutor.trigger(PluginRuleExecutor.java:80)
> at
> org.eclipse.tigerstripe.workbench.internal.core.plugin.pluggable.PluggablePlugin.trigger(PluggablePlugin.java:158)
> at
> org.eclipse.tigerstripe.workbench.internal.core.plugin.PluginHousing.trigger(PluginHousing.java:35)
> at
> org.eclipse.tigerstripe.workbench.internal.core.plugin.PluginConfig.trigger(PluginConfig.java:259)
> at
> org.eclipse.tigerstripe.workbench.internal.core.generation.M1Generator.internalPluginLoop(M1Generator.java:671)
> at
> org.eclipse.tigerstripe.workbench.internal.core.generation.M1Generator.internalRun(M1Generator.java:613)
> at
> org.eclipse.tigerstripe.workbench.internal.core.generation.M1Generator.run(M1Generator.java:349)
> at
> org.eclipse.tigerstripe.workbench.internal.api.impl.TigerstripeProjectHandle.generate(TigerstripeProjectHandle.java:514)
> at
> org.eclipse.tigerstripe.workbench.ui.internal.wizards.generate.NewTigerstripeRunWizard.finishPage(NewTigerstripeRunWizard.java:95)
> at
> org.eclipse.tigerstripe.workbench.ui.internal.wizards.NewTSElementWizard$2.run(NewTSElementWizard.java:154)
> at
> org.eclipse.jdt.internal.core.BatchOperation.executeOperation(BatchOperation.java:39)
> at
> org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaModelOperation.java:728)
> at
> org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1975)
> at org.eclipse.jdt.core.JavaCore.run(JavaCore.java:4777)
> at
> org.eclipse.jdt.internal.ui.actions.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:106)
> at
> org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
> org.apache.velocity.exception.MethodInvocationException: Invocation of
> method 'getPackagesFromArtifacts' in class
> org.eclipse.tigerstripe.generators.xml.helpers.ModelHelpers threw
> exception java.lang.ClassCastException: $Proxy12 cannot be cast to
> org.eclipse.tigerstripe.workbench.internal.core.model.AbstractArtifact
> @ templates/dependencyAnalyzer.vm[4,43]
> at
> org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:286)
> at
> org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:203)
> at
> org.apache.velocity.runtime.parser.node.ASTReference.value(ASTReference.java:419)
> at
> org.apache.velocity.runtime.parser.node.ASTExpression.value(ASTExpression.java:73)
> at
> org.apache.velocity.runtime.parser.node.ASTSetDirective.render(ASTSetDirective.java:125)
> at
> org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:318)
> at org.apache.velocity.Template.merge(Template.java:254)
> at
> org.eclipse.tigerstripe.workbench.internal.core.project.pluggable.rules.GlobalTemplateRule.trigger(GlobalTemplateRule.java:162)
> at
> org.eclipse.tigerstripe.workbench.internal.core.plugin.pluggable.PluginRuleExecutor.trigger(PluginRuleExecutor.java:80)
> at
> org.eclipse.tigerstripe.workbench.internal.core.plugin.pluggable.PluggablePlugin.trigger(PluggablePlugin.java:158)
> at
> org.eclipse.tigerstripe.workbench.internal.core.plugin.PluginHousing.trigger(PluginHousing.java:35)
> at
> org.eclipse.tigerstripe.workbench.internal.core.plugin.PluginConfig.trigger(PluginConfig.java:259)
> at
> org.eclipse.tigerstripe.workbench.internal.core.generation.M1Generator.internalPluginLoop(M1Generator.java:671)
> at
> org.eclipse.tigerstripe.workbench.internal.core.generation.M1Generator.internalRun(M1Generator.java:613)
> at
> org.eclipse.tigerstripe.workbench.internal.core.generation.M1Generator.run(M1Generator.java:349)
> at
> org.eclipse.tigerstripe.workbench.internal.api.impl.TigerstripeProjectHandle.generate(TigerstripeProjectHandle.java:514)
> at
> org.eclipse.tigerstripe.workbench.ui.internal.wizards.generate.NewTigerstripeRunWizard.finishPage(NewTigerstripeRunWizard.java:95)
> at
> org.eclipse.tigerstripe.workbench.ui.internal.wizards.NewTSElementWizard$2.run(NewTSElementWizard.java:154)
> at
> org.eclipse.jdt.internal.core.BatchOperation.executeOperation(BatchOperation.java:39)
> at
> org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaModelOperation.java:728)
> at
> org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1975)
> at org.eclipse.jdt.core.JavaCore.run(JavaCore.java:4777)
> at
> org.eclipse.jdt.internal.ui.actions.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:106)
> at
> org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
> Caused by: java.lang.ClassCastException: $Proxy12 cannot be cast to
> org.eclipse.tigerstripe.workbench.internal.core.model.AbstractArtifact
> at
> org.eclipse.tigerstripe.generators.xml.helpers.ModelHelpers.getPackagesFromArtifacts(ModelHelpers.java:235)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at
> org.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:295)
> at
> org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:245)
> ... 23 more
>
>
> To reproduce
> 1. In Eclipse select New>tigerstripe Project and create a new project
> 2. in tigerstripe.xml enable Soap Generator
> 3. generate model in work space
>
> If there is an entity in the model, this problem disappears.
> It looks like having no artifacts in an empty model causes the soap
> generator to fail. You may want to check that the dependencyAnalyser
> can cope with empty models as this will be the default state for new
> projects created by the project creator.
>
> Cheers
> Craig
>
|
|
From: Craig G. (opennms) <cg...@op...> - 2012-08-15 14:20:45
|
Xose,
This is a minor bug which may cause confusion when people start using
tigerstripe.
When I run the Soap Generator against an empty model project I get the
following error;
Unexpected error while merging 'templates/dependencyAnalyzer.vm'
template: Invocation of method 'getPackagesFromArtifacts' in class
org.eclipse.tigerstripe.generators.xml.helpers.ModelHelpers threw
exception java.lang.ClassCastException: $Proxy12 cannot be cast to
org.eclipse.tigerstripe.workbench.internal.core.model.AbstractArtifact @
templates/dependencyAnalyzer.vm[4,43]. Generation may be incomplete.
Details;
org.eclipse.tigerstripe.workbench.TigerstripeException: Unexpected error
while merging 'templates/dependencyAnalyzer.vm' template: Invocation of
method 'getPackagesFromArtifacts' in class
org.eclipse.tigerstripe.generators.xml.helpers.ModelHelpers threw
exception java.lang.ClassCastException: $Proxy12 cannot be cast to
org.eclipse.tigerstripe.workbench.internal.core.model.AbstractArtifact @
templates/dependencyAnalyzer.vm[4,43]
at
org.eclipse.tigerstripe.workbench.internal.core.project.pluggable.rules.GlobalTemplateRule.trigger(GlobalTemplateRule.java:183)
at
org.eclipse.tigerstripe.workbench.internal.core.plugin.pluggable.PluginRuleExecutor.trigger(PluginRuleExecutor.java:80)
at
org.eclipse.tigerstripe.workbench.internal.core.plugin.pluggable.PluggablePlugin.trigger(PluggablePlugin.java:158)
at
org.eclipse.tigerstripe.workbench.internal.core.plugin.PluginHousing.trigger(PluginHousing.java:35)
at
org.eclipse.tigerstripe.workbench.internal.core.plugin.PluginConfig.trigger(PluginConfig.java:259)
at
org.eclipse.tigerstripe.workbench.internal.core.generation.M1Generator.internalPluginLoop(M1Generator.java:671)
at
org.eclipse.tigerstripe.workbench.internal.core.generation.M1Generator.internalRun(M1Generator.java:613)
at
org.eclipse.tigerstripe.workbench.internal.core.generation.M1Generator.run(M1Generator.java:349)
at
org.eclipse.tigerstripe.workbench.internal.api.impl.TigerstripeProjectHandle.generate(TigerstripeProjectHandle.java:514)
at
org.eclipse.tigerstripe.workbench.ui.internal.wizards.generate.NewTigerstripeRunWizard.finishPage(NewTigerstripeRunWizard.java:95)
at
org.eclipse.tigerstripe.workbench.ui.internal.wizards.NewTSElementWizard$2.run(NewTSElementWizard.java:154)
at
org.eclipse.jdt.internal.core.BatchOperation.executeOperation(BatchOperation.java:39)
at
org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaModelOperation.java:728)
at
org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1975)
at org.eclipse.jdt.core.JavaCore.run(JavaCore.java:4777)
at
org.eclipse.jdt.internal.ui.actions.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:106)
at
org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
org.apache.velocity.exception.MethodInvocationException: Invocation of
method 'getPackagesFromArtifacts' in class
org.eclipse.tigerstripe.generators.xml.helpers.ModelHelpers threw
exception java.lang.ClassCastException: $Proxy12 cannot be cast to
org.eclipse.tigerstripe.workbench.internal.core.model.AbstractArtifact @
templates/dependencyAnalyzer.vm[4,43]
at
org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:286)
at
org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:203)
at
org.apache.velocity.runtime.parser.node.ASTReference.value(ASTReference.java:419)
at
org.apache.velocity.runtime.parser.node.ASTExpression.value(ASTExpression.java:73)
at
org.apache.velocity.runtime.parser.node.ASTSetDirective.render(ASTSetDirective.java:125)
at
org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:318)
at org.apache.velocity.Template.merge(Template.java:254)
at
org.eclipse.tigerstripe.workbench.internal.core.project.pluggable.rules.GlobalTemplateRule.trigger(GlobalTemplateRule.java:162)
at
org.eclipse.tigerstripe.workbench.internal.core.plugin.pluggable.PluginRuleExecutor.trigger(PluginRuleExecutor.java:80)
at
org.eclipse.tigerstripe.workbench.internal.core.plugin.pluggable.PluggablePlugin.trigger(PluggablePlugin.java:158)
at
org.eclipse.tigerstripe.workbench.internal.core.plugin.PluginHousing.trigger(PluginHousing.java:35)
at
org.eclipse.tigerstripe.workbench.internal.core.plugin.PluginConfig.trigger(PluginConfig.java:259)
at
org.eclipse.tigerstripe.workbench.internal.core.generation.M1Generator.internalPluginLoop(M1Generator.java:671)
at
org.eclipse.tigerstripe.workbench.internal.core.generation.M1Generator.internalRun(M1Generator.java:613)
at
org.eclipse.tigerstripe.workbench.internal.core.generation.M1Generator.run(M1Generator.java:349)
at
org.eclipse.tigerstripe.workbench.internal.api.impl.TigerstripeProjectHandle.generate(TigerstripeProjectHandle.java:514)
at
org.eclipse.tigerstripe.workbench.ui.internal.wizards.generate.NewTigerstripeRunWizard.finishPage(NewTigerstripeRunWizard.java:95)
at
org.eclipse.tigerstripe.workbench.ui.internal.wizards.NewTSElementWizard$2.run(NewTSElementWizard.java:154)
at
org.eclipse.jdt.internal.core.BatchOperation.executeOperation(BatchOperation.java:39)
at
org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaModelOperation.java:728)
at
org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1975)
at org.eclipse.jdt.core.JavaCore.run(JavaCore.java:4777)
at
org.eclipse.jdt.internal.ui.actions.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:106)
at
org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
Caused by: java.lang.ClassCastException: $Proxy12 cannot be cast to
org.eclipse.tigerstripe.workbench.internal.core.model.AbstractArtifact
at
org.eclipse.tigerstripe.generators.xml.helpers.ModelHelpers.getPackagesFromArtifacts(ModelHelpers.java:235)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:295)
at
org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:245)
... 23 more
To reproduce
1. In Eclipse select New>tigerstripe Project and create a new project
2. in tigerstripe.xml enable Soap Generator
3. generate model in work space
If there is an entity in the model, this problem disappears.
It looks like having no artifacts in an empty model causes the soap
generator to fail. You may want to check that the dependencyAnalyser can
cope with empty models as this will be the default state for new
projects created by the project creator.
Cheers
Craig
|
|
From: Pierre G. <pga...@tm...> - 2012-08-15 12:03:40
|
And latest version of TigerStipe as well ? Perre On Aug 15, 2012, at 5:50 AM, Craig Gallen (opennms) wrote: > 1.1.2-SNAPSHOT > > On 14/08/2012 01:09, Pierre Gauthier wrote: >> Thanks Craig. >> >> With what version of Josif ? >> >> Envoyé de mon iPhone >> >> Le 2012-08-13 à 18:21, "Craig Gallen (opennms)" <cg...@op...> a écrit : >> >>> Hi, >>> >>> I've checked in some work on the RAM RI /CTK etc and they should all now >>> work if you build the RAM project first with he latest plugins. >>> >>> Craig >>> >>> ------------------------------------------------------------------------------ >>> 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... >>> https://lists.sourceforge.net/lists/listinfo/openoss-devel >>> >> >> ------------------------------------------------------------------------------ >> 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... >> https://lists.sourceforge.net/lists/listinfo/openoss-devel > > |
|
From: Craig G. (opennms) <cg...@op...> - 2012-08-15 09:51:20
|
1.1.2-SNAPSHOT On 14/08/2012 01:09, Pierre Gauthier wrote: > Thanks Craig. > > With what version of Josif ? > > Envoyé de mon iPhone > > Le 2012-08-13 à 18:21, "Craig Gallen (opennms)" <cg...@op...> a écrit : > >> Hi, >> >> I've checked in some work on the RAM RI /CTK etc and they should all now >> work if you build the RAM project first with he latest plugins. >> >> Craig >> >> ------------------------------------------------------------------------------ >> 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... >> https://lists.sourceforge.net/lists/listinfo/openoss-devel >> > > ------------------------------------------------------------------------------ > 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... > https://lists.sourceforge.net/lists/listinfo/openoss-devel |
|
From: Xose R. S. V. <xr...@op...> - 2012-08-14 11:38:18
|
Hi Craig I have fixed the velocity template that miss the behaivour that you describe in your email. I will analyze the filtering model and your proposals now. Regards El 11/08/2012 11:42, Craig Gallen (opennms) escribió: > Hi Xose, Marc > > Once again I'm afraid I've come up with a new bug in the xml generated > by the soap generator and some other questions. I have found this > while trying to get the PM model implementation to generate correctly. > > 1.Problem: tipEntityGetMultiple stereotype not generating correct > iterator response element > > In pm_cbe_perf_mon_coll_adhoccollectionservice_msg.xsd we can see two > examples of generated iterators; > > a) getTrackingRecords is an explicit method declared in the > AdhocCollectionService with stereotype settings 'isBulkPotential' and > 'bulk transfer pattern = ITERATOR'. > In the this case the response object getTrackingRecordsResponse > correctly extends iterator:CommonResponse > <xsd:complexType name="getTrackingRecordsResponse"> > <xsd:complexContent> > <xsd:extension base="iterator:CommonResponse"> > <xsd:sequence> > <xsd:element name="trackingRecords" > type="problem:TrackingRecordResultWithIterator" minOccurs="0" > maxOccurs="1"> > ... etc > > b) getAdhocCollections is generated using the tipEntityGetMultiple > stereotype on the AdhocCollection entity > in this case the response object getAdhocCollectionsResponse > incorrectly does not extend iterator:CommonResponse > <xsd:complexType name="getAdhocCollectionsResponse"> > <xsd:sequence> > <xsd:element name="AdhocCollections" > type="tns:AdhocCollectionResultWithIterator" minOccurs="0" maxOccurs="1"> > ... etc > > This is a bug and needs fixed quickly for the PM interface to work. We > need to change the soap generator to ensure that all iterator > responses extend from iterator:CommonResponse whether explicitly > declared in a method stereotype or declared through the > tipEntityGetMultiple stereotype. i.e.; > <xsd:complexType name="getAdhocCollectionsResponse"> > <xsd:complexContent> > <xsd:extension base="iterator:CommonResponse"> > <xsd:sequence> > <xsd:element name="AdhocCollections" > type="tns:AdhocCollectionResultWithIterator" minOccurs="0" maxOccurs="1"> > ... etc > > ____________ > > 2. Question / feature request - needs consideration by the team > The filtering mechanism seems overly complex and very different > between the use of primitive.filter and tipEntityGetMultiple > This is a plea to think through whether we could simplify the template > filtering mechanism to support any type of entity rather than having > it type specific. The comments below are observations and will need a > bit more thinking through but I think they align with what is needed > for the inventory interface. > > In the TIP Profile the primitive.filter has the following > documentation; 'Primitive filter datatype corresponding to a choice of > template or query filter'. This is not what we generate. > > The generated XML for attribute filter type primitive.filter in the > ResourceAlarmRetreivalService ( RAM Model) is > <xsd:element name="filter" type="filter:XPathQueryFilter" > minOccurs="0" maxOccurs="1"> > > In other word there is no choice of template or query filter. > primitive.filter only uses xpath > > In the getAdhocCollections request generated from the > tipEntityGetMultiple stereotype we generate > attribute filter of type AdhocCollectionFilterChoice > > <xsd:complexType name="getAdhocCollectionsRequest"> > <xsd:complexContent> > <xsd:extension base="iterator:CommonRequest"> > <xsd:sequence> > <xsd:element name="filter" > type="tns:AdhocCollectionFilterChoice" minOccurs="0" maxOccurs="1"> > ... etc > > <xsd:complexType name="AdhocCollectionFilterChoice"> > <xsd:choice> > <xsd:element name="templateFilter" > type="tns:AdhocCollectionTemplateFilter" minOccurs="0" maxOccurs="1"/> > <xsd:element name="queryFilter" > type="filter:XPathQueryFilter" minOccurs="0" maxOccurs="1"/> > </xsd:choice> > </xsd:complexType> > > <xsd:complexType name="AdhocCollectionTemplateFilter"> > <xsd:complexContent> > <xsd:extension base="filter:TemplateFilter"> > <xsd:sequence> > <xsd:element name="templates" > type="tns:ArrayOfAdhocCollectionTemplate" minOccurs="0" maxOccurs="1"/> > </xsd:sequence> > </xsd:extension> > </xsd:complexContent> > > In other word we have a choice of AdhocCollectionTemplateFilter or the > XPathQueryFilter which we could get from primitive.filter above > (although the signature is very different). This is overly complex and > inconsistent. We clearly need primitive.filter to generated the same > sort of selection mechanisms as tipEntityGetMultiple but the > primitive.filter template filter needs to be generic to any entity > type rather than specific to a particular entity as in > AdhocCollectionTemplateFilter > > Would it be possible for both primitive.filter and > tipEntityGetMultiple to generate something like; > > <xsd:complexType name="FilterChoice"> > <xsd:choice> > <xsd:element name="templateFilter" type="tns:TemplateFilter" > minOccurs="0" maxOccurs="1"/> > <xsd:element name="queryFilter" > type="filter:XPathQueryFilter" minOccurs="0" maxOccurs="1"/> > </xsd:choice> > </xsd:complexType> > > <xsd:complexType name="TemplateFilter"> > <xsd:complexContent> > <xsd:sequence> > <xsd:element name="templates" > type="tns:ArrayOfTemplate" minOccurs="0" maxOccurs="1"/> > </xsd:sequence> > </xsd:complexContent> > > where all Entity Template types then extend Template? > > What do you think? > > 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-08-14 00:09:43
|
Thanks Craig. With what version of Josif ? Envoyé de mon iPhone Le 2012-08-13 à 18:21, "Craig Gallen (opennms)" <cg...@op...> a écrit : > Hi, > > I've checked in some work on the RAM RI /CTK etc and they should all now > work if you build the RAM project first with he latest plugins. > > Craig > > ------------------------------------------------------------------------------ > 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... > https://lists.sourceforge.net/lists/listinfo/openoss-devel > |
|
From: Craig G. (opennms) <cg...@op...> - 2012-08-13 22:21:39
|
Hi, I've checked in some work on the RAM RI /CTK etc and they should all now work if you build the RAM project first with he latest plugins. Craig |
|
From: Craig G. (opennms) <cg...@op...> - 2012-08-11 09:42:20
|
Hi Xose, Marc
Once again I'm afraid I've come up with a new bug in the xml generated
by the soap generator and some other questions. I have found this while
trying to get the PM model implementation to generate correctly.
1.Problem: tipEntityGetMultiple stereotype not generating correct
iterator response element
In pm_cbe_perf_mon_coll_adhoccollectionservice_msg.xsd we can see two
examples of generated iterators;
a) getTrackingRecords is an explicit method declared in the
AdhocCollectionService with stereotype settings 'isBulkPotential' and
'bulk transfer pattern = ITERATOR'.
In the this case the response object getTrackingRecordsResponse
correctly extends iterator:CommonResponse
<xsd:complexType name="getTrackingRecordsResponse">
<xsd:complexContent>
<xsd:extension base="iterator:CommonResponse">
<xsd:sequence>
<xsd:element name="trackingRecords"
type="problem:TrackingRecordResultWithIterator" minOccurs="0" maxOccurs="1">
... etc
b) getAdhocCollections is generated using the tipEntityGetMultiple
stereotype on the AdhocCollection entity
in this case the response object getAdhocCollectionsResponse incorrectly
does not extend iterator:CommonResponse
<xsd:complexType name="getAdhocCollectionsResponse">
<xsd:sequence>
<xsd:element name="AdhocCollections"
type="tns:AdhocCollectionResultWithIterator" minOccurs="0" maxOccurs="1">
... etc
This is a bug and needs fixed quickly for the PM interface to work. We
need to change the soap generator to ensure that all iterator responses
extend from iterator:CommonResponse whether explicitly declared in a
method stereotype or declared through the tipEntityGetMultiple
stereotype. i.e.;
<xsd:complexType name="getAdhocCollectionsResponse">
<xsd:complexContent>
<xsd:extension base="iterator:CommonResponse">
<xsd:sequence>
<xsd:element name="AdhocCollections"
type="tns:AdhocCollectionResultWithIterator" minOccurs="0" maxOccurs="1">
... etc
____________
2. Question / feature request - needs consideration by the team
The filtering mechanism seems overly complex and very different between
the use of primitive.filter and tipEntityGetMultiple
This is a plea to think through whether we could simplify the template
filtering mechanism to support any type of entity rather than having it
type specific. The comments below are observations and will need a bit
more thinking through but I think they align with what is needed for the
inventory interface.
In the TIP Profile the primitive.filter has the following documentation;
'Primitive filter datatype corresponding to a choice of template or
query filter'. This is not what we generate.
The generated XML for attribute filter type primitive.filter in the
ResourceAlarmRetreivalService ( RAM Model) is
<xsd:element name="filter" type="filter:XPathQueryFilter" minOccurs="0"
maxOccurs="1">
In other word there is no choice of template or query filter.
primitive.filter only uses xpath
In the getAdhocCollections request generated from the
tipEntityGetMultiple stereotype we generate
attribute filter of type AdhocCollectionFilterChoice
<xsd:complexType name="getAdhocCollectionsRequest">
<xsd:complexContent>
<xsd:extension base="iterator:CommonRequest">
<xsd:sequence>
<xsd:element name="filter"
type="tns:AdhocCollectionFilterChoice" minOccurs="0" maxOccurs="1">
... etc
<xsd:complexType name="AdhocCollectionFilterChoice">
<xsd:choice>
<xsd:element name="templateFilter"
type="tns:AdhocCollectionTemplateFilter" minOccurs="0" maxOccurs="1"/>
<xsd:element name="queryFilter" type="filter:XPathQueryFilter"
minOccurs="0" maxOccurs="1"/>
</xsd:choice>
</xsd:complexType>
<xsd:complexType name="AdhocCollectionTemplateFilter">
<xsd:complexContent>
<xsd:extension base="filter:TemplateFilter">
<xsd:sequence>
<xsd:element name="templates"
type="tns:ArrayOfAdhocCollectionTemplate" minOccurs="0" maxOccurs="1"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
In other word we have a choice of AdhocCollectionTemplateFilter or the
XPathQueryFilter which we could get from primitive.filter above
(although the signature is very different). This is overly complex and
inconsistent. We clearly need primitive.filter to generated the same
sort of selection mechanisms as tipEntityGetMultiple but the
primitive.filter template filter needs to be generic to any entity type
rather than specific to a particular entity as in
AdhocCollectionTemplateFilter
Would it be possible for both primitive.filter and tipEntityGetMultiple
to generate something like;
<xsd:complexType name="FilterChoice">
<xsd:choice>
<xsd:element name="templateFilter" type="tns:TemplateFilter"
minOccurs="0" maxOccurs="1"/>
<xsd:element name="queryFilter" type="filter:XPathQueryFilter"
minOccurs="0" maxOccurs="1"/>
</xsd:choice>
</xsd:complexType>
<xsd:complexType name="TemplateFilter">
<xsd:complexContent>
<xsd:sequence>
<xsd:element name="templates" type="tns:ArrayOfTemplate"
minOccurs="0" maxOccurs="1"/>
</xsd:sequence>
</xsd:complexContent>
where all Entity Template types then extend Template?
What do you think?
Craig
|
|
From: <cg...@op...> - 2012-08-10 09:18:28
|
Hi SB Firstly, could you always copy all questions to the openoss-devel list - that way we have a record and others can jump in. I have several suggestions to try. Firstly, if you are building 1.1.2 models , have you updated to the latest tigerstripe version in the JOSIF stream and are you using the latest soap plugin from xose - he has been fixing bugs related to tigerstripe and the 'TigerstripeProjectHandle.getTSProject' looks like it could be related to problems he had previously. 1. Have you got the latest 1.1.2 snapshot (trunk) tigerstripe plugins and profile installed. You need to check these out from trunk and install the in the workspace directly. You MUST uninstall the 1.1.1 plugins and profile before installing the 1.1.2-snapshot plugins. Only these generators / profile will work with trunk code. 1. Having run eclipse:eclipse, try importing the dependency project into your workspace and running tigerstripe from the workspace UI on the dependency model and see what happens. When you import the model, does it have any errors? If the UI code generation works without errors, then the build should be OK 3. sometimes (I don't know why), tigerstripe forgets about the dependency jars it needs for a model. These are imported into the workspace and are referenced from the tigerstripe.xml - but for some reason the tigerstripe model artefacts show dependencies not satisfied. The quick fix to this is to open tigerstripe.xml, unselect the dependencies and save the file ( this will cause errors) then open the file and re-select the dependency models and save. Tigerstripe is then happy. (there appears to be some sort of intermittent class loading issues for dependency models). You can then 'team>revert' the tigerstripe.xml file - because you have actually done no changes and you don't need to commit the latest version. 4. Sometimes this problem occurs if you run tigerstripe in a maven build at the same time as having eclipse open in the workspace. Close eclipse before you run the build.. 5. Finally, if all else fails, it is sometimes necessary to close eclipse, remove the .metadata from the project work space and re-create the work space in eclipse. You don't need to delete and project files - just reimport them into the new workspace. Hope this helps Craig From: SB Mahapatra [mailto:sbm...@tm...] Sent: 10 August 2012 08:06 To: Craig Gallen (opennms) Cc: Sasi Podila (sbp...@gm...) Subject: SPM and RAM Build failure Hi Craig, We are facing problem while executing the below command for RAM and SPM. 1. "mvn -U eclipse:eclipse" 2. "mvn clean install" The above commands are executed in XXX_BaseProject directory and the error log is attached. Please suggest any corrective action need to be taken. Note : The above exercise is being done by taking the latest code from SVN repository. The workbench installer "TIP_Workbench_Installer-1.1.1-20120118-standard.jar" https://collab.tmforum.org/svn/repos/tip/Features/ResourceAlarmManagement/IA /Interface/trunk/ - for RAM Thanks and Regds, SB |
|
From: Craig G. (opennms) <cg...@op...> - 2012-08-08 09:35:57
|
Hi Bernd,
Sorry we have all been on leave. It would be best for your team to look
at the wsdl generated from the RAM and MPAC models to find a number of
different examples but to simply answer your question here are two
examples;
1. attribute multiplicity is very similar to the MTOSI example and is
handled in the following way.
Ratehr than just have an anonomous array of elements, we tend to define
and reference named 'ArrayOfXXX' elements which are xsd:sequences with
minOccurs="0" maxOccurs="unbounded". the ArrayOfXXX can then be
referenced in several places which allows us to define iterator
responses using the same sequence. This is illustrated in the RAM model
'getResourceAlarms' operation which has an out argument of
ResourceAlarm[0..*] in the model
It is is rendered to look like this; (Because we have also asked for an
iterator, the result is slightly more complicated but the basic
multiplicity is defined throughout by ArrayOfResourceAlarm )
<xsd:complexType name="ResourceAlarmResultWithIterator">
<xsd:sequence>
<xsd:element name="result" type="tns:ArrayOfResourceAlarm"/>
<xsd:element name="iterator" type="iterator:IteratorInfo"/>
</xsd:sequence>
</xsd:complexType>
The way we handle the * is by referencing an 'ArrayOfResourceAlarm'
which is defined as
<xsd:complexType name="ArrayOfResourceAlarm">
<xsd:sequence>
<xsd:element name="item" type="tns:ResourceAlarm"
minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
2. How does JOSIF convert an Enumeration data type in the IA into XML?
If we take the org.tmforum.tip.resource.trouble.alarm.AlarmAckState
enumeration as an example. In the model this is defined as a string
enumeration with a number of values. The string can only take one of the
values defined in the enumeration.
In the xsd we get
<xsd:simpleType name="AlarmAckState">
<xsd:annotation>
<xsd:documentation>
<p>It defines the various alarm states that can be returned
using a get operation.</p>
</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="ALL_ALARMS">
<xsd:annotation>
<xsd:documentation>
<p/>
<p>This literal has value "ALL_ALARMS"</p>
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="ALL_ACTIVE_ALARMS">
<xsd:annotation>
<xsd:documentation>
<p/>
<p>This literal has value "ALL_ACTIVE_ALARMS"</p>
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="ALL_ACTIVE_AND_ACKNOWLEDGED_ALARMS">
<xsd:annotation>
<xsd:documentation>
<p/>
<p>This literal has value
"ALL_ACTIVE_AND_ACKNOWLEDGED_ALARMS"</p>
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="ALL_ACTIVE_AND_UNACKNOWLEDGED_ALARMS">
<xsd:annotation>
<xsd:documentation>
<p/>
<p>This literal has value
"ALL_ACTIVE_AND_UNACKNOWLEDGED_ALARMS"</p>
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="ALL_CLEARED_AND_UNACKNOWLEDGED_ALARMS">
<xsd:annotation>
<xsd:documentation>
<p/>
<p>This literal has value
"ALL_CLEARED_AND_UNACKNOWLEDGED_ALARMS"</p>
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="ALL_UNACKNOWLEDGED_ALARMS">
<xsd:annotation>
<xsd:documentation>
<p/>
<p>This literal has value
"ALL_UNACKNOWLEDGED_ALARMS"</p>
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
</xsd:restriction>
</xsd:simpleType>
For integer enumerations, such as AlarmAckStatus in MPAC, we use the
same principle. AlarmAckStatus is defined as having values
int CLEARED = 0;
int PENDING = 5;
int WARNING = 6;
int INDETERMINATE = 2;
int MINOR = 4;
int MAJOR = 3;
int CRITICAL = 1;
However we actually use strings to represent the integers rather than
xsd:int values in the definition. (Actually we need to improve this sxd
generation by listing the value represented by the int in the
documentation).
<xsd:simpleType name="AlarmStatus">
<xsd:annotation>
<xsd:documentation>
<p/>
</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="0">
<xsd:annotation>
<xsd:documentation>
<p/>
<p>This literal has value 0</p>
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="5">
<xsd:annotation>
<xsd:documentation>
<p/>
<p>This literal has value 5</p>
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="6">
<xsd:annotation>
<xsd:documentation>
<p/>
<p>This literal has value 6</p>
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="2">
<xsd:annotation>
<xsd:documentation>
<p/>
<p>This literal has value 2</p>
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="4">
<xsd:annotation>
<xsd:documentation>
<p/>
<p>This literal has value 4</p>
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="3">
<xsd:annotation>
<xsd:documentation>
<p/>
<p>This literal has value 3</p>
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="1">
<xsd:annotation>
<xsd:documentation>
<p/>
<p>This literal has value 1</p>
</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
</xsd:restriction>
</xsd:simpleType>
Hope this helps
Craig
On 06/08/2012 08:52, B.Z...@te... wrote:
> Hallo Pierre, Craig,
> At the last MMUG meeting on Friday (3rd) we got to two questions
> regarding how JOSIF maps IA definitions into XSDs.
>
> 1. Attribute multiplicity "*"
> How does JOSIF convert the "*" multiplicity of an attribute in the
> IA into XML?
> Note: In MTOSI (where the XML is created "by hand") we define an
> intermediate complex type using a sequence; see following example:
> <!-- ============== -->
> <xsd:complexType name="LayeredSNPPListType">
> <xsd:annotation>
> <xsd:documentation>
> <p> The List of layered SNPPs. It is a list of the SNPPs
> at all layers. A given layerRate value can appear only once in
> this list.</p>
> </xsd:documentation>
> </xsd:annotation>
> <xsd:sequence>
> <xsd:element name="layeredSNPPType"
> type="tns:LayeredSNPPType" minOccurs="0" maxOccurs="unbounded"/>
> </xsd:sequence>
> </xsd:complexType>
> <!-- ============== -->
> 2. Enumerations
> How does JOSIF convert an Enumeration data type in the IA into XML?
> Excerpt from the minutes of the MMUG call:
> "In cases where ENUM is used in the IA and string in the IIS, it
> may be better (for backward compatibility reasons) to use a string
> in the IA also. We should check this point with the SII team.
> Bernd thought that this would make the IA weaker. Action Item:
> Bernd to check with someone on the SII team."
>
> Thank you for your help.
> Regards
> Bernd
>
> Deutsche Telekom AG
> Group Technology
> *Bernd Zeuner*
> Heinrich-Hertz-Str. 3-7, 64295 Darmstadt, Germany
> +49 6151 58-12086 (Phone)
> +49 391 580 222 588 (Fax)
> E-Mail: b.z...@te... <mailto:b.z...@te...>
> _www.telekom.com_ <http://www.telekom.com/>
>
> Life is for sharing.
>
> Deutsche Telekom AG
> Supervisory Board: Prof. Dr. Ulrich Lehner (Chairman)
> Board of Management: René Obermann (Chairman),
> Dr. Manfred Balz, Reinhard Clemens, Niek Jan van Damme,
> Timotheus Höttges, Claudia Nemat, Prof. Dr. Marion Schick
> Commercial register: Amtsgericht Bonn HRB 6794
> Registered office: Bonn
>
> *Big changes start small --conserve resources by not printing every
> e-mail.*
>
|
|
From: Xose R. S. V. <xr...@op...> - 2012-08-02 06:35:34
|
Marc enjoy a lot in your holiday Congratulations. El 01/08/2012 13:37, Craig Gallen (opennms) escribió: > Marc > > Congratulations et félicitations > > Have a great holiday > > Craig > > On 01/08/2012 10:46, Flauw, Marc wrote: >> >> Dear all, >> >> Just to let you know our granddaughter (first grandchild) is born >> this morning. Mother and child are doing fine. We will be with them >> tomorrow morning. >> >> I was waiting for this event to trigger the start of our vacations, >> so I will be on vacations starting tomorrow up to August 17 included. >> >> Best regards >> >> Marc >> > > > > ------------------------------------------------------------------------------ > 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... > https://lists.sourceforge.net/lists/listinfo/openoss-devel -- *Xose Ramon Sousa Vazquez* | Director OSS Technologies, Director I+D T/ + 34 986 410 091 (ext) 206 | M/ +34 675 550 029 www.optaresolutions.com <http://www.optaresolutions.com> Optare Solutions <http://optarecoolvendor.com><http://optarecoolvendor.com> |
|
From: Craig G. (opennms) <cg...@op...> - 2012-08-01 21:56:36
|
Hi, I have made some corrections to the latest additions to the common model. 2 Points to note; 1. the description /documention text in a tigerstripe artifact must not contain an ampersand & as in 'date & time'. & is a reserved character which causes problems if present in the generated XSD's. A number of the imported org.tmforum.tip.cbe.time.sched package datatypes had this in their documentation. I have replaced & with 'and' wherever present. 2. a number of the new datatypes in the org.tmforum.tip.cbe.time.sched package had tipClass stereotypes applied. As determined by the tipProfile, Datatypes should only be annotated with the tipDatatype stereotype or not annotated at all. I have removed the tipClass stereotype from all the datatypes in org.tmforum.tip.cbe.time.sched package. In the PM model, I have also removed the common model from subversion as this is pulled in by the maven build from the latest common model deployed. Cheers Craig |
|
From: Craig G. (opennms) <cg...@op...> - 2012-08-01 11:38:01
|
Marc Congratulations et félicitations Have a great holiday Craig On 01/08/2012 10:46, Flauw, Marc wrote: > > Dear all, > > Just to let you know our granddaughter (first grandchild) is born this > morning. Mother and child are doing fine. We will be with them > tomorrow morning. > > I was waiting for this event to trigger the start of our vacations, so > I will be on vacations starting tomorrow up to August 17 included. > > Best regards > > Marc > |
|
From: Flauw, M. <Mar...@hp...> - 2012-08-01 06:59:07
|
Dear all, I just updated the Common Model with the changes to the Schedule Definition package agreed at TAW. Changes in the Sid were made by Yuval and reviewed yesterday. What has changed: - Updated model in org.tmforum.tip.cbe.time.sched: some modified datatypes, 4 new ones - Updated documentation - Updated jpg Best regards Marc |
|
From: Flauw, M. <Mar...@hp...> - 2012-07-31 14:00:25
|
Craig, I was thinking of the latter: having SID Import prefix the valueType attribute by an underscore, but I can put a CR on the SID also. Best regards Marc From: Craig Gallen [mailto:gal...@go...] On Behalf Of cg...@op... Sent: Tuesday, July 31, 2012 3:53 PM To: Flauw, Marc; cg...@op...; Yuv...@te... Cc: ope...@li... Subject: RE: Please avoid using valueType as a field name in JOSIF Models (PM Model) Hi, Thanks for that. In theory we could underscore valueType in the attribute access code but it will involve quite a lot of rework, testing and also loss of backwards compatibility. More importantly it will moves us away from the OSS/J design pattern which I wanted to preserve if at all possible. To my knowledge 'valueType' doesn't seem to be a generic term for field names in the SID since it is used with different type variables. Would it be impossibly difficult to change the 25 field names to more closely reflect the types they represent. Perhaps this could be done as part of the expedited interfaces project. Alternatively, could the UML importer put an underscore _valueType whenever it does an import of the valueType field name Craig From: Flauw, Marc [mailto:Mar...@hp...]<mailto:[mailto:Mar...@hp...]> Sent: 31 July 2012 14:24 To: cg...@op...<mailto:cg...@op...>; Yuv...@te...<mailto:Yuv...@te...> Cc: ope...@li...<mailto:ope...@li...> Subject: RE: Please avoid using valueType as a field name in JOSIF Models (PM Model) Hi Craig, We fixed the PM attribute, but there are 26 attributes named valueType all together in the SID. Is there a way to work around, like putting an underscore in front of the attribute? Best regards Marc From: Craig Gallen [mailto:gal...@go...]<mailto:[mailto:gal...@go...]> On Behalf Of cg...@op...<mailto:cg...@op...> Sent: Tuesday, July 31, 2012 11:08 AM To: Flauw, Marc; 'Yuval Stein' Cc: ope...@li...<mailto:ope...@li...> Subject: Please avoid using valueType as a field name in JOSIF Models (PM Model) Marc, Yuval, I have found a problem in the PM dependency model. As you know the Java API we are using for the RI / CTK is based upon the OSS/J design patterns. This means that every Java value type we generate has a reserved field VALUE_TYPE and an operator getValueType(). As a result it is important that 'valueType' is not used as a name for an attribute of an Entity, DataType or Facade in the model. This has not been a problem to date but I have found an issue in the PM Dependencies model; org.tmforum.tip.cbe.perf.spec.PerformanceIndicatorSpecification has the field valueType; // A kind of value that the PerformanceIndicator can take on, such as numeric, text, and so forth. org.tmforum.tip.cbe.perf.IndicatorType valueType Could we please change the name of the field in the model from valueType to indicatorType Thanks Craig |
|
From: <cg...@op...> - 2012-07-31 13:53:19
|
Hi, Thanks for that. In theory we could underscore valueType in the attribute access code but it will involve quite a lot of rework, testing and also loss of backwards compatibility. More importantly it will moves us away from the OSS/J design pattern which I wanted to preserve if at all possible. To my knowledge 'valueType' doesn't seem to be a generic term for field names in the SID since it is used with different type variables. Would it be impossibly difficult to change the 25 field names to more closely reflect the types they represent. Perhaps this could be done as part of the expedited interfaces project. Alternatively, could the UML importer put an underscore _valueType whenever it does an import of the valueType field name Craig From: Flauw, Marc [mailto:Mar...@hp...] Sent: 31 July 2012 14:24 To: cg...@op...; Yuv...@te... Cc: ope...@li... Subject: RE: Please avoid using valueType as a field name in JOSIF Models (PM Model) Hi Craig, We fixed the PM attribute, but there are 26 attributes named valueType all together in the SID. Is there a way to work around, like putting an underscore in front of the attribute? Best regards Marc From: Craig Gallen [mailto:gal...@go...] On Behalf Of cg...@op... Sent: Tuesday, July 31, 2012 11:08 AM To: Flauw, Marc; 'Yuval Stein' Cc: ope...@li... Subject: Please avoid using valueType as a field name in JOSIF Models (PM Model) Marc, Yuval, I have found a problem in the PM dependency model. As you know the Java API we are using for the RI / CTK is based upon the OSS/J design patterns. This means that every Java value type we generate has a reserved field VALUE_TYPE and an operator getValueType(). As a result it is important that 'valueType' is not used as a name for an attribute of an Entity, DataType or Facade in the model. This has not been a problem to date but I have found an issue in the PM Dependencies model; org.tmforum.tip.cbe.perf.spec.PerformanceIndicatorSpecification has the field valueType; // A kind of value that the PerformanceIndicator can take on, such as numeric, text, and so forth. org.tmforum.tip.cbe.perf.IndicatorType valueType Could we please change the name of the field in the model from valueType to indicatorType Thanks Craig |
|
From: Flauw, M. <Mar...@hp...> - 2012-07-31 13:25:37
|
Hi Craig, We fixed the PM attribute, but there are 26 attributes named valueType all together in the SID. Is there a way to work around, like putting an underscore in front of the attribute? Best regards Marc From: Craig Gallen [mailto:gal...@go...] On Behalf Of cg...@op... Sent: Tuesday, July 31, 2012 11:08 AM To: Flauw, Marc; 'Yuval Stein' Cc: ope...@li... Subject: Please avoid using valueType as a field name in JOSIF Models (PM Model) Marc, Yuval, I have found a problem in the PM dependency model. As you know the Java API we are using for the RI / CTK is based upon the OSS/J design patterns. This means that every Java value type we generate has a reserved field VALUE_TYPE and an operator getValueType(). As a result it is important that 'valueType' is not used as a name for an attribute of an Entity, DataType or Facade in the model. This has not been a problem to date but I have found an issue in the PM Dependencies model; org.tmforum.tip.cbe.perf.spec.PerformanceIndicatorSpecification has the field valueType; // A kind of value that the PerformanceIndicator can take on, such as numeric, text, and so forth. org.tmforum.tip.cbe.perf.IndicatorType valueType Could we please change the name of the field in the model from valueType to indicatorType Thanks Craig |
|
From: Flauw, M. <Mar...@hp...> - 2012-07-31 09:13:20
|
Hi Craig, We will discuss in PM meeting this afternoon and will come back to you. Best regards Marc From: Craig Gallen [mailto:gal...@go...] On Behalf Of cg...@op... Sent: Tuesday, July 31, 2012 11:08 AM To: Flauw, Marc; 'Yuval Stein' Cc: ope...@li... Subject: Please avoid using valueType as a field name in JOSIF Models (PM Model) Marc, Yuval, I have found a problem in the PM dependency model. As you know the Java API we are using for the RI / CTK is based upon the OSS/J design patterns. This means that every Java value type we generate has a reserved field VALUE_TYPE and an operator getValueType(). As a result it is important that 'valueType' is not used as a name for an attribute of an Entity, DataType or Facade in the model. This has not been a problem to date but I have found an issue in the PM Dependencies model; org.tmforum.tip.cbe.perf.spec.PerformanceIndicatorSpecification has the field valueType; // A kind of value that the PerformanceIndicator can take on, such as numeric, text, and so forth. org.tmforum.tip.cbe.perf.IndicatorType valueType Could we please change the name of the field in the model from valueType to indicatorType Thanks Craig |
197 messages has been excluded from this view by a project administrator.
