Hi all!
I am working on linux OS and trying to build client.
I tried to work with the bin package but for some reason my
program crashed once an instance of Stub class was created.
I think it's related to the lib libaxis_client.so.
Is there any way to compile and create this lib on
Hi,
If you wish to build from source you can find instructions on building
here: http://ws.apache.org/axis/cpp/antbuild-guide.html
What steps have you already taken for diagnosing the problem?
The most obvious reason for the Stub creation to fail is if one of the
dependent libraries is not
Hi all,
Header files in modules/xml/soap, modules/xml/om and modules/util/ are
not included in tar ball created by 'make dist'. A fix is attached.
Please review and apply.
Thanks.
~sanjaya
--
http://sanjaya.8k.com
Index: modules/xml/soap/Makefile.am
Hi all,
Directory test/wsdl is not included in tarball created by 'make dist'.
A patch is attached. Please review and apply.
Thanks.
~sanjaya
--
http://sanjaya.8k.com
Index: test/Makefile.am
===
--- test/Makefile.am
Hi,
I have also encountered this problem, when building with MS VC++ 6. It
would appear there has been a change in method signature between v6 and
v7+.
Fred has now included a change to allow this to work on v6 and v7
compilers, which is working nicely for me.
Regards,
Adrian
Yes, i noticed it and it works already for me.
Thanks
Franz
Adrian Dick schrieb:
Hi,
I have also encountered this problem, when building with MS VC++ 6. It
would appear there has been a change in method signature between v6 and
v7+.
Fred has now included a change to allow this to work
[ http://issues.apache.org/jira/browse/AXISCPP-950?page=all ]
Adrian Dick updated AXISCPP-950:
Attachment: package.xml.diff
I believe the attached patch will resolve this problem, but I haven't had an
opportunity to test on a Unix platform.
AxisCPP server cannot parse Java client arrays
--
Key: AXISCPP-952
URL: http://issues.apache.org/jira/browse/AXISCPP-952
Project: Axis-C++
Type: Bug
Components: Server - Deserialization
Versions: 1.6 Beta
AxisCPP Server cannot parse Java arrays
---
Key: AXISCPP-951
URL: http://issues.apache.org/jira/browse/AXISCPP-951
Project: Axis-C++
Type: Bug
Components: Server - Deserialization
Versions: 1.6 Beta
Environment:
[ http://issues.apache.org/jira/browse/AXIS2C-103?page=all ]
nandika jayawardana closed AXIS2C-103:
--
Fix Version: Current (Nightly)
(was: 0.9)
Resolution: Fixed
(Visible to axiscpp-developers)
Never executed block
[ http://issues.apache.org/jira/browse/AXIS2C-83?page=all ]
nandika jayawardana reassigned AXIS2C-83:
-
Assign To: nandika jayawardana
axis2_om_node_set_first_child does not update links
---
[ http://issues.apache.org/jira/browse/AXIS2C-83?page=all ]
nandika jayawardana closed AXIS2C-83:
-
Fix Version: Current (Nightly)
Resolution: Fixed
This problem is now fixed, set_first_child now sets child's parent
Hi all!
I am trying to install Axis c++ client and compile the src on
linux and I have some questions:
Which version is the most stable for linux?
I downloaded version 1.5.0 and in the INSTALL
file step five I need to run ./configure but there is no such script, what
is
Chinthaka,
in the current svn version the behaviour now is fine. But there is
another point that doesn't seem to work anymore. Notice the additional
Exception element in the detail. How to get rid of this?
Thanks
Yves
soapenv:Fault
faultcodesoapenv:Client.Validation/faultcode
Hi Soumadeep,
On 3/19/06, Soumadeep [EMAIL PROTECTED] wrote:
Chathura,
External monitoring applications would require event details from AXIS2/Synapse for instrumenting management information and otherstats let me know how are we going to expose it.
Ref
I hope I asked this question sometime back and no one answered. Anyway,
here we go.
Deepal Jayasinghe wrote:
Hi all;
In the xdoc folder contains document for already released versions (0.93
, 0.94) and current version. And I dont think we need to keep multiple
doc folders inside xdocs for
I hope I asked this question sometime back and no one answered. Anyway,
here we go.
Deepal Jayasinghe wrote:
Hi all;
In the xdoc folder contains document for already released versions (0.93
, 0.94) and current version. And I dont think we need to keep multiple
doc folders inside xdocs for
Hi,
I think we can make a better decision if we are clear about Apache
policy about maintaining docs for older revisions [Before a 1.0
version and after]. So can some one jump in an enlighten us on what
is the policy for dealing with old docs.
Best Regards,
Chamil Thanthrimudalige
On
Add a new createClientSideAxisService method to AxisService that takes a WSDL4J
Definition object
-
Key: AXIS2-507
URL: http://issues.apache.org/jira/browse/AXIS2-507
Project:
Ok thanks. Actually its fine if it doesn't get in 0.95 if I know it will
get in later. I've created a new JIRA, AXIS2-507, so its not forgotten.
...ant
Sanjiva Weerawarana [EMAIL PROTECTED] on 21/03/2006 01:40:47
Please respond to axis-dev@ws.apache.org
To:axis-dev@ws.apache.org
Hi all,
Yes I agree that the person who does it should have a major part in
deciding 'how' to do it (and ofcourse Chatra is doing a great job -
no doubts about it) But if that person chooses a particularly complex
and not-very-appropriate solution I think we, as a community should be
pointing
On Tue, 2006-03-21 at 14:33 +0600, Chamil Thanthrimudalige wrote:
Hi,
I think we can make a better decision if we are clear about Apache
policy about maintaining docs for older revisions [Before a 1.0
version and after]. So can some one jump in an enlighten us on what
is the policy
h , I do not want to start a war :)
Eran Chinthaka wrote:
I hope I asked this question sometime back and no one answered.
Anyway, here we go.
Deepal Jayasinghe wrote:
Hi all;
In the xdoc folder contains document for already released versions (0.93
, 0.94) and current version. And I
Documentation not up to date
Key: AXIS-2443
URL: http://issues.apache.org/jira/browse/AXIS-2443
Project: Apache Axis
Type: Improvement
Components: Documentation
Versions: 1.3
Environment: n/a
Reporter: Mylene Reiners
[ http://issues.apache.org/jira/browse/AXIS-2443?page=all ]
Mylene Reiners updated AXIS-2443:
-
Attachment: axis_index.txt
updated index page (link to svn instead of cvs)
updated site (left column - link to wsil deleted)
Documentation not up to date
For the time being, you always get this exception element.
I think its a good idea to make this configurable, considering security.
I will make this configurable via a property.
-- Chinthaka
Yves Langisch wrote:
Chinthaka,
in the current svn version the behaviour now is fine. But there is
[
http://issues.apache.org/jira/browse/AXIS-2436?page=comments#action_12371200 ]
George Cowe commented on AXIS-2436:
---
I have found a workaround to this problem -
The problem is caused by the test client's SOAPBodyElement constructor which
takes a
Ok, time to compromise ;-)
Lets maintain two versions of the documents inside the xdocs. One with
the *released* version of docs and the other with *latest *version of
the docs.
And lets have all the versions of the documents in the site. *BUT, *we
will update only the documents of the
+1 from me to maintain 'released' and 'latest' versions of documents
in the SVN head.
Thanks,
Ruchith
On 3/21/06, Eran Chinthaka [EMAIL PROTECTED] wrote:
Ok, time to compromise ;-)
Lets maintain two versions of the documents inside the xdocs. One with
the *released* version of docs and the
Hi all,
I'm playing a bit with AXIS2 and XMLBeans and I've found interesting
behaviour.
The generated code throws:
java.lang.RuntimeException: Data binding error
at line with:
java.lang.Object object =
fromOM(getElement(_returnEnv,doc),pattest.MethodResponseDocument.class);
The problem is in
+1 :)
Eran Chinthaka wrote:
Ok, time to compromise ;-)
Lets maintain two versions of the documents inside the xdocs. One with
the *released* version of docs and the other with *latest *version of
the docs.
And lets have all the versions of the documents in the site. *BUT, *we
will
Cool :) +1.
Damn, I was going to enjoy giving boxing gloves to see open source
developers fight about documentation!!!
Sanjiva.
On Tue, 2006-03-21 at 16:25 +0600, Eran Chinthaka wrote:
Ok, time to compromise ;-)
Lets maintain two versions of the documents inside the xdocs. One with
[ http://issues.apache.org/jira/browse/AXIS2-455?page=all ]
Ajith Harshana Ranabahu resolved AXIS2-455:
---
Resolution: Fixed
A test case is added to Axis2 as promised!
Axis2 dotNET interoperability problem with abstract types.
[
http://issues.apache.org/jira/browse/AXIS2-245?page=comments#action_12371218 ]
Ajith Harshana Ranabahu commented on AXIS2-245:
---
Hi Steve,
Could you attach the patched WSDL set ? perhaps there are imports inside the
schema files also ?
:-)
Well 2 versions seems to be an ok middle ground. +1 from me too.
Chamil
On Mar 21, 2006, at 5:27 PM, Sanjiva Weerawarana wrote:
Cool :) +1.
Damn, I was going to enjoy giving boxing gloves to see open source
developers fight about documentation!!!
Sanjiva.
On Tue, 2006-03-21 at
Damn, I was going to enjoy giving boxing gloves to see open source
developers fight about documentation!!!
Or a soccer ball, since the world cup is approaching. ;-) +1 to a good compromise.
Robert
http://www.braziloutsource.com/ On 3/21/06, Sanjiva Weerawarana
[EMAIL PROTECTED]
[ http://issues.apache.org/jira/browse/AXIS2-426?page=all ]
Ajith Harshana Ranabahu resolved AXIS2-426:
---
Resolution: Fixed
I just tried this with the latest source and it is working. I'm agreeing with
Deepak on this and marking this
[ http://issues.apache.org/jira/browse/AXIS2-337?page=all ]
Ajith Harshana Ranabahu resolved AXIS2-337:
---
Resolution: Fixed
The real problem was in the WSDLvalidatorExtension where the logic of checking
for the targetnamespace was
[ http://issues.apache.org/jira/browse/AXIS2-505?page=all ]
Deepal Jayasinghe resolved AXIS2-505:
-
Fix Version: 0.95
Resolution: Fixed
ConfigurationContext pre-calculation in ServiceContext constructor
[
http://issues.apache.org/jira/browse/AXIS2-418?page=comments#action_12371227 ]
Ajith Harshana Ranabahu commented on AXIS2-418:
---
The reason is that this includes a simple content element which is not handled
in the ADB schema compiler. It
[ http://issues.apache.org/jira/browse/AXIS2-507?page=all ]
Deepal Jayasinghe resolved AXIS2-507:
-
Fix Version: 0.95
Resolution: Fixed
Ant,
I added the method , can you please check is that what you want
Add a new
[ http://issues.apache.org/jira/browse/AXIS2-352?page=all ]
Ajith Harshana Ranabahu updated AXIS2-352:
--
type: Improvement (was: Bug)
Priority: Minor (was: Major)
Since there's agreement that this is not going to be a required feature
[ http://issues.apache.org/jira/browse/AXIS2-382?page=all ]
Ajith Harshana Ranabahu resolved AXIS2-382:
---
Resolution: Fixed
Since Simon is silent and this feature has been around for a while without any
complaints, I am marking this issue
[ http://issues.apache.org/jira/browse/AXIS2-418?page=all ]
Ajith Harshana Ranabahu updated AXIS2-418:
--
type: Improvement (was: Bug)
Priority: Minor (was: Major)
Properly attached the error message for unsupported schema constructs.
[ http://issues.apache.org/jira/browse/AXIS2-286?page=all ]
Deepal Jayasinghe resolved AXIS2-286:
-
Fix Version: 0.95
Resolution: Fixed
In latest SAAJ impl we dont have this problem , So it is fixed :)
thx Azeez
getOwnerDocument of
[
http://issues.apache.org/jira/browse/AXIS2-479?page=comments#action_12371224 ]
Ajith Harshana Ranabahu commented on AXIS2-479:
---
Seems this issue is related to the attribute namespace serialization issue
since in the WSA case I see that the
[ http://issues.apache.org/jira/browse/AXIS2-506?page=all ]
Deepal Jayasinghe resolved AXIS2-506:
-
Fix Version: 0.95
Resolution: Fixed
DescriptionBuilder and name-parameter reading/missing
[ http://issues.apache.org/jira/browse/AXIS2-503?page=all ]
Deepal Jayasinghe resolved AXIS2-503:
-
Fix Version: 0.95
Resolution: Fixed
Exposing one of the TransportUtils methods
--
Key:
[
http://issues.apache.org/jira/browse/AXIS2-418?page=comments#action_12371239 ]
Sanjiva Weerawarana commented on AXIS2-418:
---
I have no problem with not supporting simpleContent right now, but we MUST
throw an exception saying Unsupported schema
[ http://issues.apache.org/jira/browse/AXIS2-408?page=all ]
Ajith Harshana Ranabahu updated AXIS2-408:
--
type: Improvement (was: Bug)
Priority: Minor (was: Major)
Since we are not going to add complete support for Simple/Complex
[ http://issues.apache.org/jira/browse/AXIS2-498?page=all ]
Deepal Jayasinghe resolved AXIS2-498:
-
Fix Version: 0.95
Resolution: Fixed
just adding following line I was able to fix that
[ http://issues.apache.org/jira/browse/AXIS2-405?page=all ]
Deepal Jayasinghe resolved AXIS2-405:
-
Fix Version: 0.95
Resolution: Fixed
sorry for Atachament ,
it is fixed now :)
Codegeneration has a problem when de-serializing Arrays
[
http://issues.apache.org/jira/browse/AXIS2-405?page=comments#action_12371234 ]
Ajith Harshana Ranabahu commented on AXIS2-405:
---
Ahumm... Where is this mentioned Schema and the attached file ?
Codegeneration has a problem when
[
http://issues.apache.org/jira/browse/AXIS2-418?page=comments#action_12371241 ]
Ajith Harshana Ranabahu commented on AXIS2-418:
---
Agreed to Sanjiva's comment. Will be putting proper error messages in the code
generator for the unsupported
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all;
We have fixed all the blockers for the release. And I am happy to say
that we can do the Axis2 0.95 release on 23rd March :)
So I would like to propose the code freeze by today ( otherwise we
don't have enough time for testing) , I
Hi all,
Ok I'm also +1 to the compromise but I have a small issue to be clarified.
Once a release is out we do a SVN tag (and I've been told that tags
automatically become branches, of which I'm not really sure about - If
not lets say we always start a branch after a tag which seems to be
the
12:00 Midnight EST? :)
-- dims
On 3/21/06, Deepal Jayasinghe [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all;
We have fixed all the blockers for the release. And I am happy to say
that we can do the Axis2 0.95 release on 23rd March :)
So I would like to
Hi folks!
This is an automatic reminder that the weekly Axis2 developer chat
will be occurring tomorrow, March 22, at:
5AM PST, 8AM EST, 1PM GMT, 7PM SLT, midnight (next day) AEST
The chat takes place on the freenode IRC network, (use server
irc.freenode.net), on channel #apache-axis, and is
I hope we can apply our builder extensions theory here, but
unfortunately for the same person :-D
(for those who doesn't know what this builder extensions theory is,
please search for the mails of Axis2 during its start up days)
-- Chinthaka
Ajith Ranabahu wrote:
Hi all,
Ok I'm also +1 to
The usage and choice of the constructor to use with the bean
deserializer is chosen as a first found one instead if us being able to
specify what to use or as suggested by the XML mapping suggested in
JSR109 (mentioned in code). What this is doing is making the
constructortarget class not being
Consider ignoring directories called CVS when looking for services
--
Key: AXIS2-508
URL: http://issues.apache.org/jira/browse/AXIS2-508
Project: Apache Axis 2.0 (Axis2)
Type: Wish
Components:
Are you going to open a jira enh. request? This way I'm able to see how
to set the property and when it's done.
yves
On Tue, 2006-03-21 at 15:18 +0600, Eran Chinthaka wrote:
For the time being, you always get this exception element.
I think its a good idea to make this configurable,
Please go ahead and open it up, that way I also won't forget this.
But I don't think I can fix this now as Deepal has already frozen the code.
-- Chinthaka
Yves Langisch wrote:
Are you going to open a jira enh. request? This way I'm able to see how
to set the property and when it's done.
XML Deserialzation problem with Union of SimpleTypes
Key: AXIS-2444
URL: http://issues.apache.org/jira/browse/AXIS-2444
Project: Apache Axis
Type: Bug
Components: Serialization/Deserialization
Versions:
[ http://issues.apache.org/jira/browse/AXIS-2444?page=all ]
Subba Ayyagari updated AXIS-2444:
-
Attachment: EMCAxisBug.zip
XML Deserialzation problem with Union of SimpleTypes
Key:
Yes, I added that test case to demonstrate a problem in JavaBeanWriter.
Please see: http://marc.theaimsgroup.com/?l=axis-devm=114248722321343w=2
I'll poke Dims for comments on that change again.
Jarek
-Original Message-
From: Changshin Lee [mailto:[EMAIL PROTECTED]
Sent: Monday,
+1 to release 1.4 as it stands. +0 to backport memory leak patch.
--
Tom Jordahl
Adobe ColdFusion Team
-Original Message-
From: Bjorn Townsend [mailto:[EMAIL PROTECTED]
Sent: Friday, March 17, 2006 6:19 PM
To: axis-dev@ws.apache.org
Subject: Re: [VOTE] Release Axis 1.4 final branch
[ http://issues.apache.org/jira/browse/AXIS-2441?page=all ]
Tom Jordahl closed AXIS-2441:
-
Resolution: Invalid
Why should this URI be reachable? It is just a namespace, not a web page.
xmlns not reachable: http://xml.apache.org/axis/wsdd/
[
http://issues.apache.org/jira/browse/AXIS-2442?page=comments#action_12371303 ]
Tom Jordahl commented on AXIS-2442:
---
If this is a wrapped document/literal service, you should use the --noWrapped
switch to WSDL2Java to turn off the unwrapping of the
Sanjiva Weerawarana wrote:
Most definitely +1! Axis2 is now ready for prime time .. and we need
much wider user feedback to make it move to the next level. We won't get
that until we release 1.0.
I propose we change 0.96 below to the label 1.0RC to signal to everyone
that this is our planned
Hi Devs,I was trying to use several axis2 clients in multiple threads and found these problems.1:When clients are configured to use a separate transport listener the status of the listener (whether started or not) is kept in the ListenerManager and is checked by the static methods of the
Jaliya,
+1 to #1. Please commit the fix.
-- dims
On 3/21/06, Jaliya Ekanayake [EMAIL PROTECTED] wrote:
Hi Devs,
I was trying to use several axis2 clients in multiple threads and found
these problems.
1:
When clients are configured to use a separate transport listener the status
of the
One of the basic assumptions of Axis2 handler architecture is that
handlers are stateless .. so there should not be attributes in the
class (expect for HandlerMedatadata). Just notice
AddressingOutHandler has a attribute that leads to this unpleasant
surprise
We should be writing a Handler
On Tue, 2006-03-21 at 21:55 +, Steve Loughran wrote:
One caveat. Once you get to 1.0, you are making some promise of stability.
I am still trying to get code that worked with 0.93 working on 0.95
snapshot, it looks like the dynamic classloading stuff is using the
wrong classloader.
Done.
-Jaliya
- Original Message -
From: Davanum Srinivas [EMAIL PROTECTED]
To: axis-dev@ws.apache.org
Sent: Tuesday, March 21, 2006 5:40 PM
Subject: Re: [Axis2] Some problems in the client side with multiple
threading.
Jaliya,
+1 to #1. Please commit the fix.
-- dims
On 3/21/06,
Or a soccer ball, since the world cup is approaching.
yapee.u got a die hard soccer fan here.
yes+1 for compromise. on a more prcatical aspect pl do understand you cannot freeze documentation like you freeze code.
chatraOn 3/21/06, robert lazarski [EMAIL PROTECTED] wrote:
Damn, I was
ok,
I guess I went overboard with my theory of strictly maintaining the
current docs in SVN (That's no reason to pull out that old builder
extension thing anyway :( ) but I guess I'm more biased to doing
things the right way rather than the easy way (which is unfortunately
not the same and
Srinath Perera wrote:
One of the basic assumptions of Axis2 handler architecture is that
handlers are stateless .. so there should not be attributes in the
class (expect for HandlerMedatadata). Just notice
AddressingOutHandler has a attribute that leads to this unpleasant
surprise
Hmm, I
hey ajith,
you did hear my reply...may be not on mail. but i did +1 chinthaka's solution.
anyways for the record here goes:
one thing i have to make clear is that once a release has been made and
the code frozen it is very impractical to think that you can freeze the
documentaion with it.
This test currently fails in trunk because the dependent samples/wsa/* files
are missing in trunk. Can you merge these files into trunk or disable this
test?
I also fixed up the test a bit to run ok on unix/linux machines.
Jarek
80 matches
Mail list logo
