hi,
now that I stumble upon the same problem, I wonder what the exact reason for
the Can't find serializer exception is when UseJBossWebLoader is set to
false? I'm deploying my application together with axis 1.3 not using JbossWS.
This works fine in WAS 6. The Axis war calls a session bean via
[EMAIL PROTECTED] wrote : I am eager to see this deployment that works in
jboss-4.0.1 and fails in jboss-4.0.2.
|
| Please create a jira issue and attach a sample deployment (with source)
that shows your problem.
Ok... after hours of deploying and undeploying - and testing and what not...
kanno wrote : [EMAIL PROTECTED] wrote : I am eager to see this deployment
that works in jboss-4.0.1 and fails in jboss-4.0.2.
| |
| | Please create a jira issue and attach a sample deployment (with source)
that shows your problem.
|
| Ok... after hours of deploying and undeploying
The release notes of jboss-4.0.2 tell you about a change in default of
| !-- A flag indicating if the JBoss Loader should be used. This loader
| uses a unified class loader as the class loader rather than the
tomcat
| specific class loader.
| The default
[EMAIL PROTECTED] wrote : The release notes of jboss-4.0.2 tell you about a
change in default of
|
|
| | !-- A flag indicating if the JBoss Loader should be used. This
loader
| | uses a unified class loader as the class loader rather than
the tomcat
| |
I am eager to see this deployment that works in jboss-4.0.1 and fails in
jboss-4.0.2.
Please create a jira issue and attach a sample deployment (with source) that
shows your problem.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3881992#3881992
Reply to the
I'm wondering if there's anyway to see into the Typemapping registry at
runtime... I want to see why there's no mapping for the type SeacProfileBean
when I can see the mapping in the wsdd file in the data directory... I looked
at the source... and it appears that in
BeanSerializer.java...
Ryan,
your assumption is right, we only need the request response structures and
array wrappers generated by wscompile. All other artifacts are jwsdp specific.
You WS fails because it cannot find the mapping of the an array type.
The [LSomeType; is how java denotes an array type.
View the
[EMAIL PROTECTED] wrote : Ryan,
|
| your assumption is right, we only need the request response structures and
array wrappers generated by wscompile. All other artifacts are jwsdp specific.
|
| You WS fails because it cannot find the mapping of the an array type.
|
| The
Did you wrap your array in a java bean?
-Jason
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3881684#3881684
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3881684
---
Yep, I followed the exact instructions on the website. I wrapped the array in
a JavaBean... it looks as though it's attempting to serialize the original
array type and that's the serializer that can't be found, even though I can see
the typemapping in the .wsdd file on the server.
View the
kanno,
you probably need to put the class files generated by wscompile from your WSDL
file under the WEB-INF/classes directory of the war that you've deployed your
WS in. (Or under the META-INF/classes if you've used a jar with a SLSB).
Basically the error message mean the service can't find
Scharlau wrote : kanno,
|
| you probably need to put the class files generated by wscompile from your
WSDL file under the WEB-INF/classes directory of the war that you've deployed
your WS in. (Or under the META-INF/classes if you've used a jar with a SLSB).
|
| Basically the error
13 matches
Mail list logo
