[JBoss Portal Users] - Partial refresh does not seem to work for JBOSS Portlet
by Brian13
Hello,
I have embeded a recursive rich:tree implementation into JBOSS Portlet in a Portal application ... The implementation ported fine into the portlet ... But the problem that arises is that the partial page refresh of the Portlet does not seem to work quite as it is supposed to.
For the rich:tree I have the switchType set to "ajax" but when any nodes are selected
in the tree which causes a selection to be made, the whole portlet gets refreshed.
I have a simpleTogglePanel encapsulating the rich:tree which should only refresh
at the most upon the selection of the nodes in the tree ... Is there any way partial refresh of the portlet can be controlled so that only the rich:tree and the other components in the portlet which are rich:dataTable types all do not get refreshed all at the same time. I am using the JBOSS Portal version 2.7.2 and JBOSS AS 4.2.3 GA
Thank you in advance.
-- Brian
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4256230#4256230
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4256230
16 years, 7 months
[JBoss Messaging Users] - Re: Easiest way to bind IBM WS MQ hosted 'Queue' to name in
by ben.cotton＠rutgers.edu
Thanks for your reply gaohoward.
I modified the code as you indicated:
| Properties props = new Properties();
| props.setProperty(Context.INITIAL_CONTEXT_FACTORY,"org.jnp.interfaces.NamingContextFactory");
| props.setProperty(Context.PROVIDER_URL,"jnp://10.4.164.105:11099");
|
|
|
| props.setProperty(Context.URL_PKG_PREFIXES, "org.jboss.naming:org.jnp.interfaces");
|
|
| Context ctx = new InitialContext(props);
|
|
| ConnectionFactory factory = (ConnectionFactory)ctx.lookup("IVTCF");
|
| System.out.println("looked up 'IVTCF' javax.jms.ConnectionFactory established! 'factory'=["+
| factory+
| "]");
|
|
But I still only get 'factory' values == NULL after executing the lookup().
Via the JBoss admin console, I checked the value for 'IVTCF' in the JNDI global namespace and it shows a correct and expected value.
Global JNDI Namespace
|
|
| +- IVTCF (class: com.ibm.mq.connector.outbound.ConnectionFactoryImpl)
|
I guess in the worst case, I could code this Producer to directly invoke the WS MQ implementation of com.ibm.msg.client.jms.JmsConnectionFactory, but I was hoping I could just deploy the WS MQ JCA Resource adapter to my JBoss instance, config a Resource-->ConnectionFactory via the JBoss admin console, and then just do a 'lookup' on that ConnFactory to have all the plumbing (from JBoss to WS MQ) done for me transparently (via JCA).
Hoping to avoid coding directly to com.ibm.msg.client.jms.* API, do you have any other ideas/recommendations on how I might be able to get this to work via JBoss/JCA?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4256228#4256228
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4256228
16 years, 7 months
[EJB] - Re: NameAlreadyBoundException when migrate from JBoss 4.2.2.
by wluque
Hi , I fixed it this way :
fmk-entities.jar (ejb/persistence) ->> convert to a Java Project (POJO) .
Move persistence.xml to EAR/META-INF .
and Add <jar-file>fmk-entities.jar</jar-file>
My final arquitecture.
FMK-EAR
--> fmk.war ( seam 2.2 ) PLATFORM CONSOLE
--> fmk-seam.jar (ejb) ( My seam's basic actions )
--> fmk-serviceEjb.jar (ejb) ( My plattaform services )
--> fmk-entities.jar (PJO/persistence) ( My basic plattaform entities / persitence unit)
DC-EAR ( Application over my FMK platform)
--> dc.war ( seam 2.2 . Utilice dc-seam/fmk-seam )
--> dc-seam.jar (ejb) ( seam actions specific of dc )
------> components.properties
----------->ndiPattern=dc-ear/\#{ejbName}/local
--> dc-serviceEjb.jar (ejb) ( services of dc / call too fmk-serviceEjb )
---> dc-entities.jar (pojo/persistence) extends BasicEntities of Fmk
--> fmk.war
--> fmk-seam.jar
------> components.properties
----------->ndiPattern=dc-ear/\#{ejbName}/local
--> fmk-serviceEjb.jar
--> fmk-entities.jar
META-INF
--> persistence.xml
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4256222#4256222
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4256222
16 years, 7 months
[JCA] - How to configure JBossWorkManager in JBoss 5.1
by raviraghava
Hi,
I am migrating the application from WebSphere 6.1 to JBoss 5.1. In WebSphere, pieces of code were using default workmanager and asyncbean package. Can you please tell me the right configuration that I need to use in web.xml or applicationContext.xml for using JBossWorkManager. Also, please suggest if I had to make any code changes (I replaced async bean package for WebSphere with JBossWorkManager package). Furnished is the configuration that I have right now but it is throwing Exception. Your help is much appreciated.
Code in applicationContext.xml:
1.
| 2. <bean id="taskExecutor" class="org.springframework.jca.work.jboss.JBossWorkManagerTaskExecutor">
| 3. <property name="workManagerName" value="WorkManager"/>
| 4. <property name="resourceRef" value="true"/>
| 5. </bean>
|
|
Code in web.xml:
1.
| 2. <resource-ref id="ResourceRef_1163654014164">
| 3. <description>WorkManager</description>
| 4. <res-ref-name>WorkManager</res-ref-name>
| 5. <res-type>org.jboss.resource.work.JBossWorkManager</res-type>
| 6. <res-auth>Container</res-auth>
| 7. <res-sharing-scope>Shareable</res-sharing-scope>
| 8. </resource-ref>
|
|
Exception when the application is deployed:
009-09-18 13:25:58,382 SEVERE [org.springframework.web.context.ContextLoader] (HDScanner) Context initialization failed
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'taskExecutor' defined in ServletContext resource [/WEB-INF/applicationContext.xml]: Invocation of init method failed; nested exception is javax.naming.NameNotFoundException: WorkManager not bound
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1338)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:473)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:409)
.
.
.
Caused by: javax.naming.NameNotFoundException: WorkManager not bound
at org.jnp.server.NamingServer.getBinding(NamingServer.java:771)
at org.jnp.server.NamingServer.getBinding(NamingServer.java:779)
Thanks a lot. Your earliest response would be of very great help.
Ravi
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4256221#4256221
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4256221
16 years, 7 months