Mujeebur Rahman

Greenhorn
+ Follow
since Jul 10, 2008
Merit badge: grant badges
For More
Cows and Likes
Cows
Total received
In last 30 days
0
Forums and Threads

Recent posts by Mujeebur Rahman

The specified java versions are supported in RAD 7.5. But there is a check with your WAS level . WAS 6 is very well supported in RAD 7.5 if OS is not Windows Vista. .
15 years ago
When the cursor is inside the file (source), you can right click --- Show In -- Navigator . This will highlight the currently opened file in the left navigator panel.

Regards,
Mujeebur Rahman
15 years ago
Check the fix versions between both environments. It seems your problem has been fixed by the WAS fix pack (6.1.0.21) or APAR PK70391. See this APAR description
http://www-01.ibm.com/support/docview.wss?rs=180&uid=swg1PK70391.

Regards,
Mujeebur Rahman
15 years ago

I don't think so that RAD version 6 support JDK 6. I wonder if you have authorized version, what makes not to migrate your RAD to 7 or latest 7.5.
15 years ago
Did you try with the default method as "Preferences--Java--Compiler--Compiler Compliance Level ". Describe more about your problem. What is the IRAD version ?
15 years ago
Hi,

I will not say that the way you have installed Jadclipse plug-in in RAD 7.5 is wrong. The disadvantages you will feel when you distribute RAD installation, install in another location and during upgrade. One need to keep maintaining the list of plug-ins carefully . Updating them is involved with manual efforts.

The correct/approprite way of doing this via new automated mechanism (Equinox p2 Update) so your maintenance (update plug-in, distribue and upgrade RAD) becomes much more easy.

Regards,
Mujeebur Rahman
15 years ago
Incidentally, I was trying to install Jadclipse on my RSA 7.5 just today. Here I have summerized the steps in brief
1. Download Jad.exe

from URL http://web.archive.org/web/20080214075546/http://www.kpdus.com/jad.html and unzip to C:\temp\download\jadnt158

2. Install via Eclipse Equinox
http://webobjects.mdimension.com/jadclipse/3.4

3. Preferences -- Genral -- Editors -- File Associations

.class with jadclipse

4. Preferences -- Java-- Jadclipse -- Path to decompiler -- edit with the path of jad.exe

example C:\temp\download\jadnt158\jad.exe

Thats it folks. Let me know did this help you ?
15 years ago
Hi,

RAD 7.5 now using the Eclipse 3.4's feature of Equinox P2 Update mechanism. This is much more sophisticated and easy way of installing/updating 3rd party plug-ins .

Here are steps in brief

1. In the Available Software tab, Click on "Add Site" and add the URL(repository of the plug-in).

2. Now click on the newly added site and install the plug-in from the list

3. Restart RAD/ Eclipse


You can still use the old way of installing like Software Update -- Find and Install but to do this you need to enable the capablity "classic update" from Prefefrences--General--Capablities--Classic Update. If you enable this, you will get two software update submenu in Help. The first one will be old style (classic update) the second one will be new way of installing plug-ins.

Let me know the results.

Regards,
Mujeebur Rahman
15 years ago
Hi,

The best pattern is not to write the Transaction related stuff into MDB. It should be delegated to Session bean which is meant for that (Message Facade). I was doing similar your same requirement while ago and I couldn't see any problem.

Try this and let me know the results


Originally posted by Carlos Andres Holguin Arboleda:
Hi, Jeanne. My onMessage() invoke the next method:

public void insert( InfoOperacion operacion) throws AuditoriaException
{
Connection connection = null;
PreparedStatement statement = null;
ResultSet rs = null;





String sql="INSERT INTO COMPONENTE_AUDITORIA ( COMPONENTE_AUDITORIA_ID_OP"+
",COMPONENTE_AUDITORIA_USUARIO,COMPONENTE_AUDITORIA_US_BD"+
",COMPONENTE_AUDITORIA_F_HORA,COMPONENTE_AUDITORIA_ACCION"+
",COMPONENTE_AUDITORIA_OBJETO," +
"COMPONENTE_AUDITORIA_ANTES,COMPONENTE_AUDITORIA_DESPUES" +
",COMPONENTE_AUDITORIA_OID, COMPONENTE_AUDITORIA_IP) " +
"values (?,?,?,?,?,?,?,?,?,?)";
try
{
connection = DBLocator.getConnection ();
//Buscar ultimo id
statement = connection.prepareStatement("SELECT MAX(COMPONENTE_AUDITORIA_ID_OP) FROM COMPONENTE_AUDITORIA");
rs = statement.executeQuery();
if(rs.next()) {
operacion.setIdOperacion(rs.getInt(1)+1);
} else {
operacion.setIdOperacion(1);
}
rs.close();
statement.close();
statement = connection.prepareStatement ( sql );

statement.setInt(1, operacion.getIdOperacion());
statement.setString(2,operacion.getUsuario());
statement.setString(3,operacion.getUsuarioBD());
statement.setString(4,operacion.getFechaHora());
statement.setString(5,operacion.getAccion());
statement.setString(6,operacion.getObjeto());
statement.setString(7,operacion.getAntes().toString());
statement.setString(8,operacion.getDespues().toString());
statement.setString(9,operacion.getOid());
statement.setString(10,operacion.getIp());
statement.executeUpdate ( );
}
catch(Exception e)
{
throw new AuditoriaException(e.getMessage(),e);
}
finally
{
DBLocator.closeDBObject(rs);
DBLocator.closeDBObject(statement);
DBLocator.closeDBObject(connection);

}
}
Do you have any suggestion for this problem??, thanks

