Mark, Asankha,
I believe that developerworks does provide a free 90 day trial version
of WebSphere MQ [1]. Does that satisfy your needs?
Cheers,
David
[1] http://www.ibm.com/developerworks/downloads/ws/wmq/?S_TACT=105AGX10&S_CMP=LP
On 18/06/07, Mark Badorrek <[EMAIL PROTECTED]> wrote:
Hi asank
Hi David, Mark
I think for right now this would work fine - if Mark can validate that
the fixes does work as expected, and not break anything else. However in
the longer run, and to ensure that we could support MQ as well as
ActiveMQ and any other JMS implementation the best we can, it would m
Faulty handling of JMS asynchronous calls
-
Key: AXIS2-2819
URL: https://issues.apache.org/jira/browse/AXIS2-2819
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: Addressing
Affects
Hi Asankha, David,
If you can get the fix into the nightly build I'll give it a run and confirm
that everything is OK.
Additionally, I'll see if I can get local IBM sales to donate a WebsphereMQ
copy.
If that work's out I'll outline what sort of work is required to perform a test.
You can relax
Hi Devs,
If a WSDL is not given for a service, and if the service's message receiver
is not RPCMessageReceiver what would be the WSDL generation behavior.
I'm using the current Axis2 trunk head, and I've using services with custom
MR, and when I try to do ?wsdl I'm receiving the following excep
Jira-2626 is not about the *extension*... It is about "*HotUpdate*
failing on custom deployers".. Also on a side note, it would have
been really great if you sent a mail about this change, as this broke
the downstream projects which are using custom deployers..
You have also removed the worka
[
https://issues.apache.org/jira/browse/AXIS2-2626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thilina Gunarathne reopened AXIS2-2626:
---
What's fixed in the revision 547760 does not fix Jira-2626 ... Rather it breaks
the thin
[
https://issues.apache.org/jira/browse/AXIS2-2626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12506159
]
Thilina Gunarathne commented on AXIS2-2626:
---
Once again I added the above mentioned work around... Please m
Agreed. Can you please log a JIRA? and upload some sample that we can
turn into a test case.
thanks,
dims
On 6/19/07, Saminda Abeyruwan <[EMAIL PROTECTED]> wrote:
Hi Devs,
If a WSDL is not given for a service, and if the service's message receiver
is not RPCMessageReceiver what would be the W
[
https://issues.apache.org/jira/browse/AXIS2-2626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thilina Gunarathne updated AXIS2-2626:
--
Priority: Critical (was: Blocker)
reducing priority as we have a workaround...
> Hot
[
https://issues.apache.org/jira/browse/AXIS2-2819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davanum Srinivas updated AXIS2-2819:
Assignee: Asankha C. Perera
> Faulty handling of JMS asynchronous calls
> -
[
https://issues.apache.org/jira/browse/AXIS2-2817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davanum Srinivas updated AXIS2-2817:
Assignee: Nick Gallardo
> Create AttachmentDescription objects in the JAX-WS Metadata layer
[
https://issues.apache.org/jira/browse/AXIS2-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davanum Srinivas updated AXIS2-2816:
Assignee: Asankha C. Perera
> JMS over WebsphereMQ doesn't support 'CLIENT' connections
> -
[
https://issues.apache.org/jira/browse/AXIS2-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davanum Srinivas updated AXIS2-2814:
Assignee: Amila Chinthaka Suriarachchi
> XSI:TYPE not being generated for SOAP JMS client r
SimpleHTTP server can not handle multiple threads (more than 20)
Key: AXIS2-2820
URL: https://issues.apache.org/jira/browse/AXIS2-2820
Project: Axis 2.0 (Axis2)
Issue Type: Bug
[
https://issues.apache.org/jira/browse/AXIS2-2548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12506179
]
Nick Gallardo commented on AXIS2-2548:
--
Glen,
This problem surfaced because of some of the conversions that we
Jerome,
You are right!
Team,
I am reviewing the code and running the tests, i can see that
org.apache.axis2.deployment.scheduler.Scheduler needs to cancel a
timer. So this means that we have to add cleanup methods in various
layers. Here's a diff that i got working with help from Glen and
Deepal.
oops! forgot the diff.
-- dims
On 6/19/07, Davanum Srinivas <[EMAIL PROTECTED]> wrote:
Jerome,
You are right!
Team,
I am reviewing the code and running the tests, i can see that
org.apache.axis2.deployment.scheduler.Scheduler needs to cancel a
timer. So this means that we have to add cleanup m
Online report :
http://ws.zones.apache.org:1/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/1/buildId/2401
Build statistics:
State: Failed
Previous State: Ok
Started at: Tue, 19 Jun 2007 15:07:14 +
Finished at: Tue, 19 Jun 2007 15:57:14 +
Total time:
Hi guys,
My build is failing in the kernel.
Any clues
Thanks
Chathura
Testsuite: org.apache.axis2.deployment.AxisMessageTest
Tests run: 1, Failures: 1, Errors: 0, Time elapsed: 0.719 sec
- Standard Error -
Jun 19, 2007 11:53:46 AM org.apache.axis2.deployment.ModuleDe
when localname is null try set it to the tagname/nodename in the toSAAJNode
method
--
Key: AXIS2-2821
URL: https://issues.apache.org/jira/browse/AXIS2-2821
Project: Axis
[
https://issues.apache.org/jira/browse/AXIS2-2821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lin Sun updated AXIS2-2821:
---
Attachment: AXIS2-2821.patch
Tested in geronimo env.
> when localname is null try set it to the tagname/node
[
https://issues.apache.org/jira/browse/AXIS2-2702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12506249
]
Peter Danielsen commented on AXIS2-2702:
Amila,
Running the committed version on http-faults.wsdl produces a
[
https://issues.apache.org/jira/browse/AXIS2-2821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
sumedha rubasinghe reassigned AXIS2-2821:
-
Assignee: sumedha rubasinghe
> when localname is null try set it to the tagname/n
[
https://issues.apache.org/jira/browse/AXIS2-2821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
sumedha rubasinghe resolved AXIS2-2821.
---
Resolution: Fixed
Applied the patch to revision 548806.
Thanks.
sumedha
> when loca
Really? You want to default to SOAP 1.2? Really?
Did you actually flip this switch? I thought you were going to work on
stabilizing Axis2 for the 1.3 release. This is going to rock the boat
in a serious way.
Tom Jordahl
-Original Message-
From: Sanjiva Weerawarana [mailto:[EMAIL PROT
Defaulting to SOAP 1.2 will have more negative effects than positive, in my
opinion -:) have in mind that SOAP 1.2 interop with other WS frameworks is
very volatile at the moment (i.e. DotNET, and JAX-WS, more specifically -
the wsimport tool) - that's what our experiences with soap 1.2 interop
t
Online report :
http://ws.zones.apache.org:1/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/1/buildId/2411
Build statistics:
State: Ok
Previous State: Failed
Started at: Tue, 19 Jun 2007 17:06:41 +
Finished at: Tue, 19 Jun 2007 17:51:59 +
Total time:
I have read the complete thread and I know I am chiming in a little
late.
One common exception type generated for each Schema element is clearly
the optimal mapping for Java.
If I declare method1 and method2 to throw the same exception in the
server side, I expect WSDL2Java (or whatever wrong nam
Angel,
"always using / converting to SOAP 1.1 no matter which soap version is
chosen by the client" <== is a Very serious bug!!!
please log a JIRA and any help to recreate the issue would be wonderful.
thanks,
dims
On 6/19/07, Angel Todorov <[EMAIL PROTECTED]> wrote:
Defaulting to SOAP 1.2 w
Hi Dims,
I already talked to Ruchith, the problem seems to be the DOM <-> LLOM
conversion. In fact its fixing may turn out to be very easy, but i haven't
taken a look yet. I will file a jira.
Regards,
Angel
On 6/19/07, Davanum Srinivas <[EMAIL PROTECTED]> wrote:
Angel,
"always using / conver
Also, JAX-WS requires a SOAP 1.1 default so there will be additional work
there that will need to be addressed.
I'm for keeping the SOAP 1.1 default for now. There still isn't a WS-I
profile that includes SOAP 1.2 either, is there? I thought that was coming
in BP 2.0.
Regards,
-Nick
[
https://issues.apache.org/jira/browse/AXIS2-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12506293
]
Amila Chinthaka Suriarachchi commented on AXIS2-2814:
-
I fixed an issue with the ADBXMLStreamRead
[
https://issues.apache.org/jira/browse/AXIS2-2714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Daniels resolved AXIS2-2714.
-
Resolution: Fixed
Fixed for now, any further changes will be improvements, so resolving this
iss
[
https://issues.apache.org/jira/browse/AXIS2-2626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe resolved AXIS2-2626.
--
Resolution: Fixed
Revision: 548855
http://svn.apache.org/viewvc?view=rev&rev=548855
>
[
https://issues.apache.org/jira/browse/AXIS2-1510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amila Chinthaka Suriarachchi resolved AXIS2-1510.
-
Resolution: Fixed
I tested the both wsdl files and they work with
[
https://issues.apache.org/jira/browse/AXIS2-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amila Chinthaka Suriarachchi resolved AXIS2-1461.
-
Resolution: Fixed
add a seperate costructor to set isUseSeperateL
Unable to implement methods generated with WSDL2Java:
org.apache.axis2.databinding.ADBException: Unexpected subelement
PromoteEmailToActivity
-
[
https://issues.apache.org/jira/browse/AXIS2-2822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henrik Mohr updated AXIS2-2822:
---
Description:
I'm not able to implement method in skeleton-class made from WSDL.
Step1:
type the foll
[
https://issues.apache.org/jira/browse/AXIS2-2822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henrik Mohr updated AXIS2-2822:
---
Description:
I'm not able to implement method in skeleton-class made from WSDL.
Step1:
type the foll
[
https://issues.apache.org/jira/browse/AXIS2-2812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12506328
]
Amila Chinthaka Suriarachchi commented on AXIS2-2812:
-
we can do this for adb but other can't. so
Online report :
http://ws.zones.apache.org:1/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/1/buildId/2420
Build statistics:
State: Failed
Previous State: Ok
Started at: Tue, 19 Jun 2007 23:06:38 +
Finished at: Tue, 19 Jun 2007 23:40:05 +
Total time:
[
https://issues.apache.org/jira/browse/AXIS2-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
balaji iyer updated AXIS2-2814:
---
In the nightly build "axis2-SNAPSHOT"
I get the following Exception "NoSuchMethodError". Below is its st
[
https://issues.apache.org/jira/browse/AXIS2-1701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12506366
]
Amila Chinthaka Suriarachchi commented on AXIS2-1701:
-
can you please attach your wsdl as well?
Hi Deepal:
There are quite a few missing or extra spaces in this commit.
When calling methods, it should look like this:
method(arg1, arg2, arg3) NOT method( arg1 , arg2,arg3)
Operators always have spaces around them, so
"this == correct" NOT "this==not"
If statements have a space after
It works now, Thanks for the help!
The problem was with this;
QName bodyName = new QName("http://ws.apache.org/axis2/xsd";,
"x", "m");
It works after coding exactly like that. I could not found any SAAJ example
on Axis. So I started from Sun J2EE tutorial, get confused
[
https://issues.apache.org/jira/browse/AXIS2-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amila Chinthaka Suriarachchi resolved AXIS2-2290.
-
Resolution: Fixed
fixed the issue to support simple types as well
[
https://issues.apache.org/jira/browse/AXIS2-2202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amila Chinthaka Suriarachchi resolved AXIS2-2202.
-
Resolution: Invalid
resolve the issue since it is an user setting
Hi Joe,
Good to hear that you got it working!!!
Are you referring to passing a String (which is an XML) to a method in POJO
& getting a return String (which is also a XML) ?
eg:
class MyService{
public String myMethod(String xml){
//do something
}
}
On 6/20/07, Joe Nathan <[EMAIL PROTE
Exactly! I tried on Axis POJO this, but it ended up with fatal error! I think
Axis does not do proper marshalling for special characters inside xml codes.
Joe,
sumedha rubasinghe-2 wrote:
>
> Hi Joe,
> Good to hear that you got it working!!!
> Are you referring to passing a String (which is a
Online report :
http://ws.zones.apache.org:1/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/1/buildId/2422
Build statistics:
State: Failed
Previous State: Failed
Started at: Wed, 20 Jun 2007 04:36:05 +
Finished at: Wed, 20 Jun 2007 05:25:42 +
Total ti
51 matches
Mail list logo
