[jira] Commented: (AXIS2-2604) Download links for the archived releases are incorrect

[Thilina Gunarathne (JIRA)]

[ 
https://issues.apache.org/jira/browse/AXIS2-2604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493853
 ] 

Thilina Gunarathne commented on AXIS2-2604:
---

Go to http://ws.apache.org/axis2/download/1_0/download.cgi..

Try to download the 1.0 release You will end with a 404

Same goes for all the archived releases (pre 1.1)

> Download links for the archived releases are incorrect
> --
>
> Key: AXIS2-2604
> URL: https://issues.apache.org/jira/browse/AXIS2-2604
> Project: Axis 2.0 (Axis2)
>  Issue Type: Bug
>Reporter: Thilina Gunarathne
> Assigned To: Chatra Nakkawita
>Priority: Critical
>
> We need to update those pages to point to the archived locations..
> eg: http://ws.apache.org/axis2/download/1_0/download.cgi

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Commented: (AXIS2-2523) Axis Service Archiver : aar Eclipse plugin cannot be installed

[Lahiru Sandakith (JIRA)]

[ 
https://issues.apache.org/jira/browse/AXIS2-2523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493852
 ] 

Lahiru Sandakith commented on AXIS2-2523:
-

Please use the 1.2 plugin 
http://www.apache.org/dyn/mirrors/mirrors.cgi/ws/axis2/tools/1_2/axis2-eclipse-service-archiver-wizard-1.2.zip
these is a know issue in the 1.1.1 plugin with the jdk1.4.x , it works with 
1.5.x 



> Axis Service Archiver : aar Eclipse plugin cannot be installed
> --
>
> Key: AXIS2-2523
> URL: https://issues.apache.org/jira/browse/AXIS2-2523
> Project: Axis 2.0 (Axis2)
>  Issue Type: Bug
>  Components: Tools
>Affects Versions: 1.1.1
> Environment: Win 2000 / Eclipse SDK 3.2.0 / Java JDK 1.4.2
>Reporter: Benjamin Pochat
> Assigned To: Lahiru Sandakith
>
> Hi,
> I tried to install the Eclipse plugin to generate aar files. It seems the 
> installation is impossible with Eclipse 3.2.0.
> See the following Eclipse log file :
> !ENTRY org.eclipse.osgi 4 0 2007-04-13 11:21:40.122
> !MESSAGE An error occurred while automatically activating bundle 
> Axis_Service_Archiver (478).
> !STACK 0
> org.osgi.framework.BundleException: The activator 
> org.apache.axis2.tool.service.eclipse.plugin.ServiceArchiver for bundle 
> Axis_Service_Archiver is invalid
>   at 
> org.eclipse.osgi.framework.internal.core.AbstractBundle.loadBundleActivator(AbstractBundle.java:141)
>   at 
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:966)
>   at 
> org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:317)
>   at 
> org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:256)
>   at 
> org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.preFindLocalClass(EclipseLazyStarter.java:86)
>   at 
> org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:409)
>   at 
> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:188)
>   at 
> org.eclipse.osgi.framework.internal.core.BundleLoader.findLocalClass(BundleLoader.java:339)
>   at 
> org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:391)
>   at 
> org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:352)
>   at 
> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:83)
>   at java.lang.ClassLoader.loadClass(Unknown Source)
> 
> Caused by: java.lang.UnsupportedClassVersionError: 
> org/apache/axis2/tool/service/eclipse/plugin/ServiceArchiver (Unsupported 
> major.minor version 49.0)
>   at java.lang.ClassLoader.defineClass0(Native Method)
>   at java.lang.ClassLoader.defineClass(Unknown Source)
>   at 
> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.defineClass(DefaultClassLoader.java:160)
>   at 
> org.eclipse.osgi.baseadaptor.loader.ClasspathManager.defineClass(ClasspathManager.java:498)
>   at 
> org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findClassImpl(ClasspathManager.java:468)
>   at 
> org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClassImpl(ClasspathManager.java:427)
>   at 
> org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:410)
>   at 
> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:188)
>   at 
> org.eclipse.osgi.framework.internal.core.BundleLoader.findLocalClass(BundleLoader.java:339)
>   at 
> org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:391)
>   at 
> org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:352)
>   at 
> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:83)
>   at java.lang.ClassLoader.loadClass(Unknown Source)
> ...
> If you need some additional information about the configuration, please do 
> not hesitate.
> Benjamin

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [Axis2] AxisOperation needs an getMessages() method

[Eran Chinthaka]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi Saminda,

 > Hi All,
> 
> We could get the AxisMessage from the given AxisOperation using the
> AxisOperation.getMessage(String label); In order to get the AxisMessage
> we should know the MEP before hand

Well

1. AxisOperation has a method to know the MEP. see
AxisOperation.getAxisSpecifMEPConstant().

2. AxisOperation is an abstract class so you will always have a specific
implementation for the particular MEP in use which you can use with
instanceof to check the MEP.

So I hope this will help you to get the MEP from AxisOperation.

> and should know the value of the
> label. IMHO there is no way to get the AxisMessages from a given
> AxisOperation.  Shall we introduce a  method,
> 
> *public AxisMessage[] getMessages()* to AxisOperation to the
> AxisMessages from AxisOperation.

I don't think this will help you in any means. The reason is this. If
you know the MEP, from one of the above methods, you will know what the
default message labels are. So use it to get the messages.

#1. If you do not know the label of the messages, in runtime, then how
can you get the relevant message even if you have all the messages. If
they have custom labels, then you must know them before hand even to
process the messages. If you know the custom label, you can call the
existing message.

#2. If you have a MEP, which is different from existing ones, then you
need lot more things to be done in addition to this ;)

I assume Saminda has a very good point to ask this question. Saminda,
you wanna explain exactly what you are trying to do?

Thanks,
Eran Chinthaka
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGO/6cjON2uBzUhh8RAr5CAJ9VWva3J2Pk1XK652oBWKIqug0GMgCgs99w
CtrA9CUSNEu4brGOJSGL3k8=
=wdRU
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Created: (AXIS2-2640) Enum class is not known to this JAXBContext

[Nikhil Thaker (JIRA)]

Enum class is not known to this JAXBContext
---

 Key: AXIS2-2640
 URL: https://issues.apache.org/jira/browse/AXIS2-2640
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: jaxws
Reporter: Nikhil Thaker
 Assigned To: Nikhil Thaker


User reports seeing EnumString is not known to this jaxb context. Enum string 
does not have @XmlType/@XmlElement annotations,
only @XmlEnum. So when the JAXBContext is created using context path it is not 
picked up.

This is resolved by checking for enums in JAXBBlockImpl 
marshall/unmarshallByType methods.


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Commented: (AXIS2-2593) Web Service request loop causes many TIME_WAIT Connections & "BindException: Address already in use: connect"

[Davanum Srinivas (JIRA)]

[ 
https://issues.apache.org/jira/browse/AXIS2-2593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493791
 ] 

Davanum Srinivas commented on AXIS2-2593:
-

Ok then try this tactic. Can you get hold of the OperationContext for
each invocation? Typically you can use
myServiceContext.getLastOperationContext() to get the last
OperationContext. You will have to start caching them though by
calling myServiceClient.setCachingOperationContext(true) or you can
create the OperationContext by calling
myServiceContext.createOperationContext as well. Either way after the
invocation is done you can call the following snippet to cleanup the
HttpMethod.

myOperationContext.getMessageContext(WSDLConstants.MESSAGE_LABEL_OUT_VALUE);
_messageContext.getTransportOut().getSender().cleanup(_messageContext);

thanks,
- Hide quoted text -
dims

On 5/4/07, Michele Mazzucco <[EMAIL PROTECTED]> wrote:
> Dims,
>
> what do you mean by "calling the complete method"?. In this scenario I'm
> using simple ServiceClient(s) sharing the same conf. context and
> attached to custom callbacks (I'm reusing the same ServiceClients for
> thousands of asynchronous requests).
> For my knowledge (see the link below) the cleanup (on the ServiceClient)
> should be called only at the end which, as I said, is after receiving
> thousands of responses.
> Are you then suggesting me to share an OperationClient for all my
> requests and to free resources as soon as I receive the response?
>
> Thanks,
> Michele

> Web Service request loop causes many TIME_WAIT Connections & "BindException: 
> Address already in use: connect"
> -
>
> Key: AXIS2-2593
> URL: https://issues.apache.org/jira/browse/AXIS2-2593
> Project: Axis 2.0 (Axis2)
>  Issue Type: Bug
>Affects Versions: 1.1.1, nightly
> Environment: Windows XP, Tomcat, Axis2 nightly build (also 
> encountered in 1.1.1), JiBX 1.1.3, Microsoft Windows XP [Version 5.1.2600], 
> 126 GB free disk space, 1GB RAM.
>Reporter: David Bueche
>Priority: Critical
>
> I am performing the following:
> - Executing a tight loop calling a singel web service
> - Using the same Stub over and over
> - Creating the Stub with a custom ConfigurationContext (see below)
> - Sending cleanup() to Stub after each message sent (although problem existed 
> even before cleanup() was added)
> After approximately 4000 messages have been sent, an AxisFault is generated 
> caused by the following exception (see below for full stack trace):
>   java.net.BindException: Address already in use: connect
> It appears that connections from the client to Axis on Tomcat sometimes (but 
> not always) remain in the TIME_WAIT state for several minutes.  There are 
> 1200-1500 TIME_WAIT connections open when the AxisFault is generated.
> If I step through the web service messages in a debugger, the problem does 
> not appear to occur, as the system eventually releases the connections after 
> a minute or two.
> Also, if I insert a System.gc() in the client code each time it sends a 
> message to the web service (the commented out line of code below), the 
> AxisFault does not occur.  I have executed the loop over 60,000 times with 
> the garbage collection included without generating an AxisFault.  There were 
> only 400-700 connections in the TIME_WAIT state at a given time, but 
> performance slowed down to a crawl.
> Here is the code I am using to create the Stub:
>   HttpConnectionManagerParams connectionManagerParams = new 
> HttpConnectionManagerParams();
>   connectionManagerParams.setTcpNoDelay(true);
>   connectionManagerParams.setStaleCheckingEnabled(true);
>   
>   MultiThreadedHttpConnectionManager connectionManager = new 
> MultiThreadedHttpConnectionManager();
>   connectionManager.setParams(connectionManagerParams);
>   HttpClient httpClient = new HttpClient(connectionManager);
>   
>   ConfigurationContext configurationContext = 
> ConfigurationContextFactory.createConfigurationContextFromFileSystem(null, 
> null);
>   configurationContext.setProperty(HTTPConstants.REUSE_HTTP_CLIENT, 
> Boolean.TRUE);
>   configurationContext.setProperty(HTTPConstants.CACHED_HTTP_CLIENT, 
> httpClient);
>   
>   stub = new MyServiceStub(configurationContext, target);
>   
>   boolean success = true;
>   while(success) {
>   success = stub.performService(records);
>   stub.cleanup();
>   //  System.gc();
>   }
> Here is the complete stack trace:
>   Exception in thread "main" org.apache.axis2.AxisFault: Address already 
> in use: connect
>   at org.apache.axis2.AxisFault.makeFault(AxisFault.java:377)
>   at 
> org.

