Scott, If I use the trunk.zip you sent yesterday, should I be able to reproduce this on my Mac?
Thanks, Matt On 9/17/07, Scott Ryan <[EMAIL PROTECTED]> wrote: > > YEA It is working now. i removed my repository and tried again from scratch > on Windows and everything worked fine. I also tried on my Mac and the > results were not so good. The null pointer showed up. So it looks like > there is an issue on the Mac. I will continue on Windows and manually > overlay my code on to the new project and check it in and test it. Once that > is working I will port over to the mac and see if it runs there as well. I > wonder if it is something with CRLF. I will try to debug it later this > week once i get my deliverable out and some carpet on the floor. The > process I used was as follows > > 1. Remove my maven repo > 2. Create a new jsf basic project from the current archetype > 3. Modify the pom to change dao.framework to jpa > 4. Change annotation type for hibernate plugin to jpaconfigruation > 5. Remove the hibernate.cfg.xml from the main/src/resources directory > 6. Run mvn install > 7. Run mvn appfuse:full-source > > [INFO] [AppFuse] Adding dependencies from service module... > [ maven embedder INFO] snapshot > org.appfuse:appfuse-hibernate:2.0-SNAPSHOT: checking for > updates from Codehaus Snapshots > [ maven embedder INFO] snapshot > org.appfuse:appfuse-hibernate:2.0-SNAPSHOT: checking for > updates from Appfuse Repository > [ maven embedder INFO] snapshot > org.appfuse:appfuse-hibernate:2.0-SNAPSHOT: checking for > updates from central > [ maven embedder INFO] snapshot > org.appfuse:appfuse-hibernate:2.0-SNAPSHOT: checking for > updates from appfuse > [INFO] [AppFuse] Adding dependencies from web-common module... > [INFO] [AppFuse] Adding dependencies from jsf module... > [INFO] [AppFuse] Removing maven-warpath-plugin... > [INFO] > ------------------------------------------------------------------------ > [ERROR] FATAL ERROR > [INFO] > ------------------------------------------------------------------------ > [INFO] null > [INFO] > ------------------------------------------------------------------------ > [INFO] Trace > java.lang.NullPointerException > at > org.appfuse.mojo.installer.InstallSourceMojo.createFullSourcePom(InstallSourceMojo.java:333) > at > org.appfuse.mojo.installer.InstallSourceMojo.execute(InstallSourceMojo.java:225) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) > at > org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) > at > org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) > at > org.apache.maven.cli.MavenCli.main(MavenCli.java:280) > at > sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at > org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at > org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > at > org.codehaus.classworlds.Launcher.main(Launcher.java:375) > [INFO] > ------------------------------------------------------------------------ > [INFO] Total time: 48 seconds > [INFO] Finished at: Mon Sep 17 19:44:23 MDT 2007 > [INFO] Final Memory: 7M/21M > [INFO] > ------------------------------------------------------------------------ > scott-ryans-computer:~/projects/test/myproject scott$ > > > > Scott Ryan > CTO Soaring Eagle L.L.C. > Denver, Co. 80129 > www.soaringeagleco.com > www.theryansplace.com > (303) 263-3044 > [EMAIL PROTECTED] > > > On Sep 17, 2007, at 7:37 AM, Matt Raible wrote: > > If I create a basic-jsf project with 2.0 SNAPSHOT, change it to use > JPA and run full-source on it, should I see the same problem? In other > words, are these the steps I need to take to try and reproduce the > problem on my end? > > Thanks, > > Matt > > On 9/17/07, Scott Ryan <[EMAIL PROTECTED]> wrote: > Ok so this morning I started from scratch. I used the basic jsf archetype > to create a brand new project. Is is possible you have maven repositories > defined in your settings.xml and are picking up different dependecies than I > am. I removed everything from my settings.xml and renamed my local > repository so I can make sure I am using fresh code. I then updated the > pom to change the following: > > <dao.framework>jpa</dao.framework> from hibernate > <!-- > <implementation>annotationconfiguration</implementation> > Use 'jpaconfiguration' if you're using JPA. --> > > <implementation>jpaconfiguration</implementation> > from annotationconfiguration to jpaconfiguration > > I then removed the hibernate.cfg.xml file from main/resources > > Upon building I got an error looking for the hibernate-commons-annotations > file so i add the following dependency > > <dependency> > <groupId>org.hibernate</groupId> > > <artifactId>hibernate-commons-annotations</artifactId> > <version>3.3.0.ga</version> > </dependency> > > I then ran mvn install and all tests ran successfully. I then ran mvn > appfuse:full-source and got the null pointer exception. This is using the > archetype description on the confluence website which uses 2.0-SNAPSHOT. > > Once it fails the project is not usable as it complains about missing > aspectj files. I will continue to work on this issue this evening to see if > I can isolate the issue. > > [INFO] [AppFuse] Removing maven-warpath-plugin... > [INFO] > ------------------------------------------------------------------------ > [ERROR] FATAL ERROR > [INFO] > ------------------------------------------------------------------------ > [INFO] null > [INFO] > ------------------------------------------------------------------------ > [INFO] Trace > java.lang.NullPointerException > at > org.appfuse.mojo.installer.InstallSourceMojo.createFullSourcePom(InstallSourceMojo.java:333) > at > org.appfuse.mojo.installer.InstallSourceMojo.execute(InstallSourceMojo.java:225) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) > at > org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) > at > org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) > at > org.apache.maven.cli.MavenCli.main(MavenCli.java:280) > at > sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at > org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at > org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > at > org.codehaus.classworlds.Launcher.main(Launcher.java:375) > [INFO] > ------------------------------------------------------------------------ > [INFO] Total time: 41 seconds > [INFO] Finished at: Mon Sep 17 07:08:44 MDT 2007 > [INFO] Final Memory: 8M/19M > [INFO] > ------------------------------------------------------------------------ > scott-ryans-computer:~/projects/appfusenew/swoop scott$ > > > > > Scott Ryan > CTO Soaring Eagle L.L.C. > Denver, Co. 80129 > www.soaringeagleco.com > www.theryansplace.com > (303) 263-3044 > [EMAIL PROTECTED] > > > On Sep 16, 2007, at 11:32 PM, Matt Raible wrote: > > On 9/16/07, Scott Ryan <[EMAIL PROTECTED]> wrote: > I was able to upgrade but it looks like the JSF libraries were all moved up. > For example myfaces was moved up to 1.2 which requires servlet 2.5 and many > other upgrades. This change has broken my application as these libraries > are not working fully with facelets and require a lot of code changes. I > tried to just downgrade the myfaces jars back to 1.1.5 but it is conflicting > with many of the other changes that were made with this upgrade. I just > need to get my project upgraded so I can overlay the source and upgrade at > my own speed. I guess if anyone has suggestions on the following to > upgrade my 2.0.m5 project > > The only issue I've seen with MyFaces 1.2.0 and Facelets 1.1.13 is it > sometimes throws errors when you to to use JSTL to evaluate an object > that's not in any scope. I believe this is a bug in MyFaces. Is this > the error you're seeing? > > You should be able to "downgrade" by doing a couple of different things: > > 1. Manually specify the versions of MyFaces and Facelets in your pom.xml. > 2. Keep your dependency on appfuse-jsf at 2.0-m5, which specifying a > new version for appfuse-service. > > If your problems are specifically with MyFaces, you may also be able > to change to use Sun's RI instead. I've successfully switched b/w > MyFaces and Sun's RI in AppFuse Light (but MyFaces is the default). > > MyFaces 1.2.0 does require JSP 2.1. Sun's RI can run on Tomcat 5 (Serv let > > 1. Upgrade to 2.0 SNAPSHOT but keep the original 2.0-m5 jsf versions > 2. Overlay my 2.0-m5 project with source so that i can add my own entries to > the User object to link in my own tables to the user object table. > > It also appears that the hibernate bug on 2.0m5 is back when using > jpaannotations and i can't seem to trace down the issue but i will look into > it further since it shows it was fixed in JIRA. Also when I upgraded my > project to 2.0-RC1 I had issues with an incompatible > hibernate-commons-annotations library which i had to manually upgrade. I > followed the upgrade path described in the release notes. Is there a better > way to execute this upgrade. I really do want to keep on the 2.0 framework > but it is getting close to my deadline and i need to figure out an upgrade > strategy so I can get onto a full copy of the source and control the library > upgrades myself since most of my clients are not running servlet 2.5 yet and > it appears to still be pretty buggy. Appfuse is a great framework and i > really want to keep moving forward with it. > > If you ran full-source on your project, and then tried to upgrade, > that's going to be difficult. However, you may be able to create a new > project, run full-source on it and then copy your objects into the new > project. > > In reality, not much has changed since M5 as far as the core AppFuse > code. AMP has been improved a fair amount, but you should be able to > simply upgrade it w/o upgrading the rest. > > Of course, if you can somehow run "full-source" on your project, you > should do it. This isolates you from any AppFuse changes and allows > you to be completely independent. It won't be as easy to upgrade, but > it's still possible. With 1.x, there were never any upgrade paths > (besides diffing directories), but people were still able to do it. > > Matt > > Thanks > > Scott Ryan > CTO Soaring Eagle L.L.C. > Denver, Co. 80129 > www.soaringeagleco.com > www.theryansplace.com > (303) 263-3044 > [EMAIL PROTECTED] > > > > > > -- > http://raibledesigns.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: > [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > http://raibledesigns.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: > [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- http://raibledesigns.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
