Back in January I started this discussion on this same topic:
http://lists.apple.com/archives/webobjects-dev/2011/Jan/msg00224.html
>> I have an app that, during the course of normal usage, is starting httpd
>> processes on the server that instantly hit 100% CPU usage of one core. This
>> can h
On Aug 20, 2011, at 10:43 PM, Ken Anderson wrote:
> David,
>
> When you say have a Relationship to the abstract Role class, I'm assuming
> you're recommending inheritance here. I do it the exact same way, just
> wanted to make sure it's not confusing to say "do abstract this" and also
> "get
Hi Ken,
First of all you need to use J2EE deployment of your application. Second as far
as I remember there is no WO direct integration with any J2EE web technologies
such as Struts or JSF. However I developed a framework long time back which
provides integration between any web technology with
It's taken me a few days to get back to this due to a deployment.
On Aug 10, 2011, at 7:51 AM, Chuck Hill wrote:
> On 2011-08-10, at 7:03 AM, Timothy Worman wrote:
>> On Aug 9, 2011, at 9:46 AM, Chuck Hill wrote:
>>
>>> Hi Tim,
>>>
>>> I am not really clear on what you are doing and what the pr
All,
Our organization is looking into using IceFaces, a set of JSF tools that have a
very nice web presentation. The larger organization is all leaning this way,
so there are a lot of resources.
My question is, does anyone have an experience using JSF and IceFaces with WO?
Ideally, I would l
David,
When you say have a Relationship to the abstract Role class, I'm assuming
you're recommending inheritance here. I do it the exact same way, just wanted
to make sure it's not confusing to say "do abstract this" and also "get rid of
inheritance".
For me, I have this type of structure in
I've been there, Johan. Don't use inheritance. That's what is messing with you.
An EO can't switch from being one Class to another. It completely er... um...
screws with EOF.
Get rid of the inheritance. Just have a Contact class that has a relationship
to the abstract Role class, and make all t
On Aug 20, 2011, at 9:21 AM, Paul Hoadley wrote:
> Hi Kevin,
>
> On 19/08/2011, at 9:33 PM, Kevin Hinkson wrote:
>
>> The general consensus seems to be don't use primary keys in the way I
>> described, use another unique identifier/slug etc. But if one really, really
>> has to; then the follo
Dave
On Aug 20, 2011, at 1:04 AM, Ramsey Gurley wrote:
> You'd also need to add an additional qualifier to your display groups to
> prevent the 'deleted' objects from showing up in the interface.
Or create a QueryDataSourceDelegate
(http://wiki.objectstyle.org/confluence/display/WO/D2W+Flow+Co
Hi Jeff,
Maybe you changed your hard drive format to Case-Sensitive HFS+ Formatting.
Upper-Case Spaces are totally different than Lower-Case spaces. Eclipse only
knows how to deal with Lower-Case ones. I'm willing to bet that you had an UC
space in the path but with a case-insensitive file syst
On 20/08/2011, at 6:58 PM, Johan Henselmans wrote:
> On 20 aug. 2011, at 01:26, Chuck Hill wrote:
>
>> On 2011-08-19, at 2:46 PM, Johan Henselmans wrote:
>
> I thought I used a Role pattern. situation:
> base class is contact, others are inheritances all in the same table
Sounds like you're con
On 20 aug. 2011, at 01:26, Chuck Hill wrote:On 2011-08-19, at 2:46 PM, Johan Henselmans wrote:My idea:I have an entity contact, that gets vertically inherited into actor, employee, visitor, nicepersontoalwayinviteforfreetoanyshow, whatever, based on the role somebody/thing plays. A contact can have
12 matches
Mail list logo