It seems that 1.2.0 doesn't rely on the EntityResolve to resolve schema imports
locally. Instead it tries to fetch them from a remote location. You probably
experience these problems when running
a) without an internet connection
b) or firewall blocking those requests
However, in order to fix
http://jira.jboss.org/jira/browse/JBWS-1563
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4025697#4025697
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4025697
___
jboss-user
Hi,
http://jira.jboss.com/jira/secure/ManageAttachments.jspa?id=12335583
describes the issue, and provides a patch against the jbossws-samples
distributed with the biniary installer version of jbossws-1.2.0.GA
Best Regards,
Bertl
View the original post :
http://jira.jboss.com/jira/secure/ManageAttachments.jspa?id=12335583
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4025996#4025996
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4025996
Due to the complexity of this case, can you create a Jira issue and attach an
example of this? I will take a look at what is going on.
http://jira.jboss.com/jira/secure/CreateIssue!default.jspa
-Jason
View the original post :
It seems to be a known remoting bug: http://jira.jboss.com/jira/browse/JBREM-645
anonymous wrote :
| The workaround requires that a trailing '/' is added after the host:port,
for example:
| socket://succubus.starkinternational.com:4446/?datatype=invocation
|
View the original post :
If we want to nail it down, we need more information about the
request/response, the WSDL, etc.
You'll need to verify what request does exactly cause that error.
Does happen upon parsing the request or when the response is marshalled?
View the original post :
Ok, thanks for the information. We use URLs of this format to communicate with
C processes that use GSOAP. I switched to JBossWS 1.0.4 since it parses the
URLs correctly.
[EMAIL PROTECTED] wrote : It seems to be a known remoting bug:
http://jira.jboss.com/jira/browse/JBREM-645
|
|
You should add parameters (?datatype=SOAPMessage) to the URL string: Caused
by: java.lang.NumberFormatException: For input string:
8791?datatype=SOAPMessage
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4024130#4024130
Reply to the post :
Sorry for the confusion. The Install.txt has been updated to point ot the right
source of information:
http://jbws.dyndns.org/mediawiki/index.php/Install_JBossWS
You need to follow the installation steps as explained in the wiki above.
View the original post :
Did you try the samples that ship with 1.2.0? When exactly does this error
occur?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4024138#4024138
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4024138
I am not sure I understand what you are saying? Are you saying I need to add
datatype=SOAPMessage? I am not adding that currently. I am only doing this:
stub._setProperty(Stub.ENDPOINT_ADDRESS_PROPERTY,http://myhost:8791;);
This is enough to cause the parsing error.
[EMAIL PROTECTED] wrote
I did not try the samples. I upgraded from the version shipping with JBoss
4.0.5.GA. The version included in JBoss 4.0.5.GA worked, but had a problem.
2007-02-27 22:59:30,052 ERROR [org.jboss.ws.jaxrpc.CallImpl] Call invocation
failed with unkown Exception
javax.xml.rpc.JAXRPCException:
Hi,
I installed the jbossws-1.2.0.GA and noticed jboss-xml-binding.jar file is
missing.
Is there any other place to get it?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4024463#4024463
Reply to the post :
I am sorry, we update.
http://repository.jboss.com/jboss/jbossxb/1.0.0.CR9/lib/jboss-xml-binding.jar
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4024483#4024483
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4024483
I believe the andpoint address is invalid because it doesn't have a context
path.
Shouldn't it be something like
http://myhost:8791/some-context
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4024494#4024494
Reply to the post :
Agreed. The installation notes for this release are in serious need of
additional content.
i.e. Is there an intended destination for the files in the /lib/jboss-jdk15/?
jboss-jaxrpc.jar, jboss-jaxws.jar, jboss-saaj.jar
In response to the first post on this thread...
After looking at the
I failed to mention that I deployed the jdk 1.5 version. I am using JBoss
4.0.5.GA. So I deployed the JBoss 40 version of the SAR.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4024005#4024005
Reply to the post :
This showed up sometimes as well... using the exact same request and response.
2007-02-28 22:55:55,877 ERROR [STDERR] [Fatal Error] :1005:26: XML document
structures must start and end within the same entity.
2007-02-28 22:55:55,878 ERROR [org.jboss.ws.core.jaxrpc.SOAPFaultHelperJAXRPC]
SOAP
19 matches
Mail list logo
