Hi Davanum

I have been reading email of AXIS development for years and know you are
exporter on AXIS. Right now, I am working on a project to upgrade AXIS
1.2 RC1 to AXIS 1.4 and have some questions which bother me for months.
Could you kindly give me some help. I know you are very busy and I try
my best make myself clear. Thank you in advance.  (If you need fee,
please let me know the rate)

Let me simply focus on the problem instead of discuss the reason to
select AXIS 1.4 instead of AXIS2.

Upgrade AXIS 1.4 problem:
Before AXIS 1.2 RC3, AXIS 1.2 implements JAX-RPC1.0 standard.
In AXIS 1.2 RC3, AXIS 1.2 start to support JAX-RPC 1.1 standard and
mapping system was changed. 

JAX-RPC 1.1 (4.2.5 SimpleTypes Derived By Restriction) specification
says "A simpleType with derived by restriction from another simple type,
referred to as its base type is mapped to the same java type that its
base type is mapped to."  
So for same schema, AXIS 1.4 WSDL2Java implementing JAX-RPC 1.1 will NOT
map it to any java class as AXIS 1.2 RC1 does.

Example:
<xs:simpleType name="SimpleTypeString_Type">
  <xs:restriction base="xs:string"
     <xs:minLength value="1"/>
     <xs:maxLength value="5"/>
  <xs:pattern value="\d{6}"/>
 </xs:restriction>
</xs:simpleType>

AXIS 1.2 RC1 (We are using) 
<simpleString
xsi:type="ns1:SimpleTypeString_Type"xmlns="">SimpleTypeString_Type</simp
leString>
Note:The schema type SimpleTypeString_Type maps to SimpleTypeString_Type
class.

AXIS 1.4 
<simpleString xsi:type="xsd:string"
xmlns="">SimpleTypeString_Type/simpleString>
Note: The schema type SimpleTypeString_Type maps to String.

My Problem
The group I am working with is middle tier and provides web service to
all clients within Wells Fargo. We currently run AXIS 1.2 rc1 in
WebLogic Server 8.1 on Solaris and deal with millions transactions a
day.  It is a 24x7 application. 
Unfortunately, the application uses the classes generated from compiling
schema all the place. If I have the application use the code generated
from AXIS 1.4 wsdl2java, I saw more than 5 thousands compile errors. In
fact, there are other code differences between generated from AXIS1.2
RC1 wsdl2java and from AXIS 1.4 wsdl2java. We can not bear the risk to
change so many errors.

Question1:
Is there a way to configure AXIS1.4 wsdl2java to create same code as
AXIS 1.2 RC1 does? 

Question 2:
If the answer to #1 is "no".  I hope to use AXIS 1.4 runtime framework
and AXIS 1.RC1 mapping system (still use AXIS 1.2 RC1 wsdl2java to
compile schema and deploy these generated classes and wsdd files) .
deploy the classes and wsdd files generated from AXIS 1.2 RC1.
 
I did a very limited and simple testing and it worked.  Is it feasible
from technical perspective?  Any risk?

Question3:
Currently, our clients are using AXIS RC1, which is same as we (server)
do. 
Assume we use AXIS 1.4 runtime framework and AXIS 1.2 RC1 mapping
system. Is it possible to have the server deal with the xml message from
client using AXIS 1.4 mapping system.

Example. 
The client using AXIS 1.2 RC1 C mapping system sends following xml
message to server 
<simpleString
xsi:type="ns1:SimpleTypeString_Type"xmlns="">SimpleTypeString_Type</simp
leString>

Since server is using AXIS 1.2 RC1 mapping system and no problem to
deseries xml message to java SimpleTypeString_Type  object. 

The Client using AXIS 1.4 mapping system sends following xml message to
the server. 
<simpleString xsi:type="xsd:string" xmlns="">SimpleType</simpleString>

Can the server using AXIS 1.2 RC1 mapping system mapping to
SimpleTypeString_Type instead of "String"?
How does AXIS engine deal with "xsi:type" while deserializing  xml
message?   

Question4:
This is vice versa to Question3.
If server uses AXIS 1.4 runtime framework and AXIS 1.4 mapping system,
can it deal with the xml message sent from client using AXI 1.2 RC1?

For following xml message, there is no SimpleTypeString_Type class on
server side because it maps to String.  Can AXIS 1.4 smart enough to map
it to String. 

<simpleString
xsi:type="ns1:SimpleTypeString_Type"xmlns="">SimpleTypeString_Type</simp
leString>

Note: The schema type SimpleTypeString_Type maps to
SimpleTypeString_Type class in AXIS 1.2 RC1 mapping system.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to