[jira] Commented: (AXIS2-2593) Web Service request loop causes many TIME_WAIT Connections & "BindException: Address already in use: connect"

[Davanum Srinivas (JIRA)]

[ 
https://issues.apache.org/jira/browse/AXIS2-2593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493790
 ] 

Davanum Srinivas commented on AXIS2-2593:
-

[Posting my email comments here]

Michele,

Are you calling the complete method in OperationClient? that calls the
cleanup method in the TransportSender. I believe we are doing that
automatically in generated stubs as well where we generate the
following call.

_messageContext.getTransportOut().getSender().cleanup(_messageContext);

that calls the releaseConnection on the HttpMethod.

> Web Service request loop causes many TIME_WAIT Connections & "BindException: 
> Address already in use: connect"
> -
>
> Key: AXIS2-2593
> URL: https://issues.apache.org/jira/browse/AXIS2-2593
> Project: Axis 2.0 (Axis2)
>  Issue Type: Bug
>Affects Versions: 1.1.1, nightly
> Environment: Windows XP, Tomcat, Axis2 nightly build (also 
> encountered in 1.1.1), JiBX 1.1.3, Microsoft Windows XP [Version 5.1.2600], 
> 126 GB free disk space, 1GB RAM.
>Reporter: David Bueche
>Priority: Critical
>
> I am performing the following:
> - Executing a tight loop calling a singel web service
> - Using the same Stub over and over
> - Creating the Stub with a custom ConfigurationContext (see below)
> - Sending cleanup() to Stub after each message sent (although problem existed 
> even before cleanup() was added)
> After approximately 4000 messages have been sent, an AxisFault is generated 
> caused by the following exception (see below for full stack trace):
>   java.net.BindException: Address already in use: connect
> It appears that connections from the client to Axis on Tomcat sometimes (but 
> not always) remain in the TIME_WAIT state for several minutes.  There are 
> 1200-1500 TIME_WAIT connections open when the AxisFault is generated.
> If I step through the web service messages in a debugger, the problem does 
> not appear to occur, as the system eventually releases the connections after 
> a minute or two.
> Also, if I insert a System.gc() in the client code each time it sends a 
> message to the web service (the commented out line of code below), the 
> AxisFault does not occur.  I have executed the loop over 60,000 times with 
> the garbage collection included without generating an AxisFault.  There were 
> only 400-700 connections in the TIME_WAIT state at a given time, but 
> performance slowed down to a crawl.
> Here is the code I am using to create the Stub:
>   HttpConnectionManagerParams connectionManagerParams = new 
> HttpConnectionManagerParams();
>   connectionManagerParams.setTcpNoDelay(true);
>   connectionManagerParams.setStaleCheckingEnabled(true);
>   
>   MultiThreadedHttpConnectionManager connectionManager = new 
> MultiThreadedHttpConnectionManager();
>   connectionManager.setParams(connectionManagerParams);
>   HttpClient httpClient = new HttpClient(connectionManager);
>   
>   ConfigurationContext configurationContext = 
> ConfigurationContextFactory.createConfigurationContextFromFileSystem(null, 
> null);
>   configurationContext.setProperty(HTTPConstants.REUSE_HTTP_CLIENT, 
> Boolean.TRUE);
>   configurationContext.setProperty(HTTPConstants.CACHED_HTTP_CLIENT, 
> httpClient);
>   
>   stub = new MyServiceStub(configurationContext, target);
>   
>   boolean success = true;
>   while(success) {
>   success = stub.performService(records);
>   stub.cleanup();
>   //  System.gc();
>   }
> Here is the complete stack trace:
>   Exception in thread "main" org.apache.axis2.AxisFault: Address already 
> in use: connect
>   at org.apache.axis2.AxisFault.makeFault(AxisFault.java:377)
>   at 
> org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:179)
>   at 
> org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:73)
>   at 
> org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:310)
>   at 
> org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:202)
>   at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:446)
>   at 
> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:330)
>   at 
> org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:294)
>   at 
> com.ws.service.MyServiceStub.performService(MyServiceStub.java:300)
>   at com.ws.client.MyClient.main(MyClient.java:88)
>   Caused by: java.net.BindException: Address 

Re: [axis2] ContextFactory - get rid of it?

[Chamikara Jayalath]

Hi Glen,

On 5/4/07, Glen Daniels <[EMAIL PROTECTED]> wrote:


Hi Chamikara!

OK, I'll take care of this refactor over the weekend.  Before I do, let
me confirm the design with you.  You're only concerned about the
creation of contexts, and you don't want to actually inject creation
functionality yourself?  In other words, this kind of thing is sufficient:

ServiceContext {
   OperationContext createOperationContext(AxisOperation op) {
 if (op == null) throw new IllegalArgumentException();
 OperationContext oc = new OperationContext(op, this);
 ContextListener cl = myConfigCtx.getContextListener();
 if (cl != null) cl.contextCreated(oc);
 return oc;
   }
}

Yes/no?




Well, we need to inform other instances that a context was created. So we
need to hv something like ClusteringContextListener deployed. Guess we hv to
go for a array of listeners. Something like,

ServiceContext {
   OperationContext createOperationContext(AxisOperation op) {
   if (op == null) throw new IllegalArgumentException();
   OperationContext oc = new OperationContext(op, this);
   Iterator listeners = myConfigCtx.getContextListeners();
   while (listeners.hasNext) {
   ((ContextListener) listener).contextCreated(oc);
  }
  return oc;
   }
}


Chamikara


--Glen


Chamikara Jayalath wrote:
> Hi Glen, Deepal,
>
> All we needed was a way to get notified when a certain context get
> created in the system. I think we didn't go for the ContextListener
> method becoz of possible performance drawbacks. But it absolutely was my
> preference. Would be glad if we can get that introduced.
>
> Chamikara
>
>
> On 5/4/07, *Glen Daniels* <[EMAIL PROTECTED]
> > wrote:
>
> Deepal Jayasinghe wrote:
>  > I really like the idea, but one of the reason to introduce that
> factory
>  > was to support clustering requirements. They wanted to have a
single
>  > place of creating all the Contexts , then they have only one
> place to
>  > worry about. They wanted to have some triggering mechanism when
when
>  > creating Contexts that is why we introduced that.
>
> Hm... and yet that doesn't seem to happen, because everything right
now
> uses ContextFactory directly, and I don't see any hooks in there for
> supporting notifications, just a bunch of static methods.  ?
>
> I'll go read those threads (thanks for the pointers), but I think
there
> are perhaps better ways to achieve the goals than a static factory
> class, depending on exactly what the requirements are.  For example:
>
> ConfigurationContext {
>  public void setContextListener(ContextListener);
> }
>
> then every sub-context create method does something like this:
>
> ServiceContext {
>public OperationContext createOpContext(AxisOperation) {
>  if (myConfigContext.hasContextListener()) {
>// Either ask the listener to get the context itself,
>// or just notify it, etc... then return it.
>  } else {
>return new OperationContext(AxisOperation, this);
>  }
>}
> }
>
> Thanks,
> --Glen
>
>
-
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> 
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
>
>
>
>
> --
> Chamikara Jayalath
> WSO2 Inc.
> http://wso2.com/
> http://wso2.org/ - For your Oxygen needs

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





--
Chamikara Jayalath
WSO2 Inc.
http://wso2.com/
http://wso2.org/ - For your Oxygen needs

Re: [axis2] ContextFactory - get rid of it?

[Chamikara Jayalath]

Hi Dims,

On 5/4/07, Davanum Srinivas <[EMAIL PROTECTED]> wrote:


Chamikara,

What do they say about premature optimization? :)




Good point :-)
So lets do it the correct way.

Chamikara



-- dims


