[jira] [Commented] (WSS-599) Upgrade to Java 8 DateTime API
[ https://issues.apache.org/jira/browse/WSS-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17360066#comment-17360066 ] Jochen Wiedmann commented on WSS-599: - If so, a possible workaround would be to use [https://docs.oracle.com/javase/8/docs/api/java/time/format/DateTimeFormatter.html#ISO_DATE_TIME] would it? > Upgrade to Java 8 DateTime API > -- > > Key: WSS-599 > URL: https://issues.apache.org/jira/browse/WSS-599 > Project: WSS4J > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 2.2.0 > > > This task is to replace all java.util.Date, Calendar, XMLGregorianCalendar > plus the custom Date Formatter stuff with the new Java 8 DateTime API. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@ws.apache.org For additional commands, e-mail: dev-h...@ws.apache.org
[jira] [Resolved] (WSCOMMONS-588) How can fetch the xml content from the HttpServletResponse?
[ https://issues.apache.org/jira/browse/WSCOMMONS-588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jochen Wiedmann resolved WSCOMMONS-588. --- Resolution: Invalid Please understand, that the ASF Jira is not a support forum. Your question is unrelated to any component in the ws.apache.org project, in particular not to WSCOMMONS. Please move your question to an appropriate platform, like the log4j2 users mailing list. (See https://logging.apache.org/log4j/2.x/mail-lists.html.) > How can fetch the xml content from the HttpServletResponse? > --- > > Key: WSCOMMONS-588 > URL: https://issues.apache.org/jira/browse/WSCOMMONS-588 > Project: WS-Commons > Issue Type: Wish > Components: General >Reporter: sivan > > PrintWriter pr = response.getWriter(); > code for processing the web service. > . > . > . > String url = "/" + page.getPath() + "/" + pagename; > sess.startPage(page, null, req, response); > RequestDispatcher dispatcher = getServletContext().getRequestDispatcher(url); > dispatcher.include(req, response); > pr.close(); > This is the basic code we are using for processing the web service. > Here we are facing the difficulty of logging the response of the web service. > How we can retrieve the XML content from the response for logging? > We are using the log4j2 logger. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@ws.apache.org For additional commands, e-mail: dev-h...@ws.apache.org
[jira] [Closed] (XMLRPC-195) StringSerializer does not create tag
[
https://issues.apache.org/jira/browse/XMLRPC-195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jochen Wiedmann closed XMLRPC-195.
--
Resolution: Not A Problem
Assignee: Jochen Wiedmann
Works as specified, hence "not a problem".
> StringSerializer does not create tag
> -
>
> Key: XMLRPC-195
> URL: https://issues.apache.org/jira/browse/XMLRPC-195
> Project: XML-RPC
> Issue Type: Bug
> Components: Source
>Affects Versions: 3.1.3
> Environment: Windows 7
>Reporter: Gokulakrishnan
>Assignee: Jochen Wiedmann
>Priority: Critical
>
> Consider a method call (API) named 'login' that takes in 4 parameters major
> version (integer), minor version (integer), user name (string) and password
> (string). Below code snippet explains how I invoke this remote API.
> XmlRpcClient client = new XmlRpcClient();
> Object[] loginParams = {new Integer(2), new Integer(0), new
> String("u...@sample.com"), new String("password")};
> client.execute("login", loginParams);
> The four parameters are wrapped as Object array to method call named 'login'.
> Below is the XML generated and passed to server hosting login API:
>
> login
>
>
>
> 2
>
>
>
>
> 0
>
>
>
>
> u...@sample.com
>
>
>
>
> password
>
>
>
>
> As you notice the user name - u...@sample.com and password - password are
> serialized without '' tag. Is this intentional. I referred the code
> StringSerializer and noticed that '' tag is not passed to write
> method. By XML-RPC specification http://xmlrpc.scripting.com/spec it should
> have been:
> :
>
>
> u...@sample.com
>
>
> :
> Any specific reason for this change in behavior ?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@ws.apache.org
For additional commands, e-mail: dev-h...@ws.apache.org
[jira] [Commented] (XMLRPC-195) StringSerializer does not create tag
[
https://issues.apache.org/jira/browse/XMLRPC-195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13501116#comment-13501116
]
Jochen Wiedmann commented on XMLRPC-195:
Quoting from the XML-RPC specification that you have referenced yourself below:
If no type is indicated, the type is string.
In other words: What Apache XML-RPC does, is a perfectly valid behaviour and
the error (if any) is on the side of the software which doesn't deal with that
properly.
A Google search for "Apache XML RPC string tag" quickly reveals possibly
workarounds, as detailed in the Apache XML RPC FAQ:
http://www.google.de/url?sa=t&rct=j&q=&esrc=s&source=web&cd=3&cad=rja&ved=0CC8QFjAC&url=http%3A%2F%2Fapache-xml.6118.n7.nabble.com%2FAdding-lt-string-gt-tag-in-XML-RPC-3-1-td29255.html&ei=hmmrUIWSB4nHswaqr4HoCg&usg=AFQjCNFaJwfP155CYYU4xzFrtweumv_V1Q
Closing this as "not a bug".
> StringSerializer does not create tag
> -
>
> Key: XMLRPC-195
> URL: https://issues.apache.org/jira/browse/XMLRPC-195
> Project: XML-RPC
> Issue Type: Bug
> Components: Source
>Affects Versions: 3.1.3
> Environment: Windows 7
>Reporter: Gokulakrishnan
>Priority: Critical
>
> Consider a method call (API) named 'login' that takes in 4 parameters major
> version (integer), minor version (integer), user name (string) and password
> (string). Below code snippet explains how I invoke this remote API.
> XmlRpcClient client = new XmlRpcClient();
> Object[] loginParams = {new Integer(2), new Integer(0), new
> String("u...@sample.com"), new String("password")};
> client.execute("login", loginParams);
> The four parameters are wrapped as Object array to method call named 'login'.
> Below is the XML generated and passed to server hosting login API:
>
> login
>
>
>
> 2
>
>
>
>
> 0
>
>
>
>
> u...@sample.com
>
>
>
>
> password
>
>
>
>
> As you notice the user name - u...@sample.com and password - password are
> serialized without '' tag. Is this intentional. I referred the code
> StringSerializer and noticed that '' tag is not passed to write
> method. By XML-RPC specification http://xmlrpc.scripting.com/spec it should
> have been:
> :
>
>
> u...@sample.com
>
>
> :
> Any specific reason for this change in behavior ?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@ws.apache.org
For additional commands, e-mail: dev-h...@ws.apache.org
[jira] [Resolved] (XMLRPC-190) Cannot find XmlRpcServlet.properties file in war when packaged it in ear
[
https://issues.apache.org/jira/browse/XMLRPC-190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jochen Wiedmann resolved XMLRPC-190.
Resolution: Invalid
Not an XML-RPC issue.
> Cannot find XmlRpcServlet.properties file in war when packaged it in ear
>
>
> Key: XMLRPC-190
> URL: https://issues.apache.org/jira/browse/XMLRPC-190
> Project: XML-RPC
> Issue Type: Wish
>Affects Versions: 3.1.3
> Environment: linux / windows
>Reporter: zappee
>Priority: Minor
> Labels: Failed, XmlRpcServlet.properties, locate, resource, to
> Fix For: 3.0
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> Cannot find XmlRpcServlet.properties file in war when packaged it in ear.
> Workaround:
> ---
> You have to extend the original org.apache.xmlrpc.webserver.XmlRpcServlet
> class and overwrite newXmlRpcHandlerMapping() method. After it you may use
> your new class file in web.xml instead of the original
> org.apache.xmlrpc.webserver.XmlRpcServlet class.
>
> MyXmlRpcServlet.java:
> public class MyXmlRpcServlet extends org.apache.xmlrpc.webserver.XmlRpcServlet
> {
> @Override
> protected XmlRpcHandlerMapping newXmlRpcHandlerMapping() throws
> XmlRpcException
> {
> String packageName =
> this.getClass().getPackage().getName().replaceAll("\\.", "/");
> String realPath = "/WEB-INF/classes/" + packageName +
> "/XmlRpcServlet.properties";
> try
> {
> URL url = this.getServletContext().getResource(realPath);
> if (url == null)
> {
> throw new XmlRpcException("Failed to locate resource
> XmlRpcServlet.properties");
> }
> return newPropertyHandlerMapping(url);
> }
> catch (IOException e)
> {
> throw new XmlRpcException("Failed to load resource " + realPath +
> ": " + e.getMessage(), e);
> }
> }
> }
> web.xml:
>
> XmlRpcServlet
>
> com.remal.xmlrpc.webserver.MyXmlRpcServlet
>
> enabledForExtensions
> true
>
> Sets, whether the servlet supports vendor extensions for
> XML-RPC.
>
>
>
>
> XmlRpcServlet
> /xmlrpc
>
> This solution is working in standalone war and/or war when packaged it in ear.
> regards, Arnold Somogyi
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@ws.apache.org
For additional commands, e-mail: dev-h...@ws.apache.org
[jira] [Commented] (XMLRPC-190) Cannot find XmlRpcServlet.properties file in war when packaged it in ear
[
https://issues.apache.org/jira/browse/XMLRPC-190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13105342#comment-13105342
]
Jochen Wiedmann commented on XMLRPC-190:
Try replacing
URL url = this.getServletContext().getResource(realPath);
with
URL url = Thread.currentThread().getContextClassLoader()getResource(realPath);
If this doesn't work either, please contact you application servers support
forum. This issue is not related to XML-RPC.
> Cannot find XmlRpcServlet.properties file in war when packaged it in ear
>
>
> Key: XMLRPC-190
> URL: https://issues.apache.org/jira/browse/XMLRPC-190
> Project: XML-RPC
> Issue Type: Wish
>Affects Versions: 3.1.3
> Environment: linux / windows
>Reporter: zappee
>Priority: Minor
> Labels: Failed, XmlRpcServlet.properties, locate, resource, to
> Fix For: 3.0
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> Cannot find XmlRpcServlet.properties file in war when packaged it in ear.
> Workaround:
> ---
> You have to extend the original org.apache.xmlrpc.webserver.XmlRpcServlet
> class and overwrite newXmlRpcHandlerMapping() method. After it you may use
> your new class file in web.xml instead of the original
> org.apache.xmlrpc.webserver.XmlRpcServlet class.
>
> MyXmlRpcServlet.java:
> public class MyXmlRpcServlet extends org.apache.xmlrpc.webserver.XmlRpcServlet
> {
> @Override
> protected XmlRpcHandlerMapping newXmlRpcHandlerMapping() throws
> XmlRpcException
> {
> String packageName =
> this.getClass().getPackage().getName().replaceAll("\\.", "/");
> String realPath = "/WEB-INF/classes/" + packageName +
> "/XmlRpcServlet.properties";
> try
> {
> URL url = this.getServletContext().getResource(realPath);
> if (url == null)
> {
> throw new XmlRpcException("Failed to locate resource
> XmlRpcServlet.properties");
> }
> return newPropertyHandlerMapping(url);
> }
> catch (IOException e)
> {
> throw new XmlRpcException("Failed to load resource " + realPath +
> ": " + e.getMessage(), e);
> }
> }
> }
> web.xml:
>
> XmlRpcServlet
>
> com.remal.xmlrpc.webserver.MyXmlRpcServlet
>
> enabledForExtensions
> true
>
> Sets, whether the servlet supports vendor extensions for
> XML-RPC.
>
>
>
>
> XmlRpcServlet
> /xmlrpc
>
> This solution is working in standalone war and/or war when packaged it in ear.
> regards, Arnold Somogyi
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@ws.apache.org
For additional commands, e-mail: dev-h...@ws.apache.org
[jira] Resolved: (XMLRPC-182) PropertyHandlerMapping should allow unprefixed names
[ https://issues.apache.org/jira/browse/XMLRPC-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jochen Wiedmann resolved XMLRPC-182. Resolution: Fixed Fix Version/s: 3.1.4 Assignee: Jochen Wiedmann Applied, thank you! > PropertyHandlerMapping should allow unprefixed names > > > Key: XMLRPC-182 > URL: https://issues.apache.org/jira/browse/XMLRPC-182 > Project: XML-RPC > Issue Type: Improvement > Components: Source >Affects Versions: 3.1.3 >Reporter: Oliver Wagner >Assignee: Jochen Wiedmann >Priority: Minor > Fix For: 3.1.4 > > > Currently PropertyHandlerMapping will always register method names with the > form ".", there is no way to create a method without > prefix. Even when pKey is null, the name generated will be > "null.". > Similiar to the recent change on the client side, I propose to change name > generation to not generate a prefix if pKey is null, e.g. in > registerPublicMethods(): > String name=(pKey!=null)?(pKey + "." + > method.getName()):method.getName(); -- 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: dev-unsubscr...@ws.apache.org For additional commands, e-mail: dev-h...@ws.apache.org
[jira] Resolved: (XMLRPC-173) XmlRpcCommonsTransport logs one byte at a time
[
https://issues.apache.org/jira/browse/XMLRPC-173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jochen Wiedmann resolved XMLRPC-173.
Resolution: Fixed
Fix Version/s: 3.1.4
Assignee: Jochen Wiedmann
Applied, thank you!
> XmlRpcCommonsTransport logs one byte at a time
> --
>
> Key: XMLRPC-173
> URL: https://issues.apache.org/jira/browse/XMLRPC-173
> Project: XML-RPC
> Issue Type: Bug
>Affects Versions: 3.1.2
>Reporter: Brandon DuRette
>Assignee: Jochen Wiedmann
>Priority: Minor
> Fix For: 3.1.4
>
>
> In XmlRpcCommonsTransport, when the isUsingByteArrayOutput(config) = true
> branch is taken, the resulting logging is nearly impossible to understand,
> because each character (byte actually) is logged in a separate log entry.
> This occurs because the FilterOutputStream's implementation of write( byte[],
> int, int ) and write( byte[] ), just iteratively invoke write( byte ) -- and
> the underlying output stream logs each byte.
> To fix, just add the following overrides to the anonymous FilterOutputStream
> subclass:
> public void write( byte[] b, int off, int len )
> throws IOException {
> // Override to delegate directly -- improves
> performance and helps make log readable.
> out.write( b, off, len );
> }
> public void write( byte[] b ) throws IOException {
> // Override to delegate directly -- improves
> performance and helps make log readable.
> out.write( b );
> }
--
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: dev-unsubscr...@ws.apache.org
For additional commands, e-mail: dev-h...@ws.apache.org
[jira] Resolved: (XMLRPC-135) intercept method calls (on the client and on the server side)
[
https://issues.apache.org/jira/browse/XMLRPC-135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jochen Wiedmann resolved XMLRPC-135.
Resolution: Won't Fix
Assignee: Jochen Wiedmann
After 3 years, noone interested in working on this. Closing.
> intercept method calls (on the client and on the server side)
> -
>
> Key: XMLRPC-135
> URL: https://issues.apache.org/jira/browse/XMLRPC-135
> Project: XML-RPC
> Issue Type: Improvement
>Affects Versions: 3.0, 3.1
>Reporter: Mario Linke
>Assignee: Jochen Wiedmann
>
> This extension is to integrate cross-cutting concerns (AOP), how stopping the
> time, logging or transform args and return value.
> public interface Interceptor {
>
> public void beforeMethodInvocation (InterceptorContext
> pInterceptorContext);
> public void afterMethodInvocation (InterceptorContext
> pInterceptorContext);
> public void onError (Throwable pThrowable);
> }
> public final class InterceptorContext {
>
> private Method method = null;
> private Object[] args = null;
> private Object result = null;
> }
> InterceptorContext is analog to the XmlRpcRequest, extended to the result
> and the method object.
> Extend the XmlRpcController to register the Interceptors:
> - addInterceptor
> - removeInterceptor
> - getInterceptorByNumber
> and delegate before and after event:
> by the client to XmlRpcWorker
> by the server to the XmlRpcHandler
> Mario
--
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: dev-unsubscr...@ws.apache.org
For additional commands, e-mail: dev-h...@ws.apache.org
[jira] Closed: (XMLRPC-170) XML attribute issue for auto_unique ID & auto_checksum with md5
[ https://issues.apache.org/jira/browse/XMLRPC-170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jochen Wiedmann closed XMLRPC-170. -- Resolution: Invalid Assignee: Jochen Wiedmann > XML attribute issue for auto_unique ID & auto_checksum with md5 > --- > > Key: XMLRPC-170 > URL: https://issues.apache.org/jira/browse/XMLRPC-170 > Project: XML-RPC > Issue Type: Wish >Affects Versions: unspecified > Environment: window xp, other thing i dont know because my background > is not IT. >Reporter: magnate Williams >Assignee: Jochen Wiedmann >Priority: Critical > Fix For: unspecified > > Original Estimate: 504h > Remaining Estimate: 504h > > I want to develop XML document with following DTD file with XML format. I > have also XSL file as a externatl file to represent my xml in browser. > my problem is i want to create AUTO unique ID & checksum for each "leaf" > element according to DTD. > In my xml file there are more than 500 attachment & each leaf have unique ID > & Checksum, and one more thing, after creating final XML, if i make any > modification to original xml (i.e. " operation (append | delete | new | > replace) #REQUIRED " ) i need to create cross reference (i.e. > "/AAA/00/index.xml#idMG1234" here previous attached file ID = MG1234 > [means 'magnate-williams-1234] ) for new attached file. > for life cycle of my xml, i want to create checksum for final index.xml file, > that will be unique. > main folder name = AAA > sub foler to main = 00 > new version folder = 01 > next version folder = 02 and so on > I need to all version folder create auto under main folder (AAA). > Please help me out for the same. I am helpless for the same. Thanks in > Advanced... > > DTD Part is: > --- > > >xmlns:root CDATA #FIXED > xmlns:xlink CDATA #FIXED > xml:lang CDATA #IMPLIED > dtd-version CDATA #FIXED > > > >ID ID #REQUIRED > application-version CDATA #IMPLIED > version CDATA #IMPLIED > font-library CDATA #IMPLIED > operation (append | delete | new | replace) #REQUIRED > modified-file CDATA #IMPLIED > checksum CDATA #REQUIRED > checksum-type CDATA #REQUIRED > keywords CDATA #IMPLIED > xmlns:xlink CDATA #FIXED > xlink:type CDATA #FIXED > xlink:role CDATA #IMPLIED > xlink:href CDATA #IMPLIED > xlink:show (embed | none | other | new | replace) #IMPLIED > xlink:actuate (onRequest | none | other | onLoad) #IMPLIED > xml:lang CDATA #IMPLIED > > > >ID ID #IMPLIED > > > >ID ID #IMPLIED > > > >ID ID #REQUIRED > xmlns:xlink CDATA #FIXED > xlink:type CDATA #FIXED > xlink:role CDATA #IMPLIED > xlink:title CDATA #REQUIRED > xlink:href CDATA #REQUIRED > xlink:show (embed | none | other | new | replace) #IMPLIED > xlink:actuate (onRequest | none | other | onLoad) #IMPLIED > > > >ID ID #IMPLIED > xml:lang CDATA #IMPLIED > > > >ID ID #IMPLIED > xml:lang CDATA #IMPLIED > > > element-1-2-n?)> >ID ID #IMPLIED > xml:lang CDATA #IMPLIED > > > >ID ID #IMPLIED > xml:lang CDATA #IMPLIED > > > . > . > . > . > >ID ID #IMPLIED > xml:lang CDATA #IMPLIED > > > _ > - > _ > XML Part is : > > > > > > > > > > > > > > > > > > > > > . > . > . > . > > > > > > > > > -- 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: dev-unsubscr...@ws.apache.org For additional commands, e-mail: dev-h...@ws.apache.org
[jira] Closed: (XMLRPC-172) CLONE -XML attribute issue for auto_unique ID & auto_checksum with md5
[ https://issues.apache.org/jira/browse/XMLRPC-172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jochen Wiedmann closed XMLRPC-172. -- Resolution: Invalid Assignee: Jochen Wiedmann > CLONE -XML attribute issue for auto_unique ID & auto_checksum with md5 > -- > > Key: XMLRPC-172 > URL: https://issues.apache.org/jira/browse/XMLRPC-172 > Project: XML-RPC > Issue Type: Wish >Affects Versions: unspecified > Environment: window xp, other thing i dont know because my background > is not IT. >Reporter: magnate Williams >Assignee: Jochen Wiedmann >Priority: Critical > Fix For: unspecified > > Original Estimate: 504h > Remaining Estimate: 504h > > I want to develop XML document with following DTD file with XML format. I > have also XSL file as a externatl file to represent my xml in browser. > my problem is i want to create AUTO unique ID & checksum for each "leaf" > element according to DTD. > In my xml file there are more than 500 attachment & each leaf have unique ID > & Checksum, and one more thing, after creating final XML, if i make any > modification to original xml (i.e. " operation (append | delete | new | > replace) #REQUIRED " ) i need to create cross reference (i.e. > "/AAA/00/index.xml#idMG1234" here previous attached file ID = MG1234 > [means 'magnate-williams-1234] ) for new attached file. > for life cycle of my xml, i want to create checksum for final index.xml file, > that will be unique. > main folder name = AAA > sub foler to main = 00 > new version folder = 01 > next version folder = 02 and so on > I need to all version folder create auto under main folder (AAA). > Please help me out for the same. I am helpless for the same. Thanks in > Advanced... > > DTD Part is: > --- > > >xmlns:root CDATA #FIXED > xmlns:xlink CDATA #FIXED > xml:lang CDATA #IMPLIED > dtd-version CDATA #FIXED > > > >ID ID #REQUIRED > application-version CDATA #IMPLIED > version CDATA #IMPLIED > font-library CDATA #IMPLIED > operation (append | delete | new | replace) #REQUIRED > modified-file CDATA #IMPLIED > checksum CDATA #REQUIRED > checksum-type CDATA #REQUIRED > keywords CDATA #IMPLIED > xmlns:xlink CDATA #FIXED > xlink:type CDATA #FIXED > xlink:role CDATA #IMPLIED > xlink:href CDATA #IMPLIED > xlink:show (embed | none | other | new | replace) #IMPLIED > xlink:actuate (onRequest | none | other | onLoad) #IMPLIED > xml:lang CDATA #IMPLIED > > > >ID ID #IMPLIED > > > >ID ID #IMPLIED > > > >ID ID #REQUIRED > xmlns:xlink CDATA #FIXED > xlink:type CDATA #FIXED > xlink:role CDATA #IMPLIED > xlink:title CDATA #REQUIRED > xlink:href CDATA #REQUIRED > xlink:show (embed | none | other | new | replace) #IMPLIED > xlink:actuate (onRequest | none | other | onLoad) #IMPLIED > > > >ID ID #IMPLIED > xml:lang CDATA #IMPLIED > > > >ID ID #IMPLIED > xml:lang CDATA #IMPLIED > > > element-1-2-n?)> >ID ID #IMPLIED > xml:lang CDATA #IMPLIED > > > >ID ID #IMPLIED > xml:lang CDATA #IMPLIED > > > . > . > . > . > >ID ID #IMPLIED > xml:lang CDATA #IMPLIED > > > _ > - > _ > XML Part is : > > > > > > > > > > > > > > > > > > > > > . > . > . > . > > > > > > > > > -- 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: dev-unsubscr...@ws.apache.org For additional commands, e-mail: dev-h...@ws.apache.org
[jira] Deleted: (XMLRPC-180) file:///C:/Services%20Files/Apache%20Software%20Foundation/Tomcat%206.0/www/angosso.com%20%208080/conf/web.xml
[ https://issues.apache.org/jira/browse/XMLRPC-180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jochen Wiedmann deleted XMLRPC-180: --- > file:///C:/Services%20Files/Apache%20Software%20Foundation/Tomcat%206.0/www/angosso.com%20%208080/conf/web.xml > -- > > Key: XMLRPC-180 > URL: https://issues.apache.org/jira/browse/XMLRPC-180 > Project: XML-RPC > Issue Type: Improvement > Environment: PC Windows Server 2008 (Longhorn) >Reporter: Mbiama Assogo Roger > Original Estimate: 1h > Remaining Estimate: 1h > > Importance: P2 major > Target Milestone: default > Assigned To: Tomcat Developers List -- 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: dev-unsubscr...@ws.apache.org For additional commands, e-mail: dev-h...@ws.apache.org
[jira] Resolved: (XMLRPC-169) XmlRpcSunHttpTransport creates a new connection for every request.
[ https://issues.apache.org/jira/browse/XMLRPC-169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jochen Wiedmann resolved XMLRPC-169. Resolution: Fixed Fix Version/s: 3.1.4 Assignee: Jochen Wiedmann Applied. > XmlRpcSunHttpTransport creates a new connection for every request. > -- > > Key: XMLRPC-169 > URL: https://issues.apache.org/jira/browse/XMLRPC-169 > Project: XML-RPC > Issue Type: Improvement > Components: Source >Affects Versions: 3.1.3 > Environment: Solaris >Reporter: Alan Burlison >Assignee: Jochen Wiedmann >Priority: Minor > Fix For: 3.1.4 > > Attachments: XMLRPC-169.patch > > > An instance of XmlRpcSunHttpTransport creates a new connection to the server > for every request that is made via it. That's *horrendously* expensive where > the connection is a SSL connection. > Here's a trace, note the repeated connect() calls. > /2: connect(20, 0xFE32E4D0, 32, SOV_DEFAULT)= 0 > /2: getsockname(20, 0xFE32E4D0, 0xFE32E618, SOV_DEFAULT) = 0 > /2: setsockopt(20, tcp, TCP_NODELAY, 0xFE32E768, 4, SOV_DEFAULT) = 0 > /2: send(20, " P O S T / H T T P /".., 283, 0) = 283 > /2: send(20, " < ? x m l v e r s i o".., 215, 0) = 215 > /2: read(20, " H T T P / 1 . 0 2 0 0".., 8192)= 84 > /2: read(20, " < ? x m l v e r s i o".., 8108)= 202 > /2: ioctl(20, FIONREAD, 0xFE32E684) = 0 > /2: fcntl(21, F_DUP2FD, 0x0014) = 20 > /2: close(20) = 0 > /2: so_socket(PF_INET6, SOCK_STREAM, IPPROTO_IP, 0x, SOV_DEFAULT) = > 20 > /2: connect(20, 0xFE32E4D0, 32, SOV_DEFAULT)= 0 > /2: getsockname(20, 0xFE32E4D0, 0xFE32E618, SOV_DEFAULT) = 0 > /2: setsockopt(20, tcp, TCP_NODELAY, 0xFE32E768, 4, SOV_DEFAULT) = 0 > /2: send(20, " P O S T / H T T P /".., 283, 0) = 283 > /2: send(20, " < ? x m l v e r s i o".., 215, 0) = 215 > /2: read(20, " H T T P / 1 . 0 2 0 0".., 8192)= 84 > /2: read(20, " < ? x m l v e r s i o".., 8108)= 202 > /2: ioctl(20, FIONREAD, 0xFE32E684) = 0 > /2: fcntl(21, F_DUP2FD, 0x0014) = 20 > /2: close(20) = 0 > /2: so_socket(PF_INET6, SOCK_STREAM, IPPROTO_IP, 0x, SOV_DEFAULT) = > 20 > /2: connect(20, 0xFE32E4D0, 32, SOV_DEFAULT)= 0 > /2: getsockname(20, 0xFE32E4D0, 0xFE32E618, SOV_DEFAULT) = 0 > /2: setsockopt(20, tcp, TCP_NODELAY, 0xFE32E768, 4, SOV_DEFAULT) = 0 > /2: send(20, " P O S T / H T T P /".., 283, 0) = 283 > /2: send(20, " < ? x m l v e r s i o".., 215, 0) = 215 > /2: read(20, " H T T P / 1 . 0 2 0 0".., 8192)= 84 > /2: read(20, " < ? x m l v e r s i o".., 8108)= 202 > /2: ioctl(20, FIONREAD, 0xFE32E684) = 0 > /2: fcntl(21, F_DUP2FD, 0x0014) = 20 > /2: close(20) = 0 > /2: so_socket(PF_INET6, SOCK_STREAM, IPPROTO_IP, 0x, SOV_DEFAULT) = > 20 > /2: connect(20, 0xFE32E4D0, 32, SOV_DEFAULT)= 0 > /2: getsockname(20, 0xFE32E4D0, 0xFE32E618, SOV_DEFAULT) = 0 > /2: setsockopt(20, tcp, TCP_NODELAY, 0xFE32E768, 4, SOV_DEFAULT) = 0 > /2: send(20, " P O S T / H T T P /".., 283, 0) = 283 > /2: send(20, " < ? x m l v e r s i o".., 215, 0) = 215 > /2: read(20, " H T T P / 1 . 0 2 0 0".., 8192)= 84 > /2: read(20, " < ? x m l v e r s i o".., 8108)= 202 > /2: ioctl(20, FIONREAD, 0xFE32E684) = 0 > /2: fcntl(21, F_DUP2FD, 0x0014) = 20 > /2: close(20) = 0 > And if you assume that a major use of the Apache XML-RPC client is with the > Apache XML-RPC server, it means the keepalive support in the server is pretty > much a waste of time. -- 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: dev-unsubscr...@ws.apache.org For additional commands, e-mail: dev-h...@ws.apache.org
[jira] Resolved: (XMLRPC-184) OSGi packaging for XMLRPC
[ https://issues.apache.org/jira/browse/XMLRPC-184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jochen Wiedmann resolved XMLRPC-184. Resolution: Fixed Fix Version/s: (was: unspecified) 3.1.4 Assignee: Jochen Wiedmann Applied, thank you! > OSGi packaging for XMLRPC > - > > Key: XMLRPC-184 > URL: https://issues.apache.org/jira/browse/XMLRPC-184 > Project: XML-RPC > Issue Type: New Feature >Affects Versions: 3.1.3 >Reporter: Antoine Toulme >Assignee: Jochen Wiedmann > Fix For: 3.1.4 > > Attachments: bundle_packaging.diff > > > The project currently builds a set of jars. With a few modifications, we can > make it create OSGi bundles instead. -- 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: dev-unsubscr...@ws.apache.org For additional commands, e-mail: dev-h...@ws.apache.org
