Gilbert Tan

Greenhorn
+ Follow
since May 29, 2009
Merit badge: grant badges
For More
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Gilbert Tan

Well ... May be you have set all required parameters. But before coming to the page, you may definitely do some processing of data (Most probably you are calling the business layer/ data access later).

When, an exception is thrown out from any of those layers, this situation can occur. Because, due to the exception, the objects being accessed in this page are not properly set (in session/ renderRequest).
13 years ago
There are many ways to do this. And some approaches are portlet standard/ container specific.

1. If you are using IBM Portal Server, you can use 'Portlet Wiring'. This is compatible even with JSR168 standard.
http://publib.boulder.ibm.com/infocenter/wpdoc/v510/index.jsp?topic=/com.ibm.wp.ent.doc/wps/wpsc2aconfig.html

2. Another simple idea is to use the friendly URL of each page. Friendly URLs for pages are configured when you are configuring the portal pages. You can redirect the the user to the other portal page, and then that page loads, the doView (JSR168) in the target portlet is called. Before you redirect you can set the parameter values to the portlet session (both source and target portlets should have to be bundled as a single application).
13 years ago
Once I had the same problem when i try to integrate/comfigure OracleAQ with JbossAS. I have an alternative solution for this if this configuration thing does not work. You can write a JMS Listener application which listens to that foreign queue. You may integrate this application to the enterprise application that resides on the app server. Once you read a message just enqueue it into a local queue. You can easily access local queues rite.
This is a bug. But there are two ways to overcome this issue.

1. Establish the connection using DriverManager
Connection conn = DriverManager.getConnection(url, user, password)
ArrayDescriptor descriptor = ArrayDescriptor.createDescriptor(Oracle Dictionary Type, conn);

2. Using the physical connection. In this approach make sure to close the original connection and to NOT to close the physical connection.
Connection conn = this.connection; //Obtained by InitialContext.lookup(jndiDataSourceName)
Connection physicalCon = ((WrappedConnection) conn).getUnderlyingConnection();
ArrayDescriptor descriptor = ArrayDescriptor.createDescriptor(Oracle Dictionary Type, physicalCon);
......
......//dont close physicalCon
conn.close();

For the second approach we need to have a reference to jboss-common-jdbc-wrapper.jar to build the package. But we dont need to bundle that jar with the final ear/war. Boz its already there in Jboss.
14 years ago