Develope & deploy, debug JSR168 portlet with netbeans

As we know netbeans have portalpack plug in to develop JSR168 & 286 portlets. But we need portlet container to deploy & debug portlets.
GateIn give a simple portlet container where we can test our portlets. To download click here
Followed the below steps:

Install portalpack plugin in netbeans
Download and unzip GateIn Portlet Container
Add new server(Tomcat) in netbeans as Unzipped folder like E:\jeeva\gatein-portletcontainer-2.1.0-Beta01-tomcat6
Create new web application and select Portlet support in netbeans
For our webapp select server as created one.
Develop portlet and deploy. this will deploy our app as normal webapp deployment in tomcat
The GateIn Portlet Container will read this app and register with the container.
Add the portlet in demo JSP of GateIn Portlet Container's simple-portal
Access the url http://localhost:8080/simple-portal/demo/demo.jsp
To debug our app start the server in debug mode from netbeans.

So we can easily develop, deploy & debug our JSR portlets using netbeans.
happy coding..

Comments

Running and debugging jetty maven plugin in Netbeans

Coding with Netbeans will make developer life simple. We don't need search for plugins and install different plugins from different places. Maven projects can opened as directly in Netbeans without any settings. Here is the way to run & debug using maven jetty plugin. We can't add Jetty server as servers in Netbeans. Run project: Right click on project and open the properties. click on "Actions" on left side. On right side there will be list of available actions. To run jetty can be created a new action or override default "Run Project" Here I am overriding default one, Because I can run the project just by hitting "F6" key click on "Run Project" Enter the value "Execute Goals" as "jetty:run", If you want run as offline add "jetty:run -o" "Active Profiles" can be empty In "set Properties" field we can set like skip test. Here I am skipping test. Done, After setting y

remove(unset) property in a property file using ANT PropertyFile task

Using PropertyFile task we can edit the property file during ANT build. Edit property value are very easy and can find here details. http://ant.apache.org/manual/Tasks/propertyfile.html but delete a property or comment a property is the tricky one. If we are using latest ant version (1.8.1 or later), we can delete a property like below. <propertyfile file="my.properties" comment="My properties"> < entry key="propertykey" operation="del"/> < /propertyfile> but the older version that is before 1.8.1 don't have operation called " del ", if we run the command in lower version ant, we will get a error says undefined operation "del". there is workaround instead deleting a property we can comment that property using ant's replace command. < replace file="sample.properties"> < replacefilter token="propertykey" value="#propert

Disable hibernate Optimistic Lock for specific scenario

Optimistic Lock gives more control on concurrent modification on data. That can be achieved very easily in hibernate using @Version column. But in some cases we may have to avoid concurrency check, example background process. To disable Optimistic lock set OptimisticLockMode as NONE for entity class while hibernate is initiating. We can't remove version column that needs Database changes and ORM changes. In this way we can disable Optimistic Lock by code. implement "org.hibernate.event.Initializable" interface override the below method. @Override public void initialize(Configuration cfg) { Iterator<?> persistentClassIterator = cfg.getClassMappings(); while (persistentClassIterator.hasNext()) { PersistentClass persistentClass = PersistentClass.class.cast(persistentClassIterator.next()); Iterator propertyIterator = persistentClass.getDeclaredPropertyIterator(); while (proper

Useful Links & tips

Search This Blog