Generally, discussions on a jira issue should be done in jira. Otherwise there
is a disconnect between jira and the forum posts.
Joel, you should not get the exception any more. Try it out
cvs co -r Branch_4_0 jboss-4.0
View the original post :
http://www.jboss.org/index.html?module=bb&op=view
See the roadmap for release targets
http://jira.jboss.com/jira/browse/JBWS?report=com.atlassian.jira.plugin.system.project:roadmap-panel
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3866317#3866317
Reply to the post :
http://www.jboss.org/index.html?module=
when is the scheduled release?
and what package name is it?
i downloaded the newest 4.0.1RC2 and it doesnt seem to have this fix in yet.
i have the same problem and i rolled back to 4.0.0RC2.
however, i cannot use HibernateContext with 4.0.0 versions, so i m in a limbo
here.
please let me k
http://jira.jboss.com/jira/browse/JBWS-64
Thomas has added a workaround to this. It will be available in 4.0.1 SP1 to be
released sometime soon.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3866143#3866143
Reply to the post :
http://www.jboss.org/index.ht
Hello Joel,
I have gone through this long thread and I'm also having the same problem in
JBOSS4.0.1. I have deployed the webservice(JBOSSWS) in jboss4.0.1 and then I
have created stubs using Axis WSDL2Java which is accessed by my stand-alone
client program. I am also having the error:
-
Thomas,
I see via Jira that you have been working on this issue, thanks. I am not sure,
though, whether or not the work arounds that you added are going to resolve the
issue I reported in the first place. I appears to me that by leaving the checks
in Mapping.java that I will still be getting th
Thomas,
I have exactly the same problem. I use JBoss 4.0.1 and Axis 1.2RC2. I was
just wondering if you expect this to be fixed in the nearest future?
Thanks,
Yevgeny.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3865316#3865316
Reply to the post :
htt
Joel, this is only for me as a reference. Changes in the jboss-4.x will have to
be backed by a successful CTS testrun. I have not come to a conclusion yet.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3864624#3864624
Reply to the post :
http://www.jboss.org
Thomas,
I do not understand why your reply simply points back to the Jira issue. Does
that indicate that you agree that JBoss needs to roll back the changes to
Mapping.java and that this is scheduled for 4.0.2?
Thanks,
Joel
View the original post :
http://www.jboss.org/index.html?module=bb&op
http://jira.jboss.com/jira/browse/JBWS-64
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3864554#3864554
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3864554
---
Thi
It appears that this problem is being caused by a modification to Mapping.java
in Axis. This message on the Axis user mailling list from Davanum Srinivas
explains it.
anonymous wrote :
| See JBoss's CVS:
|
http://cvs.sourceforge.net/viewcvs.py/jboss/jaxrpc/src/main/org/apache/axis/utils/Map
I requsted assistance with this on the Axis user mailling list. There opinion
is that this is probably an issue with JBoss. Here is a quote from one of the
messages in that thread that pretty much sums it up. I would really appreciate
it if the two projects could cooperate towards resolving this
12 matches
Mail list logo
