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: Xose R. S. V. <xr...@op...> - 2012-06-01 12:00:11
|
I am going to view the problem to see which is the cause Regards El 31/05/2012 23:57, Craig Gallen (opennms) escribió: > Hi, > > I have been testing the TIP_PM_Col project model and have found that > the dep_cbe_perf_spec.xsd (attached) file is generated with errors > > in line 62 we have > <xsd:element name="objectInstanceFilter" > type="filter:XPathQueryFilter" minOccurs="0" maxOccurs="1"> > > filter:XPathQueryFilter is not defined and if you open the file in > eclipse it reports this error as: > > 's4s-att-invalid-value: Invalid attribute value for 'type' in element > 'element'. Recorded reason: > UndeclaredPrefix: Cannot resolve 'filter:XPathQueryFilter' as a > QName: the prefix 'filter' is not > declared'. > > Is this a known problem or a new bug? > > Craig -- *Xose Ramon Sousa Vazquez* | Director OSS Technologies, Director I+D T/ + 34 986 410 091 (ext) 206 | M/ +34 675 550 029 www.optaresolutions.com <http://www.optaresolutions.com> Optare Solutions <http://optarecoolvendor.com><http://optarecoolvendor.com> |
|
From: Flauw, M. <Mar...@hp...> - 2012-06-01 09:28:41
|
Craig, There is one same filter in the getReosurceAlarms operation, filter argument. The XPathFilter is defined in the internal_filter.xsd Best regards Marc -----Original Message----- From: Craig Gallen [mailto:gal...@go...] On Behalf Of Craig Gallen (opennms) Sent: Thursday, May 31, 2012 11:58 PM To: openoss-devel; Flauw, Marc; Xose Ramon Sousa Vazquez; pierre gauthier Subject: Problems with PM XSD generation Hi, I have been testing the TIP_PM_Col project model and have found that the dep_cbe_perf_spec.xsd (attached) file is generated with errors in line 62 we have <xsd:element name="objectInstanceFilter" type="filter:XPathQueryFilter" minOccurs="0" maxOccurs="1"> filter:XPathQueryFilter is not defined and if you open the file in eclipse it reports this error as: 's4s-att-invalid-value: Invalid attribute value for 'type' in element 'element'. Recorded reason: UndeclaredPrefix: Cannot resolve 'filter:XPathQueryFilter' as a QName: the prefix 'filter' is not declared'. Is this a known problem or a new bug? Craig |
|
From: Craig G. (opennms) <cg...@op...> - 2012-05-31 21:57:52
|
Hi, I have been testing the TIP_PM_Col project model and have found that the dep_cbe_perf_spec.xsd (attached) file is generated with errors in line 62 we have <xsd:element name="objectInstanceFilter" type="filter:XPathQueryFilter" minOccurs="0" maxOccurs="1"> filter:XPathQueryFilter is not defined and if you open the file in eclipse it reports this error as: 's4s-att-invalid-value: Invalid attribute value for 'type' in element 'element'. Recorded reason: UndeclaredPrefix: Cannot resolve 'filter:XPathQueryFilter' as a QName: the prefix 'filter' is not declared'. Is this a known problem or a new bug? Craig |
|
From: Gao, Y. (S. ES-Apps-GD-China-SH) <yan...@hp...> - 2012-05-14 06:50:13
|
Helllo Craig,
We have verified the OpenNMS services including iterator in URL: http://152.78.189.89:8086/RI/services
They both works fine.
Now our HP NMS software could integrate with opennms simulator and RI successfully.
Thanks a lot for the support!
Best Regards
Suzana Gao
MIT-CME
GD China
HP Enterprise Services Apps
Telephone +86 21 60813397
Fax +86 21 60813951
Mobile +86 21 13801716636
Email yan...@hp...<mailto:Youremail>
Mailing Address
From: Craig Gallen [mailto:gal...@go...] On Behalf Of Craig Gallen (entimoss)
Sent: Monday, May 14, 2012 9:24 AM
To: Flauw, Marc
Cc: Gao, Yan (Suzana, ES-Apps-GD-China-SH); 'Craig Gallen (opennms)'; 'openoss-devel'; Chu, Yong-Jie (Jacky,ES-BAS-China-WH); Jin, Chun-Jia (Kinny J, ES-Apps-GD-China-SH)
Subject: Re: Problems for opennms simulator and RI
Hi,
The OpenNMS iterator should now be working correctly. Alarm mapping file attached. Let me know if it works
Thanks
craig
On 10/05/2012 08:56, Flauw, Marc wrote:
Hi Suzana,
Please post on the community site, so that other people would know.
I would suggest 2 messages: one for the RI exception and one for the OpenNMS simulator.
Best regards
Marc
From: Gao, Yan (Suzana, ES-Apps-GD-China-SH)
Sent: Thursday, May 10, 2012 9:51 AM
To: Craig Gallen (entimoss)
Cc: 'Craig Gallen (opennms)'; 'openoss-devel'; Flauw, Marc; Chu, Yong-Jie (Jacky,ES-BAS-China-WH); Jin, Chun-Jia (Kinny J, ES-Apps-GD-China-SH)
Subject: Problems for opennms simulator and RI
Hello Craig,
I remembered I have received emails from you that the opennms simulator is available on:
http://152.78.189.89:8086/opennms/RI/services
But I have tried several times and the services could not be found:
"
HTTP ERROR 404
Problem accessing /opennms/RI/services. Reason:
Not Found"
And for RI, I found one iterator exception these days:
When we invoke following request using SOAPUI, one exception returns also:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:alar="http://www.tmforum.org/xml/tip/resource/trouble/alarm" xmlns:iter="http://www.tmforum.org/xml/tip/internal/iterator">
<soapenv:Header/>
<soapenv:Body>
<alar:getNextResourceAlarmIterationRequest xmlns:alar="http://www.tmforum.org/xml/tip/resource/trouble/alarm" xmlns:iter="http://www.tmforum.org/xml/tip/internal/iterator">
<iter:iteratorId>0</iter:iteratorId>
</alar:getNextResourceAlarmIterationRequest>
</soapenv:Body>
</soapenv:Envelope>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<soap:Fault>
<faultcode>soap:Server</faultcode>
<faultstring>ERROR: org.openoss.tip.model.xml.org.tmforum.tip.org.tmforum.tip.resource.trouble.alarm.ResourceAlarmIteratorWsImpl: method getNextResourceAlarmIteration Exception:</faultstring>
</soap:Fault>
</soap:Body>
</soap:Envelope>
Could you check and let us know the reasons? Thanks in advance!
Best Regards
Suzana Gao
MIT-CME
GD China
HP Enterprise Services Apps
Telephone +86 21 60813397
Fax +86 21 60813951
Mobile +86 21 13801716636
Email yan...@hp...<mailto:Youremail>
Mailing Address
|
|
From: Craig G. (opennms) <cg...@op...> - 2012-05-14 01:22:05
|
> OpenNMS configuration for catalyst > > Please find attached some documentation about opennms alarm > configuration for the catalyst. It is an XML file so best viewed in > eclipse or with a text editor. > > 1. I have used the china mobile node definitions > 2. iterators are working > 3. you can set up you own local opennms and install the RAM interface. > I will still need to provide documentation to get it going - but it > takes about 5 minutes after setting up OpenNMS ( can do whole thing in > a morning from scratch on a PC or linux box) > 4. the alarm definitions are still the standard definitions within > OpenNMS. The simulator is simulating complete node outages failures > and these tranlste into standard opennms alarms which are then > published. I will hopefully do some alarm mapping this week to create > alarms for the nodes similar to China Mobile. > > let me know how you get on connecting. > > Hope this helps > > Craig > > > > |
|
From: Craig G. (opennms) <cg...@op...> - 2012-05-14 01:17:45
|
OpenNMS configuration for catalyst Please find attached some documentation about opennms alarm configuration for the catalyst. It is an XML file so best viewed in eclipse or with a text editor. 1. I have used the china mobile node definitions 2. iterators are working 3. you can set up you own local opennms and install the RAM interface. I will still need to provide documentation to get it going - but it takes about 5 minutes after setting up OpenNMS ( can do whole thing in a morning from scratch on a PC or linux box) 4. the alarm definitions are still the standard definitions within OpenNMS. The simulator is simulating complete node outages failures and these tranlste into standard opennms alarms which are then published. I will hopefully do some alarm mapping this week to create alarms for the nodes similar to China Mobile. let me know how you get on connecting. Hope this helps Craig |
|
From: <cg...@op...> - 2012-05-10 10:27:00
|
Hi Yes there appears to be an intermittent problem with the iterator code. This is caused by the Spring application context not always finding the IteratorManager EJB ( Quite strange). This is an intermittent problem. I spent yesterday looking at it and will continue tonight. I have restarted the RI and seems to work OK now http://152.78.189.89:8084/RI/services I have disabled the iterator code on OpenNMS so that you just get a single complete alarm list for now http://152.78.189.89:8086/RI/services Please also copy questions to the openoss-devel list so we have a record thanks (sign up at http://sourceforge.net/mail/?group_id=122678) Thanks for trying to connect to the RI. it will really help in getting the code more useful Craig From: MW12 Alarm Management for Converged Networks [mailto:mw1...@co...] On Behalf Of Yan Gao Sent: 10 May 2012 09:44 To: cg...@op... Subject: [MW12 Alarm Management for Converged Networks] Problem for RI iterator [#172395] Yan Gao , Solution Architect , Hewlett-Packard Hi Craig, We found one exception when invoke request to RI iterator today: When we invoke following request using SOAPUI, one exception returns: <soapenv:Envelope xmlns:soapenv=" <http://schemas.xmlsoap.org/soap/envelope/> http://schemas.xmlsoap.org/soap/envelope/" xmlns:alar=" <http://www.tmforum.org/xml/tip/resource/trouble/alarm> http://www.tmforum.org/xml/tip/resource/trouble/alarm" xmlns:iter=" <http://www.tmforum.org/xml/tip/internal/iterator> http://www.tmforum.org/xml/tip/internal/iterator"> <soapenv:Header/> <soapenv:Body> <alar:getNextResourceAlarmIterationRequest xmlns:alar=" <http://www.tmforum.org/xml/tip/resource/trouble/alarm> http://www.tmforum.org/xml/tip/resource/trouble/alarm" xmlns:iter=" <http://www.tmforum.org/xml/tip/internal/iterator> http://www.tmforum.org/xml/tip/internal/iterator"> <iter:iteratorId>1742734339</iter:iteratorId> </alar:getNextResourceAlarmIterationRequest> </soapenv:Body> </soapenv:Envelope> Response: <soap:Envelope xmlns:soap=" <http://schemas.xmlsoap.org/soap/envelope/> http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <soap:Fault> <faultcode>soap:Server</faultcode> <faultstring>ERROR: org.openoss.tip.model.xml.org.tmforum.tip.org.tmforum.tip.resource.trouble.alarm.ResourceAlarmIteratorWsImpl: method getNextResourceAlarmIteration Exception:</faultstring> </soap:Fault> </soap:Body> </soap:Envelope> Could you check and let us know the reasons? Thanks in advance! Best Regards, Suzana. MW12 Alarm Management for Converged Networks Topics:Catalysts, general <http://www.tmforum.org/community/groups/mw11-resource-alarm-management-interface/forum/p/172395/200289.aspx?utm_campaign=community&utm_medium=mw11-resource-alarm-management-interface&utm_source=alert#200289?utm_campaign=community&utm_medium=MW12Alarm Management for Converged Networks&utm_source=alert> View thread online Full thread available online here: http://www.tmforum.org/community/groups/mw11-resource-alarm-management-interface/forum/p/172395/200289.aspx?utm_campaign=community <http://www.tmforum.org/community/groups/mw11-resource-alarm-management-interface/forum/p/172395/200289.aspx?utm_campaign=community&utm_medium=mw11-resource-alarm-management-interface&utm_source=alert#200289?utm_campaign=community&utm_medium=MW12Alarm Management for Converged Networks&utm_source=alert> &utm_medium=mw11-resource-alarm-management-interface&utm_source=alert#200289 This message was sent to cg...@op... and follows the subscription preferences of your membership of the MW12 Alarm Management for Converged Networks TM Forum Online Community. To unsubscribe immediately, please click here <http://www.tmforum.org/browse.aspx?type=3&action=9> and click "Edit Collaboration Community Notifications". You will be prompted to log in if you are not logged in already. To cut down on email volume, you may also choose to receive your discussion notifications via a daily or weekly digest email as opposed to immediate separate emails. TM Forum, 240 Headquarters Plaza, East Tower, 10th Floor, Morristown, NJ 07960-6628, USA. Call +1 973 944 5100. in...@tm... <http://www.tmforum.org/csemails/emailtrack10650257.gif> |
|
From: Flauw, M. <Mar...@hp...> - 2012-05-10 07:57:13
|
Hi Suzana,
Please post on the community site, so that other people would know.
I would suggest 2 messages: one for the RI exception and one for the OpenNMS simulator.
Best regards
Marc
From: Gao, Yan (Suzana, ES-Apps-GD-China-SH)
Sent: Thursday, May 10, 2012 9:51 AM
To: Craig Gallen (entimoss)
Cc: 'Craig Gallen (opennms)'; 'openoss-devel'; Flauw, Marc; Chu, Yong-Jie (Jacky,ES-BAS-China-WH); Jin, Chun-Jia (Kinny J, ES-Apps-GD-China-SH)
Subject: Problems for opennms simulator and RI
Hello Craig,
I remembered I have received emails from you that the opennms simulator is available on:
http://152.78.189.89:8086/opennms/RI/services
But I have tried several times and the services could not be found:
"
HTTP ERROR 404
Problem accessing /opennms/RI/services. Reason:
Not Found"
And for RI, I found one iterator exception these days:
When we invoke following request using SOAPUI, one exception returns also:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:alar="http://www.tmforum.org/xml/tip/resource/trouble/alarm" xmlns:iter="http://www.tmforum.org/xml/tip/internal/iterator">
<soapenv:Header/>
<soapenv:Body>
<alar:getNextResourceAlarmIterationRequest xmlns:alar="http://www.tmforum.org/xml/tip/resource/trouble/alarm" xmlns:iter="http://www.tmforum.org/xml/tip/internal/iterator">
<iter:iteratorId>0</iter:iteratorId>
</alar:getNextResourceAlarmIterationRequest>
</soapenv:Body>
</soapenv:Envelope>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<soap:Fault>
<faultcode>soap:Server</faultcode>
<faultstring>ERROR: org.openoss.tip.model.xml.org.tmforum.tip.org.tmforum.tip.resource.trouble.alarm.ResourceAlarmIteratorWsImpl: method getNextResourceAlarmIteration Exception:</faultstring>
</soap:Fault>
</soap:Body>
</soap:Envelope>
Could you check and let us know the reasons? Thanks in advance!
Best Regards
Suzana Gao
MIT-CME
GD China
HP Enterprise Services Apps
Telephone +86 21 60813397
Fax +86 21 60813951
Mobile +86 21 13801716636
Email yan...@hp...<mailto:Youremail>
Mailing Address
|
|
From: Gao, Y. (S. ES-Apps-GD-China-SH) <yan...@hp...> - 2012-05-10 07:51:08
|
Hello Craig,
I remembered I have received emails from you that the opennms simulator is available on:
http://152.78.189.89:8086/opennms/RI/services
But I have tried several times and the services could not be found:
"
HTTP ERROR 404
Problem accessing /opennms/RI/services. Reason:
Not Found"
And for RI, I found one iterator exception these days:
When we invoke following request using SOAPUI, one exception returns also:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:alar="http://www.tmforum.org/xml/tip/resource/trouble/alarm" xmlns:iter="http://www.tmforum.org/xml/tip/internal/iterator">
<soapenv:Header/>
<soapenv:Body>
<alar:getNextResourceAlarmIterationRequest xmlns:alar="http://www.tmforum.org/xml/tip/resource/trouble/alarm" xmlns:iter="http://www.tmforum.org/xml/tip/internal/iterator">
<iter:iteratorId>0</iter:iteratorId>
</alar:getNextResourceAlarmIterationRequest>
</soapenv:Body>
</soapenv:Envelope>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<soap:Fault>
<faultcode>soap:Server</faultcode>
<faultstring>ERROR: org.openoss.tip.model.xml.org.tmforum.tip.org.tmforum.tip.resource.trouble.alarm.ResourceAlarmIteratorWsImpl: method getNextResourceAlarmIteration Exception:</faultstring>
</soap:Fault>
</soap:Body>
</soap:Envelope>
Could you check and let us know the reasons? Thanks in advance!
Best Regards
Suzana Gao
MIT-CME
GD China
HP Enterprise Services Apps
Telephone +86 21 60813397
Fax +86 21 60813951
Mobile +86 21 13801716636
Email yan...@hp...<mailto:Youremail>
Mailing Address
|
|
From: Flauw, M. <Mar...@hp...> - 2012-05-03 08:18:48
|
Dear all,
I tried to build the Common Model IA (without new classes from Job and Schedule) and I git an exception:
[exec] [TIP_Doc_Generator(1.1)Project: org.tmforum.tip.fmk.common version=1.1, Plugin: TIP_Doc_Generator(1.1) version=1.1]
[exec] Error: Unexpected error while merging 'templates/pdfGeneration.vm' template: Invocation of method 'isContainingIAbstractArtifact' in class org.eclipse.tigerstripe.generators.utils.model.ModelHelper threw exception java.lang.IncompatibleClassChangeError: Found interface org.eclipse.tigerstripe.workbench.internal.core.model.ArtifactManager, but class was expected @ templates/pdfGeneration.vm[76,18]. Generation may be incomplete.
[exec] org.eclipse.tigerstripe.workbench.TigerstripeException: Unexpected error while merging 'templates/pdfGeneration.vm' template: Invocation of method 'isContainingIAbstractArtifact' in class org.eclipse.tigerstripe.generators.utils.model.ModelHelper threw exception java.lang.IncompatibleClassChangeError: Found interface org.eclipse.tigerstripe.workbench.internal.core.model.ArtifactManager, but class was expected @ templates/pdfGeneration.vm[76,18]
I created mantis bug 517 for this: https://sourceforge.net/apps/mantisbt/openoss/view.php?id=517
Best regards
Marc
|
|
From: Flauw, M. <Mar...@hp...> - 2012-05-03 08:15:33
|
Dear all,
I tried rebuilding the common model using latest generators.
I am not sure SOAP Generator should be enabled, but it is so far and is giving the following exception:
[TIP_Soap_Generator(1.1)Project: org.tmforum.tip.fmk.common version=1.1, 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[5,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[5,58]
I created mantis bug 516 for this: https://sourceforge.net/apps/mantisbt/openoss/view.php?id=516
Best regards
Marc
|
|
From: Craig G. (opennms) <cg...@op...> - 2012-04-25 09:27:05
|
Hi, After much heartache, working iterator code is now committed to the RAM RI and CTK The RI and CTK have been updated Cheers |
|
From: <sit...@nm...> - 2012-04-17 16:13:31
|
Subject: Date, NA and other errors
From: sit...@nm...
Date: Tue, April 17, 2012 8:43 pm
To: ope...@li...
Priority: Normal
Options: View Full Header | View Printable Version | Download this as
a file
Hi,
I though i will play around with RSA native a bit to get a feel for it
and help me understand when i attempt to get into JOSIF internals.
I took the SID9.5 UML and used RSA to transform it to JAVA.
The transformation completed, however many files were flagged as having
compile errors,
Two of them were,
1. Date was not recognized, its import was absent in many files.
2. ConnectionTerminationPoint.java had a line which read
public TerminationPointConnectionState connectionState = NA;
3. The package names too had capitalization.
Any pointers to get around these would be appreciated.
Thanks
Sitaraman
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
|
|
From: Pierre g. <pie...@os...> - 2012-04-10 12:35:50
|
Do we still have the capabilitu of injecting alarms defined in an XML file ? Regards Pierre Le 2012-04-10 à 6:09, "Craig Gallen (opennms)" <cg...@op...> a écrit : > The RI and CTK code are at > https://collab.tmforum.org/svn/repos/tip/Features/ResourceAlarmManagement/IA/RAM_RI_CTK_Project/trunk/TIP_RAM_CompatibilityTestKit > https://collab.tmforum.org/svn/repos/tip/Features/ResourceAlarmManagement/IA/RAM_RI_CTK_Project/trunk/TIP_RAM_ReferenceImplementation > > The instructions are in notes.txt in the RI and CTK respectively. Should be fairly simple to get going. > Note that you need to have built the TIP_RAM_BaseProject first for these to build. > > Cheers > Craig > > On 09/04/2012 22:28, Pierre gauthier wrote: >> Hi Craig, >> >> Are we still using an Alarm Simulator for the RI ? Where can we find instructions on usig it ? >> >> Pierre |
|
From: Craig G. (opennms) <cg...@op...> - 2012-04-10 11:10:01
|
The RI and CTK code are at https://collab.tmforum.org/svn/repos/tip/Features/ResourceAlarmManagement/IA/RAM_RI_CTK_Project/trunk/TIP_RAM_CompatibilityTestKit https://collab.tmforum.org/svn/repos/tip/Features/ResourceAlarmManagement/IA/RAM_RI_CTK_Project/trunk/TIP_RAM_ReferenceImplementation The instructions are in notes.txt in the RI and CTK respectively. Should be fairly simple to get going. Note that you need to have built the TIP_RAM_BaseProject first for these to build. Cheers Craig On 09/04/2012 22:28, Pierre gauthier wrote: > Hi Craig, > > Are we still using an Alarm Simulator for the RI ? Where can we find instructions on usig it ? > > Pierre |
|
From: Flauw, M. <Mar...@hp...> - 2012-04-07 14:15:03
|
Steve, The inventory query pattern is for the Inventory team to decide, but to make it a common pattern in JOSIF would require at least that it get reviewed in SII team. Best regards Marc From: S Fratini [mailto:sfr...@gm...] Sent: Saturday, April 07, 2012 12:38 AM To: Flauw, Marc Cc: cg...@op...; Zhang, Jin-Zhai (ES-Best-Shore-Services-China-SH); ope...@li... Subject: Re: [Openoss-devel] GoToMeeting Invitation - Josif Onramp - 05 April 2012 at 13:00 GMT Daylight Time Marc The Query pattern is for the Inventory team to decide. Maybe we should talk on this. One could make the case that all common patterns belong on the SII team. Also, Pierre has created an IA and IIS for Query pattern. Steve On Wed, Apr 4, 2012 at 1:24 AM, Flauw, Marc <Mar...@hp...<mailto:Mar...@hp...>> wrote: Steve, The Query pattern might be finalized by the Inventory team, but it is not agreed yet in SII team, and of course not implemented yet. Best regards Marc From: S Fratini [mailto:sfr...@gm...<mailto:sfr...@gm...>] Sent: Tuesday, April 03, 2012 8:49 PM To: cg...@op...<mailto:cg...@op...> Cc: Flauw, Marc; Zhang, Jin-Zhai (ES-Best-Shore-Services-China-SH); ope...@li...<mailto:ope...@li...> Subject: Re: [Openoss-devel] GoToMeeting Invitation - Josif Onramp - 05 April 2012 at 13:00 GMT Daylight Time Craig and All, Somewhat related ... Now that we have define the Query pattern on the Inventory team and have started work on the Update pattern, I plan to restart the Expedited Interfaces work where we apply the various JOSIF patterns to parts of the SID model that are not yet covered by standard interfaces. Will discuss on the TIP Technical Coordination call tomorrow (11 AM US Eastern). Steve On Tue, Apr 3, 2012 at 5:13 AM, <cg...@op...<mailto:cg...@op...>> wrote: Folks, sorry for confusion The next session is on Thursday NOT Friday The last training session on SID import has been posted http://sourceforge.net/projects/openoss/files/JOSIF/DeveloperOnRamp/JOSIF_Developer_On_Ramp_SID_Import_Monday2012-04-02.wmv/download 1. Please join my meeting, 05 April 2012 at 13:00 GMT Daylight Time. https://www3.gotomeeting.com/join/690598054 2. Use your microphone and speakers (VoIP) - a headset is recommended. Or, call in using your telephone. Australia: +61 (0) 2 9037 1944<tel:%2B61%20%280%29%202%209037%201944> Austria: +43 (0) 7 2088 0034<tel:%2B43%20%280%29%207%202088%200034> Belgium: +32 (0) 28 08 9321<tel:%2B32%20%280%29%2028%2008%209321> Canada: +1 (647) 977-5956<tel:%2B1%20%28647%29%20977-5956> Denmark: +45 (0) 69 91 80 05 Finland: +358 (0) 931 58 1746<tel:%2B358%20%280%29%20931%2058%201746> France: +33 (0) 182 880 780<tel:%2B33%20%280%29%20182%20880%20780> Germany: +49 (0) 892 2061 159<tel:%2B49%20%280%29%20892%202061%20159> Ireland: +353 (0) 15 290 180<tel:%2B353%20%280%29%2015%20290%20180> Italy: +39 0 699 26 68 58<tel:%2B39%200%20699%2026%2068%2058> Netherlands: +31 (0) 208 908 267<tel:%2B31%20%280%29%20208%20908%20267> New Zealand: +64 (0) 9 442 7358<tel:%2B64%20%280%29%209%20442%207358> Norway: +47 21 54 32 44<tel:%2B47%2021%2054%2032%2044> Spain: +34 911 23 0850<tel:%2B34%20911%2023%200850> Sweden: +46 (0) 852 500 612<tel:%2B46%20%280%29%20852%20500%20612> Switzerland: +41 (0) 435 0006 96<tel:%2B41%20%280%29%20435%200006%2096> United Kingdom: +44 (0) 203 535 0611<tel:%2B44%20%280%29%20203%20535%200611> United States: +1 (773) 945-1031<tel:%2B1%20%28773%29%20945-1031> Access Code: 690-598-054 Audio PIN: Shown after joining the meeting Meeting ID: 690-598-054 GoToMeeting® Online Meetings Made Easy™ ------------------------------------------------------------------------------ Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev _______________________________________________ Openoss-devel mailing list Ope...@li...<mailto:Ope...@li...> https://lists.sourceforge.net/lists/listinfo/openoss-devel -- Steve |
|
From: S F. <sfr...@gm...> - 2012-04-06 22:38:19
|
Marc The Query pattern is for the Inventory team to decide. Maybe we should talk on this. One could make the case that all common patterns belong on the SII team. Also, Pierre has created an IA and IIS for Query pattern. Steve On Wed, Apr 4, 2012 at 1:24 AM, Flauw, Marc <Mar...@hp...> wrote: > Steve,**** > > ** ** > > The Query pattern might be finalized by the Inventory team, but it is not > agreed yet in SII team, and of course not implemented yet. **** > > ** ** > > Best regards**** > > ** ** > > Marc**** > > ** ** > > *From:* S Fratini [mailto:sfr...@gm...] > *Sent:* Tuesday, April 03, 2012 8:49 PM > *To:* cg...@op... > *Cc:* Flauw, Marc; Zhang, Jin-Zhai (ES-Best-Shore-Services-China-SH); > ope...@li... > *Subject:* Re: [Openoss-devel] GoToMeeting Invitation - Josif Onramp - 05 > April 2012 at 13:00 GMT Daylight Time**** > > ** ** > > Craig and All, **** > > ** ** > > Somewhat related ...**** > > ** ** > > Now that we have define the Query pattern on the Inventory team and have > started work on the Update pattern, I plan to restart the Expedited > Interfaces work where we apply the various JOSIF patterns to parts of the > SID model that are not yet covered by standard interfaces. Will discuss on > the TIP Technical Coordination call tomorrow (11 AM US Eastern). **** > > ** ** > > Steve**** > > ** ** > > ** ** > > On Tue, Apr 3, 2012 at 5:13 AM, <cg...@op...> wrote:**** > > Folks,**** > > **** > > sorry for confusion The next session is on Thursday NOT Friday**** > > **** > > The last training session on SID import has been posted > http://sourceforge.net/projects/openoss/files/JOSIF/DeveloperOnRamp/JOSIF_Developer_On_Ramp_SID_Import_Monday2012-04-02.wmv/download > **** > > **** > > 1. Please join my meeting, 05 April 2012 at 13:00 GMT Daylight Time. > https://www3.gotomeeting.com/join/690598054 **** > > 2. Use your microphone and speakers (VoIP) - a headset is recommended. > Or, call in using your telephone. **** > > Australia: +61 (0) 2 9037 1944 > Austria: +43 (0) 7 2088 0034 > Belgium: +32 (0) 28 08 9321 > Canada: +1 (647) 977-5956 > Denmark: +45 (0) 69 91 80 05 > Finland: +358 (0) 931 58 1746 > France: +33 (0) 182 880 780 > Germany: +49 (0) 892 2061 159 > Ireland: +353 (0) 15 290 180 > Italy: +39 0 699 26 68 58 > Netherlands: +31 (0) 208 908 267 > New Zealand: +64 (0) 9 442 7358 > Norway: +47 21 54 32 44 > Spain: +34 911 23 0850 > Sweden: +46 (0) 852 500 612 > Switzerland: +41 (0) 435 0006 96 > United Kingdom: +44 (0) 203 535 0611 > United States: +1 (773) 945-1031 **** > > Access Code: 690-598-054 > Audio PIN: Shown after joining the meeting **** > > Meeting ID: 690-598-054 **** > > GoToMeeting® > Online Meetings Made Easy™ **** > > > > ------------------------------------------------------------------------------ > Better than sec? Nothing is better than sec when it comes to > monitoring Big Data applications. Try Boundary one-second > resolution app monitoring today. Free. > http://p.sf.net/sfu/Boundary-dev2dev > _______________________________________________ > Openoss-devel mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openoss-devel**** > > ** ** > -- Steve |
|
From: Flauw, M. <Mar...@hp...> - 2012-04-04 05:25:50
|
Steve, The Query pattern might be finalized by the Inventory team, but it is not agreed yet in SII team, and of course not implemented yet. Best regards Marc From: S Fratini [mailto:sfr...@gm...] Sent: Tuesday, April 03, 2012 8:49 PM To: cg...@op... Cc: Flauw, Marc; Zhang, Jin-Zhai (ES-Best-Shore-Services-China-SH); ope...@li... Subject: Re: [Openoss-devel] GoToMeeting Invitation - Josif Onramp - 05 April 2012 at 13:00 GMT Daylight Time Craig and All, Somewhat related ... Now that we have define the Query pattern on the Inventory team and have started work on the Update pattern, I plan to restart the Expedited Interfaces work where we apply the various JOSIF patterns to parts of the SID model that are not yet covered by standard interfaces. Will discuss on the TIP Technical Coordination call tomorrow (11 AM US Eastern). Steve On Tue, Apr 3, 2012 at 5:13 AM, <cg...@op...<mailto:cg...@op...>> wrote: Folks, sorry for confusion The next session is on Thursday NOT Friday The last training session on SID import has been posted http://sourceforge.net/projects/openoss/files/JOSIF/DeveloperOnRamp/JOSIF_Developer_On_Ramp_SID_Import_Monday2012-04-02.wmv/download 1. Please join my meeting, 05 April 2012 at 13:00 GMT Daylight Time. https://www3.gotomeeting.com/join/690598054 2. Use your microphone and speakers (VoIP) - a headset is recommended. Or, call in using your telephone. Australia: +61 (0) 2 9037 1944<tel:%2B61%20%280%29%202%209037%201944> Austria: +43 (0) 7 2088 0034<tel:%2B43%20%280%29%207%202088%200034> Belgium: +32 (0) 28 08 9321<tel:%2B32%20%280%29%2028%2008%209321> Canada: +1 (647) 977-5956<tel:%2B1%20%28647%29%20977-5956> Denmark: +45 (0) 69 91 80 05 Finland: +358 (0) 931 58 1746<tel:%2B358%20%280%29%20931%2058%201746> France: +33 (0) 182 880 780<tel:%2B33%20%280%29%20182%20880%20780> Germany: +49 (0) 892 2061 159<tel:%2B49%20%280%29%20892%202061%20159> Ireland: +353 (0) 15 290 180<tel:%2B353%20%280%29%2015%20290%20180> Italy: +39 0 699 26 68 58<tel:%2B39%200%20699%2026%2068%2058> Netherlands: +31 (0) 208 908 267<tel:%2B31%20%280%29%20208%20908%20267> New Zealand: +64 (0) 9 442 7358<tel:%2B64%20%280%29%209%20442%207358> Norway: +47 21 54 32 44<tel:%2B47%2021%2054%2032%2044> Spain: +34 911 23 0850<tel:%2B34%20911%2023%200850> Sweden: +46 (0) 852 500 612<tel:%2B46%20%280%29%20852%20500%20612> Switzerland: +41 (0) 435 0006 96<tel:%2B41%20%280%29%20435%200006%2096> United Kingdom: +44 (0) 203 535 0611<tel:%2B44%20%280%29%20203%20535%200611> United States: +1 (773) 945-1031<tel:%2B1%20%28773%29%20945-1031> Access Code: 690-598-054 Audio PIN: Shown after joining the meeting Meeting ID: 690-598-054 GoToMeeting® Online Meetings Made Easy™ ------------------------------------------------------------------------------ Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev _______________________________________________ Openoss-devel mailing list Ope...@li...<mailto:Ope...@li...> https://lists.sourceforge.net/lists/listinfo/openoss-devel |
|
From: S F. <sfr...@gm...> - 2012-04-03 18:49:06
|
Craig and All, Somewhat related ... Now that we have define the Query pattern on the Inventory team and have started work on the Update pattern, I plan to restart the Expedited Interfaces work where we apply the various JOSIF patterns to parts of the SID model that are not yet covered by standard interfaces. Will discuss on the TIP Technical Coordination call tomorrow (11 AM US Eastern). Steve On Tue, Apr 3, 2012 at 5:13 AM, <cg...@op...> wrote: > Folks,**** > > ** ** > > sorry for confusion The next session is on Thursday NOT Friday**** > > ** ** > > The last training session on SID import has been posted > http://sourceforge.net/projects/openoss/files/JOSIF/DeveloperOnRamp/JOSIF_Developer_On_Ramp_SID_Import_Monday2012-04-02.wmv/download > **** > > ** ** > > 1. Please join my meeting, 05 April 2012 at 13:00 GMT Daylight Time. > https://www3.gotomeeting.com/join/690598054 **** > > 2. Use your microphone and speakers (VoIP) - a headset is recommended. > Or, call in using your telephone. **** > > Australia: +61 (0) 2 9037 1944 > Austria: +43 (0) 7 2088 0034 > Belgium: +32 (0) 28 08 9321 > Canada: +1 (647) 977-5956 > Denmark: +45 (0) 69 91 80 05 > Finland: +358 (0) 931 58 1746 > France: +33 (0) 182 880 780 > Germany: +49 (0) 892 2061 159 > Ireland: +353 (0) 15 290 180 > Italy: +39 0 699 26 68 58 > Netherlands: +31 (0) 208 908 267 > New Zealand: +64 (0) 9 442 7358 > Norway: +47 21 54 32 44 > Spain: +34 911 23 0850 > Sweden: +46 (0) 852 500 612 > Switzerland: +41 (0) 435 0006 96 > United Kingdom: +44 (0) 203 535 0611 > United States: +1 (773) 945-1031 **** > > Access Code: 690-598-054 > Audio PIN: Shown after joining the meeting **** > > Meeting ID: 690-598-054 **** > > GoToMeeting® > Online Meetings Made Easy™ **** > > > ------------------------------------------------------------------------------ > Better than sec? Nothing is better than sec when it comes to > monitoring Big Data applications. Try Boundary one-second > resolution app monitoring today. Free. > http://p.sf.net/sfu/Boundary-dev2dev > _______________________________________________ > Openoss-devel mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openoss-devel > > |
|
From: <cg...@op...> - 2012-04-03 09:13:22
|
Folks, sorry for confusion The next session is on Thursday NOT Friday The last training session on SID import has been posted http://sourceforge.net/projects/openoss/files/JOSIF/DeveloperOnRamp/JOSIF_De veloper_On_Ramp_SID_Import_Monday2012-04-02.wmv/download 1. Please join my meeting, 05 April 2012 at 13:00 GMT Daylight Time. https://www3.gotomeeting.com/join/690598054 2. Use your microphone and speakers (VoIP) - a headset is recommended. Or, call in using your telephone. Australia: +61 (0) 2 9037 1944 Austria: +43 (0) 7 2088 0034 Belgium: +32 (0) 28 08 9321 Canada: +1 (647) 977-5956 Denmark: +45 (0) 69 91 80 05 Finland: +358 (0) 931 58 1746 France: +33 (0) 182 880 780 Germany: +49 (0) 892 2061 159 Ireland: +353 (0) 15 290 180 Italy: +39 0 699 26 68 58 Netherlands: +31 (0) 208 908 267 New Zealand: +64 (0) 9 442 7358 Norway: +47 21 54 32 44 Spain: +34 911 23 0850 Sweden: +46 (0) 852 500 612 Switzerland: +41 (0) 435 0006 96 United Kingdom: +44 (0) 203 535 0611 United States: +1 (773) 945-1031 Access Code: 690-598-054 Audio PIN: Shown after joining the meeting Meeting ID: 690-598-054 GoToMeetingR Online Meetings Made EasyT |
|
From: Xose R. S. V. <xr...@op...> - 2012-03-21 11:53:50
|
I have performed the check in of the changes in the repository Regards El 21/03/2012 12:14, Xose Ramon Sousa Vazquez escribió: > Ok I will checkin in the trunk project at: > https://openoss.svn.sourceforge.net/svnroot/openoss/tip/framework/TIP_Soap_Generator/trunk/TIP_Soap_Generator > and > the TIP_Soap_Generator-1.1_temp.zip at : > https://openoss.svn.sourceforge.net/svnroot/openoss/tip/framework/TIP_Soap_Generator/trunk/TIP_Soap_Generator_Package/src/main/resources > > > Thanks Craig > Regards > > > El 21/03/2012 10:03, Craig Gallen (opennms) escribió: >> Hi, >> >> RELEASE_1_1_1 shouldn't be touched now. We will fix bugs in the 1.1.2 >> release. >> >> The trunk version of the JOSIF framework is numbered >> RELEASE_1_1_2-SNAPSHOT. This will be released around the time of >> management world. please apply updates here. >> >> The trunk version of the RAM project uses RELEASE_1_1_2-SNAPSHOT >> framework i.e. it uses the trunk version of the generators >> >> Just update the soap generator in the trunk project. People should >> know to checkout and use this version if they are working on the >> latest version of tip >> >> You should also package up the soap generator as >> TIP_Soap_Generator-1.1_temp.zip and replace the copy in the >> TIP_Soap_Generator_Package project at >> https://openoss.svn.sourceforge.net/svnroot/openoss/tip/framework/TIP_Soap_Generator/trunk/TIP_Soap_Generator_Package/src/main/resources >> >> Ping me on skype if this is not clear >> >> Thanks >> >> Craig >> >> >> On 21/03/2012 08:50, Xose Ramon Sousa Vazquez wrote: >>> Ok Craig, two small details to perform the checkin: >>> >>> * I can upload the changes to this location, but is this the >>> location from the RAM project is going to get the generators in >>> the build? >>> * How the releases of the Josif Installer will be affected, must >>> we update from the trunk the tag >>> https://openoss.svn.sourceforge.net/svnroot/openoss/tip/framework/TIP_Soap_Generator/tags/RELEASE_1_1_1/? >>> >>> Thanks for your time Craig >>> >>> Best regards >>> >>> >>> El 21/03/2012 9:25, Craig Gallen (entimoss) escribió: >>>> xose, >>>> >>>> sorry, I thought you needed the RAM location. The soap generator is at >>>> https://openoss.svn.sourceforge.net/svnroot/openoss/tip/framework/TIP_Soap_Generator/trunk/TIP_Soap_Generator >>>> >>>> to find other things - for an explanation of the repository layout >>>> please see >>>> http://sourceforge.net/apps/mediawiki/openoss/index.php?title=Project_Structure >>>> its a little out of date but the overall structure hasn't changed >>>> >>>> Thanks for your help >>>> >>>> Craig >>>> >>>> On 21/03/2012 06:24, Xose Ramon Sousa Vazquez wrote: >>>>> I found the problem in a wrapper in the generator that don't >>>>> initialize the dependecies, so the dep prefix was not included. >>>>> >>>>> >>>>> >>>>> I can checkin the code, but in the svn path that you give me there >>>>> is no SOAPGenerator there. Must I chechin to another path and then >>>>> the maven get the implementation? >>>>> >>>>> Regards >>>>> El 16/03/2012 12:36, Xose Ramon Sousa Vazquez escribió: >>>>>> It seems that the closure is not bypassed because of the filters >>>>>> associated with the rules. I have tested and only the tracking >>>>>> record iterator is generated. In this review I have found that in >>>>>> the schema the name used to import is >>>>>> _cbe_problem_trackingrecorditerator_msg.xsd and the new file >>>>>> generated is dep_cbe_problem_trackingrecorditerator_msg.xsd. We >>>>>> are evaluating it to solve this new issue >>>>>> >>>>>> >>>>>> Best regards >>>>>> El 16/03/2012 9:56, Craig Gallen escribió: >>>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> Thanks for looking at this. the svn path for the trunk of the >>>>>>> ram project is. >>>>>>> >>>>>>> https://collab.tmforum.org/svn/repos/tip/Features/ResourceAlarmManagement/IA/Interface/trunk >>>>>>> >>>>>>> >>>>>>> Are you sure that including artefacts from dependencies and >>>>>>> referenced projects will not bypass the closure mechanism and >>>>>>> cause the plugin to generate all of the artefacts in the >>>>>>> dependencies model? >>>>>>> >>>>>>> Craig >>>>>>> >>>>>>> *From:*Xose Ramon Sousa Vazquez >>>>>>> [mailto:xr...@op...] >>>>>>> *Sent:* 15 March 2012 18:20 >>>>>>> *To:* Craig Gallen (opennms) >>>>>>> *Cc:* openoss-devel; pierre gauthier; Flauw, Marc >>>>>>> *Subject:* Re: Problems - no Tracking Record iterator wsdl >>>>>>> >>>>>>> Hi, I have analyzed the project and the SOAP Generator code and >>>>>>> seems that the problem is related with the parametrization of >>>>>>> the rules used in SOAPGenerator. >>>>>>> When you create the plugin (or generator), in the ts-plugin.xml >>>>>>> file select the Rules tab. There are defined several rules. Two >>>>>>> of them related with this generator or plugin >>>>>>> (Xsd_IteratorServiceMsg and Wsdl_IteratorService_Ws related) >>>>>>> have unchecked the option*Includes artifacts from dependences >>>>>>> and referenced projects*. As the tracking records are included >>>>>>> as dependencies, the iterator is not generated. >>>>>>> >>>>>>> >>>>>>> I think that this is the cause of the problem. If you want I can >>>>>>> checkin the*ts-plugin.xml* file with the changes, but I am not >>>>>>> sure about which svn path must be used. >>>>>>> >>>>>>> >>>>>>> Best regards >>>>>>> El 14/03/2012 12:06, Craig Gallen (opennms) escribió: >>>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> the location of the ram project is >>>>>>> https://collab.tmforum.org/svn/repos/tip/Features/ResourceAlarmManagement/IA/Interface/trunk >>>>>>> >>>>>>> >>>>>>> The model and dependency projects are in this location. >>>>>>> >>>>>>> there are no log files produced when I run a generate from eclipse >>>>>>> >>>>>>> The problem is that the trackingrecorditerator.wsdl is not >>>>>>> generated even though the resourcealarmiterator.wsdl is >>>>>>> generated. The stereotypes are the same on the respective >>>>>>> operations >>>>>>> >>>>>>> Craig >>>>>>> >>>>>>> >>>>>>> On 13/03/2012 11:48, Xose Ramón Sousa wrote: >>>>>>> >>>>>>> Craig I have taken the files from the spec of Ram but I only can >>>>>>> get >>>>>>> the model exported. >>>>>>> Please could you give me the location to download the project to >>>>>>> review it >>>>>>> >>>>>>> Also you can send me the log files stored in the target directory >>>>>>> >>>>>>> Regards >>>>>>> >>>>>>> Enviado desde mi iPhone >>>>>>> >>>>>>> El 12/03/2012, a las 12:19, "Craig Gallen (opennms)" >>>>>>> <cg...@op...> <mailto:cg...@op...> escribió: >>>>>>> >>>>>>> >>>>>>> Hi, >>>>>>> Quick question. >>>>>>> In the RAM model ResourceAlarmRetrievalService we have two >>>>>>> operations which have identical stereotypes to return iterators; >>>>>>> getResourceAlarms() and getTrackingRecords() >>>>>>> both operations state bulk transfer pattern is an iterator >>>>>>> however only getResourceAlarms() generates an additional >>>>>>> iterator wsdl file >>>>>>> >>>>>>> Where is the tracking record iterator wsdl service defined? >>>>>>> >>>>>>> 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> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> >>>>>> *Xose Ramon Sousa Vazquez* | Director OSS Technologies, Director I+D >>>>>> T/ + 34 986 410 091 (ext) 206 | M/ +34 675 550 029 >>>>>> www.optaresolutions.com >>>>>> <http://www.optaresolutions.com> >>>>>> Optare Solutions >>>>>> <http://optarecoolvendor.com><http://optarecoolvendor.com> >>>>>> >>>>> >>>>> >>>>> -- >>>>> >>>>> *Xose Ramon Sousa Vazquez* | Director OSS Technologies, Director I+D >>>>> T/ + 34 986 410 091 (ext) 206 | M/ +34 675 550 029 >>>>> www.optaresolutions.com >>>>> <http://www.optaresolutions.com> >>>>> Optare Solutions >>>>> <http://optarecoolvendor.com><http://optarecoolvendor.com> >>>>> >>> >>> >>> -- >>> >>> *Xose Ramon Sousa Vazquez* | Director OSS Technologies, Director I+D >>> T/ + 34 986 410 091 (ext) 206 | M/ +34 675 550 029 >>> www.optaresolutions.com >>> <http://www.optaresolutions.com> >>> Optare Solutions >>> <http://optarecoolvendor.com><http://optarecoolvendor.com> >>> > > > -- > > *Xose Ramon Sousa Vazquez* | Director OSS Technologies, Director I+D > T/ + 34 986 410 091 (ext) 206 | M/ +34 675 550 029 > www.optaresolutions.com > <http://www.optaresolutions.com> > Optare Solutions > <http://optarecoolvendor.com><http://optarecoolvendor.com> > -- *Xose Ramon Sousa Vazquez* | Director OSS Technologies, Director I+D T/ + 34 986 410 091 (ext) 206 | M/ +34 675 550 029 www.optaresolutions.com <http://www.optaresolutions.com> Optare Solutions <http://optarecoolvendor.com><http://optarecoolvendor.com> |
|
From: Xose R. S. V. <xr...@op...> - 2012-03-21 11:17:54
|
Ok I will checkin in the trunk project at: https://openoss.svn.sourceforge.net/svnroot/openoss/tip/framework/TIP_Soap_Generator/trunk/TIP_Soap_Generator and the TIP_Soap_Generator-1.1_temp.zip at : https://openoss.svn.sourceforge.net/svnroot/openoss/tip/framework/TIP_Soap_Generator/trunk/TIP_Soap_Generator_Package/src/main/resources Thanks Craig Regards El 21/03/2012 10:03, Craig Gallen (opennms) escribió: > Hi, > > RELEASE_1_1_1 shouldn't be touched now. We will fix bugs in the 1.1.2 > release. > > The trunk version of the JOSIF framework is numbered > RELEASE_1_1_2-SNAPSHOT. This will be released around the time of > management world. please apply updates here. > > The trunk version of the RAM project uses RELEASE_1_1_2-SNAPSHOT > framework i.e. it uses the trunk version of the generators > > Just update the soap generator in the trunk project. People should > know to checkout and use this version if they are working on the > latest version of tip > > You should also package up the soap generator as > TIP_Soap_Generator-1.1_temp.zip and replace the copy in the > TIP_Soap_Generator_Package project at > https://openoss.svn.sourceforge.net/svnroot/openoss/tip/framework/TIP_Soap_Generator/trunk/TIP_Soap_Generator_Package/src/main/resources > > Ping me on skype if this is not clear > > Thanks > > Craig > > > On 21/03/2012 08:50, Xose Ramon Sousa Vazquez wrote: >> Ok Craig, two small details to perform the checkin: >> >> * I can upload the changes to this location, but is this the >> location from the RAM project is going to get the generators in >> the build? >> * How the releases of the Josif Installer will be affected, must we >> update from the trunk the tag >> https://openoss.svn.sourceforge.net/svnroot/openoss/tip/framework/TIP_Soap_Generator/tags/RELEASE_1_1_1/? >> >> Thanks for your time Craig >> >> Best regards >> >> >> El 21/03/2012 9:25, Craig Gallen (entimoss) escribió: >>> xose, >>> >>> sorry, I thought you needed the RAM location. The soap generator is at >>> https://openoss.svn.sourceforge.net/svnroot/openoss/tip/framework/TIP_Soap_Generator/trunk/TIP_Soap_Generator >>> >>> to find other things - for an explanation of the repository layout >>> please see >>> http://sourceforge.net/apps/mediawiki/openoss/index.php?title=Project_Structure >>> its a little out of date but the overall structure hasn't changed >>> >>> Thanks for your help >>> >>> Craig >>> >>> On 21/03/2012 06:24, Xose Ramon Sousa Vazquez wrote: >>>> I found the problem in a wrapper in the generator that don't >>>> initialize the dependecies, so the dep prefix was not included. >>>> >>>> >>>> >>>> I can checkin the code, but in the svn path that you give me there >>>> is no SOAPGenerator there. Must I chechin to another path and then >>>> the maven get the implementation? >>>> >>>> Regards >>>> El 16/03/2012 12:36, Xose Ramon Sousa Vazquez escribió: >>>>> It seems that the closure is not bypassed because of the filters >>>>> associated with the rules. I have tested and only the tracking >>>>> record iterator is generated. In this review I have found that in >>>>> the schema the name used to import is >>>>> _cbe_problem_trackingrecorditerator_msg.xsd and the new file >>>>> generated is dep_cbe_problem_trackingrecorditerator_msg.xsd. We >>>>> are evaluating it to solve this new issue >>>>> >>>>> >>>>> Best regards >>>>> El 16/03/2012 9:56, Craig Gallen escribió: >>>>>> >>>>>> Hi, >>>>>> >>>>>> Thanks for looking at this. the svn path for the trunk of the ram >>>>>> project is. >>>>>> >>>>>> https://collab.tmforum.org/svn/repos/tip/Features/ResourceAlarmManagement/IA/Interface/trunk >>>>>> >>>>>> >>>>>> Are you sure that including artefacts from dependencies and >>>>>> referenced projects will not bypass the closure mechanism and >>>>>> cause the plugin to generate all of the artefacts in the >>>>>> dependencies model? >>>>>> >>>>>> Craig >>>>>> >>>>>> *From:*Xose Ramon Sousa Vazquez [mailto:xr...@op...] >>>>>> *Sent:* 15 March 2012 18:20 >>>>>> *To:* Craig Gallen (opennms) >>>>>> *Cc:* openoss-devel; pierre gauthier; Flauw, Marc >>>>>> *Subject:* Re: Problems - no Tracking Record iterator wsdl >>>>>> >>>>>> Hi, I have analyzed the project and the SOAP Generator code and >>>>>> seems that the problem is related with the parametrization of the >>>>>> rules used in SOAPGenerator. >>>>>> When you create the plugin (or generator), in the ts-plugin.xml >>>>>> file select the Rules tab. There are defined several rules. Two >>>>>> of them related with this generator or plugin >>>>>> (Xsd_IteratorServiceMsg and Wsdl_IteratorService_Ws related) have >>>>>> unchecked the option*Includes artifacts from dependences and >>>>>> referenced projects*. As the tracking records are included as >>>>>> dependencies, the iterator is not generated. >>>>>> >>>>>> >>>>>> I think that this is the cause of the problem. If you want I can >>>>>> checkin the*ts-plugin.xml* file with the changes, but I am not >>>>>> sure about which svn path must be used. >>>>>> >>>>>> >>>>>> Best regards >>>>>> El 14/03/2012 12:06, Craig Gallen (opennms) escribió: >>>>>> >>>>>> Hi, >>>>>> >>>>>> the location of the ram project is >>>>>> https://collab.tmforum.org/svn/repos/tip/Features/ResourceAlarmManagement/IA/Interface/trunk >>>>>> >>>>>> >>>>>> The model and dependency projects are in this location. >>>>>> >>>>>> there are no log files produced when I run a generate from eclipse >>>>>> >>>>>> The problem is that the trackingrecorditerator.wsdl is not >>>>>> generated even though the resourcealarmiterator.wsdl is >>>>>> generated. The stereotypes are the same on the respective operations >>>>>> >>>>>> Craig >>>>>> >>>>>> >>>>>> On 13/03/2012 11:48, Xose Ramón Sousa wrote: >>>>>> >>>>>> Craig I have taken the files from the spec of Ram but I only can get >>>>>> the model exported. >>>>>> Please could you give me the location to download the project to >>>>>> review it >>>>>> >>>>>> Also you can send me the log files stored in the target directory >>>>>> >>>>>> Regards >>>>>> >>>>>> Enviado desde mi iPhone >>>>>> >>>>>> El 12/03/2012, a las 12:19, "Craig Gallen (opennms)" >>>>>> <cg...@op...> <mailto:cg...@op...> escribió: >>>>>> >>>>>> >>>>>> Hi, >>>>>> Quick question. >>>>>> In the RAM model ResourceAlarmRetrievalService we have two >>>>>> operations which have identical stereotypes to return iterators; >>>>>> getResourceAlarms() and getTrackingRecords() >>>>>> both operations state bulk transfer pattern is an iterator >>>>>> however only getResourceAlarms() generates an additional iterator >>>>>> wsdl file >>>>>> >>>>>> Where is the tracking record iterator wsdl service defined? >>>>>> >>>>>> 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> >>>>>> >>>>> >>>>> >>>>> -- >>>>> >>>>> *Xose Ramon Sousa Vazquez* | Director OSS Technologies, Director I+D >>>>> T/ + 34 986 410 091 (ext) 206 | M/ +34 675 550 029 >>>>> www.optaresolutions.com >>>>> <http://www.optaresolutions.com> >>>>> Optare Solutions >>>>> <http://optarecoolvendor.com><http://optarecoolvendor.com> >>>>> >>>> >>>> >>>> -- >>>> >>>> *Xose Ramon Sousa Vazquez* | Director OSS Technologies, Director I+D >>>> T/ + 34 986 410 091 (ext) 206 | M/ +34 675 550 029 >>>> www.optaresolutions.com >>>> <http://www.optaresolutions.com> >>>> Optare Solutions >>>> <http://optarecoolvendor.com><http://optarecoolvendor.com> >>>> >> >> >> -- >> >> *Xose Ramon Sousa Vazquez* | Director OSS Technologies, Director I+D >> T/ + 34 986 410 091 (ext) 206 | M/ +34 675 550 029 >> www.optaresolutions.com >> <http://www.optaresolutions.com> >> Optare Solutions >> <http://optarecoolvendor.com><http://optarecoolvendor.com> >> -- *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-03-21 09:04:15
|
Hi, RELEASE_1_1_1 shouldn't be touched now. We will fix bugs in the 1.1.2 release. The trunk version of the JOSIF framework is numbered RELEASE_1_1_2-SNAPSHOT. This will be released around the time of management world. please apply updates here. The trunk version of the RAM project uses RELEASE_1_1_2-SNAPSHOT framework i.e. it uses the trunk version of the generators Just update the soap generator in the trunk project. People should know to checkout and use this version if they are working on the latest version of tip You should also package up the soap generator as TIP_Soap_Generator-1.1_temp.zip and replace the copy in the TIP_Soap_Generator_Package project at https://openoss.svn.sourceforge.net/svnroot/openoss/tip/framework/TIP_Soap_Generator/trunk/TIP_Soap_Generator_Package/src/main/resources Ping me on skype if this is not clear Thanks Craig On 21/03/2012 08:50, Xose Ramon Sousa Vazquez wrote: > Ok Craig, two small details to perform the checkin: > > * I can upload the changes to this location, but is this the > location from the RAM project is going to get the generators in > the build? > * How the releases of the Josif Installer will be affected, must we > update from the trunk the tag > https://openoss.svn.sourceforge.net/svnroot/openoss/tip/framework/TIP_Soap_Generator/tags/RELEASE_1_1_1/? > > Thanks for your time Craig > > Best regards > > > El 21/03/2012 9:25, Craig Gallen (entimoss) escribió: >> xose, >> >> sorry, I thought you needed the RAM location. The soap generator is at >> https://openoss.svn.sourceforge.net/svnroot/openoss/tip/framework/TIP_Soap_Generator/trunk/TIP_Soap_Generator >> >> to find other things - for an explanation of the repository layout >> please see >> http://sourceforge.net/apps/mediawiki/openoss/index.php?title=Project_Structure >> its a little out of date but the overall structure hasn't changed >> >> Thanks for your help >> >> Craig >> >> On 21/03/2012 06:24, Xose Ramon Sousa Vazquez wrote: >>> I found the problem in a wrapper in the generator that don't >>> initialize the dependecies, so the dep prefix was not included. >>> >>> >>> >>> I can checkin the code, but in the svn path that you give me there >>> is no SOAPGenerator there. Must I chechin to another path and then >>> the maven get the implementation? >>> >>> Regards >>> El 16/03/2012 12:36, Xose Ramon Sousa Vazquez escribió: >>>> It seems that the closure is not bypassed because of the filters >>>> associated with the rules. I have tested and only the tracking >>>> record iterator is generated. In this review I have found that in >>>> the schema the name used to import is >>>> _cbe_problem_trackingrecorditerator_msg.xsd and the new file >>>> generated is dep_cbe_problem_trackingrecorditerator_msg.xsd. We are >>>> evaluating it to solve this new issue >>>> >>>> >>>> Best regards >>>> El 16/03/2012 9:56, Craig Gallen escribió: >>>>> >>>>> Hi, >>>>> >>>>> Thanks for looking at this. the svn path for the trunk of the ram >>>>> project is. >>>>> >>>>> https://collab.tmforum.org/svn/repos/tip/Features/ResourceAlarmManagement/IA/Interface/trunk >>>>> >>>>> >>>>> Are you sure that including artefacts from dependencies and >>>>> referenced projects will not bypass the closure mechanism and >>>>> cause the plugin to generate all of the artefacts in the >>>>> dependencies model? >>>>> >>>>> Craig >>>>> >>>>> *From:*Xose Ramon Sousa Vazquez [mailto:xr...@op...] >>>>> *Sent:* 15 March 2012 18:20 >>>>> *To:* Craig Gallen (opennms) >>>>> *Cc:* openoss-devel; pierre gauthier; Flauw, Marc >>>>> *Subject:* Re: Problems - no Tracking Record iterator wsdl >>>>> >>>>> Hi, I have analyzed the project and the SOAP Generator code and >>>>> seems that the problem is related with the parametrization of the >>>>> rules used in SOAPGenerator. >>>>> When you create the plugin (or generator), in the ts-plugin.xml >>>>> file select the Rules tab. There are defined several rules. Two of >>>>> them related with this generator or plugin (Xsd_IteratorServiceMsg >>>>> and Wsdl_IteratorService_Ws related) have unchecked the >>>>> option*Includes artifacts from dependences and referenced >>>>> projects*. As the tracking records are included as dependencies, >>>>> the iterator is not generated. >>>>> >>>>> >>>>> I think that this is the cause of the problem. If you want I can >>>>> checkin the*ts-plugin.xml* file with the changes, but I am not >>>>> sure about which svn path must be used. >>>>> >>>>> >>>>> Best regards >>>>> El 14/03/2012 12:06, Craig Gallen (opennms) escribió: >>>>> >>>>> Hi, >>>>> >>>>> the location of the ram project is >>>>> https://collab.tmforum.org/svn/repos/tip/Features/ResourceAlarmManagement/IA/Interface/trunk >>>>> >>>>> >>>>> The model and dependency projects are in this location. >>>>> >>>>> there are no log files produced when I run a generate from eclipse >>>>> >>>>> The problem is that the trackingrecorditerator.wsdl is not >>>>> generated even though the resourcealarmiterator.wsdl is generated. >>>>> The stereotypes are the same on the respective operations >>>>> >>>>> Craig >>>>> >>>>> >>>>> On 13/03/2012 11:48, Xose Ramón Sousa wrote: >>>>> >>>>> Craig I have taken the files from the spec of Ram but I only can get >>>>> the model exported. >>>>> Please could you give me the location to download the project to >>>>> review it >>>>> >>>>> Also you can send me the log files stored in the target directory >>>>> >>>>> Regards >>>>> >>>>> Enviado desde mi iPhone >>>>> >>>>> El 12/03/2012, a las 12:19, "Craig Gallen (opennms)" >>>>> <cg...@op...> <mailto:cg...@op...> escribió: >>>>> >>>>> >>>>> Hi, >>>>> Quick question. >>>>> In the RAM model ResourceAlarmRetrievalService we have two >>>>> operations which have identical stereotypes to return iterators; >>>>> getResourceAlarms() and getTrackingRecords() >>>>> both operations state bulk transfer pattern is an iterator >>>>> however only getResourceAlarms() generates an additional iterator >>>>> wsdl file >>>>> >>>>> Where is the tracking record iterator wsdl service defined? >>>>> >>>>> 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> >>>>> >>>> >>>> >>>> -- >>>> >>>> *Xose Ramon Sousa Vazquez* | Director OSS Technologies, Director I+D >>>> T/ + 34 986 410 091 (ext) 206 | M/ +34 675 550 029 >>>> www.optaresolutions.com >>>> <http://www.optaresolutions.com> >>>> Optare Solutions >>>> <http://optarecoolvendor.com><http://optarecoolvendor.com> >>>> >>> >>> >>> -- >>> >>> *Xose Ramon Sousa Vazquez* | Director OSS Technologies, Director I+D >>> T/ + 34 986 410 091 (ext) 206 | M/ +34 675 550 029 >>> www.optaresolutions.com >>> <http://www.optaresolutions.com> >>> Optare Solutions >>> <http://optarecoolvendor.com><http://optarecoolvendor.com> >>> > > > -- > > *Xose Ramon Sousa Vazquez* | Director OSS Technologies, Director I+D > T/ + 34 986 410 091 (ext) 206 | M/ +34 675 550 029 > www.optaresolutions.com > <http://www.optaresolutions.com> > Optare Solutions > <http://optarecoolvendor.com><http://optarecoolvendor.com> > |
|
From: Xose R. S. V. <xr...@op...> - 2012-03-21 08:53:03
|
Ok Craig, two small details to perform the checkin:
* I can upload the changes to this location, but is this the location
from the RAM project is going to get the generators in the build?
* How the releases of the Josif Installer will be affected, must we
update from the trunk the tag
https://openoss.svn.sourceforge.net/svnroot/openoss/tip/framework/TIP_Soap_Generator/tags/RELEASE_1_1_1/?
Thanks for your time Craig
Best regards
El 21/03/2012 9:25, Craig Gallen (entimoss) escribió:
> xose,
>
> sorry, I thought you needed the RAM location. The soap generator is at
> https://openoss.svn.sourceforge.net/svnroot/openoss/tip/framework/TIP_Soap_Generator/trunk/TIP_Soap_Generator
>
> to find other things - for an explanation of the repository layout
> please see
> http://sourceforge.net/apps/mediawiki/openoss/index.php?title=Project_Structure
> its a little out of date but the overall structure hasn't changed
>
> Thanks for your help
>
> Craig
>
> On 21/03/2012 06:24, Xose Ramon Sousa Vazquez wrote:
>> I found the problem in a wrapper in the generator that don't
>> initialize the dependecies, so the dep prefix was not included.
>>
>>
>>
>> I can checkin the code, but in the svn path that you give me there is
>> no SOAPGenerator there. Must I chechin to another path and then the
>> maven get the implementation?
>>
>> Regards
>> El 16/03/2012 12:36, Xose Ramon Sousa Vazquez escribió:
>>> It seems that the closure is not bypassed because of the filters
>>> associated with the rules. I have tested and only the tracking
>>> record iterator is generated. In this review I have found that in
>>> the schema the name used to import is
>>> _cbe_problem_trackingrecorditerator_msg.xsd and the new file
>>> generated is dep_cbe_problem_trackingrecorditerator_msg.xsd. We are
>>> evaluating it to solve this new issue
>>>
>>>
>>> Best regards
>>> El 16/03/2012 9:56, Craig Gallen escribió:
>>>>
>>>> Hi,
>>>>
>>>> Thanks for looking at this. the svn path for the trunk of the ram
>>>> project is.
>>>>
>>>> https://collab.tmforum.org/svn/repos/tip/Features/ResourceAlarmManagement/IA/Interface/trunk
>>>>
>>>>
>>>> Are you sure that including artefacts from dependencies and
>>>> referenced projects will not bypass the closure mechanism and cause
>>>> the plugin to generate all of the artefacts in the dependencies model?
>>>>
>>>> Craig
>>>>
>>>> *From:*Xose Ramon Sousa Vazquez [mailto:xr...@op...]
>>>> *Sent:* 15 March 2012 18:20
>>>> *To:* Craig Gallen (opennms)
>>>> *Cc:* openoss-devel; pierre gauthier; Flauw, Marc
>>>> *Subject:* Re: Problems - no Tracking Record iterator wsdl
>>>>
>>>> Hi, I have analyzed the project and the SOAP Generator code and
>>>> seems that the problem is related with the parametrization of the
>>>> rules used in SOAPGenerator.
>>>> When you create the plugin (or generator), in the ts-plugin.xml
>>>> file select the Rules tab. There are defined several rules. Two of
>>>> them related with this generator or plugin (Xsd_IteratorServiceMsg
>>>> and Wsdl_IteratorService_Ws related) have unchecked the
>>>> option*Includes artifacts from dependences and referenced
>>>> projects*. As the tracking records are included as dependencies,
>>>> the iterator is not generated.
>>>>
>>>>
>>>> I think that this is the cause of the problem. If you want I can
>>>> checkin the*ts-plugin.xml* file with the changes, but I am not sure
>>>> about which svn path must be used.
>>>>
>>>>
>>>> Best regards
>>>> El 14/03/2012 12:06, Craig Gallen (opennms) escribió:
>>>>
>>>> Hi,
>>>>
>>>> the location of the ram project is
>>>> https://collab.tmforum.org/svn/repos/tip/Features/ResourceAlarmManagement/IA/Interface/trunk
>>>>
>>>>
>>>> The model and dependency projects are in this location.
>>>>
>>>> there are no log files produced when I run a generate from eclipse
>>>>
>>>> The problem is that the trackingrecorditerator.wsdl is not
>>>> generated even though the resourcealarmiterator.wsdl is generated.
>>>> The stereotypes are the same on the respective operations
>>>>
>>>> Craig
>>>>
>>>>
>>>> On 13/03/2012 11:48, Xose Ramón Sousa wrote:
>>>>
>>>> Craig I have taken the files from the spec of Ram but I only can get
>>>> the model exported.
>>>> Please could you give me the location to download the project to
>>>> review it
>>>>
>>>> Also you can send me the log files stored in the target directory
>>>>
>>>> Regards
>>>>
>>>> Enviado desde mi iPhone
>>>>
>>>> El 12/03/2012, a las 12:19, "Craig Gallen (opennms)"
>>>> <cg...@op...> <mailto:cg...@op...> escribió:
>>>>
>>>>
>>>> Hi,
>>>> Quick question.
>>>> In the RAM model ResourceAlarmRetrievalService we have two
>>>> operations which have identical stereotypes to return iterators;
>>>> getResourceAlarms() and getTrackingRecords()
>>>> both operations state bulk transfer pattern is an iterator
>>>> however only getResourceAlarms() generates an additional iterator
>>>> wsdl file
>>>>
>>>> Where is the tracking record iterator wsdl service defined?
>>>>
>>>> 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>
>>>>
>>>
>>>
>>> --
>>>
>>> *Xose Ramon Sousa Vazquez* | Director OSS Technologies, Director I+D
>>> T/ + 34 986 410 091 (ext) 206 | M/ +34 675 550 029
>>> www.optaresolutions.com
>>> <http://www.optaresolutions.com>
>>> Optare Solutions
>>> <http://optarecoolvendor.com><http://optarecoolvendor.com>
>>>
>>
>>
>> --
>>
>> *Xose Ramon Sousa Vazquez* | Director OSS Technologies, Director I+D
>> T/ + 34 986 410 091 (ext) 206 | M/ +34 675 550 029
>> www.optaresolutions.com
>> <http://www.optaresolutions.com>
>> Optare Solutions
>> <http://optarecoolvendor.com><http://optarecoolvendor.com>
>>
--
*Xose Ramon Sousa Vazquez* | Director OSS Technologies, Director I+D
T/ + 34 986 410 091 (ext) 206 | M/ +34 675 550 029
www.optaresolutions.com
<http://www.optaresolutions.com>
Optare Solutions <http://optarecoolvendor.com><http://optarecoolvendor.com>
|
|
From: Craig G. (opennms) <cg...@op...> - 2012-03-21 08:26:50
|
-------- Original Message -------- Subject: Re: Problems - no Tracking Record iterator wsdl Date: Wed, 21 Mar 2012 08:25:50 +0000 From: Craig Gallen (entimoss) <cra...@en...> Organisation: Entmoss Ltd To: Xose Ramon Sousa Vazquez <xr...@op...> CC: 'Craig Gallen (opennms)' <cg...@op...>, 'openoss-devel' <ope...@li...>, 'pierre gauthier' <pie...@os...>, 'Flauw, Marc' <Mar...@hp...> xose, sorry, I thought you needed the RAM location. The soap generator is at https://openoss.svn.sourceforge.net/svnroot/openoss/tip/framework/TIP_Soap_Generator/trunk/TIP_Soap_Generator to find other things - for an explanation of the repository layout please see http://sourceforge.net/apps/mediawiki/openoss/index.php?title=Project_Structure its a little out of date but the overall structure hasn't changed Thanks for your help Craig On 21/03/2012 06:24, Xose Ramon Sousa Vazquez wrote: > I found the problem in a wrapper in the generator that don't > initialize the dependecies, so the dep prefix was not included. > > > > I can checkin the code, but in the svn path that you give me there is > no SOAPGenerator there. Must I chechin to another path and then the > maven get the implementation? > > Regards > El 16/03/2012 12:36, Xose Ramon Sousa Vazquez escribió: >> It seems that the closure is not bypassed because of the filters >> associated with the rules. I have tested and only the tracking record >> iterator is generated. In this review I have found that in the schema >> the name used to import is >> _cbe_problem_trackingrecorditerator_msg.xsd and the new file >> generated is dep_cbe_problem_trackingrecorditerator_msg.xsd. We are >> evaluating it to solve this new issue >> >> >> Best regards >> El 16/03/2012 9:56, Craig Gallen escribió: >>> >>> Hi, >>> >>> Thanks for looking at this. the svn path for the trunk of the ram >>> project is. >>> >>> https://collab.tmforum.org/svn/repos/tip/Features/ResourceAlarmManagement/IA/Interface/trunk >>> >>> >>> Are you sure that including artefacts from dependencies and >>> referenced projects will not bypass the closure mechanism and cause >>> the plugin to generate all of the artefacts in the dependencies model? >>> >>> Craig >>> >>> *From:*Xose Ramon Sousa Vazquez [mailto:xr...@op...] >>> *Sent:* 15 March 2012 18:20 >>> *To:* Craig Gallen (opennms) >>> *Cc:* openoss-devel; pierre gauthier; Flauw, Marc >>> *Subject:* Re: Problems - no Tracking Record iterator wsdl >>> >>> Hi, I have analyzed the project and the SOAP Generator code and >>> seems that the problem is related with the parametrization of the >>> rules used in SOAPGenerator. >>> When you create the plugin (or generator), in the ts-plugin.xml file >>> select the Rules tab. There are defined several rules. Two of them >>> related with this generator or plugin (Xsd_IteratorServiceMsg and >>> Wsdl_IteratorService_Ws related) have unchecked the option*Includes >>> artifacts from dependences and referenced projects*. As the tracking >>> records are included as dependencies, the iterator is not generated. >>> >>> >>> I think that this is the cause of the problem. If you want I can >>> checkin the*ts-plugin.xml* file with the changes, but I am not sure >>> about which svn path must be used. >>> >>> >>> Best regards >>> El 14/03/2012 12:06, Craig Gallen (opennms) escribió: >>> >>> Hi, >>> >>> the location of the ram project is >>> https://collab.tmforum.org/svn/repos/tip/Features/ResourceAlarmManagement/IA/Interface/trunk >>> >>> >>> The model and dependency projects are in this location. >>> >>> there are no log files produced when I run a generate from eclipse >>> >>> The problem is that the trackingrecorditerator.wsdl is not >>> generated even though the resourcealarmiterator.wsdl is generated. >>> The stereotypes are the same on the respective operations >>> >>> Craig >>> >>> >>> On 13/03/2012 11:48, Xose Ramón Sousa wrote: >>> >>> Craig I have taken the files from the spec of Ram but I only can get >>> the model exported. >>> Please could you give me the location to download the project to >>> review it >>> >>> Also you can send me the log files stored in the target directory >>> >>> Regards >>> >>> Enviado desde mi iPhone >>> >>> El 12/03/2012, a las 12:19, "Craig Gallen (opennms)" >>> <cg...@op...> <mailto:cg...@op...> escribió: >>> >>> >>> Hi, >>> Quick question. >>> In the RAM model ResourceAlarmRetrievalService we have two >>> operations which have identical stereotypes to return iterators; >>> getResourceAlarms() and getTrackingRecords() >>> both operations state bulk transfer pattern is an iterator >>> however only getResourceAlarms() generates an additional iterator >>> wsdl file >>> >>> Where is the tracking record iterator wsdl service defined? >>> >>> 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> >>> >> >> >> -- >> >> *Xose Ramon Sousa Vazquez* | Director OSS Technologies, Director I+D >> T/ + 34 986 410 091 (ext) 206 | M/ +34 675 550 029 >> www.optaresolutions.com >> <http://www.optaresolutions.com> >> Optare Solutions >> <http://optarecoolvendor.com><http://optarecoolvendor.com> >> > > > -- > > *Xose Ramon Sousa Vazquez* | Director OSS Technologies, Director I+D > T/ + 34 986 410 091 (ext) 206 | M/ +34 675 550 029 > www.optaresolutions.com > <http://www.optaresolutions.com> > Optare Solutions > <http://optarecoolvendor.com><http://optarecoolvendor.com> > |
197 messages has been excluded from this view by a project administrator.
