[jira] Commented: (AXIS2-2325) Java2WSDL does not generate faults correctly
[ https://issues.apache.org/jira/browse/AXIS2-2325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12492551 ] Manoj Khangaonkar commented on AXIS2-2325: -- Jorge, The inhertiance ( hierarchy ) patch was probably committed in 1.2 Mj Java2WSDL does not generate faults correctly Key: AXIS2-2325 URL: https://issues.apache.org/jira/browse/AXIS2-2325 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: codegen Affects Versions: 1.1.1 Environment: Windows XP Java 1.5, Eclipse 3.2.2, Axis2 Eclipse Plugin 1.2.1 Reporter: Jorge Fernández Assigned To: Deepal Jayasinghe Attachments: API.java, API.java, API.wsdl, API.wsdl, API.wsdl, API.wsdl, axis2-2325patch.txt, DataAccessFault.java, IncorrectPasswordFault.java, IncorrectUserFault.java, ValidationFault.java The first problem is that in the WSDL generated my fault name is ignored and instead it's compound from the operation name and Fault. Also if I throw two exceptions from one operation, in the WSDL only one appears and with the name I said before. I attach the API from where I build the WSDL, the Faults classes and the WSDL generated. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2239) java2WSDL does not generate nillable = true
[ https://issues.apache.org/jira/browse/AXIS2-2239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491748 ] Manoj Khangaonkar commented on AXIS2-2239: -- I understand the problem now. An incorrect nillable=true is generated when a primitive is a method parameter. This is a separate defect. Please open another JIRA issue - I will provide a patch. Mj java2WSDL does not generate nillable = true --- Key: AXIS2-2239 URL: https://issues.apache.org/jira/browse/AXIS2-2239 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: codegen Affects Versions: 1.1.1 Environment: Windows XP SP2, Eclipse 3.2.1, Axis2_Codegen_Wizard_1.2.1, java 1.5.0 update 9 Reporter: Jorge Fernández Attachments: API.java, axis2-2239patch.txt, Configuration.java, example.wsdl When I generate wsdl from Java classes, sometimes, the codegen plugin doesn't generate correctly the nillable=true attribute. API.java is the service interface. Configuration is the type returned by the operation in the API and example.wsdl is the wsdl generated by the plugin. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2239) java2WSDL does not generate nillable = true
[ https://issues.apache.org/jira/browse/AXIS2-2239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491474 ] Manoj Khangaonkar commented on AXIS2-2239: -- Eugene, The patch will make only non-primitive fields nillable. Not sure how the attached WSDL was created. perhaps it was edited. Mj java2WSDL does not generate nillable = true --- Key: AXIS2-2239 URL: https://issues.apache.org/jira/browse/AXIS2-2239 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: codegen Affects Versions: 1.1.1 Environment: Windows XP SP2, Eclipse 3.2.1, Axis2_Codegen_Wizard_1.2.1, java 1.5.0 update 9 Reporter: Jorge Fernández Attachments: API.java, axis2-2239patch.txt, Configuration.java, example.wsdl When I generate wsdl from Java classes, sometimes, the codegen plugin doesn't generate correctly the nillable=true attribute. API.java is the service interface. Configuration is the type returned by the operation in the API and example.wsdl is the wsdl generated by the plugin. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-2325) Java2WSDL does not generate faults correctly
[ https://issues.apache.org/jira/browse/AXIS2-2325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manoj Khangaonkar updated AXIS2-2325: - Attachment: axis2-2325patch.txt Patch to fix this issue Java2WSDL does not generate faults correctly Key: AXIS2-2325 URL: https://issues.apache.org/jira/browse/AXIS2-2325 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: codegen Affects Versions: 1.1.1 Environment: Windows XP Java 1.5, Eclipse 3.2.2, Axis2 Eclipse Plugin 1.2.1 Reporter: Jorge Fernández Assigned To: Deepal Jayasinghe Attachments: API.java, API.wsdl, API.wsdl, axis2-2325patch.txt, IncorrectPasswordFault.java, IncorrectUserFault.java The first problem is that in the WSDL generated my fault name is ignored and instead it's compound from the operation name and Fault. Also if I throw two exceptions from one operation, in the WSDL only one appears and with the name I said before. I attach the API from where I build the WSDL, the Faults classes and the WSDL generated. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2325) Java2WSDL does not generate faults correctly
[ https://issues.apache.org/jira/browse/AXIS2-2325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12490648 ] Manoj Khangaonkar commented on AXIS2-2325: -- The attached patch takes care of the following : 1. generates multiple fault when necessary 2. generates messages and bindings for the faults 3. Name of fault is type name of the exception 4. AXISFault is shown in the inheritance heirarchy - filter it out - just as we do for java.lang.Object. Jorge, You'll need to add get/set method to exception - to get the necessary elements in the type definetion of the fault Java2WSDL does not generate faults correctly Key: AXIS2-2325 URL: https://issues.apache.org/jira/browse/AXIS2-2325 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: codegen Affects Versions: 1.1.1 Environment: Windows XP Java 1.5, Eclipse 3.2.2, Axis2 Eclipse Plugin 1.2.1 Reporter: Jorge Fernández Assigned To: Deepal Jayasinghe Attachments: API.java, API.wsdl, API.wsdl, axis2-2325patch.txt, IncorrectPasswordFault.java, IncorrectUserFault.java The first problem is that in the WSDL generated my fault name is ignored and instead it's compound from the operation name and Fault. Also if I throw two exceptions from one operation, in the WSDL only one appears and with the name I said before. I attach the API from where I build the WSDL, the Faults classes and the WSDL generated. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-2325) Java2WSDL does not generate faults correctly
[ https://issues.apache.org/jira/browse/AXIS2-2325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manoj Khangaonkar updated AXIS2-2325: - Attachment: API.wsdl API.wsdl generated by using the patch Java2WSDL does not generate faults correctly Key: AXIS2-2325 URL: https://issues.apache.org/jira/browse/AXIS2-2325 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: codegen Affects Versions: 1.1.1 Environment: Windows XP Java 1.5, Eclipse 3.2.2, Axis2 Eclipse Plugin 1.2.1 Reporter: Jorge Fernández Assigned To: Deepal Jayasinghe Attachments: API.java, API.wsdl, API.wsdl, API.wsdl, axis2-2325patch.txt, IncorrectPasswordFault.java, IncorrectUserFault.java The first problem is that in the WSDL generated my fault name is ignored and instead it's compound from the operation name and Fault. Also if I throw two exceptions from one operation, in the WSDL only one appears and with the name I said before. I attach the API from where I build the WSDL, the Faults classes and the WSDL generated. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2564) Wrong type mapping for java.lang.Long
[
https://issues.apache.org/jira/browse/AXIS2-2564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12490652
]
Manoj Khangaonkar commented on AXIS2-2564:
--
Hi,
This issue will be fixed by the patch provided for AXIS2-2239
Mj
Wrong type mapping for java.lang.Long
-
Key: AXIS2-2564
URL: https://issues.apache.org/jira/browse/AXIS2-2564
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: codegen
Reporter: Eugeniy Nizhinskiy
Priority: Critical
1. Wrong java2wsdl mapping occurs when try to use java.lang.Long types in web
service.
java.lang.Long mappes to long instead of nilable long.
2. Problem with complex types. If we use long (not java.lang.Long) as in/out
parameter in web service methods java2wsdl mappes it as nilable. But if we
use in/out complex type with long field we will get not nilable in wsdl.
Example:
From the following classes java2wsdl generates wrong WSDL.
[BatchManagerService.java]
package x;
public class BatchManagerService {
public x.Person getPerson(java.lang.Long personINTN)
{
return null;
};
public x.Person getPersonSimple(long personSIMPLEINTN)
{
return null;
};
}
[Person.java]
package x;
public class Person {
public java.lang.Long getLong(){return null;};
public long getSimpleLong(){return 0;};
}
xs:element name=getPerson
xs:complexType
xs:sequence
xs:element name=personINTN nillable=true type=xs:long /
/xs:sequence
/xs:complexType
/xs:element
xs:element name=getPersonResponse
xs:complexType
xs:sequence
xs:element name=return nillable=true type=ns:Person /
/xs:sequence
/xs:complexType
/xs:element
xs:element name=Person type=ns:Person /
xs:complexType name=Person
xs:sequence
xs:element name=long type=xs:long /
xs:element name=simpleLong type=xs:long /
/xs:sequence
/xs:complexType
xs:element name=getPersonSimple
xs:complexType
xs:sequence
xs:element name=personSIMPLEINTN nillable=true type=xs:long /
/xs:sequence
/xs:complexType
/xs:element
xs:element name=getPersonSimpleResponse
xs:complexType
xs:sequence
xs:element name=return nillable=true type=ns:Person /
/xs:sequence
/xs:complexType
/xs:element
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-1891) the generated wsdl won't describe our custom exception
[ https://issues.apache.org/jira/browse/AXIS2-1891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12490653 ] Manoj Khangaonkar commented on AXIS2-1891: -- Hi, Please take a look at the discussion and patch for AXIS2-2325. It might be addressing or fixing this issue. Mj the generated wsdl won't describe our custom exception -- Key: AXIS2-1891 URL: https://issues.apache.org/jira/browse/AXIS2-1891 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: codegen Affects Versions: 1.1 Environment: linux, jdk5, jboss4 Reporter: Francois Le Droff Assigned To: Deepal Jayasinghe Attachments: proto-axis2.zip Hello there, we're currenltly working on a ws benchmark, so far, in ourstudy, we short-listed axis2 (wso2) and jboss-ws. Unfortunately, we currently have a big issue with axis2, and it's really crippling for the rest of our study. it looks like the wsdl generated by axis2 can't/won't take into account the business exception (proto.axis2.exceptions.MonException ) we described in our POJO Service signature (in proto.axis2.Service : public OVComplexe[] myServiceSynchroneCustomEX(OVComplexe[] args) throws RemoteException, MonException; ) I will attach our axis2-related project source and build files in a zip named axis2-prototype you may try it, by launching our ant build in /axis2-prototype/MyServiceSynchrone/axis2/ don't forget to setup your environment properties in /axis2-prototype/buid.properties Thanks for your help ! Cheers ! François Le Droff -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2325) Java2WSDL does not generate faults correctly
[ https://issues.apache.org/jira/browse/AXIS2-2325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489582 ] Manoj Khangaonkar commented on AXIS2-2325: -- Jorge, In your attached API.wsdl , the definition of the fault is xs:element name=validateUserFault xs:complexType xs:sequence xs:element name=validateUserFault type=xs:anyType/ /xs:sequence /xs:complexType /xs:element Of special interest is xs:anyType. What java2WSDL options did you use to generate this ? For me it generates something like xs:element name=validateUserFault xs:complexType xs:sequence /xs:sequence /xs:complexType /xs:element Since the exception has no public members or get/set methods - I can understand what was generated for me ? What option / editing was used to add the xs;anyType to the WSDL ? Mj Java2WSDL does not generate faults correctly Key: AXIS2-2325 URL: https://issues.apache.org/jira/browse/AXIS2-2325 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: codegen Affects Versions: 1.1.1 Environment: Windows XP Java 1.5, Eclipse 3.2.2, Axis2 Eclipse Plugin 1.2.1 Reporter: Jorge Fernández Assigned To: Deepal Jayasinghe Attachments: API.java, API.wsdl, IncorrectPasswordFault.java, IncorrectUserFault.java The first problem is that in the WSDL generated my fault name is ignored and instead it's compound from the operation name and Fault. Also if I throw two exceptions from one operation, in the WSDL only one appears and with the name I said before. I attach the API from where I build the WSDL, the Faults classes and the WSDL generated. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2325) Java2WSDL does not generate faults correctly
[ https://issues.apache.org/jira/browse/AXIS2-2325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488788 ] Manoj Khangaonkar commented on AXIS2-2325: -- Hi, The things I think we need to fix are (1) WSDL does allow multiple fault messages. If a method declared multiple exception, there needs to 1 fault for each exception. (2) Need to generate messages for each fault (3) The binding section needs an fault element for each fault (4) generating faultname = operation name + Fault is not necessary , you can use the exception type name. In any case this does not work for multiple faults. (5) types section - Generate the type definition for each fault correctly. Since exception generally extend java.lang.Exception or other exception classes, we have to be careful here Will look into providing a patch Mj Java2WSDL does not generate faults correctly Key: AXIS2-2325 URL: https://issues.apache.org/jira/browse/AXIS2-2325 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: codegen Affects Versions: 1.1.1 Environment: Windows XP Java 1.5, Eclipse 3.2.2, Axis2 Eclipse Plugin 1.2.1 Reporter: Jorge Fernández Assigned To: Deepal Jayasinghe Priority: Minor Attachments: API.java, API.wsdl, IncorrectPasswordFault.java, IncorrectUserFault.java The first problem is that in the WSDL generated my fault name is ignored and instead it's compound from the operation name and Fault. Also if I throw two exceptions from one operation, in the WSDL only one appears and with the name I said before. I attach the API from where I build the WSDL, the Faults classes and the WSDL generated. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2325) Java2WSDL does not generate faults correctly
[ https://issues.apache.org/jira/browse/AXIS2-2325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488789 ] Manoj Khangaonkar commented on AXIS2-2325: -- Hi, This seems to be a pretty serious limitation. Perhaps we should raise the priority to Major Mj Java2WSDL does not generate faults correctly Key: AXIS2-2325 URL: https://issues.apache.org/jira/browse/AXIS2-2325 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: codegen Affects Versions: 1.1.1 Environment: Windows XP Java 1.5, Eclipse 3.2.2, Axis2 Eclipse Plugin 1.2.1 Reporter: Jorge Fernández Assigned To: Deepal Jayasinghe Priority: Minor Attachments: API.java, API.wsdl, IncorrectPasswordFault.java, IncorrectUserFault.java The first problem is that in the WSDL generated my fault name is ignored and instead it's compound from the operation name and Fault. Also if I throw two exceptions from one operation, in the WSDL only one appears and with the name I said before. I attach the API from where I build the WSDL, the Faults classes and the WSDL generated. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-2239) java2WSDL does not generate nillable = true
[ https://issues.apache.org/jira/browse/AXIS2-2239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manoj Khangaonkar updated AXIS2-2239: - Attachment: axis2-2239patch.txt Attached patch to fix this issue java2WSDL does not generate nillable = true --- Key: AXIS2-2239 URL: https://issues.apache.org/jira/browse/AXIS2-2239 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: codegen Affects Versions: 1.1.1 Environment: Windows XP SP2, Eclipse 3.2.1, Axis2_Codegen_Wizard_1.2.1, java 1.5.0 update 9 Reporter: Jorge Fernández Attachments: API.java, axis2-2239patch.txt, Configuration.java, example.wsdl When I generate wsdl from Java classes, sometimes, the codegen plugin doesn't generate correctly the nillable=true attribute. API.java is the service interface. Configuration is the type returned by the operation in the API and example.wsdl is the wsdl generated by the plugin. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2116) java2WSDL should generate schema elements for public fields
[
https://issues.apache.org/jira/browse/AXIS2-2116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481895
]
Manoj Khangaonkar commented on AXIS2-2116:
--
Hi,
I will provide a patch against latest svn - In any case I need to update the
patch based on a comment from 1749.
How this patch was created on march 1. Since march 1 , there have been 2
checkins to the same file , but it changes different parts of the file.
So I am not seeing any conflict --- by conflict I am thinking - two people
updating the same lines of code differently.
In any case I will merge with latest one more time.
Manoj
java2WSDL should generate schema elements for public fields
---
Key: AXIS2-2116
URL: https://issues.apache.org/jira/browse/AXIS2-2116
Project: Axis 2.0 (Axis2)
Issue Type: Improvement
Components: wsdl
Affects Versions: 1.2, 1.1.1, nightly
Environment: ALL
Reporter: Manoj Khangaonkar
Attachments: axis2-1749and2116.txt, axis2patch1749and2116-v2.txt,
patch2116.txt
When java2WSDL generates schema for method parameters, it generates elements
only for properties - those that have get/set metthods.
If I have a class that has fields without get/set methods like
public class Book {
public String title ;
public String author ;
}
The complex type in types section of the WSDL is
xs:complexType name=Book
xs:sequence /
/xs:complexType
It should be
xs:complexType name=Book
xs:sequence
xs:element name=title nillable=true type=xs:string /
xs:element name=author nillable=true type=xs:string /
/xs;sequence
/xs:complexType
java2wsdl is typically used to generate WSDL for legacy code and it is not
reasonable to expect users to go add get/set methods to legacy code
just because they need to generate WSDL
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-2116) java2WSDL should generate schema elements for public fields
[
https://issues.apache.org/jira/browse/AXIS2-2116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manoj Khangaonkar updated AXIS2-2116:
-
Attachment: axis2patch1749and2116-v3.txt
Dims,
Attached a updated patch for the latest revision.
WOuld appreciate if we can commit before someone changes the code again.
Manoj
java2WSDL should generate schema elements for public fields
---
Key: AXIS2-2116
URL: https://issues.apache.org/jira/browse/AXIS2-2116
Project: Axis 2.0 (Axis2)
Issue Type: Improvement
Components: wsdl
Affects Versions: 1.2, 1.1.1, nightly
Environment: ALL
Reporter: Manoj Khangaonkar
Attachments: axis2-1749and2116.txt, axis2patch1749and2116-v2.txt,
axis2patch1749and2116-v3.txt, patch2116.txt
When java2WSDL generates schema for method parameters, it generates elements
only for properties - those that have get/set metthods.
If I have a class that has fields without get/set methods like
public class Book {
public String title ;
public String author ;
}
The complex type in types section of the WSDL is
xs:complexType name=Book
xs:sequence /
/xs:complexType
It should be
xs:complexType name=Book
xs:sequence
xs:element name=title nillable=true type=xs:string /
xs:element name=author nillable=true type=xs:string /
/xs;sequence
/xs:complexType
java2wsdl is typically used to generate WSDL for legacy code and it is not
reasonable to expect users to go add get/set methods to legacy code
just because they need to generate WSDL
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-1749) Wrong Java2WSDL generation
[
https://issues.apache.org/jira/browse/AXIS2-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manoj Khangaonkar updated AXIS2-1749:
-
Attachment: axis2patch1749and2116-v3.txt
Changed to ComplexExtension and updated the patch to latest SVN.
Wrong Java2WSDL generation
--
Key: AXIS2-1749
URL: https://issues.apache.org/jira/browse/AXIS2-1749
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: codegen
Affects Versions: 1.1
Reporter: Jabber W
Assigned To: Deepal Jayasinghe
Attachments: axis2-1749and2116.txt, axis2patch1749and2116-v2.txt,
axis2patch1749and2116-v3.txt, patch-1749.txt
During the generation of type definitions Java2WSDL of axis2-1.1 flattens
chains of extender java data types to independent schema types without
extending relations between them, while Axis121 stores these relations by
extension base.
For example: say,
class A { public String someString; public A someLink; } and
class B extends A { public int someInt; }
and the exposed service is:
class MySvc { String myOp(A arg) {..} }
Running of Java2WSDL on it:
java2wsdl -cn MySvc -xc B
creates 2 non-related types:
xs:complexType name=A
xs:sequence
xs:element name=someLink type=ns:A/
xs:element name=someString type=xs:string/
/xs:sequence
/xs:complexType
and
xs:complexType name=B
xs:sequence
xs:element name=someLink type=ns:A/
xs:element name=someString type=xs:string/
xs:element name=someInt type=xs:int/
/xs:sequence
/xs:complexType
while B should be:
xs:complexType name=B
xs:complexContent
xs:extension base=ns:A
xs:sequence
xs:element name=someInt type=xs:int/
/xs:sequence
/xs:extension
/xs:complexContent
/xs:complexType
Since complexType B is not extension of ? it (the B type element) can't be
passed as the someLink.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-1749) Wrong Java2WSDL generation
[
https://issues.apache.org/jira/browse/AXIS2-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481280
]
Manoj Khangaonkar commented on AXIS2-1749:
--
Gier,
I meant it to be ComplexExtension , but looks like I made it
ComplexRestriction. Good catch.
In java derived types extend base types - hence extension
Since this is java2WSDL - how do you model restriction in java ? In other
words, can you think of a case in java code
where the corresponding schema needs to be restriction.
I will update the patch to generate xs:extension base=
but if you have a use case for restriction, let me know
Mj
Wrong Java2WSDL generation
--
Key: AXIS2-1749
URL: https://issues.apache.org/jira/browse/AXIS2-1749
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: codegen
Affects Versions: 1.1
Reporter: Jabber W
Assigned To: Deepal Jayasinghe
Attachments: axis2-1749and2116.txt, axis2patch1749and2116-v2.txt,
patch-1749.txt
During the generation of type definitions Java2WSDL of axis2-1.1 flattens
chains of extender java data types to independent schema types without
extending relations between them, while Axis121 stores these relations by
extension base.
For example: say,
class A { public String someString; public A someLink; } and
class B extends A { public int someInt; }
and the exposed service is:
class MySvc { String myOp(A arg) {..} }
Running of Java2WSDL on it:
java2wsdl -cn MySvc -xc B
creates 2 non-related types:
xs:complexType name=A
xs:sequence
xs:element name=someLink type=ns:A/
xs:element name=someString type=xs:string/
/xs:sequence
/xs:complexType
and
xs:complexType name=B
xs:sequence
xs:element name=someLink type=ns:A/
xs:element name=someString type=xs:string/
xs:element name=someInt type=xs:int/
/xs:sequence
/xs:complexType
while B should be:
xs:complexType name=B
xs:complexContent
xs:extension base=ns:A
xs:sequence
xs:element name=someInt type=xs:int/
/xs:sequence
/xs:extension
/xs:complexContent
/xs:complexType
Since complexType B is not extension of ? it (the B type element) can't be
passed as the someLink.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2116) java2WSDL should generate schema elements for public fields
[
https://issues.apache.org/jira/browse/AXIS2-2116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12478266
]
Manoj Khangaonkar commented on AXIS2-2116:
--
Hi Deepal,
Can you please commit this patch ?
I would like to provide a patch for AXIS2-2239 and it affects the same code.
If I provide that patch on top of commited code - there is less chance of
confflicts later on.
Manoj
java2WSDL should generate schema elements for public fields
---
Key: AXIS2-2116
URL: https://issues.apache.org/jira/browse/AXIS2-2116
Project: Axis 2.0 (Axis2)
Issue Type: Improvement
Components: wsdl
Affects Versions: 1.2, 1.1.1, nightly
Environment: ALL
Reporter: Manoj Khangaonkar
Attachments: axis2-1749and2116.txt, axis2patch1749and2116-v2.txt,
patch2116.txt
When java2WSDL generates schema for method parameters, it generates elements
only for properties - those that have get/set metthods.
If I have a class that has fields without get/set methods like
public class Book {
public String title ;
public String author ;
}
The complex type in types section of the WSDL is
xs:complexType name=Book
xs:sequence /
/xs:complexType
It should be
xs:complexType name=Book
xs:sequence
xs:element name=title nillable=true type=xs:string /
xs:element name=author nillable=true type=xs:string /
/xs;sequence
/xs:complexType
java2wsdl is typically used to generate WSDL for legacy code and it is not
reasonable to expect users to go add get/set methods to legacy code
just because they need to generate WSDL
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-2116) java2WSDL should generate schema elements for public fields
[
https://issues.apache.org/jira/browse/AXIS2-2116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manoj Khangaonkar updated AXIS2-2116:
-
Attachment: axis2patch1749and2116-v2.txt
Hi Deepal,
Attached is a patch based on the latest source code in SVN.
The only conflicts I saw were calls to getSimpleName and getQualifiedName -
these are wrapper methods on JAM that were added.
There should be no conflicts now. If you still see a conflict, please show the
code that has a conflict so I can understand what the conflict is
Mj
java2WSDL should generate schema elements for public fields
---
Key: AXIS2-2116
URL: https://issues.apache.org/jira/browse/AXIS2-2116
Project: Axis 2.0 (Axis2)
Issue Type: Improvement
Components: wsdl
Affects Versions: 1.2, 1.1.1, nightly
Environment: ALL
Reporter: Manoj Khangaonkar
Attachments: axis2-1749and2116.txt, axis2patch1749and2116-v2.txt,
patch2116.txt
When java2WSDL generates schema for method parameters, it generates elements
only for properties - those that have get/set metthods.
If I have a class that has fields without get/set methods like
public class Book {
public String title ;
public String author ;
}
The complex type in types section of the WSDL is
xs:complexType name=Book
xs:sequence /
/xs:complexType
It should be
xs:complexType name=Book
xs:sequence
xs:element name=title nillable=true type=xs:string /
xs:element name=author nillable=true type=xs:string /
/xs;sequence
/xs:complexType
java2wsdl is typically used to generate WSDL for legacy code and it is not
reasonable to expect users to go add get/set methods to legacy code
just because they need to generate WSDL
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-1749) Wrong Java2WSDL generation
[
https://issues.apache.org/jira/browse/AXIS2-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manoj Khangaonkar updated AXIS2-1749:
-
Attachment: axis2patch1749and2116-v2.txt
Hi Deepal,
Attached is a patch based on the latest source code in SVN.
The only conflicts I saw were calls to getSimpleName and getQualifiedName -
these are wrapper methods on JAM that were added.
There should be no conflicts now. If you still see a conflict, please show the
code that has a conflict so I can understand what the conflict is
Mj
Wrong Java2WSDL generation
--
Key: AXIS2-1749
URL: https://issues.apache.org/jira/browse/AXIS2-1749
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: codegen
Affects Versions: 1.1
Reporter: Jabber W
Assigned To: Deepal Jayasinghe
Attachments: axis2-1749and2116.txt, axis2patch1749and2116-v2.txt,
patch-1749.txt
During the generation of type definitions Java2WSDL of axis2-1.1 flattens
chains of extender java data types to independent schema types without
extending relations between them, while Axis121 stores these relations by
extension base.
For example: say,
class A { public String someString; public A someLink; } and
class B extends A { public int someInt; }
and the exposed service is:
class MySvc { String myOp(A arg) {..} }
Running of Java2WSDL on it:
java2wsdl -cn MySvc -xc B
creates 2 non-related types:
xs:complexType name=A
xs:sequence
xs:element name=someLink type=ns:A/
xs:element name=someString type=xs:string/
/xs:sequence
/xs:complexType
and
xs:complexType name=B
xs:sequence
xs:element name=someLink type=ns:A/
xs:element name=someString type=xs:string/
xs:element name=someInt type=xs:int/
/xs:sequence
/xs:complexType
while B should be:
xs:complexType name=B
xs:complexContent
xs:extension base=ns:A
xs:sequence
xs:element name=someInt type=xs:int/
/xs:sequence
/xs:extension
/xs:complexContent
/xs:complexType
Since complexType B is not extension of ? it (the B type element) can't be
passed as the someLink.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2116) java2WSDL should generate schema elements for public fields
[
https://issues.apache.org/jira/browse/AXIS2-2116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476715
]
Manoj Khangaonkar commented on AXIS2-2116:
--
Hi Deepal,
To integrate 1749 with 2116, I ran into a small issue that required me to open
a bug on Annogen - org.codehaus.jam.
The bug is Annogen-21 - getDeclaredFields method of JClass returns fields of
base class as well - It should not. For 1749 - I need it
to return just the fields of the current class - not of all the base classes
I am writing a wrapper method to work around the issue - until there is a fix
from Annogen.
Manoj
java2WSDL should generate schema elements for public fields
---
Key: AXIS2-2116
URL: https://issues.apache.org/jira/browse/AXIS2-2116
Project: Axis 2.0 (Axis2)
Issue Type: Improvement
Components: wsdl
Affects Versions: 1.2, 1.1.1, nightly
Environment: ALL
Reporter: Manoj Khangaonkar
Attachments: patch2116.txt
When java2WSDL generates schema for method parameters, it generates elements
only for properties - those that have get/set metthods.
If I have a class that has fields without get/set methods like
public class Book {
public String title ;
public String author ;
}
The complex type in types section of the WSDL is
xs:complexType name=Book
xs:sequence /
/xs:complexType
It should be
xs:complexType name=Book
xs:sequence
xs:element name=title nillable=true type=xs:string /
xs:element name=author nillable=true type=xs:string /
/xs;sequence
/xs:complexType
java2wsdl is typically used to generate WSDL for legacy code and it is not
reasonable to expect users to go add get/set methods to legacy code
just because they need to generate WSDL
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-2116) java2WSDL should generate schema elements for public fields
[
https://issues.apache.org/jira/browse/AXIS2-2116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manoj Khangaonkar updated AXIS2-2116:
-
Attachment: axis2-1749and2116.txt
Attached a patch that include both 1749 and 2116
Manoj
java2WSDL should generate schema elements for public fields
---
Key: AXIS2-2116
URL: https://issues.apache.org/jira/browse/AXIS2-2116
Project: Axis 2.0 (Axis2)
Issue Type: Improvement
Components: wsdl
Affects Versions: 1.2, 1.1.1, nightly
Environment: ALL
Reporter: Manoj Khangaonkar
Attachments: axis2-1749and2116.txt, patch2116.txt
When java2WSDL generates schema for method parameters, it generates elements
only for properties - those that have get/set metthods.
If I have a class that has fields without get/set methods like
public class Book {
public String title ;
public String author ;
}
The complex type in types section of the WSDL is
xs:complexType name=Book
xs:sequence /
/xs:complexType
It should be
xs:complexType name=Book
xs:sequence
xs:element name=title nillable=true type=xs:string /
xs:element name=author nillable=true type=xs:string /
/xs;sequence
/xs:complexType
java2wsdl is typically used to generate WSDL for legacy code and it is not
reasonable to expect users to go add get/set methods to legacy code
just because they need to generate WSDL
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-1749) Wrong Java2WSDL generation
[
https://issues.apache.org/jira/browse/AXIS2-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manoj Khangaonkar updated AXIS2-1749:
-
Attachment: axis2-1749and2116.txt
Attached a patch that includes 1749 and 2116.
Manoj
Wrong Java2WSDL generation
--
Key: AXIS2-1749
URL: https://issues.apache.org/jira/browse/AXIS2-1749
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: codegen
Affects Versions: 1.1
Reporter: Jabber W
Assigned To: Deepal Jayasinghe
Attachments: axis2-1749and2116.txt, patch-1749.txt
During the generation of type definitions Java2WSDL of axis2-1.1 flattens
chains of extender java data types to independent schema types without
extending relations between them, while Axis121 stores these relations by
extension base.
For example: say,
class A { public String someString; public A someLink; } and
class B extends A { public int someInt; }
and the exposed service is:
class MySvc { String myOp(A arg) {..} }
Running of Java2WSDL on it:
java2wsdl -cn MySvc -xc B
creates 2 non-related types:
xs:complexType name=A
xs:sequence
xs:element name=someLink type=ns:A/
xs:element name=someString type=xs:string/
/xs:sequence
/xs:complexType
and
xs:complexType name=B
xs:sequence
xs:element name=someLink type=ns:A/
xs:element name=someString type=xs:string/
xs:element name=someInt type=xs:int/
/xs:sequence
/xs:complexType
while B should be:
xs:complexType name=B
xs:complexContent
xs:extension base=ns:A
xs:sequence
xs:element name=someInt type=xs:int/
/xs:sequence
/xs:extension
/xs:complexContent
/xs:complexType
Since complexType B is not extension of ? it (the B type element) can't be
passed as the someLink.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2239) java2WSDL does not generate nillable = true
[ https://issues.apache.org/jira/browse/AXIS2-2239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476843 ] Manoj Khangaonkar commented on AXIS2-2239: -- Hi, Working on this. Will provide a patch shortly. Anything that is not a primitive should be nillable. Manoj java2WSDL does not generate nillable = true --- Key: AXIS2-2239 URL: https://issues.apache.org/jira/browse/AXIS2-2239 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: codegen Affects Versions: 1.1.1 Environment: Windows XP SP2, Eclipse 3.2.1, Axis2_Codegen_Wizard_1.2.1, java 1.5.0 update 9 Reporter: Jorge Fernández Attachments: API.java, Configuration.java, example.wsdl When I generate wsdl from Java classes, sometimes, the codegen plugin doesn't generate correctly the nillable=true attribute. API.java is the service interface. Configuration is the type returned by the operation in the API and example.wsdl is the wsdl generated by the plugin. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2116) java2WSDL should generate schema elements for public fields
[
https://issues.apache.org/jira/browse/AXIS2-2116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476304
]
Manoj Khangaonkar commented on AXIS2-2116:
--
Hi Deepal,
Did not notice your comments earlier.
I'll create a combined patch in the next couple of days.
In case I miss the code freeze -- the patch for 1749 can go in on its own - it
will fit in with the existing code.
Manoj
java2WSDL should generate schema elements for public fields
---
Key: AXIS2-2116
URL: https://issues.apache.org/jira/browse/AXIS2-2116
Project: Axis 2.0 (Axis2)
Issue Type: Improvement
Components: wsdl
Affects Versions: 1.2, 1.1.1, nightly
Environment: ALL
Reporter: Manoj Khangaonkar
Attachments: patch2116.txt
When java2WSDL generates schema for method parameters, it generates elements
only for properties - those that have get/set metthods.
If I have a class that has fields without get/set methods like
public class Book {
public String title ;
public String author ;
}
The complex type in types section of the WSDL is
xs:complexType name=Book
xs:sequence /
/xs:complexType
It should be
xs:complexType name=Book
xs:sequence
xs:element name=title nillable=true type=xs:string /
xs:element name=author nillable=true type=xs:string /
/xs;sequence
/xs:complexType
java2wsdl is typically used to generate WSDL for legacy code and it is not
reasonable to expect users to go add get/set methods to legacy code
just because they need to generate WSDL
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2165) Build errors in kernel
[ https://issues.apache.org/jira/browse/AXIS2-2165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12472719 ] Manoj Khangaonkar commented on AXIS2-2165: -- Keith, When you say it was fixed some time ago - Are you saying it was fixed somewhere else - in another branch or your local code but not comitted to the main branch ? Because the main branch did not build yesterday. I suppose the code is merged into trunck now Mj Build errors in kernel -- Key: AXIS2-2165 URL: https://issues.apache.org/jira/browse/AXIS2-2165 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: kernel Affects Versions: 1.2, nightly Environment: Windows Reporter: Manoj Khangaonkar Priority: Blocker Attachments: patch-2165.txt There have been some changes in woden and AXIS2 code is not current w.r.t woden The errors are : java:compile: [echo] Compiling to C:\axis2\modules\kernel/target/classes [javac] Compiling 184 source files to C:\axis2\modules\kernel\target\classes [javac] C:\axis2\modules\kernel\src\org\apache\axis2\description\WSDL20ToAxi sServiceBuilder.java:436: cannot find symbol [javac] symbol : method getHttpTransferCodingDefault() [javac] location: class org.apache.woden.internal.wsdl20.extensions.soap.SOA PBindingExtensionsImpl [javac] soapBindingExtensions.getHttpTransferCodingDefault() ); [javac] ^ [javac] C:\axis2\modules\kernel\src\org\apache\axis2\description\WSDL20ToAxi sServiceBuilder.java:465: cannot find symbol [javac] symbol : method getHttpTransferCoding() [javac] location: interface org.apache.woden.wsdl20.extensions.soap.SOAPBind ingFaultExtensions [javac] soapBindingFaultExtensions.getHttpTransferCoding ()); [javac] ^ [javac] C:\axis2\modules\kernel\src\org\apache\axis2\description\WSDL20ToAxi sServiceBuilder.java:528: cannot find symbol [javac] symbol : method getHttpTransferCodingDefault() [javac] location: interface org.apache.woden.wsdl20.extensions.soap.SOAPBind ingOperationExtensions [javac] soapBindingOperationExtensions.getHttpTransferCo dingDefault()); [javac] ^ [javac] C:\axis2\modules\kernel\src\org\apache\axis2\description\WSDL20ToAxi sServiceBuilder.java:562: cannot find symbol [javac] symbol : method getHttpTransferCoding() [javac] location: interface org.apache.woden.wsdl20.extensions.soap.SOAPBind ingMessageReferenceExtensions [javac] soapBindingMessageReferenceExtensions.getHtt pTransferCoding()); [javac] ^ [javac] C:\axis2\modules\kernel\src\org\apache\axis2\description\WSDL20ToAxi sServiceBuilder.java:622: cannot find symbol [javac] symbol : method getHttpTransferCodingDefault() [javac] location: class org.apache.woden.internal.wsdl20.extensions.http.HTT PBindingExtensionsImpl [javac] axisBinding.setProperty(WSDL2Constants.ATTR_WHTTP_TRANSFER_C ODING, httpBindingExtensions.getHttpTransferCodingDefault ()); [javac] ^ [javac] C:\axis2\modules\kernel\src\org\apache\axis2\description\WSDL20ToAxi sServiceBuilder.java:649: cannot find symbol [javac] symbol : method getHttpTransferCoding() [javac] location: interface org.apache.woden.wsdl20.extensions.http.HTTPBind ingFaultExtensions [javac] httpBindingFaultExtensions.getHttpTransferCoding ()); [javac] ^ [javac] C:\axis2\modules\kernel\src\org\apache\axis2\description\WSDL20ToAxi sServiceBuilder.java:706: cannot find symbol [javac] symbol : method getHttpTransferCodingDefault() [javac] location: interface org.apache.woden.wsdl20.extensions.http.HTTPBind ingOperationExtensions [javac] httpBindingOperationExtensions.getHttpTransferCo dingDefault()); [javac] ^ [javac] C:\axis2\modules\kernel\src\org\apache\axis2\description\WSDL20ToAxi sServiceBuilder.java:737: cannot find symbol [javac] symbol : method getHttpTransferCoding() [javac] location: interface org.apache.woden.wsdl20.extensions.http.HTTPBind ingMessageReferenceExtensions [javac] httpBindingMessageReferenceExtensions.getHtt pTransferCoding()); [javac] ^ [javac] Note: Some input files use or override a deprecated API. [javac] Note: Recompile
[jira] Updated: (AXIS2-1749) Wrong Java2WSDL generation
[
https://issues.apache.org/jira/browse/AXIS2-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manoj Khangaonkar updated AXIS2-1749:
-
Attachment: patch-1749.txt
Attached is a patch that fixes the issue described.
Mj
Wrong Java2WSDL generation
--
Key: AXIS2-1749
URL: https://issues.apache.org/jira/browse/AXIS2-1749
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: codegen
Affects Versions: 1.1
Reporter: Jabber W
Assigned To: Deepal Jayasinghe
Attachments: patch-1749.txt
During the generation of type definitions Java2WSDL of axis2-1.1 flattens
chains of extender java data types to independent schema types without
extending relations between them, while Axis121 stores these relations by
extension base.
For example: say,
class A { public String someString; public A someLink; } and
class B extends A { public int someInt; }
and the exposed service is:
class MySvc { String myOp(A arg) {..} }
Running of Java2WSDL on it:
java2wsdl -cn MySvc -xc B
creates 2 non-related types:
xs:complexType name=A
xs:sequence
xs:element name=someLink type=ns:A/
xs:element name=someString type=xs:string/
/xs:sequence
/xs:complexType
and
xs:complexType name=B
xs:sequence
xs:element name=someLink type=ns:A/
xs:element name=someString type=xs:string/
xs:element name=someInt type=xs:int/
/xs:sequence
/xs:complexType
while B should be:
xs:complexType name=B
xs:complexContent
xs:extension base=ns:A
xs:sequence
xs:element name=someInt type=xs:int/
/xs:sequence
/xs:extension
/xs:complexContent
/xs:complexType
Since complexType B is not extension of ? it (the B type element) can't be
passed as the someLink.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-2165) Build errors in kernel
Build errors in kernel -- Key: AXIS2-2165 URL: https://issues.apache.org/jira/browse/AXIS2-2165 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: kernel Affects Versions: 1.2, nightly Environment: Windows Reporter: Manoj Khangaonkar Priority: Blocker There have been some changes in woden and AXIS2 code is not current w.r.t woden The errors are : java:compile: [echo] Compiling to C:\axis2\modules\kernel/target/classes [javac] Compiling 184 source files to C:\axis2\modules\kernel\target\classes [javac] C:\axis2\modules\kernel\src\org\apache\axis2\description\WSDL20ToAxi sServiceBuilder.java:436: cannot find symbol [javac] symbol : method getHttpTransferCodingDefault() [javac] location: class org.apache.woden.internal.wsdl20.extensions.soap.SOA PBindingExtensionsImpl [javac] soapBindingExtensions.getHttpTransferCodingDefault() ); [javac] ^ [javac] C:\axis2\modules\kernel\src\org\apache\axis2\description\WSDL20ToAxi sServiceBuilder.java:465: cannot find symbol [javac] symbol : method getHttpTransferCoding() [javac] location: interface org.apache.woden.wsdl20.extensions.soap.SOAPBind ingFaultExtensions [javac] soapBindingFaultExtensions.getHttpTransferCoding ()); [javac] ^ [javac] C:\axis2\modules\kernel\src\org\apache\axis2\description\WSDL20ToAxi sServiceBuilder.java:528: cannot find symbol [javac] symbol : method getHttpTransferCodingDefault() [javac] location: interface org.apache.woden.wsdl20.extensions.soap.SOAPBind ingOperationExtensions [javac] soapBindingOperationExtensions.getHttpTransferCo dingDefault()); [javac] ^ [javac] C:\axis2\modules\kernel\src\org\apache\axis2\description\WSDL20ToAxi sServiceBuilder.java:562: cannot find symbol [javac] symbol : method getHttpTransferCoding() [javac] location: interface org.apache.woden.wsdl20.extensions.soap.SOAPBind ingMessageReferenceExtensions [javac] soapBindingMessageReferenceExtensions.getHtt pTransferCoding()); [javac] ^ [javac] C:\axis2\modules\kernel\src\org\apache\axis2\description\WSDL20ToAxi sServiceBuilder.java:622: cannot find symbol [javac] symbol : method getHttpTransferCodingDefault() [javac] location: class org.apache.woden.internal.wsdl20.extensions.http.HTT PBindingExtensionsImpl [javac] axisBinding.setProperty(WSDL2Constants.ATTR_WHTTP_TRANSFER_C ODING, httpBindingExtensions.getHttpTransferCodingDefault ()); [javac] ^ [javac] C:\axis2\modules\kernel\src\org\apache\axis2\description\WSDL20ToAxi sServiceBuilder.java:649: cannot find symbol [javac] symbol : method getHttpTransferCoding() [javac] location: interface org.apache.woden.wsdl20.extensions.http.HTTPBind ingFaultExtensions [javac] httpBindingFaultExtensions.getHttpTransferCoding ()); [javac] ^ [javac] C:\axis2\modules\kernel\src\org\apache\axis2\description\WSDL20ToAxi sServiceBuilder.java:706: cannot find symbol [javac] symbol : method getHttpTransferCodingDefault() [javac] location: interface org.apache.woden.wsdl20.extensions.http.HTTPBind ingOperationExtensions [javac] httpBindingOperationExtensions.getHttpTransferCo dingDefault()); [javac] ^ [javac] C:\axis2\modules\kernel\src\org\apache\axis2\description\WSDL20ToAxi sServiceBuilder.java:737: cannot find symbol [javac] symbol : method getHttpTransferCoding() [javac] location: interface org.apache.woden.wsdl20.extensions.http.HTTPBind ingMessageReferenceExtensions [javac] httpBindingMessageReferenceExtensions.getHtt pTransferCoding()); [javac] ^ [javac] Note: Some input files use or override a deprecated API. [javac] Note: Recompile with -Xlint:deprecation for details. [javac] 8 errors Mj -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-1749) Wrong Java2WSDL generation
[
https://issues.apache.org/jira/browse/AXIS2-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12472115
]
Manoj Khangaonkar commented on AXIS2-1749:
--
Hi all,
I am working on this issue and will provide a patch shortly.
Mj
Wrong Java2WSDL generation
--
Key: AXIS2-1749
URL: https://issues.apache.org/jira/browse/AXIS2-1749
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: codegen
Affects Versions: 1.1
Reporter: Jabber W
Assigned To: Deepal Jayasinghe
During the generation of type definitions Java2WSDL of axis2-1.1 flattens
chains of extender java data types to independent schema types without
extending relations between them, while Axis121 stores these relations by
extension base.
For example: say,
class A { public String someString; public A someLink; } and
class B extends A { public int someInt; }
and the exposed service is:
class MySvc { String myOp(A arg) {..} }
Running of Java2WSDL on it:
java2wsdl -cn MySvc -xc B
creates 2 non-related types:
xs:complexType name=A
xs:sequence
xs:element name=someLink type=ns:A/
xs:element name=someString type=xs:string/
/xs:sequence
/xs:complexType
and
xs:complexType name=B
xs:sequence
xs:element name=someLink type=ns:A/
xs:element name=someString type=xs:string/
xs:element name=someInt type=xs:int/
/xs:sequence
/xs:complexType
while B should be:
xs:complexType name=B
xs:complexContent
xs:extension base=ns:A
xs:sequence
xs:element name=someInt type=xs:int/
/xs:sequence
/xs:extension
/xs:complexContent
/xs:complexType
Since complexType B is not extension of ? it (the B type element) can't be
passed as the someLink.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2116) java2WSDL should generate schema elements for public fields
[
https://issues.apache.org/jira/browse/AXIS2-2116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12472003
]
Manoj Khangaonkar commented on AXIS2-2116:
--
Deepal / Dims,
What do think of the patch ?
I am also starting to look at AXIS2-1749. But a fix for AXIS2-1749 would need
to on top of
AXIS2- 2116 , if this patch is accepted - that is.
It would be double work to provide a patch for 1749 now on existing codebase
and then com back and provide
an additional fix for the additional code that patch 2116 provides.
Manoj
java2WSDL should generate schema elements for public fields
---
Key: AXIS2-2116
URL: https://issues.apache.org/jira/browse/AXIS2-2116
Project: Axis 2.0 (Axis2)
Issue Type: Improvement
Components: wsdl
Affects Versions: 1.2, 1.1.1, nightly
Environment: ALL
Reporter: Manoj Khangaonkar
Attachments: patch2116.txt
When java2WSDL generates schema for method parameters, it generates elements
only for properties - those that have get/set metthods.
If I have a class that has fields without get/set methods like
public class Book {
public String title ;
public String author ;
}
The complex type in types section of the WSDL is
xs:complexType name=Book
xs:sequence /
/xs:complexType
It should be
xs:complexType name=Book
xs:sequence
xs:element name=title nillable=true type=xs:string /
xs:element name=author nillable=true type=xs:string /
/xs;sequence
/xs:complexType
java2wsdl is typically used to generate WSDL for legacy code and it is not
reasonable to expect users to go add get/set methods to legacy code
just because they need to generate WSDL
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-2116) java2WSDL should generate schema elements for public fields
[
https://issues.apache.org/jira/browse/AXIS2-2116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manoj Khangaonkar updated AXIS2-2116:
-
Attachment: patch2116.txt
patch is attached.
If there is property and a public field with the same name, the property is
used ( instead of the field).
java2WSDL should generate schema elements for public fields
---
Key: AXIS2-2116
URL: https://issues.apache.org/jira/browse/AXIS2-2116
Project: Axis 2.0 (Axis2)
Issue Type: Improvement
Components: wsdl
Affects Versions: 1.2, 1.1.1, nightly
Environment: ALL
Reporter: Manoj Khangaonkar
Attachments: patch2116.txt
When java2WSDL generates schema for method parameters, it generates elements
only for properties - those that have get/set metthods.
If I have a class that has fields without get/set methods like
public class Book {
public String title ;
public String author ;
}
The complex type in types section of the WSDL is
xs:complexType name=Book
xs:sequence /
/xs:complexType
It should be
xs:complexType name=Book
xs:sequence
xs:element name=title nillable=true type=xs:string /
xs:element name=author nillable=true type=xs:string /
/xs;sequence
/xs:complexType
java2wsdl is typically used to generate WSDL for legacy code and it is not
reasonable to expect users to go add get/set methods to legacy code
just because they need to generate WSDL
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-2116) java2WSDL should generate schema elements for public fields
java2WSDL should generate schema elements for public fields
---
Key: AXIS2-2116
URL: https://issues.apache.org/jira/browse/AXIS2-2116
Project: Axis 2.0 (Axis2)
Issue Type: Improvement
Components: wsdl
Affects Versions: 1.1.1, 1.2, nightly
Environment: ALL
Reporter: Manoj Khangaonkar
When java2WSDL generates schema for method parameters, it generates elements
only for properties - those that have get/set metthods.
If I have a class that has fields without get/set methods like
public class Book {
public String title ;
public String author ;
}
The complex type in types section of the WSDL is
xs:complexType name=Book
xs:sequence /
/xs:complexType
It should be
xs:complexType name=Book
xs:sequence
xs:element name=title nillable=true type=xs:string /
xs:element name=author nillable=true type=xs:string /
/xs;sequence
/xs:complexType
java2wsdl is typically used to generate WSDL for legacy code and it is not
reasonable to expect users to go add get/set methods to legacy code
just because they need to generate WSDL
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2116) java2WSDL should generate schema elements for public fields
[
https://issues.apache.org/jira/browse/AXIS2-2116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12470696
]
Manoj Khangaonkar commented on AXIS2-2116:
--
Deepal,
There is no reason to have the limitation that AXIS2 supports only java beans.
Remember that java2WSDL is typically used
to generate WSDL for legacy java code. The legacy code may or may not be java
bean. It seems unreasonable that java2WSDL cannot
handle class if there are no get/set methods.
I propose this as an enhancement. I know how to fix it and will provide the
patch.
Currently java2WSDL uses codehaus library for introspecting the
metthods/parameters in the input java class. When
introspecting the parameters, the code gets only the properties from the
class. We really need to get the properties and
fields.
fields in codehaus refers to public members of the class.
If you see any serious downside to doing this, let me know - other wise I can
provide a patch.
Even if we decide not to support this , the code should print a warning and not
spit out incorrect WSDL.
Dims,
The issue is that the generated WSDL is incorrect. This is straight -
generation of WSDL from java - so unless I am missing
something obvious - there are no databinding issues here.
Manoj
java2WSDL should generate schema elements for public fields
---
Key: AXIS2-2116
URL: https://issues.apache.org/jira/browse/AXIS2-2116
Project: Axis 2.0 (Axis2)
Issue Type: Improvement
Components: wsdl
Affects Versions: 1.2, 1.1.1, nightly
Environment: ALL
Reporter: Manoj Khangaonkar
When java2WSDL generates schema for method parameters, it generates elements
only for properties - those that have get/set metthods.
If I have a class that has fields without get/set methods like
public class Book {
public String title ;
public String author ;
}
The complex type in types section of the WSDL is
xs:complexType name=Book
xs:sequence /
/xs:complexType
It should be
xs:complexType name=Book
xs:sequence
xs:element name=title nillable=true type=xs:string /
xs:element name=author nillable=true type=xs:string /
/xs;sequence
/xs:complexType
java2wsdl is typically used to generate WSDL for legacy code and it is not
reasonable to expect users to go add get/set methods to legacy code
just because they need to generate WSDL
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-1215) REST request not getting parsed correctly if parameter input type is an array
[
https://issues.apache.org/jira/browse/AXIS2-1215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12470369
]
Manoj Khangaonkar commented on AXIS2-1215:
--
Deepal,
The patch was provide by Manoj ( not Kris).
In any case , I will extract the latest code from SVN and provide and updated
patch
Manoj
REST request not getting parsed correctly if parameter input type is an array
-
Key: AXIS2-1215
URL: https://issues.apache.org/jira/browse/AXIS2-1215
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: kernel
Affects Versions: 1.0
Environment: windows xp pro, IE, Axis 2 version 1.0
Reporter: Kris
Assigned To: Deepal Jayasinghe
Priority: Critical
Attachments: patch-1215.txt, patch-1215v2.txt
I have a method that takes in array for strings:
public String sayHello(String [ ] to) {...}
The SOAP request for this works fine. The REST request however gets
translated into a fixed length array of only one string. For example, in the
request
http://localhost:8080/axis2/rest/helloservice/sayHello?to=Andyto=Markto=Jen
Mark and Jen are thrown away and only Andy is passed on into the array.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-1775) Axis2 fails in wsdl2java with Array is not supported exception
[
https://issues.apache.org/jira/browse/AXIS2-1775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12469549
]
Manoj Khangaonkar commented on AXIS2-1775:
--
Andreas,
Use of SOAP encoding is not recommended by the WS I Basic profile. SOAP
encoding creates a number of interoperability issue , which is
why the Basic profile prohibits the use SOAP encoding.
I am not familiar with the library you are using , but I have to think - that
if it does not follow the recommendations of Basic profile - it is a
little dated and you might want to switch to a library that follows the
standards
Mj
Axis2 fails in wsdl2java with Array is not supported exception
Key: AXIS2-1775
URL: https://issues.apache.org/jira/browse/AXIS2-1775
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: codegen
Affects Versions: 1.1
Reporter: Andreas Goetz
Attachments: wsdl.xml
Trying to run wsdl2java from axis2 creates this exception:
Exception in thread main
org.apache.axis2.wsdl.codegen.CodeGenerationException:
java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:224)
at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32)
at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21)
Caused by: java.lang.RuntimeException:
java.lang.reflect.InvocationTargetException
at
org.apache.axis2.wsdl.codegen.extension.SimpleDBExtension.engage(SimpleDBExtension.java:52)
at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:177)
... 2 more
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.apache.axis2.wsdl.codegen.extension.SimpleDBExtension.engage(SimpleDBExtension.java:49)
... 3 more
Caused by: org.apache.axis2.schema.SchemaCompilationException:
{http://schemas.xmlsoap.org/soap/encoding/}Array is not supported.
The same WSDL works fine using AXIS1
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-1215) REST request not getting parsed correctly if parameter input type is an array
[
https://issues.apache.org/jira/browse/AXIS2-1215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manoj Khangaonkar updated AXIS2-1215:
-
Priority: Critical (was: Major)
Can one of the committers review commit this patch so this issue may be
closed.
REST request not getting parsed correctly if parameter input type is an array
-
Key: AXIS2-1215
URL: https://issues.apache.org/jira/browse/AXIS2-1215
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: kernel
Affects Versions: 1.0
Environment: windows xp pro, IE, Axis 2 version 1.0
Reporter: Kris
Priority: Critical
Attachments: patch-1215.txt, patch-1215v2.txt
I have a method that takes in array for strings:
public String sayHello(String [ ] to) {...}
The SOAP request for this works fine. The REST request however gets
translated into a fixed length array of only one string. For example, in the
request
http://localhost:8080/axis2/rest/helloservice/sayHello?to=Andyto=Markto=Jen
Mark and Jen are thrown away and only Andy is passed on into the array.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-1912) java2WSDL.bat needs to use existing CLASSPATH as well
[ https://issues.apache.org/jira/browse/AXIS2-1912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465630 ] Manoj Khangaonkar commented on AXIS2-1912: -- Can one of the committer comment on this perhaps commit it. It is a trivial fix , but makes the use of java2WSDL less annoying. The current script overrides any existing CLASSPATH. Any there is simply no reason to require every user to use to -cp . (dot) command line option every time. An even better fix might be to do set AXIS2_CLASS_PATH=.;%CLASSPATH%;%AXIS2_HOME% Axis2-1714 seems to be a similar issue. As already mentioned , on the unix side, this is already done in setenv.sh thanks java2WSDL.bat needs to use existing CLASSPATH as well - Key: AXIS2-1912 URL: https://issues.apache.org/jira/browse/AXIS2-1912 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: codegen, wsdl Affects Versions: 1.2, 1.1.1, 1.1 Environment: Windows Reporter: Manoj Khangaonkar Attachments: java2wsdl.bat Users may have an existing environment variable CLASSPATH - that points to the current directory and other directories as well as other jars. java2WSDL.bat needs to append the existing classpath to AXIS2_CLASS_PATH as in set AXIS2_CLASS_PATH=%CLASSPATH%;%AXIS2_HOME% This saves user the trouble of adding multiple -cp options at the command line. Attached is an updated java2WSDL.bat as a patch. java2wsdl.sh already does the same -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-1215) REST request not getting parsed correctly if parameter input type is an array
[
https://issues.apache.org/jira/browse/AXIS2-1215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manoj Khangaonkar updated AXIS2-1215:
-
Attachment: patch-1215v2.txt
REST request not getting parsed correctly if parameter input type is an array
-
Key: AXIS2-1215
URL: https://issues.apache.org/jira/browse/AXIS2-1215
Project: Apache Axis 2.0 (Axis2)
Issue Type: Bug
Components: kernel
Affects Versions: 1.0
Environment: windows xp pro, IE, Axis 2 version 1.0
Reporter: Kris
Attachments: patch-1215.txt, patch-1215v2.txt
I have a method that takes in array for strings:
public String sayHello(String [ ] to) {...}
The SOAP request for this works fine. The REST request however gets
translated into a fixed length array of only one string. For example, in the
request
http://localhost:8080/axis2/rest/helloservice/sayHello?to=Andyto=Markto=Jen
Mark and Jen are thrown away and only Andy is passed on into the array.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-1215) REST request not getting parsed correctly if parameter input type is an array
[
https://issues.apache.org/jira/browse/AXIS2-1215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manoj Khangaonkar updated AXIS2-1215:
-
Attachment: patch-1215.txt
REST request not getting parsed correctly if parameter input type is an array
-
Key: AXIS2-1215
URL: https://issues.apache.org/jira/browse/AXIS2-1215
Project: Apache Axis 2.0 (Axis2)
Issue Type: Bug
Components: kernel
Affects Versions: 1.0
Environment: windows xp pro, IE, Axis 2 version 1.0
Reporter: Kris
Attachments: patch-1215.txt
I have a method that takes in array for strings:
public String sayHello(String [ ] to) {...}
The SOAP request for this works fine. The REST request however gets
translated into a fixed length array of only one string. For example, in the
request
http://localhost:8080/axis2/rest/helloservice/sayHello?to=Andyto=Markto=Jen
Mark and Jen are thrown away and only Andy is passed on into the array.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-1215) REST request not getting parsed correctly if parameter input type is an array
[
https://issues.apache.org/jira/browse/AXIS2-1215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465337
]
Manoj Khangaonkar commented on AXIS2-1215:
--
Attached a patch that fixes this issue. Please review and commit.
To test this patch
1. add the following method to the StockQuoteService in quickstartsample
public String[] listStocks(String[] stock) {
for (int i=0 ; i stock.length ; i++) {
System.out.println(mj:::+ received stock + stock[i]) ;
}
return stock ;
}
2. Build and deploy as usual
3. invoke the method by pointing your browser to
http://localhost:8080/axis2/rest/StockQuoteService/listStocks?stock=IBMstock=SUNstock=FICOstock=XYZ
4. You will ses the following response in the browser
ns:listStocksResponse xmlns:ns=http://quickstart.samples/xsd;
ns:returnIBM/ns:return
ns:returnSUN/ns:return
ns:returnFICO/ns:return
ns:returnXYZ/ns:return
/ns:listStocksResponse
regards
Mj
REST request not getting parsed correctly if parameter input type is an array
-
Key: AXIS2-1215
URL: https://issues.apache.org/jira/browse/AXIS2-1215
Project: Apache Axis 2.0 (Axis2)
Issue Type: Bug
Components: kernel
Affects Versions: 1.0
Environment: windows xp pro, IE, Axis 2 version 1.0
Reporter: Kris
Attachments: patch-1215.txt
I have a method that takes in array for strings:
public String sayHello(String [ ] to) {...}
The SOAP request for this works fine. The REST request however gets
translated into a fixed length array of only one string. For example, in the
request
http://localhost:8080/axis2/rest/helloservice/sayHello?to=Andyto=Markto=Jen
Mark and Jen are thrown away and only Andy is passed on into the array.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-1215) REST request not getting parsed correctly if parameter input type is an array
[
https://issues.apache.org/jira/browse/AXIS2-1215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12462920
]
Manoj Khangaonkar commented on AXIS2-1215:
--
I am able to reproduce this issue. This happens because SchemaUtil.java is not
correctly processing the request parameters.
I will provide a patch.
Mj
REST request not getting parsed correctly if parameter input type is an array
-
Key: AXIS2-1215
URL: https://issues.apache.org/jira/browse/AXIS2-1215
Project: Apache Axis 2.0 (Axis2)
Issue Type: Bug
Components: kernel
Affects Versions: 1.0
Environment: windows xp pro, IE, Axis 2 version 1.0
Reporter: Kris
I have a method that takes in array for strings:
public String sayHello(String [ ] to) {...}
The SOAP request for this works fine. The REST request however gets
translated into a fixed length array of only one string. For example, in the
request
http://localhost:8080/axis2/rest/helloservice/sayHello?to=Andyto=Markto=Jen
Mark and Jen are thrown away and only Andy is passed on into the array.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-1917) quickstart sample does not work on the trunk branch
[ https://issues.apache.org/jira/browse/AXIS2-1917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manoj Khangaonkar updated AXIS2-1917: - Component/s: kernel Priority: Critical (was: Major) Can one of the committer look into committing this patch. REST invocation is broken and the quickstart sample which is the first sample any newbie would try is broken as a result quickstart sample does not work on the trunk branch --- Key: AXIS2-1917 URL: https://issues.apache.org/jira/browse/AXIS2-1917 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: kernel, samples Affects Versions: 1.2, 1.1.1 Environment: windows Reporter: Manoj Khangaonkar Priority: Critical Attachments: patch-1917.txt, patch-1917v2.txt 1. run ant.generateservice to create StockQuoteService.aar 2. Copy the aar to webapps/axis2/WEB-INF/services 3. type http://localhost:8080/axis2/rest/StockQuoteService/getPrice?symbol=IBM in your web browser In the tomcat logs I see Dec 27, 2006 8:54:40 AM org.apache.axis2.transport.http.AxisRESTServlet doGet SEVERE: org.apache.axis2.AxisFault: I can not find a service for this request to be serviced. Check the WSDL and the request URI The browser I get URL not found -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-1917) quickstart sample does not work on the trunk branch
[ http://issues.apache.org/jira/browse/AXIS2-1917?page=all ] Manoj Khangaonkar updated AXIS2-1917: - Attachment: patch-1917.txt Patch is attached. quickstart sample does not work on the trunk branch --- Key: AXIS2-1917 URL: http://issues.apache.org/jira/browse/AXIS2-1917 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: samples Affects Versions: 1.2, 1.1.1 Environment: windows Reporter: Manoj Khangaonkar Attachments: patch-1917.txt 1. run ant.generateservice to create StockQuoteService.aar 2. Copy the aar to webapps/axis2/WEB-INF/services 3. type http://localhost:8080/axis2/rest/StockQuoteService/getPrice?symbol=IBM in your web browser In the tomcat logs I see Dec 27, 2006 8:54:40 AM org.apache.axis2.transport.http.AxisRESTServlet doGet SEVERE: org.apache.axis2.AxisFault: I can not find a service for this request to be serviced. Check the WSDL and the request URI The browser I get URL not found -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-1917) quickstart sample does not work on the trunk branch
[ http://issues.apache.org/jira/browse/AXIS2-1917?page=all ] Manoj Khangaonkar updated AXIS2-1917: - Attachment: patch-1917v2.txt Updated and corrected patch. My apologies - the earlier patch is missing an import and will cause an compilation error. quickstart sample does not work on the trunk branch --- Key: AXIS2-1917 URL: http://issues.apache.org/jira/browse/AXIS2-1917 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: samples Affects Versions: 1.2, 1.1.1 Environment: windows Reporter: Manoj Khangaonkar Attachments: patch-1917.txt, patch-1917v2.txt 1. run ant.generateservice to create StockQuoteService.aar 2. Copy the aar to webapps/axis2/WEB-INF/services 3. type http://localhost:8080/axis2/rest/StockQuoteService/getPrice?symbol=IBM in your web browser In the tomcat logs I see Dec 27, 2006 8:54:40 AM org.apache.axis2.transport.http.AxisRESTServlet doGet SEVERE: org.apache.axis2.AxisFault: I can not find a service for this request to be serviced. Check the WSDL and the request URI The browser I get URL not found -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-1900) December 20 nightly build -- jsp exception
[ http://issues.apache.org/jira/browse/AXIS2-1900?page=comments#action_12461274 ] Manoj Khangaonkar commented on AXIS2-1900: -- Thilina, Your fix seems to resolve the issue. thanks December 20 nightly build -- jsp exception -- Key: AXIS2-1900 URL: http://issues.apache.org/jira/browse/AXIS2-1900 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: admin console Affects Versions: nightly Environment: Tomcat 5.5.15, axis2 1.1.1 nightly Reporter: Gul Onural Attachments: localhost.2006-12-20.log I have downloaded the December 20, axis2 nightly build axis2.war and installed in tomcat. When I try to access axis2 admin page (http://localhost:8080/axis2/) from a web browser I get following jsp exception. Tomcat log is also attached. Gul HTTP Status 500 - type Exception report message description The server encountered an internal error () that prevented it from fulfilling this request. exception org.apache.jasper.JasperException: Exception in JSP: /axis2-web/index.jsp:23 20: */ 21: % 22: head 23: jsp:include page=include/httpbase.jsp/ 24: titleAxis 2 - Home/title 25: link href=axis2-web/css/axis-style.css rel=stylesheet type=text/css/ 26: /head Stacktrace: org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:504) org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:375) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) root cause org.apache.jasper.JasperException org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:510) org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:393) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:966) org.apache.jsp.axis2_002dweb.index_jsp._jspService(org.apache.jsp.axis2_002dweb.index_jsp:67) org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:332) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) root cause java.lang.NullPointerException org.apache.jsp.axis2_002dweb.include.httpbase_jsp.jspInit(org.apache.jsp.axis2_002dweb.include.httpbase_jsp:22) org.apache.jasper.runtime.HttpJspBase.init(HttpJspBase.java:78) org.apache.jasper.servlet.JspServletWrapper.getServlet(JspServletWrapper.java:155) org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:315) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:966) org.apache.jsp.axis2_002dweb.index_jsp._jspService(org.apache.jsp.axis2_002dweb.index_jsp:67) org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:332) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) note The full stack trace of the root cause is available in the Apache Tomcat/5.5.15 logs. Apache Tomcat/5.5.15 -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-1794) QuickStart Samples adb,xmlbean have a problem in build.xml invoking ant codegen task
[ http://issues.apache.org/jira/browse/AXIS2-1794?page=comments#action_12461275 ] Manoj Khangaonkar commented on AXIS2-1794: -- Since 1793 is resolved. This issue may be closed QuickStart Samples adb,xmlbean have a problem in build.xml invoking ant codegen task Key: AXIS2-1794 URL: http://issues.apache.org/jira/browse/AXIS2-1794 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: samples, build,site Affects Versions: 1.2 Environment: window Reporter: Manoj Khangaonkar Attachments: build.xml, build.xml The build.xml specify the classname as org.apache.axis2.tool.ant.AntCodegenTask You get class not found errror. But the correct path should be org.apache.axis2.ant.AntCodegenTask -- See JIRA - 1793 -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-1917) quickstart sample does not work on the trunk branch
quickstart sample does not work on the trunk branch --- Key: AXIS2-1917 URL: http://issues.apache.org/jira/browse/AXIS2-1917 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: samples Affects Versions: 1.2, 1.1.1 Environment: windows Reporter: Manoj Khangaonkar 1. run ant.generateservice to create StockQuoteService.aar 2. Copy the aar to webapps/axis2/WEB-INF/services 3. type http://localhost:8080/axis2/rest/StockQuoteService/getPrice?symbol=IBM in your web browser In the tomcat logs I see Dec 27, 2006 8:54:40 AM org.apache.axis2.transport.http.AxisRESTServlet doGet SEVERE: org.apache.axis2.AxisFault: I can not find a service for this request to be serviced. Check the WSDL and the request URI The browser I get URL not found -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-1917) quickstart sample does not work on the trunk branch
[
http://issues.apache.org/jira/browse/AXIS2-1917?page=comments#action_12461131 ]
Manoj Khangaonkar commented on AXIS2-1917:
--
The problem is in RESTUTIL.java
private void dispatchAndVerify(MessageContext msgContext) throws AxisFault {
RequestURIBasedDispatcher requestDispatcher = new
RequestURIBasedDispatcher();
requestDispatcher.invoke(msgContext);
if (msgContext.getAxisService() == null || msgContext.getAxisOperation() ==
null) {
throw new AxisFault(I can not find a service for this request to
be serviced. +
Check the WSDL and the request URI);
}
}
RequestURIBasedDispatcher does not resolve the Operation. Hence
msgContext.getAxisOperation is always null.
Apparently there is a RequestURIOperationDispatcher that needs to be called
before this check
quickstart sample does not work on the trunk branch
---
Key: AXIS2-1917
URL: http://issues.apache.org/jira/browse/AXIS2-1917
Project: Apache Axis 2.0 (Axis2)
Issue Type: Bug
Components: samples
Affects Versions: 1.2, 1.1.1
Environment: windows
Reporter: Manoj Khangaonkar
1. run ant.generateservice to create StockQuoteService.aar
2. Copy the aar to webapps/axis2/WEB-INF/services
3. type
http://localhost:8080/axis2/rest/StockQuoteService/getPrice?symbol=IBM in
your web browser
In the tomcat logs I see
Dec 27, 2006 8:54:40 AM org.apache.axis2.transport.http.AxisRESTServlet doGet
SEVERE: org.apache.axis2.AxisFault: I can not find a service for this request
to
be serviced. Check the WSDL and the request URI
The browser I get URL not found
--
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
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-1917) quickstart sample does not work on the trunk branch
[
http://issues.apache.org/jira/browse/AXIS2-1917?page=comments#action_12461137 ]
Manoj Khangaonkar commented on AXIS2-1917:
--
Updating the method as follows fixes the problem.
private void dispatchAndVerify(MessageContext msgContext) throws AxisFault {
RequestURIBasedDispatcher requestDispatcher = new
RequestURIBasedDispatcher();
requestDispatcher.invoke(msgContext);
RequestURIOperationDispatcher opDispatcher = new
RequestURIOperationDispatcher();
opDispatcher.invoke(msgContext);
if (msgContext.getAxisService() == null ||
msgContext.getAxisOperation() == null) {
throw new AxisFault(I can not find a service for this request to
be serviced. +
Check the WSDL and the request URI);
}
}
I will run tests and provide a patch
quickstart sample does not work on the trunk branch
---
Key: AXIS2-1917
URL: http://issues.apache.org/jira/browse/AXIS2-1917
Project: Apache Axis 2.0 (Axis2)
Issue Type: Bug
Components: samples
Affects Versions: 1.2, 1.1.1
Environment: windows
Reporter: Manoj Khangaonkar
1. run ant.generateservice to create StockQuoteService.aar
2. Copy the aar to webapps/axis2/WEB-INF/services
3. type
http://localhost:8080/axis2/rest/StockQuoteService/getPrice?symbol=IBM in
your web browser
In the tomcat logs I see
Dec 27, 2006 8:54:40 AM org.apache.axis2.transport.http.AxisRESTServlet doGet
SEVERE: org.apache.axis2.AxisFault: I can not find a service for this request
to
be serviced. Check the WSDL and the request URI
The browser I get URL not found
--
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
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-1912) java2WSDL.bat needs to use existing CLASSPATH as well
[ http://issues.apache.org/jira/browse/AXIS2-1912?page=comments#action_12460882 ] Manoj Khangaonkar commented on AXIS2-1912: -- At the very least, it saves the user the trouble of typing the redundant -cp . (dot) option with every commandline. It is reasonable to assume that the current directory is in the classpath based on the users environment java2WSDL.bat needs to use existing CLASSPATH as well - Key: AXIS2-1912 URL: http://issues.apache.org/jira/browse/AXIS2-1912 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: wsdl, codegen Affects Versions: 1.1, 1.2, 1.1.1 Environment: Windows Reporter: Manoj Khangaonkar Attachments: java2wsdl.bat Users may have an existing environment variable CLASSPATH - that points to the current directory and other directories as well as other jars. java2WSDL.bat needs to append the existing classpath to AXIS2_CLASS_PATH as in set AXIS2_CLASS_PATH=%CLASSPATH%;%AXIS2_HOME% This saves user the trouble of adding multiple -cp options at the command line. Attached is an updated java2WSDL.bat as a patch. java2wsdl.sh already does the same -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-1900) December 20 nightly build -- jsp exception
[ http://issues.apache.org/jira/browse/AXIS2-1900?page=comments#action_12460651 ] Manoj Khangaonkar commented on AXIS2-1900: -- This is still a problem on the latest code stream. When I get the code from svn and build , the build is successful but axis2.war does not have addressing-1.1.mar and the above problem exists. I am unable to reopen this issue. Please reopen it December 20 nightly build -- jsp exception -- Key: AXIS2-1900 URL: http://issues.apache.org/jira/browse/AXIS2-1900 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: admin console Affects Versions: nightly Environment: Tomcat 5.5.15, axis2 1.1.1 nightly Reporter: Gul Onural Attachments: localhost.2006-12-20.log I have downloaded the December 20, axis2 nightly build axis2.war and installed in tomcat. When I try to access axis2 admin page (http://localhost:8080/axis2/) from a web browser I get following jsp exception. Tomcat log is also attached. Gul HTTP Status 500 - type Exception report message description The server encountered an internal error () that prevented it from fulfilling this request. exception org.apache.jasper.JasperException: Exception in JSP: /axis2-web/index.jsp:23 20: */ 21: % 22: head 23: jsp:include page=include/httpbase.jsp/ 24: titleAxis 2 - Home/title 25: link href=axis2-web/css/axis-style.css rel=stylesheet type=text/css/ 26: /head Stacktrace: org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:504) org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:375) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) root cause org.apache.jasper.JasperException org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:510) org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:393) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:966) org.apache.jsp.axis2_002dweb.index_jsp._jspService(org.apache.jsp.axis2_002dweb.index_jsp:67) org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:332) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) root cause java.lang.NullPointerException org.apache.jsp.axis2_002dweb.include.httpbase_jsp.jspInit(org.apache.jsp.axis2_002dweb.include.httpbase_jsp:22) org.apache.jasper.runtime.HttpJspBase.init(HttpJspBase.java:78) org.apache.jasper.servlet.JspServletWrapper.getServlet(JspServletWrapper.java:155) org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:315) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:966) org.apache.jsp.axis2_002dweb.index_jsp._jspService(org.apache.jsp.axis2_002dweb.index_jsp:67) org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:332) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) note The full stack trace of the root cause is available in the Apache Tomcat/5.5.15 logs. Apache Tomcat/5.5.15 -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-1900) December 20 nightly build -- jsp exception
[ http://issues.apache.org/jira/browse/AXIS2-1900?page=comments#action_12460653 ] Manoj Khangaonkar commented on AXIS2-1900: -- The work around is to run maven from the addressing module and build the addressing mar separately and then copy it to webapps/axis2/modules December 20 nightly build -- jsp exception -- Key: AXIS2-1900 URL: http://issues.apache.org/jira/browse/AXIS2-1900 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: admin console Affects Versions: nightly Environment: Tomcat 5.5.15, axis2 1.1.1 nightly Reporter: Gul Onural Attachments: localhost.2006-12-20.log I have downloaded the December 20, axis2 nightly build axis2.war and installed in tomcat. When I try to access axis2 admin page (http://localhost:8080/axis2/) from a web browser I get following jsp exception. Tomcat log is also attached. Gul HTTP Status 500 - type Exception report message description The server encountered an internal error () that prevented it from fulfilling this request. exception org.apache.jasper.JasperException: Exception in JSP: /axis2-web/index.jsp:23 20: */ 21: % 22: head 23: jsp:include page=include/httpbase.jsp/ 24: titleAxis 2 - Home/title 25: link href=axis2-web/css/axis-style.css rel=stylesheet type=text/css/ 26: /head Stacktrace: org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:504) org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:375) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) root cause org.apache.jasper.JasperException org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:510) org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:393) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:966) org.apache.jsp.axis2_002dweb.index_jsp._jspService(org.apache.jsp.axis2_002dweb.index_jsp:67) org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:332) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) root cause java.lang.NullPointerException org.apache.jsp.axis2_002dweb.include.httpbase_jsp.jspInit(org.apache.jsp.axis2_002dweb.include.httpbase_jsp:22) org.apache.jasper.runtime.HttpJspBase.init(HttpJspBase.java:78) org.apache.jasper.servlet.JspServletWrapper.getServlet(JspServletWrapper.java:155) org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:315) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:966) org.apache.jsp.axis2_002dweb.index_jsp._jspService(org.apache.jsp.axis2_002dweb.index_jsp:67) org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:332) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) note The full stack trace of the root cause is available in the Apache Tomcat/5.5.15 logs. Apache Tomcat/5.5.15 -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-1912) java2WSDL.bat needs to use existing CLASSPATH as well
java2WSDL.bat needs to use existing CLASSPATH as well - Key: AXIS2-1912 URL: http://issues.apache.org/jira/browse/AXIS2-1912 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: codegen, wsdl Affects Versions: 1.1, 1.2, 1.1.1 Environment: Windows Reporter: Manoj Khangaonkar Users may have an existing environment variable CLASSPATH - that points to the current directory and other directories as well as other jars. java2WSDL.bat needs to append the existing classpath to AXIS2_CLASS_PATH as in set AXIS2_CLASS_PATH=%CLASSPATH%;%AXIS2_HOME% This saves user the trouble of adding multiple -cp options at the command line. Attached is an updated java2WSDL.bat as a patch. java2wsdl.sh already does the same -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-1912) java2WSDL.bat needs to use existing CLASSPATH as well
[ http://issues.apache.org/jira/browse/AXIS2-1912?page=all ] Manoj Khangaonkar updated AXIS2-1912: - Attachment: java2wsdl.bat Attaching as updated java2wsdl.bat as a patch java2WSDL.bat needs to use existing CLASSPATH as well - Key: AXIS2-1912 URL: http://issues.apache.org/jira/browse/AXIS2-1912 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: wsdl, codegen Affects Versions: 1.1, 1.2, 1.1.1 Environment: Windows Reporter: Manoj Khangaonkar Attachments: java2wsdl.bat Users may have an existing environment variable CLASSPATH - that points to the current directory and other directories as well as other jars. java2WSDL.bat needs to append the existing classpath to AXIS2_CLASS_PATH as in set AXIS2_CLASS_PATH=%CLASSPATH%;%AXIS2_HOME% This saves user the trouble of adding multiple -cp options at the command line. Attached is an updated java2WSDL.bat as a patch. java2wsdl.sh already does the same -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-1714) AXIS2 V1.1: java2wsdl.bat does not work.
[ http://issues.apache.org/jira/browse/AXIS2-1714?page=comments#action_12459504 ] Manoj Khangaonkar commented on AXIS2-1714: -- 1. I notice you are running from the src directory. I hope you understand that java2WSDL works of compiled code. .class file needs to be there 2. The class file must be found by the classloader from the class path. Try using the -cp to add the necessary classpath. If the problem still exists, please attach you sample. The link you have no longer works. Manoj AXIS2 V1.1: java2wsdl.bat does not work. - Key: AXIS2-1714 URL: http://issues.apache.org/jira/browse/AXIS2-1714 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: wsdl Affects Versions: 1.1 Environment: Win XP, IBM JDK 1.5 Reporter: Michael Moser The wsdl2java.bat does not work for me. I spiced it up with a few more echo ... statements and all names, the paths and the command line looks fine to me, but all it ever produced so far was: An error occured while generating codejava.lang.ClassNotFoundException: org.dailymoon.classifieds.ClassifiedService (I'm going through the classified ads example in the tutorial at http://www-128.ibm.com/developerworks/edu/ws-dw-ws-understand-web-services2.html). How to regenerate: 1.) I extracted the axis2 bin distribution to C:\Java_Extensions\axis2-1.1' 2.) My example is located under C:\JavaDevt\tutorials\webservices\ClassifiedAds\src, 3.) The actual .java file to be translated is C:\JavaDevt\tutorials\webservices\ClassifiedAds\src\org\dailymoon\classifieds\ClassifiedService.java 4.) I created a two-line .bat file: set AXIS2_HOME=C:\Java_Extensions\axis2-1.1 %AXIS2_HOME%\bin\java2wsdl.bat -cn org.dailymoon.classifieds.ClassifiedService -o . When I excute this I get: C:\JavaDevt\tutorials\webservices\ClassifiedAds\srcgenerateWSDL.bat C:\JavaDevt\tutorials\webservices\ClassifiedAds\srcset AXIS2_HOME=C:\Java_Extensions\axis2-1.1 C:\JavaDevt\tutorials\webservices\ClassifiedAds\srcC:\Java_Extensions\axis2-1.1\bin\java2wsdl.bat -cn org.dailymoon.classifieds.ClassifiedService -o . Using AXIS2_HOME: C:\Java_Extensions\axis2-1.1 Using JAVA_HOME:C:\IBMJSDK1.5.0 Using AXIS2_CLASS_PATH: C:\Java_Extensions\axis2-1.1;C:\Java_Extensions\axis2-1.1\lib\activation-1.1.jar;C:\Java_Extensions\axis2-1 .1\lib\annogen-0.1.0.jar;C:\Java_Extensions\axis2-1.1\lib\axiom-api-1.2.jar;C:\Java_Extensions\axis2-1.1\lib\axiom-dom-1.2.jar;C:\Ja va_Extensions\axis2-1.1\lib\axiom-impl-1.2.jar;C:\Java_Extensions\axis2-1.1\lib\axis2-adb-1.1.jar;C:\Java_Extensions\axis2-1.1\lib\a xis2-adb-codegen-1.1.jar;C:\Java_Extensions\axis2-1.1\lib\axis2-codegen-1.1.jar;C:\Java_Extensions\axis2-1.1\lib\axis2-java2wsdl-1.1 .jar;C:\Java_Extensions\axis2-1.1\lib\axis2-jibx-1.1.jar;C:\Java_Extensions\axis2-1.1\lib\axis2-kernel-1.1.jar;C:\Java_Extensions\ax is2-1.1\lib\axis2-saaj-1.1.jar;C:\Java_Extensions\axis2-1.1\lib\axis2-soapmonitor-1.1.jar;C:\Java_Extensions\axis2-1.1\lib\axis2-spr ing-1.1.jar;C:\Java_Extensions\axis2-1.1\lib\axis2-tools-1.1.jar;C:\Java_Extensions\axis2-1.1\lib\axis2-xmlbeans-1.1.jar;C:\Java_Ext ensions\axis2-1.1\lib\backport-util-concurrent-2.2.jar;C:\Java_Extensions\axis2-1.1\lib\commons-codec-1.3.jar;C:\Java_Extensions\axi s2-1.1\lib\commons-fileupload-1.1.1.jar;C:\Java_Extensions\axis2-1.1\lib\commons-httpclient-3.0.1.jar;C:\Java_Extensions\axis2-1.1\l ib\commons-io-1.2.jar;C:\Java_Extensions\axis2-1.1\lib\commons-logging-1.1.jar;C:\Java_Extensions\axis2-1.1\lib\geronimo-spec-jms-1. 1-rc4.jar;C:\Java_Extensions\axis2-1.1\lib\jakarta-httpcore-4.0-alpha2.jar;C:\Java_Extensions\axis2-1.1\lib\jaxen-1.1-beta-10.jar;C: \Java_Extensions\axis2-1.1\lib\jibx-bind-1.1.2.jar;C:\Java_Extensions\axis2-1.1\lib\jibx-run-1.1.2.jar;C:\Java_Extensions\axis2-1.1\ lib\mail-1.4.jar;C:\Java_Extensions\axis2-1.1\lib\neethi-2.0.jar;C:\Java_Extensions\axis2-1.1\lib\servletapi-2.3.jar;C:\Java_Extensi ons\axis2-1.1\lib\stax-api-1.0.1.jar;C:\Java_Extensions\axis2-1.1\lib\woden-1.0.0M6.jar;C:\Java_Extensions\axis2-1.1\lib\wsdl4j-1.6. 1.jar;C:\Java_Extensions\axis2-1.1\lib\wstx-asl-3.0.1.jar;C:\Java_Extensions\axis2-1.1\lib\xalan-2.7.0.jar;C:\Java_Extensions\axis2- 1.1\lib\xbean-2.2.0.jar;C:\Java_Extensions\axis2-1.1\lib\xercesImpl-2.8.1.jar;C:\Java_Extensions\axis2-1.1\lib\xml-apis-1.3.03.jar;C :\Java_Extensions\axis2-1.1\lib\XmlSchema-1.2.jar An error occured while generating codejava.lang.ClassNotFoundException: org.dailymoon.classifieds.ClassifiedService C:\JavaDevt\tutorials\webservices\ClassifiedAds\src Michael -- 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: (AXIS2-1793) class AntCodegenTask has incorrect package name
[ http://issues.apache.org/jira/browse/AXIS2-1793?page=comments#action_12457518 ] Manoj Khangaonkar commented on AXIS2-1793: -- In my latest extract of source code the code is compiled to a directory structure that matches the package name. Looks like someone fixed this. The code is obviously built using the -sourcepath and -d options in javac. Can someone explain why the source directory structure does not match the package name ? Otherwise the issue may be closed. class AntCodegenTask has incorrect package name --- Key: AXIS2-1793 URL: http://issues.apache.org/jira/browse/AXIS2-1793 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: Tools Affects Versions: 1.2 Environment: Windows Reporter: Manoj Khangaonkar Attachments: AntCodegenTask.java Path is org/apache/axis2/ant/AntCodegenTask.java but package name is org.apache.axis2.tool.ant I have no idea how this built. But this causes the build target ant generate.service generate.client to fail in the quick start samples. I changed the package name to org.apache.axis2.ant in AntCodegenTask and in the build.xmls and then the quickstart samples work. If we agree on the package name , and the build.xml of the quick start samples need to be changed - I willopen another JIRA for that -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-1793) class AntCodegenTask has incorrect package name
class AntCodegenTask has incorrect package name --- Key: AXIS2-1793 URL: http://issues.apache.org/jira/browse/AXIS2-1793 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: Tools Affects Versions: 1.2 Environment: Windows Reporter: Manoj Khangaonkar Path is org/apache/axis2/ant/AntCodegenTask.java but package name is org.apache.axis2.tool.ant I have no idea how this built. But this causes the build target ant generate.service generate.client to fail in the quick start samples. I changed the package name to org.apache.axis2.ant in AntCodegenTask and in the build.xmls and then the quickstart samples work. If we agree on the package name , and the build.xml of the quick start samples need to be changed - I willopen another JIRA for that -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-1793) class AntCodegenTask has incorrect package name
[ http://issues.apache.org/jira/browse/AXIS2-1793?page=all ] Manoj Khangaonkar updated AXIS2-1793: - Attachment: AntCodegenTask.java Patch attached. Attached is the updated file with the correct package name. class AntCodegenTask has incorrect package name --- Key: AXIS2-1793 URL: http://issues.apache.org/jira/browse/AXIS2-1793 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: Tools Affects Versions: 1.2 Environment: Windows Reporter: Manoj Khangaonkar Attachments: AntCodegenTask.java Path is org/apache/axis2/ant/AntCodegenTask.java but package name is org.apache.axis2.tool.ant I have no idea how this built. But this causes the build target ant generate.service generate.client to fail in the quick start samples. I changed the package name to org.apache.axis2.ant in AntCodegenTask and in the build.xmls and then the quickstart samples work. If we agree on the package name , and the build.xml of the quick start samples need to be changed - I willopen another JIRA for that -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-1794) QuickStart Samples adb,xmlbean have a problem in build.xml invoking ant codegen task
QuickStart Samples adb,xmlbean have a problem in build.xml invoking ant codegen task Key: AXIS2-1794 URL: http://issues.apache.org/jira/browse/AXIS2-1794 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: samples, build,site Affects Versions: 1.2 Environment: window Reporter: Manoj Khangaonkar The build.xml specify the classname as org.apache.axis2.tool.ant.AntCodegenTask You get class not found errror. But the correct path should be org.apache.axis2.ant.AntCodegenTask -- See JIRA - 1793 -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-1794) QuickStart Samples adb,xmlbean have a problem in build.xml invoking ant codegen task
[ http://issues.apache.org/jira/browse/AXIS2-1794?page=all ] Manoj Khangaonkar updated AXIS2-1794: - Attachment: build.xml fix for quickstart adb QuickStart Samples adb,xmlbean have a problem in build.xml invoking ant codegen task Key: AXIS2-1794 URL: http://issues.apache.org/jira/browse/AXIS2-1794 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: samples, build,site Affects Versions: 1.2 Environment: window Reporter: Manoj Khangaonkar Attachments: build.xml, build.xml The build.xml specify the classname as org.apache.axis2.tool.ant.AntCodegenTask You get class not found errror. But the correct path should be org.apache.axis2.ant.AntCodegenTask -- See JIRA - 1793 -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-1794) QuickStart Samples adb,xmlbean have a problem in build.xml invoking ant codegen task
[ http://issues.apache.org/jira/browse/AXIS2-1794?page=all ] Manoj Khangaonkar updated AXIS2-1794: - Attachment: build.xml fix for quickstartxmlbeans is attached QuickStart Samples adb,xmlbean have a problem in build.xml invoking ant codegen task Key: AXIS2-1794 URL: http://issues.apache.org/jira/browse/AXIS2-1794 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: samples, build,site Affects Versions: 1.2 Environment: window Reporter: Manoj Khangaonkar Attachments: build.xml, build.xml The build.xml specify the classname as org.apache.axis2.tool.ant.AntCodegenTask You get class not found errror. But the correct path should be org.apache.axis2.ant.AntCodegenTask -- See JIRA - 1793 -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-1734) Build fails
[ http://issues.apache.org/jira/browse/AXIS2-1734?page=all ] Manoj Khangaonkar updated AXIS2-1734: - Attachment: wss4j-SNAPSHOT.jar Attached a wss4j-SNAPSHOT for people to use while the build is fixed. Just drop this in your local repository Build fails --- Key: AXIS2-1734 URL: http://issues.apache.org/jira/browse/AXIS2-1734 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: samples, build,site Affects Versions: 1.1 Environment: Windows XP, cygwin, JDK1.5 Reporter: Vijay Phadke Attachments: wss4j-SNAPSHOT.jar The build fails with following error - multiproject:install-callback: [echo] Running jar:install for Apache Axis 2.0 - Rahas java:prepare-filesystem: [mkdir] Created dir: C:\dev\open-source\axis2\java\v1.1\modules\rahas\target \classes Running post goal: java:prepare-filesystem java:compile: [echo] Compiling to c:\dev\open-source\axis2\java\v1.1\modules\rahas/target/ classes [javac] Compiling 23 source files to C:\dev\open-source\axis2\java\v1.1\modu les\rahas\target\classes [javac] C:\dev\open-source\axis2\java\v1.1\modules\rahas\src\org\apache\raha s\impl\SAMLTokenIssuer.java:113: cannot find symbol [javac] symbol : method getInstance(java.util.Properties,java.lang.ClassLoa der) [javac] location: class org.apache.ws.security.components.crypto.CryptoFacto ry [javac] crypto = CryptoFactory.getInstance(TrustUtil.toPropertie s(config.cryptoPropertiesElement), [javac] ^ [javac] C:\dev\open-source\axis2\java\v1.1\modules\rahas\src\org\apache\raha s\impl\SCTIssuer.java:235: cannot find symbol [javac] symbol : variable KEY_CONTEXT_MAP [javac] location: class org.apache.ws.security.conversation.ConversationCons tants [javac] ConversationConstants.KEY_CONTEXT_MAP); [javac] ^ [javac] C:\dev\open-source\axis2\java\v1.1\modules\rahas\src\org\apache\raha s\impl\SCTIssuer.java:242: cannot find symbol [javac] symbol : variable KEY_CONTEXT_MAP [javac] location: class org.apache.ws.security.conversation.ConversationCons tants [javac] ConversationConstants.KEY_CONTEXT_MAP, map); [javac] ^ [javac] C:\dev\open-source\axis2\java\v1.1\modules\rahas\src\org\apache\raha s\impl\TokenIssuerUtil.java:111: cannot find symbol [javac] symbol : method getInstance(java.util.Properties,java.lang.ClassLoa der) [javac] location: class org.apache.ws.security.components.crypto.CryptoFacto ry [javac] crypto = CryptoFactory.getInstance(TrustUtil.toP roperties(config.cryptoPropertiesElement), [javac] ^ [javac] 4 errors BUILD FAILED File.. c:\dev\maven-1.1-beta-2\cache\maven-multiproject-plugin-1.4.1\plugin. jelly Element... maven:reactor Line.. 218 Column 9 Unable to obtain goal [multiproject:install-callback] -- c:\dev\maven-1.1-beta-2 \cache\maven-java-plugin-1.5\plugin.jelly:63:48: ant:javac Compile failed; see the compiler error output for details. Total time : 1 minutes 14 seconds -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-1577) User guide Page 3 : Writing Web service clients using code generation
[ http://issues.apache.org/jira/browse/AXIS2-1577?page=comments#action_12447330 ] Manoj Khangaonkar commented on AXIS2-1577: -- This is a 1.0 issue only. It appears fixed in the 1.1 documentation and can be closed. User guide Page 3 : Writing Web service clients using code generation - Key: AXIS2-1577 URL: http://issues.apache.org/jira/browse/AXIS2-1577 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: documentation Affects Versions: 1.0, 1.1 Environment: windows Reporter: Manoj Khangaonkar Priority: Minor The userguide says , generate stubs using the command WSDL2Java -uri ..\samples\wsdl\Axis2SampleDocLit.wsdl -o ..\samples\src -p org.apache.axis2.userguide However this generates the stub with default databinding ADB. The subsequent sample code on the same page echoString, echoStringArray etc are written assuming xmlbeans databinding and will not compile. For echoString to work as is, the stub needs to be generated using the -d xmlbeans option as below WSDL2Java -uri ..\samples\wsdl\Axis2SampleDocLit.wsdl -d xmlbeans -o ..\samples\src -p org.apache.axis2.userguide -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
