[JBoss Seam] - Re: Planning to remove @Begin(id=..)? Help Needed!
by gavin.kingï¼ jboss.com
I don't know why you just spent so many words on explaining me the current behavior. I know what the current behavior is. I know how it behaved in the test case you submitted. I'm happy with it.
There is a massive difference between what happens when you call @Begin(id="...") when there is no long-running conversation in progress, and what happens when there is already one in progress. The stuff written in the documentation refers to the case where there is no conversation in progress.
Nevertheless, both cases are at least somewhat broken because they result in changing the conversation context in the middle of a request.
You should use the new functionality for defining "natural" conversation ids, since it is not vulnerable to this problem.
Yes, I understand that this is not yet documented, but its pretty easy to figure out.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4032260#4032260
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4032260
19Â years
[JBoss Seam] - Re: How to link to page using level of indirection
by henrik.lindberg
Thanks awheeler - I tried the first but did not succeed.
And thanks for the page navigation-rule example. I got confused thinking that I needed to have from-action include parameter - but your example makes it clear, I just have to keep x from the call to virewForUpdate in the ViewSelector instance so I can pick it up again as a parameter. Understand how to make that work.
What I don't like about this solution is that it ads yet another place to configure the mapping.
What I ended up doing was this:
| <h:outputLink value="#{x.type}-view.seam" >
| <f:param name="oid" value="#{x.id}" />
| #{x.name}
| </h:outputLink>
|
Which naturally is far less elegant as it ties the view to the type (which I already had).
Will explore the page navigation rule approach sometimes later.
I would have loved to have this possibility directly available in s:link (i.e. ability to call method with parameter to set the value).
Regards
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4032253#4032253
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4032253
19Â years
[JBoss Seam] - Re: How to link to page using level of indirection
by henrik.lindberg
I really need help - I am stuck on this.
Basically I want to do:
| <a href="#{viewSelector.viewForObject(x)}?oid=#{x.oid}">some text</a>
|
But I have failed to figure out how to create such an URL.
If I use s:link I can call the method viewForObject and pass a paramter and get the view back, but then the parameter is lost (it is applied to the invocation of the action).
I then thought about using multiplen h:outputLink with static declaration of the various viewids and using
| rendered="#{viewSelector.viewForObject(x) == 'view-x'}"
|
but that is not valid (or? can this be made to work?)
I then looked at doing this with a page navigation rule instead, but my head starts to spin - how do this with page rules?
Should I have a fictious page-id that I navigate to with
redirects depending on the outcome of my method? Or add a page that never gets rendered, only redirected from? But how do I get the value of x.id in there?
Any help much appreciated...
Regards
"confused newbie"
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4032244#4032244
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4032244
19Â years
[JBossWS] - Re: BUG: MTOM with JBossWS 1.2.0SP1 server and Axis2 client
by biroj
Using SoapUI as client I collected the following trace at JBossWS side:
| 2007-03-28 00:17:59,296 DEBUG [org.jboss.ws.core.server.ServiceEndpoint] BEGIN handleRequest: jboss.ws:context=ETI-ETI_Framework,endpoint=ETI_ReceiverBean
| 2007-03-28 00:17:59,296 DEBUG [org.jboss.ws.core.soap.MessageFactoryImpl] createMessage: [contentType=multipart/related; type="application/xop+xml";
| start="<rootpart(a)soapui.org>"; startinfo="text/xml; action=\"\"";
| boundary="----=_Part_16_1798874.1175033879281"]
| 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.soap.attachment.SwapableMemoryDataSource] Using memory buffer, size = 707
| 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.soap.attachment.SwapableMemoryDataSource] Using memory buffer, size = 81
| 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerDelegateJAXWS] callRequestHandlerChain: PRE
| 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerResolverImpl] initHandlerChain: PRE
| 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerResolverImpl] Clear handler map: {}
| 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerResolverImpl] initHandlerChain: ENDPOINT
| 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerResolverImpl] Clear handler map: {}
| 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerResolverImpl] initHandlerChain: POST
| 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerResolverImpl] Clear handler map: {}
| 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerResolverImpl] getHandlerChain: [type=PRE,info=[service={http://siemens.com/ws}ETI_ReceiverBeanService,por...]
| 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerChainExecutor] Create a handler executor: []
| 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.soap.SOAPMessageDispatcher] getDispatchDestination: {http://siemens.com/ws}downloadRelationships
| 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS] unbindRequestMessage: {http://siemens.com/ws}downloadRelationships
| 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.EndpointInvocation] setRequestParamValue: [name={http://siemens.com/ws/types}downloadRelationships,value=org.jboss.w...]
| 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerDelegateJAXWS] callRequestHandlerChain: ENDPOINT
| 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerResolverImpl] initHandlerChain: PRE
| 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerResolverImpl] Clear handler map: {}
| 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerResolverImpl] initHandlerChain: ENDPOINT
| 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerResolverImpl] Clear handler map: {}
| 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerResolverImpl] initHandlerChain: POST
| 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerResolverImpl] Clear handler map: {}
| 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerResolverImpl] getHandlerChain: [type=ENDPOINT,info=[service={http://siemens.com/ws}ETI_ReceiverBeanServic...]
| 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerChainExecutor] Create a handler executor: []
| 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerDelegateJAXWS] callRequestHandlerChain: POST
| 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerResolverImpl] initHandlerChain: PRE
| 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerResolverImpl] Clear handler map: {}
| 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerResolverImpl] initHandlerChain: ENDPOINT
| 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerResolverImpl] Clear handler map: {}
| 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerResolverImpl] initHandlerChain: POST
| 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerResolverImpl] Clear handler map: {}
| 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerResolverImpl] getHandlerChain: [type=POST,info=[service={http://siemens.com/ws}ETI_ReceiverBeanService,po...]
| 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerChainExecutor] Create a handler executor: []
| 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.integration.jboss42.ServiceEndpointInvokerEJB3] invokeServiceEndpoint: downloadRelationships
| 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.EndpointInvocation] getRequestPayload
| 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.EndpointInvocation] getRequestParamValue: {http://siemens.com/ws/types}downloadRelationships
| 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.soap.SOAPContentElement] -----------------------------------
| 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.soap.SOAPContentElement] Transitioning from XML_VALID to OBJECT_VALID
| 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.soap.XMLContent] getObjectValue [xmlType={http://siemens.com/ws}downloadRelationships,javaType=class com.siemens.icm.nm.rc.eti.framework.common.generated.wsdl.DownloadRelationshipsType]
| 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.jaxws.JAXBDeserializer] deserialize: [xmlName={http://siemens.com/ws/types}downloadRelationships,xmlType={http:...]
| 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.jaxws.JAXBDeserializer] deserialized: com.siemens.icm.nm.rc.eti.framework.common.generated.wsdl.DownloadRelationshipsType
| 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.soap.XMLContent] objectValue: com.siemens.icm.nm.rc.eti.framework.common.generated.wsdl.DownloadRelationshipsType
| 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.soap.SOAPContentElement] -----------------------------------
| 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.EndpointInvocation] transformPayloadValue: org.jboss.ws.core.soap.SOAPBodyElementDoc -> com.siemens.icm.nm.rc.eti.framework.common.generated.wsdl.DownloadRelationshipsType
| 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.jaxrpc.ParameterWrapping] unwrapRequestParameters: com.siemens.icm.nm.rc.eti.framework.common.generated.wsdl.DownloadRelationshipsType
| 2007-03-28 00:17:59,312 INFO [STDOUT] 0
| 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.EndpointInvocation] setReturnValue: null
|
Additonal information:
- I tried to send a file with size 81 bytes.
- The [STDOUT] 0 means the filesize of the received attachment (0).
- It can be seen that I set the binding type properly
getHandlerChain: [type=POST,info=[service={http://siemens.com/ws}ETI_ReceiverBeanService,po...]
Do you have any idea what is the problem?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4032241#4032241
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4032241
19Â years