Re: More than one service name in a SINGLE WSDL file
The current Axis2 version still hasn't fixed this issue. This is not a problem in Axis1.4 version. There's a bug re-opened to address this problem in Axis2. I don't know when or if it will ever get fixed --- hopefully yes ??? Patrick Cook <[EMAIL PROTECTED]> wrote: First and foremost, I would like to take my hats off to Axis2 community. You all have definately raised the standards for SOAP Engines, Web Services and SOA in general. I would like to help out but don't know how. Please send me some information on how I could get involved. Secondly, I have a few questions. 1. How does Axis2 generate the ?wsdl for multiple services in a SINGLE WSDL file 2. Is there a one to one mapping of the service name in the service.xml file when there is a wsdl file in the META-INF folder 3. What is the connection of the service.xml and the *.wsdl file located in the META-INF folder How does Axis2 1.2 handle Multiple Services in a SINGLE WSDL file. i.e. if the wsdl looks something like the wsdl below. The behavior that I am seeing is that when you ask for the wsdl via (?wsdl) the SOAP engine will correctly generate the wsdl for one service but NOT the other. Service Example http://localhost:8080/services/MyService1/> Service Example http://localhost:8080/services/MyService2/> And my service.xml file would look something like this Example of Multiple Services within one wsdl example.multiple.services.test.MyServcice1 http://www.w3.org/2004/08/wsdl/in-out " class="example.multiple.receivers.MyCustomMessageReceiver "/> Example of Multiple Services within one wsdl example.multiple.services.test.MyServcice2 http://www.w3.org/2004/08/wsdl/in-out " class="example.multiple.receivers.MyCustomMessageReceiver "/> By the way, I am using the original wsdl file in the META-INF folder. all of the corresponding schemas and source class files are in the correct location. -Patrick - Luggage? GPS? Comic books? Check out fitting gifts for grads at Yahoo! Search.
[Axis2] Temporary files/ Stress testing with Axis2 1.2 [SEC=UNCLASSIFIED]
Hello, Our team is currently using Axis2 1.2 in our application and we are running some performance and stress tests with JMeter. While running these stress tests we have come across two issues that we hope someone can help us with. The first issue relates to temporary files. In our stress testing we were using the URLBasedAxisConfigurator to load .mar files on the client side, but got the error below with 1 user and 1000 iterations: java.lang.RuntimeException: java.io.IOException: Too many open files;; at org.apache.axis2.deployment.util.Utils.getURLsForAllJars(Utils.java(Compiled Code));; at org.apache.axis2.deployment.util.Utils.createClassLoader(Utils.java:684);; at au.gov.centrelink.jfs.proxy.axis2.ClientURLBasedAxisConfigurator.loadRepositoryFromURL(ClientURLBasedAxisConfigurator.java(Compiled Code));; at org.apache.axis2.deployment.URLBasedAxisConfigurator.getAxisConfiguration(URLBasedAxisConfigurator.java:72);; at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:60);; at au.gov.centrelink.jfs.proxy.ProxyFactory.createStub(ProxyFactory.java:699);; at au.gov.centrelink.jfs.proxy.ProxyFactory.createProxy(ProxyFactory.java:440);; at au.gov.centrelink.jfs.proxy.ProxyFactory.createProxy(ProxyFactory.java:395);; at au.gov.centrelink.jsf.pst.core.CDCCustomerEmailAddressTester2.execute(CDCCustomerEmailAddressTester2.java:64);; at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:421);; at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:226);; at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1164);; at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:415);; at javax.servlet.http.HttpServlet.service(HttpServlet.java:763);; at javax.servlet.http.HttpServlet.service(HttpServlet.java:856);; at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1572);; at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1521);; at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:113);; at com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:82);; at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:759);; at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:334);; at org.apache.struts.action.RequestProcessor.doForward(RequestProcessor.java:1056);; at org.apache.struts.action.RequestProcessor.processForwardConfig(RequestProcessor.java:388);; at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:231);; at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1164);; at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:415);; at javax.servlet.http.HttpServlet.service(HttpServlet.java:763);; at javax.servlet.http.HttpServlet.service(HttpServlet.java:856);; at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1572);; at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1521);; at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:136);; at au.gov.centrelink.itsecurity.acs.web.SecureRequestFilter.doFilter(SecureRequestFilter.java:60);; at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:142);; at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:121);; at au.gov.centrelink.jaf.liser.api.WebRequestLiser.doFilter(WebRequestLiser.java:267);; at au.gov.centrelink.jaf.interceptor.core.JAFFilter.doFilter(JAFFilter.java:99);; at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:142);; at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:121);; at com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:82);; at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:759);; at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java:89);; at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:1924);; at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:98);; at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:472);; at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:411);; at com.ibm.ws.http.channel.inbou
Axis2 JMS Transport to WebSphere MQ
Hi, for the project I'm on currently, I have to use an Axis2 JMS transport running on Tomcat with WebSphere MQ as the queue provider. Not having used WebSphere MQ I'm not sure how to configure this, and the JMS example on the Axis2 site is for ActiveMQ. I couldn't find any articles using google that might help either. Can anyone point me to an example of configuring axis2 to use WebSphere MQ - in particular what the settings I should use in my axis2.xml file for transportReceiver? The main thing I'm not sure about is the JNDI setup in the connection factory - since I don't have a J2EE server (Tomcat is the app server) do I need to use a filesystem context? What are the settings I should use? thanks, Anthony. -- Anthony - Anthony Bull Senior Developer Black Coffee Software Ltd PO Box 10-192 The Terrace Wellington, New Zealand [EMAIL PROTECTED] Ph +64 4 472 8818 Fax +64 4 472 8811 Mobile 021 303 692 - www.bcsoft.co.nz --- This email may contain confidential or privileged information, and is intended for use only by the addressee, or addressees. If you are not the intended recipient please advise the sender immediately and do not copy, use or disclose the contents to any other person or organisation. Black Coffee Software Ltd accepts no responsibility for viruses received with this email, or to any changes made to the original content. Any views or opinions expressed in this email may be personal to the sender and are not necessarily those of Black Coffee Software Ltd. --- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Soap fault and ADB -- How to set the fault code
Hi, I have a wsdl operation which throws fault of type "MyFault". (i.e) For this scenario ADB generates the following classes a) MyFaultException b) MyFault derived from ADBbean c) MyFaultType Class MyFault has MyFaultType as instance variable. Exception MyFault goes as detail in SOAPFault which is fine. Now I don't understand how to set faultCode and faultString. I believe ADB should inherit the class MyFaultException from AxisFault instead of Exception? Can some one please let me know how to set the faultCode and faultString? Thanks, Haneef -Original Message- From: Ali, Haneef Sent: Monday, June 11, 2007 8:44 PM To: axis-user@ws.apache.org Subject: RE: SOAP fault - custom detail namespace Thanks for the response. I do have the element and wsdl declaration. I believe in this case Axis2 works as expected, and looks like Axis1.4 has a bug. 1) Axis 2 desterilizes the elements only if the qName of the xmlFragment matches. 1) Axis 1.4 tries to look for Qname. If it can't find Qname then it looks for localName. If it finds localName then it desterilizes the request, which I think is wrong Can you please confirm whether this is a feature or bug in Axis 1.4? I debugged the code and found that the following file is accepting the fields even if they are not in the proper namespace. Method : BeanDeSerializer.onStartChild Line : 216 The code is trying to get "BeanPropertyDescriptor" based on Qname. If it can't find then it tries to find the "BeanPropertyDescriptor" using localname, which is causing the problem. (i.e) if you have xmlFragment where only "localName" matches, then it desterilizes the bean which I think is wrong Thanks, Haneef -Original Message- From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] Sent: Monday, June 11, 2007 3:19 PM To: axis-user@ws.apache.org Subject: Re: SOAP fault - custom detail namespace Based on your schema, the fault message should look like this: env:Server Some message http://MyNamespace";> Also, please verify that you have in fact defined an *element*. (The schema fragment you showed us only defines a complex type.) Make sure that this declaration is included in your schema: And make sure your WSDL fault message part references this element. Anne On 6/11/07, Ali, Haneef <[EMAIL PROTECTED]> wrote: > Hi, > > I have the following complex Element > > attributeFormDefault="qualified" > targetNamespace="http://MyNamespace";> > > > > > > > > > > > I have omitted unnecessary implementation details. Bascially my > weblogic webservice throws this excecption and the xml in the wire > look like > > > > env:Server > Some message > > http://MyNamespace";> > > > > > > > > This xml fragment is accepted by both Axis 1.4 client and weblogic > client. Axis 2.0 rejects this. Axis 2.0 is not able to findout the > namespace for the element "mesg1' and "mesg2". > > Can you please let me know who is correct? I believe Axis2.0 is > correct > > > Thanks, > Haneef > > > > > - > 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] Please VOTE for your favorite bug to be fixed.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Michele Mazzucco wrote: > Eran, > > your point is "let's add new, cool features", my point is "let's build > something reliable". I think you didn't get my point. " ..there are significant improvements over the last release .." doesn't mean they are not only new cool features. Fault handling was not working properly in the last release and we fixed it. If you really looked at what we did during the hackathon then you know how we improved it and how significant was it. That is what I meant. I am sorry if my interpretation of "significant improvements" is wrong coz I know and agree my English is not that good :) I do agree with you that we need a reliable Axis2, but that doesn't mean we need to keep on postponing releases "until" we fix everything. Ok, let's say we postpone the release. How can you help fixing some blockers to make it more reliable? What is the plan you have? Just asking to postpone thinking "some one" will fix blockers and "some day" we will get a more stable one is nothing more than following a mirage for me. Thanks, Chinthaka -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGiCoCjON2uBzUhh8RAgg2AJ9nuKj1XGyTL95b6r/RT9RvK7eaNgCgmuxL +ZibYf5NirmRu0x5uIlw18c= =cqzr -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: HTTP Status 500 from http://127.0.0.1:8080/axis2-web/
Hi Jon-
1st) do you'll have jsp-api.jar if so which version?
my jsp-api.jar has a date timestamp of 04/14/2006 and is 50,501 and is located
in %CATALINA_HOME%\common\lib
2nd) please provide the wsdl
Thanks
Martin
This email message and any files transmitted with it contain confidential
information intended only for the person(s) to whom this email message is
addressed. If you have received this email message in error, please notify
the sender immediately by telephone or email and destroy the original
message without making a copy. Thank you.
- Original Message -
From: Willard
To: axis-user@ws.apache.org
Sent: Sunday, July 01, 2007 12:29 PM
Subject: Re: HTTP Status 500 from http://127.0.0.1:8080/axis2-web/
Hi Martin,
Sorry for my confusion but jetspeed appears to be a portal ... I am trying
to use Axis / WebService with Tomcat 6. Can you clarify for me? I apologize
for being such a newbie ... Alos, jetspeed says it is compatible with
a.. Tomcat 5.0.x
b.. Tomcat 5.5.x
but I have Tomcat6
Best,
Jon
Martin Gainty wrote:
Good Evening Willard
please verify your jsp-api.jar is fairly recent (I was able to d/l from
jetspeed2.1 site)
http://portals.apache.org/jetspeed-2/download.html
04/14/2006 02:09 PM50,501 jsp-api.jar
If you can attach the WSDL I'll try to re-produce that error here...
HTH
M--
This email message and any files transmitted with it contain confidential
information intended only for the person(s) to whom this email message is
addressed. If you have received this email message in error, please notify
the sender immediately by telephone or email and destroy the original
message without making a copy. Thank you.
- Original Message -
From: Willard
To: axis-user@ws.apache.org
Sent: Saturday, June 30, 2007 6:15 PM
Subject: Re: HTTP Status 500 from http://127.0.0.1:8080/axis2-web/
Thanks Martin,
I have tomcat 6.0.1.3 and I do not have a common/lib, just a /lib under
tomcat. I added my C:\Tomcat6\lib\jsp-api.jar to my classpath, rebooted,
verified and it still does not work. Do you know if tomcat6.0 uses the Windows
env var for CLASSPATH? I rebooted because tomcat is running as a service and I
know that there are issues with SCM picking up env changes.
Any other ideas?
Best,
Jon
Martin Gainty wrote:
known bug
add
"$TOMCAT_HOME\common\lib\jsp-api.jar"
to classpath
http://mail-archives.apache.org/mod_mbox/ws-axis-user/200704.mbox/[EMAIL
PROTECTED]
HTH
M--
This email message and any files transmitted with it contain
confidential
information intended only for the person(s) to whom this email message
is
addressed. If you have received this email message in error, please
notify
the sender immediately by telephone or email and destroy the original
message without making a copy. Thank you.
- Original Message -
From: Willard
To: axis-user@ws.apache.org
Sent: Saturday, June 30, 2007 4:02 PM
Subject: HTTP Status 500 from http://127.0.0.1:8080/axis2-web/
New to axis ...
Trying to access http://127.0.0.1:8080/axis2-web/ while running
Tomcat6.0.1.3. I have placed the Axis2 war in the tomcat webapps as specified.
The tomcat Manager page is fine. Any ideas?
type Exception report
message
description The server encountered an internal error () that
prevented it from fulfilling this request.
exception
org.apache.jasper.JasperException: Unable to compile class for JSP:
An error occurred at line: 6 in the generated java file
Only a type can be imported. org.apache.axis2.Constants resolves to a package
An error occurred at line: 7 in the generated java file
Only a type can be imported. org.apache.axis2.context.ConfigurationContext
resolves to a package
An error occurred at line: 8 in the generated java file
Only a type can be imported. org.apache.axis2.description.Parameter resolves to
a package
An error occurred at line: 9 in the generated java file
Only a type can be imported. org.apache.axis2.transport.http.AxisServlet
resolves to a package
An error occurred at line: 12 in the jsp file: /include/httpbase.jsp
ConfigurationContext cannot be resolved to a type
9:
10: public void jspInit() {
11: ServletContext context = this.getServletConfig().getServletContext();
12: ConfigurationContext configctx = (ConfigurationContext)
context.getAttribute(AxisServlet.CONFIGURATION_CONTEXT);
13: Parameter parameter =
configctx.getAxisConfiguration().getParameter(Constants.HTTP_FRONTEND_HOST_URL);
14: if (parameter != null) {
15: frontendHostUrl = (String) parameter.getValue();
An error occurred at line: 12 in the jsp file: /include/httpba
Re: HTTP Status 500 from http://127.0.0.1:8080/axis2-web/
Hi Martin,
Sorry for my confusion but jetspeed appears to be a portal ... I am
trying to use Axis / WebService with Tomcat 6. Can you clarify for
me? I apologize for being such a newbie ... Alos, jetspeed says it is
compatible with
Tomcat 5.0.x
Tomcat 5.5.x
but I have Tomcat6
Best,
Jon
Martin Gainty wrote:
Good Evening Willard
please verify your jsp-api.jar is
fairly recent (I was able to d/l from jetspeed2.1 site)
http://portals.apache.org/jetspeed-2/download.html
04/14/2006 02:09 PM
50,501 jsp-api.jar
If you can attach the WSDL I'll try
to re-produce that error here...
HTH
M--
This email message and any files transmitted with it contain
confidential
information intended only for the person(s) to whom this email message
is
addressed. If you have received this email message in error, please
notify
the sender immediately by telephone or email and destroy the original
message without making a copy. Thank you.
-
Original Message -
From:
Willard
To:
axis-user@ws.apache.org
Sent:
Saturday, June 30, 2007 6:15 PM
Subject:
Re: HTTP Status 500 from http://127.0.0.1:8080/axis2-web/
Thanks Martin,
I have tomcat 6.0.1.3 and I do not have a common/lib, just a /lib under
tomcat. I added my C:\Tomcat6\lib\jsp-api.jar to my classpath,
rebooted, verified and it still does not work. Do you know if
tomcat6.0 uses the Windows env var for CLASSPATH? I rebooted because
tomcat is running as a service and I know that there are issues with
SCM picking up env changes.
Any other ideas?
Best,
Jon
Martin Gainty wrote:
known bug
add
"$TOMCAT_HOME\common\lib\jsp-api.jar"
to classpath
http://mail-archives.apache.org/mod_mbox/ws-axis-user/200704.mbox/[EMAIL PROTECTED]
HTH
M--
This email message and any files transmitted with it contain
confidential
information intended only for the person(s) to whom this email message
is
addressed. If you have received this email message in error, please
notify
the sender immediately by telephone or email and destroy the original
message without making a copy. Thank you.
-
Original Message -
From:
Willard
To:
axis-user@ws.apache.org
Sent:
Saturday, June 30, 2007 4:02 PM
Subject:
HTTP Status 500 from http://127.0.0.1:8080/axis2-web/
New to axis ...
Trying to access http://127.0.0.1:8080/axis2-web/
while running Tomcat6.0.1.3. I have placed the Axis2 war in the tomcat
webapps as specified. The tomcat Manager page is fine. Any ideas?
type Exception report
message
description The server encountered an internal
error () that prevented it from fulfilling this request.
exception
org.apache.jasper.JasperException: Unable to compile class for JSP:
An error occurred at line: 6 in the generated java file
Only a type can be imported. org.apache.axis2.Constants resolves to a package
An error occurred at line: 7 in the generated java file
Only a type can be imported. org.apache.axis2.context.ConfigurationContext resolves to a package
An error occurred at line: 8 in the generated java file
Only a type can be imported. org.apache.axis2.description.Parameter resolves to a package
An error occurred at line: 9 in the generated java file
Only a type can be imported. org.apache.axis2.transport.http.AxisServlet resolves to a package
An error occurred at line: 12 in the jsp file: /include/httpbase.jsp
ConfigurationContext cannot be resolved to a type
9:
10: public void jspInit() {
11: ServletContext context = this.getServletConfig().getServletContext();
12: ConfigurationContext configctx = (ConfigurationContext) context.getAttribute(AxisServlet.CONFIGURATION_CONTEXT);
13: Parameter parameter = configctx.getAxisConfiguration().getParameter(Constants.HTTP_FRONTEND_HOST_URL);
14: if (parameter != null) {
15: frontendHostUrl = (String) parameter.getValue();
An error occurred at line: 12 in the jsp file: /include/httpbase.jsp
ConfigurationContext cannot be resolved to a type
9:
10: public void jspInit() {
11: ServletContext context = this.getServletConfig().getServletContext();
12: ConfigurationContext configctx = (ConfigurationContext) context.getAttribute(AxisServlet.CONFIGURATION_CONTEXT);
13: Parameter parameter = configctx.getAxisConfiguration().getParameter(Constants.HTTP_FRONTEND_HOST_URL);
14: if (parameter != null) {
15: frontendHostUrl = (String) parameter.getValue();
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EM
Re: [Axis2] Please VOTE for your favorite bug to be fixed.
Michele, from prev experience it takes us at least 2-3 RC's and then final. There is no way we can get thru all that in a couple of days. do you? :) -- dims On 7/1/07, Michele Mazzucco <[EMAIL PROTECTED]> wrote: Dims, I disagree with what Eran says, which is "we have a deadline, so probably not all bugs will be fixed for the next release". I think people would be much more happy to wait 1 or 2 weeks more to have a more reliable release than having an unstable one now. Simply lowering bug priorities from blockers to critical (or other) doesn't mean the tool is bug free (this is what I understand from previous emails). And, of course, adding new features will probably mean adding new bugs as well. Michele On 1 Jul 2007, at 13:09, Davanum Srinivas wrote: > Michele, > > Why do you think that? Blockers are Blockers for the release. If the > blockers are not addressed, there will not be a release. Isn't that > why i sent this email about voting for your bug and adding comments to > make stuff blockers? > > What am i missing here? > > thanks, > dims > > On 7/1/07, Michele Mazzucco <[EMAIL PROTECTED]> wrote: >> Eran, >> >> your point is "let's add new, cool features", my point is "let's >> build something reliable". I think if you want to use a tool in a >> production environment the second point is much more important. >> >> >> Michele >> >> On 1 Jul 2007, at 04:53, Eran Chinthaka wrote: >> >> > -BEGIN PGP SIGNED MESSAGE- >> > Hash: SHA1 >> > >> > Michele Mazzucco wrote: >> >> Dims, >> >> >> >> what about postponing the 1.3 release and fixing (at least) all >> the >> >> blockers? ;) >> > >> > Michele, >> > >> > I do not see a point in that. If we have a deadline then >> everyone is >> > encouraged to work. If just postpone then we will lose the >> > momentum. And >> > also of there are significant improvements over the last release >> > then it >> > is the best to think about a release. I think what we need is to >> set >> > realistic goals with deadlines which is what Dims had done. >> > >> > Chinthaka >> > -BEGIN PGP SIGNATURE- >> > Version: GnuPG v1.4.3 (GNU/Linux) >> > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org >> > >> > iD8DBQFGhyUrjON2uBzUhh8RAoEhAKCV4AYGl18ApVdUizqc1hyOEae/mACdFAy5 >> > NT3qeHhTTHvqsM0uzVuo5Xo= >> > =QTbK >> > -END PGP SIGNATURE- >> > >> > >> - >> > 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] >> >> > > > -- > Davanum Srinivas :: http://davanum.wordpress.com > > - > 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] -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] Please VOTE for your favorite bug to be fixed.
Dims, I disagree with what Eran says, which is "we have a deadline, so probably not all bugs will be fixed for the next release". I think people would be much more happy to wait 1 or 2 weeks more to have a more reliable release than having an unstable one now. Simply lowering bug priorities from blockers to critical (or other) doesn't mean the tool is bug free (this is what I understand from previous emails). And, of course, adding new features will probably mean adding new bugs as well. Michele On 1 Jul 2007, at 13:09, Davanum Srinivas wrote: Michele, Why do you think that? Blockers are Blockers for the release. If the blockers are not addressed, there will not be a release. Isn't that why i sent this email about voting for your bug and adding comments to make stuff blockers? What am i missing here? thanks, dims On 7/1/07, Michele Mazzucco <[EMAIL PROTECTED]> wrote: Eran, your point is "let's add new, cool features", my point is "let's build something reliable". I think if you want to use a tool in a production environment the second point is much more important. Michele On 1 Jul 2007, at 04:53, Eran Chinthaka wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Michele Mazzucco wrote: >> Dims, >> >> what about postponing the 1.3 release and fixing (at least) all the >> blockers? ;) > > Michele, > > I do not see a point in that. If we have a deadline then everyone is > encouraged to work. If just postpone then we will lose the > momentum. And > also of there are significant improvements over the last release > then it > is the best to think about a release. I think what we need is to set > realistic goals with deadlines which is what Dims had done. > > Chinthaka > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.3 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFGhyUrjON2uBzUhh8RAoEhAKCV4AYGl18ApVdUizqc1hyOEae/mACdFAy5 > NT3qeHhTTHvqsM0uzVuo5Xo= > =QTbK > -END PGP SIGNATURE- > > - > 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] -- Davanum Srinivas :: http://davanum.wordpress.com - 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]
Re: [Axis2] Please VOTE for your favorite bug to be fixed.
Michele, Why do you think that? Blockers are Blockers for the release. If the blockers are not addressed, there will not be a release. Isn't that why i sent this email about voting for your bug and adding comments to make stuff blockers? What am i missing here? thanks, dims On 7/1/07, Michele Mazzucco <[EMAIL PROTECTED]> wrote: Eran, your point is "let's add new, cool features", my point is "let's build something reliable". I think if you want to use a tool in a production environment the second point is much more important. Michele On 1 Jul 2007, at 04:53, Eran Chinthaka wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Michele Mazzucco wrote: >> Dims, >> >> what about postponing the 1.3 release and fixing (at least) all the >> blockers? ;) > > Michele, > > I do not see a point in that. If we have a deadline then everyone is > encouraged to work. If just postpone then we will lose the > momentum. And > also of there are significant improvements over the last release > then it > is the best to think about a release. I think what we need is to set > realistic goals with deadlines which is what Dims had done. > > Chinthaka > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.3 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFGhyUrjON2uBzUhh8RAoEhAKCV4AYGl18ApVdUizqc1hyOEae/mACdFAy5 > NT3qeHhTTHvqsM0uzVuo5Xo= > =QTbK > -END PGP SIGNATURE- > > - > 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] -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] Please VOTE for your favorite bug to be fixed.
Eran, your point is "let's add new, cool features", my point is "let's build something reliable". I think if you want to use a tool in a production environment the second point is much more important. Michele On 1 Jul 2007, at 04:53, Eran Chinthaka wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Michele Mazzucco wrote: Dims, what about postponing the 1.3 release and fixing (at least) all the blockers? ;) Michele, I do not see a point in that. If we have a deadline then everyone is encouraged to work. If just postpone then we will lose the momentum. And also of there are significant improvements over the last release then it is the best to think about a release. I think what we need is to set realistic goals with deadlines which is what Dims had done. Chinthaka -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGhyUrjON2uBzUhh8RAoEhAKCV4AYGl18ApVdUizqc1hyOEae/mACdFAy5 NT3qeHhTTHvqsM0uzVuo5Xo= =QTbK -END PGP SIGNATURE- - 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]
RE: Rampart Without Axis
Rampart is just a wrapper around WSS4J library that plugs in Axs2 as a module. If you need to implement some custom stuff, try using it directly. From: W Strater [mailto:[EMAIL PROTECTED] Sent: Thu 6/28/2007 2:09 PM To: axis-user@ws.apache.org Subject: Rampart Without Axis Is it possible to use Rampart without Axis? We are using Weblogic and already have many webservice built and running but now we want to implement a SecureTokenService issueing SAML v1.1 tokens and protect some webservices with the tokens. Wes. ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. <>- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
