Re: Shale logo contest vote
Hi,
These are my preferences
1st choice: Andrei Dragomir{25}
2nd choice: Nik Wahlberg {66}
3rd choice: Binfel {78}
4th choice: Gulam Patel (Mikael) {38}
5th choice: Aide Chang {68}
Whilst this email has been checked for all known viruses, recipients should
undertake their own virus checking as Xansa will not accept any liability
whatsoever.
This email and any files transmitted with it are confidential and protected by
client privilege. It is solely for the use of the intended recipient.
Please delete it and notify the sender if you have received it in
error. Unauthorised use is prohibited.
Any opinions expressed in this email are those of the individual and not
necessarily the organisation.
Xansa, Registered Office: 420 Thames Valley Park Drive,
Thames Valley Park, Reading, RG6 1PU, UK.
Registered in England No.1000954.
t +44 (0)8702 416181
w www.xansa.com
Re: getbean method question
great explanations, but few more questions: * Embed the business logic in the event handlers (roughly corresponding to embedding business logic in an Action.execute() method in Struts. so i know if i push a button i can first call an event handlers and afterwards the specific action - so wouldn't be in both business logic? dont seee the advantage at all * Use standard JavaBeans for the JSF backing beans, and put the business in other pure JavaBeans. clear - or in the backing bean itself! * Use standard JavaBeans for the JSF backing beans, and put the business logic into an EJB session bean (most likely using annotations to inject this) the problem if in backing bean - how to manage the presentations preparing logic... with ejbs - should i all first prepare and then to hand down in the ejb - not so useful... and whats with shale special funcition which can not use in deep ejbs * Dispense with using a standard JavaBean, and make the EJB session bean be *both* the backing bean and the business logic (this is the approach that JBoss Seam uses, for example). the best solution - access to all features of the framework and ejb at same time ### are there more overlaps than: livecycle annotations - jsf 1.2 client- and serverside validators - jsf 2.0 thx 2006/9/19, Craig McClanahan [EMAIL PROTECTED]: On 9/18/06, numpsy beelzebub [EMAIL PROTECTED] wrote: my questions for used / important / generally functions has as context the see on the architecture! i'm excited fan of clay and its features given to developer - and shale other features. so the presentation part of application is clear. but the business logic is the fact... i mean especially the gap between ejb 3.0 and shale models It encompasses the kinds of patterns that I would recommend for building new apps today. 1. i followed your thinking about the example an the port from struts and thats right, but lets talk about you last statement. your experience is more great than my - so maybe underline your statement! 2. as i asked in another mail - all talk about ejb 3.0 and the jpa is built upon ejb 3.0. so if already use ejb 3.0 for persistence or jpa - whats your opinion about mix or share business code in the shale model objects and in stateful/stateless ejbs. Just to clarify terminology a bit ... jpa is built upon ejb 3.0 is not technically correct. The JPA specification was built by the same group that did the EJB3 specification, but the technologies are independent of each other. Informally, you can think of JPA as being the replacement for entity beans in EJB 2.1, while EJB3 contains just session beans (stateless and stateful) and message driven beans. Given that, there are really four general approaches to the business logic of a JSF based application (and they apply pretty much the same with or without Shale). * Embed the business logic in the event handlers (roughly corresponding to embedding business logic in an Action.execute() method in Struts. * Use standard JavaBeans for the JSF backing beans, and put the business in other pure JavaBeans. * Use standard JavaBeans for the JSF backing beans, and put the business logic into an EJB session bean (most likely using annotations to inject this) * Dispense with using a standard JavaBean, and make the EJB session bean be *both* the backing bean and the business logic (this is the approach that JBoss Seam uses, for example). I think we'll see all four approaches get used. The first will tend to get used by programmers not as familiar with O-O techniques, or in cases where you're primarily interested in rapid development (such as a prototype). The second and third approaches will be a natural choice if you already have your business logic encapsulated -- for instance, the second method works great if you're already using Spring for instantiating your business logic beans. The third (EJB session beans) is nice if you need the transactional behavior or statefulness you can get with EJBs without the extra setup it takes to get that out of Spring. The fourth approach (Seam) sounds a bit odd, but it's really pretty much equivalent to the first. Besides being useful in the cases described there, it can make sense when the business logic you are talking about is so tied to the particular application you are doing that you'd get no reuse benefit out of abstracting it into a separate class. The fourth approach (compared to the first) gives you transactionality and statefulness if you need them. Which is best? There's no one right answer. It's going to get driven a lot by your particular application use cases, whether you have previously abstracted your business logic (versus you have to write it from scratch), and your own preferences for object oriented development and splitting this kind of stuff. 3. what do you think about the basic approaches of shale and struts - i know you leaded both - so
Re: getbean method question
* Use standard JavaBeans for the JSF backing beans, and put the business logic into an EJB session bean (most likely using annotations to inject this) the problem if in backing bean - how to manage the presentations preparing logic... with ejbs - should i all first prepare and then to hand down in the ejb - not so useful... and whats with shale special funcition which can not use in deep ejbs yeah would you prefer to fill the backing beans within ejbs (give reference to backing bean into ejb to fill there) or not 2006/9/19, numpsy beelzebub [EMAIL PROTECTED]: great explanations, but few more questions: * Embed the business logic in the event handlers (roughly corresponding to embedding business logic in an Action.execute() method in Struts. so i know if i push a button i can first call an event handlers and afterwards the specific action - so wouldn't be in both business logic? dont seee the advantage at all * Use standard JavaBeans for the JSF backing beans, and put the business in other pure JavaBeans. clear - or in the backing bean itself! * Use standard JavaBeans for the JSF backing beans, and put the business logic into an EJB session bean (most likely using annotations to inject this) the problem if in backing bean - how to manage the presentations preparing logic... with ejbs - should i all first prepare and then to hand down in the ejb - not so useful... and whats with shale special funcition which can not use in deep ejbs * Dispense with using a standard JavaBean, and make the EJB session bean be *both* the backing bean and the business logic (this is the approach that JBoss Seam uses, for example). the best solution - access to all features of the framework and ejb at same time ### are there more overlaps than: livecycle annotations - jsf 1.2 client- and serverside validators - jsf 2.0 thx 2006/9/19, Craig McClanahan [EMAIL PROTECTED]: On 9/18/06, numpsy beelzebub [EMAIL PROTECTED] wrote: my questions for used / important / generally functions has as context the see on the architecture! i'm excited fan of clay and its features given to developer - and shale other features. so the presentation part of application is clear. but the business logic is the fact... i mean especially the gap between ejb 3.0 and shale models It encompasses the kinds of patterns that I would recommend for building new apps today. 1. i followed your thinking about the example an the port from struts and thats right, but lets talk about you last statement. your experience is more great than my - so maybe underline your statement! 2. as i asked in another mail - all talk about ejb 3.0 and the jpa is built upon ejb 3.0. so if already use ejb 3.0 for persistence or jpa - whats your opinion about mix or share business code in the shale model objects and in stateful/stateless ejbs. Just to clarify terminology a bit ... jpa is built upon ejb 3.0 is not technically correct. The JPA specification was built by the same group that did the EJB3 specification, but the technologies are independent of each other. Informally, you can think of JPA as being the replacement for entity beans in EJB 2.1, while EJB3 contains just session beans (stateless and stateful) and message driven beans. Given that, there are really four general approaches to the business logic of a JSF based application (and they apply pretty much the same with or without Shale). * Embed the business logic in the event handlers (roughly corresponding to embedding business logic in an Action.execute() method in Struts. * Use standard JavaBeans for the JSF backing beans, and put the business in other pure JavaBeans. * Use standard JavaBeans for the JSF backing beans, and put the business logic into an EJB session bean (most likely using annotations to inject this) * Dispense with using a standard JavaBean, and make the EJB session bean be *both* the backing bean and the business logic (this is the approach that JBoss Seam uses, for example). I think we'll see all four approaches get used. The first will tend to get used by programmers not as familiar with O-O techniques, or in cases where you're primarily interested in rapid development (such as a prototype). The second and third approaches will be a natural choice if you already have your business logic encapsulated -- for instance, the second method works great if you're already using Spring for instantiating your business logic beans. The third (EJB session beans) is nice if you need the transactional behavior or statefulness you can get with EJBs without the extra setup it takes to get that out of Spring. The fourth approach (Seam) sounds a bit odd, but it's really pretty much equivalent to the first. Besides being useful in the cases described there, it can make sense when the business logic you are talking about is so
Re: Building from subversion source
I got it from: http://svn.apache.org/viewvc/shale/framework/trunk I am not sure the -e output is going to help, but I'll send it here: irving-salisbury-iiis-computer-2:~/work/apache/shale-src irving$ mvn -e install + Error stacktraces are turned on. [INFO] Scanning for projects... [INFO] Reactor build order: [INFO] Apache Shale Framework Parent POM [INFO] Shale Test Framework [INFO] Shale Core Library [INFO] Shale Clay Plugin [INFO] Shale Remoting Support [INFO] Shale-Spring Integration [INFO] Shale Tiger Extensions [INFO] Shale Tiles Integration [INFO] [INFO] Building Apache Shale Framework Parent POM [INFO]task-segment: [install] [INFO] [INFO] Skipping missing optional mojo: org.apache.maven.plugins:maven-site-plugin:attach-descriptor [INFO] [install:install] [INFO] Installing /Users/irving/work/apache/shale-src/pom.xml to /Users/irving/.m2/repository/org/apache/shale/shale-parent/1.0.4-SNAPSHOT/shale- parent-1.0.4-SNAPSHOT.pom [INFO] [INFO] Building Shale Test Framework [INFO]task-segment: [install] [INFO] [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:compile] [INFO] Nothing to compile - all classes are up to date [INFO] [resources:testResources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:testCompile] [INFO] Nothing to compile - all classes are up to date [INFO] [surefire:test] [INFO] Surefire report directory: /Users/irving/work/apache/shale-src/shale-test/target/surefire-reports --- T E S T S --- Running org.apache.shale.test.mock.MockObjectsTestCase Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.141 sec Running org.apache.shale.test.mock.ValueBindingTest descriptor(class=org.apache.shale.test.mock.data.Bean, name=name Found BeanInfo [EMAIL PROTECTED] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.021 sec Running org.apache.shale.test.mock.TestMockBean Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.014 sec Results : Tests run: 5, Failures: 0, Errors: 0, Skipped: 0 Found PropertyDescriptor [EMAIL PROTECTED] [INFO] [jar:jar] [INFO] Building jar: /Users/irving/work/apache/shale-src/shale-test/target/shale- test-1.0.4-SNAPSHOT.jar [INFO] [install:install] [INFO] Installing /Users/irving/work/apache/shale-src/shale-test/target/shale- test-1.0.4-SNAPSHOT.jar to /Users/irving/.m2/repository/org/apache/shale/shale-test/1.0.4-SNAPSHOT/shale- test-1.0.4-SNAPSHOT.jar [INFO] [INFO] Building Shale Core Library [INFO]task-segment: [install] [INFO] [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:compile] Compiling 81 source files to /Users/irving/work/apache/shale-src/shale-core/target/classes [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Compilation failure /Users/irving/work/apache/shale-src/shale-core/src/main/java/org/apache/shale/component/ValidatorScript.java:[37,36] package org.apache.commons.validator does not exist /Users/irving/work/apache/shale-src/shale-core/src/main/java/org/apache/shale/component/ValidatorScript.java:[38,36] package org.apache.commons.validator does not exist /Users/irving/work/apache/shale-src/shale-core/src/main/java/org/apache/shale/validator/CommonsValidator.java:[47,36] package org.apache.commons.validator does not exist /Users/irving/work/apache/shale-src/shale-core/src/main/java/org/apache/shale/validator/CommonsValidator.java:[48,36] package org.apache.commons.validator does not exist /Users/irving/work/apache/shale-src/shale-core/src/main/java/org/apache/shale/validator/CommonsValidator.java:[49,36] package org.apache.commons.validator does not exist /Users/irving/work/apache/shale-src/shale-core/src/main/java/org/apache/shale/validator/CommonsValidator.java:[50,36] package org.apache.commons.validator does not exist /Users/irving/work/apache/shale-src/shale-core/src/main/java/org/apache/shale/validator/CommonsValidator.java:[51,36] package org.apache.commons.validator does not exist /Users/irving/work/apache/shale-src/shale-core/src/main/java/org/apache/shale/validator/CommonsValidator.java:[52,36] package org.apache.commons.validator does not exist
Re: Building from subversion source
Sorry, I actually meant: http://svn.apache.org/repos/asf/shale/framework/trunk Irv On 9/19/06, Irv Salisbury [EMAIL PROTECTED] wrote: I got it from: http://svn.apache.org/viewvc/shale/framework/trunk I am not sure the -e output is going to help, but I'll send it here: irving-salisbury-iiis-computer-2:~/work/apache/shale-src irving$ mvn -e install + Error stacktraces are turned on. [INFO] Scanning for projects... [INFO] Reactor build order: [INFO] Apache Shale Framework Parent POM [INFO] Shale Test Framework [INFO] Shale Core Library [INFO] Shale Clay Plugin [INFO] Shale Remoting Support [INFO] Shale-Spring Integration [INFO] Shale Tiger Extensions [INFO] Shale Tiles Integration [INFO] [INFO] Building Apache Shale Framework Parent POM [INFO]task-segment: [install] [INFO] [INFO] Skipping missing optional mojo: org.apache.maven.plugins:maven-site-plugin:attach-descriptor [INFO] [install:install] [INFO] Installing /Users/irving/work/apache/shale-src/pom.xml to /Users/irving/.m2/repository/org/apache/shale/shale-parent/1.0.4-SNAPSHOT/shale- parent-1.0.4-SNAPSHOT.pom [INFO] [INFO] Building Shale Test Framework [INFO]task-segment: [install] [INFO] [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:compile] [INFO] Nothing to compile - all classes are up to date [INFO] [resources:testResources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:testCompile] [INFO] Nothing to compile - all classes are up to date [INFO] [surefire:test] [INFO] Surefire report directory: /Users/irving/work/apache/shale-src/shale-test/target/surefire-reports --- T E S T S --- Running org.apache.shale.test.mock.MockObjectsTestCase Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.141 sec Running org.apache.shale.test.mock.ValueBindingTest descriptor(class=org.apache.shale.test.mock.data.Bean, name=name Found BeanInfo [EMAIL PROTECTED] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.021 sec Running org.apache.shale.test.mock.TestMockBean Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.014 sec Results : Tests run: 5, Failures: 0, Errors: 0, Skipped: 0 Found PropertyDescriptor [EMAIL PROTECTED] [INFO] [jar:jar] [INFO] Building jar: /Users/irving/work/apache/shale-src/shale-test/target/shale- test-1.0.4-SNAPSHOT.jar [INFO] [install:install] [INFO] Installing /Users/irving/work/apache/shale-src/shale-test/target/shale- test-1.0.4-SNAPSHOT.jar to /Users/irving/.m2/repository/org/apache/shale/shale-test/1.0.4-SNAPSHOT/shale- test-1.0.4-SNAPSHOT.jar [INFO] [INFO] Building Shale Core Library [INFO]task-segment: [install] [INFO] [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:compile] Compiling 81 source files to /Users/irving/work/apache/shale-src/shale-core/target/classes [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Compilation failure /Users/irving/work/apache/shale-src/shale-core/src/main/java/org/apache/shale/component/ValidatorScript.java:[37,36] package org.apache.commons.validator does not exist /Users/irving/work/apache/shale-src/shale-core/src/main/java/org/apache/shale/component/ValidatorScript.java:[38,36] package org.apache.commons.validator does not exist /Users/irving/work/apache/shale-src/shale-core/src/main/java/org/apache/shale/validator/CommonsValidator.java:[47,36] package org.apache.commons.validator does not exist /Users/irving/work/apache/shale-src/shale-core/src/main/java/org/apache/shale/validator/CommonsValidator.java:[48,36] package org.apache.commons.validator does not exist /Users/irving/work/apache/shale-src/shale-core/src/main/java/org/apache/shale/validator/CommonsValidator.java:[49,36] package org.apache.commons.validator does not exist /Users/irving/work/apache/shale-src/shale-core/src/main/java/org/apache/shale/validator/CommonsValidator.java:[50,36] package org.apache.commons.validator does not exist /Users/irving/work/apache/shale-src/shale-core/src/main/java/org/apache/shale/validator/CommonsValidator.java:[51,36] package org.apache.commons.validator does not exist
Re: wrong characters when processed by clay
Could you guys tell me how I would use clay's tiles defined in html and saved in encoding different than iso-8859-1 and make clay display those correctly when included in final layout? I need to use characters from either utf-8 or iso-8859-2 codepages and so far had no luck. Tomasz Pasierb napisał(a): Hello, I'm a shale newbie. I'm learning it and experimenting with it :-) I've recently run into a problem I cannot solve. I've configured clay to use its tiles-like features. My config files look like the following: clay-symbols-config.xml: view !-- Base layout defintion -- component extends=clay jsfid=basePage attributes set name=clayJsfid value=/symbols/layout.html/ /attributes symbols set name=@appName value=App Name/ set name=@title value=Default title/ set name=@leftColumn value=/includes/leftMenu.html/ set name=@headercontent value=/includes/header.html/ set name=@mainMenu value=space/ set name=@bodycontent value=space/ set name=@footer value=/includes/footer.html/ /symbols /component /view clay-pages-config.xml: view !-- page definition -- component extends=basePage jsfid=/index.jsf symbols set name=@title value=index page/ set name=@bodycontent value=/pages/main.html/ /symbols /component ... /view and I use the @headercontent symbol in /symbols/layout.html like this: ... head meta http-equiv=content-type content=text/html; charset=utf-8/ /head ... div id=header class=clearfix c:clayjsfid=clay clayJsfid=@headercontent allowBody=false h1Mock header h1 element/h1 h2mock header subtitle/h2 div id=branding/div div id=useruser/div /c:clay /div ... Both /symbols/layout.html and /includes/header.html are saved with UTF-8 encoding. The /includes/header.html file gets included in the final output that's generated by clay. The problem is that in header.html there are Polish characters, which are saved using two bytes. When I view the file in my browser directly the charaters are displayed correctly but when the page is run on the server and thus processed by clay the characters are not displayed right, they are converted to html entities somewhere along the way and are displayed as two disctinct characters in the browser. Could you please tell me how I can make clay include files with utf-8 encoding in the final output so that all the charaters are displayed as they are supposed to. When reading files does clay somehow check their encoding? Is there an atrribute that would make clay not escape those characters? Thanks, Tom Pasierb Szybko i tanio ubezpiecz samochod! Kupno polisy zajmie Ci 15 minut! Kontakt przez telefon albo Internet. Kliknij i sprawdz: http://link.interia.pl/f19a0 Szybko i tanio ubezpiecz samochod! Kupno polisy zajmie Ci 15 minut! Kontakt przez telefon albo Internet. Kliknij i sprawdz: http://link.interia.pl/f19a0
Re: Building from subversion source
Ok, I found the problem. It wasn't failing for me because of two things. 1) I already have a copy of commons-validator in my local repository and 2) I have settings.xml file configured with the *magical incarnation* of config settings ;) Ok, just kidding about the magical stuff, however, it's still a puzzle. I can't explain to you why this is happening, I mean, I have a few suspicions, but without further investigation, it's merely a guess at this point. If you have a settings.xml file in ~/m2/ directory, then add this to it (keeping the xml well-formed of course)else create a new file with that name and put this in it: settings profiles profile idcargo-config/id properties cargo.container.home /path/to/apache-tomcat-5.5.17/ --- change me /cargo.container.home /properties /profile /profiles activeProfiles activeProfilecargo-config/activeProfile /activeProfiles /settings Either something deep down in our (Shale's) configuration, or some whacked out plugin is relying on that profile in order to download and use the commons-validator jar in the build. Make the above changes and you should be good. Sorry for the hassle, this kind of stuff just gives some people ammunition to blast Maven with...oh well. -- James Mitchell 678.910.8017 On Sep 19, 2006, at 3:39 PM, Irv Salisbury wrote: Sorry, I actually meant: http://svn.apache.org/repos/asf/shale/framework/trunk Irv On 9/19/06, Irv Salisbury [EMAIL PROTECTED] wrote: I got it from: http://svn.apache.org/viewvc/shale/framework/trunk I am not sure the -e output is going to help, but I'll send it here: irving-salisbury-iiis-computer-2:~/work/apache/shale-src irving$ mvn -e install + Error stacktraces are turned on. [INFO] Scanning for projects... [INFO] Reactor build order: [INFO] Apache Shale Framework Parent POM [INFO] Shale Test Framework [INFO] Shale Core Library [INFO] Shale Clay Plugin [INFO] Shale Remoting Support [INFO] Shale-Spring Integration [INFO] Shale Tiger Extensions [INFO] Shale Tiles Integration [INFO] - --- [INFO] Building Apache Shale Framework Parent POM [INFO]task-segment: [install] [INFO] - --- [INFO] Skipping missing optional mojo: org.apache.maven.plugins:maven-site-plugin:attach-descriptor [INFO] [install:install] [INFO] Installing /Users/irving/work/apache/shale-src/pom.xml to /Users/irving/.m2/repository/org/apache/shale/shale-parent/1.0.4- SNAPSHOT/shale- parent-1.0.4-SNAPSHOT.pom [INFO] - --- [INFO] Building Shale Test Framework [INFO]task-segment: [install] [INFO] - --- [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:compile] [INFO] Nothing to compile - all classes are up to date [INFO] [resources:testResources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:testCompile] [INFO] Nothing to compile - all classes are up to date [INFO] [surefire:test] [INFO] Surefire report directory: /Users/irving/work/apache/shale-src/shale-test/target/surefire- reports --- T E S T S --- Running org.apache.shale.test.mock.MockObjectsTestCase Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.141 sec Running org.apache.shale.test.mock.ValueBindingTest descriptor(class=org.apache.shale.test.mock.data.Bean, name=name Found BeanInfo [EMAIL PROTECTED] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.021 sec Running org.apache.shale.test.mock.TestMockBean Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.014 sec Results : Tests run: 5, Failures: 0, Errors: 0, Skipped: 0 Found PropertyDescriptor [EMAIL PROTECTED] [INFO] [jar:jar] [INFO] Building jar: /Users/irving/work/apache/shale-src/shale-test/target/shale- test-1.0.4-SNAPSHOT.jar [INFO] [install:install] [INFO] Installing /Users/irving/work/apache/shale-src/shale-test/target/shale- test-1.0.4-SNAPSHOT.jar to /Users/irving/.m2/repository/org/apache/shale/shale-test/1.0.4- SNAPSHOT/shale- test-1.0.4-SNAPSHOT.jar [INFO] - --- [INFO] Building Shale Core Library [INFO]task-segment: [install] [INFO] - --- [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:compile] Compiling 81 source files to /Users/irving/work/apache/shale-src/shale-core/target/classes [INFO]
Re: Building from subversion source
By the way, if I build from the downloaded sources from http://people.apache.org/dist/shale/v1.0.3/ instead of the subversion repository, it all builds fine. For now, I am fine using those for my exploration. Still curious why it didn't build the other way. I am also downloading the repository onto my windows box to see if I have the same problem there. thanks, Irv On 9/19/06, Irv Salisbury [EMAIL PROTECTED] wrote: Sorry, I actually meant: http://svn.apache.org/repos/asf/shale/framework/trunk Irv On 9/19/06, Irv Salisbury [EMAIL PROTECTED] wrote: I got it from: http://svn.apache.org/viewvc/shale/framework/trunk I am not sure the -e output is going to help, but I'll send it here: irving-salisbury-iiis-computer-2:~/work/apache/shale-src irving$ mvn -e install + Error stacktraces are turned on. [INFO] Scanning for projects... [INFO] Reactor build order: [INFO] Apache Shale Framework Parent POM [INFO] Shale Test Framework [INFO] Shale Core Library [INFO] Shale Clay Plugin [INFO] Shale Remoting Support [INFO] Shale-Spring Integration [INFO] Shale Tiger Extensions [INFO] Shale Tiles Integration [INFO] [INFO] Building Apache Shale Framework Parent POM [INFO]task-segment: [install] [INFO] [INFO] Skipping missing optional mojo: org.apache.maven.plugins:maven-site-plugin:attach-descriptor [INFO] [install:install] [INFO] Installing /Users/irving/work/apache/shale-src/pom.xml to /Users/irving/.m2/repository/org/apache/shale/shale-parent/1.0.4-SNAPSHOT/shale- parent-1.0.4-SNAPSHOT.pom [INFO] [INFO] Building Shale Test Framework [INFO]task-segment: [install] [INFO] [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:compile] [INFO] Nothing to compile - all classes are up to date [INFO] [resources:testResources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:testCompile] [INFO] Nothing to compile - all classes are up to date [INFO] [surefire:test] [INFO] Surefire report directory: /Users/irving/work/apache/shale-src/shale-test/target/surefire-reports --- T E S T S --- Running org.apache.shale.test.mock.MockObjectsTestCase Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.141sec Running org.apache.shale.test.mock.ValueBindingTest descriptor(class=org.apache.shale.test.mock.data.Bean, name=name Found BeanInfo [EMAIL PROTECTED] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.021sec Running org.apache.shale.test.mock.TestMockBean Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.014sec Results : Tests run: 5, Failures: 0, Errors: 0, Skipped: 0 Found PropertyDescriptor [EMAIL PROTECTED] [INFO] [jar:jar] [INFO] Building jar: /Users/irving/work/apache/shale-src/shale-test/target/shale- test-1.0.4-SNAPSHOT.jar [INFO] [install:install] [INFO] Installing /Users/irving/work/apache/shale-src/shale-test/target/shale- test-1.0.4-SNAPSHOT.jar to /Users/irving/.m2/repository/org/apache/shale/shale-test/1.0.4-SNAPSHOT/shale- test-1.0.4-SNAPSHOT.jar [INFO] [INFO] Building Shale Core Library [INFO]task-segment: [install] [INFO] [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:compile] Compiling 81 source files to /Users/irving/work/apache/shale-src/shale-core/target/classes [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Compilation failure /Users/irving/work/apache/shale-src/shale-core/src/main/java/org/apache/shale/component/ValidatorScript.java:[37,36] package org.apache.commons.validator does not exist /Users/irving/work/apache/shale-src/shale-core/src/main/java/org/apache/shale/component/ValidatorScript.java:[38,36] package org.apache.commons.validator does not exist /Users/irving/work/apache/shale-src/shale-core/src/main/java/org/apache/shale/validator/CommonsValidator.java:[47,36] package org.apache.commons.validator does not exist /Users/irving/work/apache/shale-src/shale-core/src/main/java/org/apache/shale/validator/CommonsValidator.java:[48,36] package org.apache.commons.validator does not exist
Re: Building from subversion source
On 9/18/06, Irv Salisbury [EMAIL PROTECTED] wrote: I am following the instructions for building from source. However, I get this error: /Users/irving/work/apache/shale-src/shale-core/src/main/java/org/apache/shale/component/ValidatorScript.java:[37,36] package org.apache.commons.validator does not exist I saw this last week, and can still reproduce it. (Delete org/apache/shale from your local repo and try 'mvn clean install' from framework.) It fails even with the Cargo plugin config in settings.xml, but that really shouldn't have anything to do with commons-validator. My bet is on dependencyManagement not working correctly again. I haven't looked at the changes Craig made recently, I'd start there. -- Wendy
Shale book
Hi guys! These days i found in emule a pdf called struts-shale.pdf and there was the documentation from the web site. Is this auto generated and is it there something like that for the newest documentation of shale? -- Seeing is believing
I am sure you guys get asked this a hundred times, but google didn't turn up anything
Tomorrow at work I have to defend why I want to use shale. I see many good things (I18N, the view controller, remoting) that I know we will need. They want to use straight JSF and just use glassfish with no add-ons. Any additional ammo I can have? Thanks, Irv
common areas
In shale, what is the best way to handle common areas of the page? So, if I had something like html head link href=css/PCX.css rel=stylesheet type=text/css/link !-- Now I want subpages to be able to put stuff here such as the line below -- link href=css/mainPage.css rel=stylesheet type=text/css/link !-- I want each subpage to control the title, so this needs to be a callback as well -- titleSome title/title script language=JavaScript type=text/JavaScript src=js/PCX.js/script script language=JavaScript type=text/JavaScript src=js/mainPage.js/script /head body id=main class=main div class=mainOuterDiv
