Re: [AXIS2C][WSDL2C] close to despair

2007-06-12 Thread Dr. Florian Steinborn

Hi Samisa,



I never had problems in compiling the Axis2c sources. But when I check  
out the latest svn I have to run the autoconf.sh because there is no  
configure-script.
I have uploaded a nightly build today at :  
http://people.apache.org/dist/axis2/nightly/c/


With this, you will be able to run ./configure

Please try that.



thanks for the quick reply. Unfortunately there was no change - the same  
error happens again



Flori





When I run the configure script afterwards it fails with

+Error start +

checking for LIBXML2... configure: error: The pkg-config script could  
not be found or is too old.  Make sure it

is in your PATH or set the PKG_CONFIG environment variable to the full
path to pkg-config.

Alternatively you may set the LIBXML2_CFLAGS and LIBXML2_LIBS  
environment variables

to avoid the need to call pkg-config.  See the pkg-config man page for
more details.
configure: error: /bin/sh './configure' failed for axiom

+Error end +

It was no error with the other releases. The installed version of  
libxml2 is 2.6.20 and the system is a Suse Linux 10.0.


Thanks,
Flori

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









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



Re: [AXIS2C][WSDL2C] close to despair

2007-06-12 Thread Samisa Abeysinghe

Dr. Florian Steinborn wrote:

Hi Samisa,



I never had problems in compiling the Axis2c sources. But when I 
check out the latest svn I have to run the autoconf.sh because there 
is no configure-script.
I have uploaded a nightly build today at : 
http://people.apache.org/dist/axis2/nightly/c/


With this, you will be able to run ./configure

Please try that.



thanks for the quick reply. Unfortunately there was no change - the 
same error happens again

What is your 'pkg-config --version'?
Also did you try setting the LIBXML2_CFLAGS and LIBXML2_LIBS environment
variables?

Samisa...

--
Samisa Abeysinghe : http://www.wso2.org/ (WSO2 Oxygen Tank - Web 
Services Developers' Portal)




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



problem while using any element with axis2c

2007-06-12 Thread Sampath Kannan
Hi

We were trying to generate using wsdl2c. The wsdl files are from
axis1.x java. When we use axis2java it works fine, but

while trying out with wsdl2c we get errors. The error seems to point to
the element any (when we comment that line it generates fine). Below are
the wsdl file snip and the trace.

Any help would be much appreciated.

 

Thanks

Sampath Kannan

 

SNIP

wsdl:types

schema xmlns=http://www.w3.org/2001/XMLSchema;

targetNamespace=urn:services.ws.core.collabnet.com

elementFormDefault=qualified

import namespace=http://xml.apache.org/xml-soap/

element name=request

complexType

sequence

any minOccurs=1 maxOccurs=1/

/sequence

/complexType

/element

element name=response

complexType

sequence

any minOccurs=1 maxOccurs=1/

/sequence

/complexType

/element

/schema

/wsdl:types

SNIP

 

Exception Trace:

 

Retrieving document at 'exception.wsdl-import', relative to
'file:/d:/myspace/pr

ojects/Connectors/wsdl/wsdl/'.

Retrieving document at 'exception.wsdl-import', relative to
'file:/d:/myspace/pr

ojects/Connectors/wsdl/wsdl/'.

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(CodeGener

ationEngine.java:256)

at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32)

at org.apache.axis2.wsdl.WSDL2C.main(WSDL2C.java:28)

Caused by: java.lang.RuntimeException:
java.lang.reflect.InvocationTargetExcepti

on

at
org.apache.axis2.wsdl.codegen.extension.SimpleDBExtension.engage(Simp

leDBExtension.java:50)

at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGener

ationEngine.java:209)

... 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(DelegatingMethodAcces

sorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:585)

at
org.apache.axis2.wsdl.codegen.extension.SimpleDBExtension.engage(Simp

leDBExtension.java:47)

... 3 more

Caused by: org.apache.axis2.schema.SchemaCompilationException:
java.lang.NullPoi

nterException

at
org.apache.axis2.schema.writer.CStructWriter.write(CStructWriter.java

:169)

at
org.apache.axis2.schema.SchemaCompiler.writeElement(SchemaCompiler.ja

va:439)

at
org.apache.axis2.schema.SchemaCompiler.compile(SchemaCompiler.java:31

1)

at
org.apache.axis2.schema.SchemaCompiler.compile(SchemaCompiler.java:21

0)

at
org.apache.axis2.schema.ExtensionUtility.invoke(ExtensionUtility.java

:75)

... 8 more

Caused by: java.lang.NullPointerException

at
org.apache.axis2.schema.writer.CStructWriter.addPropertyEntries(CStru

ctWriter.java:612)

