[JBoss Portal] .jsp caching or something similar in jboss portal 2.6.5?
by Alexander Lvov
Hi i am experimenting with that jsp example helloworldjspportlet.war that
is provided for jboss portal 2.6.5
and have problems with quite basic things. In the java portlet i can see
that there are jsp pages
used for each of those 3 modes (View, Edit and Help), view.jsp, view2.jsp,
edit.jsp and help.jsp
So i figured i should be able to use other jsp pages like that (forex
index.jsp) but the portal just dont seem to except anything else but
view.jsp and view2.jsp in view mode so then i simply take a copy of view.jsp
and change text in it i still get the old view.jsp. And yes i am sure i am
building and deploying stuff correctly, i was actually been able to change
context of view.jsp to
something else but not to use index.jsp or something instead.
rRequest.setAttribute("yourname", sYourName);
PortletRequestDispatcher prd =
getPortletContext().getRequestDispatcher("/WEB-INF/jsp/index.jsp");
prd.include(rRequest, rResponse);
Another problem i experienced is that i dont seem to be able to bundle
images in the same .war
When i use <img src="http://localhost:8080/portal/cotent/default/....> way
of refering to the picture then no problem
but if i place the picture in the same map in the .war as the jsp page and
directly refer to it then no, it wont find it.
I am using Jboss Portal 2.6.5 GA
Any Experiences, Ideas on that matter ?
/Alexander
18 years
[JBossWS] - Error on starting jbossws-native-3.0.2.GA with custom server
by zeko
Hi,
our server setup defines follwowing properties:
| -Djboss.platform.mbeanserver \
| -Djavax.management.builder.initial=org.jboss.system.server.jmx.MBeanServerBuilderImpl \
| -Djboss.server.base.dir=${DOMAIN_HOME}/config \
| -Djboss.server.home.dir=${DOMAIN_HOME} \
| -Djboss.server.home.url=file:${DOMAIN_HOME}/config \
| -Djboss.server.temp.dir=${DOMAIN_HOME}/tmp \
| -Djboss.server.data.dir=${DOMAIN_HOME}/data \
| -Djboss.server.log.dir=${DOMAIN_HOME}/log"
|
|
which runs fine using the previous version of JbossWS.
Using the standard directory structure as depicted in
http://docs.jboss.org/jbossas/jboss4guide/r2/html/ch01.html and *not* defining those properties is fine, too.
So I gues there must be some hard coded dependencies.
first error is:
| 16:04:38,815 ERROR [AbstractKernelController] Error installing to Configured: name=WSDeployerHook_JAXWS_PRE_JSE state=Instantiated mode=Manu
| al requiredState=Installed
| org.jboss.joinpoint.spi.JoinpointException: Property runtime not found for AbstractBeanInfo(a)3e1d25{name=org.jboss.wsf.container.jboss42.JAXW
| SDeployerHookPreJSE classInfo= properties=[deploymentType, class, phaseTwoInterceptors, deploymentManagerName, deploymentModelFactory, phase
| OneInterceptors, deploymentAspectManager] methods=[, , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ] constructors=[] e
| vents=}
| at org.jboss.kernel.plugins.config.Configurator.resolveProperty(Configurator.java:659)
| at org.jboss.kernel.plugins.config.Configurator.getPropertySetterJoinPoint(Configurator.java:433)
| at org.jboss.kernel.plugins.config.Configurator.getPropertySetterJoinPoints(Configurator.java:398)
| at org.jboss.kernel.plugins.config.AbstractKernelConfigurator.getPropertySetterJoinPoints(AbstractKernelConfigurator.java:112)
| at org.jboss.kernel.plugins.dependency.KernelControllerContextActions$ConfigureAction.installAction(KernelControllerContextActions.j
| ava:313)
| at org.jboss.kernel.plugins.dependency.KernelControllerContextActions$KernelControllerContextAction.install(KernelControllerContextA
| ctions.java:147)
| at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
| at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:226)
| at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:593)
| at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:346)
| at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:438)
| at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:379)
| at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:263)
| at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:164)
| at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.changeBean(AbstractKernelDeployer.java:327)
| at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.changeBeans(AbstractKernelDeployer.java:311)
| at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.change(AbstractKernelDeployer.java:139)
| at org.jboss.kernel.deployment.jboss.JBossBeanDeployment.startService(JBossBeanDeployment.java:81)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
| at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
| at $Proxy0.start(Unknown Source)
| at org.jboss.system.ServiceController.start(ServiceController.java:417)
| at sun.reflect.GeneratedMethodAccessor10.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
| at $Proxy20.start(Unknown Source)
| at org.jboss.deployment.SimpleSubDeployerSupport.startService(SimpleSubDeployerSupport.java:356)
| at org.jboss.deployment.SimpleSubDeployerSupport.start(SimpleSubDeployerSupport.java:127)
| at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
| at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1015)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
| at $Proxy10.deploy(Unknown Source)
| at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
| at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
| at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
| at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
| at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
| at $Proxy0.start(Unknown Source)
| at org.jboss.system.ServiceController.start(ServiceController.java:417)
| at sun.reflect.GeneratedMethodAccessor10.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
| at $Proxy4.start(Unknown Source)
| at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
| at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMet
Any ideas?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160568#4160568
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160568
18 years
[JNDI/Naming/Network] - Re: How to Access EJB over HTTP in remote machine?
by robert.geisler
"ritesh163" wrote : "robert.geisler" wrote : please check whether JBoss starts successfully with your command if you do not have configured standardjboss.xml, jboss.xml and the InvokerURLs.
| The error may be due to InvokerURLs of the servlets which was set to the router ip and jboss starting on internal IP.
did you test that? O: ) imho your bindings seem to be correct, both JBoss instances should bind to their "internal address". anyway i do not know why JBoss cannot find attribute named "RmiBindAddress".
if you enable DEBUG-logging in /conf/log4j.xml we can check what the ServiceConfigurator tries to do and what he actually does.
"ritesh163" wrote : machine A only invokes the EJB of machine B over http. Machine A has external IP and jboss is also starting on that ip. This machine A is connected to machine B through router Ip only. Machine A only knows Router IP of machine B.when message is send through router IP by machine A, this message is redirect to machine B's internal IP by router. Also machine B is starting only in Internal IP.
thank you for clearing it up to me.
in my opinion, your machine A do not need servlets and http-invokers. just machine B need these invokers and servlets, because only the EJBs of machine B will get accessed via http. nonetheless, imho the InvokerURL of the servlets have to point to the "router ip", because machine B create proxies which machine A uses to communicate to machine B. and because machine A (and its proxies) just know the "router ip", machine A has (especially its proxies have) to connect to the "router ip". machine B should never complain about setting the "router ip" as InvokerURL, because not machine B, but only machine A, will ever use the InvokerURL. at least this is my understanding.
regards
robert
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160556#4160556
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160556
18 years