Wow, good diagnosing!

Suppose someone was using IBM Java 7 with Ruta, what kinds of problems would
this cause? 
I presume they would be "undetected" - in that no exception, etc. would happen,
but instead, just some wrong results?

If it is detected, or the undetected wrong results you think would be of no
significant consequence, then I could call this a non-blocker.

Since we've had no complaints about this before (is this right?), I'm guessing
this goes undetected (or no one is using a Java like IBM Java 7).

If the wrong results are significant, I'd call it a blocker...

-Marshall

On 5/9/2017 12:06 PM, Peter Klügl wrote:
> Thanks Marshall.
>
>
> I was able to reproduce the problem. It was caused by the (really really
> old) code of the sax parser handler for reading the mtwl files. Some
> sort of buffering caused two calls of characters() instead of one,
> breaking up the string for the type mapping.
>
>
> It's now fixed in the current trunk.
>
>
> How should be proceed? Blocker or not?
>
>
> Best,
>
>
> Peter
>
>
> Am 08.05.2017 um 16:32 schrieb Marshall Schor:
>> this might work:
>>
>>
>> https://www.ibm.com/developerworks/java/jdk/eclipse/index.html
>>
>> Scroll down to where it says:
>>
>> Download the IBM Development Package for Eclipse, Version 5.0, including IBM
>> SDK, Java Technology Edition, Version 7 Release 1:
>>
>>   * 32-bit Windows
>>     
>> <https://www.ibm.com/services/forms/preLogin.do?source=idpe&S_TACT=105AGX05&S_CMP=JDK&lang=en_US&S_PKG=win32-5.3.1>
>>   * 64-bit Windows
>>     
>> <https://www.ibm.com/services/forms/preLogin.do?source=idpe&S_TACT=105AGX05&S_CMP=JDK&lang=en_US&S_PKG=win64-5.3.1>
>>
>>
>> -Marshall
>>
>> On 5/7/2017 10:49 AM, Peter Klügl wrote:
>>> Looks like finding/downloading IBM Java 7 for windows is not trivial.
>>>
>>>
>>> Peter
>>>
>>>
>>> Am 05.05.2017 um 17:51 schrieb Marshall Schor:
>>>> These things sometimes are artifacts of hash table implementations. 
>>>>
>>>> To reproduce, you might need to run with IBM Java.
>>>>
>>>> If possible, can Burn try with Oracle Java 7?
>>>>
>>>> (set JAVA_HOME to that).
>>>>
>>>> -Marshall
>>>>
>>>>
>>>> On 5/5/2017 2:03 AM, Peter Klügl wrote:
>>>>> Ok that's strange. I know that I changed something in that project
>>>>> because Marshall had problems building it with Java 8 when he tested the
>>>>> v3 compatibility.
>>>>>
>>>>>
>>>>> Here's my env
>>>>>
>>>>> Apache Maven 3.2.5 (12a6b3acb947671f09b81f49094c53f426d8cea1;
>>>>> 2014-12-14T18:29:23+01:00)
>>>>> Maven home: C:\work\misc\apache-maven-3.2.5\bin\..
>>>>> Java version: 1.7.0_75, vendor: Oracle Corporation
>>>>> Java home: C:\Program Files\Java\jdk1.7.0_75\jre
>>>>> Default locale: en_DE, platform encoding: Cp1252
>>>>> OS name: "windows 8.1", version: "6.3", arch: "amd64", family: "windows"
>>>>>
>>>>>
>>>>> I'll try to reproduce it, but I won't be able to do it today :-(
>>>>>
>>>>>
>>>>> Peter
>>>>>
>>>>>
>>>>>
>>>>> Am 05.05.2017 um 00:02 schrieb Burn Lewis:
>>>>>> Worked with IBM Java 1.8 ... fails reliably with IBM Java 1.7
>>>>>>
>>>>>> On Thu, May 4, 2017 at 10:50 AM, Marshall Schor <[email protected]> wrote:
>>>>>>
>>>>>>> that is correct - maven uses the value of JAVA_HOME
>>>>>>>
>>>>>>> -Marshall
>>>>>>>
>>>>>>>
>>>>>>> On 5/4/2017 10:45 AM, Burn Lewis wrote:
>>>>>>>> man is apparently using $JAVA_HOME as this is not the java in my path
>>>>>>>>
>>>>>>>>> mvn -version
>>>>>>>> Apache Maven 3.3.3 (7994120775791599e205a5524ec3e0dfe41d4a06;
>>>>>>>> 2015-04-22T07:57:37-04:00)
>>>>>>>> Maven home: /share/apache-maven-3.3.3
>>>>>>>> Java version: 1.7.0, vendor: IBM Corporation
>>>>>>>> Java home: /share/ibm-java-x86_64-70-SR9/jre
>>>>>>>> Default locale: en_US, platform encoding: UTF-8
>>>>>>>> OS name: "linux", version: "2.6.32-431.17.1.el6.x86_64", arch: "amd64",
>>>>>>>> family: "unix"
>>>>>>>>
>>>>>>>>
>>>>>>>> On Thu, May 4, 2017 at 10:38 AM, Peter Klügl <[email protected]>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Should work just without any preconditions.
>>>>>>>>>
>>>>>>>>> What build environement do you have? OS, Java version...
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Peter
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Am 04.05.2017 um 16:36 schrieb Burn Lewis:
>>>>>>>>>> Failing assertion & stacktrace:
>>>>>>>>>>
>>>>>>>>>>     Type type4 = cas.getTypeSystem().getType("
>>>>>>>>> my.package.one.One.Mtwl2");
>>>>>>>>>>     AnnotationIndex<AnnotationFS> ai4 = 
>>>>>>>>>> cas.getAnnotationIndex(type4);
>>>>>>>>>>>  assertEquals(1, ai4.size());
>>>>>>>>>>     assertEquals("2", ai4.iterator().next().getCoveredText());
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Running org.apache.uima.ruta.maven.OneEngineTest
>>>>>>>>>> Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 2.307
>>>>>>> sec
>>>>>>>>>> <<< FAILURE!
>>>>>>>>>> test(org.apache.uima.ruta.maven.OneEngineTest)  Time elapsed: 2.259
>>>>>>> sec
>>>>>>>>>>  <<< FAILURE!
>>>>>>>>>> java.lang.AssertionError: expected:<1> but was:<0>
>>>>>>>>>> at org.junit.Assert.fail(Assert.java:91)
>>>>>>>>>> at org.junit.Assert.failNotEquals(Assert.java:618)
>>>>>>>>>> at org.junit.Assert.assertEquals(Assert.java:126)
>>>>>>>>>> at org.junit.Assert.assertEquals(Assert.java:443)
>>>>>>>>>> at org.junit.Assert.assertEquals(Assert.java:427)
>>>>>>>>>> at org.apache.uima.ruta.maven.OneEngineTest.test(
>>>>>>> OneEngineTest.java:78)
>>>>>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>>>>>>> at
>>>>>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(
>>>>>>>>> NativeMethodAccessorImpl.java:95)
>>>>>>>>>> at
>>>>>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(
>>>>>>>>> DelegatingMethodAccessorImpl.java:56)
>>>>>>>>>> at java.lang.reflect.Method.invoke(Method.java:620)
>>>>>>>>>> at
>>>>>>>>>> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(
>>>>>>>>> FrameworkMethod.java:44)
>>>>>>>>>> at
>>>>>>>>>> org.junit.internal.runners.model.ReflectiveCallable.run(
>>>>>>>>> ReflectiveCallable.java:15)
>>>>>>>>>> at
>>>>>>>>>> org.junit.runners.model.FrameworkMethod.invokeExplosively(
>>>>>>>>> FrameworkMethod.java:41)
>>>>>>>>>> at
>>>>>>>>>> org.junit.internal.runners.statements.InvokeMethod.
>>>>>>>>> evaluate(InvokeMethod.java:20)
>>>>>>>>>> at
>>>>>>>>>> org.junit.internal.runners.statements.RunBefores.
>>>>>>>>> evaluate(RunBefores.java:28)
>>>>>>>>>> at
>>>>>>>>>> org.junit.internal.runners.statements.RunAfters.evaluate(
>>>>>>>>> RunAfters.java:31)
>>>>>>>>>> at
>>>>>>>>>> org.junit.runners.BlockJUnit4ClassRunner.runChild(
>>>>>>>>> BlockJUnit4ClassRunner.java:73)
>>>>>>>>>> at
>>>>>>>>>> org.junit.runners.BlockJUnit4ClassRunner.runChild(
>>>>>>>>> BlockJUnit4ClassRunner.java:46)
>>>>>>>>>> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:180)
>>>>>>>>>> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:41)
>>>>>>>>>> at org.junit.runners.ParentRunner$1.evaluate(ParentRunner.java:173)
>>>>>>>>>> at
>>>>>>>>>> org.junit.internal.runners.statements.RunBefores.
>>>>>>>>> evaluate(RunBefores.java:28)
>>>>>>>>>> at
>>>>>>>>>> org.junit.internal.runners.statements.RunAfters.evaluate(
>>>>>>>>> RunAfters.java:31)
>>>>>>>>>> at org.junit.runners.ParentRunner.run(ParentRunner.java:220)
>>>>>>>>>> at
>>>>>>>>>> org.apache.maven.surefire.junit4.JUnit4Provider.execute(
>>>>>>>>> JUnit4Provider.java:252)
>>>>>>>>>> at
>>>>>>>>>> org.apache.maven.surefire.junit4.JUnit4Provider.
>>>>>>>>> executeTestSet(JUnit4Provider.java:141)
>>>>>>>>>> at
>>>>>>>>>> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(
>>>>>>>>> JUnit4Provider.java:112)
>>>>>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>>>>>>> at
>>>>>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(
>>>>>>>>> NativeMethodAccessorImpl.java:95)
>>>>>>>>>> at
>>>>>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(
>>>>>>>>> DelegatingMethodAccessorImpl.java:56)
>>>>>>>>>> at java.lang.reflect.Method.invoke(Method.java:620)
>>>>>>>>>> at
>>>>>>>>>> org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(
>>>>>>>>> ReflectionUtils.java:189)
>>>>>>>>>> at
>>>>>>>>>> org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(
>>>>>>>>> ProviderFactory.java:165)
>>>>>>>>>> at
>>>>>>>>>> org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(
>>>>>>>>> ProviderFactory.java:85)
>>>>>>>>>> at
>>>>>>>>>> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(
>>>>>>>>> ForkedBooter.java:115)
>>>>>>>>>> at org.apache.maven.surefire.booter.ForkedBooter.main(
>>>>>>>>> ForkedBooter.java:75)
>>>>>>>>>> On Thu, May 4, 2017 at 10:18 AM, Burn Lewis <[email protected]>
>>>>>>> wrote:
>>>>>>>>>>> Keep getting the same test failure ... do I have to install UIMA &
>>>>>>>>> UIMAFit
>>>>>>>>>>> somewhere?
>>>>>>>>>>>
>>>>>>>>>>> ~Burn
>>>>>>>>>>>
>>>>>>>>>>> On Thu, May 4, 2017 at 9:10 AM, Marshall Schor <[email protected]> 
>>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> The problem seems (somewhat) intermittent. Yesterday, solid 
>>>>>>>>>>>> failure.
>>>>>>>>> This
>>>>>>>>>>>> morning, first time - it failed, 2nd time it worked (for me).  Burn
>>>>>>>>>>>> reports he
>>>>>>>>>>>> got past this, this morning, as well...
>>>>>>>>>>>>
>>>>>>>>>>>> -Marshall
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On 5/4/2017 3:05 AM, Peter Klügl wrote:
>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> no idea yet. I successfully downloaded the file outside of our
>>>>>>>>> network.
>>>>>>>>>>>>> Any ideas how we can *reasonably* hotfix the problem for the 
>>>>>>>>>>>>> review?
>>>>>>>>> Can
>>>>>>>>>>>>> you download it from somewhere else and manually add it to the 
>>>>>>>>>>>>> local
>>>>>>>>> m2
>>>>>>>>>>>>> folder?
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Best,
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Peter
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Am 03.05.2017 um 19:47 schrieb Marshall Schor:
>>>>>>>>>>>>>> more info:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> That directory
>>>>>>>>>>>>>> (http://maven.averbis.com/m2/org/eclipse/swt/win32/win32/x86
>>>>>>>>>>>> _64/3.104.1/) has
>>>>>>>>>>>>>> .jar, .pom, and .md5 and .sha1 for both of those.  All of the
>>>>>>> files I
>>>>>>>>>>>> can
>>>>>>>>>>>>>> download except the .jar.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> In linux, doing a "curl" command on this site, it seems to get
>>>>>>> about
>>>>>>>>>>>> 105K bytes,
>>>>>>>>>>>>>> and then fail.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Here's the output from curl:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> curl
>>>>>>>>>>>>>> http://maven.averbis.com/m2/org/eclipse/swt/win32/win32/x86_
>>>>>>>>>>>> 64/3.104.1/x86_64-3.104.1.jar
>>>>>>>>>>>>>>> t.jar
>>>>>>>>>>>>>>   % Total    % Received % Xferd  Average Speed   Time    Time
>>>>>>>>>>>>  Time  Current
>>>>>>>>>>>>>>                                  Dload  Upload   Total   Spent
>>>>>>>>>>>> Left  Speed
>>>>>>>>>>>>>>   3 2684k    3  105k    0     0   216k      0  0:00:12 --:--:--
>>>>>>>>>>>> 0:00:12  269k
>>>>>>>>>>>>>> curl: (56) Failure when receiving data from the peer
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Another go gives the same failure point: after receiving 105k:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> curl
>>>>>>>>>>>>>> http://maven.averbis.com/m2/org/eclipse/swt/win32/win32/x86_
>>>>>>>>>>>> 64/3.104.1/x86_64-3.104.1.jar
>>>>>>>>>>>>>>> t.jar
>>>>>>>>>>>>>>   % Total    % Received % Xferd  Average Speed   Time    Time
>>>>>>>>>>>>  Time  Current
>>>>>>>>>>>>>>                                  Dload  Upload   Total   Spent
>>>>>>>>>>>> Left  Speed
>>>>>>>>>>>>>>   3 2684k    3  105k    0     0   212k      0  0:00:12 --:--:--
>>>>>>>>>>>> 0:00:12  263k
>>>>>>>>>>>>>> curl: (56) Failure when receiving data from the peer
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> -Marshall
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On 5/3/2017 10:39 AM, Peter Klügl wrote:
>>>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I was able to download it (from within our network). I'll ask 
>>>>>>>>>>>>>>> our
>>>>>>> IT
>>>>>>>>>>>> for
>>>>>>>>>>>>>>> advice...
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Peter
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Am 03.05.2017 um 16:34 schrieb Marshall Schor:
>>>>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> I just went to
>>>>>>>>>>>>>>>> http://maven.averbis.com/m2/org/eclipse/swt/win32/win32/x86_
>>>>>>>>>>>> 64/3.104.1/ in a
>>>>>>>>>>>>>>>> browser, and could see the jar file, but downloading it 
>>>>>>>>>>>>>>>> produced
>>>>>>> a
>>>>>>>>>>>> network error
>>>>>>>>>>>>>>>> (reported by my browser...)
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Would be good to get this fixed :-)
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> -Marshall
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On 5/3/2017 8:54 AM, Peter Klügl wrote:
>>>>>>>>>>>>>>>>> Could maybe some server maintenance (yesterday 18:00 CEST), 
>>>>>>>>>>>>>>>>> or a
>>>>>>>>>>>>>>>>> timeout. The server is terribly slow.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Peter
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Am 03.05.2017 um 14:51 schrieb Burn Lewis:
>>>>>>>>>>>>>>>>>> My build from the source zip on Linux failed with a reference
>>>>>>> to
>>>>>>>>>>>> win32:
>>>>>>>>>>>>>>>>>> [ERROR] Failed to execute goal on project ruta-ep-parent: 
>>>>>>>>>>>>>>>>>> Could
>>>>>>>>>>>> not resolve
>>>>>>>>>>>>>>>>>> dependencies for project org.apache.uima:ruta-ep-
>>>>>>>>> parent:pom:2.6.1:
>>>>>>>>>>>> Could
>>>>>>>>>>>>>>>>>> not transfer artifact org.eclipse.swt.win32.win32:x8
>>>>>>>>>>>> 6_64:jar:3.104.1
>>>>>>>>>>>>>>>>>> from/to averbis-osgi-releases (http://maven.averbis.com/m2/):
>>>>>>>>> GET
>>>>>>>>>>>> request
>>>>>>>>>>>>>>>>>> of: 
>>>>>>>>>>>>>>>>>> org/eclipse/swt/win32/win32/x86_64/3.104.1/x86_64-3.104.1.
>>>>>>>>> jar
>>>>>>>>>>>> from
>>>>>>>>>>>>>>>>>> averbis-osgi-releases failed: Connection reset
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> ~Burn
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> On Tue, May 2, 2017 at 3:30 AM, Peter Klügl <
>>>>>>>>>>>> [email protected]>
>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> a gentle ping :-)
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> The vote is now open for almost two weeks and only one vote 
>>>>>>>>>>>>>>>>>>> is
>>>>>>>>>>>> missing.
>>>>>>>>>>>>>>>>>>> Peter
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Am 19.04.2017 um 17:32 schrieb Peter Klügl:
>>>>>>>>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> the first release candidate of Apache UIMA Ruta v2.6.1 is
>>>>>>> ready
>>>>>>>>>>>> for
>>>>>>>>>>>>>>>>>>> voting.
>>>>>>>>>>>>>>>>>>>> This bugfix release is not compatible with UIMA 3.0.0.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Major changes in this release:
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> UIMA Ruta Language and Analysis Engine:
>>>>>>>>>>>>>>>>>>>> * Fixed problem with empty annotation list expressions
>>>>>>>>>>>>>>>>>>>> * Fixed false positive match in conjunct rules
>>>>>>>>>>>>>>>>>>>> * Requires UIMA 2.10.0 and uimaFIT 2.3.0
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> UIMA Ruta Workbench:
>>>>>>>>>>>>>>>>>>>> * Fixed Query View
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Staging repository:
>>>>>>>>>>>>>>>>>>>> https://repository.apache.org/content/repositories/orgapache
>>>>>>>>>>>> uima-1138/
>>>>>>>>>>>>>>>>>>>> SVN tag:
>>>>>>>>>>>>>>>>>>>> https://svn.apache.org/repos/asf/uima/ruta/tags/ruta-2.6.1
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Update site:
>>>>>>>>>>>>>>>>>>>> https://dist.apache.org/repos/dist/dev/uima/ruta-2.6.1-rc1/
>>>>>>>>>>>>>>>>>>> eclipse-update-site/ruta/
>>>>>>>>>>>>>>>>>>>> Archive with all sources:
>>>>>>>>>>>>>>>>>>>> https://dist.apache.org/repos/dist/dev/uima/ruta-2.6.1-rc1/
>>>>>>>>>>>>>>>>>>> ruta-2.6.1-source-release.zip
>>>>>>>>>>>>>>>>>>>> Overall 7 issues have been fixed for this release
>>>>>>>>>>>>>>>>>>>> They can be found in the RELEASE_NOTES.html.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> ... and here:
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> https://issues.apache.org/jira/issues/?jql=project%20%
>>>>>>>>>>>>>>>>>>> 3D%20UIMA%20AND%20fixVersion%20%3D%202.6.1ruta%20AND%
>>>>>>>>>>>>>>>>>>> 20component%20%3D%20ruta%20ORDER%20BY%20created%20DESC
>>>>>>>>>>>>>>>>>>>> Please vote on release:
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> [ ] +1 OK to release
>>>>>>>>>>>>>>>>>>>> [ ]  0 Don't care
>>>>>>>>>>>>>>>>>>>> [ ] -1 Not OK to release, because ...
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Thanks.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Peter
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>

Reply via email to