Hi Paul;
I can not see any problem in ur service archive file and infact it works
fine with me. I think the problem might be in ur invocation codes I mean
client side so pls chcek that. I have attached a Test class that u can ues
to test ur service.
Thanks
Deepal
> Deepal
>
> Here is the samp
[
http://issues.apache.org/jira/browse/AXIS-849?page=comments#action_12312604 ]
Peter Wisnovsky commented on AXIS-849:
--
I see from a closer reading of the spec that use=prohibited exists to remove
superclass attributes from the subclass. This is obviou
[
http://issues.apache.org/jira/browse/AXIS-849?page=comments#action_12312599 ]
Peter Wisnovsky commented on AXIS-849:
--
Hmm...my schema is huge at this point, and is spread over 8 files. But I can
give you:
This generates
[ http://issues.apache.org/jira/browse/AXIS-2039?page=all ]
daryoush mehrtash updated AXIS-2039:
Attachment: StockQuoteProviderSoapBindingImpl.java
133wsdl.xml
> Axis generates invalid fault messages.
> ---
Axis generates invalid fault messages.
--
Key: AXIS-2039
URL: http://issues.apache.org/jira/browse/AXIS-2039
Project: Axis
Type: Bug
Components: Serialization/Deserialization
Versions: 1.2
Reporter: daryoush mehrtas
[ http://issues.apache.org/jira/browse/AXIS-2038?page=all ]
daryoush mehrtash updated AXIS-2038:
Attachment: patch.txt
This patch fixes the problem for me. It simply adds the context to the fault.
> Fault Serialization problem when invoked form Get
Fault Serialization problem when invoked form Get.
--
Key: AXIS-2038
URL: http://issues.apache.org/jira/browse/AXIS-2038
Project: Axis
Type: Bug
Components: Serialization/Deserialization
Versions: 1.2
Re
[
http://issues.apache.org/jira/browse/AXIS-849?page=comments#action_12312596 ]
Davanum Srinivas commented on AXIS-849:
---
Can you please post a complete WSDL?
thanks,
dims
> WSDL2Java ignores fixed elements/attributes
> ---
[
http://issues.apache.org/jira/browse/AXIS-849?page=comments#action_12312591 ]
Peter Wisnovsky commented on AXIS-849:
--
This is still broken in 1.2.
> WSDL2Java ignores fixed elements/attributes
> ---
>
>
[
http://issues.apache.org/jira/browse/AXIS-2037?page=comments#action_12312562 ]
Sunil Sane commented on AXIS-2037:
--
Tom,
I tried to clear the attachment this way
attachmentPart.clearContent();
attachmentPart.dispose();
call.clearO
[
http://issues.apache.org/jira/browse/AXIS-1433?page=comments#action_12312558 ]
Lisa Preston commented on AXIS-1433:
This issue still exists in the Axis 1.2 Final release code. I was trace the
problem to the fact that the Stub.extractAttachments call
[
http://issues.apache.org/jira/browse/AXIS-2037?page=comments#action_12312544 ]
Tom Jordahl commented on AXIS-2037:
---
How do you suggest that Axis clean up these files?
It is the responsiblity of the service or the client to remove the attachements
when i
[ http://issues.apache.org/jira/browse/AXIS-2037?page=all ]
Sunil Sane updated AXIS-2037:
-
Attachment: attachmentissue.rtf
> attachment temp files are not deleted
> -
>
> Key: AXIS-2037
> URL: http://issu
attachment temp files are not deleted
-
Key: AXIS-2037
URL: http://issues.apache.org/jira/browse/AXIS-2037
Project: Axis
Type: Bug
Environment: Any Windows OS e.g XP, 2000, 2003
Reporter: Sunil Sane
Attachments: attachmentis
Tom,
I can take responibility for the problems :) Am actually happy that it
is a handful of problems...lessons learned:
- Put out more releases, more often.
- Make everyone run their test suites more often.
- Add *MORE* test cases.
- When fixing a problem, add a test case first.
I don't care too
Title: Current Axis problems and questions about the future
FYI
I am currently debugging the following problems in an attempt to resolve all the issues my local product regression tests have uncovered in 1.2.
1. WSDL2Java emits the wrapper types for Doc/lit wrapped services, even though we
should not build process be modular i.e.one could build AXIS2 with only
transports required (without SMTP)?
thanks,
alek
Deepal Jayasinghe wrote:
hi ;
The reason behind JavaMail is Axis2 M2 is going to support SMTP , in
that case it is requird to have those lib files.
Thanks and regards
[
http://issues.apache.org/jira/browse/AXIS-2033?page=comments#action_12312526 ]
Davanum Srinivas commented on AXIS-2033:
Note that calculating the message length is a perfomance hit...Can you please
submit a patch to make your behavior optional? (f
Hi Paul;
> Why does Axis2 seem to have a hard dependency on JavaMail? The need
> for loads of dependent JARS for things I never used was one of the
> issues I've had with Axis1. Can we make this more pluggable?
I too like a switch for not compile the additional stuff, we can put a exclude
rule in
Hi Ashutosh ;
I am also looking a better ways to handle the jars that we can not get
from a repository. If I found a better thingy I will fix the saaj
things as well.
Let us compile the thing with Geronimo activation jar for the time been
Thanks
Srinath
On 6/3/05, Shahi, Ashutosh <[EMAIL PROTECTE
[
http://issues.apache.org/jira/browse/AXIS-2018?page=comments#action_12312480 ]
Daniel Kador commented on AXIS-2018:
Sorry that I haven't responded in a few days. I had to take care of another
project.
The problem is that I cannot even get to see the
[ http://issues.apache.org/jira/browse/AXIS-1958?page=comments#action_67009
]
Christian Pesch commented on AXIS-1958:
---
Of course, this is a classpath issue. The problem is, that I cannot change the
C:\usr\sap\J2E\JC00\j2ee\cluster\server0\bin\ext\webs
Hi Thilina,
There is no attachment support that I am providing in Axis2 M2 saaj. I
needed it just to compile AttachementPart interface of Saaj api.
I am anyway looking to use your mtom stuff for attachment support when
its ready.
Of course Geronimo Activation jar should be fine with m
HI,
Also u can use Gerenimo Activation Jar implementation. As i can remember i didn;t come across any probs with Gerenimo activation implementation. If something fails with that u can use it just for the build and then u can use sun implemetations only if u won't to use & check the test cases.
B
Hi,
It can also be due to MTOM support. For the moment the mtom source files in the build uses Gerenimo Java Mail & Activation implementations. But those implementations seems not complete yet. So to have MTOM support we need to have Sun javamail packages. In that case we'll be giving the option fo
This definition:
….
should produce this:
2ndString
(That's assuming you used elementFormDefault="qualified" -
Deepal
Here is the sample JAR file.
Here is the stack trace.
org.apache.axis.engine.AxisFault: No Operation named "echo" Not found
at org.apache.axis.engine.AddressingBasedDispatcher.findOperation(Addres
singBasedDispatcher.java:52)
at org.apache.axis.engine.AbstractDispatcher.i
Thanks Tomek and Eran, it worked
-Ashutosh
From: Eran Chinthaka
[mailto:[EMAIL PROTECTED]]
Sent: Friday, June 03, 2005 4:59
PM
To: axis-dev@ws.apache.org
Subject: RE: [Axis2]Help on maven
Ashu,
Thilina also wanted activation.jar for his
MTOM stuff and I saw he has ad
Ashu,
Thilina also wanted activation.jar for his
MTOM stuff and I saw he has added that to project.xml of xml module. He has
commented it now. So if you un-comment, your classes will compile.
Chinthaka
From: Shahi, Ashutosh
[mailto:[EMAIL PROTECTED]
Sent: Friday, June
hi ;
The reason behind JavaMail is Axis2 M2 is going to support SMTP , in that
case it is requird to have those lib files.
Thanks and regards.
Deepal
- Original Message -
From: "Paul Fremantle" <[EMAIL PROTECTED]>
To:
Sent: Friday, June 03, 2005 4:07 PM
Subject: Dependency on Java
Hi Paul;
I can not give the correct answer without looking at the source codes , if
you can pls send your service archive file and corresponding source files to
mailing list or to me , then I can take a look at that.
BTW at which point did u get this exception ?
Deepal
- Original Messa
On 6/3/05, Shahi, Ashutosh <[EMAIL PROTECTED]> wrote:
>
> Hi Srinath,
It's not for me but...
>The saaj API needs activation.jar in classpath for attachment
> support. Though we don't have attachment support now, but because of
> activation.jar missing, most of the interfaces and
Hi Srinath,
The saaj API needs activation.jar in classpath for attachment support. Though
we don’t have attachment support now, but because of activation.jar
missing, most of the interfaces and hence classes fail to compile. I had added
exclusion condition in project.xml if
Ok now I'm getting a fault
AxisFault: No Operation named "echo" Not found. I have a method called
echo in my class and a in my service.xml.
Any ideas?
Paul
On 6/3/05, Deepal Jayasinghe <[EMAIL PROTECTED]> wrote:
> Hi all;
> I forgot to tell every thing in the previous mail , in the current
>
Folks
Why does Axis2 seem to have a hard dependency on JavaMail? The need
for loads of dependent JARS for things I never used was one of the
issues I've had with Axis1. Can we make this more pluggable?
Paul
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project ws-axis has an issue affecting its community integration.
This issue affects 45 p
Hi all;
I forgot to tell every thing in the previous mail , in the current
implementation it can possible to specify operations specific
messgeRecievers , if you don't do so default message receiver will acts as
the messageReciever.
Any way why don't u take a look at the deployment sample the
hi paul
This service echo the given input , and this was developed to
text the axis system working
correctly
locked="xsd:false">org.apache.axis.echo.Echo
This is service.xml corresponds to an echo service
parameter ServiceClass is
I suggest we go with Document extend OMElement to resolve this until
next refactoring of OM. WDYT?
On 6/3/05, Venkat Reddy <[EMAIL PROTECTED]> wrote:
> just saw some more issues if we go with new Interface.
>
> The client API uses OMElement.addChild() to build the message. Even if
> we try to use
Hi
I'm trying to deploy the sample service on the latest code. The
service.xml seems to have changed since M1. Can someone please post a
working service.xml!???
Paul
>
> Can we have test cases under o.a.a.om.infoset.* ?
>
Sure. No issues. To be explicit, it goes into
java\modules\xml\test\org\apache\axis\om\infoset
- venkat
Oops it is June Absolutly
On 6/3/05, Venkat Reddy <[EMAIL PROTECTED]> wrote:
> Srinath,
>
> Is it June or July :-) your first mail says July.
> SAAJ:
> We're going to check in the code support today alongwith its maven
> files. It only depends on OM. No DOM implementation is required. There
> ar
>
> Srinath,
>
> Is it June or July :-) your first mail says July.
>
> SAAJ:
> We're going to check in the code support today alongwith its maven
> files. It only depends on OM. No DOM implementation is required. There
> are no other dependencies. SAAJ code should go into java/modules/SAAJ.
>
It will not come in M2.
I could not get the code to a level to be
released. L.
Sorry for inconveniences ;).
From: Shahi, Ashutosh
[mailto:[EMAIL PROTECTED]
Sent: Friday, June 03, 2005 2:45
PM
To: axis-dev@ws.apache.org
Subject: [Axis2]SOAPFault specific
classes in OM
Hi Eran,
I don’t see any implementation for
SOAPFault specific interfaces like SOAPFaultCode, SOAPFaultCodeValue, SOAPFaultDetail,
SOAPFaultNode and others.
We need to have them right? Or Am I missing something?
-Ashutosh
Srinath,
Is it June or July :-) your first mail says July.
SAAJ:
We're going to check in the code support today alongwith its maven
files. It only depends on OM. No DOM implementation is required. There
are no other dependencies. SAAJ code should go into java/modules/SAAJ.
We are porting Axis 1.2
Hi Venkat,All;
Please checked in the code, I will bring them to main tree
1) Where should the code go? new module?
2) What are the dpedndancies?
I like to not to waver the deadline for M2 June 7th, can we get the
things in safe and sound by the day? I think the code need bit
documetations + tes
Srinath,
The SAAJ code is ready. Ashu or I will check it in into scratch area
today, so that you can move it to main src on Monday.
Regarding the full info set support: We have support for comments and
PIs fully and provided a test case for running XML test suite against
OM. DTD support is curren
just saw some more issues if we go with new Interface.
The client API uses OMElement.addChild() to build the message. Even if
we try to use setParent() instead of addChild() here, the user has to
typecast the OMElement into OMElementImpl and pass it to setParent,
which is not elegant.
If we add a
49 matches
Mail list logo