NetBeans Forums
| View previous topic :: View next topic |
| Author |
Message |
wire
Joined: 31 Aug 2009
Posts: 1
|
 Posted: Mon Aug 31, 2009 7:19 pm Post subject: Deploy Portlet in Jetspeed |
 |
|
I've installed NetBeans 6.7.1 with the Java Web Applications 1.3.2 plugin and the Generic Portlets 3.0.1.1 plugin. I've also installed Jetspeed 2.2.0 using the autoinstaller that sets it up as Tomcat. I've registered the Jetspeed "Tomcat" server in NetBeans as Tomcat 6.0. I then create a new Java Web Application registered to the same Tomcat server using the Portlet Support framework which is set to create the Portlet and JSPs in the Portlet Support Configuration window.
Everything works fine, but I don't understand how to conveniently deploy a Portlet to my Jetspeed server using NetBeans...
If I build and deploy my NetBeans project to my Jetspeed server using the project context menu, it "works" in that the application is started on the server:
| Code: |
init:
deps-module-jar:
deps-ear-jar:
deps-jar:
library-inclusion-in-archive:
library-inclusion-in-manifest:
compile:
compile-jsps:
In-place deployment at /export/home/wire/Desktop/WebApplication3/build/web
Deployment is in progress...
deploy?config=file%3A%2Fvar%2Ftmp%2Fcontext50105864752951746.xml&path=/WebApplication3
OK - Deployed application at context path /WebApplication3
Start is in progress...
start?path=/WebApplication3
OK - Started application at context path /WebApplication3
run-deploy:
BUILD SUCCESSFUL (total time: 6 seconds)
|
I can then access it at "http://localhost:8080/WebApplication3" and see the "Hello World" index.jsp page that is automatically created with the project. However, I see no actual files in the server's directory structure that have anything to do with the deployed application. Is this supposed to be the case? I see the "in-place" deployment above, and wonder if that's why.
When I then login to my Jetspeed server and try to add my WebApplication3 portlet to any page, the portlet isn't registered with Jetspeed so it doesn't show up. If I instead copy the built .war file into the Jetspeed deploy or (webapp folder directly) the server sees it and deploys, extracting the files. Then I can access both the localhost context and install the Portlet into Jetspeed, because the files are actually there and it sees the Portlet.
What I want to know is... shouldn't NetBeans create files on the Jetspeed server when it deploys? Or is this process somehow virtual. Without the files, the application does not recognize the portlet at all. I'm completely confused about the process. Do I manually have to build my portlet project and then copy the .war to the Jetspeed deploy directory every single time? Or is there an easier way to do this...
Help would be greatly appreciated. Thank you. |
|
| Back to top |
|
 |
olze
Joined: 07 Aug 2009
Posts: 32
|
| Posted: Sun Nov 22, 2009 9:25 am Post subject: |
|
|
have the same problem here.. the portlet server inside the application server must be known by netbeans, and i think this is not the case for jetspeed, but for liferay it is with the portal pack plugin.
the reason why i want to change from liferay to a smaller portlet container is that i want to develop on my laptop which has just 2gb ram and this is really ugly to do with tomcat+liferay (nearly impossible).
so if you have a good system you can try to use liferay or another portlet container which is supported by netbeans, than you can just hit "deploy" and the .war is created, copied to the deploy folder and everything works automaticly - you can then even debug your portlet. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You can attach files in this forum
You can download files in this forum
|
|
FAQ
Search
Memberlist
Register
Profile
Log in to check your private messages
Log in
