• 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: Custom type EOModeler issue
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Custom type EOModeler issue


  • Subject: Re: Custom type EOModeler issue
  • From: Wolfram Stebel <email@hidden>
  • Date: Thu, 29 Dec 2005 16:09:36 +0100
  • Thread-topic: Custom type EOModeler issue

Am 28.12.2005 19:23 Uhr schrieb "Chuck Hill" unter
<email@hidden>:

Hi Chuck,

thanks for this perfect support.
Practical WO has been a little incomplete on this to get it working :-)

> I think  you are slightly mistaken.  The stack trace indicates that
> the problem happens during the takeValues phase, which occurs before
> invokeAction and the code tied to the Submit button.
I'll practice reading stack traces, i promise

>
>> java.lang.IllegalArgumentException: While trying to invoke the set
>> method
>> "public void CSampleTable.setAvalue(MyType)" on an object of type
>> CSampleTable we received an argument of type java.lang.String. This
>> often
>> happens if you forget to use a formatter.
I was told about the formatter...

>
...

>> What am i missing?
>>
> There are a few things you can do.  One is to follow EOF's suggestion
> and add a formatter that can format (convert between) MyType and
> String.  Given a String s, it will return new MyType(s).  Given a
> MyType t, it will return t.getValue().
...
>
> I'd prefer a formatter: it keeps the code all in one place and is
> easy to reuse.  I'd avoid adding code to CSampleTable as you would
> have to do this in every object that used MyType.
I followed your recommendations regarding the implementation of the MyType
class (immutable etc.).
Further i implemented a formatter "MyTypeFormatter" which i use for data
exchange in my component.
Works like a charme!!!

One question remains:

I allocate the formatter as a public final member in my application at the
moment. Is it a reasonable place or should i allocate it in session or
component context?

I would say, session is best for speed, resources and safety, do you agree?

Thanks

Wolfram

P.S. In a short while i will publish my "BaseWOApp" with several interesting
solutions (MyType EO data type, timertask for property update [from
PropDemo.zip, www.bugs-and-errors.de], page member pushing and popping for
correct forward and backward navigation, standard error handling pages...)
That's something for beginners :-)


 _______________________________________________
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: Custom type EOModeler issue
      • From: Chuck Hill <email@hidden>
References: 
 >Re: Custom type EOModeler issue (From: Chuck Hill <email@hidden>)

  • Prev by Date: Re: Unable to read index.eomodeld
  • Next by Date: Re: Unable to read index.eomodeld
  • Previous by thread: Re: Custom type EOModeler issue
  • Next by thread: Re: Custom type EOModeler issue
  • Index(es):
    • Date
    • Thread