apache shared memory
Hello list, I have a strange behavior and hopefully someone can help me. I have implemented a simple service and I want to access the shared memory of the apache daemon. The service stores a object, which can perform some basic mathematical operations and store a value. In the first call of the service the shared variable is initialized and stored with a value in the shared memory. Every following call should get the shared variable, add two numbers and store it in the shared variable (setLaenge(int a) in myadd.cpp). The result should look like this: first call 10, second call 19, third call 28 and so on, increasing with nine for every following call. The problem know is that I only get the correct value from the service every third call, but then the right value. For the other calls I always got the same, invalid value. It looks like first call 10, second call -1211088511, third call -1211088511, fourth call 19 and so on. I tested it on two servers with an older and newer apache, having the same behavior, but other incorrect values. If I test the service with the axis simple server everything works fine, but I don't know if I can test the shared memory with the simple server? My question now is: Does anybody knew this behavior? Maybe I have implemented something wrong and attached the service. It would be very nice, if someone can have a look inside my code. Kind regards Michael service.tar.gz Description: GNU Zip compressed data - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: apache shared memory
You can enable Shared memory for mod_axis2 by adding Axis2GlobalPoolSize parameter in the httpd.conf. And when accessing that shared variable you need to switch to global pool. Please see axutil_allocator.h for details. On Tue, 2008-12-02 at 11:53 +0100, Michael Sutter wrote: Hello list, I have a strange behavior and hopefully someone can help me. I have implemented a simple service and I want to access the shared memory of the apache daemon. The service stores a object, which can perform some basic mathematical operations and store a value. In the first call of the service the shared variable is initialized and stored with a value in the shared memory. Every following call should get the shared variable, add two numbers and store it in the shared variable (setLaenge(int a) in myadd.cpp). The result should look like this: first call 10, second call 19, third call 28 and so on, increasing with nine for every following call. The problem know is that I only get the correct value from the service every third call, but then the right value. For the other calls I always got the same, invalid value. It looks like first call 10, second call -1211088511, third call -1211088511, fourth call 19 and so on. I tested it on two servers with an older and newer apache, having the same behavior, but other incorrect values. If I test the service with the axis simple server everything works fine, but I don't know if I can test the shared memory with the simple server? My question now is: Does anybody knew this behavior? Maybe I have implemented something wrong and attached the service. It would be very nice, if someone can have a look inside my code. Kind regards Michael - 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: Problem related to ADB when transferring a byte array [== AXIS2-3538]
Marc F. wrote: To demonstrate a possible bug in ADB Webservice I attached a zip file, containing two aar files, and the source code as well. Alas, I think this is a well-known issue: https://issues.apache.org/jira/browse/AXIS2-3538 I had an exchange of e-mails with Deepal, but it ended in nothing. The issue was submitted on 24/Feb/08 09:13 AM and a suggestion for a patch is available from June 2008, but it is currently unassigned. It is marked as critical. In our organisation we wrote a patch, recompiled axis2, and we are using the patch (with success). I can send the patch to anyone interested, but I think this is a REALLY BAD problem and should be fixed as soon as possible by the axis2 development team. Is anyone in the axis2 team listening? Hi Andrea -- dott. Andrea Spinelli - IMTeam e-mail: andrea dot spinelli at imteam dot it phone: +39-035-636029 fax: +39-035-638129 www: http://www.imteam.it/ IANA enterprise number: 1.3.6.1.4.1.30916 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Axis2] excludeOperations in services.xml problem
Hi, I have a webservices (written in Java) with several operations. I want to exclude couple of operations from that. I've used the excludeOperations tag in services.xml as shown below excludeOperations operationcopy/operation operationmove/operation /excludeOperations After restarting the app server when I see view the WSDL in the browser, I still see these 2 operations also I was able to access those operations from the Java client. Thanks Raghu
Java2WSDL: not generating ComplexType for JavaBean Array
Hi, I'm using a Java Bean array as input parameter to a method. When i generate WSDL using Java2WSDL it is not including information about this Bean as complex type in the WSDL file. The input parameter is referred as soapenc:Array and when i generate java client from WSDL it is just showing as an object array. public void changeSWInstallation(String ID, *ClearingIndicator[] SW_ClearingIndicators*, String identifier, String version); here is the command i used to generate WSDL java -classpath axis.jar;commons-discovery.jar;commons-logging.jar;jaxrpc.jar;wsdl4j.jar;saaj.jar;app.jar org.apache.axis.wsdl.Java2WSDL -o MyService.wsdl -lhttp: //localhost:8081/MyService/services/MyService -n http://hk.com/MyService; -pcom.hk.MyService http://hk.com/MyService; --style wrapped --use literal com.hk.MyService am i missing any other parameters to Java2WSDL? I'm using *axis 1.1* as product using the the same and i can't move to other version to solve this. Please help me out... -- Hari Krishna Vemula
Re: WSDL2JAVA created uncompilable Stub
Hi I am having same issue, any idea how to solve this. I am using Eclipse Platform Version: 3.3.1.1, and my axis2 runtime is axis2-1.4 I have also noticed that in service.xml says !-- This file was auto-generated from WSDL -- !-- by the Apache Axis2 version: 1.3 Built on : Aug 10, 2007 (04:45:47 LKT) -- I was expecting to service.xml to say !-- This file was auto-generated from WSDL -- !-- by the Apache Axis2 version: 1.34 On Wed, Jun 11, 2008 at 7:17 PM, Kraus, David [EMAIL PROTECTED]wrote: Yeah, something similar happened to me. The MTOMAwareXMLStreamWriter parameter is replaced by XMLStreamWriter in the stub code, which causes the compilation problems. I am not absolutely sure what is happening here. I tried enabling MTOM in my services.xml file, and found that wsdl2java generated different stubs, which did compile. However, when I went back and removed the services.xml setting, stub generation did not change, and I could still compile. I began to think that maybe my environment had been mixed between two different versions of Axis2 (I was upgrading from axis2 1.2 to 1.4). So, make sure you have your environment variables set correctly, and then your classpath is correct. Dave -Original Message- From: Adam Muller [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 11, 2008 4:02 AM To: axis-user@ws.apache.org Subject: WSDL2JAVA created uncompilable Stub Hi, with Axis2 1.4 - when I regenerate Stub, it cannot be compiled. I got errors like these all over it: The type WhoIsWhoServiceStub.AddressType must implement the inherited abstract method ADBBean.serialize(QName, OMFactory, MTOMAwareXMLStreamWriter, boolean) The type WhoIsWhoServiceStub.AsyncResponseType must implement the inherited abstract method ADBBean.serialize(QName, OMFactory, MTOMAwareXMLStreamWriter, boolean) etc. (there are about 100 errors in the file). What am I doing wrong? I just upgraded from axis2 1.3 - it worked there perfectly. Thanks for your reply! Best regards Adam - 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]
create and deploy a jaxws service programatically
Hello! Looking at [1] you have the explanation to deploy an axis service programatically. But using this approach you need the services.xml and it is oriented to the standard axis2-way service. I didn't find a reference to do the same for jaxws services. I have two questions (i) What is the best way to launch a service programatically and then deploy jaxws services on it since we don't need the services.xml file to deploy it on servicejar dir. (ii) How do I get the properties (context) of a running server for getting the list of services using the Amila's idea on [2]? Thanks in advance Best regards Javier [1] http://www-128.ibm.com/developerworks/library/ws-axis2soap/index.html [2] http://markmail.org/message/shoyhqnxfjxskcz3 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Still problems encrypting service fault messages
I still don't get my service fault messages encrypted:
Axis 1.4.1
Client server stubs generated from WSDL by wsdl2java
The outFaultFlow does contain the security phase
Messages get signed and encrypted, see service.xml below
Response messages do get encrypted/signed fine, so there is no issue
with the keystore setup, configuration, etc, but if I throw a service
exception, the resulting fault message is send in plain text without
security header, etc...
public SResults SSearch(SearchRequest sRequest)
throws XYZFault {
[...]
throw new XYZFault(Please please encrypt me);
[...]
}
Is there ANYthing I am doing wrong? I assume there must be a way to
sign/encrypt fault messages...
Thanks for any suggestion
snip ---
serviceGroup
service name=SearchServices
messageReceivers
messageReceiver mep=http://www.w3.org/ns/wsdl/in-out;
class=ca.bc.xyz.SearchServicesMessageReceiverInOut/
/messageReceivers
parameter name=ServiceClass
locked=falseca.bc.xyz.SearchServiceImplementation/parameter
!--
parameter name=useOriginalwsdltrue/parameter
parameter name=modifyUserWSDLPortAddresstrue/parameter
--
operation name=SSearch
mep=http://www.w3.org/ns/wsdl/in-out; namespace=
actionMappingSyncSearch/actionMapping
outputActionMapping/outputActionMapping
faultActionMapping
faultName=DPSearchFault.../faultActionMapping
faultActionMapping
faultName=XYZFaulturn:/faultActionMapping
/operation
module ref=rampart /
wsp:Policy
xmlns:sp=http://schemas.xmlsoap.org/ws/2005/07/securitypolicy;
xmlns:wsp=http://schemas.xmlsoap.org/ws/2004/09/policy;
xmlns:wsu=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd;
wsu:Id=mypolicy
sp:AsymmetricBinding
wsp:Policy
sp:InitiatorToken
wsp:Policy
sp:X509Token
sp:IncludeToken=http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/IncludeToken/AlwaysToRecipient;
wsp:Policy
sp:WssX509V3Token10 /
/wsp:Policy
/sp:X509Token
/wsp:Policy
/sp:InitiatorToken
sp:RecipientToken
wsp:Policy
sp:X509Token
sp:IncludeToken=http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/IncludeToken/Never;
wsp:Policy
sp:WssX509V3Token10 /
/wsp:Policy
/sp:X509Token
/wsp:Policy
/sp:RecipientToken
sp:AlgorithmSuite
wsp:Policy
sp:TripleDesRsa15 /
/wsp:Policy
/sp:AlgorithmSuite
/wsp:Policy
/sp:AsymmetricBinding
sp:Wss10
wsp:Policy
sp:MustSupportRefEmbeddedToken /
sp:MustSupportRefIssuerSerial /
/wsp:Policy
/sp:Wss10
sp:SignedParts
sp:Body /
/sp:SignedParts
sp:EncryptedParts
sp:Body /
/sp:EncryptedParts
RampartConfig
xmlns=http://ws.apache.org/rampart/policy;
users1/user
encryptionUseruseReqSigCert/encryptionUser
passwordCallbackClass
ca.webservice.server.search.PasswordCallbackHandler
/passwordCallbackClass
signatureCrypto
crypto
provider=org.apache.ws.security.components.crypto.Merlin
Re: Problem related to ADB when transferring a byte array [== AXIS2-3538]
Andrea Spinelli-2 wrote: Alas, I think this is a well-known issue: https://issues.apache.org/jira/browse/AXIS2-3538 I had an exchange of e-mails with Deepal, but it ended in nothing. The issue was submitted on 24/Feb/08 09:13 AM and a suggestion for a patch is available from June 2008, but it is currently unassigned. It is marked as critical. In our organisation we wrote a patch, recompiled axis2, and we are using the patch (with success). I can send the patch to anyone interested, but I think this is a REALLY BAD problem and should be fixed as soon as possible by the axis2 development team. Is anyone in the axis2 team listening? Hi Andrea -- dott. Andrea Spinelli - IMTeam e-mail: andrea dot spinelli at imteam dot it phone: +39-035-636029 fax: +39-035-638129 www: http://www.imteam.it/ IANA enterprise number: 1.3.6.1.4.1.30916 Thank you very much for your reply, Andrea. Yes, this is a really bad problem that should be fixed, mainly because this kind of problem is not like a common bug, or a little mistake. It is a kind of bug that can make something completely unreliable. I do not rely on ADB, and I will never use it until they fix the problem. And I will recommend everybody to not use ADB as well. I simply do not rely on ADB anymore. That´s sad. Fortunately, using a XML Beans webservice this problem doesn´t happen. Well, at least until now this didn´t happen to me. -- View this message in context: http://www.nabble.com/Problem-related-to-ADB-when-transferring-a-byte-array-tp20607870p20801565.html Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: SOAPMessage with attachment problem
Chinmoy,
The error indeed indicates that you also need to upgrade to a newer
AXIOM version. Snapshots are available from [1]. For the other issue:
the next Axis2 release will indeed require Java 1.5. If upgrading to
that Java version is not an option for you, please have a look at
retrotranslator [2].
Andreas
[1]
http://people.apache.org/repo/m2-snapshot-repository/org/apache/ws/commons/axiom/
[2] http://retrotranslator.sourceforge.net/
On Tue, Dec 2, 2008 at 06:34, Chinmoy Chakraborty [EMAIL PROTECTED] wrote:
Andreas,
I have downloaded the axis2-saaj-SNAPSHOT.jar from the [2] link but I am
getting following error:
Caused by: java.lang.NoSuchMethodError:
org.apache.axiom.om.impl.MIMEOutputUtils.writeDataHandlerWithAttachmentsMessage(Ljavax/activation/DataHandler;Ljava/lang/String;Ljava/io/OutputStream;Ljava/util/Map;Lorg/apache/axiom/om/OMOutputFormat;)V
at org.apache.axis2.saaj.SOAPMessageImpl.writeTo(SOAPMessageImpl.java:327)
I guess I need to download latest axiom code also. Could you please tell me
the url? One more thing I noticed latest saaj-impl code has been compiled in
jdk 1.5 and as I have been running jdk1.4 it was giving version error. Do
you plan to compile this in jdk 1.4 also?
Chinmoy
On Mon, Dec 1, 2008 at 5:45 PM, Andreas Veithen [EMAIL PROTECTED]
wrote:
Chinmoy,
You can either build it from sources (using the Subversion repository
at [1]) or wait for the next build and pick up the JAR at [2]. I don't
know the exact build schedule, but a new build should be available
within 24 hrs. Also, be aware that axis2-saaj-api no longer exists,
but has been moved to Geronimo.
Andreas
[1] http://svn.apache.org/repos/asf/webservices/axis2/trunk/java/
[2]
http://people.apache.org/repo/m2-snapshot-repository/org/apache/axis2/axis2-saaj/SNAPSHOT/
On Mon, Dec 1, 2008 at 12:48, Chinmoy Chakraborty [EMAIL PROTECTED]
wrote:
Hi Andreas,
Thanks for reply. How do I get the fixed version? From where do I get
latest
jars?
Chinmoy
On Mon, Dec 1, 2008 at 4:59 PM, Andreas Veithen
[EMAIL PROTECTED]
wrote:
Chinmoy,
It is not writing MIME messages because the writeTo method was not
implemented correctly. This should now be fixed in trunk.
Andreas
On Mon, Dec 1, 2008 at 09:52, Chinmoy Chakraborty [EMAIL PROTECTED]
wrote:
Hi All,
I am creating a SOAP message using axis2 soap-api and soap-impl.
First I
am
creating the SOAPPart and then I am adding the attachmentpart.
Now, when I do soapMessage.writeTo(OuputStream out), it only writes
the
soap
envelop and not the MIME message. Could somebody please clarify why
it
is
not writing the MIME message. Following is my code snippet
soapMsg = MessageFactory.newInstance().createMessage();
//setting the namespace declaration.
SOAPPart sp = soapMsg.getSOAPPart();
SOAPEnvelope se = sp.getEnvelope();
soapMsg.setProperty(soapMsg.CHARACTER_SET_ENCODING,
DEFAULT_ENCODING);
soapMsg.setProperty(soapMsg.WRITE_XML_DECLARATION, true);
se.addChildElemet()...
then I am adding the attachments...like
addAttachments(attachmentList);
private void addAttachments(List attachmentList) throws
SOAPException,
IOException {
if (attachmentList != null attachmentList.size() 0) {
Iterator attachmentit = attachmentList.iterator();
while (attachmentit.hasNext()) {
DataHandler dh = (DataHandler) attachmentit.next();
AttachmentPart ap = soapMsg.createAttachmentPart();
ap.setContentId(dh.getName());
Object content = dh.getContent();
ap.setContent(dh.getContent(), dh.getContentType());
soapMsg.addAttachmentPart(ap);
}
}
}
Thanks,
Chinmoy
-
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]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
JSON - Badgerfish
History:
Historically we support SOAP messages which has the standard format for
exchange of Web services messages. I am attempting to support JSON
badgerfish messages with Axis2, since most all our messages have
namespaces. I downloaded the latest Axis2 1.4.1 and followed the
instructions to setup Axis2 1.4.1 with JSON, the best information I could
find was at http://wso2.org/library/768. I updated an axis2.xml for
client and and read in an updated axis2.xml with message formatter and
message builders supporting badgerfish applications.
Problem Description:
I run the SOAP message and it appears to complete successfully. I switch
from SOAP to JSON Badgerfish and it appears the message is getting
formatted correctly on the HTTP Request, but I get a SOAP fault an
exception on the Server side.
Message:
[ERROR] Exception occurred while trying to invoke service method
converttemp_XML_Dan
org.apache.axis2.AxisFault: namespace mismatch require
http://converttemp.wsbeans.iseries/xsd found
I have tried every configuration, removing and adding namespaces, and
endpoints. So I even attempted on Axis2 1.4, 1.3 and get the same error,
so I am assuming I am missing something in either the configuration or in
the composition of my JSON badgerfish message.
Any help would be greatly appreciated. If this is not enough information,
I can enable tracing and get all messages.
Soap Setting:
options.setProperty(Constants.Configuration.MESSAGE_TYPE, text/xml);
TCPMON Soap Message Request (Working)
POST /axis2/services/ConvertTempJava.ConvertTempJavaHttpSoap11Endpoint/
HTTP/1.1
Content-Type: text/xml; charset=UTF-8
SOAPAction: urn:anonOutInOp
User-Agent: Axis2
Host: optimus:9099
Transfer-Encoding: chunked
11e
?xml version='1.0' encoding='UTF-8'?soapenv:Envelope
xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;soapenv:Bodyns:converttemp_XML_Dan
xmlns:ns=http://converttemp.wsbeans.iseries/xsd;ns:param034/ns:param0/ns:converttemp_XML_Dan/soapenv:Body/soapenv:Envelope
0
TCPMON Soap Message Response (Working):
HTTP/1.1 200 OK
Date: Tue, 02 Dec 2008 21:43:23 GMT
Server: Simple-Server/1.1
Transfer-Encoding: chunked
Content-Type: text/xml; charset=UTF-8
198
?xml version='1.0' encoding='UTF-8'?soapenv:Envelope
xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;soapenv:Bodyns:converttemp_XML_DanResponse
xmlns:ns=http://converttemp.wsbeans.iseries/xsd;ns:returnlt;?xml
version=1.0 encoding=UTF-8?
lt;CONVERTTEMP
lt;TEMPOUT7.7lt;/TEMPOUT
lt;/CONVERTTEMP
/ns:return/ns:converttemp_XML_DanResponse/soapenv:Body/soapenv:Envelope
0
JSON Badgerfish Setting:
options.setProperty(Constants.Configuration.MESSAGE_TYPE,
application/json/badgerfish);
TCPMON JSON Message Request
POST /axis2/services/ConvertTempJava.ConvertTempJavaHttpSoap11Endpoint/
HTTP/1.1
Content-Type: application/json/badgerfish; charset=UTF-8
User-Agent: Axis2
Host: optimus:9099
Transfer-Encoding: chunked
6f
{ns:converttemp_XML_Dan:{@xmlns:{ns:http:\/\/converttemp.wsbeans.iseries
\/xsd},ns:param0:{$:34}}}
0
TCPMON JSON Message Response
HTTP/1.1 500 namespace mismatch require
http://converttemp.wsbeans.iseries/xsd found
Date: Tue, 02 Dec 2008 21:58:34 GMT
Server: Simple-Server/1.1
Transfer-Encoding: chunked
Content-Type: application/json/badgerfish; charset=UTF-8
10b
{Fault:{$:soapenv:Fault xmlns:soapenv=\http:\/\/schemas.xmlsoap.org
\/soap\/envelope\/\faultcodesoapenv:Server
\/faultcodefaultstringnamespace mismatch require
http:\/\/converttemp.wsbeans.iseries\/xsd found \/faultstringdetail \/
\/soapenv:Fault}}
0
Exception in Server log File:
[ERROR] Exception occurred while trying to invoke service method
converttemp_XML_Dan
org.apache.axis2.AxisFault: namespace mismatch require
http://converttemp.wsbeans.iseries/xsd found
at org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass
(RPCUtil.java:177)
at
org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic
(RPCMessageReceiver.java:102)
at
org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic
(AbstractInOutMessageReceiver.java:40)
at org.apache.axis2.receivers.AbstractMessageReceiver.receive
(AbstractMessageReceiver.java:100)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:176)
at
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest
(HTTPTransportUtils.java:275)
at org.apache.axis2.transport.http.HTTPWorker.service
(HTTPWorker.java:278)
at org.apache.axis2.transport.http.server.AxisHttpService.doService
(AxisHttpService.java:281)
at
org.apache.axis2.transport.http.server.AxisHttpService.handleRequest
(AxisHttpService.java:187)
at org.apache.axis2.transport.http.server.HttpServiceProcessor.run
(HttpServiceProcessor.java:82)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker
(ThreadPoolExecutor.java:1061)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor
Re: [Axis2] excludeOperations in services.xml problem
What is the Axis2 version you are using? Azeez On Tue, Dec 2, 2008 at 8:30 PM, Raghu Upadhyayula [EMAIL PROTECTED] wrote: Hi, I have a webservices (written in Java) with several operations. I want to exclude couple of operations from that. I've used the excludeOperations tag in services.xml as shown below excludeOperations operationcopy/operation operationmove/operation /excludeOperations After restarting the app server when I see view the WSDL in the browser, I still see these 2 operations also I was able to access those operations from the Java client. Thanks Raghu -- Thanks Afkham Azeez Blog: http://afkham.org Developer Portal: http://www.wso2.org WSAS Blog: http://wso2wsas.blogspot.com Company: http://wso2.com GPG Fingerprint: 643F C2AF EB78 F886 40C9 B2A2 4AE2 C887 665E 0760
Re: Problem related to ADB when transferring a byte array [== AXIS2-3538]
Have you submitted this patch? Is this the same patch that is attached to JIRA issue AXIS2-3538? Thanks Azeez On Tue, Dec 2, 2008 at 2:07 PM, Andrea Spinelli [EMAIL PROTECTED]wrote: Marc F. wrote: To demonstrate a possible bug in ADB Webservice I attached a zip file, containing two aar files, and the source code as well. Alas, I think this is a well-known issue: https://issues.apache.org/jira/browse/AXIS2-3538 I had an exchange of e-mails with Deepal, but it ended in nothing. The issue was submitted on 24/Feb/08 09:13 AM and a suggestion for a patch is available from June 2008, but it is currently unassigned. It is marked as critical. In our organisation we wrote a patch, recompiled axis2, and we are using the patch (with success). I can send the patch to anyone interested, but I think this is a REALLY BAD problem and should be fixed as soon as possible by the axis2 development team. Is anyone in the axis2 team listening? Hi Andrea -- dott. Andrea Spinelli - IMTeam e-mail: andrea dot spinelli at imteam dot it phone: +39-035-636029 fax: +39-035-638129 www: http://www.imteam.it/ IANA enterprise number: 1.3.6.1.4.1.30916 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Thanks Afkham Azeez Blog: http://afkham.org Developer Portal: http://www.wso2.org WSAS Blog: http://wso2wsas.blogspot.com Company: http://wso2.com GPG Fingerprint: 643F C2AF EB78 F886 40C9 B2A2 4AE2 C887 665E 0760
Re: WSDL2JAVA created uncompilable Stub
On Wed, Jun 11, 2008 at 4:32 PM, Adam Muller [EMAIL PROTECTED] wrote: Hi, with Axis2 1.4 - when I regenerate Stub, it cannot be compiled. I got errors like these all over it: The type WhoIsWhoServiceStub.AddressType must implement the inherited abstract method ADBBean.serialize(QName, OMFactory, MTOMAwareXMLStreamWriter, boolean) The type WhoIsWhoServiceStub.AsyncResponseType must implement the inherited abstract method ADBBean.serialize(QName, OMFactory, MTOMAwareXMLStreamWriter, boolean) etc. (there are about 100 errors in the file). What am I doing wrong? I just upgraded from axis2 1.3 - it worked there perfectly. I think you compiling code with the axis2 1.3 jars. please make sure you have axis2 1.4 jars in the class patch. thanks, Amila. Thanks for your reply! Best regards Adam - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Amila Suriarachchi WSO2 Inc. blog: http://amilachinthaka.blogspot.com/
RE: [Axis2] excludeOperations in services.xml problem
I'm using Axis2 1.4 -Raghu From: Afkham Azeez [mailto:[EMAIL PROTECTED] Sent: Tue 12/2/2008 6:22 PM To: axis-user@ws.apache.org Subject: Re: [Axis2] excludeOperations in services.xml problem What is the Axis2 version you are using? Azeez On Tue, Dec 2, 2008 at 8:30 PM, Raghu Upadhyayula [EMAIL PROTECTED] wrote: Hi, I have a webservices (written in Java) with several operations. I want to exclude couple of operations from that. I've used the excludeOperations tag in services.xml as shown below excludeOperations operationcopy/operation operationmove/operation /excludeOperations After restarting the app server when I see view the WSDL in the browser, I still see these 2 operations also I was able to access those operations from the Java client. Thanks Raghu -- Thanks Afkham Azeez Blog: http://afkham.org http://afkham.org/ Developer Portal: http://www.wso2.org http://www.wso2.org/ WSAS Blog: http://wso2wsas.blogspot.com http://wso2wsas.blogspot.com/ Company: http://wso2.com http://wso2.com/ GPG Fingerprint: 643F C2AF EB78 F886 40C9 B2A2 4AE2 C887 665E 0760 winmail.dat- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Registering new handlers programmatically with Axis2
Hi, Currently Axis2 registers the handlers specified in the axis2.xml configuration file. Is there a way to programmatically register new custom handlers with Axis2 runtime i.e. i don't want to use the axis2.xml approach? How can this be achieved? Thanks, Deepak. Add more friends to your messenger and enjoy! Go to http://messenger.yahoo.com/invite/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
