[JBossWS] - Re: Enabling MTOM-Support at JBossWS client fails
by lfoggy
Well, I am using document/literal wrapped for my wsdl file, and what I have found so far is that mtom only works if the parameter type of the method is DataHandler. For example, this works:
@WebMethod
@RequestWrapper(localName = "sendOctet", targetNamespace = "http://xxx.com/webservice/mtom/", className = "com.xxx.webservice.mtom.SendOctet")
@ResponseWrapper(localName = "sendOctetResponse", targetNamespace = "http://xxx.com/stat/webservice/mtom/", className = "com.xxx.webservice.mtom.SendOctetResponse")
public void sendOctet(
@WebParam(name = "octet", targetNamespace = "")
DataHandler octet,
But if I pass something like List, or another holder bean that contains a DataHandler field, mtom does not work anymore, and the message is send inline.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4170124#4170124
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4170124
17 years, 11 months
[JBoss Portal] - WSRP and initCookie (JBoss Portal 2.6.5.SP1)
by andreas.chlupacek
Hiyas,
we're currently evaluating Portal 2.6.5.SP1 in a WSRP scenario. Currently we are running two instances, one as consumer, one as producer. The producer offers two remote portlets from two distinct web apps. As we are trying to gain some insight into the nature of the cookies being passed around, we stumbled across the fact that the consumer does not seem to call the initCookie operation before invoking getMarkup.
JBoss Portal's WSRP producer demands perUser initalization, which we can see coming across the wire nicely in its getServiceDescriptionResponse envelope. So theoretically, the consumer should invoke initCookie on the producer's markup service before trying to invoke getMarkup, right?
>From what I've gathered from a glimpse at the sources (and debugging around a bit), requiresInitCookie() in org.jboss.portal.wsrp.consumer.SessionHandler will never return true since the SessionHandler's member requiresInitCookie seems always to hold null.
...or am I just missing something obvious? If so, please give me a hint ;-)
Kind Regards,
Andreas
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4170122#4170122
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4170122
17 years, 11 months
[Installation, Configuration & DEPLOYMENT] - Re: how to configure JBOSS to connect to two databases schem
by badam571
Hi PeterJ
thank you for the reassuring and prompt response.
the other config files
standardjbosscmp-jdbc.xml
standardjaws.xml
jboss-login.xml
I am interested in knowing about: standardjbosscmp-jdbc.xml
should I add another defaults tag for the new datasource in standardjbosscmp-jdbc.xml or how I will accommodate the new datasource in this file. This config file continuouly generate an errror like this:
--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss.jdbc:service=metadata
State: FAILED
Reason: org.jboss.deployment.DeploymentException: Invalid XML: file=file:/C:/j
boss-4.0.4.GA/server/default/conf/standardjbosscmp-jdbc.xml; - nested throwable:
(org.xml.sax.SAXParseException: The content of element type "jbosscmp-jdbc" mus
t match "(defaults?,enterprise-beans?,relationships?,dependent-value-classes?,ty
pe-mappings?,entity-commands?,user-type-mappings?,reserved-words?)".)
Depends On Me:
jboss.jdbc:service=metadata,datasource=DefaultDS
jboss.jdbc:service=metadata,datasource=SybaseDS
jboss.jdbc:service=metadata,datasource=SybaseDB
at org.jboss.deployment.MainDeployer.checkIncompleteDeployments(MainDepl
oyer.java:1367)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:774)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:755)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIntercept
or.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelM
BeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy5.deploy(Unknown Source)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
at org.jboss.Main.boot(Main.java:200)
at org.jboss.Main$1.run(Main.java:464)
at java.lang.Thread.run(Thread.java:595)
11:53:09,363 INFO [Http11BaseProtocol] Starting Coyote HTTP/1.1 on http-0.0.0.0
-8080
Best Regards
badam571
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4170115#4170115
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4170115
17 years, 11 months
[JBoss jBPM] - Re: workaround for StackOverflow exception
by vanyatka
anonymous wrote : You could try to use an in-memory configured version of HSQLDB. That does not realy persist to file, but it does doe db stuff.
Good idea. But I'm not there yet, I still cannot make it going without exception.
anonymous wrote : Regarding the issue, it manifests itself in Seam, but is jBPM related and fixed in the upcomming 3.2.4 afaik.
You know, I nearly gave up using Seam because of this issue, trying to re-implement the process in "pure" jBPM. But if it is a jBPM's issue, are you saying that Timers cannot be used with States? Sounds like an ultra-critical issue to me.
anonymous wrote : btw, you could configure jBPM to *not* use transactions or use it's own transactions instead of using the seam provided one.
I would do anything, but I'm lost at what are the alternatives.
I need to persist a state into DB. The only proper way to do that (is it so?) is to use State + Timer like I did. But you're saying it's not available till 3.2.4.
If you could suggest how to persist the state in a decision loop (with or without States) in order to get rid of StackOverflow I would be grateful.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4170104#4170104
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4170104
17 years, 11 months