On 5/4/07, Chamikara Jayalath <[EMAIL PROTECTED]> wrote:
> Hi Glen, Deepal,
>
> All we needed was a way to get notified when a certain context get
created
> in the system. I think we didn't go for the ContextListener method becoz
of
> possible performance drawbacks. But it absolutely was my preference.
Would
> be glad if we can get that introduced.
>
> Chamikara
>
>
>
> On 5/4/07, Glen Daniels <[EMAIL PROTECTED]> wrote:
> > Deepal Jayasinghe wrote:
> > > I really like the idea, but one of the reason to introduce that
factory
> > > was to support clustering requirements. They wanted to have a single
> > > place of creating all the Contexts , then they have only one place
to
> > > worry about. They wanted to have some triggering mechanism when when
> > > creating Contexts that is why we introduced that.
> >
> > Hm... and yet that doesn't seem to happen, because everything right
now
> > uses ContextFactory directly, and I don't see any hooks in there for
> > supporting notifications, just a bunch of static methods.  ?
> >
> > I'll go read those threads (thanks for the pointers), but I think
there
> > are perhaps better ways to achieve the goals than a static factory
> > class, depending on exactly what the requirements are.  For example:
> >
> > ConfigurationContext {
> >  public void setContextListener(ContextListener);
> > }
> >
> > then every sub-context create method does something like this:
> >
> > ServiceContext {
> >public OperationContext createOpContext(AxisOperation) {
> >  if (myConfigContext.hasContextListener()) {
> >// Either ask the listener to get the context itself,
> >// or just notify it, etc... then return it.
> >  } else {
> >return new OperationContext(AxisOperation, this);
> >  }
> >}
> > }
> >
> > Thanks,
> > --Glen
> >
> >
> -
> > To unsubscribe, e-mail:
> [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
>
> --
> Chamikara Jayalath
> WSO2 Inc.
> http://wso2.com/
> http://wso2.org/ - For your Oxygen needs


--
Davanum Srinivas :: http://davanum.wordpress.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





--
Chamikara Jayalath
WSO2 Inc.
http://wso2.com/
http://wso2.org/ - For your Oxygen needs

[jira] Commented: (AXIS2-2565) Documentation cleanup of ADB how-to pages

[Glen Mazza (JIRA)]

[ 
https://issues.apache.org/jira/browse/AXIS2-2565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493743
 ] 

Glen Mazza commented on AXIS2-2565:
---

Hello Chatra,

If I check more website pages, should I create a patch against the 1.2
branch or against the trunk?  Which is easier for you?

Thanks,
Glen





> Documentation cleanup of ADB how-to pages
> -
>
> Key: AXIS2-2565
> URL: https://issues.apache.org/jira/browse/AXIS2-2565
> Project: Axis 2.0 (Axis2)
>  Issue Type: Improvement
>  Components: documentation
>Affects Versions: nightly
>Reporter: Glen Mazza
> Assigned To: Chatra Nakkawita
>Priority: Minor
> Fix For: 1.2
>
> Attachments: adbpatch.txt
>
>
> While studying the four ADB docs I made a note of and fixed typos, 
> grammatical nitpicks, etc.  Patch is attached.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

WS-Transaction sample

[Marcus Vinicius A Silva]

Hi,

I'm trying implement Ws-transaction example with Axis
2. But in my searches i didn't find any sample. I
found some APIs to implement it, like kandula
Apache,jax-ws,WS-TX, but i dont't know the best.
Do you know if there is someone that have implemented
something using this especification.

Best regards,

Marcus Vinicius


Pessoal

alguem já implementou transações atômicos com web
services? Na net vejo muito especificação, mas queria
algo mais na prática. Alguem já trabalhou? Qual API
vocês utilizaram?
Vi por alto o kandula, jax-ws e wsit. Alguma
recomendação?

Agradecido

Marcus Vinicius

__
Fale com seus amigos  de graça com o novo Yahoo! Messenger 
http://br.messenger.yahoo.com/ 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Created: (AXIS-2659) Weblogic 8.1 & axis 1.4 org.apache.axis.encoding.ser.BeanDeserializer.onStartChild(BeanDeserializer.java:258

[David Langston (JIRA)]

Weblogic 8.1 & axis 1.4 
org.apache.axis.encoding.ser.BeanDeserializer.onStartChild(BeanDeserializer.java:258


 Key: AXIS-2659
 URL: https://issues.apache.org/jira/browse/AXIS-2659
 Project: Axis
  Issue Type: Bug
  Components: Serialization/Deserialization
Affects Versions: 1.4
 Environment: Sun/BEA Weblogic
Reporter: David Langston
 Fix For: 1.4


Looks like we are having issues around getting our service to work correctly on 
weblogic 8.1. If there is configuration we need to do on weblogic 8.1 that 
anyone can share that would be great. Thanks for your help,

Message: severity=Error date=May 1, 2007 time=6:06:08 PM

Description:(ImplAbstractWSService.java:140) 
ImplAppGetAccountProfileSrv.invoke() - failed when invoke the web service. The 
error is: 

Throws:AxisFault

 faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException

 faultSubcode: 

 faultString: org.xml.sax.SAXException: Invalid element in 
com.cingular.csi.CSI.Namespaces.Types.Public.CingularDataModel_xsd.AccountBillingInfo
 - billDate

 faultActor: 

 faultNode: 

 faultDetail: 

{http://xml.apache.org/axis/}stackTrace:org.xml.sax.SAXException: 
Invalid element in 
com.cingular.csi.CSI.Namespaces.Types.Public.CingularDataModel_xsd.AccountBillingInfo
 - billDate

at 
org.apache.axis.encoding.ser.BeanDeserializer.onStartChild(BeanDeserializer.java:258)

 

The CSI InquireAccountProfile Response is not parsing by the Axis. It is giving 
error. 



-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [axis2] ContextFactory - get rid of it?

[Glen Daniels]

Hi Chamikara!

OK, I'll take care of this refactor over the weekend.  Before I do, let 
me confirm the design with you.  You're only concerned about the 
creation of contexts, and you don't want to actually inject creation 
functionality yourself?  In other words, this kind of thing is sufficient:


ServiceContext {
  OperationContext createOperationContext(AxisOperation op) {
if (op == null) throw new IllegalArgumentException();
OperationContext oc = new OperationContext(op, this);
ContextListener cl = myConfigCtx.getContextListener();
if (cl != null) cl.contextCreated(oc);
return oc;
  }
}

Yes/no?

--Glen

Chamikara Jayalath wrote:

Hi Glen, Deepal,

All we needed was a way to get notified when a certain context get 
created in the system. I think we didn't go for the ContextListener 
method becoz of possible performance drawbacks. But it absolutely was my 
preference. Would be glad if we can get that introduced.


Chamikara


On 5/4/07, *Glen Daniels* <[EMAIL PROTECTED] 
> wrote:


Deepal Jayasinghe wrote:
 > I really like the idea, but one of the reason to introduce that
factory
 > was to support clustering requirements. They wanted to have a single
 > place of creating all the Contexts , then they have only one
place to
 > worry about. They wanted to have some triggering mechanism when when
 > creating Contexts that is why we introduced that.

Hm... and yet that doesn't seem to happen, because everything right now
uses ContextFactory directly, and I don't see any hooks in there for
supporting notifications, just a bunch of static methods.  ?

I'll go read those threads (thanks for the pointers), but I think there
are perhaps better ways to achieve the goals than a static factory
class, depending on exactly what the requirements are.  For example:

ConfigurationContext {
 public void setContextListener(ContextListener);
}

then every sub-context create method does something like this:

ServiceContext {
   public OperationContext createOpContext(AxisOperation) {
 if (myConfigContext.hasContextListener()) {
   // Either ask the listener to get the context itself,
   // or just notify it, etc... then return it.
 } else {
   return new OperationContext(AxisOperation, this);
 }
   }
}

Thanks,
--Glen

-
To unsubscribe, e-mail: [EMAIL PROTECTED]

For additional commands, e-mail: [EMAIL PROTECTED]





--
Chamikara Jayalath
WSO2 Inc.
http://wso2.com/
http://wso2.org/ - For your Oxygen needs


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Patches provided for issues AXIS2-2055 and AXIS2-1899

[Deepal Jayasinghe]

Actually error occur when you deploy the service and then generate code
using the wsdl. Then invoke the service using generated stub , after
that we got the error.

Thanks
Deepal

Sathija Pavuluri wrote:

> Charitha,
>
> With the patch applied, I am able to build the samples module
> successfully.
> Is there anything else I need to test to reproduce the exception?
>
> Thanks,
> Sathija.
>
>
> - Original Message 
> From: Charitha Kankanamge <[EMAIL PROTECTED]>
> To: axis-dev@ws.apache.org
> Sent: Friday, May 4, 2007 2:23:07 AM
> Subject: Re: Patches provided for issues AXIS2-2055 and AXIS2-1899
>
> Sathija,
> We were testing a Axis2-1.2 build just before releasing 1.2 and found
> out that the pojo, pojoguide and pojoguidespring samples did not work at
> all. I can't remember the exception and without reporting it through
> JIRA I reported it to Deepal for fixing it quickily since we were about
> to release Axis2-1.2. Those samples worked fine in all axis2-1.2 release
> candidates. Those issues came only in the last build we got on 27th
> April. Your patch was the culprit for this error and we did not
> encounter any errors in those samples after reverting that patch. We
> should be able to reproduce it and report the error if a binary can be
> provided with applying that patch again.
>
> Thanks and regards
> Charitha
>
>
> Deepal Jayasinghe wrote:
>
> >Hi Sathija ,
> >
> >Once I applied your patch , it broke the Axis2 samples. I think Caritha
> >will be able to answer this better than me , since he is the one who
> >find the bug :)
> >
> >Thanks
> >Deepal
> >
> >  
> >
> >>Deepal,
> >>
> >>I had earlier posted a question about the codegen issue you mentioned
> >>after patches for AXIS2-2055 were applied.
> >>I have since built the codegen module with the patch and didnt notice
> >>any issue and nor were there any issues
> >>building any of other axis2 modules.
> >>So I am still puzzled by what issue the patch may have caused. Would
> >>you please elaborate on that issue you mentioned the patch had caused.
> >>
> >>Also, the issues AXIS2-2055 and AXIS2-1899 are marked as resolved, but
> >>they are in fact not, because of the patch reversal.
> >>
> >>Thanks.
> >>Sathija.
> >>
> >>
> >>
> >>- Original Message 
> >>From: Deepal Jayasinghe <[EMAIL PROTECTED]>
> >>To: axis-dev@ws.apache.org
> >>Sent: Friday, April 27, 2007 12:10:41 PM
> >>Subject: Re: Patches provided for issues AXIS2-2055 and AXIS2-1899
> >>
> >>Yes , there was an issue with the codegen , so I had to revert that.
> >>
> >>Thanks
> >>Deepal
> >>
> >>Sathija Pavuluri wrote:
> >>
> >>
> >>
> >>>Deepal,
> >>>
> >>>Noticed that the patches were applied and then reverted on the 1.2
> >>>  
> >>>
> >>branch?
> >>
> >>
> >>>Was anything wrong?
> >>>
> >>>Thanks
> >>>Sathija.
> >>>
> >>>
> >>>- Original Message 
> >>>From: Deepal Jayasinghe <[EMAIL PROTECTED]>
> >>>To: axis-dev@ws.apache.org
> >>>Sent: Friday, April 27, 2007 12:16:05 AM
> >>>Subject: Re: Patches provided for issues AXIS2-2055 and AXIS2-1899
> >>>
> >>>Done , thx very much for your patches.
> >>>
> >>>Thanks
> >>>Deepal
> >>>
> >>>
> >>>-
> >>>To unsubscribe, e-mail: [EMAIL PROTECTED]
> >>>For additional commands, e-mail: [EMAIL PROTECTED]
> >>>
> >>>
> >>>
> >>>
> >>>Ahhh...imagining that irresistible "new car" smell?
> >>>Check out new cars at Yahoo! Autos.
> >>>
> >>>  
> >>>
> >>
> >>
> >>
> >>
> >>--
> >>Thanks,
> >>Deepal
> >>
> >>"The highest tower is built one brick at a time"
> >>
> >>
> >>
> >>-
> >>To unsubscribe, e-mail: [EMAIL PROTECTED]
> >>For additional commands, e-mail: [EMAIL PROTECTED]
> >>
> >>
> >>
> >>
> >>Ahhh...imagining that irresistible "new car" smell?
> >>Check out new cars at Yahoo! Autos.
> >>
> >>
> >>
> >
> >
> >
> >  
> >
>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
> __
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com 


-- 
Thanks,
Deepal

"The highest tower is built one brick at a time"



-
To unsubscribe, e-mail: [EMAI

[Axis2][continuum] BUILD SUCCESSFUL

[davidillsley (Continuum)]

Online report : 
http://ws.zones.apache.org:1/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/1/buildId/1957
Build statistics:
  State: Ok
  Previous State: Error
  Started at: Fri, 4 May 2007 13:50:42 +
  Finished at: Fri, 4 May 2007 14:34:53 +
  Total time: 44m 10s
  Build Trigger: Forced
  Exit code: 0
  Building machine hostname: ws.zones.apache.org
  Operating system : SunOS(unknown)
  Java version : 1.5.0_09(Sun Microsystems Inc.)

Changes
 dims  fix build break
 /webservices/axis2/trunk/java/modules/adb-codegen/pom.xml


Output:

Snipped Output:
build:start:

multiproject:install-callback:
[echo] Running jar:install for Apache Axis 2.0 - MTOM Policy
java:prepare-filesystem:
[mkdir] Created dir: 
/export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/mtompolicy/target/classes
Running post goal: java:prepare-filesystem

java:compile:
[copy] Copying 1 file to 
/export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/mtompolicy/target/classes/META-INF
[echo] Compiling to 
/export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/mtompolicy/target/classes
[javac] Compiling 2 source files to 
/export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/mtompolicy/target/classes

java:jar-resources:
Copying 2 files to 
/export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/mtompolicy/target/classes/META-INF

test:test:
java:prepare-filesystem:
Running post goal: java:prepare-filesystem

java:compile:
[echo] Compiling to 
/export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/mtompolicy/target/classes

java:jar-resources:

test:prepare-filesystem:
[mkdir] Created dir: 
/export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/mtompolicy/target/test-classes
[mkdir] Created dir: 
/export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/mtompolicy/target/test-reports

test:test-resources:
Copying 1 file to 
/export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/mtompolicy/target/test-classes

test:compile:
[javac] Compiling 1 source file to 
/export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/mtompolicy/target/test-classes

[junit] Running org.apache.axis2.policy.model.MTOMAssertionTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.495 sec

jar:jar:
[jar] Building jar: 
/export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/mtompolicy/target/axis2-mtompolicy-SNAPSHOT.jar

jar:install:
[echo] Installing...
Uploading to org.apache.axis2/jars/axis2-mtompolicy-SNAPSHOT.jar: 
 (8K)
Uploading to org.apache.axis2/poms/axis2-mtompolicy-SNAPSHOT.pom: 
 (13K)

+
| Executing multiproject:install-callback Apache Axis 2.0 - ping
| Memory: 31M/52M
+
DEPRECATED: the default goal should be specified in the  section of 
project.xml instead of maven.xml
DEPRECATED: the default goal should be specified in the  section of 
project.xml instead of maven.xml

build:end:

build:start:

multiproject:install-callback:
[echo] Running jar:install for Apache Axis 2.0 - ping
java:prepare-filesystem:
[mkdir] Created dir: 
/export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/ping/target/classes
Running post goal: java:prepare-filesystem

java:compile:
[echo] Compiling to 
/export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/ping/target/classes
[javac] Compiling 3 source files to 
/export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/ping/target/classes
Running post goal: java:compile
[mkdir] Created dir: 
/export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/ping/target/classes/META-INF
[copy] Copying 1 file to 
/export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/ping/target/classes/META-INF
[copy] Copying 1 file to 
/export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/ping/target/classes/META-INF
[copy] Copying 1 file to 
/export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/ping/target/classes/META-INF
[mkdir] Created dir: 
/export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/ping/target/modules
[jar] Building jar: 
/export/

Invoke Axis2 Web Service from Non JVM Client?

[Rupal Soni]

I want to develop Axis2 Web Service on MyEclipse and want to be able to invoke 
it via any client which may be java, non java, non JVM compatible. In short I 
want my Web Service to return XML response which can be utilized by any type of 
client. Please let me know if this is possible with a Web Service developed in 
Axis2 and how. If not, are there any other alternatives. 
 __
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

[Axis2][continuum] BUILD ERROR

[davidillsley (Continuum)]

Online report : 
http://ws.zones.apache.org:1/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/1/buildId/1956
Build statistics:
  State: Error
  Previous State: Ok
  Started at: Fri, 4 May 2007 13:40:04 +
  Finished at: Fri, 4 May 2007 13:43:36 +
  Total time: 3m 32s
  Build Trigger: Forced
  Exit code: 0
  Building machine hostname: ws.zones.apache.org
  Operating system : SunOS(unknown)
  Java version : 1.5.0_09(Sun Microsystems Inc.)

Changes
  No files changed
  

Build Error:

Provider message: The svn command failed.
Command output: 
---
svn: Caught signal
---



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [axis2] ContextFactory - get rid of it?

[Davanum Srinivas]

Chamikara,

What do they say about premature optimization? :)

-- dims

On 5/4/07, Chamikara Jayalath <[EMAIL PROTECTED]> wrote:

Hi Glen, Deepal,

All we needed was a way to get notified when a certain context get created
in the system. I think we didn't go for the ContextListener method becoz of
possible performance drawbacks. But it absolutely was my preference. Would
be glad if we can get that introduced.

Chamikara



On 5/4/07, Glen Daniels <[EMAIL PROTECTED]> wrote:
> Deepal Jayasinghe wrote:
> > I really like the idea, but one of the reason to introduce that factory
> > was to support clustering requirements. They wanted to have a single
> > place of creating all the Contexts , then they have only one place to
> > worry about. They wanted to have some triggering mechanism when when
> > creating Contexts that is why we introduced that.
>
> Hm... and yet that doesn't seem to happen, because everything right now
> uses ContextFactory directly, and I don't see any hooks in there for
> supporting notifications, just a bunch of static methods.  ?
>
> I'll go read those threads (thanks for the pointers), but I think there
> are perhaps better ways to achieve the goals than a static factory
> class, depending on exactly what the requirements are.  For example:
>
> ConfigurationContext {
>  public void setContextListener(ContextListener);
> }
>
> then every sub-context create method does something like this:
>
> ServiceContext {
>public OperationContext createOpContext(AxisOperation) {
>  if (myConfigContext.hasContextListener()) {
>// Either ask the listener to get the context itself,
>// or just notify it, etc... then return it.
>  } else {
>return new OperationContext(AxisOperation, this);
>  }
>}
> }
>
> Thanks,
> --Glen
>
>
-
> To unsubscribe, e-mail:
[EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>



--
Chamikara Jayalath
WSO2 Inc.
http://wso2.com/
http://wso2.org/ - For your Oxygen needs



--
Davanum Srinivas :: http://davanum.wordpress.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [axis2] ContextFactory - get rid of it?

[Chamikara Jayalath]

Hi Glen, Deepal,

All we needed was a way to get notified when a certain context get created
in the system. I think we didn't go for the ContextListener method becoz of
possible performance drawbacks. But it absolutely was my preference. Would
be glad if we can get that introduced.

Chamikara


On 5/4/07, Glen Daniels <[EMAIL PROTECTED]> wrote:


Deepal Jayasinghe wrote:
> I really like the idea, but one of the reason to introduce that factory
> was to support clustering requirements. They wanted to have a single
> place of creating all the Contexts , then they have only one place to
> worry about. They wanted to have some triggering mechanism when when
> creating Contexts that is why we introduced that.

Hm... and yet that doesn't seem to happen, because everything right now
uses ContextFactory directly, and I don't see any hooks in there for
supporting notifications, just a bunch of static methods.  ?

I'll go read those threads (thanks for the pointers), but I think there
are perhaps better ways to achieve the goals than a static factory
class, depending on exactly what the requirements are.  For example:

ConfigurationContext {
 public void setContextListener(ContextListener);
}

then every sub-context create method does something like this:

ServiceContext {
   public OperationContext createOpContext(AxisOperation) {
 if (myConfigContext.hasContextListener()) {
   // Either ask the listener to get the context itself,
   // or just notify it, etc... then return it.
 } else {
   return new OperationContext(AxisOperation, this);
 }
   }
}

Thanks,
--Glen

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





--
Chamikara Jayalath
WSO2 Inc.
http://wso2.com/
http://wso2.org/ - For your Oxygen needs

Re: Patches provided for issues AXIS2-2055 and AXIS2-1899

[Davanum Srinivas]

Sathija,

Could you please deploy them and test them? i believe it was a runtime issue.

-- dims

On 5/4/07, Sathija Pavuluri <[EMAIL PROTECTED]> wrote:


Charitha,

With the patch applied, I am able to build the samples module successfully.
Is there anything else I need to test to reproduce the exception?

Thanks,
Sathija.


- Original Message 
From: Charitha Kankanamge <[EMAIL PROTECTED]>
To: axis-dev@ws.apache.org
Sent: Friday, May 4, 2007 2:23:07 AM
Subject: Re: Patches provided for issues AXIS2-2055 and AXIS2-1899

Sathija,
We were testing a Axis2-1.2 build just before releasing 1.2 and found
out that the pojo, pojoguide and pojoguidespring samples did not work at
all. I can't remember the exception and without reporting it through
JIRA I reported it to Deepal for fixing it quickily since we were about
to release Axis2-1.2. Those samples worked fine in all axis2-1.2 release
candidates. Those issues came only in the last build we got on 27th
April. Your patch was the culprit for this error and we did not
encounter any errors in those samples after reverting that patch. We
should be able to reproduce it and report the error if a binary can be
provided with applying that patch again.

Thanks and regards
Charitha


Deepal Jayasinghe wrote:

>Hi Sathija ,
>
>Once I applied your patch , it broke the Axis2 samples. I think Caritha
>will be able to answer this better than me , since he is the one who
>find the bug :)
>
>Thanks
>Deepal
>
>
>
>>Deepal,
>>
>>I had earlier posted a question about the codegen issue you mentioned
>>after patches for AXIS2-2055 were applied.
>>I have since built the codegen module with the patch and didnt notice
>>any issue and nor were there any issues
>>building any of other axis2 modules.
>>So I am still puzzled by what issue the patch may have caused. Would
>>you please elaborate on that issue you mentioned the patch had caused.
>>
>>Also, the issues AXIS2-2055 and AXIS2-1899 are marked as resolved, but
>>they are in fact not, because of the patch reversal.
>>
>>Thanks.
>>Sathija.
>>
>>
>>
>>- Original Message 
>>From: Deepal Jayasinghe <[EMAIL PROTECTED]>
>>To: axis-dev@ws.apache.org
>>Sent: Friday, April 27, 2007 12:10:41 PM
>>Subject: Re: Patches provided for issues AXIS2-2055 and AXIS2-1899
>>
>>Yes , there was an issue with the codegen , so I had to revert that.
>>
>>Thanks
>>Deepal
>>
>>Sathija Pavuluri wrote:
>>
>>
>>
>>>Deepal,
>>>
>>>Noticed that the patches were applied and then reverted on the 1.2
>>>
>>>
>>branch?
>>
>>
>>>Was anything wrong?
>>>
>>>Thanks
>>>Sathija.
>>>
>>>
>>>- Original Message 
>>>From: Deepal Jayasinghe <[EMAIL PROTECTED]>
>>>To: axis-dev@ws.apache.org
>>>Sent: Friday, April 27, 2007 12:16:05 AM
>>>Subject: Re: Patches provided for issues AXIS2-2055 and AXIS2-1899
>>>
>>>Done , thx very much for your patches.
>>>
>>>Thanks
>>>Deepal
>>>
>>>
>>>-
>>>To unsubscribe, e-mail:
[EMAIL PROTECTED]
>>>For additional commands, e-mail: [EMAIL PROTECTED]
>>>
>>>
>>>
>>>
>>>Ahhh...imagining that irresistible "new car" smell?
>>>Check out new cars at Yahoo! Autos.
>>>
>>>
>>>
>>
>>
>>
>>
>>--
>>Thanks,
>>Deepal
>>
>>"The highest tower is built one brick at a time"
>>
>>
>>
>>-
>>To unsubscribe, e-mail:
[EMAIL PROTECTED]
>>For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>>
>>
>>Ahhh...imagining that irresistible "new car" smell?
>>Check out new cars at Yahoo! Autos.
>>
>>
>>
>
>
>
>
>



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com



--
Davanum Srinivas :: http://davanum.wordpress.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Patches provided for issues AXIS2-2055 and AXIS2-1899

[Sathija Pavuluri]

Charitha,

With the patch applied, I am able to build the samples module successfully. 
Is there anything else I need to test to reproduce the exception?

Thanks,
Sathija.


- Original Message 
From: Charitha Kankanamge <[EMAIL PROTECTED]>
To: axis-dev@ws.apache.org
Sent: Friday, May 4, 2007 2:23:07 AM
Subject: Re: Patches provided for issues AXIS2-2055 and AXIS2-1899

Sathija,
We were testing a Axis2-1.2 build just before releasing 1.2 and found 
out that the pojo, pojoguide and pojoguidespring samples did not work at 
all. I can't remember the exception and without reporting it through 
JIRA I reported it to Deepal for fixing it quickily since we were about 
to release Axis2-1.2. Those samples worked fine in all axis2-1.2 release 
candidates. Those issues came only in the last build we got on 27th 
April. Your patch was the culprit for this error and we did not 
encounter any errors in those samples after reverting that patch. We 
should be able to reproduce it and report the error if a binary can be 
provided with applying that patch again.

Thanks and regards
Charitha


Deepal Jayasinghe wrote:

>Hi Sathija ,
>
>Once I applied your patch , it broke the Axis2 samples. I think Caritha
>will be able to answer this better than me , since he is the one who
>find the bug :)
>
>Thanks
>Deepal
>
>  
>
>>Deepal,
>>
>>I had earlier posted a question about the codegen issue you mentioned
>>after patches for AXIS2-2055 were applied.
>>I have since built the codegen module with the patch and didnt notice
>>any issue and nor were there any issues
>>building any of other axis2 modules.
>>So I am still puzzled by what issue the patch may have caused. Would
>>you please elaborate on that issue you mentioned the patch had caused.
>>
>>Also, the issues AXIS2-2055 and AXIS2-1899 are marked as resolved, but
>>they are in fact not, because of the patch reversal.
>>
>>Thanks.
>>Sathija.
>>
>>
>>
>>- Original Message 
>>From: Deepal Jayasinghe <[EMAIL PROTECTED]>
>>To: axis-dev@ws.apache.org
>>Sent: Friday, April 27, 2007 12:10:41 PM
>>Subject: Re: Patches provided for issues AXIS2-2055 and AXIS2-1899
>>
>>Yes , there was an issue with the codegen , so I had to revert that.
>>
>>Thanks
>>Deepal
>>
>>Sathija Pavuluri wrote:
>>
>>
>>
>>>Deepal,
>>>
>>>Noticed that the patches were applied and then reverted on the 1.2
>>>  
>>>
>>branch?
>>
>>
>>>Was anything wrong?
>>>
>>>Thanks
>>>Sathija.
>>>
>>>
>>>- Original Message 
>>>From: Deepal Jayasinghe <[EMAIL PROTECTED]>
>>>To: axis-dev@ws.apache.org
>>>Sent: Friday, April 27, 2007 12:16:05 AM
>>>Subject: Re: Patches provided for issues AXIS2-2055 and AXIS2-1899
>>>
>>>Done , thx very much for your patches.
>>>
>>>Thanks
>>>Deepal
>>>
>>>
>>>-
>>>To unsubscribe, e-mail: [EMAIL PROTECTED]
>>>For additional commands, e-mail: [EMAIL PROTECTED]
>>>
>>>
>>>
>>>
>>>Ahhh...imagining that irresistible "new car" smell?
>>>Check out new cars at Yahoo! Autos.
>>>
>>>  
>>>
>>
>>
>>
>>
>>-- 
>>Thanks,
>>Deepal
>>
>>"The highest tower is built one brick at a time"
>>
>>
>>
>>-
>>To unsubscribe, e-mail: [EMAIL PROTECTED]
>>For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>>
>>
>>Ahhh...imagining that irresistible "new car" smell?
>>Check out new cars at Yahoo! Autos.
>>
>>
>>
>
>
>
>  
>



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]







