[
http://issues.apache.org/jira/browse/AXIS2-1268?page=comments#action_12439062 ]
Xia Zhao commented on AXIS2-1268:
-
Thanks for your reply, dims.
I provide the way I create my services and attached related files. Hope these
helpful.
I followed
[ http://issues.apache.org/jira/browse/AXIS2-1268?page=all ]
Xia Zhao updated AXIS2-1268:
Attachment: AnalysisMethod.java
> Unexpected subelement - problem of correctly invoking services
> --
>
>
[ http://issues.apache.org/jira/browse/AXIS2-1268?page=all ]
Xia Zhao updated AXIS2-1268:
Attachment: AnalysisMethod1.java
> Unexpected subelement - problem of correctly invoking services
> --
>
>
[ http://issues.apache.org/jira/browse/AXIS2-1268?page=all ]
Xia Zhao updated AXIS2-1268:
Attachment: Job.java
> Unexpected subelement - problem of correctly invoking services
> --
>
>
[ http://issues.apache.org/jira/browse/AXIS2-1264?page=all ]
Eran Chinthaka resolved AXIS2-1264.
---
Fix Version/s: 1.1
Resolution: Fixed
Fixed in 451907.
> java.lang.RuntimeException: Unexpected subelement (xs:any)
>
[ http://issues.apache.org/jira/browse/AXIS2-1268?page=all ]
Xia Zhao updated AXIS2-1268:
Attachment: AnalysisMethod1Skeleton.java
> Unexpected subelement - problem of correctly invoking services
>
[
http://issues.apache.org/jira/browse/AXIS2-1163?page=comments#action_12439066 ]
Dennis Sosnoski commented on AXIS2-1163:
It makes sense to support endpoint address modification. We should not assume
that endpoint address modification s
[
http://issues.apache.org/jira/browse/AXIS2-653?page=comments#action_12439068 ]
Eran Chinthaka commented on AXIS2-653:
--
Dims,
I added a comment for Handler and AbstractHandler. Please take a look at them
and downgrade the priority if you
Hey dims,
Thanks again for your fast support. Are your changes already in the
current nightly builds (with these, I get the same message at the
moment), or have I to checkput current svn version?
best regards,
Kai
On 10/2/06, Davanum Srinivas (JIRA) <[EMAIL PROTECTED]> wrote:
[ http://iss
[
http://issues.apache.org/jira/browse/AXIS2-1252?page=comments#action_12439073 ]
Venkatakrishnan commented on AXIS2-1252:
Hi.. thanks.
Well, looking at the src there, I observe that HelloBean belongs to the package
named 'test'. Hence
Hi Devs,If an .aar contains a "www" folder with web resources (html, js, css, etc), in embeddable version (war), resource urls will not work due to the following reason.In the web.xml provided, there exists the following entry,
/axis2-web/index.jsp This will cause the following problem. Say,
[
http://issues.apache.org/jira/browse/AXIS2-1268?page=comments#action_12439078 ]
Thilina Gunarathne commented on AXIS2-1268:
---
Seems like you are using Axis2 1.0
Please use the latest nightly builds available at
http://people.apac
[
http://issues.apache.org/jira/browse/AXIS2-1206?page=comments#action_12439081 ]
Keith Godwin Chapman commented on AXIS2-1206:
-
I'm using the latest version. The issue is still there.
> Cannot load a jar with a different version one
Samples folder structure is not convenient
--
Key: AXIS2-1281
URL: http://issues.apache.org/jira/browse/AXIS2-1281
Project: Apache Axis 2.0 (Axis2)
Issue Type: Wish
Components: samples, build
[
http://issues.apache.org/jira/browse/AXIS2-1268?page=comments#action_12439083 ]
Xia Zhao commented on AXIS2-1268:
-
Hi,
I've tried to use Java2WSDL in the nightly builds. However, I encounter an
error:
An error occurred while generating code
[ http://issues.apache.org/jira/browse/AXIS2-917?page=all ]
Eran Chinthaka resolved AXIS2-917.
--
Fix Version/s: 1.1
Resolution: Fixed
Samples added to Axis2.
> User guide should give explanation and examples of fault handling
> -
[ http://issues.apache.org/jira/browse/AXIS2-1075?page=all ]
Eran Chinthaka resolved AXIS2-1075.
---
Fix Version/s: 1.1
Resolution: Fixed
This has already been fixed. Sorry didn't see this earlier by the time I was
fixing it.
> AxisService shoul
[
http://issues.apache.org/jira/browse/AXIS2-1052?page=comments#action_12439094 ]
Eran Chinthaka commented on AXIS2-1052:
---
Hi Richard,
I just used a wsdl which has a custom fault defined in it. And it seems all the
issues linked from this
[ http://issues.apache.org/jira/browse/AXIS2-929?page=all ]
Eran Chinthaka resolved AXIS2-929.
--
Fix Version/s: 1.1
Resolution: Won't Fix
Hi Sandakith,
I tried to apply this patch, but the original file has changed a lot and I can
not simply app
[
http://issues.apache.org/jira/browse/AXIS2-1258?page=comments#action_12439097 ]
indika priyantha kumara commented on AXIS2-1258:
hi dims
i tested again three times with newly built jars. But same error was occurred.
It is seem
[
http://issues.apache.org/jira/browse/AXIS2-1220?page=comments#action_12439099 ]
Eran Chinthaka commented on AXIS2-1220:
---
Hi Bob,
We divide the the whole context in to two. Context path and service root.
if the url is something like htt
[ http://issues.apache.org/jira/browse/AXIS2-1258?page=all ]
Thilina Gunarathne reopened AXIS2-1258:
---
Re open as per the comment
https://issues.apache.org/jira/browse/AXIS2-1258#action_12439097
> Problem in ADB code generation for a WSDL
+1 !! and may be we should keep adding the best practises to developer
guide .. to make sure they are kept track of
On 10/2/06, Eran Chinthaka <[EMAIL PROTECTED]> wrote:
Hi,
When you fix a bug and resolve a JIRA, let's make it a best practice to
include the revision number in the comment you pu
wsa:Action setting in client side
--
Key: AXIS2-1282
URL: http://issues.apache.org/jira/browse/AXIS2-1282
Project: Apache Axis 2.0 (Axis2)
Issue Type: Bug
Components: Addressing
Environment
[
http://issues.apache.org/jira/browse/AXIS2-1268?page=comments#action_12439107 ]
Xia Zhao commented on AXIS2-1268:
-
Hi,
I managed to build my service using nightly builds. This time I just builds an
even simple service which read input job st
[ http://issues.apache.org/jira/browse/AXIS2-1268?page=all ]
Xia Zhao updated AXIS2-1268:
Attachment: Analysis.xml
> Unexpected subelement - problem of correctly invoking services
> --
>
>
[ http://issues.apache.org/jira/browse/AXIS2-1268?page=all ]
Xia Zhao updated AXIS2-1268:
Attachment: errortrace.rtf
> Unexpected subelement - problem of correctly invoking services
> --
>
>
Hi,There are a number of spelling mistakes/convention violations in some of the Axis2 API methods. e.g. public void disEngageModule(QName moduleName);
Should be disengageModule(QName)In the axis2.xml the phase orders types named as follows:
As can be seen, no convention has been followed in na
+1 for the Deepal's idea...
So here's the plan..
Let's get rid of 1_0 directory as the first step.. Its highly unlike
that we get a change request for the 1.0 docs... In the rare case we
need to do that, we can create a separate branch of 1.0 documents as
an when needed..
Then move the contents
On Mon, 2006-10-02 at 17:19 +0530, Afkham Azeez wrote:
> Hi,
> There are a number of spelling mistakes/convention violations in some
> of the Axis2 API methods.
>
> e.g. public void disEngageModule(QName moduleName);
> Should be disengageModule(QName)
>
> In the axis2.xml the phase orders t
Hello All,
I think it is a great idea to have the
svn revision in the JIRA. Instead of explicitly commenting the JIRA,
there may be an easier way:
It seems that if, when you do your commit,
you put the JIRA number in the comment, some magic happens and the SVN
revision and commit message is add
[
http://issues.apache.org/jira/browse/AXIS2-1268?page=comments#action_12439131 ]
Xia Zhao commented on AXIS2-1268:
-
Hi,
I noticed that in my generated WSDL file, the location soap address is
http://192.168.225.1:8080/axis2/services/Analysis, b
Please do.
+1
-Bill
On Mon, 2006-10-02 at 17:19 +0530, Afkham Azeez wrote:
> Hi,
> There are a number of spelling mistakes/convention violations in some
> of the Axis2 API methods.
>
> e.g. public void disEngageModule(QName moduleName);
> Should be disengageModule(QName)
>
> In the axis2.
I wanted to clarify that what I meant
by putting the "JIRA number in the comment" was put the JIRA
number in the first line of the commit message when you commit your changes.
I put that JIRA number on a line by itself (for example "AXIS2-1195",
minus the quotes, for the example blow), so I know
[
http://issues.apache.org/jira/browse/AXIS2-1138?page=comments#action_12439181 ]
Thilina Gunarathne commented on AXIS2-1138:
---
I was able to fix the issue in my local Axis2..But the fix involved fixing a
bug in XMLSchema.. On other wor
I submitted a patch for this last week. How do I get the patch into svn?
Its currently Unassigned, can I assign it?
Thanks,
Nate
___
Notice: This email message, together with any attachments, may contain
information of BEA S
Hi Thilina,
The current plan was implemented earlier to enable both the convenience
of the people who are managing docs and to minimize the effect on others
when they checkout.
But if people think, following is the correct way, I have no objections
for that. But remember who ever putting the link
[
http://issues.apache.org/jira/browse/AXIS2-1259?page=comments#action_12439197 ]
vladi vladii commented on AXIS2-1259:
-
So there s a need to download source code? Now I use jars from standard axis
distribuiton. I have found that methode OMT
[ http://issues.apache.org/jira/browse/AXIS2-1268?page=all ]
Eran Chinthaka resolved AXIS2-1268.
---
Fix Version/s: 1.1
Resolution: Fixed
Can you please open a new JIRA from your new issues. Let's resolve this for now.
That will help for some one
Interesting idea.
I also used to put the JIRA number in the comment of the SVN commit
(rather Dims once forced me to do so ;) ), but never checked it in JIRA.
In whichever way, when you resolve a JIRA, let's either
- put the JIRA number on the first line of the comment going with the
SVN commit
org.apache.axis2.AxisFault: Operation not found
---
Key: AXIS2-1283
URL: http://issues.apache.org/jira/browse/AXIS2-1283
Project: Apache Axis 2.0 (Axis2)
Issue Type: Bug
Affects Versions: night
[ http://issues.apache.org/jira/browse/AXIS2-1283?page=all ]
Xia Zhao updated AXIS2-1283:
Attachment: Analysis.xml
> org.apache.axis2.AxisFault: Operation not found
> ---
>
> Key: AXIS2-1283
>
Kai,
The nightly builds are using the release version of xmlschema. You
will have to build the xmlschema from svn (or wait for us a bit to
change back to xmlschema snapshots).
-- dims
On 10/2/06, Kai Hüner <[EMAIL PROTECTED]> wrote:
Hey dims,
Thanks again for your fast support. Are your chang
[ http://issues.apache.org/jira/browse/AXIS2-653?page=all ]
Davanum Srinivas updated AXIS2-653:
---
Priority: Critical (was: Blocker)
downgrading after javadoc'ing the issues.
> Handler method "cleanup" is never called
>
RejectedExecutorException on multiple Async Invokes
---
Key: AXIS2-1284
URL: http://issues.apache.org/jira/browse/AXIS2-1284
Project: Apache Axis 2.0 (Axis2)
Issue Type: Bug
Component
[ http://issues.apache.org/jira/browse/AXIS2-1284?page=all ]
Nikhil Thaker updated AXIS2-1284:
-
Attachment: JIRA_1284_UseExecutorFromPool.txt
Attached is the fix for this JIRA.
> RejectedExecutorException on multiple Async Invokes
>
[
http://issues.apache.org/jira/browse/AXIS2-1138?page=comments#action_12439334 ]
Davanum Srinivas commented on AXIS2-1138:
-
+1 from me. but wait for a few more days to see if anything eslse pops up.
> Generated client code does not hand
[
http://issues.apache.org/jira/browse/AXIS2-1206?page=comments#action_12439335 ]
Davanum Srinivas commented on AXIS2-1206:
-
can u please upload your aar?
-- dims
> Cannot load a jar with a different version ones axis loads its jars
> -
+1
On 10/2/06, Bill Nagy <[EMAIL PROTECTED]> wrote:
Please do.
+1
-Bill
On Mon, 2006-10-02 at 17:19 +0530, Afkham Azeez wrote:
> Hi,
> There are a number of spelling mistakes/convention violations in some
> of the Axis2 API methods.
>
> e.g. public void disEngageModule(QName moduleName);
>
+1
On 10/2/06, Saminda Abeyruwan <[EMAIL PROTECTED]> wrote:
Hi Devs,
If an .aar contains a "www" folder with web resources (html, js, css, etc),
in embeddable version (war), resource urls will not work due to the
following reason.
In the web.xml provided, there exists the following entry,
[ http://issues.apache.org/jira/browse/AXIS2-1265?page=all ]
Jeff Barrett resolved AXIS2-1265.
-
Resolution: Fixed
Patch commited
> Doc/Lit Bare soap body elements missing namespace.
> --
>
>
[ http://issues.apache.org/jira/browse/AXIS2-1265?page=all ]
Jeff Barrett closed AXIS2-1265.
---
> Doc/Lit Bare soap body elements missing namespace.
> --
>
> Key: AXIS2-1265
> URL: h
[ http://issues.apache.org/jira/browse/AXIS2-1273?page=all ]
Jeff Barrett resolved AXIS2-1273.
-
Resolution: Fixed
Patch commited
> OneWayOperation NPE
> ---
>
> Key: AXIS2-1273
> URL: http://issues.apache
[ http://issues.apache.org/jira/browse/AXIS2-1273?page=all ]
Jeff Barrett closed AXIS2-1273.
---
> OneWayOperation NPE
> ---
>
> Key: AXIS2-1273
> URL: http://issues.apache.org/jira/browse/AXIS2-1273
> P
[ http://issues.apache.org/jira/browse/AXIS2-1262?page=all ]
Jeff Barrett resolved AXIS2-1262.
-
Resolution: Fixed
Patch commited
> AsyncCallback Hang As
> -
>
> Key: AXIS2-1262
> URL: http://issues.apa
[ http://issues.apache.org/jira/browse/AXIS2-1262?page=all ]
Jeff Barrett closed AXIS2-1262.
---
> AsyncCallback Hang As
> -
>
> Key: AXIS2-1262
> URL: http://issues.apache.org/jira/browse/AXIS2-1262
>
[
http://issues.apache.org/jira/browse/AXIS2-1252?page=comments#action_12439362 ]
Kinichiro Inoguchi commented on AXIS2-1252:
---
Hi Venkat,
Thanks for good explanations.
I just believed that namespace of "type" used by service
is same
[
http://issues.apache.org/jira/browse/AXIS2-805?page=comments#action_12439364 ]
Kinichiro Inoguchi commented on AXIS2-805:
--
AXIS2-1252 is same kind of issue.
The namespace of "type" used by service as IN/OUT
comes from package name of
[ http://issues.apache.org/jira/browse/AXIS2-1285?page=all ]
Kinichiro Inoguchi updated AXIS2-1285:
--
Attachment: WsdlTest2.aar
I'll attach WsdlTest2.aar for reproduce this issue.
> Invalid namespace in response by RPCMessagaReceiver
> -
Invalid namespace in response by RPCMessagaReceiver
---
Key: AXIS2-1285
URL: http://issues.apache.org/jira/browse/AXIS2-1285
Project: Apache Axis 2.0 (Axis2)
Issue Type: Bug
Component
+1.. Lets go ahead and do this before the release.
Thilina
On 10/3/06, Davanum Srinivas <[EMAIL PROTECTED]> wrote:
+1
On 10/2/06, Bill Nagy <[EMAIL PROTECTED]> wrote:
> Please do.
>
> +1
>
> -Bill
> On Mon, 2006-10-02 at 17:19 +0530, Afkham Azeez wrote:
> > Hi,
> > There are a number of spelli
[ http://issues.apache.org/jira/browse/AXIS2-1284?page=all ]
Nick Gallardo closed AXIS2-1284.
Resolution: Fixed
Fixed in SVN version 452305.
> RejectedExecutorException on multiple Async Invokes
> ---
>
>
+1.
At the same time please make sure you change all the places, especially
look for places which has these names hard coded. I know the IDE you are
using has very good support for this ;).
-- Chinthaka
Afkham Azeez wrote:
> Hi,
> There are a number of spelling mistakes/convention violations i
[ http://issues.apache.org/jira/browse/AXIS2-1219?page=all ]
Eran Chinthaka resolved AXIS2-1219.
---
Resolution: Fixed
This seems to be fixed some time back.
Please see
http://svn.apache.org/viewvc/webservices/axis2/trunk/java/modules/integration/test/o
[
http://issues.apache.org/jira/browse/AXIS2-1280?page=comments#action_12439393 ]
indika priyantha kumara commented on AXIS2-1280:
i have found a compile error in generated test case
there is a coma with method parameter
RawXMLINOutMessageReceiver throws up a NPE if the business logic returns null
-
Key: AXIS2-1286
URL: http://issues.apache.org/jira/browse/AXIS2-1286
Project: Apache Axis 2.0 (
[
http://issues.apache.org/jira/browse/AXIS2-1286?page=comments#action_12439394 ]
Asankha C. Perera commented on AXIS2-1286:
--
test.mr.MRTest1
urn:returnNull
public class MRTest1 {
public OMElement returnNull(O
RawXMLINOnlyMessageReceiver throws a NPE if method is not found
---
Key: AXIS2-1287
URL: http://issues.apache.org/jira/browse/AXIS2-1287
Project: Apache Axis 2.0 (Axis2)
Issue Type:
[ http://issues.apache.org/jira/browse/AXIS2-1287?page=all ]
Asankha C. Perera reassigned AXIS2-1287:
Assignee: Asankha C. Perera
> RawXMLINOnlyMessageReceiver throws a NPE if method is not found
>
[ http://issues.apache.org/jira/browse/AXIS2-1287?page=all ]
Asankha C. Perera resolved AXIS2-1287.
--
Resolution: Fixed
> RawXMLINOnlyMessageReceiver throws a NPE if method is not found
> --
[ http://issues.apache.org/jira/browse/AXIS2-1286?page=all ]
Asankha C. Perera resolved AXIS2-1286.
--
Resolution: Fixed
> RawXMLINOutMessageReceiver throws up a NPE if the business logic returns null
>
You might wanna look at the names of these classes as well.
RawXMLINOutMessageReceiver, RawXMLINOutAsyncMessageReceiver,
RawXMLINOnlyMessageReceiver
See how In and Out is written.
But remember, lot of users must have used this name in their
services.xml files :).
-- Chinthaka
Afkham Azeez wr
Title: RE: Soap Request with X509 Token
Hi Ruchith,
Thanks a lot for sharing your views with me on the mentioned problem in this email.
Ruchith,I have to create the mentioned SOAP format while I am creating SOAP request i.e. before sending request to web service and don't have to do anythin
73 matches
Mail list logo
