Re: D2W and CooperatingEditingContext: Can anybody use together? SOLVED

From: Chuck Hill (chil..lobal-village.net)
Date: Mon Apr 25 2005 - 14:10:39 EDT

  • Next message: David Teran: "Re: D2W and CooperatingEditingContext: Can anybody use together? SOLVED"

    It is certainly worthy of a bug report! I did not even notice the
    missing public.

    Chuck

    On Apr 25, 2005, at 11:06 AM, gbrown wrote:

    > Error was because it should say:� public� Session() {.....}
    > The session was created by WOLips D2W wizard, not Xcode which
    > correctly (IMHO) creates Session java with a constructor like:
    >
    > ��� public Session() {
    > ������� super();
    > �������
    > ������� /* ** Put your per-session initialization code here ** */
    > ��� }
    >
    > Hmm..is that worty of a WOLips request? I find several little
    > glitches with wolips...but Eclipse is so nice for all this java
    > stuff.....
    >
    > Chuck Hill wrote:
    >
    > That seems like a very odd exception.� It seems to be complaining
    > about� accessing a package instance variable in Session.� Try wrapping
    > the� call in a try... catch block and see what it shows.
    >
    > ���� Session(){ // use my ec
    > ���� ��� super();
    > �������� try {
    > ���� ������������� setDefaultEditingContext(new�
    > CooperatingEditingContext());
    > ���� ���}
    > ������� catch (Throwable t) {
    > �������������� NSLog.debug.appendln("setting default EC threw " +�
    > t.getMessage());
    > �������������� t.printStackTrace();
    > ���� }
    >
    > Chuck
    >
    >
    > On Apr 21, 2005, at 1:19 PM, gbrown wrote:
    >
    >
    > �Can a D2W use a CooperatingEditingContext, which implements the�
    > EOStateTransition interface?
    >
    > �Is there a way?
    >
    > �if I modify the session object :
    > ���� Session(){ // use my ec
    > ���� ��� super();
    > ���� ��� setDefaultEditingContext(new CooperatingEditingContext());
    > ���� ���
    > ���� }
    >
    >
    > �then the app explodes with:
    >
    > ��Error: java.lang.IllegalStateException exception
    > ��Reason:
    > ��java.lang.IllegalStateException: An Exception occurred while�
    > generating the Exception page 'WOExceptionPage'. This is most likely�
    > due to an error in 'WOExceptionPage' itself or WebObjects encountered�
    > an uncaught exception while creating a Session object.
    >
    >
    > ��Below are the logs of the original Exception which occured in�
    > Application, then the later Exception in WOExceptionPage.
    >
    > ��Original Exception:
    > ��java.lang.IllegalAccessException: Class�
    > com.webobjects.foundation._NSUtilities can not access a member of�
    > class Session with modifiers ""
    > ��at sun.reflect.Reflection.ensureMemberAccess(Reflection.java:57)
    > ��at java.lang.Class.newInstance0(Class.java:302)
    > .....SNIP.....
    >
    >

    -- 
    Practical WebObjects - a book for intermediate WebObjects developers 
    who want to increase their overall knowledge of WebObjects, or those 
    who are trying to solve specific application development problems.
    http://www.global-village.net/products/practical_webobjects
    



    This archive was generated by hypermail 2.0.0 : Mon Apr 25 2005 - 14:11:20 EDT