On May 2, 2014, at 12:27 PM, Fred Opims wrote:
> After that, i've tried to to have the same configuration you've set in the
> Wolips Pane.
> I had to copy some frameworks in some specific location.
Those are just the defaults. You can actually put them anywhere you want, as
long as the wolip.
Hi Oliver,
Did you manage to solve your problem?
I agree that an article on embedded WO would be delightful to read, please let
us know if you decide to write it.
Good luck,
Angelo
Em 27/03/2013, à(s) 13:03, Ingenieurbüro Birnfeld - Oliver Birnfeld
escreveu:
> Hi,
>
> jstack does not show
Hi Ramsey
Thanks very much for pointing me to that: the query is now working fine.
Liz
On 2 May 2014, at 16:45, Ramsey Gurley wrote:
> http://jenkins.wocommunity.org/job/Wonder/javadoc/er/extensions/eof/qualifiers/ERXToManyQualifier.html
>
> On May 2, 2014, at 2:54 AM, Elizabeth Lynch wrote
The WOComponent parser chokes because that is invalid XML and also a bad
practice in general [much like using inline bindings and ognl :)]
If you want to optionally include a div tag, there’s a dynamic element for
that. You should use WOGenericContainer with an omitTags binding on the
conditi
I am trying to port my old WebObjects to Wonder/WOLips and am getting errors in
the HTML.
The error is that about the , , and tag
is missing.
First, the code is correct. I think that the parser is not pairing the correct
open and close tags.
I am using Eclipse 4.3.2 and Wolips 4.3.2.
I have
Hi Dave!
Thank you very much!
I've finally succeed to make the build.
I don't know why but Eclipse prefers using wolips.543.properties files
rather than wolips.properties. I could not change the Wolips Properies file
value (in Wolips pane) to wolips.properties. Eclipse didn't allow me to do
that. S
http://jenkins.wocommunity.org/job/Wonder/javadoc/er/extensions/eof/qualifiers/ERXToManyQualifier.html
On May 2, 2014, at 2:54 AM, Elizabeth Lynch wrote:
> I've got a query which could be dealt with by building up qualifiers, but I'd
> prefer to use the model-based fetch spec.
>
> As backgrou
Okay, now looking over all the files together, I may have found the issue!
I see in the wolips.properties file you have:
wo.local.frameworks=/Library/Frameworks
in wolips.543.properties file you have:
wo.local.frameworks=/Library/WebObjects/Versions/WebObjects543/System/Library/Frameworks
Whic
Hi Dave!
Thank you!
The wolips.properties file i sent you was coming from ~/Library/Application
Support/WOLips/
This was a only place where this file exists.
So i put the entry wolips.properties=~/Library/Application Support/WOLips/ in
my build.properties. But i got an new error message The proper
You could do it using GROUP BY HAVING COUNT with count being the number of
categories.
I implemented a EOGroupByQualifier some years ago. I don’t think it made it
into Wonder.
Am 02.05.2014 um 11:54 schrieb Elizabeth Lynch :
> I've got a query which could be dealt with by building up qualifie
I've got a query which could be dealt with by building up qualifiers, but I'd
prefer to use the model-based fetch spec.
As background: I have three tables: Image, Category and CategoryImage.
Image:
id name
1 Fred
2 Joan
CategoryImage
imageId categoryId
Hi Sankar,
I suppose you mean WebObjects 5.4.3 and Java 8, as there is not yet any JDK 9
specified, much less released, and WO 4.x wasn’t even Java-based.
Nevertheless, those sun.* API uses have to be cleaned up sooner or later, yes.
I’m sure this will happen soon as JDK 8 gets adopted. But thi
12 matches
Mail list logo
