Hi Chuck,
I like your answer :-)
Any insight that could explain why we see this bug so rarely?
Philippe
Sent from my iPhone
On 6 déc. 2011, at 23:45, Chuck Hill wrote:
>
> On 2011-12-06, at 2:31 PM, Lachlan Deck wrote:
>
>> On 07/12/2011, at 9:23 AM, Philippe Rabier wrote:
>
>>> And a que
On 2011-12-06, at 2:31 PM, Lachlan Deck wrote:
> On 07/12/2011, at 9:23 AM, Philippe Rabier wrote:
>> And a question regarding the workaround: is there any drawback to call the
>> EOObserver in the dispatchRequest method like suggested?
>
> For multiple active worker threads, a good question..
On 2011-12-06, at 2:31 PM, Lachlan Deck wrote:
> On 07/12/2011, at 9:23 AM, Philippe Rabier wrote:
>
>> I can feel how uncomfortable you are.
>>
>> What makes me confused is to never see this bug before. It's hard to believe
>> that nobody saw the errors if there are error. But on another sid
On 2011-12-06, at 2:15 PM, Lachlan Deck wrote:
> On 07/12/2011, at 7:46 AM, Pascal Robert wrote:
>
>> Le 2011-12-06 à 15:44, Andrew Lindesay a écrit :
>>
>>> Hello Calven;
>>>
>>> Thanks, but I guess we should thank the original people who investigated!
>>>
>>> It would be nice if a dot relea
On 07/12/2011, at 9:23 AM, Philippe Rabier wrote:
> I can feel how uncomfortable you are.
>
> What makes me confused is to never see this bug before. It's hard to believe
> that nobody saw the errors if there are error. But on another side, I (and
> all the team) worked on many applications s
On 07/12/2011, at 9:18 AM, prob...@macti.ca wrote:
> Le 2011-12-06 à 17:15, "Lachlan Deck" a écrit :
>
>> On 07/12/2011, at 7:46 AM, Pascal Robert wrote:
>>
>>> Le 2011-12-06 à 15:44, Andrew Lindesay a écrit :
>>>
Hello Calven;
Thanks, but I guess we should thank the original p
I can feel how uncomfortable you are.
What makes me confused is to never see this bug before. It's hard to believe
that nobody saw the errors if there are error. But on another side, I (and all
the team) worked on many applications so following the explanation, I don't
know why we don't see t
Envoyé de mon iPhone
Le 2011-12-06 à 17:15, "Lachlan Deck" a écrit :
> On 07/12/2011, at 7:46 AM, Pascal Robert wrote:
>
>> Le 2011-12-06 à 15:44, Andrew Lindesay a écrit :
>>
>>> Hello Calven;
>>>
>>> Thanks, but I guess we should thank the original people who investigated!
>>>
>>> It wou
On 07/12/2011, at 7:46 AM, Pascal Robert wrote:
> Le 2011-12-06 à 15:44, Andrew Lindesay a écrit :
>
>> Hello Calven;
>>
>> Thanks, but I guess we should thank the original people who investigated!
>>
>> It would be nice if a dot release of WO could be done with a patch for
>> whatever problem
I expect that in most cases it would be rather rare that this caused problems.
I am surprised that adding this so immediately resolved your problem.
On 2011-12-06, at 1:52 PM, Calven Eggert wrote:
> uncomfortable doesn't begin to describe how I'm feeling. Now I question the
> data in our d
On 2011-12-06, at 1:43 PM, James Cicenia wrote:
> I have an old app and was wondering if you could use ERExcellLook within my
> app
> to generate some custom reports.
>
> Is it possible? If so any pointers, screen casts
yes
> , on how to integrate?
>
> Thanks,
> James
>
>
uncomfortable doesn't begin to describe how I'm feeling. Now I question the
data in our database for all of our WO applications. egad. I need a drink.
while I'm at it I'll get one for the boss too.
On 2011-12-06, at 3:44 PM, Andrew Lindesay wrote:
> Hello Calven;
>
> Thanks, but I guess we
I have an old app and was wondering if you could use ERExcellLook within my app
to generate some custom reports.
Is it possible? If so any pointers, screen casts, on how to integrate?
Thanks,
James
smime.p7s
Description: S/MIME cryptographic signature
_
Le 2011-12-06 à 15:44, Andrew Lindesay a écrit :
> Hello Calven;
>
> Thanks, but I guess we should thank the original people who investigated!
>
> It would be nice if a dot release of WO could be done with a patch for
> whatever problem this is because it's a bit of an uncomfortable bug.
Sadl
Hello Calven;
Thanks, but I guess we should thank the original people who investigated!
It would be nice if a dot release of WO could be done with a patch for
whatever problem this is because it's a bit of an uncomfortable bug.
cheers.
On 7/12/11 3:35 AM, Calven Eggert wrote:
Andrew, THAN
It is not fixed in Wonder that I see.
On 2011-12-06, at 7:44 AM, Alexander Spohr wrote:
> Hm, should we all put that in our apps then?
> Or is it fixed in 5.4 or Wonder?
>
>
>
> Am 06.12.2011 um 15:35 schrieb Calven Eggert:
>
>> Andrew, THANK YOU, THANK YOU, THANK YOU!!!
>>
>> This was ex
I'm using WO 5.4.3 so that means it's not fixed there. I'm going to add to all
my projects. (I don't use Wonder)
Calven
On 2011-12-06, at 10:44 AM, Alexander Spohr wrote:
> Hm, should we all put that in our apps then?
> Or is it fixed in 5.4 or Wonder?
>
>
>
> Am 06.12.2011 um 15:35 schrie
Hm, should we all put that in our apps then?
Or is it fixed in 5.4 or Wonder?
Am 06.12.2011 um 15:35 schrieb Calven Eggert:
> Andrew, THANK YOU, THANK YOU, THANK YOU!!!
>
> This was exactly what was happening in my case and by simply adding this:
>
>public WOResponse dispatchRequest(WOR
Andrew, THANK YOU, THANK YOU, THANK YOU!!!
This was exactly what was happening in my case and by simply adding this:
public WOResponse dispatchRequest(WORequest request) {
EOObserverCenter.notifyObserversObjectWillChange(null);
return super.dispatchRequest(request);
}
I
Hi List,
I am creating a RMDocument to generate pdf report using ReportMill.jar
in webobjects 5.4.3
Now i want to provide the same output in excel format to the user using
ReportMill with the same document.
Thanks in advance.
--Pavan Jayam.
__
20 matches
Mail list logo
