On Tue, 2006-07-11 at 08:19 +0200, Carsten Ziegeler wrote:
> > So in effect the properties hashtable inherited from the superclass is
> > not used by the MessageContext class.
> >
> Yes, except in the getProperties() method. If you do a setProperty("A",
> "B") on the message context and then do a
Sanjiva Weerawarana wrote:
> On Tue, 2006-07-11 at 08:19 +0200, Carsten Ziegeler wrote:
>>> So in effect the properties hashtable inherited from the superclass is
>>> not used by the MessageContext class.
>>>
>> Yes, except in the getProperties() method. If you do a setProperty("A",
>> "B") on the
[ http://issues.apache.org/jira/browse/AXIS2-865?page=all ]
Deepal Jayasinghe resolved AXIS2-865:
-
Resolution: Fixed
fixed in current SVN
> RPCMessageReceiver response NOT qualified well
> --
>
>
[
http://issues.apache.org/jira/browse/AXIS2-865?page=comments#action_12420269 ]
Kinichiro Inoguchi commented on AXIS2-865:
--
I checked latest nightly build war,
But still problem remains.
An element "return" was qualified.
But elements in were NO
Hello,
The compile problem that I was having
was due to my build environment. When I trashed my environment and recreated
it the compile problem went away.
Cheers
Brian DePradine
Web Services Development
IBM Hursley
External +44 (0) 1962 816319 Internal
246319
If you can't find the ti
[
http://issues.apache.org/jira/browse/AXIS2-828?page=comments#action_12420279 ]
Tomas Ruff commented on AXIS2-828:
--
I had AXIS2-668 bug with AntCodegenTask.
Started using nightly build but stuck on this issue.
Currently AntCodegenTask is unusable in all
[ http://issues.apache.org/jira/browse/AXIS2-881?page=all ]
Rich Scheuerle updated AXIS2-881:
-
Assign To: Rich Scheuerle
Thanks Nick,
Nick has almost completed this initial work. I will be committing the changes
soon.
> JAXWS: Refactoring invocation
[ http://issues.apache.org/jira/browse/AXIS2-882?page=all ]
Rich Scheuerle reassigned AXIS2-882:
Assign To: Rich Scheuerle
> JAX-WS: Endpoint Controller framework
> -
>
> Key: AXIS2-882
> URL: htt
Enhance support for the WS-Addressing anonymous and none URIs
-
Key: AXIS2-885
URL: http://issues.apache.org/jira/browse/AXIS2-885
Project: Apache Axis 2.0 (Axis2)
Type: Improvement
Components: core
[ http://issues.apache.org/jira/browse/AXIS2-885?page=all ]
Brian DePradine updated AXIS2-885:
--
Attachment: patch.txt
This patch:
1) Ensures that appropriate defaults are set for any WS-Addressing headers that
are missing.
2) The correct semantics ar
[
http://issues.apache.org/jira/browse/AXIS2-878?page=comments#action_12420301 ]
Rich Scheuerle commented on AXIS2-878:
--
Rajith,
Thanks for the heads up. We don't want to duplicate work. The intention of
the JAX-WS metadata layer is to provide an a
Hi
I am having the itest jar problem with building Axis2, which I have just
checked out from SVN.
I tried to get the itest jar as described in the FAQ, but:
[echo] 1.4
build:start:
plugin:download-artifact:
[echo] repo is 'http://www.openejb.org/maven'
[echo] trying to download
Hi,
I'm looking for examples of using JMS with Axis2. Does anyone have some ?
Thanks
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Sorry for the late reply.Thanks Jeff and Rich for the update.I will sync up with Jeff to figure out how things tie in to the work described in AXIS2-883.Looking forward to work with you guys.Regards,
RajithOn 7/11/06, Rich Scheuerle (JIRA) <[EMAIL PROTECTED]> wrote:
[ http://issues.apache.org/j
Hi Nathan,
I also noticed that the ibiblio repos do not contain the itest plugin
anymore.
Try the following.
maven plugin:download -DgroupId=maven-itest-plugin
-DartifactId=maven-itest-plugin -Dversion=1.0
-Dmaven.repo.remote=http://people.apache.org/repository/maven
-- Chinthaka
Nathan Sowats
Rajith Attapattu wrote:
Hi Dims,
I finnaly managed to get an annotated POJO exposed as an axis2 web
service.
Before I submit the patch I need to clarify a few things.
1. We need to figure out a way to find the classes marked with
@WebService.
Right now I just have my test POJO hard corde
Hi Guillaume,if the service deployed as an ".aar" then we know which classes to introspect or use ASM.If there is a service.xml then we can easily figure out what the class is.The above approach will make life easier.
But I think the expectation is that service.xml is optional.Also there maybe an e
Rajith--
I'm not super familiar with the Axis2 architecture, but in the
absence of both a .aar file and service.xml, is there some default
binding between a URL and a Java class? If so, the metadata could be
checked and processed at runtime to dynamically wire-up a service
based on the shape of
Hi
Many thanks for the pointer! This invocation worked for me:
maven plugin:download -DgroupId=maven -DartifactId=maven-itest-plugin
-Dversion=1.0 -Dmaven.repo.remote=http://people.apache.org/repository
Regards
Nathan
Eran Chinthaka wrote:
Hi Nathan,
I also noticed that the ibiblio repos
Almost, I also had to rename the "maven" directory thus created in my
repository to "maven-itest-plugin" after deleting the empty one created
earlier.
Regards
Nathan
Nathan Sowatskey wrote:
Hi
Many thanks for the pointer! This invocation worked for me:
maven plugin:download -DgroupId=maven
New JMS sender should take account of WS-Addressing destination even on the
server
--
Key: AXIS2-886
URL: http://issues.apache.org/jira/browse/AXIS2-886
Project: Apache Axis 2.0 (Axis2)
[ http://issues.apache.org/jira/browse/AXIS2-886?page=all ]
Brian DePradine updated AXIS2-886:
--
Attachment: patch.txt
Added my patch.
> New JMS sender should take account of WS-Addressing destination even on the
> server
>
Hi
I have:
The build cannot continue because of the following unsatisfied dependency:
stax-utils-20060501.jar
Total time: 11 minutes 7 seconds
Finished at: Tue Jul 11 16:42:33 CEST 2006
Any ideas anyone please?
Many thanks
Nathan
--
Nathan Sowatskey - Technical Leader, NMTG CTO Engineering
Hi folks!
This is an automatic reminder that the weekly Axis2 developer chat
will be occurring tomorrow, July 12, at:
5AM SF, 8AM Boston, 1PM London, 5:30PM Colombo, 10PM Melbourne
The chat takes place on the freenode IRC network, (use server
irc.freenode.net), on channel #apache-axis, and is sc
[ http://issues.apache.org/jira/browse/AXIS2-886?page=all ]
Davanum Srinivas resolved AXIS2-886:
Resolution: Fixed
Applied.
thanks,
dims
> New JMS sender should take account of WS-Addressing destination even on the
> server
>
I am planning to use AXIS2 within
J2EE Security environment. Does AXIS2 currently support J2EE security (with
Security Manager enabled)? If yes, Could anyone please provide me some
detail information of how to make/enable AXIS2 to work within J2EE Security
environment?
One of examples of using J2
Nathan Sowatskey wrote:
> Hi
>
> I have:
>
> The build cannot continue because of the following unsatisfied dependency:
>
> stax-utils-20060501.jar
>
> Total time: 11 minutes 7 seconds
> Finished at: Tue Jul 11 16:42:33 CEST 2006
>
> Any ideas anyone please?
Get it from here http://ws.zones.a
Nathan,
I'm going though this process too :-0 To pre-empt your next roadblock, you
may now find you have
bcprov-jdk13-132.jar
missing also.
If so this can be found at
http://ws.zones.apache.org/~dims/maven/bouncycastle/jars/ and should be
copied into .maven/repository/bouncycastle/jars
Kind Re
Old JMS sender needs to take account of WS-Addressing none URI.
---
Key: AXIS2-887
URL: http://issues.apache.org/jira/browse/AXIS2-887
Project: Apache Axis 2.0 (Axis2)
Type: Improvement
Components: transp
[ http://issues.apache.org/jira/browse/AXIS2-887?page=all ]
Brian DePradine updated AXIS2-887:
--
Attachment: patch.txt
Here it is ...
> Old JMS sender needs to take account of WS-Addressing none URI.
> ---
Graham Turrell wrote:
> Nathan,
>
> I'm going though this process too :-0 To pre-empt your next roadblock, you
> may now find you have
>
> bcprov-jdk13-132.jar
>
> missing also.
>
> If so this can be found at
> http://ws.zones.apache.org/~dims/maven/bouncycastle/jars/ and should be
> copied int
Hi folks,
As I mentioned in one of my notes a while ago, we have an issue with
some APIs (e.g. security, Tx) requiring that data be present on Thread
Local Storage (TLS). I believe that we can work around (at least for
now) needing to migrate information between threads, and can simply get
away w
[ http://issues.apache.org/jira/browse/AXIS2-876?page=all ]
Rich Scheuerle updated AXIS2-876:
-
Attachment: jirapatch.txt
Combined patch for the following JIRA Issues:
AXIS2-873: Nikhil - JAXB Wrapper SubComponent
AXIS2-874: Mike - Handler SubComponent I
[ http://issues.apache.org/jira/browse/AXIS2-876?page=all ]
Rich Scheuerle resolved AXIS2-876:
--
Resolution: Fixed
> JAXWS: Message Subsystem
>
>
> Key: AXIS2-876
> URL: http://issues.apache.org/jira/browse
[ http://issues.apache.org/jira/browse/AXIS2-872?page=all ]
Rich Scheuerle resolved AXIS2-872:
--
Resolution: Fixed
(Visible to axis2-developers)
> JAXWS: MetaDataQuery (MDQ) - Tool for merging and checking annotation
> information with other depl
[ http://issues.apache.org/jira/browse/AXIS2-875?page=all ]
Rich Scheuerle resolved AXIS2-875:
--
Resolution: Fixed
(Visible to axis2-developers)
> JAXWS: Proxy Implementation for JAXWS
> -
>
> Key: AXIS
[ http://issues.apache.org/jira/browse/AXIS2-873?page=all ]
Rich Scheuerle resolved AXIS2-873:
--
Resolution: Fixed
(Visible to axis2-developers)
> JAXWS: Wrap and unWrap JAXB Objects using JAXBWrapperTool
>
[ http://issues.apache.org/jira/browse/AXIS2-878?page=all ]
Rich Scheuerle resolved AXIS2-878:
--
Resolution: Fixed
(Visible to axis2-developers)
> JAXWS: Metadata Abstraction Layer
> -
>
> Key: AXIS2-878
>
[ http://issues.apache.org/jira/browse/AXIS2-874?page=all ]
Rich Scheuerle resolved AXIS2-874:
--
Resolution: Fixed
See AXIS2-876
I just committed Mike's changes. Mike will be working on the next set of
handler functionality (including the excepti
[ http://issues.apache.org/jira/browse/AXIS2-882?page=all ]
Rich Scheuerle resolved AXIS2-882:
--
Resolution: Fixed
(Visible to axis2-developers)
> JAX-WS: Endpoint Controller framework
> -
>
> Key: AXIS
[ http://issues.apache.org/jira/browse/AXIS2-881?page=all ]
Rich Scheuerle resolved AXIS2-881:
--
Resolution: Fixed
(Visible to axis2-developers)
> JAXWS: Refactoring invocation APIs
> --
>
> Key: AXIS2-881
[ http://issues.apache.org/jira/browse/AXIS2-887?page=all ]
Davanum Srinivas resolved AXIS2-887:
Resolution: Fixed
applied.
-- dims
> Old JMS sender needs to take account of WS-Addressing none URI.
> ---
Dims,
Would it be possible to update the JAX-B
RI version in the repository to the final release available from Sun (https://jaxb.dev.java.net/jaxb20-fcs/).?
Some of the APIs and annotations have
changed slightly since the EA3 version and we'd like to be on the latest
version before creating t
Nicholas,
the api jar in that dist does not have javax.xml.bind.annotation.AccessType...
-- dims
[javac] Compiling 48 source files to
C:\APACHE\axis2\modules\jaxws\target\test-classes
[javac] C:\APACHE\axis2\modules\jaxws\test\client\EchoString.java:11:
cannot find symbol
[javac] symbo
Dims,
Yep, that's one of the problems. That
particular annotation has changed to XmlAccessType in the latest jar.
We'd regenerated the JAX-B classes using
the EA3 jar to get the code to work, but I guess we'll have to re-gen them
with the latest and check that in at the same time. Should I ope
Nicholas,
It'd be better if we don't check-in generated code. Would it be
possible for you to try generating the code using a preGoal in
maven.xml?
If that does not work, then please gen the new sources and post a diff
to jira and i'll pick it up.
thanks,
dims
On 7/11/06, Nicholas L Gallardo <
Hi;
Engaging module at client side can be done in two ways;
- Create ConfigurationContext using a repository where that repository
has addressing module
- And then create ServiceClient using that configuration context
- The second way is to drop the addressing.mar into class path and
then c
Any possibility of seeing the service implementation class.
Davanum Srinivas wrote:
> fwd to list
>
> -- Forwarded message --
> From: 邱家榆 <[EMAIL PROTECTED]>
> Date: Jul 10, 2006 3:09 AM
> Subject: A Axis2 problem!~
> To: davanum <[EMAIL PROTECTED]>
>
>
>
>
> There is a Axis2 1.0
Hi Carsten;
I went through your patch and realized that , you are giving read only
access to the properties . So if someone want to change the value of
property (properties) then he wont be able to do that. I think we need
to provide way to change them as well .
Carsten Ziegeler wrote:
>Sanjiv
stub._getServiceClient().getOption().setUseSeparateListener(true);
Jean-Michel PATER wrote:
> Hi,
>
> How can I specify that I want to use two separate transports
> connection when I use a stub generated from a WSDL.
>
> A+
>
--
Thanks,
Deepal
...
Dims,
That sounds reasonable to me.
Thanks,
Nicholas Gallardo
WebSphere - WebServices Development
[EMAIL PROTECTED]
Phone: 512-838-1182
Building: 901 / 5G-016
"Davanum Srinivas"
<[EMAIL PROTECTED]>
07/11/2006 10:05 PM
Please respond to
axis-dev@ws.apache.org
To
axis-dev@ws.apach
[
http://issues.apache.org/jira/browse/AXIS2-864?page=comments#action_12420506 ]
Deepal Jayasinghe commented on AXIS2-864:
-
hmm , according to getEPRForService method in SimpleHTTPServer you will never
get null , it should either 127.0.0.1 or real I
[ http://issues.apache.org/jira/browse/AXIS2-879?page=all ]
Deepal Jayasinghe resolved AXIS2-879:
-
Resolution: Fixed
Fixed in current SVN
> invalid generated WSDL for method returns array
> ---
>
>
[ http://issues.apache.org/jira/browse/AXIS2-880?page=all ]
Deepal Jayasinghe resolved AXIS2-880:
-
Resolution: Fixed
Fixed current SVN
> service method that returns array got Exception
> ---
>
>
[
http://issues.apache.org/jira/browse/AXIS2-871?page=comments#action_12420512 ]
Deepal Jayasinghe commented on AXIS2-871:
-
can you please attached the wsdl file ?
> Service created with WSDL2Code from a wsdl2 description fails to deploy in
> axis2
[ http://issues.apache.org/jira/browse/AXIS2-709?page=all ]
Deepal Jayasinghe resolved AXIS2-709:
-
Resolution: Fixed
Fixed in current SVN
> IOException when when a module with its own jars in the 'lib' dir is deployed
>
[ http://issues.apache.org/jira/browse/AXIS2-725?page=all ]
Deepal Jayasinghe resolved AXIS2-725:
-
Resolution: Fixed
marking as fixed
> "Address already in use: JVM_Bind" exception while creating second
> SimpleHTTPServer instance
> --
When trying to invoke a RPC based service, Axis throws an exception when trying to serialize a response of hierarchic bean structure to response SOAP request. I have attached the service jar deployed on JBoss 4.0.4 and I have tested the simple response sayHello but when it comes to complex st
Hi Pradeepta;
Since you have the wsdl why dont you code generate rather than using
RPCMessage receiver , I think that is the best way.
Any way can you pls send me the service impl class as well (if possible)
Pradeepta Bhattacharya wrote:
>When trying to invoke a RPC based service, Axis throws an
Reviewing the code...i realized that the code was generated using w2j
of JAXWS RI (NOT just JAXB's xjc). So i fixed the name change of the
class AccessType to XmlAccessType and checked it in.
thanks,
dims
PS: tests fails under JDK1.6 Beta2 as it has an internal impl of
jaxb2/jaxws. JDK1.5 worked
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Devs,
AxisEngine#receiver() always check for must understand header before
invoking the relevant message receiver. This would really give a hard
time in Synapse when we tried to implement qos support such as RM ect.
Synapse has its own SynapseMes
Deepal Jayasinghe wrote:
> Hi Carsten;
>
> I went through your patch and realized that , you are giving read only
> access to the properties . So if someone want to change the value of
> property (properties) then he wont be able to do that. I think we need
> to provide way to change them as well
62 matches
Mail list logo
