Hi Michaël,
hi Ede,
I tested it on two computer with different
environments and it works fine.
Thank you for your patience and your help!
Have a nice weekend.
Uwe
Am 18.04.2013 23:32, schrieb Michaël Michaud:
> Hi Uwe,
>
> Good catch !
> I could reproduce the bug with th elast JRE.
> I did no
Hi Uwe,
Good catch !
I could reproduce the bug with th elast JRE.
I did not remove dispose as I think it it is usefull to free
all resources attached to the TaskMonitor dialog box,
but I moved it after the error message display.
Available in r3513
Michaël
> Hi,
>
> in the class TaskMonitorManag
Hi,
in the class TaskMonitorManager
(package com.vividsolutions.jump.workbench.ui.task;)
there is a method "public void run ( )"
(line 148)
under "finally"
you will find:
dialog.setVisible( false );
dialog.dispose();
When I comment out
dialog.dispose();
then I see the error-gui with JRE 1.
Hi Michaël,
I think I know why we get different
behaviours of OpenJUMP.
It is an JRE problem, I believe!
I tested it now on several computer and different JRE.
I *see* the error message (like you) on computer with JRE
1.6.0_30 (x86) and (amd64)
1.6.0_31 (x86)
1.6.0_33 (x86)
1.7.0_02 (amd64)
1.7
On 18.04.2013 12:40, Uwe Dalluege wrote:
> Am 18.04.2013 10:40, schrieb edgar.sol...@web.de:
>> On 18.04.2013 08:59, Michaël Michaud wrote:
it is thrown by PostgisFeatureInputStreamIn
>> it is tranformed into an error (no need to add throws clause to the
>> method)
>> it is wrapped
Am 18.04.2013 10:40, schrieb edgar.sol...@web.de:
> On 18.04.2013 08:59, Michaël Michaud wrote:
>>> it is thrown by PostgisFeatureInputStreamIn
> it is tranformed into an error (no need to add throws clause to the
> method)
> it is wrapped into a string including sql + exception messag
On 18.04.2013 08:59, Michaël Michaud wrote:
>> it is thrown by PostgisFeatureInputStreamIn
>> >> it is tranformed into an error (no need to add throws clause to the
>> >> method)
>> >> it is wrapped into a string including sql + exception message + sql
>> >> message
>> >> it is thrown to the cal
Hi Uwe,
> I would say :
>> it is thrown by PostgisFeatureInputStreamIn
>> it is tranformed into an error (no need to add throws clause to the
>> method)
>> it is wrapped into a string including sql + exception message + sql
>> message
>> it is thrown to the caller (see the stacktrace)
>
> This i
Hi Michaël,
Am 17.04.2013 20:43, schrieb Michaël Michaud:
> Hi Uwe,
>> Hi Ede,
>>
>> I like to find an error in OJ.
>> Michaël can see this error but I do not see it.
>> There must be something different between
>> Michaël environment and my environment.
>>
>> Can *you* reproduce this error?
>>
>>
Hi Uwe,
Hi Ede,
I like to find an error in OJ.
Michaël can see this error but I do not see it.
There must be something different between
Michaël environment and my environment.
Can *you* reproduce this error?
1. File>Run Datastore Query.
2. Connect to a PostGIS databas
On 17.04.2013 20:22, Michaël Michaud wrote:
> Hi,
>> i suggested
B. handle the error there, via
JumpWorkbench.getInstance().getFrame().handleThrowable(t)
>> below. why don't you use this?
> I did not change because I saw one + and one -
> + : processing the exception in the class which t
Hi,
> i suggested
>>> B. handle the error there, via
>>> JumpWorkbench.getInstance().getFrame().handleThrowable(t)
> below. why don't you use this?
I did not change because I saw one + and one -
+ : processing the exception in the class which throwed it is more readable
- : introducing JumpWorkben
sorry, unfortunately i have no postgis set up here. ..ede
On 17.04.2013 11:54, Uwe Dalluege wrote:
> Hi Ede,
>
> I like to find an error in OJ.
> Michaël can see this error but I do not see it.
> There must be something different between
> Michaël environment and my environment.
>
> Can *you* re
Hi Ede,
I like to find an error in OJ.
Michaël can see this error but I do not see it.
There must be something different between
Michaël environment and my environment.
Can *you* reproduce this error?
1. File>Run Datastore Query.
2. Connect to a PostGIS database.
3. Type after Query: select * fr
i suggested
>>B. handle the error there, via
>>JumpWorkbench.getInstance().getFrame().handleThrowable(t)
below. why don't you use this?
..ede
On 17.04.2013 11:27, Uwe Dalluege wrote:
> Hi Michaël,
>
> now I have OJ3512 in eclipse.
>
> Is it right that the method toMessage ( )
> in com.vivids
Hi Michaël,
now I have OJ3512 in eclipse.
Is it right that the method toMessage ( )
in com.vividsolutions.jump.workbench.ui.WorkbenchFrame
(line 1089) should be invoked by the exception of
the method public FeatureSchema getFeatureSchema()
from the class PostgisFeatureInputStream?
I put an Syst
On 16.04.2013 20:19, Michaël Michaud wrote:
> Hi,
>> A. remove the catch.. it will be caught further up
> I think the catch is used to throw an error instead of an exception to
> conform to
> the method signature .
ok
>> or
>> B. handle the error there, via
>> JumpWorkbench.getInstance().getF
Hi,
> A. remove the catch.. it will be caught further up
I think the catch is used to throw an error instead of an exception to
conform to
the method signature .
> or
> B. handle the error there, via
> JumpWorkbench.getInstance().getFrame().handleThrowable(t)
I did not know this trick, thanks.
you could..
A. remove the catch.. it will be caught further up
or
B. handle the error there, via
JumpWorkbench.getInstance().getFrame().handleThrowable(t)
..ede
On 16.04.2013 14:07, Uwe Dalluege wrote:
> Hi Michaël,
>
> in the class PostgisFeatureInputStream
> from the package
> com.vividsolu
Hi Michaël,
in the class PostgisFeatureInputStream
from the package
com.vividsolutions.jump.datastore.postgis;
there is the method
public FeatureSchema getFeatureSchema(){ ...
which throw new Error ( ...
...
catch (SQLException ex) {
//savedException = ex;
// from uwe
System.out.pri
Hi Uwe,
>
> I have tested it again with the lates nightbuild
> (20130414 rev.3505) but I get no errormessage
> like you.
> Do you tested it with JRE 1.7.0_17?
>
> Do you know which class is resposible for the error-message?
This is WorkbenchFrame,
Here is the diff from March 21th which fixed the
Hi Michaël,
I have tested it again with the lates nightbuild
(20130414 rev.3505) but I get no errormessage
like you.
Do you tested it with JRE 1.7.0_17?
Do you know which class is resposible for the error-message?
Uwe
Am 11.04.2013 20:27, schrieb Michaël Michaud:
> Hi,
>> With OJ rev. 3459
>>
Hi,
With OJ rev. 3459
and W7 (64 bit) I do not
see errors or exceptions.
There is no dialog window or a message
in the status-line.
I tested "Run Datastore Query"
with this simple query:
select * from xyz
The table xyz does not exists in my database!
But there
Hi Michaël,
Am 10.04.2013 21:51, schrieb Michaël Michaud:
> Hi,
>> You can see that the rectangular geometry of the fence itself, not any
>> features inside it, is placed into the query. The number after ":" is
>> SRID, I used -1 in my case. The query itself gives an error when I
>> tested it dire
24 matches
Mail list logo
