Re: [jboss-user] [JBoss Web Services CXF] - Continuing problem with XTS WS-T tests in AS trunk/CXF 2.2.9
by Jim Ma
Jim Ma [http://community.jboss.org/people/jim.ma] replied to the discussion
"Continuing problem with XTS WS-T tests in AS trunk/CXF 2.2.9"
To view the discussion, visit: http://community.jboss.org/message/549617#549617
--------------------------------------------------------------
> Yes, I assumed there woud lbe further problems. This may require a few chnages from me -- for example I may need to provide a real implemntation of SoapFaultService rather than just adding a doapFault(Fault) WebMethod to the WS-T service endpoint beans. If you can get past the problems with interceptors not expecting soap faults let me know what else breaks.
OK. I will continue to look at this issue in CXF and give you update.
> I am not sure how big an issue this is for CXF. It ought to be perfectly legitimate to define (as I have done) a JaxWS service whose web methods accept a single soap fault as argument. In practice I am not clear what the implications are of requiring this to be supported. It is quite possible for the implementation to isolate the case where a fault is being delivered as an incoming payload from the case where it is being returned from a failed (OneWay or RPC) request. However, this implies that the handler stack has to discriminate these cases by evaluating somthing like isRequest() && isFault() rather than just isFault().
Agreed. I need to change the current code to route the asynchronous fault to the server pipeline to process the normal soap request. I'll figure out and shoot the blocks for this request in CXF.
> n.b. this problem can also arise with synchronous fault delivery on any JaxWS request when using WSA. This is because when using WSA it is possible to configure a FaultTo endpoint which is not the same as the From endpoint. So, if, for example, delivery of a OneWay message failed because of a problem with a mustUnderstand header the fault should be routed to the FaultTo endpoint rather than returned to the sender on the HTTP connection used to make the request. So, the fault will still be an incoming message for the FaultTo endpoint; it wiill not be paired with an outgoing message.
This could be a common user case for Fault message will be delievered to another Endpoint not the sender . I remembered a similar case in CXF couple of months ago, the ReplyTo is not the sender and another endpoint with http url address. CXF can not send this response message to the ReplyTo endpoint correctly. And only with jms transport , it works well . Anyway , I will look at this problem and fix it in CXF.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/549617#549617]
Start a new discussion in JBoss Web Services CXF at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years, 10 months
[jBPM Development] - JBPM-1209 about el refactor(2rd)
by HuiSheng Xu
HuiSheng Xu [http://community.jboss.org/people/rebody] created the discussion
"JBPM-1209 about el refactor(2rd)"
To view the discussion, visit: http://community.jboss.org/message/549605#549605
--------------------------------------------------------------
Hi guys,
I upload a patch to finish the el refactor jobs which Tom left. The details is followed:
org.jbpm.bpmn.flownodes.ScriptTaskActivity.java [no modification]
org.jbpm.jpdl.internal.activity.JmsActivity.java [delete unused import]
org.jbpm.jpdl.internal.activity.ScriptActivity.java [no modification]
org.jbpm.jpdl.internal.activity.ScriptBinding.java [no modification]
org.jbpm.jpdl.internal.activity.SubProcessActivity.java [delete unused import - already fixed by alejandro]
org.jbpm.jpdl.internal.activity.TaskActivity.java [delete unused import - already fixed by alejandro]
org.jbpm.pvm.internal.cal.Duration.java [change scriptmanager to el]
org.jbpm.pvm.internal.el.ScriptExpression.java [no modification]
org.jbpm.pvm.internal.email.impl.MailProducerImpl.java [change scriptmanager to el]
org.jbpm.pvm.internal.model.ExecutionImpl.java [change scriptmanager to el]
org.jbpm.pvm.internal.model.ExpressionCondition.java [change scriptmanager to el]
org.jbpm.pvm.internal.model.VariableOutDefinitionSet.java [change scriptmanager to el]
org.jbpm.pvm.internal.script.ScriptManager.java [no modification]
org.jbpm.pvm.internal.wire.binding.ScriptManagerBinding.java [no modification]
org.jbpm.pvm.internal.wire.descriptor.ExpressionDescriptor.java [change scriptmanager to el]
After add some method into Expression, I could replace all of ScriptManager by Expression, except for Script****Activity part, these activities should use ScriptManager to evaluate script content.
Please refer this https://jira.jboss.org/browse/JBPM-1209 https://jira.jboss.org/browse/JBPM-1209. Any reply will be apprieciated. Thank you very much.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/549605#549605]
Start a new discussion in jBPM Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years, 10 months
[Beginner's Corner] - how to closed jboss port 8009
by love red
love red [http://community.jboss.org/people/tuelip] created the discussion
"how to closed jboss port 8009"
To view the discussion, visit: http://community.jboss.org/message/549604#549604
--------------------------------------------------------------
hello,
I'm running jboss 4.0.5ga and now i am trying to figure out jboss security and also about the ports.
As far as i knew, jboss port could be figure out through jboss-service.xml and serxer.xml.
I've tried to remove rmi configuration in the jboss-service.xml and i've got blank page when running the http://localhost:8080 http://localhost:8080
<!-- ==================================================================== -->
<!-- JNDI -->
<!-- ==================================================================== -->
<mbean code="org.jboss.naming.NamingService"
name="jboss:service=Naming"
xmbean-dd="resource:xmdesc/NamingService-xmbean.xml">
<!-- The call by value mode. true if all lookups are unmarshalled using
the caller's TCL, false if in VM lookups return the value by reference.
-->
<attribute name="CallByValue">false</attribute>
<!-- The listening port for the bootstrap JNP service. Set this to -1
to run the NamingService without the JNP invoker listening port.
-->
<attribute name="Port">1099</attribute>
<!-- The bootstrap JNP server bind address. This also sets the default
RMI service bind address. Empty == all addresses
-->
<attribute name="BindAddress">${jboss.bind.address}</attribute>
<!-- The port of the RMI naming service, 0 == anonymous -->
<attribute name="RmiPort">1098</attribute>
<!-- The RMI service bind address. Empty == all addresses
-->
<attribute name="RmiBindAddress">${jboss.bind.address}</attribute>
<!-- The thread pool service used to control the bootstrap lookups -->
<depends optional-attribute-name="LookupPool"
proxy-type="attribute">jboss.system:service=ThreadPool</depends>
</mbean>
<mbean code="org.jboss.naming.JNDIView"
name="jboss:service=JNDIView"
xmbean-dd="resource:xmdesc/JNDIView-xmbean.xml">
<!-- The HANamingService service name -->
<attribute name="HANamingService">jboss:service=HAJNDI</attribute>
</mbean>
Now, i want to closed the other jboss port and wants to find out how it gonna affect the related port and the server page.
for instance, how to closed port 8009?
any guidance or link would be appreciate :)
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/549604#549604]
Start a new discussion in Beginner's Corner at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years, 10 months