Re: WO54 - New Component HTML format.
On 08/11/2007, at 6:52 PM, Les Vogel wrote: It worked! Thanks. Great. You've probably noticed a number of people talking about utilising a preceeding '$' rather than surrounding square brackets. The dollar symbol is used traditionally for oognl style bindings. WO5.4 by default uses the surrounding square brackets. But this can be customised. See the following thread: Is there an example that uses the new WO component format? http://wiki.objectstyle.org/confluence/display/WOL/mail/2097544 On 11/7/07, Lachlan Deck [EMAIL PROTECTED] wrote: Helpful log output ay! Have you tried this? wo:WOTextField value = [myVar] / On 08/11/2007, at 4:24 PM, Les Vogel wrote: I'm trying to get the new HTML Components to work, any ideas what might be wrong? !DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.0 Transitional//EN http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd; HTML HEAD META NAME=generator CONTENT=Testing/ TITLEWOTest/TITLE /HEAD BODY BGCOLOR=#FF wo:WOForm centerbHello and Welcome/b/center br / wo:WOTextField value = $myVar / wo:WOSubmitButton action = $doit value = submit / /wo:WOForm /BODY /HTML I get: *Error:* com.webobjects.appserver.parser.woml.WOMLTemplateParserException: Main: 12:2: Could not generate an element named: WOTextField *Reason:* Could not generate an element named: WOTextField Thoughts? with regards, -- Lachlan Deck ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
Re: WOShowcase at DynEd?
Le 07-11-05 à 12:37, Chuck Hill a écrit : On Nov 3, 2007, at 11:55 PM, Pascal Robert wrote: On Nov 3, 2007, at 10:05 PM, Klaus Berkling wrote: Does anyone still look at or use the WOShowcase at DynEd? http://www.dyned.com/woshowcase/ With the wiki pages and http://www.wocommunity.org/ I don't think there is much of a reason to keep it around. Thoughts anyone? We don't plan to have a apps directory on wocommunity.org (only a members listing), so I think your site is a great addition. I'd also like to see it say around. The community site could link to it under Who? Done. http://www.wocommunity.org/webobjects_directory.html ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
Re: Editing Contexts and Autorelease Pools in 4.5.1
On 7 Nov 2007, at 17:29, Dana Kashubeck wrote: Remember way back when WebObjects supported Objective-C /and/ Java? Well, travel back with me if you are able. I'm working with an Objective-C port of the MultiECLockManager. I ran into a really nasty situation because when you lock an editing context, it creates an autorelease pool that is subsequently released on unlock. Since autorelease pools work in stacks and I was locking/unlocking an array of editing contexts, pools were being released before I wanted them to. I did end up solving this issue by going /backwards/ through the array of editing contexts when unlocking. However, I'm wondering if there is a way to avoid this situation altogether. It is a long-shot that anyone here will be able to help (as you've all been writing Java apps for so long!), but I thought it couldn't hurt to ask: Does anyone have experience working with peer editing contexts in Objective-C WO? My dealings with multiple ECs in WO4.5.1 were -- indeed, are -- mostly to do with either nested ECs or ECs being worked in separate threads. I found when doing something time consuming, it was necessary to do it in a separate thread, and it was best to use a separate EC which I could lock and unlock as needed to avoid risking have the session's default EC be locked by a detached thread at a time when the session wanted to lock it because of servicing a page request. Yes, locking the EC will cause it to create a new NSAutoreleasePool, and yes, there are various things you can do such as -reset that will cuase the EC to lock itself. NSAutoreleasePools are stacked, so there is lots of scope to be bitten, and the best solution I can see is unlock the peer ECs in the reverse order to which they were locked, as described. NSAutoreleasePools are stacked per thread (and it says so in the class reference documentation). If you had each EC in a different thread, then you wouldn't encounter the problem you have -- rather, a whole bunch of different problems instead. I found that getting editing contexts to deallocate cleanly was a severe pain, because EOF hacks -dealloc for objects managed by ECs, and I was frequently hitting problems where something that was doing a pretend-to- deallocate-now-but-really-deallocate-later because of EOF was causing crashes when it actually did deallocate, because it had references to other parts of the EOF object graph which had already genuinely deallocated. Although I can't find the bit of documentation that says so (ie, it's not in the class reference documentation), it's my understanding that when an NSAutoreleasePool is released, any child NSAutoreleasePools -- necessarily stacked -- will also be released, and this would be a severe nuisance. Having reviewed Jonathan's original code, if we are working solely with peer ECs, do we really need MultiECLockManager? If all I needed was some convenience for ensuring that when I was finished, all ECs of interest were sent the right number of -unlock messages, I'd refactor this (or write something else) so that each editing context had its own lock count, and I could lock or unlock any managed EC (or query its lock count) via my manager object. That way, I could unlock ECs when they no longer needed to be locked ... except if I lock A then lock B, I cannot let the lock count for A fall to 0 until the lock count for B has fallen to 0 because of the stacked NSAutoreleasePool problem. Hmmm. This whole matter would be much simpler if one could refactor one's code to ensure that a maximum of 1 peer editing contexts was ever concurrently locked. -- Patrick ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
Redundant Results from Fetch to Single Table Inheritance Entity
Greetings,
I don't seem to be getting the correct SQL generated for a query and
I'm ending up with redundant results. I've fixed the problem by
adding an additional explicit EOQualifier to do the job that I think
that EOF should be doing, so this is no longer an immediate problem.
However, I'd like to throw the question out to the list to determine
if: 1) I'm doing anything wrong to cause the SQL to be generated the
way it is, or 2) whether there's a bug in EOF that I should report
(or have known about if already reported).
Environment:
WO 5.3
OpenBase 10.0
We have an EOModel with several entities, say, Student, School,
Teacher, etc. that have locations. The Location entity contains
address, city, state, postalCode, phone, and so forth. Using single-
table inheritance, We have several subentities for location to match
the entities being located, such as StudentLocation, SchoolLocation,
TeacherLocation, etc.
Each of the entities with locations has a one-to-many relationship
with the appropriate subentity for its locations, such as:
Student - StudentLocation
School - SchoolLocation
Teacher - TeacherLocation
The parent Location entity has a partyID attribute to hold the
foreign key for the to-one relationship back to the located entity
and, of course, a locationType attribute to distinguish among the
Location subentities.
We also use a State reference table/entity to hold the state's full
name (e.g. New York) and the state's abbreviation (e.g. NY).
To search for all male students in New York, NY with an Underwater
Basketweaving major, I use the following code to build and execute
the fetch:
static final NSArray preFetchKeyPaths = new NSArray(new Object[] {
locations,
locations.state,
locations.zipCodeLocation
});
...
EOQualifier qual;
NSMutableArray theQualifiers = new NSMutableArray();
qual = EOQualifier.qualifierWithQualifierFormat
(locations.state.abbreviation caseInsensitiveLike %s, new NSArray
(selectedStateAbbreviation));
theQualifiers.addObject(qual);
qual = EOQualifier.qualifierWithQualifierFormat(locations.city
caseInsensitiveLike %s, new NSArray(selectedCityName));
theQualifiers.addObject(qual);
qual = EOQualifier.qualifierWithQualifierFormat(major
caseInsensitiveLike %s, new NSArray(selectedMajor.name()));
theQualifiers.addObject(qual);
EOFetchSpecification fs = new EOFetchSpecification(StudentRecord,
new EOAndQualifier(theQualifiers), null);
LOGGER.debug(Get the DoctorRecords with qualifiers = + new
EOAndQualifier(theQualifiers).toString());
fs.setPrefetchingRelationshipKeyPaths(preFetchKeyPaths);
filteredDoctors = ec.objectsWithFetchSpecification(fs);
The problem occurs if a Student happens to have the same address as a
Teacher or School. The SQL that's generated for the above fetch is as
follows:
[2007-11-06 09:33:14 EST] WorkerThread1 evaluateExpression:
com.webobjects.jdbcadaptor.OpenBasePlugIn$OpenBaseExpression:
SELECT t0.MAJOR, t0.EMAIL_ADDRESS, t0.FIRST_NAME, t0.LAST_NAME, ...,
FROM STUDENT_RECORD t0, STATE T2, LOCATION T1 WHERE (UPPER
(T2.ABBREVIATION) LIKE UPPER(?) AND UPPER(T1.CITY) LIKE UPPER(?) AND
UPPER(t0.MAJOR) LIKE UPPER(?)) AND T1.STATE_ID = T2.OID AND t0.OID =
T1.PARTY_ID withBindings: 1:NY(abbreviation), 2:New York(city),
3:Underwater Basketweaving(major)
I don't understand why EOF doesn't automatically add the WHERE
clause: t0.LOCATION_TYPE = ? AND .
Notice the setPrefetchingRelationshipKeyPaths statement. That causes
the generation of the following SQL statements as well, which EACH
INCLUDE THE LOCATION_TYPE CLAUSE appropriately:
[2007-11-08 07:33:14 EST] WorkerThread1 evaluateExpression:
com.webobjects.jdbcadaptor.OpenBasePlugIn$OpenBaseExpression:
SELECT t0.ADDRESS_1, t0.ADDRESS_2, t0.CITY, t0.PARTY_ID,
t0.LOCATION_TYPE, t0.OID, t0.PHONE_NUMBER, t0.POSTAL_CODE,
t0.STATE_ID, t0.ZIP_CODE_ID FROM LOCATION t0, STUDENT T1, STATE T2
WHERE (t0.LOCATION_TYPE = ? AND (UPPER(T1.MAJOR) LIKE UPPER(?) AND
UPPER(t0.CITY) LIKE UPPER(?) AND UPPER(T2.ABBREVIATION) LIKE UPPER
(?))) AND t0.PARTY_ID = T1.OID AND t0.STATE_ID = T2.OID
withBindings: 1:6(locationType), 2:Underwater Basketweaving(major),
3:New York(city), 4:NY(abbreviation)
[2007-11-08 07:33:14 EST] WorkerThread1 evaluateExpression:
com.webobjects.jdbcadaptor.OpenBasePlugIn$OpenBaseExpression:
SELECT DISTINCT t0.ABBREVIATION, t0.NAME, t0.OID FROM STATE t0,
LOCATION T1, STUDENT T2 WHERE ((UPPER(t0.ABBREVIATION) LIKE UPPER(?)
AND UPPER(T1.CITY) LIKE UPPER(?) AND UPPER(T2.MAJOR) LIKE UPPER(?))
AND T1.LOCATION_TYPE = ?) AND
Re: Slogan
OR: WebObjects: Less Tar, More Taste On Nov 7, 2007, at 10:25 AM, Michael Kondratov wrote: OR: Easy things are easy and hard things are possible. On Nov 7, 2007, at 5:49 AM, Pierre Bernard wrote: +1 On Nov 5, 2007, at 12:41 PM, Mitchel Roider wrote: Imagine - WebObjects - Deploy - - - Houdah Software s. à r. l. http://www.houdah.com HoudahGeo: One-stop photo geocoding HoudahSpot: Powerful Spotlight frontend ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/michael% 40aspireauctions.com This email sent to [EMAIL PROTECTED] ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/mmwarner% 40mac.com This email sent to [EMAIL PROTECTED] ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
Re: ENOUGH ALREADY: Slogan
Please, please, please, I beg you - move this to WO-Talk. Or better, just stop with the awful slogans. On Nov 8, 2007, at 9:00 AM, Anjo Krank wrote: This thread was fun for the first two posts but it's gotten so old it smells, so please move it to wo-talk before something bad happens. Cheers, Anjo ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/chill% 40global-village.net This email sent to [EMAIL PROTECTED] -- Practical WebObjects - for developers who want to increase their overall knowledge of WebObjects or who are trying to solve specific problems. http://www.global-village.net/products/practical_webobjects ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
ENOUGH ALREADY: Slogan
This thread was fun for the first two posts but it's gotten so old it smells, so please move it to wo-talk before something bad happens. Cheers, Anjo ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
Re: Slogan
WebObjects - The function behind the form. (use the WO gear logo behind a Web or Java UI front) WebObjects - Making Java concise since 1996. ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
Re: Slogan
OR: WebObjects: Powering the Web since 1996 OR: WebObjects. Founded 1996. Going strong OR: WebObjects: Where the competition failed. OR: Get WebObjects now, or learn a lesson OR: WebObjects: Web application fast track OR: Man, that was WebObjects! OR: WebObjects: Would you believe? You should! On Nov 8, 2007, at 5:03 PM, Michael Warner wrote: OR: WebObjects: Less Tar, More Taste On Nov 7, 2007, at 10:25 AM, Michael Kondratov wrote: OR: Easy things are easy and hard things are possible. On Nov 7, 2007, at 5:49 AM, Pierre Bernard wrote: +1 On Nov 5, 2007, at 12:41 PM, Mitchel Roider wrote: Imagine - WebObjects - Deploy - - - Houdah Software s. à r. l. http://www.houdah.com HoudahGeo: One-stop photo geocoding HoudahSpot: Powerful Spotlight frontend ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/michael%40aspireauctions.com This email sent to [EMAIL PROTECTED] ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/mmwarner%40mac.com This email sent to [EMAIL PROTECTED] ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/webobjects-lists%40houdah.com This email sent to [EMAIL PROTECTED] - - - Houdah Software s. à r. l. http://www.houdah.com HoudahGeo: One-stop photo geocoding HoudahSpot: Powerful Spotlight frontend ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
Re: ENOUGH ALREADY: Slogan
This thread was fun for the first two posts but it's gotten so old it smells, so please move it to wo-talk before something bad happens. Or just send the slogans directly to me. ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
5.4 API diff javadoc?
Have I missed this? I am not able to find it. There should be a javadoc for the differences between the WO 5.3 API and the WO 5.4 API. If Apple has not generated this, has anybody outside of Apple generated this yet? thanx - ray ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
Re: deep down NPE in EOF
Ken Anderson wrote on 11/5/07 9:04 AM:
Since you state that all StoredName objects have MyAppPerson data, why
not just fetch MyAppPerson initially and have a to-one relationship back
to StoredName?
This is what I wound up doing. I didn't like that approach at first
because it seemed to unnecessarily clutter up the database (if
MyAppPerson has relationships but no attributes, it is exactly the
equivalent of a StoredName). But if imagine that maybe at some point in
the future, MyAppPerson will have attributes, then it clearly becomes an
EO that needs to be modeled separately.
With this implementation, EOF is now happy.
zak.
On Nov 4, 2007, at 7:32 PM, Chuck Hill wrote:
On Nov 4, 2007, at 8:09 AM, Zak Burke wrote:
I'm getting a strange NPE from deep down in EOF that I can't figure
out. I think it might be related to some slightly funky modeling I'm
doing,
It is. :-)
but my EOs work fine in other places so I'm not sure why they're
broken here.
Here's the funkiness: I have two models -- NameStore and MyApp.
NameStore contains a single EO, StoredName. MyApp has an EO
MyAppPerson that extends StoredName, but the restricting qualifier is
just id 0, that is, all StoredName EOs are MyAppPerson EOs.
Basically, we have lots of (non-WO) apps that use the StoredName
table and have their own tables joined to it. I modeled it in WO this
way to keep the NameStore EO pristine -- all it does is hand out
names -- while allowing other apps to tack things onto a local EO
that extends StoredName.
What I want to do is retrieve a StoredName and then bless it into
existence by re-fetching it as a MyAppPerson
Can't. When you fetch it as a StoredName, EOF associates the GlobalID
with that entity. When you re-fetch it as MyAppPerson, EOF will
still treat it as a StoredName.
You are going to have to fetch it as a MyAppPerson the first time.
Chuck
so I can access all its related objects. Because the StoredName and
the MyAppPerson share the same primary key value, I'm just passing
storedName.id() to a MyAppPerson method that retrieves items by their
PKs.
try {
return (MyAppPerson) EOUtilities.objectMatchingKeyAndValue(ec,
MyAppPerson.ENTITY_NAME, MyAppPerson.ID_KEY, id);
} catch (EOObjectNotAvailableException e) {
throw new RuntimeException(An MyAppPerson identified by + id +
could not be found.);
} catch (EOUtilities.MoreThanOneException e) {
throw new RuntimeException(More than one MyAppPerson identified by
+ id + was found.);
}
The fetch works fine; I get an object back. But EOF explodes when I
true access it, even just item.toString() to print it to a log
(stacktrace below). It appears to be exploding after traversing an
optional to-many join. I can use MyAppPerson items elsewhere so I
don't think I have modeling errors, but, well, I'm totally stumped.
Any ideas?
TIA,
zak.
___
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
Re: 5.4 API diff javadoc?
On Nov 8, 2007, at 10:56 AM, David Holt wrote: http://developer.apple.com/documentation/MacOSXServer/Reference/ WO54_Reference/deprecated-list.html Is this what you're looking for? David Only if no additions at all were made. Some things were made public, yes? See http://developer.apple.com/documentation/WebObjects/Reference/API/ changes.html This page above gives the API differences between WO 5.2.4 and WO 5.3. I had generated pages for many of the other upgrades and I am not seeing any of those, nor do I see a 5.3.* - 5.4 page. - ray On 8-Nov-07, at 10:42 AM, Ray Kiddy wrote: Have I missed this? I am not able to find it. There should be a javadoc for the differences between the WO 5.3 API and the WO 5.4 API. If Apple has not generated this, has anybody outside of Apple generated this yet? thanx - ray ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/ programmingosx%40mac.com This email sent to [EMAIL PROTECTED] ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
access to flattened relationship EOs
I have two EO classes joined in a flattened many-to-many relationship (User -- UserGroupJoin -- Group). UserGroupJoin is dead-simple -- nothing but foreign keys to User and Group. I want to log whenever one of the join items is created or removed. The UI for this is a UserEdit page with Group items in checkboxes, and, likewise, a GroupEdit page with User items in checkboxes. I use a custom EC subclass, so I thought I'd create the log by checking for UserGroupJoin items in insertedObjects() and deletedObjects() during saveChanges(). Well, they never show up there. So then I tried adding logging to UserGroupJoin.awakeFromInsertion(). That isn't called either. Does anybody know how I can get at this information? zak. ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
Re: WO5.4 and Java Client
Argh, I shouldn't have relied on my memory. What I meant was the WebServicesAssistant.app, which is only a WOA that is repackaged as an app. Sorry. But then I don't know why D2JC is deprecated at all, except that all the cocoa components are most likely broken and they didn't want to provide an IB replacement or conversion tool. Cheers, Anjo Am 08.11.2007 um 20:22 schrieb David Avendasora: Hey Anjo, Can you give me more information or examples of getting assistant to use normal WO files? That would help me a lot right now. I would also very much like to try to get D2JC unDEpreciated even if it does remain unAppreciated. :) Thanks, Dave On Nov 4, 2007, at 2:56 PM, Anjo Krank wrote: Am 01.11.2007 um 20:33 schrieb David Avendasora: I know I'm planning on digging into it soon because a large portion of my application is D2JC, which will need to be replaced. Again: D2JC is deprecated, but wrongly so. If you know how to write individual components by hand, then you should file a radar to get the assistant to use normal WO files and not the D2JC stub (sth you can easily do yourself). Also again: I have no idea if the JC stuff will be brought forward or not, but at least you don't *need* to rewrite your interfaces. Cheers, Anjo ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
Re: WO5.4 and Java Client
Hey Anjo, Can you give me more information or examples of getting assistant to use normal WO files? That would help me a lot right now. I would also very much like to try to get D2JC unDEpreciated even if it does remain unAppreciated. :) Thanks, Dave On Nov 4, 2007, at 2:56 PM, Anjo Krank wrote: Am 01.11.2007 um 20:33 schrieb David Avendasora: I know I'm planning on digging into it soon because a large portion of my application is D2JC, which will need to be replaced. Again: D2JC is deprecated, but wrongly so. If you know how to write individual components by hand, then you should file a radar to get the assistant to use normal WO files and not the D2JC stub (sth you can easily do yourself). Also again: I have no idea if the JC stuff will be brought forward or not, but at least you don't *need* to rewrite your interfaces. Cheers, Anjo ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
Re: WO5.4 and Java Client
Hi Florijan, it's because the core jc stuff still stays that I think It's reasonable to continue to use in the jc application EODisplayGroup, EOAssociation, etc. I think the status is like as the web WO where the core stuff stays but WebObjects Builder is lacking. In the jc client development the core stuff largely stays but now Interface Builder is lacking. Doubtless in my xml binding approach, to edit by hands a xml file is'nt fun as to play with Interface Builder but it's much better that to hardcode in the gui java class all the EODisplayGroup, EOAssociation code. The gui java class remain a pure swing class, the needed EODisplayGroup, EOAssociation, etc. stuff are automagically added following the binding described in the xml file. One have to extends the gui class as EOApplication but this requiremet is just only to start the application, in order to do the applicationClassName binding in JavaClient.wo working, as you has described in your WebObjects Java Client tutorial. Furthermore, in the future one can creates a visually tool, an eclipse plugin or other, which can generate the xml file Regards Paolo Il giorno 08/nov/07, alle ore 03:05, Florijan Stamenkovic ha scritto: Thanks to all, and apologies as well, last time I checked (a few days ago) I was unable to locate the 5.4 API online, possibly to my own stupidity. My best, Flor On Nov 07, 2007, at 14:09, Mike Schrag wrote: Could we stop the speculation and look at the facts. The documentation is here: http://developer.apple.com/documentation/MacOSXServer/Reference/WO54_Reference/ .. and also http://developer.apple.com/documentation/MacOSXServer/Reference/WO54_Reference/deprecated-list.html ms ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/flor385%40mac.com This email sent to [EMAIL PROTECTED] ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/psomma%40jpaso.com This email sent to [EMAIL PROTECTED] -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
Re: 5.4 API diff javadoc?
+1 This document would be very usefull. Ray Kiddy a écrit : Have I missed this? I am not able to find it. There should be a javadoc for the differences between the WO 5.3 API and the WO 5.4 API. If Apple has not generated this, has anybody outside of Apple generated this yet? -- Francis Labrie, System Architect, OS communications informatiques - Your communication engine [EMAIL PROTECTED] | Phone: (450) 676-1238 ext. 27 | Fax: (450) 676-5276 ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
Re: Editing Contexts and Autorelease Pools in 4.5.1
On 11/8/07 7:00 AM, Patrick Middleton wrote: My dealings with multiple ECs in WO4.5.1 were -- indeed, are -- mostly to do with either nested ECs or ECs being worked in separate threads. I found when doing something time consuming, it was necessary to do it in a separate thread, and it was best to use a separate EC which I could lock and unlock as needed to avoid risking have the session's default EC be locked by a detached thread at a time when the session wanted to lock it because of servicing a page request. Yes, locking the EC will cause it to create a new NSAutoreleasePool, and yes, there are various things you can do such as -reset that will cuase the EC to lock itself. NSAutoreleasePools are stacked, so there is lots of scope to be bitten, and the best solution I can see is unlock the peer ECs in the reverse order to which they were locked, as described. Then I'm not crazy! I was wondering if there was just something I wasn't understanding. NSAutoreleasePools are stacked per thread (and it says so in the class reference documentation). If you had each EC in a different thread, then you wouldn't encounter the problem you have -- rather, a whole bunch of different problems instead. I found that getting editing contexts to deallocate cleanly was a severe pain, because EOF hacks -dealloc for objects managed by ECs, and I was frequently hitting problems where something that was doing a pretend-to-deallocate-now-but-really-deallocate-later because of EOF was causing crashes when it actually did deallocate, because it had references to other parts of the EOF object graph which had already genuinely deallocated. This fits the intermittent errors that I'm seeing and makes a lot of sense now. Crud. Although I can't find the bit of documentation that says so (ie, it's not in the class reference documentation), it's my understanding that when an NSAutoreleasePool is released, any child NSAutoreleasePools -- necessarily stacked -- will also be released, and this would be a severe nuisance. Yes, this is exactly what happens. Having reviewed Jonathan's original code, if we are working solely with peer ECs, do we really need MultiECLockManager? If all I needed was some convenience for ensuring that when I was finished, all ECs of interest were sent the right number of -unlock messages, I'd refactor this (or write something else) so that each editing context had its own lock count, and I could lock or unlock any managed EC (or query its lock count) via my manager object. That way, I could unlock ECs when they no longer needed to be locked ... except if I lock A then lock B, I cannot let the lock count for A fall to 0 until the lock count for B has fallen to 0 because of the stacked NSAutoreleasePool problem. Hmmm. This whole matter would be much simpler if one could refactor one's code to ensure that a maximum of 1 peer editing contexts was ever concurrently locked. I've started down the exact same train of thought. While debugging and trying to figure out the whole autorelease pool stack thing, I did write a category for EOEditingContext that exposed some ivars, namely lockCount and lockPool. I could use that to track the lock count, at least. Thank you for your response! I really thought I had to be missing something here, but at least it is nice to know that I'm not. -- - Dana Kashubeck Systems Manager Riemer Reporting Service Inc. http://www.riemer.com Phone: 440-835-2477 x. 125 Fax: 440-835-4594 - begin:vcard fn:Dana Kashubeck n:Kashubeck;Dana org:Riemer Reporting Service, Inc.;MIS adr:Suite 100;;24600 Detroit Road;Westlake;Ohio;44135;United States of America email;internet:[EMAIL PROTECTED] title:Systems Manager tel;work:440-835-2477 ext. 125 tel;fax:440-835-4594 x-mozilla-html:FALSE url:http://www.riemer.com version:2.1 end:vcard smime.p7s Description: S/MIME Cryptographic Signature ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
Re: 5.4 API diff javadoc?
+1 Also, documentation on the new features besides just the vague API reference. On Nov 8, 2007, at 2:32 PM, Francis Labrie wrote: +1 This document would be very usefull. Ray Kiddy a écrit : Have I missed this? I am not able to find it. There should be a javadoc for the differences between the WO 5.3 API and the WO 5.4 API. If Apple has not generated this, has anybody outside of Apple generated this yet? -- Francis Labrie, System Architect, OS communications informatiques - Your communication engine [EMAIL PROTECTED] | Phone: (450) 676-1238 ext. 27 | Fax: (450) 676-5276 ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/grhodes%40thissmallworld.com This email sent to [EMAIL PROTECTED] ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
Re: 5.4 API diff javadoc?
The documentation for this release seems to be really lacking. I've seen the deprecation list, the JavaDocs, the fixed issues, and the file schema. But there's nothing that talks about the new APIs that were added. For example, the JavaDocs mention a host of new methods, classes, and fields for working with AJAX (such as http://developer.apple.com/documentation/MacOSXServer/Reference/WO54_Reference/com/webobjects/appserver/WOSession.PageFragmentCache.html) . But the JavaDocs only mention their purpose but not really how to implement them properly. I can probably poke around at them and figure it out to some degree but proper documentation would save a LOT of time. Even some sample code would help out a lot here. On Nov 8, 2007, at 2:49 PM, Ray Kiddy wrote: On Nov 8, 2007, at 10:56 AM, David Holt wrote: http://developer.apple.com/documentation/MacOSXServer/Reference/WO54_Reference/deprecated-list.html Is this what you're looking for? David Only if no additions at all were made. Some things were made public, yes? See http://developer.apple.com/documentation/WebObjects/Reference/API/changes.html This page above gives the API differences between WO 5.2.4 and WO 5.3. I had generated pages for many of the other upgrades and I am not seeing any of those, nor do I see a 5.3.* - 5.4 page. - ray On 8-Nov-07, at 10:42 AM, Ray Kiddy wrote: Have I missed this? I am not able to find it. There should be a javadoc for the differences between the WO 5.3 API and the WO 5.4 API. If Apple has not generated this, has anybody outside of Apple generated this yet? thanx - ray ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/programmingosx%40mac.com This email sent to [EMAIL PROTECTED] ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/grhodes%40thissmallworld.com This email sent to [EMAIL PROTECTED] ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
