Robert, let us know how that new build works with web modules.

Unfortunately, I don't have time to mess with it right now.


99 comments
Comment actions Permalink

Thanks again Robert. That is exactly what I need but I just don't express it
as well as you.

"Robert S. Sfeir" <robert@codepuccino.com> wrote in message
news:bsuog9$g8l$1@is.intellij.net...

For what it's worth to everyone, I've setup a web app without deploying
it, the way 3.0.5 used to work, it doesn't take a lot of effort either,
about as much as 3.0.5. I've included a pic to show how to set that up.

>

The issue right now is that if you check off both the war and exploded
dir deployment, you get an error on run. So the workaround is to just
setup a webapp dir and deploy to that for now, until JetBrains fixes the
problem.

>

I've filed a bug with the following description:

>

While trying to setup a web app with no exploded dir, and no war file, I
tried to start the debugging process, and it popped up an error saying
that Exploded module not found for webapp.

>

The issue here is that sometimes folks want to setup a web module which
in itself is the exploded directory, and we don't want to copy all the
files to one location.

>

If I check off the exploded and war file J2EE deployment settings, I
expect IDEA to just assume that the web module itself is setup properly.

>

In that case, web.xml should be copied to the existing WEB-INF at the
root of the web module, if it's not already there, and the rest should
be left alone, and the web module should be considered the web root with
relative path of /.

>

Thanks
R

>


-


-







0
Comment actions Permalink

I hope things can still work even if you choose not to deploy to a dir or to create a war (ie, the dir structure you have is a webapp, that can run as is and doesn't require pulling things together from different places).

Currently the openAPI for this seems a be a bit of a mess. For example, no combination of checking or specifying an exploded dir will return in EXPLODED_SELECTED (or whatever the field name is, I don't remember offhand) being true, and getExplodedPath() always returns null. It's also very unclear on how to navigate the WebApp object, to get at stuff like the content entry (I'd like to use that as the 'root' if no war is checked and no deployment dir is set).

0
Comment actions Permalink

Will the
http://www.intellij.net/tracker/idea/viewSCR?publicId=25151
suit your needs ?


--
regards,
Alexey Kudravtsev
Software Developer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


"Hani Suleiman" <hani@formicary.net> wrote in message news:5339195.1072899182797.JavaMail.itn@is.intellij.net...

I hope things can still work even if you choose not to deploy to a dir or to create a war (ie, the dir structure you have is a

webapp, that can run as is and doesn't require pulling things together from different places).
>

Currently the openAPI for this seems a be a bit of a mess. For example, no combination of checking or specifying an exploded dir

will return in EXPLODED_SELECTED (or whatever the field name is, I don't remember offhand) being true, and getExplodedPath() always
returns null. It's also very unclear on how to navigate the WebApp object, to get at stuff like the content entry (I'd like to use
that as the 'root' if no war is checked and no deployment dir is set).


0
Comment actions Permalink

Okay ;) after reading most of the wonderful "tweaks and hacks" you guys have been through, I am stuck in the same position - no resolution of jsp-tags.

But with me, the problem is a little bit different, I guess. I am using MyFaces (a free JavaServerFaces implementation), and include their jar in my WEB-INF/lib directory and as a lib in the project.

My JSPs include these tlds in the form:

<%@ taglib uri="http://java.sun.com/jsf/html" prefix="h"%>
<%@ taglib uri="http://java.sun.com/jsf/core" prefix="f"%>
<%@ taglib uri="http://myfaces.sourceforge.net/tld/myfaces_ext_0_4.tld" prefix="x"%>

As my web-application (started from the war-file) can correctly resolve these tlds, I would expect IntelliJ to resolve them as well - but all I see are red tags.

I ended up extracting the tlds to the WEB-INF directory and changing the taglib-pointer to that position, along with setting the external resources - did not work either.
Finally I put the taglib information additionally in my web.xml - did not work either.

I am kind of devastated here ... I would love to have the thing running with just the jar, as the web-application does it perfectly!

What can I do? Waiting for the next release, I guess, even though I don't want to as I love the new IntelliJ version apart from the tld problem ;)

best regards,

Hugo

0
Comment actions Permalink

I've got the same problem. Some tags resolve, others don't.

I've spent all day trying to get this to work with no success at all.

0
Comment actions Permalink

No, my jsp's are in the web-root directory (which is also marked with "/") and not somewhere down-under...

So that is not the solution.

my directory structure:

/web (= web root)
/WEB-INF
web.xml
/lib
myfaces.jar (with tld's in it)
/classes
*.jsp

is there something incorrect with that structure?

Best regards,

Martin


0
Comment actions Permalink

And by the way .. it seems to be fixed in 1070!

0

Please sign in to leave a comment.