Glen Daniels wrote:
Hi Tom, all:
IMO, there should be exactly *one* "extra" API on the generated class,
and that thing should give you access to all the Axis2-specific
functionality. This could be done in several ways:
- 1 -
class StubAPI {
public MessageContext getMessageContext();
jayachandra wrote:
Sounds reasonable to me for now.
Even in Axis 1.x if user wishes to ser and deser a particular part of
SOAP message as per a different data binding standard,
what about parts of message - if i want to databind only some specific
headers? and to have one header databound with
Hi Venkat,
IMHO if we are to have an object[] input then we have to have some kind
of databinding inside. Since we don't have our own databinding yet,
such a client is not possible (yet). Certainly it is a wish but
unfortunaltely I don't see it coming in the near future.
Hmmm.. RPC encoding... We a
Sounds reasonable to me for now.
Even in Axis 1.x if user wishes to ser and deser a particular part of
SOAP message as per a different data binding standard, he must have
the intelligentia to code the ser and deser factory for that data
binding mechanism. Castor serializer and deserializer factorie
Hi Alek,
The idea in having pluggable data binding is not making it pluggable
after code generation. Our view of 'pluggability' is at the code
generation level. i.e. if the user needs his own data binding he has to
engage that extension at the code generation stage to have the required
code generat
Ajith and Chathura,
If i want to write a DII kind of client which doesn't use any static
stubs, then isn't it too much work to write the databinding code on my
own? I was expecting a version of Call.invoke() which can take
Object[]. Is this not in our wish list? What's our approach to support
RPC
If user wishes they can pass the generated code through some nmake-pretty tools.
So, +1 for not forcing the code to comply with 80-column rule.
However, we have other formatting issues in generated code which are
not related 80-column rule - indentation, extra empty lines etc.
- venkat
On 7/27/
[ http://issues.apache.org/jira/browse/AXIS2-96?page=all ]
Srinath Perera resolved AXIS2-96:
-
Resolution: Fixed
I choose #2, engageing twice will not throw a exception
> Call.isModuleEngaged(QName) will be useful
> -
Hi Shahi, Ashutosh
There is no difference between cline side and server side you have to do the
something in both side , so the way of adding module in client side is
first create repository
create modules directory inside that
then put your module.mar into that
and use call's constructor whic
[ http://issues.apache.org/jira/browse/AXIS2-74?page=all ]
Srinath Perera updated AXIS2-74:
Priority: Minor (was: Critical)
Bringing down the prority of issues that are not supported in 1.0
> Full Infoset support in AXIOM
>
Yep, I did that, and the module.xml was present in the repository. I am
still facing this problem. Any ideas?
Ashutosh
-Original Message-
From: Saminda Abeyruwan [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 27, 2005 8:50 AM
To: axis-dev@ws.apache.org
Subject: Re: [Axis2]client side ha
http://ws.apache.org/axis2/api/ is outdated and we are no longer maintaining
that. Anyway, I can't see a link to that in the site.
The reason for not maintaining that is the api has very large number of
files and its difficult to upload them at each and every time. If one need
to access the api, h
No no, its not only for you, we are with you :).
Anyway, it was due to a file that has not being added the repo. We added it
and now the build should work
Chinthaka
> -Original Message-
> From: jayachandra [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, July 26, 2005 6:46 PM
> To: axis-dev@ws
Hi Glen and all,
My intention of putting that in the EPR class itself is to avoid having
another class for each and every EPR type. I think this is what you also
have mentioned by saying " to have an addressing.ToHeader type which
extended EndpointReference ". This extension will contain nothing e
[ http://issues.apache.org/jira/browse/AXIS-2121?page=all ]
Davanum Srinivas resolved AXIS-2121:
Resolution: Fixed
Checked in a fix to
ws-axis/java/src/org/apache/axis/message/SOAPFaultBuilder.java. Please check
latest CVS.
thanks,
dims
> CL
[
http://issues.apache.org/jira/browse/AXIS-2121?page=comments#action_12316843 ]
Davanum Srinivas commented on AXIS-2121:
Could you please add a trace (soap message) that triggers this behavior?
thanks,
dims
> CLONE -IncompatibleClassChangeError wh
[
http://issues.apache.org/jira/browse/AXIS-2119?page=comments#action_12316842 ]
Davanum Srinivas commented on AXIS-2119:
can you please check the logs in your tomcat? we need a stack trace to do
anything meaningful.
thanks,
dims
> ?wsdl returns h
[ http://issues.apache.org/jira/browse/AXIS-2133?page=all ]
Davanum Srinivas resolved AXIS-2133:
Resolution: Fixed
got fixed in later versions of axis. closing for now. please ping us and we can
reopen it if you see it in 1.2.1 or above.
-- di
[
http://issues.apache.org/jira/browse/AXIS-2134?page=comments#action_12316838 ]
Davanum Srinivas commented on AXIS-2134:
Is this patch ok? i fixed it in CVS like this. thanks, dims
Index: ManagedMemoryDataSource.java
==
[ http://issues.apache.org/jira/browse/AXIS-2134?page=all ]
Davanum Srinivas resolved AXIS-2134:
Resolution: Fixed
I checked in a fix (see last comment). Please verify.
thanks,
dims
> ManagedMemoryDataSource does not correctly handle large att
[ http://issues.apache.org/jira/browse/AXIS-2135?page=all ]
Davanum Srinivas resolved AXIS-2135:
Resolution: Fixed
Applied patch.
thanks,
dims
> CastorSerializer 1.2/1.2.1 does not handle arrays correctly
>
Shahi, Ashutosh wrote:
Hi all,
I am facing some problem with the deployment of client-side handlers
in Axis2. I am not sure if I am doing the correct thing, so wanted to
confirm.
I create the handlers and add that information in module.xml as we do
at the server end and finally call call.e
[
http://issues.apache.org/jira/browse/AXIS-2132?page=comments#action_12316834 ]
Davanum Srinivas commented on AXIS-2132:
Hmmm...could you please try Axis 1.2.1? i don't see any pathways in the code
where a DocumentBuilderFactory can get created wit
[ http://issues.apache.org/jira/browse/AXIS-2137?page=all ]
Davanum Srinivas resolved AXIS-2137:
Resolution: Won't Fix
no guarantees on this kind of behavior
thanks,
dims
> Holder parameters are lost in generated stubs
> --
[
http://issues.apache.org/jira/browse/AXIS-2136?page=comments#action_12316832 ]
Davanum Srinivas commented on AXIS-2136:
Simon,
how soon can you get this to me?
thanks,
dims
> support request & response gzip compression on HTTP transport
> --
[ http://issues.apache.org/jira/browse/AXIS-2142?page=all ]
Davanum Srinivas resolved AXIS-2142:
Resolution: Fixed
Applied.
thanks,
dims
> ClassCastException in JavaUtils.convert
> ---
>
> Key: AXIS
[ http://issues.apache.org/jira/browse/AXIS-2139?page=all ]
Davanum Srinivas reassigned AXIS-2139:
--
Assign To: Venkat Reddy
> SAX recorder is dirty after deserialization
> ---
>
> Key: AXIS-2139
>
will take some getting used to...choice #1, we still have to be
careful and use '_' right? or am i missing something?
-- dims
On 7/26/05, Glen Daniels <[EMAIL PROTECTED]> wrote:
> Hi Tom, all:
>
> IMO, there should be exactly *one* "extra" API on the generated class, and
> that thing should give
+1
On 7/26/05, Glen Daniels <[EMAIL PROTECTED]> wrote:
> Hey all:
>
> I just noticed that our EndpointReference class has this field which doesn't
> make any sense. An EndpointReference is just that, an EPR. The fact that a
> given EPR happens to be a wsa:To header, or a myNS:Whatever header,
Hey all:
I just noticed that our EndpointReference class has this field which doesn't
make any sense. An EndpointReference is just that, an EPR. The fact that a
given EPR happens to be a wsa:To header, or a myNS:Whatever header, does not
matter to the type itself, and therefore this field sh
Hi Tom, all:
IMO, there should be exactly *one* "extra" API on the generated class, and
that thing should give you access to all the Axis2-specific functionality.
This could be done in several ways:
- 1 -
class StubAPI {
public MessageContext getMessageContext();
...etc (Axis APIs)...
[
http://issues.apache.org/jira/browse/AXIS-2141?page=comments#action_12316801 ]
Davanum Srinivas commented on AXIS-2141:
Reading up on this...Here's some interesteing code that we can reuse:
http://www.koders.com/java/fid7CA7F685A43D3B8BD45166093033
I will be out of the office starting July 25, 2005 and will not return
until August 1, 2005.
I am now out of the office for 1 week and will be returning on Monday 1st
August. If you need assistance, please contract John Hawkins.
Ajith,
Don't these extra functions need to begin with "_" to avoid conflicting
with generated operation methods?
--
Tom Jordahl
Macromedia Server Development
> -Original Message-
> From: Ajith Harshana Ranabahu (JIRA) [mailto:[EMAIL PROTECTED]
> Sent: Monday, July 25, 2005 5:13 AM
> To:
+1 to reverting line breaks in the
templates.
Who cares if generated code has 132
character lines? I don’t….
--
Tom Jordahl
Macromedia Server Development
From: Ajith Ranabahu
[mailto:[EMAIL PROTECTED]
Sent: Monday, July 25, 2005 1:19
AM
To: Axis developer list
Subject:
Guys,
Just a quick note on this, you have to make sure that *all* of the
support APIs on the stub class start with "_" (underscore). Otherwise
if a service has a method named "setTransportInfo", bad things may
happen.
Yes, we did get this wrong in Axis 1.x. :-{
--
Tom Jordahl
Macromedia Server
Array serialization error with multiple namespaces
--
Key: AXIS-2143
URL: http://issues.apache.org/jira/browse/AXIS-2143
Project: Apache Axis
Type: Bug
Components: Serialization/Deserialization
Versions: 1.2.1
if databinding selection happens during code generation how user can
plugin their own databinding?
and in particular what about case when user wants to apply different
databinding for different parts of SOAP/XML message?
thanks,
alek
Ajith Ranabahu wrote:
Hi Jaya,
Well. You are quite righ
I will be out of the office starting July 25, 2005 and will not return
until August 1, 2005.
I am now out of the office for 1 week and will be returning on Monday 1st
August. If you need assistance, please contract John Hawkins.
[ http://issues.apache.org/jira/browse/AXIS-2142?page=all ]
Archit Shah updated AXIS-2142:
--
Attachment: DH.patch
This patch replaces the calls to getContent with calls to getInputStream in
four locations (3 in JavaUtils and 1 in SourceDataHandlerDeserializ
ClassCastException in JavaUtils.convert
---
Key: AXIS-2142
URL: http://issues.apache.org/jira/browse/AXIS-2142
Project: Apache Axis
Type: Bug
Versions: current (nightly)
Environment: Axis 1.2 CVS using GNU classpathx javam
[
http://issues.apache.org/jira/browse/AXIS2-80?page=comments#action_12316780 ]
Simon Fell commented on AXIS2-80:
-
For SOAP 1.1 at least, the specs are clear that the charset indicated in the
content-type header overrides any charset you might sniff from th
Navin -
My mistake I was referring to Axis 1.2RC3.
a quck look at http://ws.apache.org/axis2/api/
shows call has a setAction, yet it has a "todo" next to it.
Sorry for the confusion..
On Tue, 26 Jul 2005, Navinkumar Shetty wrote:
> Thanks for the reply.
> However, I do NOT see the "setUseSO
Thanks for the reply.
However, I do NOT see the "setUseSOAPAction method in
_call. What version of Axis2 are you using?
I am using 0.9
Regards,
Navin
--- csj <[EMAIL PROTECTED]> wrote:
> Navin -
>
> I've never had this particular problem, but
> something to look into..
>
> make sure...
>
> _ca
Indigo Interop - UTF-16
---
Key: AXIS-2141
URL: http://issues.apache.org/jira/browse/AXIS-2141
Project: Apache Axis
Type: Improvement
Reporter: Davanum Srinivas
[snippet from kirill's email]
The reason I am asking is that current POR for In
Hi folks!
This is an automatic reminder that the weekly Axis2 developer chat
will be occurring tomorrow, July 27, at:
7PM PDT, 10PM EDT, 2AM GMT, 8AM (next day) SLT, 12PM (next day) AEST
The chat takes place on the freenode IRC network, (use server
irc.freenode.net), on channel #apache-axis, and
[
http://issues.apache.org/jira/browse/AXIS2-80?page=comments#action_12316773 ]
Davanum Srinivas commented on AXIS2-80:
---
More feedback/questions from Kirill:
- XML1.0 requires to put BOM for entities encoded with utf-16, do you
think you could file a
Hi all,
I am facing some problem with the deployment of client-side
handlers in Axis2. I am not sure if I am doing the correct thing, so wanted to
confirm.
I create the handlers and add that information in module.xml
as we do at the server end and finally call call.engageModule() method.
[
http://issues.apache.org/jira/browse/AXIS-2140?page=comments#action_12316761 ]
Rodrigo Ruiz commented on AXIS-2140:
It also happens when using parameters of "wrapper holder" types. If I have a
method in the server with a signature:
public void proces
I will be out of the office starting July 25, 2005 and will not return
until August 1, 2005.
I am now out of the office for 1 week and will be returning on Monday 1st
August. If you need assistance, please contract John Hawkins.
[
http://issues.apache.org/jira/browse/AXIS-2140?page=comments#action_12316760 ]
Rodrigo Ruiz commented on AXIS-2140:
I am experiencing this bug with Axis 1.2.1 release version. Primitive wrapper
types are not made nillable from Java2WSDL.
I am using t
CLONE -Java2WSDL not generating nillable attribute for primitive wrapper types
--
Key: AXIS-2140
URL: http://issues.apache.org/jira/browse/AXIS-2140
Project: Apache Axis
Type: Bug
Component
Just to clarify:
WS-I Attachment Profile 1.0 describes how to send attachments with
SOAP 1.1 messages based on the SOAP with Attachments (SwA)
specification using MIME packaging. WS-I endorsed SwA because it is
more broadly implemented than any other attachment mechanism. Keep in
mind that SwA is
[
http://issues.apache.org/jira/browse/AXIS-2113?page=comments#action_12316755 ]
Davanum Srinivas commented on AXIS-2113:
Glen:
I think SchemaUtils.getCollectionComponentQName() is skipping some
complex types from being added to Symbol table, and ma
Simplest way to test is to run SimpleAxisServer with
com.sun.management.jmxremote set on the prompt (using JDK1.5) and then
run jconsole with the pid
http://java.sun.com/j2se/1.5.0/docs/guide/management/agent.html
http://java.sun.com/j2se/1.5.0/docs/tooldocs/share/jconsole.html
http://java.sun.com
great!!
On 7/26/05, Eran Chinthaka <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Code has been changed and committed to handle SOAP messages properly for
> following scenarios.
>
> 1. The sending message is of the same version as the recd message. (if SOAP
> 1.1 message is recd the sending message is SOA
Tony,
PLEASE open a bug report ("new feature") for things you need from
Axis. Whether it is 1.X or 2.X.
thanks,
dims
On 7/26/05, Tony Opatha <[EMAIL PROTECTED]> wrote:
>
>
> I agree SOAP with (MIME) Attachment is probably more interoperable than
> DIME.
>
> However, keep in mind that WS-
no.
On 7/26/05, Yege Li (SH/RDC) <[EMAIL PROTECTED]> wrote:
>
> > Hello,
> >
> > I have a question regarding encryption and export control. Does Axis 1.2
> > include any SW encryption algorithm that restricts export (i.e. special
> > ECCN code)? Thanks.
> >
> > Best regards, Yege Li
> >
> >
> >
IIRC, it should go into MessageReceiver which is opposite of stub on
client-side.
- venkat
On 7/26/05, jayachandra <[EMAIL PROTECTED]> wrote:
> Okay got it!
>
> One small confusion, will the actual ser/deser work go into Message
> Receiver (I hope not) or the skeleton on server side.
> If I got
Hi!
I was trying to update and build the axis2 svn code on my machine but...
the latest dependency of axis-common-0.9.jar hosted at
http://ws.zones.apache.org/~dims/maven/axis/jars/axis2-common-0.9.jar
is unsatisfied because of server error with the host. Is it just for
me?
Can the jar also be alte
Hi John, We have not done any work
regarding C code generation but it is very
much possible with the current architecture of the code generator. The
primary thing you have to do is to write an XSLT that generates the
relevant C code!
As a proof of our flexibility we
plan to ship C# code
Okay got it!
One small confusion, will the actual ser/deser work go into Message
Receiver (I hope not) or the skeleton on server side.
If I got your idea right, on the client side this ser and deser
functionality should go into the generated stub object, isn't it?
Best regards
Jayachandra
On 7/2
[
http://issues.apache.org/jira/browse/AXIS2-74?page=comments#action_12316746 ]
Jayachandra Sekhara Rao Sunkara commented on AXIS2-74:
--
Dims!
Done.
> Full Infoset support in AXIOM
> -
>
> Key: AXIS2
Yup. The data binding is interfaced to the
engine through the Message receiver that will also be generated. Serialization
and deserialization is handled by the data binding framework.
Chathura
From: Ajith Ranabahu [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 26, 2005
Hi Jaya,
Well. You are quite right. Right now core has no such dependancy on the
databinding. The idea is to incorporate databound objects when
skeletons are code generated. Our plan is to generate the databound
objects, skeletons and the relevant message receiver when skeletons are
generated.
The
Hi folks,
I wasn't aware that the C generation
was actually being implemented. Is it actually happening and being tested
or are we just investigating?
thanks,
John.
Ajith Ranabahu <[EMAIL PROTECTED]>
26/07/2005 12:41
Please respond to
axis-dev
To
axis-dev@ws.apache.org, Venkat
Re
[
http://issues.apache.org/jira/browse/AXIS2-74?page=comments#action_12316744 ]
Davanum Srinivas commented on AXIS2-74:
---
Jaya,
looks good. Please check it in.
-- dims
> Full Infoset support in AXIOM
> -
>
> Key:
[
http://issues.apache.org/jira/browse/AXIS2-80?page=comments#action_12316745 ]
Davanum Srinivas commented on AXIS2-80:
---
Was reviewing Axis 1.X code for Kirill...we take into account of in the
incoming request's encoding by peeking at the charset in t
ah
Will try to fix it soon. Probably we have to put a to check nullOn 7/26/05, Venkat Reddy <[EMAIL PROTECTED]
> wrote:Ajith,Still XXXMessageReciever won't compile since it expects init method on
XXXSkeleton and the JUnit TestCase XXXLocalTestcase won't compile dueto broken code like the followin
Ajith et al,
In axis2 there is some databinding code present, but looks that only
codegen of wsdl module is using it and not any other module like core
etc. seems like using it. The existing typemapping framework is
registering only the xml type and java type names in the map, and with
just that m
Ajith,
Still XXXMessageReciever won't compile since it expects init method on
XXXSkeleton and the JUnit TestCase XXXLocalTestcase won't compile due
to broken code like the following,
//create a new databinder
.echoStringDatabindingSupporter databindSupporter = new ..
Note
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-xerces-HEAD has an issue affecting its community integration.
This issue
Hi Venkat,
Actually the 80 column change that was done some time back has caused
this problem. Now the templates are reverted and it should work if you
get the latest from SVNOn 7/26/05, Venkat Reddy <[EMAIL PROTECTED]> wrote:
I just tried it with some simplest wsdl file and code generated is notin
I just tried it with some simplest wsdl file and code generated is not
in a compilable shape with lot of illegal and unnecessary line breaks.
I thought we had this code since M2, so is it because i'm doing
something wrong?
Actually, i'm looking to use this tool to generate code for JAX-WS
stubs. I
Tony Opatha wrote:
I agree SOAP with (MIME) Attachment is probably more interoperable
than DIME.
However, keep in mind that WS-I BP 1.1 has a SOAP Attachment Profile 1.0
finalized since last year.
I believe currently WS-BP 1.1 is being supported by some commercial
Hi,
Code has been changed and committed to handle SOAP messages properly for
following scenarios.
1. The sending message is of the same version as the recd message. (if SOAP
1.1 message is recd the sending message is SOAP 1.1 too) - this was there in
the code.
2. Getting and identifying the SOAP
[ http://issues.apache.org/jira/browse/AXIS2-96?page=all ]
Srinath Perera reassigned AXIS2-96:
---
Assign To: Srianth Perera
> Call.isModuleEngaged(QName) will be useful
> --
>
> Key: AXIS2-96
> UR
[ http://issues.apache.org/jira/browse/AXIS2-87?page=all ]
Srinath Perera reassigned AXIS2-87:
---
Assign To: Eran Chinthaka
> Faults based on SOAP version?
> -
>
> Key: AXIS2-87
> URL: http://issues.apache.or
Separating sample and test cases form Sample module
---
Key: AXIS2-100
URL: http://issues.apache.org/jira/browse/AXIS2-100
Project: Apache Axis 2.0 (Axis2)
Type: Wish
Components: samples, build,site & docs
Repo
[ http://issues.apache.org/jira/browse/AXIS2-79?page=all ]
Srinath Perera reassigned AXIS2-79:
---
Assign To: Eran Chinthaka
> AddressingInHandler doesn't set the properly
> -
>
> Key: AXIS2-79
[ http://issues.apache.org/jira/browse/AXIS-2132?page=all ]
xiao-fei song updated AXIS-2132:
Attachment: UojDocumentService.xml
> WSDL document object generated by AxisServer can not be read successfully
> using WSDL4J API
>
[ http://issues.apache.org/jira/browse/AXIS-2132?page=all ]
xiao-fei song updated AXIS-2132:
Attachment: QSWSDLHandler.java
> WSDL document object generated by AxisServer can not be read successfully
> using WSDL4J API
>
I will be out of the office starting July 25, 2005 and will not return
until August 1, 2005.
I am now out of the office for 1 week and will be returning on Monday 1st
August. If you need assistance, please contract John Hawkins.
[
http://issues.apache.org/jira/browse/AXIS-2132?page=comments#action_12316724 ]
xiao-fei song commented on AXIS-2132:
-
Some more investigations have been made which reveal that the issue is caused
by the combination between axis and xerces xml parser.
[ http://issues.apache.org/jira/browse/AXIS2-99?page=all ]
Ruchith Fernando updated AXIS2-99:
--
Attachment: OMBlankElementTest.java
Test case for empty element name value\:
OMFactory factory = OMAbstractFactory.getOMFactory();
OM allows the element name to be null
-
Key: AXIS2-99
URL: http://issues.apache.org/jira/browse/AXIS2-99
Project: Apache Axis 2.0 (Axis2)
Type: Bug
Components: om
Versions: 0.9
Reporter: Ruchith Fernando
Priorit
InOutMEPClient.invokeBlocking() can not expect to have a Exception element in a
Fault message
-
Key: AXIS2-98
URL: http://issues.apache.org/jira/browse/AXIS2-98
Project: Apache Axis
> Hello,
>
> I have a question regarding encryption and export control. Does Axis 1.2
> include any SW encryption algorithm that restricts export (i.e. special ECCN
> code)? Thanks.
>
> Best regards, Yege Li
>
>
>
>
>
[ http://issues.apache.org/jira/browse/AXIS2-74?page=all ]
Jayachandra Sekhara Rao Sunkara updated AXIS2-74:
-
Attachment: PInCommentImplModify.patch
Am attaching the patch for here community review. If there aren't any
objections will co
[
http://issues.apache.org/jira/browse/AXIS2-74?page=comments#action_12316720 ]
Jayachandra Sekhara Rao Sunkara commented on AXIS2-74:
--
Hi all!
On a latest SVN copy I was able to get a success count of 542 initially today.
The reasons f
Turn off web services through Axis2 web admin module
Key: AXIS2-97
URL: http://issues.apache.org/jira/browse/AXIS2-97
Project: Apache Axis 2.0 (Axis2)
Type: New Feature
Reporter: Deepal Jayasinghe
Assigned to:
Call.isModuleEngaged(QName) will be useful
--
Key: AXIS2-96
URL: http://issues.apache.org/jira/browse/AXIS2-96
Project: Apache Axis 2.0 (Axis2)
Type: Improvement
Components: client-api
Versions: 0.9
Reporter: Go
92 matches
Mail list logo
