From: Anjo K. <ak...@pr...> - 2002-03-06 12:09:16
|
[moved from wonder-cvs to wonder-disc] Hi Patrice, > * BugTracker hobbles along for me (for bugs related stuff at least, haven't > tried test items). The initialization sequence you refer to should be > occurring automatically. There are bits in: > > - for Log4J in ERXExtensions static initializer (should be called > automatically since ERXExtensions is the principal class of the ERExtensions > framework) My fault. The Log4J wasn't initializing because I didn't have a config in my path. It would be good to note that at least something like this belongs in your WebObjects.properties: log4j.rootCategory=DEBUG, A1 log4j.appender.A1=org.apache.log4j.ConsoleAppender log4j.appender.A1.layout=er.extensions.ERXPatternLayout log4j.appender.A1.layout.ConversionPattern=%-5p %d{HH:mm:ss} (%-20c:%L) %x - %m%n log4j.category.er=INFO Also: ER[X]EntityClassDescription.registerDescription(); is commented out in the ERXExtensions...is there a reason for that? > - for ERD2WModel similary in the ERDirectToWeb static initializer > There should be no need for the explicit initialization Class c=ERDirectToWeb.class; in my app's constructor, because the framework does *not* load it's main class. The reason for this is: ak@linux:ak > cat /Library/Frameworks/ERDirectToWebJava.framework/Resources/Info.plist <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist SYSTEM "file://localhost/System/Library/DTDs/PropertyList.dtd"> <plist version="0.9"> <dict> <key>CFBundleDevelopmentRegion</key> <string>English</string> <key>CFBundleExecutable</key> <string>_WO$(SERVER_UNIQUIFIER)ERDirectToWebJava</string> <key>CFBundleInfoDictionaryVersion</key> <string>6.0</string> <key>CFBundlePackageType</key> <string>FMWK</string> <key>CFBundleSignature</key> <string>????</string> <key>CFBundleVersion</key> <string>0.0.1d1</string> <key>NSJavaNeeded</key> <string>YES</string> <key>NSJavaPath</key> <array> <string>_WO$(SERVER_UNIQUIFIER)ERDirectToWebJava.jar</string> </array> <key>NSJavaRoot</key> <string>Versions/A/Resources/Java</string> </dict> </plist> Compare this to: ak@linux:ak > cat /Library/Frameworks/ERExtensionsJava.framework/Resources/Info.plist <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist SYSTEM "file://localhost/System/Library/DTDs/PropertyList.dtd"> <plist version="0.9"> <dict> <key>CFBundleDevelopmentRegion</key> <string>English</string> <key>CFBundleInfoDictionaryVersion</key> <string>6.0</string> <key>CFBundlePackageType</key> <string>FMWK</string> <key>CFBundleSignature</key> <string>????</string> <key>CFBundleVersion</key> <string>0.0.1d1</string> <key>Has_WOComponents</key> <true/> <key>NSExecutable</key> <string>ERExtensionsJava</string> <key>NSJavaPathClient</key> <string>ERExtensionsJava.jar</string> <key>NSJavaRootClient</key> <string>WebServerResources/Java</string> <key>NSPrincipalClass</key> <string>er.extensions.ERXExtensions</string> </dict> </plist> So, the path to the jar not set correctly. I have *no* clue why this might be the case. Could someone else please verify this? > * As far as missing components (which ones are missing btw? for ex. The missing components is "ERDEditDateJavascript". The other errors I had where D2W "can't find page for ..." errors. In every case, either the d2w.d2wmodel was wrong or the missing initialisation was causing problems. > I know > the printer friendly rules are just pointing to the wrong component names at > the moment) and model glitches it's very likely those are just straight > bugs. Please go ahead and commit your fixes! As long as only normal files are concerned, I'll gladly fix the stuff I encounter but I'm running into problems with the .pbxproj folders. The way it works on my machine, I run into problems if I set the build location to some real path ("/Users/roots" or whatever) That is because "Application Server.build" has no project specific prefix and thus is shared amongst all open projects. Since this directory contains "JavaClasses" it get's overwritten at will and is confusing PB to no end. My solution is to set the INSTALL_PATH_FOR_STYLE = $(INSTALL_PATH) in the "Development" build style. Then the final framework lands in /Library/Frameworks and I reference them in other projects from this location. I have *no* clue if that is correct procedure or not, I just know that I had no end of trouble when I didn't do things that way. I'd be glad if someone with more insight (Bill?-) could help me a bit with that procedure...until then I'm very reluctant to commit my pbxproj's as this might seriously screw up builds for others. Some other points I'd like do/add/see soon: 1) add support for my "defaultValues" to ERXEntityClassDescription I sent to Max a while ago. It let's you set initial values in EOModeler (via a userInfo entry) so you don't need to write custom classes just to have some defaults. 2) add use of the CompilerProxy framework. This can only happen when the extra garbage files are removed because of the way the class names list it needs is created (something like 'grep package *.java|...'). So there mustn't be any other files in the project directory. 3) I added support for Mysql in the BugTracker model. Unfortunately, Mysql doesn't like "READ" and "TEXT" as column names, so I changed them to "READ_" and "TEXT_". Should I create a separate model or what should I do with it? 4) Once the ClassList.txt is up to date, move the texts into JavaDoc comments the respective classes and turn it into a more readable HTML page. 5) Re-Group the Components/Classes in the PBX Tree view. It is painfully slow with these many many files... Cheers, Anjo on 05.03.2002 19:39 Uhr, Patrice Gautier at pa...@ma... wrote: > Hi Anjo, > > > A few things: > > * wonder-cvs is not the ideal place to send discussion mail. It probably > should only be used by cvs itself, since a lot of us will have mail rules to > put those messages in different places. I've created a new list, > wonder-disc, which according to sourceforge should be available in the next > 24 hours. Details to follow.. > > * BugTracker hobbles along for me (for bugs related stuff at least, haven't > tried test items). The initialization sequence you refer to should be > occurring automatically. There are bits in: > > - for Log4J in ERXExtensions static initializer (should be called > automatically since ERXExtensions is the principal class of the ERExtensions > framework) > > - for ERD2WModel similary in the ERDirectToWeb static initializer > > > There should be no need for the explicit initialization > > * As far as missing components (which ones are missing btw? for ex. I know > the printer friendly rules are just pointing to the wrong component names at > the moment) and model glitches it's very likely those are just straight > bugs. Please go ahead and commit your fixes! > > > Thanks in advance for your help! > > > > -P > > > >> All: >> >> I'm currently trying to get BugTracker app to work...since I'm not very sure >> if I'm doing the right thing - has anyone tried to actually run the version >> in the CVS? It doesn't work (at least for long) if I don't add a bit of >> initialization in the constructor , like setting put the D2WModel and >> configuring Log4J. >> >> ERXLog4j.configureLogging(); >> Class c=ERD2WModel.class; // force initialization >> // Configures the system for trace rule firing. >> if (!WOApplication.application().isCachingEnabled()) { >> ERXLog4j.configureRapidTurnAround(); >> ERDirectToWeb.configureTraceRuleFiringRapidTurnAround(); >> } >> ERXEntityClassDescription.registerDescription(); >> >> This is copied from the wrox example. Also a few components are missing and >> I noticed several other things, like TestItem being a ERXGenericRecord in >> the model. Question is, should I put my "fixes" in CVS if I don't even know >> what's going on? >> >> And is this the right channel to post questions like this or is there some >> other place? >> >> Cheers, Anjo |