[Glass] Is it possible to explore/inspect objects from seaside callbacks in GemTools?
Mariano Martinez Peck
marianopeck at gmail.com
Wed Dec 18 07:12:04 PST 2013
On Wed, Dec 18, 2013 at 12:07 PM, Dale K. Henrichs <
dale.henrichs at gemtalksystems.com> wrote:
>
>
> ------------------------------
>
> *From: *"Mariano Martinez Peck" <marianopeck at gmail.com>
> *To: *"Dale K. Henrichs" <dale.henrichs at gemtalksystems.com>
> *Cc: *glass at lists.gemtalksystems.com
> *Sent: *Wednesday, December 18, 2013 6:20:50 AM
> *Subject: *Re: [Glass] Is it possible to explore/inspect objects from
> seaside callbacks in GemTools?
>
>
>
>
>
> On Tue, Dec 17, 2013 at 7:22 PM, Dale K. Henrichs <
> dale.henrichs at gemtalksystems.com> wrote:
>
>>
>>
>> ------------------------------
>>
>> *From: *"Mariano Martinez Peck" <marianopeck at gmail.com>
>> *To: *glass at lists.gemtalksystems.com
>> *Sent: *Tuesday, December 17, 2013 11:59:09 AM
>> *Subject: *[Glass] Is it possible to explore/inspect objects from
>> seaside callbacks in GemTools?
>>
>> .....
>>
>> Finally, and this is my real question...I have gems running seaside in
>> which I have some buttons to ease development. These buttons send #inspect
>> or #explore to some objects in seaside callbacks. When I do that (having a
>> GemTools connected to the same GemStone), I get this error:
>>
>> -----------
>>
>> Internal Server Error:
>>
>> a TransactionError occurred (error 2407), The object aSessionTemps(
>> #'GsHostRandomFile'->aGsFile,
>> #'GRGemStoneRandomProvider_MUTEX'->aTransientMutex,
>> #'SystemChangeNotifier_UniqueInstance'->aSystemChangeNotifier,
>> #'GsPackage_TransactionBoundary_Dict'->aSessionTemps(
>> #'SessionMethodChange'->1614, #'ClassChange'->6791),
>> #'Cached_Class_Organizer'->aCachingClassOrganizer,
>> #'GRGemStoneRandomProvider_GENERATOR'->aHostRandom,
>> #'GemToGemStaticException'->aGsExceptionHandler,
>> #'GsPackagePolicy_SessionMethodDictionary'->anIdentitySet( Array,
>> Association, Behavior, Boolean, Character, Class, Collection, Integer,
>> Magnitude, ObsoleteMetaclass, Number, Object, PositionableStream,
>> ReadStream, SequenceableCollection, SmallInteger, Stream, String,
>> UndefinedObject, ...), ...) may not be committed, 'instances of its class
>> are non-persistent'
>>
>> You should contact the system administrator
>>
>> -------------
>>
>>
>> So I guess this is expected right? there is no workaround?
>>
>> I'm not surprised that you are getting an error ... presumably we're
>> trying to dump the stack into the object log and it has some references to
>> the SessionTemps ... since there is no head inspect/explore aren't going to
>> bring up an inspector, however, it wouldn't be a bad idea to go ahead and
>> change inspect/explore to drop off the object into the ObjectLog ...
>>
>
> Yes, I was thinking about that too.
>
>
>> it is possible to tell if GemTools is connected, if `OBGemStonePlatform
>> canInform` answers true GemTools is running ...
>>
>>
> And do you think it is possible to avoid dumping the stack in the object
> log for the case of inspect/explore? because if true, we can check if
> GemTools is running, if true, we might be able to open a real
> inspector/explorer in GemTools and otherwise (or in addition) write the
> object to the object log?
>
> Exactly what I was thinking ... if GemTools (or Tode) is not present, drop
> the object into the object log for later ...
>
>
We are in sync then :)
--
Mariano
http://marianopeck.wordpress.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gemtalksystems.com/mailman/private/glass/attachments/20131218/0cffd945/attachment-0001.html>
More information about the Glass
mailing list