[Design of JBoss Portal] - Issue with JSF <f:view> tag
by vaalati
Hi,
I am trying to use JSF to develop a portlet and when I load the Portlet in a page I get an error which says
javax.portlet.PortletException: Org.apache.jasper.JasperException:Exception in JSP
And this exception points to the line in the JSP where the <f:view> tag is defined. I have pasted the code in my JSP below. Could some one please tell me what is wrong with it and why I am getting the error.
I am extending the GenericPortlet to write my own Portlet class. I hope this should not be an issue, correct?
Thanks much,
Vijay
<%@ page language="java" session="true" %>
<%@ page import = "java.util.HashMap" %>
<%@ page import = "javax.swing.*" %>
<%@ page import = "javax.portlet.PortletSession" %>
<%@ taglib uri="http://java.sun.com/jsf/html" prefix="h" %>
<%@ taglib uri="http://java.sun.com/jsf/core" prefix="f" %>
<%@ taglib uri="/WEB-INF/tld/portlet.tld" prefix="portlet" %>
<portlet:defineObjects/>
<portlet:actionURL var="loginAction">
<portlet:param name="command" value="doLogin" />
</portlet:actionURL>
<%
HashMap dbMap = new HashMap();
dbMap.put((Object)(new String("DB 1")),(Object)(new String("1")));
dbMap.put((Object)(new String("DB 2")),(Object)(new String("2")));
%>
ADM Login Page
<f:view>
</f:view>
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4026062#4026062
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4026062
19 years, 1 month
[Design of JBoss Build System] - Re: New JBoss Deploy Plugin
by scott.stark@jboss.org
I tried the deploy target for the current jbossxb-2.0.0.CR1 I'm working on, and I did not have the jboss.repository.root define in my local settings.xml:
| [INFO] [jar:jar]
| [INFO] Building jar: /home/svn/Common/tags/jbossxb-2.0.0.CR1/target/jboss-xml-binding.jar
| [INFO] Preparing source:jar
| [WARNING] Removing: jar from forked lifecycle, to prevent recursive invocation.[INFO] No goals needed for project - skipping
| [INFO] [source:jar {execution: default}]
| [INFO] Building jar: /home/svn/Common/tags/jbossxb-2.0.0.CR1/target/jboss-xml-binding-sources.jar
| [INFO] [install:install]
| [INFO] Installing /home/svn/Common/tags/jbossxb-2.0.0.CR1/target/jboss-xml-binding.jar to /usr/Repository/repository.jboss.com/maven2/jboss/jbossxb/2.0.0.CR1/jbossxb-2.0.0.CR1.jar
| [INFO] Installing /home/svn/Common/tags/jbossxb-2.0.0.CR1/target/jboss-xml-binding-sources.jar to /usr/Repository/repository.jboss.com/maven2/jboss/jbossxb/2.0.0.CR1/jbossxb-2.0.0.CR1-sources.jar
| [INFO] [deploy:deploy]
| Uploading: file:///usr/Repository/repository.jboss.com/maven2/jboss/jbossxb/2.0.0.CR...
| 355K uploaded
| [INFO] Retrieving previous metadata from cvs-file-repository
| [INFO] Uploading repository metadata for: 'artifact jboss:jbossxb'
| [INFO] Retrieving previous metadata from cvs-file-repository
| [WARNING] *** CHECKSUM FAILED - Error retrieving checksum file for jboss/jbossxb/2.0.0.CR1/jbossxb-2.0.0.CR1.pom - IGNORING
| [INFO] Uploading project information for jbossxb 2.0.0.CR1
| Uploading: file:///usr/Repository/repository.jboss.com/maven2/jboss/jbossxb/2.0.0.CR...
| 240K uploaded
| [INFO] ------------------------------------------------------------------------[INFO] BUILD SUCCESSFUL
| [INFO] ------------------------------------------------------------------------[INFO] Total time: 55 seconds
| [INFO] Finished at: Wed Mar 07 16:25:06 PST 2007
| [INFO] Final Memory: 13M/293M
| [INFO] ------------------------------------------------------------------------
|
Maybe the CHECKSUM warning I can gather something is missing, but it would be good if the warning could say that jboss.repository.root was not defined or was pointing to an invalid location. However, after defining jboss.repository.root, I'm still not seeing any attempt to load jars to the ${jboss.repository.root}/jboss/jbossxb/2.0.0.CR1 location as would be expected:
| [INFO] [jar:jar]
| [INFO] Building jar: /home/svn/Common/tags/jbossxb-2.0.0.CR1/target/jboss-xml-binding.jar
| [INFO] Preparing source:jar
| [WARNING] Removing: jar from forked lifecycle, to prevent recursive invocation.[INFO] No goals needed for project - skipping
| [INFO] [source:jar {execution: default}]
| [INFO] Building jar: /home/svn/Common/tags/jbossxb-2.0.0.CR1/target/jboss-xml-binding-sources.jar
| [INFO] [install:install]
| [INFO] Installing /home/svn/Common/tags/jbossxb-2.0.0.CR1/target/jboss-xml-binding.jar to /usr/Repository/repository.jboss.com/maven2/jboss/jbossxb/2.0.0.CR1/jbossxb-2.0.0.CR1.jar
| [INFO] Installing /home/svn/Common/tags/jbossxb-2.0.0.CR1/target/jboss-xml-binding-sources.jar to /usr/Repository/repository.jboss.com/maven2/jboss/jbossxb/2.0.0.CR1/jbossxb-2.0.0.CR1-sources.jar
| [INFO] [deploy:deploy]
| Uploading: file:///usr/Repository/repository.jboss.com/maven2/jboss/jbossxb/2.0.0.CR...
| 355K uploaded
| [INFO] Retrieving previous metadata from cvs-file-repository
| [INFO] Uploading repository metadata for: 'artifact jboss:jbossxb'
| [INFO] Retrieving previous metadata from cvs-file-repository
| [INFO] Uploading project information for jbossxb 2.0.0.CR1
| Uploading: file:///usr/Repository/repository.jboss.com/maven2/jboss/jbossxb/2.0.0.CR...
| 240K uploaded
|
and I don't see anything new under ${jboss.repository.root}/jboss/jbossxb
| [starksm@succubus jbossxb-2.0.0.CR1]$ ls /usr/Repository/repository.jboss.com/jboss/jbossxb/
| 1.0.0.CR3/ 1.0.0.CR6.patch01/ 1.0.1.TEST/ lib/
| 1.0.0.CR4/ 1.0.0.CR7/ 1.0RC1/ snapshot/
| 1.0.0.CR5/ 1.0.0.CR8/ 1.0RC2/
| 1.0.0.CR5_JBoss-4.0.4.GA/ 1.0.0.CR9/ as405-snapshot/
| 1.0.0.CR6/ 1.0.0.CR9-brew/ CVS/
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4026058#4026058
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4026058
19 years, 1 month
[Design of EJB 3.0] - Re: IsLocalInterceptor not detecting local container
by bstansberry@jboss.com
I (mostly) understand what's going on here, but need input from the rest of the EJB3 team on how to fix it and resolve EJBTHREE-881. I'll post separately later about the bit I don't understand.
Basic problem is very simple:
1) A invocation is made on a parent bean with REQUIRED tx semantics. Parent delegates to an @Remote nested child; tx is associated with the thread.
2) IsLocalInterceptor will only attempt to directly optimize the call to the local bean if the interceptor instance itself was created in the local VM. So, if an SFSB fails over, the interceptor contained in any nested bean proxy will not have been created in the failover VM and IsLocalInterceptor will not optimize the call.
3) Since the call isn't optimized locally, ClientTxPropagationInterceptor adds transaction metadata to the invocation context.
4) org.jboss.remoting.Client detects that the bean *is* available locally, and executes it locally.
5) TxPropagationInterceptor throws an exception when it finds a tx bound to the thread and tx metadata associated with the invocation that it thinks it should import.
A couple possible solutions come to mind, but I don't know enough to recommend one and certainly won't implement one without someone's OK:
Option A) Make IsLocalInterceptor work more like the EJB3 InvokerInterceptor.
InvokerInterceptor performs the following check when deciding whether to optimize a call locally:
i) check if the interceptor was created in the VM (same as the IsLocalInterceptor).
ii) if not, check if the invocation is for a clustered bean.
iii) if i == true || ii == true, check if the target bean exists locally.
IsLocalInterceptor could be made to work the same way. Odd bit is checking if the invocation is for a clustered bean. That could be done by checking the invocation metadata for any of the cluster-related bindings.
Option B) Does TxPropagationInterceptor need to fail if there is already a tx associated with the thread? Could it just accept the existing tx and not bother importing the tx specified in the metadata? Is there any scenario other than this one where a tx would be associated with the thread?
Me thinks Option B is not good, but if there is a reason Option A is no good, it may be needed.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4026031#4026031
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4026031
19 years, 1 month