Hi list,
I have been porting our current application from XFire to CXF. I think
I'm 80% of the way there now but have run into an issue with the SOAP
output from a Web service.
As shown in the below output the id attribute on the message is in the
namespace ns1. XFire would put this in no namespace. This is a big issue
for me because we do a lot of XSLT work with SOAP results and unless I
can supress adding namespaces to attributes I will need to rewrite a
huge number of XSLTs. Any assistance on how I can do this?
<ns1:message ns1:id="132">
<ns1:createdBy>1</ns1:createdBy>
<ns1:createdOn>2007-11-21T12:56:33.257Z</ns1:createdOn>
<ns1:messageXml>
<messageXml>Do it NOW!</messageXml>
</ns1:messageXml>
</ns1:message>
Also, the only other issue I have is that on my development machine a
service can take up to 30 seconds to initialise. Given that I have over
30 services I've found the startup time for the app server is about 10
minutes. Any way I could bring this down?
rgds,
Richard
Richard Grantham
Development
-------------------------------
[EMAIL PROTECTED]
Limehouse Software Ltd
DDI: (020) 7566 3336
Main: (020) 7566 3320
Fax: (020) 7566 3321
Limehouse Software Ltd
4th Floor
1 London Bridge
London
SE1 9BG
Manchester Office:
3rd Floor, The Triangle, Exchange Square, Manchester M4 3TR
Tel: (0161) 240 2440, Fax: (0161) 240 2441, ISDN: 08700 119 400
Check out Limehouse Software's innovative solutions
www.limehousesoftware.co.uk - Transforming the way you publish and consult on
information
The information contained in this e-mail or in any attachments is confidential
and is intended solely for the named addressee only. Access to this e-mail by
anyone else is unauthorised. If you are not the intended recipient, please
notify Limehouse Software Ltd immediately by returning this e-mail to sender or
calling 020 7566 3320 and do not read, use or disseminate the information.
Opinions expressed in this e-mail are those of the sender and not necessarily
the company. Although an active anti-virus policy is operated, the company
accepts no liability for any damage caused by any virus transmitted by this
e-mail, including any attachments.
