[JBoss Seam] - Re: @Out frustration
by CptnKirk
Well EVENT obviously won't work because state is destroyed at the end of the request, so it won't be available across redirects (which have 2 requests).
PAGE on the other hand I'm not 100% sure about. I'll admit I don't use page scope. I was under the impression that this was like a mini-session tied to a given instance of a page. So if you had data that was specific to a single page, yet needed to save state across requests you could use page scope. A clickable list with data that changes due to other events on the back end is given as an example in the documentation. So in your case where you navigate back to the same view, I'd expect page scope to work. If you're sure it doesn't, then either I don't understand what page scope actually does, or there may be a bug in Seam.
Page scope in this understanding would seem to leak memory like the session though, as there would be no way to clean up resources of an infrequently used page. In this case, a conversation may still be desirable even though page scope is available. Plus we know it works. :)
It may be that I'm wrong and page scope may simply restrict event data to a given view. However if this were the case, I'd think page would be the narrowest context, and yet the docs say that event is.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3970211#3970211
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3970211
19 years, 7 months
[JBoss Seam] - Re: @Out frustration
by texan
Well, this was just a test example. My application has all sorts of the usual cross-page navigation.
In the example above, the page navigates to itself. The first time you load it (.../test.seam), there's no "bean" in any context, so it's blank. When you click the button, it goes to the action, which returns back to the same page.
It's that last part that confuses me. Since my action returns "/test.xhtml", I was assuming that when the page was rendered, it would see any bean that was placed into the EVENT or PAGE scope. I still don't quite understand what PAGE scope does.
Anyway, I realize that Seam does a redirect to display the page, but I thought that the serialized context was passed along to the page somehow. I can't figure out what is happening in between my action exuction and my page rendering that makes an EVENT or PAGE scoped bean inaccessible to the page.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3970209#3970209
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3970209
19 years, 7 months
[Datasource Configuration] - javax.naming.NameNotFoundException: OracleDS not bound error
by itsmeabhi99
I am trying to Connect to Oracle database through my webapplication and I am getting the following error
14:41:46,536 INFO [ApplicationInitPlugin] Loading DataSource...
14:41:46,536 INFO [ApplicationInitPlugin] Looking up: OracleDS
14:41:46,536 ERROR [ApplicationInitPlugin] Unable to find DataSource
14:41:46,536 ERROR [[/MyApplication]] Servlet /MyApplication threw load() exception
javax.naming.NameNotFoundException: OracleDS not bound
at org.jnp.server.NamingServer.getBinding(NamingServer.java:514)
at org.jnp.server.NamingServer.getBinding(NamingServer.java:522)
at org.jnp.server.NamingServer.getObject(NamingServer.java:528)
at org.jnp.server.NamingServer.lookup(NamingServer.java:281)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:610)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:572)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at com.zsf.struts.plugin.ApplicationInitPlugin.loadDataSource(Unknown Source)
at com.zsf.struts.plugin.ApplicationInitPlugin.init(Unknown Source)
at org.apache.struts.action.ActionServlet.initModulePlugIns(ActionServlet.java:1105)
at org.apache.struts.action.ActionServlet.init(ActionServlet.java:468)........
when i am starting the server however my oracle-service.xml file is deployed and stating that the File is Deployed Successfully with the JNDINAME: OracleDs.
14:39:48,528 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:name=OracleDS,service=DataSourceBinding' to JNDI name 'java:OracleDS'
I am Using JBoss 4.0.3SP1.
I checked in the jmx-console of my application server and OracleDS is listed under java:namespace. Still I am getting this error.
Can any one help me with this error. I will be really thankful.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3970208#3970208
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3970208
19 years, 7 months