at
org.apache.axis2.schema.writer.CStructWriter.populateInfo(CStructWrit

er.java:503)

at
org.apache.axis2.schema.writer.CStructWriter.getBeanElement(CStructWr

iter.java:426)

at
org.apache.axis2.schema.writer.CStructWriter.process(CStructWriter.ja

va:315)

at
org.apache.axis2.schema.writer.CStructWriter.write(CStructWriter.java

:167)

... 12 more

 



Re: [AXIS2C][WSDL2C] close to despair

2007-06-12 Thread Dr. Florian Steinborn

Hi Samisa,



thanks for the quick reply. Unfortunately there was no change - the  
same error happens again

What is your 'pkg-config --version'?
Also did you try setting the LIBXML2_CFLAGS and LIBXML2_LIBS environment
variables?


I can check this out this evening at my home machine. I was just wondering  
why the error suddenly arises - there was no problem with the ordinary  
Axis2C 1.0 download so I thought something changed in the generator  
sources...


When you tell me how the LIBXML2_CFLAGS and the LIBXML2_LIBS vars have to  
look like I can test that way as well...


Thanks,
Flori

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



Problems while compiling using axis2c

2007-06-12 Thread Sampath Kannan
Folks

   We generated c files using wsdl2c available with axis2. The generated
code has some variables and function calls like

axis2_env_t , axis2_qname_t  and axis2_qname_create(). While we tried to
compile the generated code it was throwing errors. 

After digging up a bit we found that by changing axis2 prefixes to
axutil, it was compiling. We also did some googling and found that 

some other project which uses axis2c had the same problem. Even after
compiling we were getting linker errors. Are we doing any mistakes here?
the

flags we used to generate the code is  wsdl2c -uri wsdl  -d adb -u .
We were trying to use wsdl files generated by axis1.x java. Any
immediate help is much appreciated.

 

Thanks

Sampath Kannan

 

 

 

 



Re: Problems while compiling using axis2c

2007-06-12 Thread Dr. Florian Steinborn

Hi Sampath,

you googled, you found the questions, but not the answers?
If you look into the archive of the axis-c-user list you will find my  
question with the subject types axutil_env_t vs. axis2_env_t


The answer is: download the latest nightly build of Axis2. The generation  
should then be using the new type names.


Concering the linker I do not know - maybe the linker errors could be  
informative.


Regards,
Flori

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



Re: [AXIS2C]: How to implement business logic in C++?

2007-06-12 Thread Yingwei Yang

Hi Dumindu,

After several tries, I found out the segmentation error is because I updated
the libhello.so file but didn't restart the axis2_http_server.

It is not a permission issue.

Thanks.
Yingwei

On 6/11/07, Dumindu Pallewela [EMAIL PROTECTED] wrote:


Yingwei Yang wrote:
 Hi Dinesh,

 Thank you very much for the reply. I just realized that I didn't run the
 axis2_http_server with the correct permission, which caused the error I
 mentioned above. and no log files been written because of the lack of
 permission.

Hi Yang and Dinesh,

I don't think that the axis2_http_server should seg fault on a
permissions issue. When I try to run the server without write
permissions for log file, it instead is written to the standard output.

I guess that this _might_ possibly be a bug. If you could please provide
more details on how the seg fault could be recreated.

-Dumindu.

 Now it runs fine. :)
 Thanks.

 On 6/11/07, *Dinesh Premalal* [EMAIL PROTECTED]
 mailto:[EMAIL PROTECTED] wrote:

 Hi Yingwei,

 Yingwei Yang [EMAIL PROTECTED]
 mailto:[EMAIL PROTECTED] writes:
   then I got the Segmentation fault at the Invoke the handler
 context_handler
   within the phase PostDispatch phase.
  
   what did I do wrong? is it possible to implement the service
 skeleton code in
   C++?

 I think it is possible, in order to determine what has happened in
 your case we need some more details.

 1. Are you sure about your service.xml ? What is the directory name
 that you use to put your service?

 2. Can you provide us your axis2.log , Please make sure to run
server
 in debug mode.

 3. It would be great if you could send us gdb backtrace.

 thanks,
 Dinesh
 --
 Dinesh Premalal
 http://xydinesh.wordpress.com
 GPG ID : A255955C
 GPG Key Finger Print : C481 E5D4 C27E DC34 9257  0229 4F44 266E A255
 955C


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




 --
 Yingwei Yang


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





--
Yingwei Yang


Re: [AXIS2C]: How to implement business logic in C++?

2007-06-12 Thread Dumindu Pallewela

Yingwei Yang wrote:

Hi Dumindu,

After several tries, I found out the segmentation error is because I 
updated the libhello.so file but didn't restart the axis2_http_server.


It is not a permission issue.


That's good news :)

Thanks for the feedback.

-Dumindu.



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