Just where exactly is an RR loop in a JC scenario?
Cheers, Anjo
Am 13.10.2008 um 22:43 schrieb Florijan Stamenkovic:
I tried adapting ERXEC to a JC scenario. I stripped away the factory
stuff, the delegate and properties (I made it always autoLock), as
well as lock coalescing. However, it d
I have been following the tutorial "WO_WOLips_Wonder_Tutorial_Part_1". The
tutorial is wonderful and answers a lot of questions I had about setting up
a project using wolips. I am running into a few problems with this tutorial
1. For some reason migrations is not creating the table. I can create t
FYI, time machine worked like a charm. Just moved my frameworks dir
and my whole workspace back to this morning. Very nice!
Jeff
On Oct 13, 2008, at 11:00 PM, Jeff Schmitz wrote:
I think I want to go back. Would my time machine backup be the
easiest thing to do?
On Oct 13, 2008, at 10
This should hopefully be fixed in the next nightly build. The javadoc
should automagically be set for WO Java* frameworks to the wo.api.root
path defined in your wolips.properties file.
On 12/10/2008, at 8:06 AM, Phillip Hutchings wrote:
On 12/10/2008, at 05:33, JR Ruggentaler wrote:
This
On Oct 13, 2008, at 11:55 PM, Mike Schrag wrote:
I tried upgrading to Eclipse 3.4.1, upgraded to the WOLips nightly
build and downloaded and installed the lastest Wonder-latest-
frameworks-5.4. Now, when I open my workspace I don't see my
WOFrameworks folder, and neither does eclipse since
I think I want to go back. Would my time machine backup be the
easiest thing to do?
On Oct 13, 2008, at 10:58 PM, Mike Schrag wrote:
A little more specific info. One of the packages that can't be
seen bythe compiler is er.extension.ERXGenericRecord.
If you're using a version of Wonder new
A little more specific info. One of the packages that can't be seen
bythe compiler is er.extension.ERXGenericRecord.
If you're using a version of Wonder newer than June, this is the wrong
package for ERXGenericRecord. Wonder 5 was refactored into packages
(see the June 7th post on the Proj
I tried upgrading to Eclipse 3.4.1, upgraded to the WOLips nightly
build and downloaded and installed the lastest Wonder-latest-
frameworks-5.4. Now, when I open my workspace I don't see my
WOFrameworks folder, and neither does eclipse since nothing in the
ERX framework compiles. What can
Thanks, I can now see my frameworks listed. It looks like they are
all there (see previous e-mail) and yet the compiler doesn't seem to
be picking them up. Any ideas? Do I need to regenerate my EOModel
classes?
Thanks,
Jeff
On Oct 13, 2008, at 10:43 PM, Ramsey Gurley wrote:
Hi Jeff,
A little more specific info. One of the packages that can't be seen
bythe compiler is er.extension.ERXGenericRecord. Looking at the java
build path, Libraries, it lists the following as selected (among
others):
ERExtensions Framework
ERJars Framework
ERPrototypes Framework.
Thanks,
Jeff
Hi Jeff,
I'm doing the same thing now. I had the same problem. I think you're
in the wrong view. Go to Window->Show View->Other and pick WO Explorer.
Ramsey
On Oct 13, 2008, at 11:14 PM, Jeff Schmitz wrote:
Hello,
I tried upgrading to Eclipse 3.4.1, upgraded to the WOLips nightly
bu
So, assuming I didn't do any major screw-ups when doing this, it
should work. However, what I'm currently doing with JC might produce
an even "heavier" load then a web scenario. Not in terms of volumes
for sure, but in terms of how rapidly calls from different threads
are made to a single e
Hi Gus,
Using Activity Monitor (or any utility that shows process information
like 'top') search for processes name 'java' running as your user.
Kill the process you suspect to be the offender.
sharpy..
On 14/10/2008, at 1:21 PM, WebObjects wrote:
Hello,
Well working here, my Eclipse c
Hello,
Well working here, my Eclipse crashed this afternoon, and I just force
quit it. Then I went out and now that I came back I opened Eclipse
once again and run the project, and there was an error:
Caused by: java.net.BindException: Address already in use
at java.net.PlainSocketImp
Hello,
I tried upgrading to Eclipse 3.4.1, upgraded to the WOLips nightly
build and downloaded and installed the lastest Wonder-latest-
frameworks-5.4. Now, when I open my workspace I don't see my
WOFrameworks folder, and neither does eclipse since nothing in the ERX
framework compiles.
On Oct 13, 2008, at 5:43 PM, Ash Mishra wrote:
I'm trying to switch a WOApp that has a framework with my model
and entity classes to use Project Wonder. I've followed the
Quickstart guide, but the following error occurs when the
application launches:
[main] WARN er.extensions.ERXEntity
I'm trying to switch a WOApp that has a framework with my model and
entity classes to use Project Wonder. I've followed the Quickstart
guide, but the following error occurs when the application launches:
[main] WARN er.extensions.ERXEntityClassDescription - Invalid
class name for entity:
I don't understand what you say about autoLocking being RR based.
Yep, sorry -- you're right ... Lock coalescing is the one that depends
on the RR loop. That said, I definitely ran into cases where auto-
locking alone was not enough (at least on the web ... maybe it's less
of an issue with J
On 13-Oct-08, at 3:29 PM, Chuck Hill wrote:
I'm trying to switch a WOApp that has a framework with my model and
entity classes to use Project Wonder. I've followed the Quickstart
guide, but the following error occurs when the application launches:
[main] WARN er.extensions.ERXEntityClassD
Hm, yeah, to some degree. However, for any user action tens of events
can be fired, of different types. During application startup this
number can grow to hundreds. I am not sure what you're getting at,
but trying to handle events globally would not work, in my opinion. I
guess this is a pa
Hey Mike,
Thanks for replying. There is no practical equivalent of the RR loop
on the client. While there is an RR loop during which the client asks
the server for data, the client side EOF can be doing a lot of things
outside of it. Because of that I kicked out lock coalescing. The
relev
On 14/10/2008, at 7:47 AM, Mike Schrag wrote:
I tried adapting ERXEC to a JC scenario. I stripped away the
factory stuff, the delegate and properties (I made it always
autoLock), as well as lock coalescing. However, it does not help. I
get deadlocks and exceptions. There are two threads inv
On Oct 13, 2008, at 3:15 PM, Ash Mishra wrote:
Hi,
I'm trying to switch a WOApp that has a framework with my model and
entity classes to use Project Wonder. I've followed the Quickstart
guide, but the following error occurs when the application launches:
[main] WARN er.extensions.ERXEnti
Hi,
I'm trying to switch a WOApp that has a framework with my model and
entity classes to use Project Wonder. I've followed the Quickstart
guide, but the following error occurs when the application launches:
[main] WARN er.extensions.ERXEntityClassDescription - Invalid class
name for ent
I tried adapting ERXEC to a JC scenario. I stripped away the factory
stuff, the delegate and properties (I made it always autoLock), as
well as lock coalescing. However, it does not help. I get deadlocks
and exceptions. There are two threads involved, one instance of my
WorkerThread class a
Hi all,
Cross posting this to wonder and WO, as it seems appropriate on both
lists.
I tried adapting ERXEC to a JC scenario. I stripped away the factory
stuff, the delegate and properties (I made it always autoLock), as
well as lock coalescing. However, it does not help. I get deadlocks
The Chicago CocoaHeads / Chicago Cocoa and WebObjects User Group
(CAWUG) is holding our next meeting Tuesday, October 14th, at 7:00 PM
at the Apple Store on Michigan Ave.
Agenda:
- Introductions & Announcements
- Jon on iPhone development A.N. (After NDA)
- adjour
On Oct 13, 2008, at 11:03 AM, Florijan Stamenkovic wrote:
Without more info, it looks as though your eogen file is not finding
your prototypes entity / model. This makes it unable to detect the
class types of attributes, because that information is stored in the
prototype.
Some questions
Hi Mersida
There is a page here that should answer all your questions and
provides a build script as well
http://wiki.objectstyle.org/confluence/display/WOL/Alternative+Ant+Build+Script+for+Fully+Embedded+and+Split+Install+Bundles
That page assumes you are using a web server. If you are doi
Without more info, it looks as though your eogen file is not finding
your prototypes entity / model. This makes it unable to detect the
class types of attributes, because that information is stored in the
prototype.
Some questions:
1. How do you deal with prototypes (separate model, separat
Hello ms,
Thanks for the response. Now, this might be obvious to you, but I've never
actually done this before, what does this mean...to "embed frameworks when
building ... " and does it or does it not have anything to do with my machine
being WO 5.4.3 and server being WO 5.4.2? I am checking
With regards Windows config you should ask on the mailing list ... I
generally use Mac OS X every day and Windows when I have to, so
Windows config for WO is not fresh in my mind at the moment.
Regards, Kieran
On Oct 13, 2008, at 9:56 AM, FOGWE wrote:
Thanks Kieran, for your quick respons
Hi Henri,
I cc the list for you in the reply ;-) Maybe others can reply all and
help you while you wait for your mailing list signup ...?
I don't use PostgreSQL yet, are you using Project Wonder's
PostgreSQL JDBC Adaptor framework? If not, use it. If you are, then
you need help from
Hi,
By translating Wonder to Japanese I have a question.
* If you actually want to see those new bindings in WOBuilder, edit
the file
* WebObjects Builder.app/Contents/Resources/
WebObjectDefinitions.xml,
* which contains the .api for the dynamic elements.
I would love to see this bind
34 matches
Mail list logo
