My personal experience with maven and eclipse is using the maven command
line for any maven command, and Eclipse only for coding, debugging, etc.
I don't even import the project on Eclipse as maven project, as it
continually keeps lunching maven commands when I do not want to.
Josep
2010/9/15 web
Problem solved,
In my Eclipse, I go to Window / Preferences / Java / Installed JREs, and
change the entry to point to a JDK, not a JRE directory.
After several minutes, the mvn jetty:run-war command finished and I was
able to hit http://localhost:8080.
Now I’am very very happy, my friends!!
T
Hi,
I use ubuntu as well, and used an earlier version of appfuse without issue
with ubuntu 8.04. I am having some problems with the current appfuse
2.1.0-M1 on ubuntu 10.04 using the same JDK you're using but I've seen no
reason to think this is ubuntu related, though it may be.
I also say the
Hi Ferenc,
With respect to the JDK vs. JRE issue, look at what your JAVA_HOME is set
to:
Java home: /usr/lib/jvm/java-6-openjdk/jre
See the "jre" at the end of that line? Before when you were using the sun
JDK it said the same thing, you want iit to point to the JDK home directory,
not the JR
Ferenc, I'd suggest you not try to use the maven stuff from within eclipse, I
have been doing some RESTful service dev using JBoss's "RESTEasy" code and
have run into strange dependency related problems with it relating to that
distribution too. I have in the past seen issues like this with appfu
Comments inline below...
On Sep 15, 2010, at 6:34 PM, jackalista wrote:
>
> Hi,
>
> I'm using the modular struts archetype, this is my command for creating the
> project:
>
> mvn archetype:generate -B -DarchetypeGroupId=org.appfuse.archetypes
> -DarchetypeArtifactId=appfuse-modular-struts-arch
OK I was also having the same problem with "mvn install eclipse:eclipse" that
Ferenc was having, so I set the version from 2.7 --> 2.5.1 as Matt suggested
and the command succeeded this time, thanks Matt.
I'm going to try to follow the tutorials "to the letter" and see if this
changes anything, a
Ooops, didn;t see this, thanks Matt.
Matt said:
---
Do you have implementations of PersonDao in your project? If so, does it
contain a @Repository annotation?
---
Yes indeed, it looks like this:
@Repository("personDao")
public class PersonDaoHib
OK, I'm *not* going to use the package from the tutorial code... Since the
archetype creation went and created the folders for my packages, it looks
like that is working properly, and so I'm guessing (but don't know for sure)
that this package thing isn't the problem... ifanybody knows differently
If you look in the Spring XML files, there's a component-scan tag that tells
Spring what packages to look in.
On Sep 16, 2010, at 10:01 AM, jackalista wrote:
>
> OK, I'm *not* going to use the package from the tutorial code... Since the
> archetype creation went and created the folders for my
Yes, I saw that, it's set to the correct package, this is from
core/src/main/resources/applicationContext.xml:
I am thinking that this is not related to that strange new exception, but do
you disagree? Should I regenerate a project using org.appfuse.tutorial?
--
View this message in context
What's the "strange new exception" you're referring to? The Hibernate JNDI
error, the can't fine class error or uncaught exception issue?
Feel free to zip up your project and send to me and I can try to reproduce.
On Sep 16, 2010, at 10:26 AM, jackalista wrote:
>
> Yes, I saw that, it's set to
Thanks, what's your email address? [or how do you want me to get it to you,
it's been a while since I've done this so I've lost your coordinates].
I will run through the rest of the dao test stuff and see if I can solve
this myself but will send it to you if I get back to the same exception;...
-
I was talking about the JNDI thing, which I understood to be the exception
you hadn't seen before...
--
View this message in context:
http://appfuse.547863.n4.nabble.com/problem-with-hibernate-tutorial-imports-for-annotations-tp2541421p2542598.html
Sent from the AppFuse - User mailing list archi
[email protected]
On Thu, Sep 16, 2010 at 10:55 AM, jackalista wrote:
>
> Thanks, what's your email address? [or how do you want me to get it to you,
> it's been a while since I've done this so I've lost your coordinates].
>
> I will run through the rest of the dao test stuff and see if I c
OK, there are for sure missing imports in the tutorial code, I'm not sure if
this is contributing tpo the problem I"m seeing but I'm going to detail the
things I did to resolve it:
1. added import static org.junit.Assert.*; to my PersonDaoTest
2. added import org.junit.Test; to same test class
3.
OK, I have a zip file for ya (435.5 KB). Interestingly, even though that
test blew up with that exception, looking atthe MySQL DB, there is indeed a
Matt raible now in the person table...
--
View this message in context:
http://appfuse.547863.n4.nabble.com/problem-with-hibernate-tutorial-import
OK, I think I see one problem, there used to be a statement in the tutorials
(which is now missing it looks like) that had you change the XML for the
generic DAO to be your own implementation and that isn't there before but
I'm betting one still needs to do that... I don't think I have any old
pro
I looked at the tutorial a little more closely, and the implication *seems*
to be that the annotation (@Repository) is an alternative to changing the
XML in applcationContext.xml. I commented out the XML declaration that
refers to the generic DAO and I am now not getting as many errors, just the
OK, I tried using the following XML in applicationContext.xml and it made no
difference, both with the @Repository annotation present and with it
removed:
I'm going to try to add some language to the tutorial about commenting out
the generic DAO reference in applicationContext.xml, as that did
XML is only needed if you don't write Java code and want to use the
GenericDAOs. Annotations can be used if you write Java code, but they're not
required. You can still use XML like you have below. Hope this helps clarify.
On Sep 16, 2010, at 12:25 PM, jackalista wrote:
>
> OK, I tried using t
Yes, I just figured that out, but thanks. I added a short statement to the
page about how you should comment out the reference to the generic Dao if
you are writing java code as that did reduce the exceptions to the one about
JNDI which you had mentioned you think has something to do with hiberna
Hi,All
Can you help me?
error:
Unable to instantiate Action, projectAction, defined for 'project' in
namespace '/'Error creating bean with name 'projectAction' defined in
ServletContext resource [/WEB-INF/applicationContext-struts.xml]:
Cannot resolve reference to bean 'projectManager' whil
Did you create a PersonDao interface and implementation in your project? If
so, did you register them in an XML file or with annotations? If so, what
version of AppFuse are you using?
2010/9/16 Cody Zhang
> Hi,All
>Can you help me?
> error:
>
>
>
> Unable to instantiate Action, projectActi
In your hibernate.cfg.xml, remove the "name" attribute from the
element.
http://hibernate.sourceforge.net/hibernate-configuration-3.0.dtd";>
I also removed the personDao bean definition from the XML.
Result:
---
T E S T S
---
Hi,Matt
I will add something on xml file when new project class?
applicationContext-struts.xml
hibernate.cfg.xml
How do it?
Best Regards，
--Cody.Zhang
2010/9/17 Matt Raible
> Did you create a PersonDao interface and implementation in your project? If
> so, did you regi
26 matches
Mail list logo
