Jason sais:
anonymous wrote :
| >> When I generate the interface and server stub code the corresponding web
| >> methods are tagged with an @OneWay annotation. My question regarding the
| >> spec is very simple: what is meant to happen if the implementation of
| >> such a one way method throws a SoapFaultException, a ProtocolException
| >> or some other Exception? Is the JaxWS implementation supposed to throw a
| >> corresponding exception in the client context? The sections of the spec
| >> I cited in my original post do not make the answer clear.
|
No, it can not, it violates the WS-I BP 1.0 which JAX-WS conforms to:
http://www.ws-i.org/Profiles/BasicProfile-1.0-2004-04-16.html#refinement1...
"R2714 - For one-way operations, an INSTANCE MUST NOT return a HTTP
response that contains a SOAP envelope. Specifically, the HTTP response
entity-body must be empty."
That said, you can still present a different WSDL to a consumer than the
semantic one in operation. Just removing @OneWay should do the trick If
a XTS endpoint returns SOAP responses, then it really is a two-way endpoint.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4090538#4090538
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4090538
Thanks Anders, those are good suggestions. I decided to remove the module pom and just have the entire project 2 levels deep. That will avoid a lot of uneeded complexity and confusion. This will also help with the current and future team members maven learning curve, and it follows the MC structure.
I propose we name 2nd level directories like:
| jboss-portal-modules-common/
| jboss-portal/
| jboss-portal-**-**/ (etc...)
|
I went ahead and deployed common to snapshots.jboss.org here. Ignore the jbossportal/, modules/, and common/ directories... I'm waiting on a response to remove those ;)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4090471#4090471
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4090471
fine with me, didn't like the workaround code anyway :). There still is the transaction part. Do such prop changes subscribe to the ongoing transaction policy? E.g.
tx.start();
| aNode.setResident(true);
| tx.rollback();
| //what's the value of aNode.sResident here?
|
Generally speaking we might want to have metadata that does/doesn't subscribe(?); or which we want (want not) to replicate ?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4090459#4090459
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4090459
This feature request is requesting an API which adds a version of token.getAvailableTransitions() which returns an ordered List that preserves the order of the transitions as defined in the processdefinition.xml file for the node, rather than returning an unordered Set object.
node.getLeavingTransitions() appears to preserve the order, but the order is apparently lost when the transistions are added to the Set which is returned by token.getAvailableTransitions().
Preserving the ordering is highly useful when implementing a minimal data-driven interface which presents the user with the transitions to choose from. The designer could exercise some control over the presentation of the choices if only the order were preserved as defined in the processdefinition.xml file.
Although workarounds exist with existing code, it would be very helpful (and consistent I think) to provide an API that retrieves a list of the "available transitions" that is ordered as defined in the processdefinition.xml file instead of (or in addition to) an unordered set.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4090457#4090457
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4090457