Samuel just pointed me at the answer - the param is coming from the previous request. So when you submit the form (and it evalutates the rendered expression to check whether the button push is valid) the param isn't available (it's the next request).
I would suggest pushing (e.g. in pages.xml, a @Factory) your param.mode variable into page scope when the page is loaded, then it will be there when you submit the page.
Alternatively you can use a h:commandLink with a nested f:param to propagate the parameter.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4091730#4091730
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4091730
I have a large project that I am splitting into too separate ear files. I have modified the build script and config files to build two different ear files (two different build targets). I've almost got it working but I have hit a wall: the main jar file never gets scanned for components.
that is,
project.ear
+project.jar <--never gets scanned
+project.war
I know there is some config param I am missing but I can't figure it out.
I get this:
| 13:10:52,858 INFO [EJB3Deployer] Deployed: file:/home/dustin/rhdevstudio/jboss-eap/jboss-as/server/default/deploy/trend.ear/trend.jar/
|
but it never scans.
my jboss-app.xml
| <jboss-app>
| <loader-repository>
| seam.jboss.org:loader=trend
| </loader-repository>
| </jboss-app>
|
my application.xml
| <application xmlns="http://java.sun.com/xml/ns/javaee"
| xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
| xsi:schemaLocation="http://java.sun.com/xml/ns/javaeehttp://java.sun.com/xml/ns/javaee/application_5.xsd"
| version="5">
|
| <display-name>Trend</display-name>
|
| <module>
| <web>
| <web-uri>trend.war</web-uri>
| <context-root>/</context-root>
| </web>
| </module>
|
| <module>
| <ejb>trend.jar</ejb>
| </module>
|
| <!-- Seam and EL -->
| <module>
| <ejb>jboss-seam.jar</ejb>
| </module>
| </application>
|
Any help is appreciated,
Dustin
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4091727#4091727
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4091727
In my (limited) experience:
EntityHome is most useful when you need to do CRUD operations on a single entity. It makes it super-convenient if you do things the "seam-gen way".
If you don't want to do things that way, it can be hard to work with. So, for example, if you want a component that does CRUD simultaneously on multiple entity objects, then I think you're better off with an EntityController.
EntityHome extends EntityController, by the way, which is why most of the methods are the same. EntityController really just provides a ton of convenience methods.
I find that I use EntityController more often than EntityHome.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4091726#4091726
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4091726
Hello,
using wsconsume, I generated a webservice with all corresponding classes. In the WSDL there is one field xs:anyType that should be mapped to Object.
In the webservice, if I do a System.out.println of the corresponding object, I go null while there is data in the soaprequest.
How can I access the data coming in the xs:anyType ? I would like to get the xml representation of this block of data ?
Many thanks in advance
Vincent
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4091720#4091720
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4091720