WOLips Problem Occured

2008-07-08 Thread Gennady Kushnir
Hello, List I have problems with my Eclipse IDE (3.3.2) with WOLips 3.3.5047 Every time I configure frameworks it shows me Problem Occured error message: } WOLips Include Files Updates } Attempted to beginRule: R/, does not match outer scope rule: P/Rujel I don't get what it means. But as a

Re: EOFetchSpecification text to number conversion

2008-07-08 Thread Pierre Bernard
On 7 Jul 2008, at 18:55, Chuck Hill wrote: I can't think of any. This is yet another reason to never use qualifierWithQualifierFormat. If you had used EOKeyValueQualifier, you would not have this problem. Just say no to magic strings. Does EOF again apply automatic coercion? I found

Re: empty relationship qualifier question

2008-07-08 Thread Michael Bushkov
Hi, Pierre! Thanks for the answer. I've actually tried using EOKeyValueQualifier(tracks, EOQualifier.QualifierOperatorEquals, NSKeyValueCoding.NullValue). It generates the following sql, which is just wrong: SELECT RTRIM(t0.artist), t0.guitarProSongId, t0.id, RTRIM(t0.title) FROM Song t0 WHERE

Re: DB uniqueness constraints and dealing with them

2008-07-08 Thread Florijan Stamenkovic
A slightly modified version of Chuck's db specific stuff, for OpenBase: public class OpenBaseExInterpreter implements ExInterpreter{ private Pattern column = Pattern.compile(column \\'(.*)\\' is not unique), table = Pattern.compile(SQL\\: INSERT

Re: WOCollapsibleComponentContent is broken on Leopard

2008-07-08 Thread Xia, Wen
It works. Thanks a lot for your help! On 7/7/08 5:12 PM, Lachlan Deck [EMAIL PROTECTED] wrote: Hi Wen, On 08/07/2008, at 3:58 AM, Xia, Wen wrote: Seems like projects with WOCollapsibleComponentContent are broken after deploying to Leopard server (works on local Leopard). Error:

D2W and Qualifying Relationships

2008-07-08 Thread David Avendasora
Hi all, I have two to-one relationships on my Routing entity: Routing - ManufacturingLine Routing - WorkCenter ManufacturingLine and WorkCenter are also related with a many-to-many: ManufacturingLine - WorkCenter On the form for Routing, I'd like to restrict the possible options on the

Re: D2W and Qualifying Relationships

2008-07-08 Thread Guido Neitzer
If you have them on the same page, you need to do an Ajax call to set the manufacturingLine and than limit the other one with the restrictedChoiceKey in the rules. Never tried that though. cug On 08.07.2008, at 12:55, David Avendasora wrote: I have two to-one relationships on my Routing

WOXMLDecoder and NSData

2008-07-08 Thread Steve Peery
I am upgrading a WO Application to version 5.4 and everywhere I use WOXMLDecoder to decode a NSData object it generates a NullPointerException. It worked fine before. Any clues? Steve ___ Do not post admin requests to the list. They will be ignored.

Re: D2W and Qualifying Relationships

2008-07-08 Thread David Avendasora
restrictedChoiceKey Hmmm Ahg! WOnder. Figures. :) I was hopping for a WO-only solution. Thanks for the quick reply though! Dave On Jul 8, 2008, at 3:45 PM, Guido Neitzer wrote: If you have them on the same page, you need to do an Ajax call to set the manufacturingLine and than

Re: D2W and Qualifying Relationships

2008-07-08 Thread Alan Ward
On Jul 8, 2008, at 2:09 PM, Chuck Hill wrote: On Jul 8, 2008, at 1:07 PM, David Avendasora wrote: restrictedChoiceKey Hmmm Ahg! WOnder. Figures. :) I was hopping for a WO-only solution. Thanks for the quick reply though! I thought The First Rule of D2W was D2W without Wonder

Re: WOXMLDecoder and NSData

2008-07-08 Thread Daryl Lee
Do you have a stacktrace? WO 5.4 was upgraded to use the sax2 parser. On Jul 8, 2008, at 1:05 PM, Steve Peery wrote: I am upgrading a WO Application to version 5.4 and everywhere I use WOXMLDecoder to decode a NSData object it generates a NullPointerException. It worked fine before. Any

