[ http://issues.apache.org/jira/browse/AXIS2-301?page=all ]
Eran Chinthaka resolved AXIS2-301:
--
Resolution: Invalid
> Visibility of HTTP error code with CommonsHTTPSender
>
>
> Key: AXIS
Hi Deepal,
On 1/9/06, Deepal Jayasinghe <[EMAIL PROTECTED]> wrote:
> Hi Sanka ;
>
> I am not telling to add three init methods , what I want is to modify the
> init method in the useful way , giving AxisConfiguration is not enough for
> module , they might need to add some data to context at the i
[ http://issues.apache.org/jira/browse/AXIS2-281?page=all ]
Deepal Jayasinghe resolved AXIS2-281:
-
Fix Version: 0.94
Resolution: Fixed
same as ?wsdl it work both in SimpleHTTPServer and AxisServlet
> Support for "?xsd"
> --
Visibility of error code with CommonsHttpSender
---
Key: AXIS-2361
URL: http://issues.apache.org/jira/browse/AXIS-2361
Project: Apache Axis
Type: Bug
Components: Basic Architecture
Versions: 1.2
Reporter: Am
Re-use of MultiThreadedConnectionManager in CommonsHTTPSender
-
Key: AXIS-2362
URL: http://issues.apache.org/jira/browse/AXIS-2362
Project: Apache Axis
Type: Bug
Components: Basic Architecture
Versio
[ http://issues.apache.org/jira/browse/AXIS2-308?page=all ]
Eran Chinthaka resolved AXIS2-308:
--
Fix Version: 0.94
Resolution: Fixed
Patch has already been applied.
> Client API changes to have REST support (WSDL 2.0 - IRI style)
> --
[ http://issues.apache.org/jira/browse/AXIS2-315?page=all ]
Eran Chinthaka resolved AXIS2-315:
--
Fix Version: 0.94
(was: 0.93)
Resolution: Won't Fix
*MEPClient were removed and we only have ServiceClients.
> Rename InOnly
[ http://issues.apache.org/jira/browse/AXIS2-317?page=all ]
Ruchith Udayanga Fernando reassigned AXIS2-317:
---
Assign To: Ajith Harshana Ranabahu
> WSDL2java generated classes throw "Operation Not found" when wsdl
> soapAction=""
> -
[ http://issues.apache.org/jira/browse/AXIS2-333?page=all ]
Eran Chinthaka resolved AXIS2-333:
--
Fix Version: 0.94
Resolution: Fixed
ServiceClient introduction has eliminated this.
> Non blocking dual client does not receive an error when an i
[ http://issues.apache.org/jira/browse/AXIS2-369?page=all ]
Eran Chinthaka resolved AXIS2-369:
--
Fix Version: 0.94
Resolution: Fixed
Applied.
> New AXIS2 Packaging Structure
> -
>
> Key: AXIS2-369
>
[ http://issues.apache.org/jira/browse/AXIS2-364?page=all ]
Eran Chinthaka resolved AXIS2-364:
--
Resolution: Invalid
This should be filed against WS-Commons.
> XmlSchema POM
> -
>
> Key: AXIS2-364
> URL: http://issues.
[ http://issues.apache.org/jira/browse/AXIS2-357?page=all ]
Eran Chinthaka resolved AXIS2-357:
--
Fix Version: 0.94
Resolution: Fixed
Applied. Thanks.
> Axis2 Architecture Guide has been corrected and updated to 0.94 version of
> Axis2. Review
[ http://issues.apache.org/jira/browse/AXIS2-355?page=all ]
Eran Chinthaka resolved AXIS2-355:
--
Fix Version: 0.94
Resolution: Fixed
Applied. Thanks.
> Review and apply more axis2 -0.94 documents
> ---
>
[ http://issues.apache.org/jira/browse/AXIS2-356?page=all ]
Eran Chinthaka resolved AXIS2-356:
--
Fix Version: 0.94
Resolution: Fixed
Applied. Thanks.
> OMTutorial.html doc of Axis2 has been updated to 0.94 version and imrpoved
> usability and
[ http://issues.apache.org/jira/browse/AXIS2-354?page=all ]
Eran Chinthaka resolved AXIS2-354:
--
Resolution: Fixed
Already fixed.
> Test cases should be re-instated
>
>
> Key: AXIS2-354
> URL: http
[
http://issues.apache.org/jira/browse/AXIS2-348?page=comments#action_12362190 ]
Eran Chinthaka commented on AXIS2-348:
--
Reason behind us implementing the detach function was to relieve the user from
handling the links, between parents , siblings and c
[ http://issues.apache.org/jira/browse/AXIS2-345?page=all ]
Ruchith Udayanga Fernando resolved AXIS2-345:
-
Resolution: Fixed
This is fixed in ServiceClient.sendRobust(OMElement elem) throws AxisFault
> InOnly MEP should rethrow transpor
[ http://issues.apache.org/jira/browse/AXIS2-368?page=all ]
Ajith Harshana Ranabahu resolved AXIS2-368:
---
Resolution: Fixed
The issue really was that the code generator was not handling the multiple
porttypes properly. The code generator h
Invalid generated class from wsdl2java for xsd:date
---
Key: AXIS-2363
URL: http://issues.apache.org/jira/browse/AXIS-2363
Project: Apache Axis
Type: Bug
Components: WSDL processing
Versions: 1.3
Environmen
Sanjiva,
this is when the wsdl is missingand the code was generated using
w2j/xmlbeans.
-- dims
On 1/9/06, Sanjiva Weerawarana <[EMAIL PROTECTED]> wrote:
> On Mon, 2006-01-09 at 00:27 -0500, Davanum Srinivas wrote:
> > Sanjiva,
> >
> > If we generate xmlbeans databinding code, we still end u
[ http://issues.apache.org/jira/browse/AXIS2-171?page=all ]
Ajith Harshana Ranabahu resolved AXIS2-171:
---
Resolution: Fixed
The latest change to the code generator allows to specifiy the port, if not it
picks the first
> Handling multiple
[ http://issues.apache.org/jira/browse/AXIS2-270?page=all ]
Ajith Harshana Ranabahu resolved AXIS2-270:
---
Resolution: Fixed
the latest change to the codebase allows this to be done. Now parameters can be
passed to select the port to be cod
[ http://issues.apache.org/jira/browse/AXIS2-343?page=all ]
Ajith Harshana Ranabahu resolved AXIS2-343:
---
Resolution: Fixed
Done. There has been enough testing to show that this is no longer an issue
> WSDL2Java fails during code gen for m
[
http://issues.apache.org/jira/browse/AXIS2-364?page=comments#action_12362205 ]
Dan Diephouse commented on AXIS2-364:
-
There is no WS-Commons JIRA project. Dims said to attach it here.
> XmlSchema POM
> -
>
> Key: AXIS2-364
>
[
http://issues.apache.org/jira/browse/AXIS2-365?page=comments#action_12362206 ]
Davanum Srinivas commented on AXIS2-365:
The summary/description does not indicate that it needs to be stored in
services.xml. So please feel free to propose an alterna
On Mon, 2006-01-09 at 08:03 -0500, Davanum Srinivas wrote:
> Sanjiva,
>
> this is when the wsdl is missingand the code was generated using
> w2j/xmlbeans.
Those two statements are contradictory; the WSDL was there but we're
losing it when WSDL2Java generates a skeleton. That's the problem we
[
http://issues.apache.org/jira/browse/AXIS2-365?page=comments#action_12362208 ]
Sanjiva Weerawarana commented on AXIS2-365:
---
Sorry, I was referring to the email discussion we're having about keeping
target namespaces ... so the solution for this
How about we have an xml format for wom itself? that is neither wsdl11
or wsdl12? Am bringing this up to figure how how we should fix
AXIS2-365. Specifically the comment from Sanjiva here:
http://marc.theaimsgroup.com/?l=axis-dev&m=113679084111960&w=2
The idea is to store it a neutral format (neit
Sanjiva,
we need a "digested" version of the wsdl for example to deal with
wsdl's that import other wsdl's. So we can't just store the original
wsdl as-is because the url references will be broken as well.
thanks,
-- dims
On 1/9/06, Sanjiva Weerawarana <[EMAIL PROTECTED]> wrote:
> On Mon, 2006-0
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Isn't it the WSDL2Writer you are talking about ? I think WOM model is
completely WSDL2 and saving WOM means its saving a WSDL 2.0 document.
Davanum Srinivas wrote:
> How about we have an xml format for wom itself? that is neither
> wsdl11 or wsdl12?
Another thing, the problem is same if one uses XSD2Java or scomp to
generate the classes and then uses the "New Feature - making java
class a web service"
-- dims
On 1/9/06, Sanjiva Weerawarana <[EMAIL PROTECTED]> wrote:
> On Mon, 2006-01-09 at 08:03 -0500, Davanum Srinivas wrote:
> > Sanjiva,
>
[ http://issues.apache.org/jira/browse/AXIS2-364?page=all ]
Davanum Srinivas reopened AXIS2-364:
let's move it *when* we have that set up...
> XmlSchema POM
> -
>
> Key: AXIS2-364
> URL: http://issues.apache.org/jira/b
[ http://issues.apache.org/jira/browse/AXIS2-369?page=all ]
Afkham Azeez reopened AXIS2-369:
Assign To: Afkham Azeez (was: Eran Chinthaka)
More updates to be carried out on this issue
> New AXIS2 Packaging Structure
>
[ http://issues.apache.org/jira/browse/AXIS2-369?page=all ]
Afkham Azeez updated AXIS2-369:
---
Attachment: axis2.patch
Patch attached.
Modified maven.xml to properly fetch dependencies for std and min distros, and
also to reflect the proper std binary ditri
[
http://issues.apache.org/jira/browse/AXIS2-369?page=comments#action_12362215 ]
Davanum Srinivas commented on AXIS2-369:
Azeez,
Please click on granting the license to ASF. otherwise, i can't apply the patch.
thanks,
dims
> New AXIS2 Packaging St
Eran,
If that's what you prefer, then sure...but remember we can't read it
then. On a related note, AxisServiceBuilder should *NOT* be working
with WSDL4J classes. getAxisService should operate on a wom.
-- dims
On 1/9/06, Eran Chinthaka <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Devs,
As you know, we had to postpone the release due to some blockers. And
now I think they are getting ok. So thought of freezing the code from
tonight, US Time (and tomorrow, Sri Lankan time). If everything goes
well, I think we can relea
Hi all,
According to what I have heard, MTOM interop tests are done and working...
Saminda,
Please update and close this issue...
Thanks,
~Thilina
On 1/9/06, Eran Chinthaka (JIRA) <[EMAIL PROTECTED]> wrote:
[ http://issues.apache.org/jira/browse/AXIS2-78?page=all
]Eran Chinthaka reassign
+1 from me.
On 1/9/06, Sanka Samaranayake <[EMAIL PROTECTED]> wrote:
> Hi Deepal,
>
> On 1/9/06, Deepal Jayasinghe <[EMAIL PROTECTED]> wrote:
> > Hi Sanka ;
> >
> > I am not telling to add three init methods , what I want is to modify the
> > init method in the useful way , giving AxisConfiguratio
[
http://issues.apache.org/jira/browse/AXIS2-345?page=comments#action_12362234 ]
Peter McEvoy commented on AXIS2-345:
OK - this is good news. However, I am using proxies generated by the
wsdl2java tool, and it does not seem to generate client proxies
[
http://issues.apache.org/jira/browse/AXIS2-345?page=comments#action_12362238 ]
Davanum Srinivas commented on AXIS2-345:
Please open another bug :)
thanks,
dims
> InOnly MEP should rethrow transport level exceptions
> -
not yet. CC'ing to axis-dev@, please follow up there.
Eran,
What's the new plan?
thanks,
dims
On 1/9/06, Nathaniel Auvil <[EMAIL PROTECTED]> wrote:
> the web site says there is a 0.94 release, but it is not on the download
> page.
>
--
Davanum Srinivas : http://wso2.com/blogs/
[ http://issues.apache.org/jira/browse/AXIS2-243?page=all ]
Davanum Srinivas resolved AXIS2-243:
Resolution: Fixed
fixed all the javadoc warnings.
> Missing javadoc, javadoc warnings, undocumented behavior
>
I’m still trying to get my first Axis2 build to
succeed. I’m
using Maven 1.1-beta-2. My first failure occurs when
Maven
can’t download bcprov-jdk13-128.jar and opensaml-1.0.1.jar.
After installing those manually in the repository and doing
a
clean, attempting to build results in
…
Are u on JDK1.5? can u please use 1.4.2?
thanks,
dims
On 1/9/06, Wayne Adams <[EMAIL PROTECTED]> wrote:
>
>
>
> I'm still trying to get my first Axis2 build to succeed. I'm
>
> using Maven 1.1-beta-2. My first failure occurs when Maven
>
> can't download bcprov-jdk13-128.jar and opensaml-1.0.1.
[
http://issues.apache.org/jira/browse/AXIS2-345?page=comments#action_12362276 ]
Sanjiva Weerawarana commented on AXIS2-345:
---
I didn't know that our tool supported one way operations yet! I guess we do -
and in that case indeed this should be an i
[ http://issues.apache.org/jira/browse/AXIS2-367?page=all ]
Ajith Harshana Ranabahu resolved AXIS2-367:
---
Resolution: Fixed
The ADB codegen has been modified to handle this case. If the user never sets a
particular value in the bean, he'll
[ http://issues.apache.org/jira/browse/AXIS2-366?page=all ]
Ajith Harshana Ranabahu resolved AXIS2-366:
---
Resolution: Fixed
The codegen has been modified to handle this case (for ADB)
> ADB schema compiler ignores the elementFormDefault="q
[ http://issues.apache.org/jira/browse/AXIS2-260?page=all ]
Ajith Harshana Ranabahu resolved AXIS2-260:
---
Resolution: Fixed
Assign To: Ajith Harshana Ranabahu
Added code (to the template) to only add the header parameters only if they
Fixing the interop tests in itest
-
Key: AXIS2-370
URL: http://issues.apache.org/jira/browse/AXIS2-370
Project: Apache Axis 2.0 (Axis2)
Type: Improvement
Components: Integration
Environment: WinXP, JDK 1.4
Reporter: Thilini Gu
Hi,
Dims has a point, in the sense that WOM represents both the WSDL
versions and a serialization of one version may not be a complete
representation of the other. However I feel that it'll be an over
engineering as far as WOM is considered. I mean if you want to
serialize it go do it as either a W
Hi all,
It seems we are drifting away from the release every day. I would at
this point say we should go ahead with the release. I've managed to fix
a number of blockers (except fault handling - issue 360, and null
handling - issue 321 which seem to be significant work and we are
better off calli
Ajith,
it's not just serializationI think of it as one central
representation of an axis service. whether it is on disk or in memory.
Annotations in code will affect it, entries in services.xml may affect
it, runtime reflection may affect it. But at any given point after
taking into account th
Perfect :)
This gives the necessary flexibilty for the module to act properly when engaged.
+1 from meOn 1/10/06, Davanum Srinivas <[EMAIL PROTECTED]> wrote:
+1 from me.-- Ajith Ranabahu
+1 from me.
On 1/9/06, Ajith Ranabahu <[EMAIL PROTECTED]> wrote:
> Hi all,
> It seems we are drifting away from the release every day. I would at this
> point say we should go ahead with the release. I've managed to fix a number
> of blockers (except fault handling - issue 360, and null handling
On Tue, 2006-01-10 at 10:17 +0600, Ajith Ranabahu wrote:
> Hi all,
> It seems we are drifting away from the release every day. I would at
> this point say we should go ahead with the release. I've managed to
> fix a number of blockers (except fault handling - issue 360, and null
> handling - issu
[ http://issues.apache.org/jira/browse/AXIS2-283?page=all ]
Ajith Harshana Ranabahu resolved AXIS2-283:
---
Resolution: Fixed
The latest changes to the code base allows this to be processed. Now it's added
to the test case again
> The Sales
Hi dims ;
As Snajiva mentioned when we code gen we have the wsdl , so lets copy that
to META-INF directory , so in that case we give higher priority to that
WSDL. And I also agree that duplicating information here and there make
people confusing. So its up to service author to take the decis
Excellent. Thanks a lot Dims !!!
Davanum Srinivas (JIRA) wrote:
[ http://issues.apache.org/jira/browse/AXIS2-243?page=all ]
Davanum Srinivas resolved AXIS2-243:
Resolution: Fixed
fixed all the javadoc warnings.
Missing javadoc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thilina,
Let me add some points for this.
If you go to the JIRA and see, it says we have to host Axis2 some
where else (in Zones, may be) and test those. So I just wanted to wait
till that is finished. But at the sametime, we did a successful
Hi Nathaniel, Dims and all,
We have started the "process" of releasing Axis2 0.94. So we are
updating the web site and the docs in parallel to other releasing
things. So the web site now is in a transition stage. I thought the
chron job was not working and web site will not automatically gets
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hmm,
I'm using JDK 1.5 without a problem. BUT, I had to include the
following line in "/jdk1.5.0_06/jre/lib/security/java.security" file
*security.provider.6=com.sun.security.sasl.Provider. **
*I think I should include this in FAQ.
- -- Chin
AxisServiceBuilder should be using WOM not WSDL4J
--
Key: AXIS2-371
URL: http://issues.apache.org/jira/browse/AXIS2-371
Project: Apache Axis 2.0 (Axis2)
Type: Bug
Reporter: Davanum Srinivas
Can we please standard
Deepal,
If people have multiple wsdl's with concrete/abstract wsdls and
imports between them, then we will run into problems. no?
-- dims
On 1/9/06, Deepal Jayasinghe <[EMAIL PROTECTED]> wrote:
> Hi dims ;
>
> As Snajiva mentioned when we code gen we have the wsdl , so lets copy that
> to META-
Are u sure that's the right entry? i see that in the default install already :(
thanks
-- dims
On 1/9/06, Eran Chinthaka <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> hmm,
>
> I'm using JDK 1.5 without a problem. BUT, I had to include the
> following line i
[ http://issues.apache.org/jira/browse/AXIS2-269?page=all ]
Ajith Harshana Ranabahu resolved AXIS2-269:
---
Resolution: Fixed
Since this is a broad issue (We have no clear mechanism to select the correct
Operation Description in a custome ME
Client API support Attachments (like Axis 1.X)
--
Key: AXIS2-372
URL: http://issues.apache.org/jira/browse/AXIS2-372
Project: Apache Axis 2.0 (Axis2)
Type: Bug
Reporter: Davanum Srinivas
Use case: want to write an in
[ http://issues.apache.org/jira/browse/AXIS2-369?page=all ]
Afkham Azeez updated AXIS2-369:
---
Attachment: axis2.patch
Reuploading patch with license granted to ASF
> New AXIS2 Packaging Structure
> -
>
> Key: AXIS2-369
[ http://issues.apache.org/jira/browse/AXIS2-369?page=all ]
Afkham Azeez updated AXIS2-369:
---
Attachment: (was: axis2.patch)
> New AXIS2 Packaging Structure
> -
>
> Key: AXIS2-369
> URL: http://issues.apache
[ http://issues.apache.org/jira/browse/AXIS2-369?page=all ]
Afkham Azeez updated AXIS2-369:
---
Attachment: axis2.patch
Reattaching patch with license granted to ASF
> New AXIS2 Packaging Structure
> -
>
> Key: AXIS2-369
[ http://issues.apache.org/jira/browse/AXIS2-369?page=all ]
Afkham Azeez updated AXIS2-369:
---
Attachment: (was: axis2.patch)
> New AXIS2 Packaging Structure
> -
>
> Key: AXIS2-369
> URL: http://issues.apache
[
http://issues.apache.org/jira/browse/AXIS2-360?page=comments#action_12362287 ]
Ajith Harshana Ranabahu commented on AXIS2-360:
---
I believe the current code base has enough flexibility to handle this. I
already have some slots (marked with com
On Mon, 2006-01-09 at 23:54 -0500, Davanum Srinivas wrote:
> Deepal,
>
> If people have multiple wsdl's with concrete/abstract wsdls and
> imports between them, then we will run into problems. no?
I have to think about this a bit more but I think that we can flatten
the schema/message/portType pa
Ruchith,
Can you please comment on this and please add this to FAQ. (You are the
one who helped me to configure it.
:-) )
Davanum Srinivas wrote:
>Are u sure that's the right entry?
i see that in the default install already :(
>
>thanks
>-- dims
>
>On 1/9/06, Eran Chinthaka <[EMAIL PROTECTE
[
http://issues.apache.org/jira/browse/AXIS2-371?page=comments#action_12362288 ]
Sanjiva Weerawarana commented on AXIS2-371:
---
We discussed this at the hackathon and the consensus was that we need to plan
to migrate to Woden when they're ready. Tha
Hi All,
The entry should be
security.provider.7=org.bouncycastle.jce.provider.BouncyCastleProvider
This will add BouncyCastle as another JCE provider.
Will update the FAQ.
Thanks,
Ruchith
On 1/10/06, Eran Chinthaka <[EMAIL PROTECTED]> wrote:
> Ruchith,
>
> Can you please comment on this and
[ http://issues.apache.org/jira/browse/AXIS2-370?page=all ]
Thilini Gunawardhana updated AXIS2-370:
---
Attachment: patch.jar
Fixed following tests in whitemesa/round2. Please apply the patch.
* MStk3Round2InteropTest.java
* S
and drop the jar where? :)
On 1/10/06, Ruchith Fernando <[EMAIL PROTECTED]> wrote:
> Hi All,
>
> The entry should be
>
> security.provider.7=org.bouncycastle.jce.provider.BouncyCastleProvider
>
> This will add BouncyCastle as another JCE provider.
>
> Will update the FAQ.
>
> Thanks,
> Ruchith
>
>
[
http://issues.apache.org/jira/browse/AXIS2-371?page=comments#action_12362290 ]
Davanum Srinivas commented on AXIS2-371:
should we keep this open or close it? I just noticed another file
ClientUtils.java has the same problem.
thanks,
dims
> Axis
[
http://issues.apache.org/jira/browse/AXIS2-371?page=comments#action_12362291 ]
Deepal Jayasinghe commented on AXIS2-371:
-
Well , I think when we generating AxisService using given WSDL , if we create
WOM and using that if we create AxisService , w
UDP transport for Axis2
---
Key: AXIS2-373
URL: http://issues.apache.org/jira/browse/AXIS2-373
Project: Apache Axis 2.0 (Axis2)
Type: New Feature
Components: transports
Reporter: Deepal Jayasinghe
Assigned to: Deepal Jayasinghe
I think
[ http://issues.apache.org/jira/browse/AXIS2-112?page=all ]
Ajith Harshana Ranabahu resolved AXIS2-112:
---
Resolution: Fixed
This is solved after the improvements to the codegenerator. The particualr WSDL
has been verified to generate work
[ http://issues.apache.org/jira/browse/AXIS2-370?page=all ]
Thilini Gunawardhana updated AXIS2-370:
---
Attachment: patch1.jar
IMO following issues were found regarding some test cases in whitemase/round2.
I have attached complete stack traces and re
Option in ADB codegen to generate separate _Helper files like Axis 1.X
--
Key: AXIS2-374
URL: http://issues.apache.org/jira/browse/AXIS2-374
Project: Apache Axis 2.0 (Axis2)
Type: Bug
Reporter: D
[
http://issues.apache.org/jira/browse/AXIS2-371?page=comments#action_12362294 ]
Sanka Samaranayake commented on AXIS2-371:
--
In AxisServiceBuilder we had two options on how to process the given WSDL
document. Using wsdl4j IMO gave a cleaner API to
[
http://issues.apache.org/jira/browse/AXIS2-222?page=comments#action_12362295 ]
Ajith Harshana Ranabahu commented on AXIS2-222:
---
I'm inclined to think that this is a problem with the whitemesa server!
> Round3 DoclitParam interop test failed
[ http://issues.apache.org/jira/browse/AXIS2-225?page=all ]
Ajith Harshana Ranabahu resolved AXIS2-225:
---
Resolution: Fixed
This has been tested enough to be marked resolved
> Invoking muliple services pertaining to multiple wsdls
> --
[ http://issues.apache.org/jira/browse/AXIS2-229?page=all ]
Ajith Harshana Ranabahu resolved AXIS2-229:
---
Resolution: Fixed
Now the databinders are implemented internally which means the databinding
methods are not visible at all.
> When
[ http://issues.apache.org/jira/browse/AXIS2-244?page=all ]
Ajith Harshana Ranabahu resolved AXIS2-244:
---
Resolution: Fixed
This is a symptom of the WSDL imports not being handled properly. Now it's fixed
> porttypes are not imported via
[
http://issues.apache.org/jira/browse/AXIS2-250?page=comments#action_12362299 ]
Ajith Harshana Ranabahu commented on AXIS2-250:
---
My guess is this is a post .94 feature (Definitley pre 1.0 though)
> Extracting WS-Addressing properties (E.g. Ac
[
http://issues.apache.org/jira/browse/AXIS2-262?page=comments#action_12362300 ]
Ajith Harshana Ranabahu commented on AXIS2-262:
---
This is really an issue for the XMLbeans Jira ??
> provider wrapper for xsd:any
>
>
[
http://issues.apache.org/jira/browse/AXIS2-262?page=comments#action_12362301 ]
Davanum Srinivas commented on AXIS2-262:
we could add one there and link it to this one.
-- dims
> provider wrapper for xsd:any
>
>
>
[
http://issues.apache.org/jira/browse/AXIS2-266?page=comments#action_12362302 ]
Ajith Harshana Ranabahu commented on AXIS2-266:
---
More like another XMLBeans issue ?
> can't serialize a request that contains a derived type
> ---
[
http://issues.apache.org/jira/browse/AXIS2-275?page=comments#action_12362303 ]
Ajith Harshana Ranabahu commented on AXIS2-275:
---
This seems to be a post .94 issue. However the issue is that since we support
different frameworks it may not be
[
http://issues.apache.org/jira/browse/AXIS2-266?page=comments#action_12362304 ]
Davanum Srinivas commented on AXIS2-266:
i just tried to run codegen and got this error.
Exception in thread "main"
org.apache.axis2.wsdl.codegen.CodeGenerationExcepti
[
http://issues.apache.org/jira/browse/AXIS2-287?page=comments#action_12362305 ]
Ajith Harshana Ranabahu commented on AXIS2-287:
---
XMLbeans problem ?
> Facet minInclusive causes RunTimeException
> --
>
>
Hi All,
The jar should be automatically downloaded by maven.
By the way the original problem mentioned : "[junit] - Invalid service
PingPort.aar due to Two services can not have same name, a service
with PingPort already exists in the system" seems to be a problem with
the way the org.apache.ax
>>we have to host Axis2 some where else (in Zones, may be) and test those. So I just wanted to>> wait till that is finished. But at the sametime, we did a successful interop with Indigo.Oooops...Sorry for the false call... Completely forgot that hosting part..
Seems like I have something interesti
98 matches
Mail list logo
