A word of warning for those of us building WARs in "Collapsed EAR" format
(http://openejb.apache.org/collapsed-ear.html):
* The place that T5.4 uses for javascript modules and assets,
WEB-INF/classes/META-INF/ , is also used by your EJB layer for persistence.xml
and, for OpenEJB, ejb-jar/xml.
Well, that worked! Thank you very much.
For anyone else who's confused, the structure of the WAR ends up with 2
META-INF files:
- one in the root context (generated by mvn war:war, it contains the
MANIFEST.MF, pom, etc)
- one in WEB-INF/classes/ (copied there from src/main/resources/ by mvn
r
On Thu, 03 Oct 2013 09:36:13 -0300, Geoff Callender
wrote:
Now I'm really confused!
But I see a few people have said to put META-INF/modules/ in
src/main/resources, which would be picked up by mvn resources:resources
and put into the project's target/classes, eventually put in the WAR as
Now I'm really confused!
mvn war:war puts META-INF in the context root - see
http://maven.apache.org/plugins/maven-war-plugin/usage.html and
http://www.tech-juice.org/2012/05/12/how-maven-builds-a-war-file/ .
But I see a few people have said to put META-INF/modules/ in
src/main/resources, whic
Hi Geoff.
Believe the META-INF should be on the classpath (in resources if using
maven structure)
On Thu, Oct 3, 2013 at 1:52 PM, Geoff Callender <
geoff.callender.jumpst...@gmail.com> wrote:
> I've dropped the @Import and tried many things inspired by Thiago and
> Lenny's source (thanks guys),
On Thu, 03 Oct 2013 08:52:13 -0300, Geoff Callender
wrote:
I've dropped the @Import and tried many things inspired by Thiago and
Lenny's source (thanks guys), but the module is still not found.
Does the URL of the module look right?
http://gc1.local:8080/myapp/asset.gz/module/page
I've dropped the @Import and tried many things inspired by Thiago and Lenny's
source (thanks guys), but the module is still not found.
Does the URL of the module look right?
http://gc1.local:8080/myapp/asset.gz/module/pages/stuff.js
My WAR has META-INF/ at the top level alongside WEB-I
Hi, Geoff!
As Lance said, with JavaScriptSupport.require(), you shouldn't use @Import
in the same file, because require() already does that.
Check these examples from tapestry-wymeditor:
https://github.com/thiagohp/tapestry-wymeditor/blob/master/src/main/java/br/com/arsmachina/tapestry_wymed
Not sure what you are doing wrong here, besides Lance' suggestion, but
I have plenty of up to date examples in FlowLogix under tapestry-5.4 branch or
the source code in maven central snapshot release.
Ex:
https://code.google.com/p/flowlogix/source/browse/tapestry-services/src/main/java/com/flow
Thanks, Lance, but no cigar. If I leave out the @Import line then I don't get
the good news message. If I leave out the jsSupport.require line then I don't
get the bad news message (and of course the javascript still doesn't run).
BTW, notice that the URLs of the two messages differ. The first o
You are trying to import stuff.js twice. Once via require.js and once via
@Import. I get the feeling it's the @Import that's failing.
On 2 Oct 2013 14:13, "Geoff Callender"
wrote:
> I'm desperately seeking an up-to-date example of custom javascript,
> because nothing I've tried works. Here's on
I'm desperately seeking an up-to-date example of custom javascript, because
nothing I've tried works. Here's one attempt that failed...
package myapp.pages;
import javax.inject.Inject;
import org.apache.tapestry5.annotations.Import;
import org.apache.tapestry5.json.JSONObject;
import org.apach
12 matches
Mail list logo
