[JBoss Seam] - Re: Seam and Adobe Flex
by DavidInTx
There is one example project in cvs which is already has web services built in--seambay (careful--it's not seampay, which is another example project). However, as seambay is not included in the copyexamples task in the build.xml in cvs, you'll have to do the following:
1. Check out seam from cvs.
2. Modify the build.xml that is directly under the main seam directory. Specifically, search for
<target name="copyexamples" description="Copy examples to dist dir">
and then add <include name="seambay/**/*" />
|
to the list of examples to be copied.
3. run "ant dist" in the main seam directory, which contains that build.xml that you just modified. You will get a jboss-seam-1.3.0-ALPHA directory created next to the jboss-seam directory you checked out from cvs.
4. Go into the jboss-seam-1.3.0-ALPHA directory, and modify your build.properties file to point to your jboss location. (Seambay doesn't work with tomcat--that may be why it's not included in copyexamples by default).
5. Still in the jboss-seam-1.3.0-ALPHA directory, go to examples/seambay, and type "ant deploy".
6. Start up jboss, and point to localhost:8080/seam-bay, and play with the example. In particular, register via the regular ui, and then go to the test page and send ws requests as desired.
7. I didn't see any documentation regarding whether or not the wsdl is supposed to be published somewhere. However, when I was watching the jboss startup logs, I saw this message:
anonymous wrote : 10:46:52,401 INFO [WSDLFilePublisher] WSDL published to: file:/C:/Program Files/jboss-4.2.0.GA/server/default/data/wsdl/seam-bay.ear/seam-bay.jar/AuctionServiceService62575.wsdl and sure enough, the wsdl was there. Note that the numbers (62575) seem to change each time I restart jboss.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4052658#4052658
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4052658
19Â years
[JBoss Seam] - Building parent and child in one page
by mustaghattack
I would like to create a questionnaire and its questions in the same page.
The user will be able to add/remove/edit question to a new questionnaire and save/cancel the whole thing at the end.
I have problems for editing a question. Here is the use case :
-> New Questionnaire
-> New Question (1)
-> Save Question (1)
-> Edit Question (1)
-> Cancel changes on Question 1
-> Cancel Questionnaire (everything is rolled back)
I tried few things but I can't get both cancel phase working in a nice way.
Any ideas ??
This is what I tried :
* A questionnaire editor start a conversation on a newQuestionnaire request.
When the user add a question, I just add it to the questionnaire entity question collection.
Problem when editing I can't rollback the user changes (cause the question object is used and modified on update model JSF phase).
The only solution I see is cloning the editing question. But I don't like it.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4052657#4052657
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4052657
19Â years
[JBoss Seam] - Re: Extending Identity/RuleBasedIdentity
by joeyxxx
I keep getting the ff error.
javax.faces.el.PropertyNotFoundException: /login.xhtml @32,66 value="#{identity.myDestination}": Bean: org.jboss.seam.security.RuleBasedIdentity, property: myDestination
| at com.sun.facelets.el.LegacyValueBinding.getValue(LegacyValueBinding.java:58)
| at javax.faces.component.UIOutput.getValue(UIOutput.java:77)
|
I've tried different combinations of annotations on myDestination yet nothing seems to work.
The ff is the code for the subclass I want to use in place of the default identity object
| @Name("org.jboss.seam.core.identity")
| @Scope(ScopeType.SESSION)
| @Intercept(InterceptionType.AFTER_RESTORE_VIEW)
| @Startup
| public class MyIdentity extends RuleBasedIdentity {
|
| private String myDestination;
|
| @Logger Log log;
|
| public void create(){
|
| super.create();
| this.myDestination="xxx is not null";
| log.info("My create is called and destination is set to:"+ myDestination);
| }
|
| public String getMyDestination() {
| return myDestination;
| }
|
| public void setMyDestination(String destination) {
| this.myDestination = destination;
| }
| }
|
The ff is the code in the facelets template
| <h:outputLabel for="myDestination">Destination</h:outputLabel>
| <h:inputText id="myDestination"
| value="#{identity.myDestination}"/>
|
>From the JBoss server logs, the ff entries indicate that an instance of MYIdentity is loaded and that the @Create method is invoked.
| 10:33:01,484 INFO [Component] Component: org.jboss.seam.core.identity, scope: SESSION, type: JAVA_BEAN, class: com.baisidirect.action.MyIdentity
| 10:39:10,616 INFO [MyIdentity] My create is called and myDestination is set to:xxx is not null
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4052654#4052654
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4052654
19Â years
[JBossWS] - wstools exception in jboss4.2
by johnefranklinï¼ yahoo.com
Hi,
I am attaching a wsdl that used to work nicely with JBoss 4.0.5. But when I try to generate the java files from the wsdl using the wstools shipped along with JBoss 4.2, it keeps giving me this error.
Exception in thread "main" org.jboss.ws.WSException: [JAX-RPC 2.3.1.2] Unable to unwrap model group with multiple particles.
at org.jboss.ws.tools.helpers.ReturnTypeUnwrapper.unwrapModelGroup(ReturnTypeUnwrapper.java:120)
at org.jboss.ws.tools.helpers.ReturnTypeUnwrapper.unwrap(ReturnTypeUnwrapper.java:87)
at org.jboss.ws.tools.WSDLToJava.getReturnType(WSDLToJava.java:632)
at org.jboss.ws.tools.WSDLToJava.appendDocParameters(WSDLToJava.java:395)
at org.jboss.ws.tools.WSDLToJava.appendMethods(WSDLToJava.java:290)
at org.jboss.ws.tools.WSDLToJava.createSEIFile(WSDLToJava.java:588)
at org.jboss.ws.tools.WSDLToJava.createSEI(WSDLToJava.java:618)
at org.jboss.ws.tools.WSDLToJava.generateSEI(WSDLToJava.java:186)
at org.jboss.ws.tools.helpers.ToolsHelper.handleWSDLToJavaGeneration(ToolsHelper.java:303)
at org.jboss.ws.tools.WSTools.process(WSTools.java:137)
at org.jboss.ws.tools.WSTools.generate(WSTools.java:69)
at org.jboss.ws.tools.WSTools.generate(WSTools.java:119)
at org.jboss.ws.tools.WSTools.main(WSTools.java:58)
Can someone please look at the wsdl and point me the problem in the wsdl?
regards,
johnf
| <definitions name="EventMonitoringService" targetNamespace="http://com.ws.test/sample"
| xmlns="http://schemas.xmlsoap.org/wsdl/"
| xmlns:ns2="http://com.ws.test/sample"
| xmlns:tns="http://com.ws.test/sample/types"
| xmlns:xsd="http://www.w3.org/2001/XMLSchema"
| xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
| xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"
| xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/">
| <types>
| <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
| targetNamespace="http://com.ws.test/sample/types"
| xmlns:tns="http://com.ws.test/sample/types">
|
| <xsd:simpleType name="DeviceID">
| <xsd:restriction base="xsd:string">
| <xsd:minLength value="0"/>
| </xsd:restriction>
| </xsd:simpleType>
|
| <xsd:complexType name="LogicalEvents">
| <xsd:sequence>
| <xsd:element name="logicalVar1" type="xsd:boolean" minOccurs="0"/>
| <xsd:element name="logicalVar2" type="xsd:boolean" minOccurs="0"/>
| </xsd:sequence>
| </xsd:complexType>
|
| <xsd:complexType name="PhysicalEvents">
| <xsd:sequence>
| <xsd:element name="physicalVar1" type="xsd:boolean" minOccurs="0"/>
| <xsd:element name="physicalVar2" type="xsd:boolean" minOccurs="0"/>
| </xsd:sequence>
| </xsd:complexType>
|
| <xsd:complexType name="FilterEvents">
| <xsd:sequence>
| <xsd:element name="physical" type="tns:PhysicalEvents" minOccurs="0"/>
| <xsd:element name="logical" type="tns:LogicalEvents" minOccurs="0"/>
| </xsd:sequence>
| </xsd:complexType>
|
| <xsd:simpleType name="ErrorValue">
| <xsd:restriction base="xsd:string">
| <xsd:minLength value="0"/>
| </xsd:restriction>
| </xsd:simpleType>
|
| <xsd:complexType name="TestException">
| <xsd:sequence>
| <xsd:element name="errorValue" type="tns:ErrorValue"/>
| <xsd:element name="errorMessage" type="xsd:string" nillable="true"/>
| </xsd:sequence>
| </xsd:complexType>
|
| <xsd:element name="ErrorValue" type="tns:ErrorValue"/>
| <xsd:element name="TestException" type="tns:TestException"/>
|
| <xsd:element name="MonitorEventsRequest">
| <xsd:complexType>
| <xsd:sequence>
| <xsd:element name="deviceID" type="tns:DeviceID"/>
| <xsd:element name="requestFilter" type="tns:FilterEvents" minOccurs="0"/>
| </xsd:sequence>
| </xsd:complexType>
| </xsd:element>
|
| <xsd:element name="MonitorEventsResponse">
| <xsd:complexType>
| <xsd:sequence>
| <xsd:element name="deviceID" type="tns:DeviceID"/>
| <xsd:element name="allotedFilter" type="tns:FilterEvents" minOccurs="0"/>
| </xsd:sequence>
| </xsd:complexType>
| </xsd:element>
| </xsd:schema>
| </types>
|
| <message name="MonitorEventsRequest">
| <part name="parameters" element="tns:MonitorEventsRequest"/>
| </message>
|
| <message name="MonitorEventsResponse">
| <part name="result" element="tns:MonitorEventsResponse"/>
| </message>
|
| <message name="TestException">
| <part name="exception" element="tns:TestException"/>
| </message>
|
| <portType name="EventMonitoringService">
| <operation name="MonitorEventsRequest">
| <input message="ns2:MonitorEventsRequest"/>
| <output message="ns2:MonitorEventsResponse"/>
| <fault name="FaultName" message="ns2:TestException"/>
| </operation>
| </portType>
|
|
| <binding name="EventMonitoringServiceBinding" type="ns2:EventMonitoringService">
| <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/>
| <operation name="MonitorEventsRequest">
| <soap:operation soapAction=""/>
| <input>
| <soap:body use="literal"/>
| </input>
| <output>
| <soap:body use="literal"/>
| </output>
| <fault name="FaultName">
| <soap:fault name="FaultName" use="literal"/>
| </fault>
| </operation>
|
| </binding>
| <service name="EventMonitoringService">
| <port name="EventMonitoringServicePort" binding="ns2:EventMonitoringServiceBinding">
| <soap:address location="http://localhost/test/EventMonitoringService"/>
| </port>
| </service>
|
| </definitions>
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4052646#4052646
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4052646
19Â years