__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

[jira] Commented: (AXIS-2391) WSDL2Java ignores attributes for complex types that have only element with maxOccurs=unbounded in sequence

[JIRA]

[ 
https://issues.apache.org/jira/browse/AXIS-2391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493661
 ] 

Sören-Helge Zaschke commented on AXIS-2391:
---

It looks like the same bug as I have observed:
AXIS can not handle the following type definition:







Fix 1:
Change the xsd by adding another element (that is not used), e.g.








Fix 2:
Correct the AXIS source code, SchemaUtils.java:

public static QName getCollectionComponentQName(Node node,
QNameHolder itemQName,
BooleanHolder forElement,
SymbolTable symbolTable) {
// If we're going to turn "wrapped" arrays into types such that
...
}
if (element == null) {
return null;
}

// OK, exactly one element child of ,
// now check if there is no attribute
if (SchemaUtils.getChildByName(node, "attribute") != null) {
return null;
}

// continue the processing using that element ...




> WSDL2Java ignores attributes for complex types that have only element with 
> maxOccurs=unbounded in sequence
> --
>
> Key: AXIS-2391
> URL: https://issues.apache.org/jira/browse/AXIS-2391
> Project: Axis
>  Issue Type: Bug
>  Components: WSDL processing
>Affects Versions: 1.3
> Environment: Axis for Java v1.3
> java version "1.5.0_01"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_01-b08)
> Java HotSpot(TM) Client VM (build 1.5.0_01-b08, mixed mode, sharing)
> Windows XP Professional, SP2
>Reporter: Vaduz
>Priority: Blocker
> Attachments: axis-2391.zip
>
>
> WSDL2Java generates wrong source code for the complex type of the following 
> structure:
>   
>   
>maxOccurs="unbounded"/>
>   
>   
>   
>   
> The complex type should be a sequence with only element, which has 
> maxOccurs="unbounded".
> In this case all atributes are ignored and not included to the resulting type.
> Version 1.2 works correctly. Version 1.3 works correctly, if the sequense has 
> includes more than one element.
> The sample WSDL used for test:
> --
> 
>targetNamespace="http://www/bug/DayOfWeek.wsdl";
>   xmlns:tns="http://www/bug/DayOfWeek.wsdl";
>   xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"; 
>   xmlns:xsd="http://www.w3.org/2001/XMLSchema";
>   xmlns="http://schemas.xmlsoap.org/wsdl/";> 
> 
> 
>   
>   
>maxOccurs="unbounded"/>
>   
>   
>   
>   
> 
> 
>   
> 
>   
>   
> 
>   
>   
> 
>   
>   
> 
>   
>   
>transport="http://schemas.xmlsoap.org/soap/http"/>
> 
>   
>   
>namespace="http://www/bug"; 
>   encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
>   
>   
>namespace="http://www/bug";  
> encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
>   
> 
>   
>   
> 
>   Returns the day-of-week name for a given date
> 
> 
>   http://www/dayofweek/DayOfWeek"/>
> 
>   
> 
> --
> For this WSDL Axis 1.2 generates the correct code:
> ...
> public www.bug.DayOfWeek_wsdl.ReplyType getDayOfWeek(java.util.Date date) ...
> ...
> Where reply type includes attributes attr1 and attr2 as well as Item array.
> Axis 1.3 does not generate ReplyType class at all, and declares getDayOfWeek 
> as following:
> public java.lang.String[] getDayOfWeek(java.util.Date date)...
> which is obviosly wrong.
>  

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [Axis2] 1.2-src build fails

