Re: Wonder javadoc missing?

2013-08-21 Thread Pascal Robert
Hum, I upgraded Jenkins this morning. I guess it broke something.

> Hi All,
> 
> I'm noticing that the javadoc has been missing for at least a couple of hours 
> now. Can someone take a look at this please? Or point me to an alternative 
> URL?
> 
> This is the URL I've been using:
> http://jenkins.wocommunity.org/job/Wonder/lastSuccessfulBuild/javadoc/?
> 
> Thanks,
> Ben
> ___
> 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:
> https://lists.apple.com/mailman/options/webobjects-dev/probert%40macti.ca
> 
> This email sent to prob...@macti.ca


 ___
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:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Wonder javadoc missing?

2013-08-21 Thread Benjamin Chew
Hi All,

I'm noticing that the javadoc has been missing for at least a couple of
hours now. Can someone take a look at this please? Or point me to an
alternative URL?

This is the URL I've been using:
http://jenkins.wocommunity.org/job/Wonder/lastSuccessfulBuild/javadoc/?

Thanks,
Ben
 ___
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:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: WOUnit testing with partial entities

2013-08-21 Thread Henrique Prange
Hi Paul,

That is exactly the problem some WOUnit's users are reporting. The only way I 
was able to reproduce this kind of issue in my own environment was by turning 
the unit tests execution parallel. Anyway, this causes me problems even with 
WOUnit 1.2. :(

So, I added a lot of logs and compared the execution of tests on WOUnit 1.2 and 
the latest version of WOUnit. Clearly, the current version is reusing the same 
model group between test executions. I've changed the way things are 
initialized and the logs look almost identical now. There's a new snapshot here 
[1] with the mentioned changes. Would you mind to try it?

[1]https://dl.dropboxusercontent.com/u/9599580/wounit-1.3-SNAPSHOT-3.jar

Cheers,

Henrique

On 17/08/2013, at 08:29, Paul Hoadley  wrote:

> Hi Henrique,
> 
> On 02/08/2013, at 9:08 AM, Henrique Prange  wrote:
> 
>> Good to hear.
>> 
>> I'm trying to solve another problem that seems related to the EOF 
>> initialization. I'm going to release a new version of WOUnit during the 
>> weekend (solving the other problem or not).
> 
> Just out of interest, what was the other problem you were having with EOF 
> initialisation?  I've updated to that 1.3-SNAPSHOT build across a range of 
> projects, and while it fixes the issue with partial entities, _some_ tests 
> that were passing under 1.2 are now failing, and it seems to be during EO 
> initialisation, for example setting up @Dummy EOs.  Worse, everything is fine 
> in development, the tests are only failing once they hit the Jenkins build 
> server, which makes it awful to debug.
> 
> Here's an example stack trace at the point of failure, for what it's worth.  
> I'm a bit stumped.  Can you see anything meaningful?
> 
>   [junit] Testcase: 
> testToString(net.logicsquad.lssurvey.model.SurveyInstanceTest):   Caused an 
> ERROR
>   [junit] java.lang.reflect.InvocationTargetException
>   [junit] com.webobjects.foundation.NSForwardException 
> [java.lang.reflect.InvocationTargetException] 
> null:java.lang.reflect.InvocationTargetException
>   [junit] at 
> com.webobjects.foundation._NSUtilities._explainInstantiationException(_NSUtilities.java:626)
>   [junit] at 
> com.webobjects.foundation._NSUtilities.instantiateObjectWithConstructor(_NSUtilities.java:665)
>   [junit] at 
> com.webobjects.eoaccess.EOEntityClassDescription.createInstanceWithEditingContext(EOEntityClassDescription.java:242)
>   [junit] at 
> com.wounit.rules.MockEditingContext.createSavedObject(MockEditingContext.java:216)
>   [junit] at 
> com.wounit.rules.MockEditingContext.createSavedObject(MockEditingContext.java:177)
>   [junit] at 
> com.wounit.rules.MockEditingContext$DummyFacade.create(MockEditingContext.java:83)
>   [junit] at 
> com.wounit.rules.AnnotationProcessor.createEOForType(AnnotationProcessor.java:49)
>   [junit] at 
> com.wounit.rules.AnnotationProcessor.initializeObject(AnnotationProcessor.java:172)
>   [junit] at 
> com.wounit.rules.AnnotationProcessor.process(AnnotationProcessor.java:205)
>   [junit] at 
> com.wounit.rules.MockEditingContext.before(MockEditingContext.java:149)
>   [junit] at 
> com.wounit.rules.AbstractEditingContextRule$1.evaluate(AbstractEditingContextRule.java:160)
>   [junit] Caused by: java.lang.reflect.InvocationTargetException
>   [junit] at 
> java.lang.reflect.Constructor.newInstance(Constructor.java:532)
>   [junit] at 
> com.webobjects.foundation._NSUtilities.instantiateObjectWithConstructor(_NSUtilities.java:659)
>   [junit] Caused by: java.lang.NullPointerException
>   [junit] at 
> com.webobjects.eoaccess.EOModel.createPrototypeCache(EOModel.java:631)
>   [junit] at 
> com.webobjects.eoaccess.EOModel.prototypeAttributeNamed(EOModel.java:699)
>   [junit] at 
> com.webobjects.eoaccess.ERXModel.prototypeAttributeNamed(ERXModel.java:315)
>   [junit] at 
> com.webobjects.eoaccess.EOAttribute.(EOAttribute.java:998)
>   [junit] at 
> com.webobjects.eoaccess.EOEntity.attributes(EOEntity.java:816)
>   [junit] at 
> com.webobjects.eoaccess.EOEntity.attributeNamed(EOEntity.java:789)
>   [junit] at 
> com.webobjects.eoaccess.EOEntity.classProperties(EOEntity.java:1098)
>   [junit] at 
> com.webobjects.eoaccess.EOEntity._propertyDictionaryInitializer(EOEntity.java:3321)
>   [junit] at 
> com.webobjects.eoaccess.EOEntity._newDictionaryForProperties(EOEntity.java:3667)
>   [junit] at 
> com.webobjects.eoaccess.EOEntityClassDescription._newDictionaryForProperties(EOEntityClassDescription.java:88)
>   [junit] at 
> com.webobjects.eocontrol.EOGenericRecord.__setClassDescription(EOGenericRecord.java:111)
>   [junit] at 
> com.webobjects.eocontrol.EOGenericRecord.__setClassDescription(EOGenericRecord.java:100)
>   [junit] at 
> com.webobjects.eocontrol.EOGenericRecord.(EOGenericRecord.java:73)
>   [junit] at 
> er.extensions.eof.ERXGenericRecord.(ERXGenericRecord.java:102)
>   [junit] at 
> net.logicsquad.webobjects.core.eof.LSGener

OT: Has anybody worked with DMQL and/or RETS?

2013-08-21 Thread Johnny Miller
Hi,

Not a lot of information on the web about this stuff and I just have a couple 
of noob questions.

Aloha,
Mr. Johnny Miller
Web Development Manager
Kahalawai Media Company
Lahaina, HI 96761
tel: (808) 661-7962 | mobile: (808) 283-0791
website | e-mail

 ___
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:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: unique contraint error

2013-08-21 Thread Ramsey Gurley
http://thecodinglove.com/post/49933241299/when-i-start-using-a-3rd-party-lib-and-notice-there-is

ERXValidationFactory.templateForEntityPropertyType determines what keys are 
considered for most validation messages. In order, they are

entity.property.type
entity.property
property.type
property
type

So let's say you have an EO named Document with a mandatory title attribute. 
Leaving that blank would result in a NullPropertyException type validation 
error. So, your keys would be from most specific to least:

Document.title.NullPropertyException
Document.title
title.NullPropertyException
title
NullPropertyException

Typically, the least specific key is already defined in Wonder's 
ValidationTemplate.strings in the frameworks.

"NullPropertyException" = "Please provide @@indefiniteArticleForProperty@@ 
@@displayNameForProperty@@.";

You can override these with the more specific keys.

In this specific case, the validation template string is actually defined 
elsewhere. It's the result of an EOGeneralAdaptorException being converted into 
a standard validation exception in the ERXSQLHelper. You can find it in the 
PostgresqlSQLHelper.handleDatabaseException method.

On Aug 21, 2013, at 10:22 AM, Christoph Wick wrote:

> Is there a documentation about the possible keys for that? What kinds of keys 
> can I put into a ValidationTemplates.string?
> 
> Thx, C.U.CW
> -- 
> What are the three enemies of a programmer? Sunlight, oxygen, and the 
> appalling roar of the birds.
> 
> On 14.08.2013, at 04:07, Theodore Petrosky  wrote:
> 
>> wow, that's beautiful
>> 
>> 
>> 
>> On Aug 13, 2013, at 8:45 PM, Paul Hoadley  wrote:
>> 
>>> Hi Ted,
>>> 
>>> On 14/08/2013, at 10:03 AM, Theodore Petrosky  wrote:
>>> 
 I added an index and unique constraint to my User. loginName column. 
 
 I see in the logs that when I try to violate the uniqueness my d2w does 
 the correct thing and complain however this is the error:
 
 Could not save your changes: CustomMethodException
 
 I do see in the logs:
 
 ERROR: duplicate key value violates unique constraint "loginname_idx"
 
 did I miss something in a rule to pass the better worded error message to 
 the user?
>>> 
>>> Create Resources/English.lproj/ValidationTemplate.strings and add:
>>> 
>>> {
>>> "UniqueConstraintException.loginname_idx" = "Please choose a different 
>>> username.";
>>> }
>>> 
>>> Does that work?
>>> 
>>> 
>>> -- 
>>> Paul Hoadley
>>> http://logicsquad.net/
>>> 
>>> 
>>> 
>> 
>> 
>> ___
>> 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:
>> https://lists.apple.com/mailman/options/webobjects-dev/wicki%40me.com
>> 
>> This email sent to wi...@me.com
> 
> 
> ___
> 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:
> https://lists.apple.com/mailman/options/webobjects-dev/rgurley%40smarthealth.com
> 
> This email sent to rgur...@smarthealth.com


 ___
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:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: unique contraint error

2013-08-21 Thread Christoph Wick
Is there a documentation about the possible keys for that? What kinds of keys 
can I put into a ValidationTemplates.string?

Thx, C.U.CW
-- 
What are the three enemies of a programmer? Sunlight, oxygen, and the appalling 
roar of the birds.

On 14.08.2013, at 04:07, Theodore Petrosky  wrote:

> wow, that's beautiful
> 
> 
> 
> On Aug 13, 2013, at 8:45 PM, Paul Hoadley  wrote:
> 
>> Hi Ted,
>> 
>> On 14/08/2013, at 10:03 AM, Theodore Petrosky  wrote:
>> 
>>> I added an index and unique constraint to my User. loginName column. 
>>> 
>>> I see in the logs that when I try to violate the uniqueness my d2w does the 
>>> correct thing and complain however this is the error:
>>> 
>>> Could not save your changes: CustomMethodException
>>> 
>>> I do see in the logs:
>>> 
>>> ERROR: duplicate key value violates unique constraint "loginname_idx"
>>> 
>>> did I miss something in a rule to pass the better worded error message to 
>>> the user?
>> 
>> Create Resources/English.lproj/ValidationTemplate.strings and add:
>> 
>> {
>>  "UniqueConstraintException.loginname_idx" = "Please choose a different 
>> username.";
>> }
>> 
>> Does that work?
>> 
>> 
>> -- 
>> Paul Hoadley
>> http://logicsquad.net/
>> 
>> 
>> 
> 
> 
> ___
> 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:
> https://lists.apple.com/mailman/options/webobjects-dev/wicki%40me.com
> 
> This email sent to wi...@me.com


 ___
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:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: where do I look

2013-08-21 Thread David Avendasora
Hi Ted,

Since every DB engine has it's own way of expressing discontent with constraint 
violations, some of which include the name of the constraint, and/or possibly 
the type (UNIQUE, CHECK, etc) and/or nothing it has been left as an exercise 
for the developer to parse the exception text returned by the database and then 
do something about it.

I've started naming all my constraints explicitly instead of letting FrontBase 
name them something completely meaningless. I can therefor use a REGEX to parse 
the error (because FrontBase will tell you the name of the constraint violated, 
but not the type)

For example:

NOT NULL constraints get named "NN.TABLE_NAME.COLUMN_NAME" and UNIQUE constrats 
are: "UNQ.TABLE_NAME.COLUMN_NAME.ANOTHER_COLUMN_NAME"

If you just create a column and specify it as not null in the column definition 
you get a constraint name like _C123 which is somewhat less than useful…

Dave

On Aug 17, 2013, at 11:04 AM, Theodore Petrosky  wrote:

> 
> UniqueConstraintException is defined in ERXSQLHelper as a response in method 
> "handleDatabaseException".
> 
> what about the rest of the exceptions? if I insert a alpha keystroke into a 
> currencyAmount prototype, how can I adjust the message similar to:
> 
> "UniqueConstraintException.loginname_idx" = "Please choose a different 
> username.";
> 
> in the ValidationTemplate.strings
> ___
> 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:
> https://lists.apple.com/mailman/options/webobjects-dev/webobjects%40avendasora.com
> 
> This email sent to webobje...@avendasora.com



—
WebObjects - so easy that even Dave Avendasora can do it!™
—
David Avendasora
Senior Software Abuser
Nekesto, Inc.





 ___
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:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: new Wonder app ??

2013-08-21 Thread Pascal Robert
Common best practice: having a common class for components...

> is there a "Best Practices" section on this? I will read up and see what it 
> means.
> 
> Ted
> 
> 
> On Aug 20, 2013, at 5:16 PM, prob...@macti.ca wrote:
> 
>> New since last year. For best practices.
>> 
>> Envoyé de mon iPhone
>> 
>> Le 2013-08-20 à 16:43, "Theodore Petrosky"  a écrit :
>> 
>>> I have not created a new wonder app in a long time. I just did and 
>>> something different happened. It created the normal Main component and an 
>>> extra .java called BaseComponent.java.
>>> 
>>> I have not noticed this before. what is it? is this something new?
>>> 
>>> Ted
>>> ___
>>> 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:
>>> https://lists.apple.com/mailman/options/webobjects-dev/probert%40macti.ca
>>> 
>>> This email sent to prob...@macti.ca
> 


 ___
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:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com