Re: D2W and Qualifying Relationships

2008-07-08 Thread David Avendasora
On Jul 8, 2008, at 4:09 PM, Chuck Hill wrote: On Jul 8, 2008, at 1:07 PM, David Avendasora wrote: restrictedChoiceKey Hmmm Ahg! WOnder. Figures. :) I was hopping for a WO-only solution. Thanks for the quick reply though! I thought The First Rule of D2W was D2W without Wonder

Re: D2W and Qualifying Relationships

2008-07-08 Thread Guido Neitzer
On 08.07.2008, at 14:18, Alan Ward wrote: I thought The First Rule of D2W was D2W without Wonder is a deadlock waiting to happen I thought it was more like it's a deadlock that already happened ;-) That's probably pretty close ... cug -- http://www.event-s.net

Re: D2W and Qualifying Relationships

2008-07-08 Thread Chuck Hill
On Jul 8, 2008, at 1:24 PM, David Avendasora wrote: On Jul 8, 2008, at 4:09 PM, Chuck Hill wrote: On Jul 8, 2008, at 1:07 PM, David Avendasora wrote: restrictedChoiceKey Hmmm Ahg! WOnder. Figures. :) I was hopping for a WO-only solution. Thanks for the quick reply though! I

Re: WOXMLDecoder and NSData

2008-07-08 Thread Jake MacMullin
Speaking of using the SAX parser (and other XML apis), is there a good reason WebObjects contains a bunch of 3rd party libraries in the java- xml .jar? Couldn't these just be expressed as dependencies in the Maven project? Including specific versions of these libraries in one of the WO

Re: DB uniqueness constraints and dealing with them

2008-07-08 Thread Florijan Stamenkovic
Uhm sorry, that was partly bad. Matcher will not find any groups unless one of the matching methods is invoked on it first... The working version of the code is: public class OpenBaseExInterpreter implements ExInterpreter{ private Pattern column =

Re: WOXMLDecoder and NSData

2008-07-08 Thread Daryl Lee
On Jul 8, 2008, at 1:27 PM, Jake MacMullin wrote: Speaking of using the SAX parser (and other XML apis), is there a good reason WebObjects contains a bunch of 3rd party libraries in the java-xml .jar? Couldn't these just be expressed as dependencies in the Maven project? If everyone was

Re: WOXMLDecoder and NSData

2008-07-08 Thread Chuck Hill
On Jul 8, 2008, at 3:26 PM, Daryl Lee wrote: On Jul 8, 2008, at 1:27 PM, Jake MacMullin wrote: Speaking of using the SAX parser (and other XML apis), is there a good reason WebObjects contains a bunch of 3rd party libraries in the java-xml .jar? Couldn't these just be expressed as

SimpleDateFormat vs [Deprecated] NSTimestampFormatter

2008-07-08 Thread Gennady Kushnir
Hello list! As mentioned in WO 5.4 documentation NSTimestampFormatter class is now deprecated. They recommend using java.text.SimpleDateFormat instead. Pattern formats for NSTimestampFormatter and SimpleDateFormat a different. But when binding WOString and WOTextFiend it still takes patterns for

Re: SimpleDateFormat vs [Deprecated] NSTimestampFormatter

2008-07-08 Thread Chuck Hill
On Jul 8, 2008, at 3:59 PM, Gennady Kushnir wrote: Hello list! As mentioned in WO 5.4 documentation NSTimestampFormatter class is now deprecated. They recommend using java.text.SimpleDateFormat instead. Pattern formats for NSTimestampFormatter and SimpleDateFormat a different. But when binding

Re: empty relationship qualifier question

2008-07-08 Thread Gennady Kushnir
Очень похоже на ошибку в модели. Check your relationship tracks to be toMany is NULL behavior is usually for toOne relationships. 2008/7/8 Michael Bushkov [EMAIL PROTECTED]: Hi, Pierre! Thanks for the answer. I've actually tried using EOKeyValueQualifier(tracks,

Re: SimpleDateFormat vs [Deprecated] NSTimestampFormatter

2008-07-08 Thread Gennady Kushnir
NSTimestampFormatter also understands the SimpleDateFormat pattern symbols. Just use the SimpleDateFormat symbols for both. Does it work only for 5.4 or also for earler versions of WO? Gennady 2008/7/9 Chuck Hill [EMAIL PROTECTED]: On Jul 8, 2008, at 3:59 PM, Gennady Kushnir wrote: Hello

Re: SimpleDateFormat vs [Deprecated] NSTimestampFormatter

2008-07-08 Thread Chuck Hill
On Jul 8, 2008, at 4:10 PM, Gennady Kushnir wrote: NSTimestampFormatter also understands the SimpleDateFormat pattern symbols. Just use the SimpleDateFormat symbols for both. Does it work only for 5.4 or also for earler versions of WO? NSTimestampFormatter has always understood the

Re: WOLips Problem Occured

2008-07-08 Thread Lachlan Deck
On 08/07/2008, at 5:03 PM, Gennady Kushnir wrote: Hello, List I have problems with my Eclipse IDE (3.3.2) with WOLips 3.3.5047 Every time I configure frameworks it shows me Problem Occured error message: } WOLips Include Files Updates } Attempted to beginRule: R/, does not match outer

