• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: D2W and CooperatingEditingContext: Can anybody use together? SOLVED
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


  • Subject: Re: D2W and CooperatingEditingContext: Can anybody use together? SOLVED
  • From: gbrown <email@hidden>
  • Date: Mon, 25 Apr 2005 14:06:27 -0400

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.....

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Follow-Ups:
    • Re: D2W and CooperatingEditingContext: Can anybody use together? SOLVED
      • From: Chuck Hill <email@hidden>
References: 
 >D2W and CooperatingEditingContext: Can anybody use together? (From: gbrown <email@hidden>)
 >Re: D2W and CooperatingEditingContext: Can anybody use together? (From: Chuck Hill <email@hidden>)

  • Prev by Date: Threaded / offline processor (EOF Memory Management)
  • Next by Date: Re: D2W and CooperatingEditingContext: Can anybody use together? SOLVED
  • Previous by thread: Re: D2W and CooperatingEditingContext: Can anybody use together?
  • Next by thread: Re: D2W and CooperatingEditingContext: Can anybody use together? SOLVED
  • Index(es):
    • Date
    • Thread