[jira] Created: (AXISCPP-887) WSDL2Ws ignores xsd:any inside xsd:choice
WSDL2Ws ignores xsd:any inside xsd:choice - Key: AXISCPP-887 URL: http://issues.apache.org/jira/browse/AXISCPP-887 Project: Axis-C++ Type: Bug Components: WSDL processing - Doc Reporter: Manohar WSDL2Ws ignores xsd:any inside xsd:choice and won't generate source. Here is the complextype definition, xsd:complexType name=SimpleComplexType1 xsd:choice xsd:any namespace = ##any / xsd:element name=field3 type=xsd:string nillable=false/ xsd:element name=field4 type=xsd:string nillable=false/ /xsd:choice /xsd:complexType When WSDL2Ws generates code for wsdl having above complex type definition, there are no entries for xsd:any element in SimpleComplexType1.hpp file. I am attaching the wsdl here and I will add a test for this. Regards Manohar -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AXISCPP-887) WSDL2Ws ignores xsd:any inside xsd:choice
[ http://issues.apache.org/jira/browse/AXISCPP-887?page=all ] Manohar updated AXISCPP-887: Attachment: ComplexTypeChoiceNestedAny.wsdl WSDL2Ws ignores xsd:any inside xsd:choice - Key: AXISCPP-887 URL: http://issues.apache.org/jira/browse/AXISCPP-887 Project: Axis-C++ Type: Bug Components: WSDL processing - Doc Reporter: Manohar Attachments: ComplexTypeChoiceNestedAny.wsdl WSDL2Ws ignores xsd:any inside xsd:choice and won't generate source. Here is the complextype definition, xsd:complexType name=SimpleComplexType1 xsd:choice xsd:any namespace = ##any / xsd:element name=field3 type=xsd:string nillable=false/ xsd:element name=field4 type=xsd:string nillable=false/ /xsd:choice /xsd:complexType When WSDL2Ws generates code for wsdl having above complex type definition, there are no entries for xsd:any element in SimpleComplexType1.hpp file. I am attaching the wsdl here and I will add a test for this. Regards Manohar -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Calclient exception on WIndows
HI All, I build Axis C++ calclient on Windows. I followed build and setup instructions as per Axis C++ Windows Developers Guide. In xsd__int Calculator::add(xsd__int Value0, xsd__int Value1)function when it calls if (AXIS_SUCCESS != m_pCall-initialize(CPP_RPC_PROVIDER)) it is giving exception AXISC_NODE_VALUE_MISMATCH_EXCEPTION. Apache server is running and I can get page of http://localhost/axis Please let me know what me the problem at the earliest. With Regards Deepak _ A Camera Sells every 2 Minutes on eBay. Get Your's at a Great Price Now! http://adfarm.mediaplex.com/ad/ck/4686-26272-10936-699?ck=Cameras
[jira] Created: (AXISCPP-888) Deserializer does give any indication of error when tags not in the WSDL are encountered.
Deserializer does give any indication of error when tags not in the WSDL are encountered. - Key: AXISCPP-888 URL: http://issues.apache.org/jira/browse/AXISCPP-888 Project: Axis-C++ Type: Bug Components: Client - Deserialization Versions: 1.5 Beta Environment: Linux Reporter: Chip Stettler The WSDL contract was modified on the server to add an additional field. The client side marshalled all data upto the unexpected field. All data after the unexpected field was null, however, the call returned without error. I tried the same test in java Axis and java version throws an exception. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (AXISCPP-888) Deserializer does give any indication of error when tags not in the WSDL are encountered.
[ http://issues.apache.org/jira/browse/AXISCPP-888?page=comments#action_12360423 ] Chip Stettler commented on AXISCPP-888: --- This is an issue with 1.5 Final also. Deserializer does give any indication of error when tags not in the WSDL are encountered. - Key: AXISCPP-888 URL: http://issues.apache.org/jira/browse/AXISCPP-888 Project: Axis-C++ Type: Bug Components: Client - Deserialization Versions: 1.5 Beta Environment: Linux Reporter: Chip Stettler The WSDL contract was modified on the server to add an additional field. The client side marshalled all data upto the unexpected field. All data after the unexpected field was null, however, the call returned without error. I tried the same test in java Axis and java version throws an exception. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (AXISCPP-890) Deserializer does give any indication of error when tags not in the WSDL are encountered.
Deserializer does give any indication of error when tags not in the WSDL are encountered. - Key: AXISCPP-890 URL: http://issues.apache.org/jira/browse/AXISCPP-890 Project: Axis-C++ Type: Bug Versions: 1.5 Final Environment: Linux Reporter: Chip Stettler The WSDL contract was modified on the server to add an additional field. The client side marshalled all data upto the unexpected field. All data after the unexpected field was null, however, the call returned without error. I tried the same test in java Axis and java version throws an exception. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (AXISCPP-891) Deserializer output being returned as null
Deserializer output being returned as null -- Key: AXISCPP-891 URL: http://issues.apache.org/jira/browse/AXISCPP-891 Project: Axis-C++ Type: Bug Components: Client - Deserialization Versions: 1.5 Final Environment: Linux Reporter: Chip Stettler The schema has element define Messages as a complex type of ArrayOfString s:element minOccurs=0 maxOccurs=1 name=Messages type=tns:ArrayOfString / ArrayOfString looks like s:complexType name=ArrayOfString s:sequence s:element minOccurs=0 maxOccurs=unbounded name=string nillable=true type=s:string / /s:sequence /s:complexType The SOAP document contains Messages/Messages When Messages is empty the entire Output struct is null with no exception being generated. If I put Messagesstringastring/Messages data returns fine. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (AXISCPP-889) Deserializer does give any indication of error when tags not in the WSDL are encountered.
Deserializer does give any indication of error when tags not in the WSDL are encountered. - Key: AXISCPP-889 URL: http://issues.apache.org/jira/browse/AXISCPP-889 Project: Axis-C++ Type: Bug Versions: 1.5 Final Environment: Linux Reporter: Chip Stettler The WSDL contract was modified on the server to add an additional field. The client side marshalled all data upto the unexpected field. All data after the unexpected field was null, however, the call returned without error. I tried the same test in java Axis and java version throws an exception. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (AXISCPP-892) Please change occured to occurred globally
Please change occured to occurred globally -- Key: AXISCPP-892 URL: http://issues.apache.org/jira/browse/AXISCPP-892 Project: Axis-C++ Type: Bug Versions: current (nightly) Reporter: Henrik Nordberg Priority: Trivial Occurred is spelled with only one r in several places in the code. Some of these may show up in error messages, so I think this should be fixed soon. It is trivial to do a global search and replace to fix this. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (AXISCPP-720) Returning Array of complex type is broken
[
http://issues.apache.org/jira/browse/AXISCPP-720?page=comments#action_12360449
]
Henrik Nordberg commented on AXISCPP-720:
-
I see that the dtors are no longer virtual. What is the reason for this?
I am in the process of testing this now.
Returning Array of complex type is broken
-
Key: AXISCPP-720
URL: http://issues.apache.org/jira/browse/AXISCPP-720
Project: Axis-C++
Type: Bug
Components: Serialization, WSDL processing - Doc
Versions: current (nightly)
Environment: Windows Linux
Reporter: Henrik Nordberg
Attachments: konga_database_infoprovider.1.2.wsdl,
konga_database_infoprovider.wsdl
There is a problem with the way arrays of complex types are being serialized
before they are returned to the client from the web service. The problem went
away when returned an object that contained the array (different classes
where then generated for the array, see below). I think the problem is the
way the stubs are generated for the case when a complex array is retured
directly and not as part of a class.
First I had the following interface on which I ran Java2WSDL and then WSDL2WS:
public interface DatabaseInfoProvider {
WsDatabaseObject[] getDatabaseObjects(String sUser, String sPassword,
String connect, String objectTypes[], String searchString);
}
where
public class WsDatabaseObject {
public String sObjectType; // TABLE, VIEW, SP, SYNONYM
public String sObjectName;
public WsDatabaseColumn[] Columns;
}
where
public class WsDatabaseColumn {
public String name;
public Boolean isPrimaryKey;
}
Here is the important part:
The generated code for the array looks like:
typedef struct WsDatabaseObject_ArrayTag
{
WsDatabaseObject** m_Array; // -- BUG MAY BE HERE
int m_Size;
} WsDatabaseObject_Array;
Then I change the interface to:
public interface DatabaseInfoProvider {
WsDatabaseInfo getDatabaseObjects(String sUser, String sPassword,
String connect, String objectTypes[], String searchString);
}
where
public class WsDatabaseInfo {
public WsDatabaseObject[] dbInfo;
}
Note that the only difference is that I now return a class containing the
array, instead of returning the array itself as was the case above.
The code for the array now looks like:
typedef struct WsDatabaseObject_ArrayTag
{
WsDatabaseObject* m_Array; // NOTE: just one * used
int m_Size;
} WsDatabaseObject_Array;
The same thing is true for the nested array ( public WsDatabaseColumn[]
Columns; ). I.e., in the code generated by from the first version of the
interface defined in Java, WsDatabaseColumn_ArrayTag has WsDatabaseColumn**
m_Array;, but in the second version it has WsDatabaseColumn* m_Array;.
The first version crashes when serializing the result to be sent back to the
client. The engine code seems to assume that the arrays are defined as T*
m_Array and not T** m_Array.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
CalClient giving Exception
HI All, I build Axis C++ calclient on Windows. I followed build and setup instructions as per Axis C++ Windows Developers Guide. In xsd__int Calculator::add(xsd__int Value0, xsd__int Value1)function when it calls if (AXIS_SUCCESS != m_pCall-initialize(CPP_RPC_PROVIDER)) it is giving exception AXISC_NODE_VALUE_MISMATCH_EXCEPTION. Apache server is running and I can get page of http://localhost/axis Please let me know what me the problem at the earliest. With Regards Deepak _ A Camera Sells every 2 Minutes on eBay. Get Your's at a Great Price Now! http://adfarm.mediaplex.com/ad/ck/4686-26272-10936-699?ck=Cameras
Is it a bug? Multi-nested includes. Server.generalException - makeTypeElement() was told to create a type ...
Hi
I have a problem with multi-nested includes, and I
thing that it is a bug. I use java Axis 1.3.
I try in my wsdl file to import two difrent
namespaces from two difrent xsd files. And then I generate classes using
WSDL2JAVA (org.apache.axis.wsdl.WSDL2Java -v -a --server-side
--skeletonDeploy true --NStoPkg urn:Wms=wms wms.wsdl ) Then I copy files to
server and when I wanted to see server generated wsdl Axis error is
generated:
AXIS error
Sorry, something seems to have gone wrong... here are the details:
Fault - makeTypeElement() was told to create a type
"{http://www.opengis.net/bla}zzbb", with no containing
elementAxisFaultfaultCode:
{http://schemas.xmlsoap.org/soap/envelope/}Server.generalExceptionfaultSubcode:
faultString: makeTypeElement() was told to create a type
"{http://www.opengis.net/bla}zzbb", with no containing
elementfaultActor: faultNode: faultDetail:
{http://xml.apache.org/axis/}hostname:pocitacSo my question is it is possible to import in wsdl two difrent schemas?Or
not and it is a bug. I enclose some files which demonstrate this problem. I
hope, that they are good writed because I beginner in soap. If it is not bug,
please write to me, how to solve this problem, because it is wery
important.
Thank you
Ales
wms-pok2.xsd
Description: Binary data
wms.wsdl
Description: Binary data
wms_schemas.xsd
Description: Binary data
[jira] Commented: (AXIS-1551) SOAPMonitor should display exceptions too
[ http://issues.apache.org/jira/browse/AXIS-1551?page=comments#action_12360415 ] przemek słupkowski commented on AXIS-1551: -- Are enybody fixing this bug. I would like to use SOAPMonitor in my company to monitor exception but it doesent display it in monitor Or maybe someone got an idea to monitor exception on axias without changing ports (my application send soap messages on some port and I dont want to change it all the time when I want to monitor soap messages) I used tcpmon but it is not that I want. SOAPMonitor that is but doesent work propertly Please do something SOAPMonitor should display exceptions too - Key: AXIS-1551 URL: http://issues.apache.org/jira/browse/AXIS-1551 Project: Apache Axis Type: Improvement Reporter: Markus Heiden Priority: Minor The SOAPMonitor fails to log the answer when the server answers with a remote exception. This response is never displayed in the soap monitor and the request status is still active (the client gets the exception). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Calclient exception on WIndows
HI All, I build Axis C++ calclient on Windows. I followed build and setup instructions as per Axis C++ Windows Developers Guide. In xsd__int Calculator::add(xsd__int Value0, xsd__int Value1)function when it calls if (AXIS_SUCCESS != m_pCall-initialize(CPP_RPC_PROVIDER)) it is giving exception AXISC_NODE_VALUE_MISMATCH_EXCEPTION. Apache server is running and I can get page of http://localhost/axis Please let me know what me the problem at the earliest. With Regards Deepak _ A Camera Sells every 2 Minutes on eBay. Get Your's at a Great Price Now! http://adfarm.mediaplex.com/ad/ck/4686-26272-10936-699?ck=Cameras
FW: Bug in beandeserializer??
Title: Bug in beandeserializer??
Can someone please look into this.
Thanks,
Parikh, Pratik | Software Engineer | Cerner Corporation | (1)-816-201-1298 | [EMAIL PROTECTED] | www.cerner.com
From: Parikh,Pratik
[mailto:[EMAIL PROTECTED] Sent: Tuesday, December 13, 2005
6:55 PMTo: axis-user@ws.apache.orgSubject: Bug in
beandeserializer??
Hi Everyone,
I have a case where the
generated code is that behaving right with case sensitivity. My element name is
"EmptyName" and the generate code is something like this:
elemField
= new org.apache.axis.description.ElementDesc();
elemField.setFieldName("emptyName"); elemField.setXmlName(new
javax.xml.namespace.QName("urn:person-org", "EmptyName"));
elemField.setXmlType(new javax.xml.namespace.QName("urn:person-org",
"PersonOrg.EmptyName"));
elemField.setNillable(false);
typeDesc.addFieldDesc(elemField);
The schema is as following
?xml version="1.0" encoding="utf-8"?
xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
targetNamespace="urn:person-org" elementFormDefault="qualified"
xmlns:porg="urn:person-org" xmlns="urn:person-org"
xs:element name="PersonOrg"
type="PersonOrg.Message"/
xs:complexType name="PersonOrg.Message"
xs:sequence
xs:element
name="EmptyName" type="PersonOrg.EmptyName"/ /xs:sequence /xs:complexType xs:complexType
name="PersonOrg.EmptyName" xs:sequence
xs:element type="xsd:string" minOccurs="1" maxOccurs="1"
name="author"/ /xs:sequence /xs:complexType /xs:schema
faultcodesoapenv:Server.userException/faultcodefaultstringorg.xml.sax.SAXException:
Invalid element in org.person.PersonOrg -
EmptyName/faultstringdetailns1:hostname xmlns:ns1="http://xml.apache.org/axis/"LPP010755/ns1:hostname/detail
When I debugged thought it is erroring out on
BeanDeserilizer line 259. Please help I need to get this working by tomorrow
morning??? I think this is a bug and if someone can fix it for me then it will
be nice???
Thanks, Parikh, Pratik | Software Engineer | Cerner Corporation | (1)-816-201-1298 | [EMAIL PROTECTED] | www.cerner.com
CONFIDENTIALITY NOTICEThis
message and any included attachmentsare from Cerner Corporation and
are intendedonly for the addressee. The informationcontained in
this message is confidential andmay constitute inside or non-public
informationunder international, federal, or statesecurities laws.
Unauthorized forwarding,printing, copying, distribution, or use of
suchinformation is strictly prohibited and may beunlawful. If you
are not the addressee, pleasepromptly delete this message and notify
thesender of the delivery error by e-mail or youmay call Cerner's
corporate offices in KansasCity, Missouri, U.S.A at (+1)
(816)221-1024.
--
[jira] Commented: (AXIS-1551) SOAPMonitor should display exceptions too
[ http://issues.apache.org/jira/browse/AXIS-1551?page=comments#action_12360419 ] Tom Jordahl commented on AXIS-1551: --- I would say it is fairly certain that no one is actively working on this bug. Patches are always welcome. SOAPMonitor should display exceptions too - Key: AXIS-1551 URL: http://issues.apache.org/jira/browse/AXIS-1551 Project: Apache Axis Type: Improvement Reporter: Markus Heiden Priority: Minor The SOAPMonitor fails to log the answer when the server answers with a remote exception. This response is never displayed in the soap monitor and the request status is still active (the client gets the exception). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Is it a bug? Multi-nested includes. Server.generalException - makeTypeElement() was told to create a type ...
You must use xsd:include to bring in a schema with the same
namespace and xsd:import to bring in a schema with a different
namespace. So you must change this:
xsd:schema targetNamespace=
http://www.opengis.net/ows
xsd:import namespace=http://www.opengis.net/ows
schemaLocation=./wms_schemas.xsd
/
/xsd:schema
xsd:schema targetNamespace=
http://www.opengis.net/bla
xsd:import namespace=
http://www.opengis.net/bla
schemaLocation=./wms-pok2.xsd /
/xsd:schema
to this:
xsd:schema targetNamespace=
http://www.opengis.net/ows
xsd:include schemaLocation=
./wms_schemas.xsd
/
/xsd:schema
xsd:schema targetNamespace=
http://www.opengis.net/bla
xsd:include schemaLocation=
./wms-pok2.xsd /
/xsd:schema
Anne
On 12/14/05, Ales St [EMAIL PROTECTED] wrote:
Hi
I have a problem with multi-nested includes, and I
thing that it is a bug. I use java Axis 1.3.
I try in my wsdl file to import two difrent
namespaces from two difrent xsd files. And then I generate classes using
WSDL2JAVA (org.apache.axis.wsdl.WSDL2Java -v -a --server-side
--skeletonDeploy true --NStoPkg urn:Wms=wms wms.wsdl ) Then I copy files to
server and when I wanted to see server generated wsdl Axis error is
generated:
AXIS error
Sorry, something seems to have gone wrong... here are the details:
Fault - makeTypeElement() was told to create a type
{http://www.opengis.net/bla}zzbb, with no containing
elementAxisFaultfaultCode:
{http://schemas.xmlsoap.org/soap/envelope/}Server.generalException
faultSubcode:
faultString: makeTypeElement() was told to create a type
{http://www.opengis.net/bla}zzbb, with no containing
elementfaultActor: faultNode: faultDetail:
{http://xml.apache.org/axis/}hostname:pocitacSo my question is it is possible to import in wsdl two difrent schemas?Or
not and it is a bug. I enclose some files which demonstrate this problem. I
hope, that they are good writed because I beginner in soap. If it is not bug,
please write to me, how to solve this problem, because it is wery
important.
Thank you
Ales
Re: setBody() and setHeader() problem in Axis 1.2 RC3
Hi All,
Can anybody (axis core development team) through some light on this
issue?
These methods work perfectly in Axis1.2 Beta and not in Axis1.2 RC1.3.
It might be a bug or issue in AXIS. Right now these methods are setting
null into SOAP Message.
Thanks,
Damodar.
On Tue, 2005-12-13 at 11:47 -0500, dyemme wrote:
Hi,
I have a problem with two methods in the Axis latest release and I don't
have this problem in the Axis 1.2 Beta versions. The setBody() and
setHeader() methods in the SOAPEnvelope are not working properly in
latest Axis release. Is there any substitute to this methods in the
latest release?.
Thanks,
Damodar.
Here are the details.
public void wsInfraProcessMethod(SOAPEnvelope req, SOAPEnvelope resp) {
if (req.toString().indexOf(
WsrmServiceParameters.getApplicationMessage()) != -1) {
SOAPBody soapBody = null;
SOAPHeader soapHeader = null;
try {
soapBody = (SOAPBody) req.getBody();
soapHeader = (SOAPHeader) req.getHeader();
}
catch (SOAPException ex) {
ex.printStackTrace();
}
resp.setBody(soapBody);
resp.setHeader(soapHeader);
System.out.println( *);
System.out.println(moduleName + Sending message reliably \n +
resp);
System.out.println( *);
}
if (req.toString().indexOf(
WsrmServiceParameters.getResponseMessage()) != -1) {
System.out.println();
System.out.println(moduleName + Message has been received \n
+ req);
System.out.println(*);
}
}
Re: Is it a bug? Multi-nested includes. Server.generalException - makeTypeElement() was told to create a type ...
Hi, I did It, but still the same Server exception.
I write this wsdl to create the simpler similar situation as with StyledLayerDescription.xsd,what I solve. So it is
my wsdl correct?
Ales
- Original Message -
From:
Anne Thomas
Manes
To: axis-dev@ws.apache.org
Sent: Wednesday, December 14, 2005 4:36
PM
Subject: Re: Is it a bug? Multi-nested
includes. Server.generalException - makeTypeElement() was told to create a
type ...
You must use xsd:include to bring in a schema
with the same namespace and xsd:import to bring in a schema with a
different namespace. So you must change this:
xsd:schema
targetNamespace=" http://www.opengis.net/ows"
xsd:import namespace="http://www.opengis.net/ows "
schemaLocation="./wms_schemas.xsd" //xsd:schema
xsd:schema
targetNamespace=" http://www.opengis.net/bla"
xsd:import namespace=" http://www.opengis.net/bla"schemaLocation="./wms-pok2.xsd"
/
/xsd:schemato this:
xsd:schema
targetNamespace=" http://www.opengis.net/ows"
xsd:include schemaLocation="
./wms_schemas.xsd"
/
/xsd:schema
xsd:schema
targetNamespace=" http://www.opengis.net/bla"
xsd:include schemaLocation="
./wms-pok2.xsd" /
/xsd:schemaAnne
On 12/14/05, Ales
St [EMAIL PROTECTED]
wrote:
Hi
I have a problem with multi-nested includes,
and I thing that it is a bug. I use java Axis 1.3.
I try in my wsdl file to import two difrent
namespaces from two difrent xsd files. And then I generate classes using
WSDL2JAVA (org.apache.axis.wsdl.WSDL2Java -v -a --server-side
--skeletonDeploy true --NStoPkg urn:Wms=wms wms.wsdl ) Then I copy files to
server and when I wanted to see server generated wsdl Axis error is
generated:
AXIS error
Sorry, something seems to have gone wrong... here are the
details:
Fault - makeTypeElement() was told to create a type "{http://www.opengis.net/bla}zzbb", with no containing
elementAxisFaultfaultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.generalExceptionfaultSubcode:
faultString: makeTypeElement() was told to create a type "{http://www.opengis.net/bla}zzbb", with no containing
elementfaultActor: faultNode: faultDetail: {http://xml.apache.org/axis/}hostname:pocitacSo my question is it is possible to import in wsdl two
difrent schemas?Or not and it is a bug. I enclose some files which
demonstrate this problem. I hope, that they are good writed because I
beginner in soap. If it is not bug, please write to me, how to solve this
problem, because it is wery important.
Thank you
Ales
Re: Is it a bug? Multi-nested includes. Server.generalException - makeTypeElement() was told to create a type ...
Please post the updated wsdl and schema files.On 12/14/05, Ales St [EMAIL PROTECTED] wrote:
Hi, I did It, but still the same Server exception.
I write this wsdl to create the simpler similar situation as with StyledLayerDescription.xsd,what I solve. So it is
my wsdl correct?
Ales
- Original Message -
From:
Anne Thomas
Manes
To:
axis-dev@ws.apache.org
Sent: Wednesday, December 14, 2005 4:36
PM
Subject: Re: Is it a bug? Multi-nested
includes. Server.generalException - makeTypeElement() was told to create a
type ...
You must use xsd:include to bring in a schema
with the same namespace and xsd:import to bring in a schema with a
different namespace. So you must change this:
xsd:schema
targetNamespace= http://www.opengis.net/ows
xsd:import namespace=http://www.opengis.net/ows
schemaLocation=./wms_schemas.xsd //xsd:schema
xsd:schema
targetNamespace= http://www.opengis.net/bla
xsd:import namespace= http://www.opengis.net/bla
schemaLocation=./wms-pok2.xsd
/
/xsd:schemato this:
xsd:schema
targetNamespace= http://www.opengis.net/ows
xsd:include schemaLocation=
./wms_schemas.xsd
/
/xsd:schema
xsd:schema
targetNamespace= http://www.opengis.net/bla
xsd:include schemaLocation=
./wms-pok2.xsd /
/xsd:schemaAnne
On 12/14/05, Ales
St [EMAIL PROTECTED]
wrote:
Hi
I have a problem with multi-nested includes,
and I thing that it is a bug. I use java Axis 1.3.
I try in my wsdl file to import two difrent
namespaces from two difrent xsd files. And then I generate classes using
WSDL2JAVA (org.apache.axis.wsdl.WSDL2Java -v -a --server-side
--skeletonDeploy true --NStoPkg urn:Wms=wms wms.wsdl ) Then I copy files to
server and when I wanted to see server generated wsdl Axis error is
generated:
AXIS error
Sorry, something seems to have gone wrong... here are the
details:
Fault - makeTypeElement() was told to create a type {http://www.opengis.net/bla}zzbb, with no containing
elementAxisFaultfaultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.generalException
faultSubcode:
faultString: makeTypeElement() was told to create a type {http://www.opengis.net/bla}zzbb, with no containing
elementfaultActor: faultNode: faultDetail: {http://xml.apache.org/axis/}hostname:pocitac
So my question is it is possible to import in wsdl two
difrent schemas?Or not and it is a bug. I enclose some files which
demonstrate this problem. I hope, that they are good writed because I
beginner in soap. If it is not bug, please write to me, how to solve this
problem, because it is wery important.
Thank you
Ales
Re: Is it a bug? Multi-nested includes. Server.generalException - makeTypeElement() was told to create a type ...
Here is that files.
- Original Message -
From:
Anne Thomas
Manes
To: axis-dev@ws.apache.org
Sent: Wednesday, December 14, 2005 5:18
PM
Subject: Re: Is it a bug? Multi-nested
includes. Server.generalException - makeTypeElement() was told to create a
type ...
Please post the updated wsdl and schema files.
On 12/14/05, Ales
St [EMAIL PROTECTED]
wrote:
Hi, I did It, but still the same Server
exception. I write this wsdl to create the simpler similar situation as
with StyledLayerDescription.xsd,what I solve. So it is my wsdl
correct?
Ales
-
Original Message -
From:
Anne Thomas Manes
To:
axis-dev@ws.apache.org
Sent:
Wednesday, December 14, 2005 4:36 PM
Subject:
Re: Is it a bug? Multi-nested includes. Server.generalException -
makeTypeElement() was told to create a type ...
You must use xsd:include to bring in a
schema with the same namespace and xsd:import to bring in a schema
with a different namespace. So you must change this:
xsd:schema
targetNamespace="
http://www.opengis.net/ows"
xsd:import
namespace="http://www.opengis.net/ows
"
schemaLocation="./wms_schemas.xsd"
//xsd:schema
xsd:schema
targetNamespace="
http://www.opengis.net/bla"
xsd:import
namespace="
http://www.opengis.net/bla
"schemaLocation="./wms-pok2.xsd"
/
/xsd:schemato
this:
xsd:schema
targetNamespace="
http://www.opengis.net/ows"
xsd:include
schemaLocation="
./wms_schemas.xsd" /
/xsd:schema
xsd:schema
targetNamespace="
http://www.opengis.net/bla"
xsd:include
schemaLocation="
./wms-pok2.xsd" /
/xsd:schemaAnne
On 12/14/05, Ales
St [EMAIL PROTECTED]
wrote:
Hi
I have a problem with multi-nested
includes, and I thing that it is a bug. I use java Axis
1.3.
I try in my wsdl file to import two difrent
namespaces from two difrent xsd files. And then I generate classes using
WSDL2JAVA (org.apache.axis.wsdl.WSDL2Java -v -a --server-side
--skeletonDeploy true --NStoPkg urn:Wms=wms wms.wsdl ) Then I copy files
to server and when I wanted to see server generated wsdl Axis error is
generated:
AXIS error
Sorry, something seems to have gone wrong... here are the
details:
Fault - makeTypeElement() was told to create a type "{http://www.opengis.net/bla}zzbb", with no
containing elementAxisFaultfaultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.generalException
faultSubcode: faultString: makeTypeElement() was told to
create a type "{http://www.opengis.net/bla}zzbb", with no
containing elementfaultActor: faultNode: faultDetail:
{http://xml.apache.org/axis/}hostname:pocitac
So my question is it is possible to
import in wsdl two difrent schemas?Or not and it is a bug. I enclose
some files which demonstrate this problem. I hope, that they are good
writed because I beginner in soap. If it is not bug, please write to me,
how to solve this problem, because it is wery important.
Thank you
Ales
wms.wsdl
Description: Binary data
wms_schemas.xsd
Description: Binary data
wms-pok2.xsd
Description: Binary data
wms-pok.xsd
Description: Binary data
getPrefix() problem with axis 1.3?
Hello, I have noticed a few posts regarding the exception below that occurrs while running WSDL2Java. Is there a resolution or work around for this issue? I have ensured that I have the correct wsdl4j jar, although I can only find the class in the jaxrpc jar. [axis-wsdl2java] java.lang.NoSuchMethodError: javax.xml.namespace.QName.getPrefix()Ljava/lang/String; [axis-wsdl2java]at org.apache.axis.wsdl.symbolTable.BackslashUtil.getQNameWithDifferentLoca l(BackslashUtil.java:62) [axis-wsdl2java]at org.apache.axis.wsdl.symbolTable.BackslashUtil.getQNameWithBackslashless Local(BackslashUtil.java:39) [axis-wsdl2java]at org.apache.axis.wsdl.symbolTable.SymbolTable.populateServices(SymbolTabl e.java:3078) [axis-wsdl2java]at org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:7 45) [axis-wsdl2java]at org.apache.axis.wsdl.symbolTable.SymbolTable.add(SymbolTable.java:543) [axis-wsdl2java]at org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:5 18) [axis-wsdl2java]at org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:4 95) [axis-wsdl2java]at org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run(Parser.java:361) [axis-wsdl2java]at java.lang.Thread.run(Thread.java:534) Any help would be greatly appreciated Thanks Jeremy
Re: Is it a bug? Multi-nested includes. Server.generalException - makeTypeElement() was told to create a type ...
You have a bunch of namespace errors in these files.
Fix them and try again.
I strongly recommend that you use a WSDL editor such as Cape Clear SOA
Editor. (It's free.) See http://www.capescience.com/soa/index.shtml.
The validate function is very handy.
AnneOn 12/14/05, Ales St [EMAIL PROTECTED] wrote:
Here is that files.
- Original Message -
From:
Anne Thomas
Manes
To:
axis-dev@ws.apache.org
Sent: Wednesday, December 14, 2005 5:18
PM
Subject: Re: Is it a bug? Multi-nested
includes. Server.generalException - makeTypeElement() was told to create a
type ...
Please post the updated wsdl and schema files.
On 12/14/05, Ales
St [EMAIL PROTECTED]
wrote:
Hi, I did It, but still the same Server
exception. I write this wsdl to create the simpler similar situation as
with StyledLayerDescription.xsd,what I solve. So it is my wsdl
correct?
Ales
-
Original Message -
From:
Anne Thomas Manes
To:
axis-dev@ws.apache.org
Sent:
Wednesday, December 14, 2005 4:36 PM
Subject:
Re: Is it a bug? Multi-nested includes. Server.generalException -
makeTypeElement() was told to create a type ...
You must use xsd:include to bring in a
schema with the same namespace and xsd:import to bring in a schema
with a different namespace. So you must change this:
xsd:schema
targetNamespace=
http://www.opengis.net/ows
xsd:import
namespace=http://www.opengis.net/ows
schemaLocation=./wms_schemas.xsd
//xsd:schema
xsd:schema
targetNamespace=
http://www.opengis.net/bla
xsd:import
namespace=
http://www.opengis.net/bla
schemaLocation=./wms-pok2.xsd
/
/xsd:schemato
this:
xsd:schema
targetNamespace=
http://www.opengis.net/ows
xsd:include
schemaLocation=
./wms_schemas.xsd /
/xsd:schema
xsd:schema
targetNamespace=
http://www.opengis.net/bla
xsd:include
schemaLocation=
./wms-pok2.xsd /
/xsd:schemaAnne
On 12/14/05, Ales
St [EMAIL PROTECTED]
wrote:
Hi
I have a problem with multi-nested
includes, and I thing that it is a bug. I use java Axis
1.3.
I try in my wsdl file to import two difrent
namespaces from two difrent xsd files. And then I generate classes using
WSDL2JAVA (org.apache.axis.wsdl.WSDL2Java -v -a --server-side
--skeletonDeploy true --NStoPkg urn:Wms=wms wms.wsdl ) Then I copy files
to server and when I wanted to see server generated wsdl Axis error is
generated:
AXIS error
Sorry, something seems to have gone wrong... here are the
details:
Fault - makeTypeElement() was told to create a type {http://www.opengis.net/bla}zzbb, with no
containing elementAxisFaultfaultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.generalException
faultSubcode: faultString: makeTypeElement() was told to
create a type {http://www.opengis.net/bla}zzbb, with no
containing elementfaultActor: faultNode: faultDetail:
{http://xml.apache.org/axis/}hostname:pocitac
So my question is it is possible to
import in wsdl two difrent schemas?Or not and it is a bug. I enclose
some files which demonstrate this problem. I hope, that they are good
writed because I beginner in soap. If it is not bug, please write to me,
how to solve this problem, because it is wery important.
Thank you
Ales
Re: Is it a bug? Multi-nested includes. Server.generalException - makeTypeElement() was told to create a type ...
Hi
I see my file in Cape Clear SOA Editor and see that errors,bud I don't know how to fix
them, please help.
Thank you
Ales
- Original Message -
From:
Anne Thomas
Manes
To: axis-dev@ws.apache.org
Sent: Wednesday, December 14, 2005 6:27
PM
Subject: Re: Is it a bug? Multi-nested
includes. Server.generalException - makeTypeElement() was told to create a
type ...
You have a bunch of namespace errors in these files. Fix
them and try again.I strongly recommend that you use a WSDL editor
such as Cape Clear SOA Editor. (It's free.) See http://www.capescience.com/soa/index.shtml.
The validate function is very handy.Anne
On 12/14/05, Ales
St [EMAIL PROTECTED]
wrote:
Here is that files.
-
Original Message -
From:
Anne Thomas Manes
To:
axis-dev@ws.apache.org
Sent:
Wednesday, December 14, 2005 5:18 PM
Subject:
Re: Is it a bug? Multi-nested includes. Server.generalException -
makeTypeElement() was told to create a type ...
Please post the updated wsdl and schema files.
On 12/14/05, Ales
St [EMAIL PROTECTED]
wrote:
Hi, I did It, but still the same Server
exception. I write this wsdl to create the simpler similar situation as
with StyledLayerDescription.xsd,what I solve. So it is my wsdl
correct?
Ales
-
Original Message -
From:
Anne Thomas Manes
To:
axis-dev@ws.apache.org
Sent:
Wednesday, December 14, 2005 4:36 PM
Subject:
Re: Is it a bug? Multi-nested includes. Server.generalException -
makeTypeElement() was told to create a type ...
You must use xsd:include to bring in a
schema with the same namespace and xsd:import to bring in a
schema with a different namespace. So you must change this:
xsd:schema
targetNamespace="
http://www.opengis.net/ows"
xsd:import
namespace="http://www.opengis.net/ows
"
schemaLocation="./wms_schemas.xsd"
//xsd:schema
xsd:schema
targetNamespace="
http://www.opengis.net/bla"
xsd:import
namespace="
http://www.opengis.net/bla
"schemaLocation="./wms-pok2.xsd"
/
/xsd:schemato
this:
xsd:schema
targetNamespace="
http://www.opengis.net/ows"
xsd:include
schemaLocation="
./wms_schemas.xsd" /
/xsd:schema
xsd:schema
targetNamespace="
http://www.opengis.net/bla"
xsd:include
schemaLocation="
./wms-pok2.xsd" /
/xsd:schemaAnne
On 12/14/05, Ales St [EMAIL PROTECTED]
wrote:
Hi
I have a problem with multi-nested
includes, and I thing that it is a bug. I use java Axis
1.3.
I try in my wsdl file to import two
difrent namespaces from two difrent xsd files. And then I generate
classes using WSDL2JAVA (org.apache.axis.wsdl.WSDL2Java -v -a
--server-side --skeletonDeploy true --NStoPkg urn:Wms=wms
wms.wsdl ) Then I copy files to server and when I wanted to see
server generated wsdl Axis error is generated:
AXIS error
Sorry, something seems to have gone wrong... here are the
details:
Fault - makeTypeElement() was told to create a type "{http://www.opengis.net/bla}zzbb", with no
containing elementAxisFaultfaultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.generalException
faultSubcode: faultString: makeTypeElement() was told to
create a type "{http://www.opengis.net/bla}zzbb", with no
containing elementfaultActor: faultNode: faultDetail:
{http://xml.apache.org/axis/}hostname:pocitac
So my question is it is possible
to import in wsdl two difrent schemas?Or not and it is a bug. I
enclose some files which demonstrate this problem. I hope, that they
are good writed because I beginner in soap. If it is not bug, please
write to me, how to solve this problem, because it is wery
important.
Thank you
Ales
Re: Is it a bug? Multi-nested includes. Server.generalException - makeTypeElement() was told to create a type ...
Sorry, I'm not going to do your homework for you.On 12/14/05, Ales St [EMAIL PROTECTED] wrote:
Hi
I see my file in Cape Clear SOA Editor and see that errors,bud I don't know how to fix
them, please help.
Thank you
Ales
- Original Message -
From:
Anne Thomas
Manes
To:
axis-dev@ws.apache.org
Sent: Wednesday, December 14, 2005 6:27
PM
Subject: Re: Is it a bug? Multi-nested
includes. Server.generalException - makeTypeElement() was told to create a
type ...
You have a bunch of namespace errors in these files. Fix
them and try again.I strongly recommend that you use a WSDL editor
such as Cape Clear SOA Editor. (It's free.) See http://www.capescience.com/soa/index.shtml
.
The validate function is very handy.Anne
On 12/14/05, Ales
St [EMAIL PROTECTED]
wrote:
Here is that files.
-
Original Message -
From:
Anne Thomas Manes
To:
axis-dev@ws.apache.org
Sent:
Wednesday, December 14, 2005 5:18 PM
Subject:
Re: Is it a bug? Multi-nested includes. Server.generalException -
makeTypeElement() was told to create a type ...
Please post the updated wsdl and schema files.
On 12/14/05, Ales
St [EMAIL PROTECTED]
wrote:
Hi, I did It, but still the same Server
exception. I write this wsdl to create the simpler similar situation as
with StyledLayerDescription.xsd,what I solve. So it is my wsdl
correct?
Ales
-
Original Message -
From:
Anne Thomas Manes
To:
axis-dev@ws.apache.org
Sent:
Wednesday, December 14, 2005 4:36 PM
Subject:
Re: Is it a bug? Multi-nested includes. Server.generalException -
makeTypeElement() was told to create a type ...
You must use xsd:include to bring in a
schema with the same namespace and xsd:import to bring in a
schema with a different namespace. So you must change this:
xsd:schema
targetNamespace=
http://www.opengis.net/ows
xsd:import
namespace=http://www.opengis.net/ows
schemaLocation=./wms_schemas.xsd
//xsd:schema
xsd:schema
targetNamespace=
http://www.opengis.net/bla
xsd:import
namespace=
http://www.opengis.net/bla
schemaLocation=./wms-pok2.xsd
/
/xsd:schemato
this:
xsd:schema
targetNamespace=
http://www.opengis.net/ows
xsd:include
schemaLocation=
./wms_schemas.xsd /
/xsd:schema
xsd:schema
targetNamespace=
http://www.opengis.net/bla
xsd:include
schemaLocation=
./wms-pok2.xsd /
/xsd:schemaAnne
On 12/14/05, Ales St [EMAIL PROTECTED]
wrote:
Hi
I have a problem with multi-nested
includes, and I thing that it is a bug. I use java Axis
1.3.
I try in my wsdl file to import two
difrent namespaces from two difrent xsd files. And then I generate
classes using WSDL2JAVA (org.apache.axis.wsdl.WSDL2Java -v -a
--server-side --skeletonDeploy true --NStoPkg urn:Wms=wms
wms.wsdl ) Then I copy files to server and when I wanted to see
server generated wsdl Axis error is generated:
AXIS error
Sorry, something seems to have gone wrong... here are the
details:
Fault - makeTypeElement() was told to create a type {http://www.opengis.net/bla}zzbb, with no
containing elementAxisFaultfaultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.generalException
faultSubcode: faultString: makeTypeElement() was told to
create a type {http://www.opengis.net/bla}zzbb, with no
containing elementfaultActor: faultNode: faultDetail:
{http://xml.apache.org/axis/}hostname:pocitac
So my question is it is possible
to import in wsdl two difrent schemas?Or not and it is a bug. I
enclose some files which demonstrate this problem. I hope, that they
are good writed because I beginner in soap. If it is not bug, please
write to me, how to solve this problem, because it is wery
important.
Thank you
Re: Is it a bug? Multi-nested includes. Server.generalException - makeTypeElement() was told to create a type ...
Ok,I try to solve it by myself, but problem is , that I trying to solve it for one week and still can't find resolution. So I try to askyou, where can I find somegood book or web pages about wsdl i know only this http://www.w3.org/TR/wsdland it is hard for me to find resolution of my problem there. Or do you knew some source where where is my problem solved? Please help Ales - Original Message - From: Anne Thomas Manes To: axis-dev@ws.apache.org Sent: Wednesday, December 14, 2005 6:54 PM Subject: Re: Is it a bug? Multi-nested includes. Server.generalException - makeTypeElement() was told to create a type ... Sorry, I'm not going to do your homework for you. On 12/14/05, Ales St [EMAIL PROTECTED] wrote: Hi I see my file in Cape Clear SOA Editor and see that errors,bud I don't know how to fix them, please help. Thank you Ales - Original Message - From: Anne Thomas Manes To: axis-dev@ws.apache.org Sent: Wednesday, December 14, 2005 6:27 PM Subject: Re: Is it a bug? Multi-nested includes. Server.generalException - makeTypeElement() was told to create a type ... You have a bunch of namespace errors in these files. Fix them and try again.I strongly recommend that you use a WSDL editor such as Cape Clear SOA Editor. (It's free.) See http://www.capescience.com/soa/index.shtml . The validate function is very handy.Anne On 12/14/05, Ales St [EMAIL PROTECTED] wrote: Here is that files. - Original Message - From: Anne Thomas Manes To: axis-dev@ws.apache.org Sent: Wednesday, December 14, 2005 5:18 PM Subject: Re: Is it a bug? Multi-nested includes. Server.generalException - makeTypeElement() was told to create a type ... Please post the updated wsdl and schema files. On 12/14/05, Ales St [EMAIL PROTECTED] wrote: Hi, I did It, but still the same Server exception. I write this wsdl to create the simpler similar situation as with StyledLayerDescription.xsd,what I solve. So it is my wsdl correct? Ales - Original Message - From: Anne Thomas Manes To: axis-dev@ws.apache.org Sent: Wednesday, December 14, 2005 4:36 PM Subject: Re: Is it a bug? Multi-nested includes. Server.generalException - makeTypeElement() was told to create a type ... You must use xsd:include to bring in a schema with the same namespace and xsd:import to bring in a schema with a different namespace. So you must change this: xsd:schema targetNamespace=" http://www.opengis.net/ows" xsd:import namespace="http://www.opengis.net/ows " schemaLocation="./wms_schemas.xsd" //xsd:schema xsd:schema targetNamespace=" http://www.opengis.net/bla" xsd:import namespace=" http://www.opengis.net/bla "schemaLocation="./wms-pok2.xsd" / /xsd:schemato this: xsd:schema targetNamespace=" http://www.opengis.net/ows" xsd:include schemaLocation=" ./wms_schemas.xsd" / /xsd:schema xsd:schema targetNamespace=" http://www.opengis.net/bla" xsd:include schemaLocation=" ./wms-pok2.xsd" / /xsd:schemaAnne On 12/14/05, Ales St [EMAIL PROTECTED] wrote: Hi I have a problem with multi-nested includes, and I thing that it is a bug. I use java Axis 1.3. I try in my wsdl file to import two difrent namespaces from two difrent xsd files. And then I generate classes using WSDL2JAVA
Re: [Axis2] Maven module for DOOM
On Wed, 2005-12-14 at 15:26 +0600, Ruchith Fernando wrote: Hi All, Right now DOOM is in saaj maven module and therefore the security maven module has a dependency on saaj [1]. And anyone else who'd want to use DOOM will have to use axis2-saaj-##.jar Shall we move the DOOM code from saaj to a new maven module? +1. Sanjiva.
Re: Clustering Axis2
On Tue, 2005-12-13 at 23:52 -0800, Dennis Sosnoski wrote: My first thought was that it would be pretty much automatic when Axis2 is deployed to a clusterable server - but then there are all the issues of deploying services and sharing service state information across the cluster. At an absolute minimum I'd think the deployment interface would need to be cluster-aware. +1. We've started on that already .. with refactoring the config stuff to not be file independent. Once that's done we'd need to implement a cluster-aware config impl and things should work right. Also looking at RSS based approaches for distributing config data. Let's see how it goes! Sanjiva.
Re: [Axis2] Maven module for DOOM
Hi Ruchith, all: Right now DOOM is in saaj maven module and therefore the security maven module has a dependency on saaj [1]. And anyone else who'd want to use DOOM will have to use axis2-saaj-##.jar Shall we move the DOOM code from saaj to a new maven module? What's the relationship between the DOOM code and the SAAJ code? Do we have two different DOM implementations over OM now? --Glen
RE: Clustering Axis2
Any plans on using something like WADI. It's not complete but it's currently a subproject of Geronimo. It does things like Web session clustering. May be u guys can build on top of it to support SOAP session clustering so that if one node fails the client can be redirected to another node transparently. Rajith -Original Message- From: Sanjiva Weerawarana [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 14, 2005 1:19 PM To: axis-dev@ws.apache.org Subject: Re: Clustering Axis2 On Tue, 2005-12-13 at 23:52 -0800, Dennis Sosnoski wrote: My first thought was that it would be pretty much automatic when Axis2 is deployed to a clusterable server - but then there are all the issues of deploying services and sharing service state information across the cluster. At an absolute minimum I'd think the deployment interface would need to be cluster-aware. +1. We've started on that already .. with refactoring the config stuff to not be file independent. Once that's done we'd need to implement a cluster-aware config impl and things should work right. Also looking at RSS based approaches for distributing config data. Let's see how it goes! Sanjiva.
RE: Clustering Axis2
On Wed, 2005-12-14 at 13:29 -0500, Rajith Attapattu wrote: Any plans on using something like WADI. It's not complete but it's currently a subproject of Geronimo. It does things like Web session clustering. May be u guys can build on top of it to support SOAP session clustering so that if one node fails the client can be redirected to another node transparently. Ah I forgot about you :) .. can you help get that sorted out? We'd love to use WADI (I know nothing about it .. pointer appreciated) if it does the job for us! Sanjiva.
Re: [Axis2] Maven module for DOOM
On Wed, 2005-12-14 at 10:25 -0800, Glen Daniels wrote: Hi Ruchith, all: Right now DOOM is in saaj maven module and therefore the security maven module has a dependency on saaj [1]. And anyone else who'd want to use DOOM will have to use axis2-saaj-##.jar Shall we move the DOOM code from saaj to a new maven module? What's the relationship between the DOOM code and the SAAJ code? Do we have two different DOM implementations over OM now? No .. the SAAJ code was incomplete and now we have to go back and build SAAJ over DOOM. Sanjiva.
Re: Is it a bug? Multi-nested includes. Server.generalException - makeTypeElement() was told to create a type ...
Your problems are with schema and namespaces, not with WSDL. In addition to the wsdl spec, you should study these documents: - WS-I Basic Profile: http://www.ws-i.org/Profiles/BasicProfile-1.1-2004-08-24.html - XML Namespaces: http://www.w3.org/TR/REC-xml-names/ - XML Schema Tutorial: http://www.w3schools.com/schema/default.asp - XML Schema Primer: http://www.w3.org/TR/xmlschema-0/ I think you should work on the assumption that it isn't a bug, but a problem with the way you're importing/including schemas and referencing elements. XML Schema is really complicated, but you're fortunate in that you don't really need to define your elements and types. You just need to import and include the files properly, and reference your elements and types properly. Going back to your first question -- that was caused by the fact that the StyledLayerDescription element references elements (Name, Description, etc) that are defined in the common.xsd schema rather than in the sld.xsd schema, and the sld.xsd schema doesn't x:include common.xsd schema. (They are both in the sld namespace, therefore you must x:include the common.xsd schema rather than x:import it.) As I said to you before, I recommend that you consolidate all the schemas that have the same targetNamespace. That should resolve the problems you're experiencing. AnneOn 12/14/05, Ales St [EMAIL PROTECTED] wrote: Ok,I try to solve it by myself, but problem is , that I trying to solve it for one week and still can't find resolution. So I try to askyou, where can I find somegood book or web pages about wsdl i know only this http://www.w3.org/TR/wsdland it is hard for me to find resolution of my problem there. Or do you knew some source where where is my problem solved? Please help Ales - Original Message - From: Anne Thomas Manes To: axis-dev@ws.apache.org Sent: Wednesday, December 14, 2005 6:54 PM Subject: Re: Is it a bug? Multi-nested includes. Server.generalException - makeTypeElement() was told to create a type ... Sorry, I'm not going to do your homework for you. On 12/14/05, Ales St [EMAIL PROTECTED] wrote: Hi I see my file in Cape Clear SOA Editor and see that errors,bud I don't know how to fix them, please help. Thank you Ales - Original Message - From: Anne Thomas Manes To: axis-dev@ws.apache.org Sent: Wednesday, December 14, 2005 6:27 PM Subject: Re: Is it a bug? Multi-nested includes. Server.generalException - makeTypeElement() was told to create a type ... You have a bunch of namespace errors in these files. Fix them and try again.I strongly recommend that you use a WSDL editor such as Cape Clear SOA Editor. (It's free.) See http://www.capescience.com/soa/index.shtml . The validate function is very handy.Anne On 12/14/05, Ales St [EMAIL PROTECTED] wrote: Here is that files. - Original Message - From: Anne Thomas Manes To: axis-dev@ws.apache.org Sent: Wednesday, December 14, 2005 5:18 PM Subject: Re: Is it a bug? Multi-nested includes. Server.generalException - makeTypeElement() was told to create a type ... Please post the updated wsdl and schema files. On 12/14/05, Ales St [EMAIL PROTECTED] wrote: Hi, I did It, but still the same Server exception. I write this wsdl to create the simpler similar situation as with StyledLayerDescription.xsd,what I solve. So it is my wsdl correct? Ales - Original Message - From: Anne Thomas Manes To: axis-dev@ws.apache.org Sent: Wednesday, December 14, 2005 4:36 PM Subject: Re: Is it a bug? Multi-nested includes. Server.generalException - makeTypeElement() was told to create a type ... You must use xsd:include to bring in a schema with the same namespace and xsd:import to bring in a schema with a different namespace. So you must change this: xsd:schema targetNamespace= http://www.opengis.net/ows xsd:import namespace=http://www.opengis.net/ows schemaLocation=./wms_schemas.xsd //xsd:schema xsd:schema targetNamespace= http://www.opengis.net/bla
RE: getPrefix() problem with axis 1.3?
You are probably getting a older wsdl4j jar file from somewhere else on your classpath. -- Tom Jordahl Adobe ColdFusion Team -Original Message- From: Cooper, Jeremy [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 14, 2005 11:40 AM To: axis-dev@ws.apache.org Cc: Cooper, Jeremy Subject: getPrefix() problem with axis 1.3? Hello, I have noticed a few posts regarding the exception below that occurrs while running WSDL2Java. Is there a resolution or work around for this issue? I have ensured that I have the correct wsdl4j jar, although I can only find the class in the jaxrpc jar. [axis-wsdl2java] java.lang.NoSuchMethodError: javax.xml.namespace.QName.getPrefix()Ljava/lang/String; [axis-wsdl2java]at org.apache.axis.wsdl.symbolTable.BackslashUtil.getQNameWithDifferentLoca l(BackslashUtil.java:62) [axis-wsdl2java]at org.apache.axis.wsdl.symbolTable.BackslashUtil.getQNameWithBackslashless Local(BackslashUtil.java:39) [axis-wsdl2java]at org.apache.axis.wsdl.symbolTable.SymbolTable.populateServices(SymbolTabl e.java:3078) [axis-wsdl2java]at org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:7 45) [axis-wsdl2java]at org.apache.axis.wsdl.symbolTable.SymbolTable.add(SymbolTable.java:543) [axis-wsdl2java]at org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:5 18) [axis-wsdl2java]at org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:4 95) [axis-wsdl2java]at org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run(Parser.java:361) [axis-wsdl2java]at java.lang.Thread.run(Thread.java:534) Any help would be greatly appreciated Thanks Jeremy
RE: setBody() and setHeader() problem in Axis 1.2 RC3
Hi Tom,
It didn't work with Axis 1.3 Final either. It works only with Axis 1.2
Beta and older versions. I don't what changes they made to the latest
releases.
Thanks,
Damodar.
On Wed, 2005-12-14 at 12:27 -0800, Tom Jordahl wrote:
Why don't you try the 1.3 final release or a build of the current source
tree and see if the problem is fixed.
--
Tom Jordahl
Adobe ColdFusion Team
-Original Message-
From: dyemme [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 14, 2005 10:55 AM
To: axis-dev@ws.apache.org
Subject: Re: setBody() and setHeader() problem in Axis 1.2 RC3
Hi All,
Can anybody (axis core development team) through some light on this
issue?
These methods work perfectly in Axis1.2 Beta and not in Axis1.2 RC1.3.
It might be a bug or issue in AXIS. Right now these methods are
setting
null into SOAP Message.
Thanks,
Damodar.
On Tue, 2005-12-13 at 11:47 -0500, dyemme wrote:
Hi,
I have a problem with two methods in the Axis latest release and I
don't
have this problem in the Axis 1.2 Beta versions. The setBody() and
setHeader() methods in the SOAPEnvelope are not working properly in
latest Axis release. Is there any substitute to this methods in the
latest release?.
Thanks,
Damodar.
Here are the details.
public void wsInfraProcessMethod(SOAPEnvelope req, SOAPEnvelope
resp) {
if (req.toString().indexOf(
WsrmServiceParameters.getApplicationMessage()) != -1) {
SOAPBody soapBody = null;
SOAPHeader soapHeader = null;
try {
soapBody = (SOAPBody) req.getBody();
soapHeader = (SOAPHeader) req.getHeader();
}
catch (SOAPException ex) {
ex.printStackTrace();
}
resp.setBody(soapBody);
resp.setHeader(soapHeader);
System.out.println( *);
System.out.println(moduleName + Sending message reliably \n
+
resp);
System.out.println( *);
}
if (req.toString().indexOf(
WsrmServiceParameters.getResponseMessage()) != -1) {
System.out.println();
System.out.println(moduleName + Message has been received
\n
+ req);
System.out.println(*);
}
}
Re: Is it a bug? Multi-nested includes. Server.generalException - makeTypeElement() was told to create a type ...
Hi Thank you for your time. I willstudy that documents and I hope, that it help me. Now i know that it is not a bug, because I use Cape Clear SOA Editor and use: Insert -Embedded schema from file, it insert xsd schemas to my wsdl file and it works. But it insert all schema definition, and it is not, what I want. So i try to Schema-Insert schema import ,and it write error: "The prefix "xsd" for element "xsd:import" is not bound. at Line: 1 Character: 175" ,bud when I get to validate xsd. file , everything is Ok. I will work on it and I hope, that I will find a solution. Thank you again for your time, because you help me a lot. Ales - Original Message - From: Anne Thomas Manes To: axis-dev@ws.apache.org Sent: Wednesday, December 14, 2005 9:35 PM Subject: Re: Is it a bug? Multi-nested includes. Server.generalException - makeTypeElement() was told to create a type ... Your problems are with schema and namespaces, not with WSDL. In addition to the wsdl spec, you should study these documents:- WS-I Basic Profile: http://www.ws-i.org/Profiles/BasicProfile-1.1-2004-08-24.html- XML Namespaces: http://www.w3.org/TR/REC-xml-names/- XML Schema Tutorial: http://www.w3schools.com/schema/default.asp- XML Schema Primer: http://www.w3.org/TR/xmlschema-0/I think you should work on the assumption that it isn't a bug, but a problem with the way you're importing/including schemas and referencing elements. XML Schema is really complicated, but you're fortunate in that you don't really need to define your elements and types. You just need to import and include the files properly, and reference your elements and types properly.Going back to your first question -- that was caused by the fact that the StyledLayerDescription element references elements (Name, Description, etc) that are defined in the common.xsd schema rather than in the sld.xsd schema, and the sld.xsd schema doesn't x:include common.xsd schema. (They are both in the sld namespace, therefore you must x:include the common.xsd schema rather than x:import it.)As I said to you before, I recommend that you consolidate all the schemas that have the same targetNamespace. That should resolve the problems you're experiencing.Anne On 12/14/05, Ales St [EMAIL PROTECTED] wrote: Ok,I try to solve it by myself, but problem is , that I trying to solve it for one week and still can't find resolution. So I try to askyou, where can I find somegood book or web pages about wsdl i know only this http://www.w3.org/TR/wsdland it is hard for me to find resolution of my problem there. Or do you knew some source where where is my problem solved? Please help Ales - Original Message - From: Anne Thomas Manes To: axis-dev@ws.apache.org Sent: Wednesday, December 14, 2005 6:54 PM Subject: Re: Is it a bug? Multi-nested includes. Server.generalException - makeTypeElement() was told to create a type ... Sorry, I'm not going to do your homework for you. On 12/14/05, Ales St [EMAIL PROTECTED] wrote: Hi I see my file in Cape Clear SOA Editor and see that errors,bud I don't know how to fix them, please help. Thank you Ales - Original Message - From: Anne Thomas Manes To: axis-dev@ws.apache.org Sent: Wednesday, December 14, 2005 6:27 PM Subject: Re: Is it a bug? Multi-nested includes. Server.generalException - makeTypeElement() was told to create a type ... You have a bunch of namespace errors in these files. Fix them and try again.I strongly recommend that you use a WSDL editor such as Cape Clear SOA Editor. (It's free.) See http://www.capescience.com/soa/index.shtml . The validate function is very handy.Anne On 12/14/05, Ales St [EMAIL PROTECTED] wrote: Here is that files. - Original Message - From: Anne Thomas Manes To: axis-dev@ws.apache.org Sent: Wednesday, December 14, 2005 5:18 PM Subject: Re: Is it a bug? Multi-nested includes. Server.generalException - makeTypeElement() was told to create a type ... Please post the updated wsdl and schema files. On 12/14/05, Ales St [EMAIL PROTECTED] wrote: Hi, I did It, but still the same Server exception. I write this wsdl to create the
[axis2][SampleCompetition] Rhino sample
Hi there!
Stimulated by the hope of winning a shiny Nano, I started hacking a
sample integrating Rhino and Axis2. I know Rhino quite well as Cocoon is
using it extensively, but I'm a total newbie when it comes to Axis2. So
I wrote the sample, but failed to run a test to see if it actually works.
So please find attached the patch against modules/samples with what I've
been up to, in the hope that it can be useful and that you guys can
spend a bit of time to check if it works.
Thanks,
Sylvain
PS: I started to use Axiom for what could become a StAX-based Cocoon.
Nice stuff, although I found little things that I'm missing. Working
around for now, but expect some patches in the near future :-)
--
Sylvain WallezAnyware Technologies
http://bluxte.net http://www.anyware-tech.com
Apache Software Foundation Member Research Technology Director
Index: maven.xml
===
--- maven.xml (revision 355804)
+++ maven.xml (working copy)
@@ -258,6 +258,26 @@
/goal
!-- --
+!--- Rhino Service Sample --
+!-- --
+
+goal name=rhino
+mkdir dir=target/samples/
+ant:copy file=./src/sample/rhino/rhino-sample.js
tofile=target/samples/rhino/sample/rhino/rhino-sample.js/
+ant:copy file=target/classes/sample/rhino/RhinoReceiver.class
+
tofile=target/samples/rhino/sample/rhino/RhinoReceiver.class/
+ant:copy file=${maven.repo.local}/rhino/jars/js-1.6R2.jar
tofile=target/samples/rhino/lib/js-1.6R2.jar/
+ant:copy file=${maven.repo.local}/xmlbeans/jars/xbean-2.0.0.jar
tofile=target/samples/rhino/lib/xbean-2.0.0.jar/
+jar destfile=${samples.dir}/rhinoService.aar
+fileset dir=target/samples/rhino
+/fileset
+fileset dir=src/sample/rhino/
+include name=META-INF/**/
+/fileset
+/jar
+/goal
+
+!-- --
!--- Security Sample --
!-- --
goal name=securitySample
Index: project.xml
===
--- project.xml (revision 355804)
+++ project.xml (working copy)
@@ -211,6 +211,14 @@
moduletrue/module
/properties
/dependency
+dependency
+groupIdrhino/groupId
+artifactIdjs/artifactId
+version${rhino.version}/version
+properties
+moduletrue/module
+/properties
+/dependency
/dependencies
!-- build information for the project --
Index: src/sample/rhino/META-INF/services.xml
===
--- src/sample/rhino/META-INF/services.xml (revision 0)
+++ src/sample/rhino/META-INF/services.xml (revision 0)
@@ -0,0 +1,12 @@
+service name=RhinoService
+description
+This is Rhino service , what this really does is take the incoming
SOAP message
+and hand that over to a Rhino function which processes the message and
return a SOAP
+message back to MessageReceiver
+/description
+parameter name=JavaScriptSource
locked=falsesample/rhino/rhino-sample.js/parameter
+
+operation name=hello
+messageReceiver class=sample.rhino.RhinoReceiver/
+/operation
+/service
\ No newline at end of file
Property changes on: src/sample/rhino/META-INF/services.xml
___
Name: svn:keywords
+ Id
Name: svn:eol-style
+ native
Index: src/sample/rhino/RhinoReceiver.java
===
--- src/sample/rhino/RhinoReceiver.java (revision 0)
+++ src/sample/rhino/RhinoReceiver.java (revision 0)
@@ -0,0 +1,160 @@
+/*
+ * Copyright 2004,2005 The Apache Software Foundation.
+ *
+ * Licensed under the Apache License, Version 2.0 (the License);
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an AS IS BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+package sample.rhino;
+
+import java.io.ByteArrayInputStream;
+import java.io.IOException;
+import java.io.InputStream;
+import java.io.InputStreamReader;
+import java.io.StringWriter;
+
+import javax.xml.stream.XMLInputFactory;
+import javax.xml.stream.XMLStreamException;
+import
Re: [Axis2] Maven module for DOOM
What's the relationship between the DOOM code and the SAAJ code? Do we have two different DOM implementations over OM now? No .. the SAAJ code was incomplete and now we have to go back and build SAAJ over DOOM. OK, that's cool then. --Glen
[jira] Created: (AXIS-2340) BeanDeserializer cannot deserialize the array in the complex type
BeanDeserializer cannot deserialize the array in the complex type -- Key: AXIS-2340 URL: http://issues.apache.org/jira/browse/AXIS-2340 Project: Apache Axis Type: Bug Components: Basic Architecture Versions: 1.3 Reporter: Dmytro Dyachuk Priority: Blocker The problem is the BeanSerializer throws an exception during deserializing the SOAP response on the clients stub. It seems that it tries to cast to some type [J which is definately is not long. The soap message is: ?xml version=1.0 encoding=utf-8? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; soapenv:Body ns1:createOrderResponse soapenv:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; xmlns:ns1=http://tpcapp.kvn.usask.ca; createOrderReturn href=#id0/ /ns1:createOrderResponse multiRef id=id0 soapenc:root=0 soapenv:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; xsi:type=ns2:CreateOrderResponse xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/; xmlns:ns2=structs.kvn.usask.ca systemId xsi:type=xsd:string xsi:nil=true/ orderId xsi:type=xsd:long740488771/orderId orderStatus xsi:type=xsd:stringPENDING/orderStatus orederTotal xsi:type=xsd:double72875.404390735/orederTotal orderTax xsi:type=xsd:double12442.961820735/orderTax orderShipCost xsi:type=xsd:double28154.98/orderShipCost discount xsi:type=xsd:double42.34/discount itemId xsi:type=xsd:long7838/itemId itemId xsi:type=xsd:long78844/itemId itemId xsi:type=xsd:long50151/itemId itemId xsi:type=xsd:long80088/itemId itemId xsi:type=xsd:long88702/itemId itemId xsi:type=xsd:long64908/itemId itemQty xsi:type=xsd:long2/itemQty itemQty xsi:type=xsd:long6/itemQty itemQty xsi:type=xsd:long6/itemQty itemQty xsi:type=xsd:long1/itemQty itemQty xsi:type=xsd:long7/itemQty itemQty xsi:type=xsd:long4/itemQty itemCost xsi:type=xsd:double455.28/itemCost itemCost xsi:type=xsd:double1935.29/itemCost itemCost xsi:type=xsd:double3383.91/itemCost itemCost xsi:type=xsd:double98.62/itemCost itemCost xsi:type=xsd:double2256.43/itemCost itemCost xsi:type=xsd:double1814.89/itemCost itemStatus xsi:type=xsd:stringPENDING/itemStatus itemStatus xsi:type=xsd:stringPENDING/itemStatus itemStatus xsi:type=xsd:stringPENDING/itemStatus itemStatus xsi:type=xsd:stringPENDING/itemStatus itemStatus xsi:type=xsd:stringPENDING/itemStatus itemStatus xsi:type=xsd:stringPENDING/itemStatus /multiRef /soapenv:Body /soapenv:Envelope The exception: - Could not convert java.lang.Long to bean field 'itemId', type [J - Exception: java.lang.IllegalArgumentException: argument type mismatch at org.apache.axis.encoding.ser.BeanPropertyTarget.set(BeanPropertyTarget.java:157) at org.apache.axis.encoding.DeserializerImpl.valueComplete(DeserializerImpl.java:249) at org.apache.axis.encoding.DeserializerImpl.endElement(DeserializerImpl.java:509) at org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087) at org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.java:171) at org.apache.axis.message.MessageElement.publishToHandler(MessageElement.java:1141) at org.apache.axis.encoding.DeserializerImpl.startElement(DeserializerImpl.java:369) at org.apache.axis.encoding.ser.BeanDeserializer.startElement(BeanDeserializer.java:154) at org.apache.axis.encoding.DeserializationContext.startElement(DeserializationContext.java:1048) at org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.java:165) at org.apache.axis.message.MessageElement.publishToHandler(MessageElement.java:1141) at org.apache.axis.message.RPCElement.deserialize(RPCElement.java:236) at org.apache.axis.message.RPCElement.getParams(RPCElement.java:384) at org.apache.axis.client.Call.invoke(Call.java:2467) at org.apache.axis.client.Call.invoke(Call.java:2366) at org.apache.axis.client.Call.invoke(Call.java:1812) at ca.usask.kvn.tpcapp.client.axis.BookStoreService.BookStoreServiceSoapBindingStub.createOrder(BookStoreServiceSoapBindingStub.java:603) at ca.usask.kvn.tpcapp.client.BookstoreClient.createNewOrder(BookstoreClient.java:135) at ca.usask.kvn.tpcapp.client.ClientSuite.main(ClientSuite.java:55) The code of the generated stub: /** * CreateOrderResponse.java * * This file was
Re: [axis2][SampleCompetition] Rhino sample
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Sylvian,
We are happy to announce you as the winner of WSO2 samples competition
held during ApacheCon US 2005. And you will be the fortunate winner of
a brand new nano pod for your valuable contribution to Axis2.
We hope to see your contributions in the future as well.
Chinthaka
Sylvain Wallez wrote:
Hi there!
Stimulated by the hope of winning a shiny Nano, I started
hacking a
sample integrating Rhino and Axis2. I know Rhino quite well as
Cocoon is using it extensively, but I'm a total newbie when it
comes to Axis2. So I wrote the sample, but failed to run a test
to
see if it actually works.
So please find attached the patch against modules/samples with
what
I've been up to, in the hope that it can be useful and that you
guys can spend a bit of time to check if it works.
Thanks, Sylvain
PS: I started to use Axiom for what could become a StAX-based
Cocoon. Nice stuff, although I found little things that I'm
missing. Working around for now, but expect some patches in the
near future :-)
--
Index: maven.xml
===
--- maven.xml (revision 355804) +++ maven.xml (working copy) @@
-258,6 +258,26 @@ /goal
!--
-- + !--- Rhino Service Sample -- + !--
-- + + goal name="rhino" + mkdir
dir="target/samples"/ + ant:copy
file="./src/sample/rhino/rhino-sample.js"
tofile="target/samples/rhino/sample/rhino/rhino-sample.js"/ +
ant:copy
file="target/classes/sample/rhino/RhinoReceiver.class" +
tofile="target/samples/rhino/sample/rhino/RhinoReceiver.class"/ +
ant:copy file="${maven.repo.local}/rhino/jars/js-1.6R2.jar"
tofile="target/samples/rhino/lib/js-1.6R2.jar"/ +
ant:copy
file="${maven.repo.local}/xmlbeans/jars/xbean-2.0.0.jar"
tofile="target/samples/rhino/lib/xbean-2.0.0.jar"/ + jar
destfile="${samples.dir}/rhinoService.aar" + fileset
dir="target/samples/rhino" + /fileset +
fileset dir="src/sample/rhino/" + include
name="META-INF/**"/ + /fileset + /jar +
/goal + + !--
-- !--- Security Sample -- !--
-- goal name="securitySample" Index: project.xml
===
--- project.xml (revision 355804) +++ project.xml (working copy)
@@ -211,6 +211,14 @@ moduletrue/module
/properties
/dependency + dependency +
groupIdrhino/groupId +
artifactIdjs/artifactId +
version${rhino.version}/version +
properties +
moduletrue/module + /properties +
/dependency /dependencies
!-- build information for the project -- Index:
src/sample/rhino/META-INF/services.xml
===
--- src/sample/rhino/META-INF/services.xml (revision 0) +++
src/sample/rhino/META-INF/services.xml (revision 0) @@ -0,0 +1,12
@@ +service name="RhinoService" + description +
This
is Rhino service , what this really does is take the incoming
SOAP
message + and hand that over to a Rhino function which
processes the message and return a SOAP + message back to
MessageReceiver + /description + parameter
name="_javascript_Source"
locked="false"sample/rhino/rhino-sample.js/parameter
+ +
operation name="hello" + messageReceiver
class="sample.rhino.RhinoReceiver"/ + /operation
+/service
\ No newline at end of file
Property changes on: src/sample/rhino/META-INF/services.xml
___
Name: svn:keywords + Id Name: svn:eol-style + native
Index: src/sample/rhino/RhinoReceiver.java
===
--- src/sample/rhino/RhinoReceiver.java (revision 0) +++
src/sample/rhino/RhinoReceiver.java (revision 0) @@ -0,0 +1,160
@@
+/* + * Copyright 2004,2005 The Apache Software Foundation. + *
+ *
Licensed under the Apache License, Version 2.0 (the "License");
+ *
you may not use this file except in compliance with the License.
+
* You may obtain a copy of the License at + * + *
http://www.apache.org/licenses/LICENSE-2.0 + * + * Unless
required
by applicable law or agreed to in writing, software + *
distributed
under the License is distributed on an "AS IS" BASIS, + * WITHOUT
WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+
* See the License for the specific language governing permissions
and + * limitations under the License. + */ + +package
sample.rhino; + +import java.io.ByteArrayInputStream; +import
java.io.IOException; +import java.io.InputStream; +import
java.io.InputStreamReader; +import java.io.StringWriter; +
+import
javax.xml.stream.XMLInputFactory; +import
javax.xml.stream.XMLStreamException;
Re: [Axis2] Maven module for DOOM
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 +1 Ruchith Fernando wrote: Hi All, Right now DOOM is in saaj maven module and therefore the security maven module has a dependency on saaj [1]. And anyone else who'd want to use DOOM will have to use axis2-saaj-##.jar Shall we move the DOOM code from saaj to a new maven module? Thanks, Ruchith [1] http://marc.theaimsgroup.com/?l=axis-devm=113453731208858w=2 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (MingW32) iD8DBQFDoOfIjON2uBzUhh8RAiifAJ49i1GBfIsbNjiwPeXY1LulDrNKigCgjHLB BKzs9+Qysii10IdzTuojRgI= =gKC3 -END PGP SIGNATURE-
Unsubcription
Hi Please unsubcribe me becouse by a mistake I registered here.kind regards thilina Yahoo! Shopping Find Great Deals on Holiday Gifts at Yahoo! Shopping
[Axis2] Possible bug in the AxisEngine.resume() method
Hi All,
There seems to be a bug in the AxisEngine.resume() method (which was recently added)
Wihtin this, only the currently attached execution chain is resumed.
But AxisEngine.send() method attachs two execution chains
(service specific and global) and invoke both. Because of this if
pausing happen in a service specific out handler, the global out
handlers are ommitted when resuming. Also resume mothod does not seem
to be calling the MessageReceiver or TransportSender.
I have attached a fix to this. First doing two msgContext.invoke()
calls in the send() method will not work because when resuming we don't
know weather the first or second chain we were in when pausing. So I
combined both chains to a one ArrayList and invoked at once.
Also since we have to call the MessageReceiver or TransportSender after
the invocation of handlers (depending on weather we paused in the
send() method or receive() method) it seems better to have two resume
methods named resumeSend() and resumeReceive() which will call
TransportSender and MessageReceiver respectively (after invoking the
execution chain).
Please see the attached patch.
Thank you,
Chamikara
Index: engine/AxisEngine.java
===
--- engine/AxisEngine.java (revision 356796)
+++ engine/AxisEngine.java (working copy)
@@ -66,12 +66,13 @@
public void send(MessageContext msgContext) throws AxisFault {
//find and invoke the Phases
OperationContext operationContext = msgContext.getOperationContext();
-ArrayList executionChain = operationContext.getAxisOperation().getPhasesOutFlow();
-msgContext.setExecutionChain((ArrayList) executionChain.clone());
+ArrayList outFlow = (ArrayList) operationContext.getAxisOperation().getPhasesOutFlow().clone();
+ArrayList globalOutFlow = (ArrayList) msgContext.getConfigurationContext().getAxisConfiguration().getGlobalOutPhases().clone();
+
+outFlow.addAll(globalOutFlow);
+
+msgContext.setExecutionChain(outFlow);
msgContext.invoke();
-msgContext.setExecutionChain((ArrayList)msgContext.getConfigurationContext().
-getAxisConfiguration().getGlobalOutPhases().clone());
-msgContext.invoke();
if (!msgContext.isPaused()) {
//write the Message to the Wire
@@ -385,10 +386,29 @@
}
-public void resume(MessageContext msgctx)
+public void resumeSend(MessageContext msgctx)
throws AxisFault {
msgctx.resume();
+
+if (!msgctx.isPaused()) {
+//write the Message to the Wire
+TransportOutDescription transportOut = msgctx.getTransportOut();
+TransportSender sender = transportOut.getSender();
+sender.invoke(msgctx);
+}
}
+
+public void resumeReceive(MessageContext msgctx)
+ throws AxisFault {
+ msgctx.resume();
+
+if (msgctx.isServerSide() !msgctx.isPaused()) {
+// invoke the Message Receivers
+checkMustUnderstand(msgctx);
+MessageReceiver receiver = msgctx.getAxisOperation().getMessageReceiver();
+receiver.receive(msgctx);
+}
+}
private String getSenderFaultCode(String soapNamespace) {
return SOAP12Constants.SOAP_ENVELOPE_NAMESPACE_URI.equals(