Maven Optimism

2008-07-08 Thread Pierce T . Wetter III
Last week, I posted a thread titled Maven Skepticism to the WOProject list. It was about my misgivings about Maven, and the issues I was having getting started with it. So the last few days I've been playing with Maven. I am no longer skeptical. So I thought I would post about my

Re: EOFetchSpecification text to number conversion

2008-07-08 Thread Lachlan Deck
On 08/07/2008, at 6:24 PM, Pierre Bernard wrote: On 7 Jul 2008, at 18:55, Chuck Hill wrote: I can't think of any. This is yet another reason to never use qualifierWithQualifierFormat. If you had used EOKeyValueQualifier, you would not have this problem. Just say no to magic strings.

Re: Maven Optimism

2008-07-08 Thread Lachlan Deck
On 09/07/2008, at 10:05 AM, Pierce T.Wetter III wrote: ... So I thought I would post about my newfound optimism with Maven. I feel I owe it to Henrique and Lachlan for their help. (Thanks guys) I also think the current maven evangelism documentation is written a little too formally to be

Re: Maven Optimism

2008-07-08 Thread Mike Schrag
Many of these jar files are duplicates of each other, or even worse, different versions of the same jar, like there is a version of commons-logging.jar in ERJGroupsSynchronizer and another one in EROpenID. Meanwhile, commons-logging is up to version 1.1.1. To my way of thinking, the

NPE on project import

2008-07-08 Thread Patrick Robinson
I asked about this last week on the WOLips list, but that was maybe the wrong place. I have eclipse 3.3.2 and the newest stable wolips (3.3.5311) on two machines (a powermac G5, and a Mac Book Pro), both still running Tiger. I have a project on my G5 that I need to import into eclipse on

Re: Maven Optimism

2008-07-08 Thread Anjo Krank
Am 09.07.2008 um 02:05 schrieb Pierce T.Wetter III: To give you some examples, for the current Wonder Ant builds, between build.xml files, generic.xml, build.properties files, .classpath and .patternset files, there are 5320 lines of build configuration information in the current Wonder

Re: Maven Optimism

2008-07-08 Thread Anjo Krank
Am 09.07.2008 um 06:16 schrieb Anjo Krank: Am 09.07.2008 um 02:05 schrieb Pierce T.Wetter III: To give you some examples, for the current Wonder Ant builds, between build.xml files, generic.xml, build.properties files, .classpath and .patternset files, there are 5320 lines of build

Re: Maven Optimism

2008-07-08 Thread Chuck Hill
Anjo: 1 Maven: 0 :-P On Jul 8, 2008, at 9:16 PM, Anjo Krank wrote: Am 09.07.2008 um 02:05 schrieb Pierce T.Wetter III: To give you some examples, for the current Wonder Ant builds, between build.xml files, generic.xml, build.properties files, .classpath and .patternset files, there