[AXIS2] PHP extension for axis2 - automake/autoconf problems
I have been looking into getting this PHP binding code working on Linux.
The PHP source depends on autoconf-2.13 and automake-1.5.
Our build system is based on autoconf-2.59 and automake-1.9
This is a problem when it comes to working on both axis2c and PHP
extentions on the same machine :(
Thanks,
Samisa...
nandika jayawardana wrote:
Hi all,
I have started writing a php extension for axis2c starting with om.
For that I have added axis2_xml_reader api in this extension.
Lot has to be done before everything in axis2 is supported.
Pls commit this code.
I think we can put it in a folder named c/bindings/php .
Thanks
nandika
#ifndef AXIS2_CE_H
#define AXIS2_CE_H
zend_class_entry *axis2_xml_reader_class_entry;
zend_class_entry *axis2_xml_writer_class_entry;
zend_class_entry *axis2_om_element_class_entry;
zend_class_entry *axis2_om_comment_class_entry;
zend_class_entry *axis2_om_text_class_entry;
zend_class_entry *axis2_om_pi_entry;
zend_class_entry *axis2_om_stax_builder_class_entry;
zend_class_entry *axis2_om_document_class_entry;
zend_class_entry *axis2_om_attribute_class_entry;
zend_class_entry *axis2_om_namespace_class_entry;
#endif /* AXIS2_CE_H */
#ifndef AXIS2_PROPERTIES_H
#define AXIS2_PROPERTIES_H
#endif /* AXIS2_PROPERTIES_H */
/*
+--+
| PHP Version 5|
+--+
| Copyright (c) 1997-2004 The PHP Group|
+--+
| This source file is subject to version 3.0 of the PHP license, |
| that is bundled with this package in the file LICENSE, and is|
| available through the world-wide-web at the following url: |
| http://www.php.net/license/3_0.txt. |
| If you did not receive a copy of the PHP license and are unable to |
| obtain it through the world-wide-web, please send a note to |
| [EMAIL PROTECTED] so we can mail you a copy immediately. |
+--+
| Author: |
+--+
*/
/* $Id: header,v 1.15 2004/01/08 16:46:52 sniper Exp $ */
#ifdef HAVE_CONFIG_H
#include config.h
#endif
#include php.h
#include php_ini.h
#include ext/standard/info.h
#include php_axis2.h
#include axis2_env.h
#include axis2_error_default.h
#include axis2_stream_default.h
#include axis2_log_default.h
zend_object_value axis2_objects_new(zend_class_entry *class_type TSRMLS_DC );
/* If you declare any globals in php_axis2.h uncomment this:
*/
ZEND_DECLARE_MODULE_GLOBALS(axis2)
/* True global resources - no need for thread safety here */
static int le_axis2;
static zend_object_handlers axis2_object_handlers;
/* {{{ axis2_functions[]
*
* Every user visible function must have an entry in axis2_functions[].
*/
function_entry axis2_functions[] = {
PHP_FE(axis2_helloworld,NULL)
{NULL, NULL, NULL} /* Must be the last line in axis2_functions[] */
};
/* }}} */
/* {{{ axis2_module_entry
*/
zend_module_entry axis2_module_entry = {
#if ZEND_MODULE_API_NO = 20010901
STANDARD_MODULE_HEADER,
#endif
axis2,
axis2_functions,
PHP_MINIT(axis2),
PHP_MSHUTDOWN(axis2),
PHP_RINIT(axis2), /* Replace with NULL if there's nothing
to do at request start */
PHP_RSHUTDOWN(axis2), /* Replace with NULL if there's nothing to do
at request end */
PHP_MINFO(axis2),
#if ZEND_MODULE_API_NO = 20010901
0.1, /* Replace with version number for your extension */
#endif
STANDARD_MODULE_PROPERTIES
};
/* }}} */
#ifdef COMPILE_DL_AXIS2
ZEND_GET_MODULE(axis2)
#endif
/* {{{ PHP_INI
*/
/* Remove comments and fill if you need to have entries in php.ini
PHP_INI_BEGIN()
STD_PHP_INI_ENTRY(axis2.global_value, 42, PHP_INI_ALL,
OnUpdateLong, global_value, zend_axis2_globals, axis2_globals)
STD_PHP_INI_ENTRY(axis2.global_string, foobar, PHP_INI_ALL,
OnUpdateString, global_string, zend_axis2_globals, axis2_globals)
PHP_INI_END()
*/
/* }}} */
/* {{{ php_axis2_init_globals
*/
static void php_axis2_init_globals(zend_axis2_globals *axis2_globals)
{
axis2_allocator_t *allocator = NULL;
axis2_error_t *err = NULL;
axis2_log_t *log = NULL;
axis2_stream_t *stream = NULL;
axis2_env_t *environment = NULL;
allocator = axis2_allocator_init (NULL);
log = axis2_log_create(allocator, NULL);
stream = axis2_stream_create(allocator,
Re: [Axis2] Deployment packaging
Deepal, i already did. -- dims On 12/3/05, Deepal Jayasinghe [EMAIL PROTECTED] wrote: Thank you very much for the patch, I will apply that. Thanks, Deepal ~Future is Open~ - Original Message - From: Alex Artigues [EMAIL PROTECTED] To: axis-dev@ws.apache.org Sent: Saturday, December 03, 2005 12:12 AM Subject: Re: [Axis2] Deployment packaging A patch would be awesome!! we could possibly help with perf testing as well if we see the patch. And here it is! This patch does not include any attempts at optimization. It addresses the following issues: 1) Resources cannot be loaded from jars inside of the service .aar getResourceAsStream() has been overridden to allow this. 2) ZipInputStreams were left open by getBytes() if the target was not found. An additional try/catch block has been added after the search loop to make sure this happens. 3) Minor change in findLibJars() to normalize the path for startsWith() and endsWith() checks. What's missing from this patch is optimization code to address the extended loading times of the DeploymentClassLoader. We still don't know how to best deal with this. We forgot to extend a big Thank You to everyone out there working on this project in the last post. Thanks! --Alex Ralf [EMAIL PROTECTED] [EMAIL PROTECTED] ### Sidenote: Should we post this to JIRA also? -- Davanum Srinivas : http://wso2.com/blogs/
RE: [jira] Resolved: (AXIS-2305) Axis Fault : java.net.SocketException Connection reset
Hi Dims,
Is this fix available, I am running the same issue???
Thanks,
Parikh, Pratik
-Original Message-
From: Davanum Srinivas (JIRA) [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 29, 2005 9:13 AM
To: axis-dev@ws.apache.org
Subject: [jira] Resolved: (AXIS-2305) Axis Fault :
java.net.SocketException Connection reset
[ http://issues.apache.org/jira/browse/AXIS-2305?page=all ]
Davanum Srinivas resolved AXIS-2305:
Resolution: Duplicate
duplicate.
Axis Fault : java.net.SocketException Connection reset
--
Key: AXIS-2305
URL: http://issues.apache.org/jira/browse/AXIS-2305
Project: Apache Axis
Type: Bug
Versions: 1.3
Environment: Tested on Solaris 8 and Win 2000 Prof
Reporter: Heemanshu Jain
Priority: Blocker
Hi,
I am using Apache Axis 1.3 and JDK 1.5 to consume web services
from a SOAP webserver.
I have a loop which executes every 5 seconds and makes a call to
the web service.
The code works fine for a few requests but I get this error after
some requests at regular intervals. Nearly 1 failure in 50 requests.
I have another program written in plain java code. This program is
executing with no errors. This proves that there is no problem at the
server side. (This program has hardcoded SOAP request so cannot use this
plain java code for production).
Is this a known bug. Is there any workaround for the same
AxisFault
faultCode:
{http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: java.net.SocketException: Connection reset
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace:java.net.SocketException:
Connec tion reset
at java.net.SocketInputStream.read(Unknown Source)
at java.io.BufferedInputStream.fill(Unknown Source)
at java.io.BufferedInputStream.read(Unknown Source)
at
org.apache.axis.transport.http.HTTPSender.readHeadersFromSocket(HTTPS
ender.java:583)
at
org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:143)
at
org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrateg
y.java:32)
at
org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at
org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
at org.apache.axis.client.Call.invoke(Call.java:2767)
at org.apache.axis.client.Call.invoke(Call.java:2443)
at org.apache.axis.client.Call.invoke(Call.java:2366)
at org.apache.axis.client.Call.invoke(Call.java:1812)
at
com.bt.www.mta._2005._09.MTASoapPortStub.requestCheck(MTASoapPortStub
.java:298)
at
com.bt.www.mta.types._2005._09.Main4test.main(Main4test.java:92)
{http://xml.apache.org/axis/}hostname:DSCP07364
java.net.SocketException: Connection reset
at org.apache.axis.AxisFault.makeFault(AxisFault.java:101)
at
org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:154)
at
org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrateg
y.java:32)
at
org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at
org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
at org.apache.axis.client.Call.invoke(Call.java:2767)
at org.apache.axis.client.Call.invoke(Call.java:2443)
at org.apache.axis.client.Call.invoke(Call.java:2366)
at org.apache.axis.client.Call.invoke(Call.java:1812)
at
com.bt.www.mta._2005._09.MTASoapPortStub.requestCheck(MTASoapPortStub
.java:298)
at
com.bt.www.mta.types._2005._09.Main4test.main(Main4test.java:92)
Caused by: java.net.SocketException: Connection reset
at java.net.SocketInputStream.read(Unknown Source)
at java.io.BufferedInputStream.fill(Unknown Source)
at java.io.BufferedInputStream.read(Unknown Source)
at
org.apache.axis.transport.http.HTTPSender.readHeadersFromSocket(HTTPS
ender.java:583)
at
org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:143)
... 11 more
Please help.
I need to have this running asap.
Thanks in advance.
Heemanshu
--
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
CONFIDENTIALITY NOTICE
This message and any included attachments
are from Cerner Corporation and are intended
only for the addressee. The information
TCP transport interop with WCF: WSDL?
Hi everybody, I just joined this list to help you testing interop with WCF/Indigo when it comes to the TCP transport. In order to be able to test the interaction in a senseful way we need WSDL generation from Axis2. AFAIK, this is not yet available in 0.93. Is there any way to get at least some experimnetal version of this? Thanks - let's rock on :) Cheers, --- Christian Weyer WSCF - Web Services Contract-First, for real! http://www.thinktecture.com/WSCF/ jWSCF - Web Services Interface Design for Java and the Eclipse IDE http://blogs.thinktecture.com/cweyer/archive/2005/08/06/414103.aspx
XML realted projects for Grad School?
Hello, What would be a good source (website or books or journals)for xml webservicesrelated projects which could be done for Grad school? Looking for ideas or a list of projects from which I could pick one as a Master's project ? Thanks in advance!!
Re: TCP transport interop with WCF: WSDL?
Christian, if you drop a service.wsdl in META-INF, that will be served from ?wsdl just like Axis1.X thanks, dims On 12/3/05, Christian Weyer [EMAIL PROTECTED] wrote: Hi everybody, I just joined this list to help you testing interop with WCF/Indigo when it comes to the TCP transport. In order to be able to test the interaction in a senseful way we need WSDL generation from Axis2. AFAIK, this is not yet available in 0.93. Is there any way to get at least some experimnetal version of this? Thanks - let's rock on :) Cheers, --- Christian Weyer WSCF - Web Services Contract-First, for real! http://www.thinktecture.com/WSCF/ jWSCF - Web Services Interface Design for Java and the Eclipse IDE http://blogs.thinktecture.com/cweyer/archive/2005/08/06/414103.aspx -- Davanum Srinivas : http://wso2.com/blogs/
Re: TCP transport interop with WCF: WSDL?
Team, Here's the background example from Axis1: http://blogs.msdn.com/smguest/articles/axistcp.aspx Christian, Looking forward to making it happen :) and working with you. thanks, dims On 12/3/05, Davanum Srinivas [EMAIL PROTECTED] wrote: Christian, if you drop a service.wsdl in META-INF, that will be served from ?wsdl just like Axis1.X thanks, dims On 12/3/05, Christian Weyer [EMAIL PROTECTED] wrote: Hi everybody, I just joined this list to help you testing interop with WCF/Indigo when it comes to the TCP transport. In order to be able to test the interaction in a senseful way we need WSDL generation from Axis2. AFAIK, this is not yet available in 0.93. Is there any way to get at least some experimnetal version of this? Thanks - let's rock on :) Cheers, --- Christian Weyer WSCF - Web Services Contract-First, for real! http://www.thinktecture.com/WSCF/ jWSCF - Web Services Interface Design for Java and the Eclipse IDE http://blogs.thinktecture.com/cweyer/archive/2005/08/06/414103.aspx -- Davanum Srinivas : http://wso2.com/blogs/ -- Davanum Srinivas : http://wso2.com/blogs/
Re: [Axis2]Support for the wsdl based dynamic invocation
Will do :) I get in to little trouble with it I think I should be creating Call and MessageSender Objects rather than InOutMEPClient and InOnlyMEPCleint as the latter accept message contexts and AxisOperations, as a result not very user fiendly . right? But if I choose the first I can not use the information avalible to me via the WSDL (like AxisOperation) as Call and MessageSender assume certain things (e.g. create a Dummy Operation by the name) What do you think and recommand? I am not sure which way to go Thanks Srinath On 12/3/05, Davanum Srinivas [EMAIL PROTECTED] wrote: Srinath, Could you please look at DynamicInvoker in Axis1 and add corresponding functionality in Axis2? I know tons of people who use/need that :) thanks, dims On 12/2/05, Srinath Perera [EMAIL PROTECTED] wrote: Hi All; I checked in a WSDLMEPClientBuilder, which can accept a WSDL and produce a configured MEPClient. It would be very useful for the dynamic invocation (e.g. running a work flow). We might need to discuss the interfaces in more detail, But I just go ahead and add it as it is completely standalone from the other things. Thanks Srinath -- Davanum Srinivas : http://wso2.com/blogs/
[Axis2] Configuration hierarchy no longer extends the WSDLComponents !
Hi, I was just observing that we no longer extend our Configuration (or Axis* , AxisOperation, etc) from the relevant WSDL component. eg AxisOperation (use to) extends WSDLOperation. I thought that was a nice thing to do because our WOM builder has the flexibility of building objects out of factory. That is you can ask the WOM builder to build a AxisOperation object rather than a WSDLOperation by registering a (AxisDescWSDLComponentFactory). IMO it is a cleaner way to build the configuration objects rather than keeping the object inside and delegating ALL the methods which it does right now. Is there any good reason why we did this change? Chathura On 12/1/05, Deepal Jayasinghe [EMAIL PROTECTED] wrote: Hi all; There was a class called MessageDescription to hold Message level information (like WS policy) , but there was no any usage of that class , So I removed that class and Added a new class called AxisMessage to do the same thing. In addition to that removed handler flow data from AxisOperation and moved that down to AxisMessage. So now there is a place holder to store WS-policy information at the message level as well. In the same time you can add message level parameters as well , the way of doing is my adding message element in operation as below; operation name=echoString message label=In parameter name=messageIN locked=falsemessageIN/parameter /message /operation I am sorry for send the mail after I doing this , I really forgot to send the mail Im really sorry for that. Thanks, Deepal ~Future is Open~ -- Chathura Herath http://www.bloglines.com/blog/chathurah
Re: svn commit: r348141 - /webservices/axis2/trunk/java/modules/saaj/src/org/apache/axis2/saaj/NodeImpl.java
Removed - r353805
Thanks,
ruchith
On 12/4/05, Davanum Srinivas [EMAIL PROTECTED] wrote:
Hmm...Please don't do this. If the NodeImpl class gets loaded the
ENTIRE JVM will start using our Document Builder Factory.
thanks,
-- dims
On 12/3/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Author: ruchithf
Date: Tue Nov 22 02:17:13 2005
New Revision: 348141
URL: http://svn.apache.org/viewcvs?rev=348141view=rev
Log:
Makeing the saaj imple use the OM-DOM Dom impl
Modified:
webservices/axis2/trunk/java/modules/saaj/src/org/apache/axis2/saaj/NodeImpl.java
Modified:
webservices/axis2/trunk/java/modules/saaj/src/org/apache/axis2/saaj/NodeImpl.java
URL:
http://svn.apache.org/viewcvs/webservices/axis2/trunk/java/modules/saaj/src/org/apache/axis2/saaj/NodeImpl.java?rev=348141r1=348140r2=348141view=diff
==
---
webservices/axis2/trunk/java/modules/saaj/src/org/apache/axis2/saaj/NodeImpl.java
(original)
+++
webservices/axis2/trunk/java/modules/saaj/src/org/apache/axis2/saaj/NodeImpl.java
Tue Nov 22 02:17:13 2005
@@ -21,6 +21,7 @@
import org.apache.axis2.om.OMNode;
import org.apache.axis2.om.OMText;
import org.apache.axis2.om.impl.OMNodeEx;
+import org.apache.axis2.om.impl.dom.jaxp.DocumentBuilderFactoryImpl;
import org.apache.axis2.util.Dom2OmUtils;
import org.w3c.dom.DOMException;
import org.w3c.dom.Document;
@@ -36,7 +37,12 @@
* Class NodeImpl
*/
public class NodeImpl implements Node {
-
+
+ static {
+
System.setProperty(javax.xml.parsers.DocumentBuilderFactory,DocumentBuilderFactoryImpl.class.getName());
+ }
+
+
/**
* Field omNode
*/
--
Davanum Srinivas : http://wso2.com/blogs/
--
Ruchith
Re: [Axis2]Support for the wsdl based dynamic invocation
Very good test for refactoring client package again? Your call, am still digesting all the changes. Of course we may have to tweak a wee bit again :) thanks, -- dims On 12/3/05, Srinath Perera [EMAIL PROTECTED] wrote: Will do :) I get in to little trouble with it I think I should be creating Call and MessageSender Objects rather than InOutMEPClient and InOnlyMEPCleint as the latter accept message contexts and AxisOperations, as a result not very user fiendly . right? But if I choose the first I can not use the information avalible to me via the WSDL (like AxisOperation) as Call and MessageSender assume certain things (e.g. create a Dummy Operation by the name) What do you think and recommand? I am not sure which way to go Thanks Srinath On 12/3/05, Davanum Srinivas [EMAIL PROTECTED] wrote: Srinath, Could you please look at DynamicInvoker in Axis1 and add corresponding functionality in Axis2? I know tons of people who use/need that :) thanks, dims On 12/2/05, Srinath Perera [EMAIL PROTECTED] wrote: Hi All; I checked in a WSDLMEPClientBuilder, which can accept a WSDL and produce a configured MEPClient. It would be very useful for the dynamic invocation (e.g. running a work flow). We might need to discuss the interfaces in more detail, But I just go ahead and add it as it is completely standalone from the other things. Thanks Srinath -- Davanum Srinivas : http://wso2.com/blogs/ -- Davanum Srinivas : http://wso2.com/blogs/
Re: TCP transport interop with WCF: WSDL?
Interesting...digging a bit more. WSE used DIME for framing (differentiate between 2 subsequent soap messages) and Indigo seems to use standard TCP framing. See here: http://beuchelt.blogdns.net:8080/2005/09/21/Framing+In+Indigo.aspx thanks, dims On 12/3/05, Davanum Srinivas [EMAIL PROTECTED] wrote: Team, Here's the background example from Axis1: http://blogs.msdn.com/smguest/articles/axistcp.aspx Christian, Looking forward to making it happen :) and working with you. thanks, dims On 12/3/05, Davanum Srinivas [EMAIL PROTECTED] wrote: Christian, if you drop a service.wsdl in META-INF, that will be served from ?wsdl just like Axis1.X thanks, dims On 12/3/05, Christian Weyer [EMAIL PROTECTED] wrote: Hi everybody, I just joined this list to help you testing interop with WCF/Indigo when it comes to the TCP transport. In order to be able to test the interaction in a senseful way we need WSDL generation from Axis2. AFAIK, this is not yet available in 0.93. Is there any way to get at least some experimnetal version of this? Thanks - let's rock on :) Cheers, --- Christian Weyer WSCF - Web Services Contract-First, for real! http://www.thinktecture.com/WSCF/ jWSCF - Web Services Interface Design for Java and the Eclipse IDE http://blogs.thinktecture.com/cweyer/archive/2005/08/06/414103.aspx -- Davanum Srinivas : http://wso2.com/blogs/ -- Davanum Srinivas : http://wso2.com/blogs/ -- Davanum Srinivas : http://wso2.com/blogs/
[jira] Resolved: (AXIS2-307) Generated stubs do not consistent with Call
[ http://issues.apache.org/jira/browse/AXIS2-307?page=all ] Eran Chinthaka resolved AXIS2-307: -- Resolution: Fixed This is fixed with the introduction of Options to the MEPClients. Generated stubs do not consistent with Call --- Key: AXIS2-307 URL: http://issues.apache.org/jira/browse/AXIS2-307 Project: Apache Axis 2.0 (Axis2) Type: Bug Components: databinding Reporter: Eran Chinthaka Assignee: Ajith Harshana Ranabahu Fix For: 0.93 It seems that we do always have inconsistency with the methods in the Call API and the methods in the Stub. IMO, all the methods that are in Call should be made available via stub. Current stub seems doesnot contain methods like setTimeOut. So shall we fix this ? Plus, one solution for this recurring problem is to use properties to pass parameters via the Call api, so that there is no need to add methods whenever Call changes. I think its better to use the properties from here on. But we need to fix the current problem. -- 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