[ September 21, 2008: Message edited by: Carlos Andres Holguin Arboleda ]

[ September 21, 2008: Message edited by: Carlos Andres Holguin Arboleda ]

16 years ago
Which version of WAS , you are using?. As far as I remember JMSAdmin tool was used in WAS version 3.5/4 . In WAS 6.x versions you can do JMS configurations in admin console.
-----------------

I hope your os is Windows. I try to explain you with brief steps. You will find number of tutorials online.

1) After you install MQ, you will get GUI from MQ software. create Queue Manager and Queues via this GUI.

You can also use the script utility (I think you can get it by some thing like "run MQSC".)

2) You can do all the JMS configurations like creating Queue Connection Factory, Destination queues, Listener Port via WAS admin console.

3) For starting stuff, you can try with Message Driven Bean. You have to asscociate Listener Port via MDB's deployment descriptor.

4) You can open the Queue via MQ Explorer and place some test message.

5) If you have done the right steps, the message should reach your MDB.

Let me know if any specific issues.


Regards,
Mujeebur Rahman






Originally posted by Vishal Vohra:
Hello,

I am new to MQ and want to know how to setup the MQ environment.
I have WebSphere installed on my system with "MQ Messaging Provider" that comes with default with WebSphere.
I have found some PDF's from IBM explaining how to code using MQ Base JAVA and MQ JMS java classes, but I am finding it difficult to set up the MQ environment like the Queue Manager, Connection Factory, Queue itself and the destination.
I also came to know that this environment setting can be done with the help of JMSAdmin tool, but where I can find this tool.
On my system I have RAD installed with a plugin support for WebSphere, I mean the WebSphere has not been installed seperately, it is being used from the RAD and therefore I am not able to find JMSAdmin tool.

Please let me know how to set up Queue managers, connection factory, queue and the destination and once configured how can I administer them from WebSphere Administration console.

16 years ago
I meant it should be useBean instead of usebean

Originally posted by Mujeebur Rahman:
Check your code weather login.jsp uses <jsp:useBean>

The problem seems with the lower case. Let me know the result.


16 years ago
Check your code weather login.jsp uses <jsp:useBean<br /> <br /> The problem seems with the lower case. Let me know the result.<br /> <br /> <br />

Originally posted by Lee Sha:<br /> Hi,<br /> I am trying to migrate my application from WSAD5.1 to RAD7. In RAD7, it is throwing the below exception when I try to access a jsp page which uses "usebean":<br /> <br /> Servlet Error]-[/logon/logon.jsp]: com.ibm.ws.jsp.translator.JspTranslationException: JSPG0227E: Exception caught while translating /logon/logon.jsp: <br /> /logon/logon.jsp(11,1) --> JSPG0145E: Unknown JSP element : jsp:usebean

at com.ibm.ws.jsp.translator.visitor.JspVisitor.processJspElement(JspVisitor.java:263)
at com.ibm.ws.jsp.translator.visitor.JspVisitor.processChildren(JspVisitor.java:309)
at com.ibm.ws.jsp.translator.visitor.JspVisitor.processJspElement(JspVisitor.java:139)
at com.ibm.ws.jsp.translator.visitor.JspVisitor.visit(JspVisitor.java:121)
at com.ibm.ws.jsp.translator.JspTranslator.processVisitors(JspTranslator.java:121)
at com.ibm.ws.jsp.translator.utils.JspTranslatorUtil.translateJsp(JspTranslatorUtil.java:181)
at com.ibm.ws.jsp.translator.utils.JspTranslatorUtil.translateJspAndCompile(JspTranslatorUtil.java:83)
at com.ibm.ws.jsp.webcontainerext.AbstractJSPExtensionServletWrapper.translateJsp(AbstractJSPExtensionServletWrapper.java:349)
at com.ibm.ws.jsp.webcontainerext.AbstractJSPExtensionServletWrapper._checkForTranslation(AbstractJSPExtensionServletWrapper.java:317)
at com.ibm.ws.jsp.webcontainerext.AbstractJSPExtensionServletWrapper.checkForTranslation(AbstractJSPExtensionServletWrapper.java:226)
at com.ibm.ws.jsp.webcontainerext.AbstractJSPExtensionServletWrapper.handleRequest(AbstractJSPExtensionServletWrapper.java:131)
at com.ibm.ws.jsp.webcontainerext.AbstractJSPExtensionProcessor.handleRequest(AbstractJSPExtensionProcessor.java:270)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:308)
at com.ibm.ws.webcontainer.extension.DefaultExtensionProcessor.handleRequest(DefaultExtensionProcessor.java:472)
at com.ibm.ws.wswebcontainer.extension.DefaultExtensionProcessor.handleRequest(DefaultExtensionProcessor.java:111)
at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3129)
at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:238)
at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:811)
at com.ibm.ws.wswebcontainer.WebContainer.handleRequest(WebContainer.java:1433)
at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:93)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:465)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:394)
at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:102)
at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:152)
at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:213)
at com.ibm.io.async.AbstractAsyncFuture.fireCompletionActions(AbstractAsyncFuture.java:195)
at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:136)
at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:194)
at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:741)
at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:863)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1510)

Does anyone know what may be the reason for this?

[ August 21, 2008: Message edited by: Lee Sha ]

16 years ago
I don't think so that special settings required. debug like this,
1) Clear the cached JSP in AppServer temp folder (java file, class files etc)
2) Access this JSP
3) Check the .java file and .class file(decompile) to see weather it has really translated JSP code into java.

Eager to see your results.
16 years ago
Before answering your stuff, one basic query.

Do any of the JSP expression work in your code?.
16 years ago