Hi Ken,
Thanks for the pointer. I fixed some of the issues below.
Irfan Ahmed wrote:
- The breadcrumbs issue was solved by restarting the app server.
I
have no idea why?
It seems that I was not including the correct file. This has been
resolved.
- I wanted to know what is the difference between the dev-setup
and
the normal build target.
- Here is what I have noticed. To begin with I ran the targets
dev-setup and dev-build. Then I did an asadmin deploydir for the
docroot directory and it deployed fine.
- I could go to the admin GUI in the deployed directory and see
the changes that I have made to peTree.jsf. Cool.
- Now I did an ant build under admin-gui. It packed up the
peTree.jsf into admin-jsf.jar and copied the file into the
lib/install/applications... directory.
- Now I restarted the admin and was hoping to see my changes in
the admin GUI at http://localhost:4848.
However none
of the changes
that I had made showed up there. Moreover there is no way to undo the
changes that were made in peTree.jsf.
- I installed a fresh unchanged copy of peTree.jsf, did ant
build all and restarted the app server. The changes were still there.
The above have been resolved. I did some digging into the code and saw
that the JSF files in the JAR files placed under the WEB-INF/lib
directory were cached under
<gf-install>/domains/domain1/generated/jsp/j2ee-modules/admingui/loader.
Now when once restarts the application server the files under this
directory are not updated. I though this would have been deleted and
new files from the corresponding jars expanded again.
Also I think this is specific to the admin GUI. That is why when the
admin GUI is deployed as a simple webapp in dev setup, I do not see
this problem.
This is why the changes in peTree.jsf as well as the old files in
sailfin specific admin GUI jar file were persisting. There are two ways
to fix this
- place all your JSF files including the Sailfin JSF files under
<gf-install>/lib/install/applications/admingui/adminGUI_war
- Place new copies of the updated JAR files in the WEB-INF/lib
directory and make sure you delete the generated .jsf files and restart
the application server.
- Another thing I noted was that when I call info.jsf, it does
not give me the detailed information it used to, it just shows the link
to jsftemplating.dev.java.net
OK this was a blooper. info.jsf does its magic only if
com.sun.jsftemplating.DEBUG in web.xml is set to true.
- Also where can I get more documentation on the tags used in
the
template such as dynamicTreeNode and all.
This is still open.
Thanks and Warm Rgds,
Irfan.
--
irfan@sun.com
Irfan Ahmed
|
Sun Microsystems Inc., Bangalore, India. | irfan@sun.com - 9180.66927726 -
x27726