So, how does Tapestry support work in 9m1?

I tried installing IDEA 9m1 on my Mac Pro today because I wanted to test the new Tapestry support feature, plus IDEA 8.1.3 (#9886) keeps crashing on me when I change TML files with HTML preview visible, so I wanted to see if that got any better in the 9m1 along with the Tapestry support.

I have tried to enable the Tapestry facet on an existing Project project and that didn't work. Then I created a new project from scratch using Tapestry-support and even though the libraries started downloading, IDEA switched back to the view you get when you just open IntelliJ without a project.
So I loaded the new project-file up and it appeared as if no Tapestry module was created, so I tried to add it manually and again that seems to fail.

Is Tapestry support supposed to be working at all? Is there any documentation available?
To me proper Tapestry-support would be the number 1 feature for upgrading to IDEA 9 since I use Tapestry for pretty much all my web-projects these days.

4 comments
Comment actions Permalink

Hi, Onno

Please, provide <idea.system.path>\system\log\idea.log file or
stacktrace of the exception you see.

Onno Scheffers wrote:

I tried installing IDEA 9m1 on my Mac Pro today because I wanted to test the new Tapestry support feature, plus IDEA 8.1.3 (#9886) keeps crashing on me when I change TML files with HTML preview visible, so I wanted to see if that got any better in the 9m1 along with the Tapestry support.

I have tried to enable the Tapestry facet on an existing Project project and that didn't work. Then I created a new project from scratch using Tapestry-support and even though the libraries started downloading, IDEA switched back to the view you get when you just open IntelliJ without a project.
So I loaded the new project-file up and it appeared as if no Tapestry module was created, so I tried to add it manually and again that seems to fail.

Is Tapestry support supposed to be working at all? Is there any documentation available?
To me proper Tapestry-support would be the number 1 feature for upgrading to IDEA 9 since I use Tapestry for pretty much all my web-projects these days.

---
Original message URL: http://www.jetbrains.net/devnet/message/5241661#5241661

0
Comment actions Permalink

Hi Alexey,

In idea.properties, the idea.system.path is defined as idea.system.path=${user.home}/.IntelliJIdea9M1/system.
But the .IntelliJIdea9M1 folder is not available in my home-folder (I know it is supposed to be hidden, but I cannot access it from the commandline either). So I haven't been able to find the log file.

I think I did figure out what was causing the problems for me though. I typically organise my projects/modules a little differently; I have one 'src'-folder with 'java', 'test', 'web' etc. as subfolders). When I tried to create a new project where 'src' and 'web' were in the module root, things seemed to work okay. Maybe the plugin expects fixed paths for source-code and web-content?

I also noticed that the plugin still includes the old xsd file in the generated page template (http://tapestry.apache.org/schema/tapestry_5_0_0.xsd instead of http://tapestry.apache.org/schema/tapestry_5_1_0.xsd). The new xsd is required for supporting some of the new Tapestry features introduced in 5.1.0.5. Since that's the version of Tapestry you are supporting, it makes sense to include the new xsd by default.

I am now going to check and see if I can get Tapestry support going on my existing project if I move the source-folders around.


regards,

Onno

0
Comment actions Permalink

Onno,
thanks for info about tapestry_5_1_0.xsd, it's become available not long
ago :), I'll update schema references.

Onno Scheffers wrote:

Hi Alexey,

In idea.properties, the idea.system.path is defined as idea.system.path=${user.home}/.IntelliJIdea9M1/system.
But the .IntelliJIdea9M1 folder is not available in my home-folder (I know it is supposed to be hidden, but I cannot access it from the commandline either). So I haven't been able to find the log file.

I think I did figure out what was causing the problems for me though. I typically organise my projects/modules a little differently; I have one 'src'-folder with 'java', 'test', 'web' etc. as subfolders). When I tried to create a new project where 'src' and 'web' were in the module root, things seem
ed to work okay. Maybe the plugin expects fixed paths for source-code and web-content?

I also noticed that the plugin still includes the old xsd file in the generated page template (http://tapestry.apache.org/schema/tapestry_5_0_0.xsd instead of http://tapestry.apache.org/schema/tapestry_5_1_0.xsd). The new xsd is required for supporting some of the new Tapestry features introduced in
5.1.0.5. Since that's the version of Tapestry you are supporting, it makes sense to include the new xsd by default.

I am now going to check and see if I can get Tapestry support going on my existing project if I move the source-folders around.


regards,

Onno

---
Original message URL: http://www.jetbrains.net/devnet/message/5241719#5241719

0
Comment actions Permalink

Onno,
thanks for info about tapestry_5_1_0.xsd, it's become available not long
ago :), I'll update schema references.


Thanks. It seems template-detection is done based on the included xsd, since the Tapestry-support was not working on templates in my existing project until I put back the old xsd.

I also got an existing project working now, but I indeed had to change the directory-structure around for the Tapestry Facet to be detected. I am gonna rollback those changes, because I cannot expect other developer on the team to be happy when I change everything around just to be able to play with a new feature in a pre-release edition of my favorite IDE .

A little more work in this area would be appreciated before the final 9.0 release. Other than that I'm looking forward to using Tapestry support. Switching between page classes and templates is much quicker and I love the built-in checks for required component-parameters etc.

0

Please sign in to leave a comment.