> If you want the benefits of using Scala, you need to go to the old idea that
> every editing context will need its own entirely separate EOF stack. There is
> an obvious mis-match in the conceptual frames here
As I said, I just glanced through it, but it seems to me that what scala is
do
Well, I grok groovy more than scala, but that isn't saying much. I
just see Grails as getting everything right about Java (for the most
part) and picking what was right about Rails. Liftweb seems to make my
brain hurt, and Play is a minimal Grails without half the traction to
getting things done.
Still haven't figured this one out so I downloaded and installed the Wonder
source so I can setup breakpoints in it. I see that my _rewriteURL should be
getting called by the ERXWOContext _postprocessURL function, so I put a break
point there. Moving up the chain, I also put breakpoints in:
On Mar 10, 2011, at 1:29 PM, Anjo Krank wrote:
> Just finished glancing through a Scala book... how do you implement faulting
> with it? You know: Bar bar = foo.getBar(). The only thing I saw is
> continuation-passing, which is async by nature?
>
> Cheers, Anjo
>
In order to use WO stuff wit
Just finished glancing through a Scala book... how do you implement faulting
with it? You know: Bar bar = foo.getBar(). The only thing I saw is
continuation-passing, which is async by nature?
Cheers, Anjo
Am 10.03.2011 um 21:18 schrieb Lachlan Deck:
> lift (for scala) is pretty cool.
>
> htt
lift (for scala) is pretty cool.
http://liftweb.net/
http://demo.liftweb.net/
http://exploring.liftweb.net/
On 11/03/2011, at 3:25 AM, Joe Little wrote:
> Grails is more similar to WO than Play though -- especially
> considering GORM approaches some of the niceties of EOF and Wonder
> qualifiers
Hi Markus,
I think a regular ERD2WEditToOneRelationship should do the trick for you.
100: task = 'edit' and smartRelatinship.isToMany != 1 and
smartRelationship.destinationEntity.name = "TechnicalDoc" => componentName =
ERD2WEditToOneRelationship [Assignment]
That will give you the full list.
Grails is more similar to WO than Play though -- especially
considering GORM approaches some of the niceties of EOF and Wonder
qualifiers. Both easier in the easy case, but harder when you have
multiple relationships (stuck with Hibernate criteria builders then)
On Wed, Mar 9, 2011 at 7:17 PM, Pa
On Mar 10, 2011, at 1:22 AM, Gennady Kushnir wrote:
> Hello all !
> I am wondering whether to turn on concurrent request handling on my
> deployment or not.
I always have this on.
> What are potential drawbacks of this? I assume there should be some.
> Why would it be off by default otherwise?
I have installed this update and have no problems with command line (ant)
build. Compile works fine. Check your ant installation and try this update
again.
Chuck
On Mar 9, 2011, at 5:46 AM, Alexander Spohr wrote:
> Hi list,
>
> after the March 8th 2011 Java update (javac 1.6.0_24) I can no
Sounds like your ant installation is messed up. I don't what it is supposed
to look like, but here is what I have:
john$ which ant
/usr/bin/ant
john$ ls -l /usr/bin/ant
lrwxr-xr-x 1 root wheel 22 Feb 17 16:01 /usr/bin/ant ->
/usr/share/ant/bin/ant
john$ ls -l /usr/share/ant
lrwxr-xr-x 1 root
Hi list,
after the March 8th 2011 Java update (javac 1.6.0_24) I can not compile using
ant any more:
BUILD FAILED
build.xml:204: taskdef A class needed by class
org.objectstyle.woproject.ant.WOCompile cannot be found:
org/apache/tools/ant/taskdefs/Javac
At first we thought it was the missing
HI Paul,
Sorry for the delay in reply...
The below issues are coming while opening a page in eclipse
Problems occurred when invoking code from plug-in:
"org.eclipse.ui.workbench".
Could not create action delegate for id:
org.objectstyle.wolips.wizards.actions.OpenWOComponentWizard
Plug-in org
Hello Gennady;
If you are having application-freezes on exceptions that may be another
problem and it may be best to conclusively sort that out rather than
work around it.
cheers.
On 10/03/11 10:22 PM, Gennady Kushnir wrote:
Hello all !
I am wondering whether to turn on concurrent request h
Hello all !
I am wondering whether to turn on concurrent request handling on my
deployment or not.
What are potential drawbacks of this? I assume there should be some.
Why would it be off by default otherwise?
I could not find anything interesting on this in documentation.
And another question: wo
15 matches
Mail list logo