[Armin Ehrenfels]

mvn install from the toplevel directory.

Regards

Armin

Deepal Jayasinghe wrote:


Hi Armin,

What is the maven goal did you run ?

Thanks
Deepal

 


Hi list,

the 1.2-src build fails since it tries to access xdocs which isn't
part of the source distribution.
I commented out the lines in
modules/tool/axis2-eclipse-service-plugin/pom.xml and
modules/tool/axis2-eclipse-codegen-plugin/pom.xml which contain
references to xdocs and it succeeded.

Regards

Armin

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



   




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


 




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Commented: (AXIS2-2137) Common invocation using Axis2 client framework

[Hasalaka Waravita (JIRA)]

[ 
https://issues.apache.org/jira/browse/AXIS2-2137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493660
 ] 

Hasalaka Waravita commented on AXIS2-2137:
--

A patch including WSIF provider Axis2 is provided. Somebody need to evaluate it

http://issues.apache.org/jira/browse/WSIF-86?page=all 

> Common invocation using Axis2 client framework
> --
>
> Key: AXIS2-2137
> URL: https://issues.apache.org/jira/browse/AXIS2-2137
> Project: Axis 2.0 (Axis2)
>  Issue Type: Improvement
>  Components: client-api
>Affects Versions: nightly
>Reporter: Hasalaka Waravita
> Attachments: Axis2-Common-Invocation-Framwework.zip
>
>
> This is a patch for Axis2 to use existing client framwork to invoke Web 
> Services using any tranport. It enables Axis2 ServiceClient to invoke non 
> SOAP based WS as well. Please refer Readme.txt 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [Axis2] 1.2-src build fails

