[JBossWS] - Re: Ejb3 JMSTransportSupport
by jgilbert
This could be handle generically without writing code. Just define the mdb in the deployment descriptor with an env-entry for the real service.
<enterprise-beans>
| <message-driven>
| <ejb-name>AuthorizationCallbackMDB</ejb-name>
| <ejb-class>
| org.jboss.webservice.transport.jms.JMSTransportSupport
| </ejb-class>
| <messaging-type>javax.jms.MessageListener</messaging-type>
| <transaction-type>Container</transaction-type>
| <message-destination-type>javax.jms.Queue</message-destination-type>
| </message-driven>
| <env-entry>
| <env-entry-name>serviceName</env-entry-name>
| <env-entry-type>String</env-entry-type>
| <env-entry-value>AuthorizationCallbackServiceMockBean</env-entry-value>
| </env-entry>
| </enterprise-beans>
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986251#3986251
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986251
19Â years, 7Â months
[JBoss Seam] - Re: more seam resolver issues - how to handle a list that is
by arnieAustin
Granted, I'm inexperienced with JSF. But in all fairness, I created this application following the examples and using the seam-gen program. I was able to alter the first form and got it to work.
I've been looking through the example programs as well, including the DvdStore project and it doesn't exactly correlate to the book due to its complexity.
I did as suggested and I still get the same error. I finds the dpsDriversList component but thinks the dpsDriversFound property is a component.
| 2006-11-15 11:41:24,578 DEBUG [org.jboss.seam.contexts.Lifecycle] >>> Begin web request
| 2006-11-15 11:41:24,609 DEBUG [org.jboss.seam.Component] instantiating Seam component: org.jboss.seam.core.manager
| 2006-11-15 11:41:24,609 DEBUG [org.jboss.seam.core.Manager] No stored conversation
| 2006-11-15 11:41:24,609 DEBUG [org.jboss.seam.contexts.Contexts] found in application context: org.jboss.seam.core.init
| 2006-11-15 11:41:24,609 DEBUG [org.jboss.seam.jsf.AbstractSeamPhaseListener] After restoring conversation context: ConversationContext(3)
| 2006-11-15 11:41:24,609 DEBUG [org.jboss.seam.jsf.SeamVariableResolver] resolving name: dpsDriversFound
| 2006-11-15 11:41:24,609 DEBUG [org.jboss.seam.Component] seam component not found: dpsDriversFound
| 2006-11-15 11:41:24,609 DEBUG [org.jboss.seam.jsf.SeamVariableResolver] could not resolve name
| 2006-11-15 11:41:24,609 DEBUG [org.jboss.seam.jsf.SeamVariableResolver] resolving name: dpsDriversFound
| 2006-11-15 11:41:24,609 DEBUG [org.jboss.seam.Component] seam component not found: dpsDriversFound
| 2006-11-15 11:41:24,609 DEBUG [org.jboss.seam.jsf.SeamVariableResolver] could not resolve name
| 2006-11-15 11:41:24,609 DEBUG [org.jboss.seam.jsf.SeamVariableResolver] resolving name: dpsDriverCriteria
| 2006-11-15 11:41:24,609 DEBUG [org.jboss.seam.Component] seam component not found: dpsDriverCriteria
| 2006-11-15 11:41:24,609 DEBUG [org.jboss.seam.jsf.SeamVariableResolver] could not resolve name
| 2006-11-15 11:41:24,687 DEBUG [org.jboss.seam.jsf.SeamVariableResolver] resolving name: dpsDriverCriteria
| 2006-11-15 11:41:24,687 DEBUG [org.jboss.seam.Component] seam component not found: dpsDriverCriteria
| 2006-11-15 11:41:24,687 DEBUG [org.jboss.seam.jsf.SeamVariableResolver] could not resolve name
| 2006-11-15 11:41:24,687 DEBUG [org.jboss.seam.jsf.SeamVariableResolver] resolving name: dpsDriverCriteria
| 2006-11-15 11:41:24,687 DEBUG [org.jboss.seam.Component] seam component not found: dpsDriverCriteria
| 2006-11-15 11:41:24,687 DEBUG [org.jboss.seam.jsf.SeamVariableResolver] could not resolve name
| 2006-11-15 11:41:24,687 DEBUG [org.jboss.seam.jsf.SeamVariableResolver] resolving name: dpsDriverCriteria
| 2006-11-15 11:41:24,687 DEBUG [org.jboss.seam.Component] seam component not found: dpsDriverCriteria
| 2006-11-15 11:41:24,687 DEBUG [org.jboss.seam.jsf.SeamVariableResolver] could not resolve name
| 2006-11-15 11:41:24,687 DEBUG [org.jboss.seam.jsf.SeamVariableResolver] resolving name: dpsDriverCriteria
| 2006-11-15 11:41:24,687 DEBUG [org.jboss.seam.Component] seam component not found: dpsDriverCriteria
| 2006-11-15 11:41:24,687 DEBUG [org.jboss.seam.jsf.SeamVariableResolver] could not resolve name
| 2006-11-15 11:41:24,687 DEBUG [org.jboss.seam.jsf.SeamVariableResolver] resolving name: dpsDriversFound
| 2006-11-15 11:41:24,687 DEBUG [org.jboss.seam.Component] seam component not found: dpsDriversFound
| 2006-11-15 11:41:24,687 DEBUG [org.jboss.seam.jsf.SeamVariableResolver] could not resolve name
| 2006-11-15 11:41:24,687 DEBUG [org.jboss.seam.jsf.SeamVariableResolver] resolving name: dpsDriversFound
| 2006-11-15 11:41:24,687 DEBUG [org.jboss.seam.Component] seam component not found: dpsDriversFound
| 2006-11-15 11:41:24,687 DEBUG [org.jboss.seam.jsf.SeamVariableResolver] could not resolve name
| 2006-11-15 11:41:24,687 DEBUG [org.jboss.seam.util.Naming] JNDI InitialContext properties:{java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory, java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces}
| 2006-11-15 11:41:24,687 DEBUG [org.jboss.seam.jsf.SeamExtendedManagedPersistencePhaseListener] committing transaction after phase: PROCESS_VALIDATIONS(3)
| 2006-11-15 11:41:24,687 DEBUG [org.jboss.seam.util.Naming] JNDI InitialContext properties:{java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory, java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces}
| 2006-11-15 11:41:24,687 DEBUG [org.jboss.seam.util.Naming] JNDI InitialContext properties:{java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory, java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces}
| 2006-11-15 11:41:24,687 DEBUG [org.jboss.seam.jsf.SeamExtendedManagedPersistencePhaseListener] beginning transaction prior to phase: RENDER_RESPONSE(6)
| 2006-11-15 11:41:24,687 DEBUG [org.jboss.seam.util.Naming] JNDI InitialContext properties:{java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory, java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces}
| 2006-11-15 11:41:24,687 DEBUG [org.jboss.seam.Component] instantiating Seam component: facesMessages
| 2006-11-15 11:41:24,718 DEBUG [org.jboss.seam.jsf.SeamVariableResolver] resolving name: dpsDriversFound
| 2006-11-15 11:41:24,718 DEBUG [org.jboss.seam.Component] seam component not found: dpsDriversFound
| 2006-11-15 11:41:24,718 DEBUG [org.jboss.seam.jsf.SeamVariableResolver] could not resolve name
| 2006-11-15 11:41:24,718 DEBUG [org.jboss.seam.jsf.SeamVariableResolver] resolving name: dpsDriversFound
| 2006-11-15 11:41:24,718 DEBUG [org.jboss.seam.Component] seam component not found: dpsDriversFound
| 2006-11-15 11:41:24,718 DEBUG [org.jboss.seam.jsf.SeamVariableResolver] could not resolve name
| 2006-11-15 11:41:24,718 DEBUG [org.jboss.seam.jsf.SeamVariableResolver] resolving name: dpsDriversFound
| 2006-11-15 11:41:24,718 DEBUG [org.jboss.seam.Component] seam component not found: dpsDriversFound
| 2006-11-15 11:41:24,718 DEBUG [org.jboss.seam.jsf.SeamVariableResolver] could not resolve name
| 2006-11-15 11:41:24,718 DEBUG [org.jboss.seam.jsf.SeamVariableResolver] resolving name: dpsDriversFound
| 2006-11-15 11:41:24,718 DEBUG [org.jboss.seam.Component] seam component not found: dpsDriversFound
| 2006-11-15 11:41:24,718 DEBUG [org.jboss.seam.jsf.SeamVariableResolver] could not resolve name
| 2006-11-15 11:41:24,718 DEBUG [org.jboss.seam.core.Manager] Discarding conversation state: 3
| 2006-11-15 11:41:24,718 DEBUG [org.jboss.seam.contexts.Lifecycle] flushing page context
| 2006-11-15 11:41:24,734 DEBUG [org.jboss.seam.util.Naming] JNDI InitialContext properties:{java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory, java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces}
| 2006-11-15 11:41:24,734 DEBUG [org.jboss.seam.jsf.SeamExtendedManagedPersistencePhaseListener] committing transaction after phase: RENDER_RESPONSE(6)
| 2006-11-15 11:41:24,734 DEBUG [org.jboss.seam.util.Naming] JNDI InitialContext properties:{java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory, java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces}
| 2006-11-15 11:41:24,734 DEBUG [org.jboss.seam.contexts.Lifecycle] After render response, destroying contexts
| 2006-11-15 11:41:24,734 DEBUG [org.jboss.seam.contexts.Lifecycle] destroying event context
| 2006-11-15 11:41:24,734 DEBUG [org.jboss.seam.contexts.Contexts] destroying: org.jboss.seam.core.manager
| 2006-11-15 11:41:24,734 DEBUG [org.jboss.seam.contexts.Contexts] destroying: org.apache.myfaces.application.jsp.JspStateManagerImpl.SERIALIZED_VIEW
| 2006-11-15 11:41:24,734 DEBUG [org.jboss.seam.contexts.Contexts] destroying: com.sun.facelets.legacy.ELCONTEXT
| 2006-11-15 11:41:24,734 DEBUG [org.jboss.seam.contexts.Lifecycle] destroying conversation context
| 2006-11-15 11:41:24,734 DEBUG [org.jboss.seam.contexts.Contexts] destroying: facesMessages
| 2006-11-15 11:41:24,734 DEBUG [org.jboss.seam.contexts.Lifecycle] flushing server-side conversation context
| 2006-11-15 11:41:24,734 DEBUG [org.jboss.seam.contexts.Lifecycle] <<< End web request
| 2006-11-15 11:41:24,734 DEBUG [org.jboss.seam.util.Naming] JNDI InitialContext properties:{java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory, java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces}
|
In regards to the @Factory, page 13, item 5, states that the Factory method
tells the system to call this method upon first invocation to preload data.
There is nothing to preload until the user has entered a search criteria. The
first time in, yea, there wouldn't be a variable created. But the second time
in it should create and populate the dpsDriverCriteria property, but again,
it treats that as a component, not a property of the DpsDriversList object.
and again, following the examples in the book, shouldn't
<h:commandButton styleClass="formButton" action="#{dpsDriversList.findDpsDrivers}" value="Search"/>
invoke the method dpsDriversList.findDpsDrivers() ?!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986248#3986248
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986248
19Â years, 7Â months