Howdy

What i mostly did was implement the work that Robert Dingwell did on the
and posted to the dev list.  I based mine against 3.0.1.  I think i did
some minor tweaks as well to get it to fit into 3.0.1.  

I have not seen any security issues come up yet..  But i also have not
worked over the testsuite to make it work either.

>From what Ive seen this should work for the HEAD for the most part as
well.  and I don't think there is that much change for Axis RC1 as
well.  Should be an easy drop in.   

Right now my needs are for 3.0.1 and im going to stick with Axis beta3
for cause its stable and working (for me at least).  We I get some more
time (after the end of the month) I would be more then happy to help out
with this more.

Thanks for the had work btw..


-=Brian





On Mon, 2002-09-02 at 09:21, Jung , Dr. Christoph wrote:
> Meeeee tooo.
> 
> No, really. Frederick Brier has already done the integration, but stuck with
> some security issues
> before being able to commit it. Any additional hints to what changes from
> beta2 to beta3 may affect
> Jboss.net would be helpful to get this highly requested "feature" into head
> (and then the next 3.x, is 
> this enough?)
> 
> CGJ
> 
> -----Urspr�ngliche Nachricht-----
> Von: Matt Munz [mailto:[EMAIL PROTECTED]] 
> Gesendet: Freitag, 30. August 2002 22:09
> An: [EMAIL PROTECTED]
> Betreff: RE: [JBoss-user] JBoss-3.0.2 released
> 
> 
> Brian,
> 
>   I am interested in the patches.  Could you send them?
> 
>   - Matt
> 
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Brian Towles
> Sent: Friday, August 30, 2002 2:56 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [JBoss-user] JBoss-3.0.2 released
> 
> 
> I have done an Axis Beta3 Integration but have not had time to change all
> the test case stuff in jboss.net yet so i have not submitted it back yet.
> 
> If there is interest in the patches  i will make them available.  It has
> been working for me just fine.
> 
> -=Brian
> 
> 
> On Fri, 2002-08-30 at 12:54, David Ward wrote:
> > I also am looking forward to Axis beta 3 integration:
> >
> > http://www.jboss.org/forums/thread.jsp?forum=137&thread=17461
> >
> > --
> >
> > Emily Short wrote:
> > > When will Axis beta 3 be integrated?  I built jboss 4.0.0alpha and 
> > > beta3 is not yet integrated.  I heard this would be done by the end 
> > > of the summer?
> > >
> > > Thanks,
> > > Emily
> > >
> >
> >
> >
> > -------------------------------------------------------
> > This sf.net email is sponsored by: OSDN - Tired of that same old cell 
> > phone?  Get a new here for FREE! 
> > https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
> > _______________________________________________
> > JBoss-user mailing list
> > [EMAIL PROTECTED] 
> > https://lists.sourceforge.net/lists/listinfo/jboss-user
> 
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by: OSDN - Tired of that same old cell phone?
> Get a new here for FREE!
> https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-user
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by: OSDN - Tired of that same old cell phone?
> Get a new here for FREE!
> https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-user
> ###########################################
> 
> This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange.
> For more information, connect to http://www.F-Secure.com/
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by: OSDN - Tired of that same old
> cell phone?  Get a new here for FREE!
> https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-user

--- Begin Message ---
Hi,

I noticed that the latest version of Axis (beta 3) had not been
integrated into the .net packages as of yet. I took it upon myself to
perform the integration and would like to share with you all what needed
to be changed. Below you will find a log of what I did along the way to
perform the modification.  This was all done using the 3.1 alpha code in
cvs and hence will not work in the 3.0 production server without further
modification.

It builds and deploys without error but I have not had a chance to do
any real testing with though.

I noticed something else while I was routing around in the EJBProvider.
At present it does not support EJBLocalHome only EJBHome so a
ClassCastException is thrown if the the ejb being accessed through it's
local interfaces.


Rob


Thirdparty jars that need to be updated
axis.jar
wsdl.jar:   need the latest one it has been changed to use the same
QName class throughout that axis uses

Additional jars needed    I changed my build.xml file to includes these
in the build paths

saaj.jar:   part of the apache axis distro. this has the latest version
of the javax.xml.soap I left this in the axis thirdparty lib for now
probably should go under sun/?

javaxRPC.jar: contains the javax.xml.rpc packages I put this under the
thirdparty/sun/javaxrpc directory on my machine but it can go where ever



Changed all package import statements of javax.xml.rpc.namespace.Qname
and java.wsdl.Qname to  javax.xml.namespace.Qname

Removed  import org.apache.axis.deployment.DeploymentException; changed
deployToRegistry method to throw ConfigurationException in
Deployment.java


Removed protected TypeMapping(Element e, boolean b) throws
WSDDException  constructor from TypeMapping.java
this constructor is no longer in the axis WSDDTypeMapping parent class

Changed EJBProvider to use local definitions of empty_class_array and
empty_object_array
empty_class_array and empty_object_array are now private members of the
org.apache.axis.provider.java.EJBProvider class
in the current release beta 3. The latest code in axis cvs changes these
to protected but I am mainly concerned with the
release version at this point in time so I am coding to that.

Changed
String fieldName = typeDesc.getFieldNameForElement(elemQName); to String
fieldName = typeDesc.getFieldNameForElement(elemQName,false);in the
onStartChild method of EntityBeanDeserializer.java the boolean tells the
method whether or not to ignore namespaces


Removed the boolean reusable flag from the constructors in
ParameterizableDeserializerFactory and change the super
calls to reflect this change. the reusable flag is no longer in the axis
api.
Modified EntityBeanDeserializerFactory with these changes as well


Modified writeSchema method in ObjectNameSerializer to use the QName it
was constructed with and removed the QName qName =
types.getWsdlQName(xmlType); line from the method. The wsdl packages
have been updated to use the same javax.xml.namspace.Qname as the rest
of the axis api so this call is no longer needed to convert to the wsdl
QName impl.
Same goes for AttributeSerializer.

changed method call in writeSchema of AttributeSerializer
Element valueElement =
   types.createElement(
    "value",
    XMLType.XSD_ANYTYPE.toString(),
    true,
    all.getOwnerDocument());
to
Element valueElement =
   types.createElement(
    "value",
    XMLType.XSD_ANYTYPE.toString(),
    true,
    true,
    all.getOwnerDocument());

The additional boolean is a flag that states whether or not the item is
omittable or not. I set this to true for now.
What happens is that a minocurrs="0" and a maxocurrs ="1" is set in the
schema for the attribute



axis Constants changes in MBeanProvider
 org.apache.axis.Constants.URI_SOAP_ENC no longer exists using
 org.apache.axis.Constants.URI_DEFAULT_SOAP_ENC

 org.apache.axis.Constants.URI_CURRENT_SOAP_ENC no longer exists using
 org.apache.axis.Constants.URI_DEFAULT_SOAP_ENC


emitter.setMode(service.getStyle()) changed to
emitter.setMode(service.getStyle().getValue() )

the getStyle method of org.apache.axis.handlers.soap.SOAPService now
returns a Style object not an int
the getValue method of the style object returns the int needed









begin:vcard 
n:Dingwell;Robert
tel;work:781-271-2829
x-mozilla-html:FALSE
org:Mitre Corp.
adr:;;;;;;
version:2.1
email;internet:[EMAIL PROTECTED]
fn:Robert Dingwell
end:vcard
--- End Message ---

Reply via email to