[Deepal Jayasinghe]

Hi Armin,

What is the maven goal did you run ?

Thanks
Deepal

> Hi list,
>
> the 1.2-src build fails since it tries to access xdocs which isn't
> part of the source distribution.
> I commented out the lines in
> modules/tool/axis2-eclipse-service-plugin/pom.xml and
> modules/tool/axis2-eclipse-codegen-plugin/pom.xml which contain
> references to xdocs and it succeeded.
>
> Regards
>
> Armin
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[Axis2] 1.2-src build fails

[Armin Ehrenfels]

Hi list,

the 1.2-src build fails since it tries to access xdocs which isn't part 
of the source distribution.
I commented out the lines in 
modules/tool/axis2-eclipse-service-plugin/pom.xml and 
modules/tool/axis2-eclipse-codegen-plugin/pom.xml which contain 
references to xdocs and it succeeded.


Regards

Armin

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Converting a SOAP 1.1 Message Context (with an existing envelope) into SOAP 1.2 MessageContext

[Asankha C. Perera]

Hi

What is the correct way to "convert" an existing SOAP 1.1 message 
context (with a SOAP 1.1 envelope as well) into a SOAP 1.2 message 
context? Do I have to create a new SOAP 1.2 envelope and copy the 
payload from the 1.1.. or is there any other way?


Seems like MessageContext.setIsSOAP11Explicit(false) etc. does not 
convert the existing envelope.. but only the content type of the message 
when serialized, causing "Transport level information does not match 
with SOAP Message namespace URI" error..


thanks
asankha

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [Axis2] Inconsistencies in getting engaged modules

[Davanum Srinivas]

+1 standardize it. +1 to return List containing AxisModules.

thanks,
dims

On 5/4/07, Saminda Abeyruwan <[EMAIL PROTECTED]> wrote:

Hi Devs,

We've came across the following inconsistencies when calling
getEngagedModules() method, in
1. AxisOperation
2. AxisService
3. AxisServiceGroup

AxisOperation has,
public Collection getEngagedModules() {...} --> This will give an instance
of ArrayList which has AxisModule  objects.

AxisService has,
public Collection getEngagedModules() {...} --> This will give an instance
of ArrayList which has String objects.

 String objects are the names of engaged
modules.

AxisServiceGroup has,
public ArrayList getEngagedModules() {...} --> This will give an instance of
ArrayList which has String objects.

 String objects are the names of engaged
modules.

This will lead to difficulties when working with them.

IMHO  getEngagedModules() should be a method an abstract in AxisDescription;

public Collection getEngagedModules()

or

public List getEngagedModules(),

and should return either AxisModule or Name of the module as String. IMHO
AxisModule would be preferable. Thus, others that extend from AxisDecription
will be benefited too.

Please be kind enough to  express your thoughts on  prior.

Thank you

Saminda





--
Saminda Abeyruwan

Software Engineer
WSO2 Inc. - www.wso2.org



--
Davanum Srinivas :: http://davanum.wordpress.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Patches provided for issues AXIS2-2055 and AXIS2-1899

[Davanum Srinivas]

Charitha,

Next time, *please* log the error in the JIRA

thanks,
dims


On 5/4/07, Charitha Kankanamge <[EMAIL PROTECTED]> wrote:

Sathija,
We were testing a Axis2-1.2 build just before releasing 1.2 and found
out that the pojo, pojoguide and pojoguidespring samples did not work at
all. I can't remember the exception and without reporting it through
JIRA I reported it to Deepal for fixing it quickily since we were about
to release Axis2-1.2. Those samples worked fine in all axis2-1.2 release
candidates. Those issues came only in the last build we got on 27th
April. Your patch was the culprit for this error and we did not
encounter any errors in those samples after reverting that patch. We
should be able to reproduce it and report the error if a binary can be
provided with applying that patch again.

Thanks and regards
Charitha


Deepal Jayasinghe wrote:

>Hi Sathija ,
>
>Once I applied your patch , it broke the Axis2 samples. I think Caritha
>will be able to answer this better than me , since he is the one who
>find the bug :)
>
>Thanks
>Deepal
>
>
>
>>Deepal,
>>
>>I had earlier posted a question about the codegen issue you mentioned
>>after patches for AXIS2-2055 were applied.
>>I have since built the codegen module with the patch and didnt notice
>>any issue and nor were there any issues
>>building any of other axis2 modules.
>>So I am still puzzled by what issue the patch may have caused. Would
>>you please elaborate on that issue you mentioned the patch had caused.
>>
>>Also, the issues AXIS2-2055 and AXIS2-1899 are marked as resolved, but
>>they are in fact not, because of the patch reversal.
>>
>>Thanks.
>>Sathija.
>>
>>
>>
>>- Original Message 
>>From: Deepal Jayasinghe <[EMAIL PROTECTED]>
>>To: axis-dev@ws.apache.org
>>Sent: Friday, April 27, 2007 12:10:41 PM
>>Subject: Re: Patches provided for issues AXIS2-2055 and AXIS2-1899
>>
>>Yes , there was an issue with the codegen , so I had to revert that.
>>
>>Thanks
>>Deepal
>>
>>Sathija Pavuluri wrote:
>>
>>
>>
>>>Deepal,
>>>
>>>Noticed that the patches were applied and then reverted on the 1.2
>>>
>>>
>>branch?
>>
>>
>>>Was anything wrong?
>>>
>>>Thanks
>>>Sathija.
>>>
>>>
>>>- Original Message 
>>>From: Deepal Jayasinghe <[EMAIL PROTECTED]>
>>>To: axis-dev@ws.apache.org
>>>Sent: Friday, April 27, 2007 12:16:05 AM
>>>Subject: Re: Patches provided for issues AXIS2-2055 and AXIS2-1899
>>>
>>>Done , thx very much for your patches.
>>>
>>>Thanks
>>>Deepal
>>>
>>>
>>>-
>>>To unsubscribe, e-mail: [EMAIL PROTECTED]
>>>For additional commands, e-mail: [EMAIL PROTECTED]
>>>
>>>
>>>
>>>
>>>Ahhh...imagining that irresistible "new car" smell?
>>>Check out new cars at Yahoo! Autos.
>>>
>>>
>>>
>>
>>
>>
>>
>>--
>>Thanks,
>>Deepal
>>
>>"The highest tower is built one brick at a time"
>>
>>
>>
>>-
>>To unsubscribe, e-mail: [EMAIL PROTECTED]
>>For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>>
>>
>>Ahhh...imagining that irresistible "new car" smell?
>>Check out new cars at Yahoo! Autos.
>>
>>
>>
>
>
>
>
>



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





--
Davanum Srinivas :: http://davanum.wordpress.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (AXIS2-2638) stub sending text/xml instead of application/x-www-form-urlencoded

