| General question about Java/Eclipse projects [message #69961] |
Thu, 26 May 2005 15:48  |
Eclipse User |
|
|
|
My background is C/C++ and other more "traditional" languages than Java.
I've recently inherited a fairly large J2EE project, and am trying to
get my head around it.
One thing that seems to keep biting us is the basic nature of Java - as
it doesn't compile until someone actually opens the page in which any
new code resides, we've had a few "gotchas" where new files don't get
checked in, syntax errors exist, or other bugs that in a compiled
language would be found at compile time - long before a user or tester
opens the screen where they're located.
These kinds of bugs are really getting frustrating. It seems like there
should be a better way of ensuring that required changes get rolled into
our test environment other than "OK, someone sit down and open up every
single screen where the code has changed and make sure it compiles
correctly."
I can't imagine that really large J2EE shops do it that way - so that's
my question. What processes do large shops put in place to ensure that
the right files get built into an .ear file (we use JBoss) from the
get-go, and that they compile correctly when they're run? Is there some
sort of way to tell Eclipse to go through a project and compile every
file? Or can it be done at the JBoss level?
Apologies if this isn't the right forum to be asking these questions -
as I said, this is all new to me, and I'm struggling to educate myself
in the ins and outs of large Java projects.
|
|
|
|
|
|
| Re: General question about Java/Eclipse projects [message #70849 is a reply to message #69961] |
Fri, 27 May 2005 14:25  |
| Eclipse User |
|
|
|
Originally posted by: eclipse.rizzoweb.com
Barbra Letts wrote:
> My background is C/C++ and other more "traditional" languages than Java.
> I've recently inherited a fairly large J2EE project, and am trying to
> get my head around it.
>
> One thing that seems to keep biting us is the basic nature of Java - as
> it doesn't compile until someone actually opens the page in which any
> new code resides, we've had a few "gotchas" where new files don't get
> checked in, syntax errors exist, or other bugs that in a compiled
> language would be found at compile time - long before a user or tester
> opens the screen where they're located.
>
> These kinds of bugs are really getting frustrating. It seems like there
> should be a better way of ensuring that required changes get rolled into
> our test environment other than "OK, someone sit down and open up every
> single screen where the code has changed and make sure it compiles
> correctly."
>
> I can't imagine that really large J2EE shops do it that way - so that's
> my question. What processes do large shops put in place to ensure that
> the right files get built into an .ear file (we use JBoss) from the
> get-go, and that they compile correctly when they're run? Is there some
> sort of way to tell Eclipse to go through a project and compile every
> file? Or can it be done at the JBoss level?
>
> Apologies if this isn't the right forum to be asking these questions -
> as I said, this is all new to me, and I'm struggling to educate myself
> in the ins and outs of large Java projects.
>
OK, where to start...?
It appears that you are talking about JSP pages, not .java files. Is
that correct? Assuming it is...
First, Java *is* a compiled language. Second, if you have files that are
not getting checked in or not tested before they are checked in, well
you have bigger problems than those that have to do with Java or
Eclipse. If that is happening, you need to address with the team your
software development process and how developer-level testing should be done.
Now, JSP pages can be pre-compiled before deploying the application.
Unfortunately, the exact means of doing so varies with each J2EE server
(JBoss is different than WebLogic which is different than WebSphere,
etc). You can use Ant to do that pre-compilation, or you can use an
editor/IDE plugin that does syntax checking and/or compilation testing
as you edit/save the source files.
Here's the bottom line (that you probably don't want to hear): it sounds
as if you may be in over your head. I really enjoy helping people out,
including newbies, but this just feels like a problem too big to tackle
in a public forum. I strongly suspect you may need more direct attention
to get to the point where it all falls into place. My recommendation is
to find a good consultant or "expert" who has J2EE experience and bring
them on-board for at least a jump-start basis. Try to find someone whom
members of your team know personally or have worked with in the past,
since there are a lot of hacks out there and it is better to go with
recommendations than resumes.
J2EE is not a simple technology that can be picked up in a few days by
reading some books and articles. Like Eclipse, it is a powerful tool,
but one that takes some training and experience to properly understand
and leverage.
Perhaps I have mis-assessed your situation. If so, please post with more
specific questions/problems and I will be among those who try to help.
Eric
|
|
|
Powered by
FUDForum. Page generated in 0.09559 seconds
Home