| Error with 2nd EJB3 Added [message #256750] |
Fri, 03 October 2008 17:43  |
Eclipse User |
|
|
|
I created an EJB project.
I added a Stateless EJB3 Bean.
I added a method to the Bean.
I called the method from a JSP page invoked from the Bean and it worked
perfectly!
Then I added a second Bean. Before Eclipse launches the jsp page, it
reports:
An error occurred at line: 7 in the generated java file
Only a type can be imported. com.bowne.TrackkerBean resolves to a package
I have tried deleting the 2nd Bean and re adding several times and it
keeps throwing the message. I have even restarted Eclipse and rebooted
my machine.
I then created a brand new EJB project and added a 1st Bean and it caused
the jsp to throw the problem!
What is going on with the 2nd Bean??!
|
|
|
|
| Re: Error with 2nd EJB3 Added [message #256762 is a reply to message #256758] |
Sun, 05 October 2008 03:40  |
| Eclipse User |
|
|
|
"John Bailo" <John.Bailo@Bowne.com> wrote in message
news:8e82f9a3ce5a173fa9efe84a13c558a7$1@www.eclipse.org...
>
> More information:
>
> What appears to be happening is that whatever my Dynamic Web Project
> thinks in in the Bean is what was there when it was first created /
> deployed.
>
> From there on, any changes seem to be ignored!
>
> This is strange, since in the Eclipse IDE I see all my changes reflected
> when I go to add a reference to the Bean in my JSP code, the Intellisense
> shows the new class and even builts the Import statement for me.
>
> However, when I start the debugger (JBoss) the error occurs as if only the
> first version of the Bean were recognized.
>
> Is there something else I need to do, set, configure, deploy, clear to get
> new versions of my Bean recognized?
I'm guessing you will probably have more luck getting an answer if you post
this to the eclipse.webtools group. The eclipse.tools.jdt group is mainly
aimed at POJO development issues. This problem sounds like it's got
something to do with the JBoss tooling.
|
|
|
Powered by
FUDForum. Page generated in 0.03738 seconds
Home