[Brad (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AXIS2-2638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Brad updated AXIS2-2638:


Affects Version/s: 1.2

Also tested with Axis2-1.2 which gave the same result.

> stub sending text/xml instead of application/x-www-form-urlencoded
> --
>
> Key: AXIS2-2638
> URL: https://issues.apache.org/jira/browse/AXIS2-2638
> Project: Axis 2.0 (Axis2)
>  Issue Type: Bug
>  Components: client-api
>Affects Versions: 1.2, 1.1.1
> Environment: JDK 1.4.2._13
>Reporter: Brad
> Attachments: postcodeAnywhere.wsdl
>
>
> Hi all,
> I've generated client classes from a WSDL doc using the following command 
> line:
> wsdl2java.bat -pn xSoap -o src -d xmlbeans -uri xxx.wsdl
> It all works fine but when I try to invoke the remote service I get
> the following error:
> org.apache.axis2.AxisFault: Transport error 500 . Error Message is
> Request format is invalid: text/xml; charset=UTF-8.
> ;
> Which is fair enough as the server is expecting content type
> "application/x-www-form-urlencoded", as specified in the WSDL:
> 
>
>
> 
>
>
>
>
> 
> Is there any way to over ride the content type? I tried this:
>Options opts = new Options();
>opts.setProperty(Configuration.CONTENT_TYPE,
> HTTPConstants.MEDIA_TYPE_X_WWW_FORM);
>opts.setProperty(HTTPConstants.CHUNKED, Boolean.FALSE);
>client.setOptions(opts);
> I get the same error though. I tried client.setOverrideOptions(opts)
> as well but no change. Using them both causes a StackOverflowError :-)
> Any help greatly appreciated!
> Cheers,
> Brad.
> --
> Brad,
> Could you please log a bug in JIRA and upload your wsdl. Something is
> seriously wrong esp with the StackOverflowError.
> thanks,
> dims

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[Axis2] Inconsistencies in getting engaged modules

[Saminda Abeyruwan]

Hi Devs,

We've came across the following inconsistencies when calling
getEngagedModules() method, in
1. AxisOperation
2. AxisService
3. AxisServiceGroup

AxisOperation has,
public Collection getEngagedModules() {...} --> This will give an instance
of ArrayList which has AxisModule  objects.

AxisService has,
public Collection getEngagedModules() {...} --> This will give an instance
of ArrayList which has String objects.

String objects are the names of engaged modules.

AxisServiceGroup has,
public ArrayList getEngagedModules() {...} --> This will give an instance of
ArrayList which has String objects.

String objects are the names of engaged modules.

This will lead to difficulties when working with them.

IMHO  getEngagedModules() should be a method an abstract in AxisDescription;


public Collection getEngagedModules()

or

public List getEngagedModules(),

and should return either AxisModule or Name of the module as String. IMHO
AxisModule would be preferable. Thus, others that extend from AxisDecription
will be benefited too.

Please be kind enough to  express your thoughts on  prior.

Thank you

Saminda





--
Saminda Abeyruwan

Software Engineer
WSO2 Inc. - www.wso2.org

[jira] Created: (AXIS2-2639) maven dist-doc results tools documents images distroted.

[Lahiru Sandakith (JIRA)]

maven dist-doc results tools documents images distroted.


 Key: AXIS2-2639
 URL: https://issues.apache.org/jira/browse/AXIS2-2639
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: samples, build,site
Affects Versions: 1.2
 Environment: maven 1.0.2
Reporter: Lahiru Sandakith


Invoking maven dist-doc results the images linked from tools documents 
corrupted. 
Since most of the files were png images, simply excluding it from the document 
filter and copying back again with out the filter did not resolve the problem. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Resolved: (AXIS2-2637) Updated the index.html file

[Chatra Nakkawita (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AXIS2-2637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chatra Nakkawita resolved AXIS2-2637.
-

Resolution: Fixed

Reviewed and committed. This patch makes the index.html inline with the release 
note of axis1.2

Thanks Marietta,

Chatra

> Updated the index.html file
> ---
>
> Key: AXIS2-2637
> URL: https://issues.apache.org/jira/browse/AXIS2-2637
> Project: Axis 2.0 (Axis2)
>  Issue Type: Bug
>  Components: documentation
>Affects Versions: 1.2
> Environment: Windows XP
>Reporter: Marietta Lovendhal
>Priority: Minor
> Attachments: index.patch
>
>
> Updated the index.html file according to the release note.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (AXIS2-2468) Handling of names with '-' symbol

[Jose Antonio (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AXIS2-2468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jose Antonio updated AXIS2-2468:


Attachment: oasis-200401-wss-wssecurity-utility-1.0.xsd

Also required to generate code

> Handling of names with '-' symbol
> -
>
> Key: AXIS2-2468
> URL: https://issues.apache.org/jira/browse/AXIS2-2468
> Project: Axis 2.0 (Axis2)
>  Issue Type: Bug
>  Components: codegen
>Affects Versions: 1.2
> Environment: Ubuntu 6.10, Jdk 1.4.2
>Reporter: Jose Antonio
> Attachments: oasis-200401-wss-wssecurity-utility-1.0.xsd, 
> reference-1.1.xsd, wsctx.wsdl, wsctx.xsd
>
>
> I have a schema with an attribute named 'reference-scheme' and I need to use 
> it in my code. When I try to generate code using ADB I get the following:
> ..
>  // handle attribute "reference-scheme"
> java.lang.String tempAttribreference-scheme =
>   reader.getAttributeValue("","reference-scheme");
>if (tempAttribreference-scheme!=null){
>  java.lang.String content = 
> tempAttribreference-scheme;
> 
>  object.setReferenceScheme(
> 
> org.apache.axis2.databinding.utils.ConverterUtil.convertToAnyURI(tempAttribreference-scheme));
> 
> } else {
>
> }
> handledAttributes.add("reference-scheme");
> 
> 
> reader.next();
> .
> And that doesn't compile, so when an attribute or element name contains a '-' 
> character, the generated variables should replace it by _ so it generates the 
> following code:
> ..
>  // handle attribute "reference-scheme"
> java.lang.String tempAttribreference_scheme =
>   reader.getAttributeValue("","reference-scheme");
>if (tempAttribreference_scheme!=null){
>  java.lang.String content = 
> tempAttribreference_scheme;
> 
>  object.setReferenceScheme(
> 
> org.apache.axis2.databinding.utils.ConverterUtil.convertToAnyURI(tempAttribreference_scheme));
> 
> } else {
>
> }
> handledAttributes.add("reference-scheme");
> 
> 
> reader.next();
> .
> That compiles or something similar.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (AXIS2-2468) Handling of names with '-' symbol

[Jose Antonio (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AXIS2-2468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jose Antonio updated AXIS2-2468:


Attachment: wsctx.xsd

Required schema

> Handling of names with '-' symbol
> -
>
> Key: AXIS2-2468
> URL: https://issues.apache.org/jira/browse/AXIS2-2468
> Project: Axis 2.0 (Axis2)
>  Issue Type: Bug
>  Components: codegen
>Affects Versions: 1.2
> Environment: Ubuntu 6.10, Jdk 1.4.2
>Reporter: Jose Antonio
> Attachments: reference-1.1.xsd, wsctx.wsdl, wsctx.xsd
>
>
> I have a schema with an attribute named 'reference-scheme' and I need to use 
> it in my code. When I try to generate code using ADB I get the following:
> ..
>  // handle attribute "reference-scheme"
> java.lang.String tempAttribreference-scheme =
>   reader.getAttributeValue("","reference-scheme");
>if (tempAttribreference-scheme!=null){
>  java.lang.String content = 
> tempAttribreference-scheme;
> 
>  object.setReferenceScheme(
> 
> org.apache.axis2.databinding.utils.ConverterUtil.convertToAnyURI(tempAttribreference-scheme));
> 
> } else {
>
> }
> handledAttributes.add("reference-scheme");
> 
> 
> reader.next();
> .
> And that doesn't compile, so when an attribute or element name contains a '-' 
> character, the generated variables should replace it by _ so it generates the 
> following code:
> ..
>  // handle attribute "reference-scheme"
> java.lang.String tempAttribreference_scheme =
>   reader.getAttributeValue("","reference-scheme");
>if (tempAttribreference_scheme!=null){
>  java.lang.String content = 
> tempAttribreference_scheme;
> 
>  object.setReferenceScheme(
> 
> org.apache.axis2.databinding.utils.ConverterUtil.convertToAnyURI(tempAttribreference_scheme));
> 
> } else {
>
> }
> handledAttributes.add("reference-scheme");
> 
> 
> reader.next();
> .
> That compiles or something similar.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (AXIS2-2468) Handling of names with '-' symbol

[Jose Antonio (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AXIS2-2468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jose Antonio updated AXIS2-2468:


Attachment: wsctx.wsdl

Wsdl file

> Handling of names with '-' symbol
> -
>
> Key: AXIS2-2468
> URL: https://issues.apache.org/jira/browse/AXIS2-2468
> Project: Axis 2.0 (Axis2)
>  Issue Type: Bug
>  Components: codegen
>Affects Versions: 1.2
> Environment: Ubuntu 6.10, Jdk 1.4.2
>Reporter: Jose Antonio
> Attachments: reference-1.1.xsd, wsctx.wsdl, wsctx.xsd
>
>
> I have a schema with an attribute named 'reference-scheme' and I need to use 
> it in my code. When I try to generate code using ADB I get the following:
> ..
>  // handle attribute "reference-scheme"
> java.lang.String tempAttribreference-scheme =
>   reader.getAttributeValue("","reference-scheme");
>if (tempAttribreference-scheme!=null){
>  java.lang.String content = 
> tempAttribreference-scheme;
> 
>  object.setReferenceScheme(
> 
> org.apache.axis2.databinding.utils.ConverterUtil.convertToAnyURI(tempAttribreference-scheme));
> 
> } else {
>
> }
> handledAttributes.add("reference-scheme");
> 
> 
> reader.next();
> .
> And that doesn't compile, so when an attribute or element name contains a '-' 
> character, the generated variables should replace it by _ so it generates the 
> following code:
> ..
>  // handle attribute "reference-scheme"
> java.lang.String tempAttribreference_scheme =
>   reader.getAttributeValue("","reference-scheme");
>if (tempAttribreference_scheme!=null){
>  java.lang.String content = 
> tempAttribreference_scheme;
> 
>  object.setReferenceScheme(
> 
> org.apache.axis2.databinding.utils.ConverterUtil.convertToAnyURI(tempAttribreference_scheme));
> 
> } else {
>
> }
> handledAttributes.add("reference-scheme");
> 
> 
> reader.next();
> .
> That compiles or something similar.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (AXIS2-2468) Handling of names with '-' symbol

[Jose Antonio (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AXIS2-2468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jose Antonio updated AXIS2-2468:


Attachment: reference-1.1.xsd

The file causing problems

> Handling of names with '-' symbol
> -
>
> Key: AXIS2-2468
> URL: https://issues.apache.org/jira/browse/AXIS2-2468
> Project: Axis 2.0 (Axis2)
>  Issue Type: Bug
>  Components: codegen
>Affects Versions: 1.2
> Environment: Ubuntu 6.10, Jdk 1.4.2
>Reporter: Jose Antonio
> Attachments: reference-1.1.xsd, wsctx.wsdl, wsctx.xsd
>
>
> I have a schema with an attribute named 'reference-scheme' and I need to use 
> it in my code. When I try to generate code using ADB I get the following:
> ..
>  // handle attribute "reference-scheme"
> java.lang.String tempAttribreference-scheme =
>   reader.getAttributeValue("","reference-scheme");
>if (tempAttribreference-scheme!=null){
>  java.lang.String content = 
> tempAttribreference-scheme;
> 
>  object.setReferenceScheme(
> 
> org.apache.axis2.databinding.utils.ConverterUtil.convertToAnyURI(tempAttribreference-scheme));
> 
> } else {
>
> }
> handledAttributes.add("reference-scheme");
> 
> 
> reader.next();
> .
> And that doesn't compile, so when an attribute or element name contains a '-' 
> character, the generated variables should replace it by _ so it generates the 
> following code:
> ..
>  // handle attribute "reference-scheme"
> java.lang.String tempAttribreference_scheme =
>   reader.getAttributeValue("","reference-scheme");
>if (tempAttribreference_scheme!=null){
>  java.lang.String content = 
> tempAttribreference_scheme;
> 
>  object.setReferenceScheme(
> 
> org.apache.axis2.databinding.utils.ConverterUtil.convertToAnyURI(tempAttribreference_scheme));
> 
> } else {
>
> }
> handledAttributes.add("reference-scheme");
> 
> 
> reader.next();
> .
> That compiles or something similar.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: AxisOperation needs an getMessages() method

[Deepal Jayasinghe]

Hi Saminda

+1

Thanks
Deepal

> Hi All,
>
> We could get the AxisMessage from the given AxisOperation using the
> AxisOperation.getMessage(String label); In order to get the
> AxisMessage we should know the MEP before hand and should know the
> value of the label. IMHO there is no way to get the AxisMessages from
> a given AxisOperation.  Shall we introduce a  method,
>
> *public AxisMessage[] getMessages()* to AxisOperation to the
> AxisMessages from AxisOperation.
>
> Thank you
>
> Saminda 
>
> -- 
> Saminda Abeyruwan
>
> Software Engineer
> WSO2 Inc. - www.wso2.org 



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[Axis2] AxisOperation needs an getMessages() method

[Charitha Kankanamge]

Forwarding with axis2 prefix
--- Begin Message ---

Hi All,

We could get the AxisMessage from the given AxisOperation using the
AxisOperation.getMessage(String label); In order to get the AxisMessage we
should know the MEP before hand and should know the value of the label. IMHO
there is no way to get the AxisMessages from a given AxisOperation.  Shall
we introduce a  method,

*public AxisMessage[] getMessages()* to AxisOperation to the AxisMessages
from AxisOperation.

Thank you

Saminda

--
Saminda Abeyruwan

Software Engineer
WSO2 Inc. - www.wso2.org
--- End Message ---
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (AXIS2-2638) stub sending text/xml instead of application/x-www-form-urlencoded

[Brad (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AXIS2-2638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Brad updated AXIS2-2638:


Attachment: postcodeAnywhere.wsdl

The WSDL for the service I'm trying to call.

> stub sending text/xml instead of application/x-www-form-urlencoded
> --
>
> Key: AXIS2-2638
> URL: https://issues.apache.org/jira/browse/AXIS2-2638
> Project: Axis 2.0 (Axis2)
>  Issue Type: Bug
>  Components: client-api
>Affects Versions: 1.1.1
> Environment: JDK 1.4.2._13
>Reporter: Brad
> Attachments: postcodeAnywhere.wsdl
>
>
> Hi all,
> I've generated client classes from a WSDL doc using the following command 
> line:
> wsdl2java.bat -pn xSoap -o src -d xmlbeans -uri xxx.wsdl
> It all works fine but when I try to invoke the remote service I get
> the following error:
> org.apache.axis2.AxisFault: Transport error 500 . Error Message is
> Request format is invalid: text/xml; charset=UTF-8.
> ;
> Which is fair enough as the server is expecting content type
> "application/x-www-form-urlencoded", as specified in the WSDL:
> 
>
>
> 
>
>
>
>
> 
> Is there any way to over ride the content type? I tried this:
>Options opts = new Options();
>opts.setProperty(Configuration.CONTENT_TYPE,
> HTTPConstants.MEDIA_TYPE_X_WWW_FORM);
>opts.setProperty(HTTPConstants.CHUNKED, Boolean.FALSE);
>client.setOptions(opts);
> I get the same error though. I tried client.setOverrideOptions(opts)
> as well but no change. Using them both causes a StackOverflowError :-)
> Any help greatly appreciated!
> Cheers,
> Brad.
> --
> Brad,
> Could you please log a bug in JIRA and upload your wsdl. Something is
> seriously wrong esp with the StackOverflowError.
> thanks,
> dims

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[Axis2] ServiceClient exception. was Re: [axis2] ContextFactory - get rid of it?

[Paul Fremantle]

Smitha

Could you please post the exception trace?

Paul

On 5/4/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:


Hi

  I am trying to create a ServiceClient by ServiceClient = new
ServiceClient().But I am getting a runtimeException there and could not
proceed from there.Do you have any idea how can I come out of that?

Thanks And Regards
Smitha Aldrin

-Original Message-
From: Deepal Jayasinghe [mailto:[EMAIL PROTECTED]
Sent: Friday, May 04, 2007 3:21 AM
To: axis-dev@ws.apache.org
Subject: Re: [axis2] ContextFactory - get rid of it?


> Hm... and yet that doesn't seem to happen, because everything right
> now uses ContextFactory directly, and I don't see any hooks in there
> for supporting notifications, just a bunch of static methods.  ?
>
> I'll go read those threads (thanks for the pointers), but I think
> there are perhaps better ways to achieve the goals than a static
> factory class, depending on exactly what the requirements are.  For
> example:

So let's go for those.


Thanks
Deepal


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



The information contained in this electronic message and any attachments to 
this message are intended for the exclusive use of the addressee(s) and may 
contain proprietary, confidential or privileged information. If you are not the 
intended recipient, you should not disseminate, distribute or copy this e-mail. 
Please notify the sender immediately and destroy all copies of this message and 
any attachments.

WARNING: Computer viruses can be transmitted via email. The recipient should 
check this email and any attachments for the presence of viruses. The company 
accepts no liability for any damage caused by any virus transmitted by this 
email.

www.wipro.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





--
Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair

http://bloglines.com/blog/paulfremantle
[EMAIL PROTECTED]

"Oxygenating the Web Service Platform", www.wso2.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Created: (AXIS2-2638) stub sending text/xml instead of application/x-www-form-urlencoded

[Brad (JIRA)]

stub sending text/xml instead of application/x-www-form-urlencoded
--

 Key: AXIS2-2638
 URL: https://issues.apache.org/jira/browse/AXIS2-2638
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: client-api
Affects Versions: 1.1.1
 Environment: JDK 1.4.2._13
Reporter: Brad


Hi all,

I've generated client classes from a WSDL doc using the following command line:

wsdl2java.bat -pn xSoap -o src -d xmlbeans -uri xxx.wsdl

It all works fine but when I try to invoke the remote service I get
the following error:

org.apache.axis2.AxisFault: Transport error 500 . Error Message is
Request format is invalid: text/xml; charset=UTF-8.
;

Which is fair enough as the server is expecting content type
"application/x-www-form-urlencoded", as specified in the WSDL:


   
   

   
   
   
   


Is there any way to over ride the content type? I tried this:

   Options opts = new Options();
   opts.setProperty(Configuration.CONTENT_TYPE,
HTTPConstants.MEDIA_TYPE_X_WWW_FORM);
   opts.setProperty(HTTPConstants.CHUNKED, Boolean.FALSE);
   client.setOptions(opts);

I get the same error though. I tried client.setOverrideOptions(opts)
as well but no change. Using them both causes a StackOverflowError :-)

Any help greatly appreciated!

Cheers,
Brad.

--


Brad,

Could you please log a bug in JIRA and upload your wsdl. Something is
seriously wrong esp with the StackOverflowError.

thanks,
dims

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

AxisOperation needs an getMessages() method

[Saminda Abeyruwan]

Hi All,

We could get the AxisMessage from the given AxisOperation using the
AxisOperation.getMessage(String label); In order to get the AxisMessage we
should know the MEP before hand and should know the value of the label. IMHO
there is no way to get the AxisMessages from a given AxisOperation.  Shall
we introduce a  method,

*public AxisMessage[] getMessages()* to AxisOperation to the AxisMessages
from AxisOperation.

Thank you

Saminda

--
Saminda Abeyruwan

Software Engineer
WSO2 Inc. - www.wso2.org

[jira] Resolved: (AXIS2-2565) Documentation cleanup of ADB how-to pages

[Chatra Nakkawita (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AXIS2-2565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chatra Nakkawita resolved AXIS2-2565.
-

   Resolution: Fixed
Fix Version/s: (was: nightly)
   1.2

Great work. Your patches are most welcome. Reviewed and committed changes in 
attached patch to Axis2 1.2 branch. Changes will be merged to the trunk. Also 
updated 1.2 pages in this site

Thanks,
Chatra

> Documentation cleanup of ADB how-to pages
> -
>
> Key: AXIS2-2565
> URL: https://issues.apache.org/jira/browse/AXIS2-2565
> Project: Axis 2.0 (Axis2)
>  Issue Type: Improvement
>  Components: documentation
>Affects Versions: nightly
>Reporter: Glen Mazza
> Assigned To: Chatra Nakkawita
>Priority: Minor
> Fix For: 1.2
>
> Attachments: adbpatch.txt
>
>
> While studying the four ADB docs I made a note of and fixed typos, 
> grammatical nitpicks, etc.  Patch is attached.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]