Actually I got it working with the normal URI/prefix combo...
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3932684#3932684
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3932684
---
Should addHeaderElement in SOAPHeader in latest CVS head allow for simple local
named items (i.e. soapEnvelope.createName("name") instead of the 3 parameter
one)? It seems to mandate a URI and prefix, and there are some web services
out there that use simple named header entries (if you give it
Ok, investigating a bit further, I don't think WSDLToJava handles anonymous
complex types properly yet (it assumes the type is named). I believe someone
logged the issue is in JIRA:
http://jira.jboss.com/jira/browse/JBWS-624
View the original post :
http://www.jboss.com/index.html?module=bb&
Well, almost... xerces updated but a nice WSException:
| [wstools] 19:54:53,612 DEBUG [main:WSDLBinding] new WSDLBinding
| [wstools] 19:54:53,612 DEBUG [main:WSDLBinding] setName:
InfoServiceSoapBinding
| [wstools] 19:54:53,613 DEBUG [main:WSDLBinding] setInterfaceName:
InfoServiceS
Ok... updating xerces seemed to fix that!
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3926982#3926982
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3926982
---
Thi
Hmm.. jboss head (from today) gives the following NPE in wsdl2Java... anyone
have any thoughts? Something with xerces it seems...
| [wstools] 19:15:32,105 DEBUG [main:WSDL11Reader] processSchemaInclude:
[targetNS=https://adwords.google.com/api/adwords/v3,parentURL=file:/wsdl/google/InfoSer
I am going to try wstools (as it probably understands itself better :-).
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3926950#3926950
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3926950
I'm new to the JBossWS layer, and have run into the following issue with
anonymous type name mapping (perhaps it is a result of the new JSR). As an
example, try the following wsdl file from Google's APIs (just enough info to
show the issue):
https://adwords.google.com/api/adwords/v3/InfoServic
Thanks, I'll try this
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3925172#3925172
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3925172
---
This SF.net email is sp
Understood. Perhaps if there was a way to single thread access to the bean
automatically as if all calls were synchronized, I suppose this is what I'm
looking for -- perhaps this is more of a locking strategy. I have a web tier
in which parts get composed in mutiple threads, but would like to
Hope this doesn't sound too idiotic, but I'm running into an issue where some
concurrent calls to a EJB 3.0 SFSB cause EJBExceptions on local interfaces, and
am wondering if there is any way to automatically have these calls act single
threaded (instead of wrapping calls externally), or alternat
I believe the jboss serialization is related to your #2 case (you'll see it
stems from the ClassCaseException in ClassReferencePersister). It looks like
someone filed a bug on it:
EJBTHREE-423
Andrew
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3922619#39
I have also experienced this -- seems like jboss serialization cannot handle
the uninitialized lazy attributes (ClassCastException in
ClassReferencePersister.java:42). In my case I can work around it for the time
being by using a local interface on the same machine, but I can see how this is
a
Anyone know how to dynamically specify the datasource of an entity bean during
runtime, specifically so some methods can go to replicated datasources /
non-updating? I'd like to programatically specify which EJB calls are
read-only (to the database).
Andrew
View the original post :
http://ww
14 matches
Mail list logo
