Request to not treat J2EE like a step-child

There has been a continual pattern to treat the J2EE integration (JSP,
EJB, etc) as the very last thing to update in a new build cycle.

Please make these a higher priority and work on these earlier in the
development cycle.

--
Norris Shelton
Sun Certified Java Programmer

10 comments

+1. J2EE is busted again in this build.

That said Norris, most of the work in Irida is J2EE related, so it would be
very surprising if it wasn't earlier in the cycle. Here's hoping.

R

On 10/27/04 2:39 PM, in article cloq48$n3d$1@is.intellij.net, "Norris
Shelton" <i.hate.spam@yahoo.com> wrote:

There has been a continual pattern to treat the J2EE integration (JSP,
EJB, etc) as the very last thing to update in a new build cycle.

Please make these a higher priority and work on these earlier in the
development cycle.


0

+ 1 to imporove productivity in J2EE too.

Ahmed.

0

+1

There has been a continual pattern to treat the J2EE integration (JSP,
EJB, etc) as the very last thing to update in a new build cycle.

Please make these a higher priority and work on these earlier in the
development cycle.


0

Enhancing J2EE development should really be given higher priority; I like the general development-approach for J2EE in IDEA (having general Java features which can be very well applied to J2EE/EJB), but it would really be nice to enhance the J2EE-specific features, as this is what I miss most in this great IDE (e.g. compared to JBuilder).

kind regards,

Messi

P.S.: Did anyone have the same J2EE-related problems with Irida like me (see "J2EE development in Irida completely fails)? Would be good to know if this was just my fault (project-cfg, whatever) and how to fix it...

0

Hi,

It will not be the same again.
The JSP support is being rewritten in order to support JSP in xml form,
add refactorings, optimize imports, etc

Norris Shelton wrote:

There has been a continual pattern to treat the J2EE integration (JSP,
EJB, etc) as the very last thing to update in a new build cycle.

Please make these a higher priority and work on these earlier in the
development cycle.



--
Best regards,
Maxim Mossienko
IntelliJ Labs / JetBrains Inc.
http://www.intellij.com
"Develop with pleasure!"

0

Great thanks. Part of my post was that all webapp functionality is
usually the last functionality to be implemented in a release.

Norris Shelton
Sun Certified Java Programmer




Maxim Mossienko wrote:

Hi,

>

It will not be the same again.
The JSP support is being rewritten in order to support JSP in xml
form, add refactorings, optimize imports, etc

>

Norris Shelton wrote:

>
>> There has been a continual pattern to treat the J2EE integration
>> (JSP, EJB, etc) as the very last thing to update in a new build cycle.
>>
>> Please make these a higher priority and work on these earlier in the
>> development cycle.
>>
>
>

0

+1

Please, a gui tool to do specific appserver/ejb mapping (in others words, I hate IBM RAD, but is the only tool I know what can handle the Map.mapxmi and other files)

0

Please sign in to leave a comment.