Re: [PR] Fix AXIS2-5858 [axis-axis2-java-core]
robertlazarski commented on PR #842:
URL:
https://github.com/apache/axis-axis2-java-core/pull/842#issuecomment-2658118230
@cortlepp upon further review this code finds my default ipv6 address on my
local Ubuntu machine but doesn't return it - only ipv4.
See this print statement that you can see in the unit test logs at
modules/transport/tcp/target/surefire-reports/org.apache.axis2.transport.tcp.TCPEchoRawXMLTest-output.txt
import java.net.Inet6Address;
if ( !inetAddr.isLoopbackAddress() )
{
if (inetAddr instanceof Inet6Address)
{
System.out.println("found ipv6: " + inetAddr);
}
...
System.out.println("found addresses: " + addresses);
return addresses;
}
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[PR] Bump spring.version from 6.2.2 to 6.2.3 [axis-axis2-java-core]
dependabot[bot] opened a new pull request, #854: URL: https://github.com/apache/axis-axis2-java-core/pull/854 Bumps `spring.version` from 6.2.2 to 6.2.3. Updates `org.springframework:spring-core` from 6.2.2 to 6.2.3 Release notes Sourced from https://github.com/spring-projects/spring-framework/releases";>org.springframework:spring-core's releases. v6.2.3 :star: New Features Add form fields to MockMvc Kotlin DSL https://redirect.github.com/spring-projects/spring-framework/pull/34412";>#34412 Make ProblemDetail implement Serializable https://redirect.github.com/spring-projects/spring-framework/issues/34409";>#34409 Support @MockitoSpyBean at the type level on test classes https://redirect.github.com/spring-projects/spring-framework/issues/34408";>#34408 Expose order values of TestExecutionListener implementations as constants https://redirect.github.com/spring-projects/spring-framework/issues/34404";>#34404 ContentDisposition should match attributes in a case-insensitive fashion https://redirect.github.com/spring-projects/spring-framework/pull/34383";>#34383 Provide access to servletPath in ServletRequestPathUtils https://redirect.github.com/spring-projects/spring-framework/issues/34379";>#34379 Use ConversionService to convert POJO to array for SpEL varargs invocations https://redirect.github.com/spring-projects/spring-framework/issues/34371";>#34371 Provide a more actionable CGLIB error message with native https://redirect.github.com/spring-projects/spring-framework/issues/34370";>#34370 Wrap disconnected client exceptions as AsyncRequestNotUsableException in Servlet container onError callback https://redirect.github.com/spring-projects/spring-framework/issues/34363";>#34363 Support RFC 8441 WebSocket upgrade with HTTP/2 CONNECT https://redirect.github.com/spring-projects/spring-framework/pull/34362";>#34362 Optimize default property editor allocations for bean instance creation https://redirect.github.com/spring-projects/spring-framework/issues/34361";>#34361 Continue with pre-instantiation when current bean is in creation already https://redirect.github.com/spring-projects/spring-framework/issues/34349";>#34349 Allow filtering bean instances returned by ObjectProvider#stream() https://redirect.github.com/spring-projects/spring-framework/issues/34318";>#34318 GenericConversionService finds wrong converter for partially unresolvable generic types https://redirect.github.com/spring-projects/spring-framework/issues/34298";>#34298 Avoid re-creating HandlerMethod unless handler is resolved through the BeanFactory https://redirect.github.com/spring-projects/spring-framework/issues/34277";>#34277 UrlResource should leniently handle HTTP endpoints which do not support HEAD https://redirect.github.com/spring-projects/spring-framework/issues/34217";>#34217 Add API counterpart for handling Fallback and 'defaultCandidate=false' beans https://redirect.github.com/spring-projects/spring-framework/issues/34203";>#34203 Add support for multidimensional arrays https://redirect.github.com/spring-projects/spring-framework/pull/34183";>#34183 Add getters to ServerResponseResultHandler https://redirect.github.com/spring-projects/spring-framework/pull/34066";>#34066 Improve diagnostics when a Bean Override cannot be selected by type https://redirect.github.com/spring-projects/spring-framework/pull/34006";>#34006 Expression performance regression due to missing annotation types on context classes https://redirect.github.com/spring-projects/spring-framework/issues/33948";>#33948 :lady_beetle: Bug Fixes PathMatchingResourcePatternResolver failing against non-jar file in classpath https://redirect.github.com/spring-projects/spring-framework/issues/34417";>#34417 GenericTypeResolver Since 6.2.0, generics cannot be obtained correctly in multi-layer interface inheritance (possible regression of https://redirect.github.com/spring-projects/spring-framework/issues/24963";>#24963) https://redirect.github.com/spring-projects/spring-framework/issues/34386";>#34386 Test Bean Overrides honor fallback qualifier instead of @Primary semantics https://redirect.github.com/spring-projects/spring-framework/issues/34374";>#34374 HTTP interface client raises IllegalArgumentException if query param name contains a colon https://redirect.github.com/spring-projects/spring-framework/issues/34364";>#34364 Quartz-style Nth Day of Week cron expressions can overflow to other month https://redirect.github.com/spring-projects/spring-framework/issues/34360";>#34360 Component scan fails to find jar entries in WEB-INF/classes with embedded Tomcat https://redirect.github.com/spring-projects/spring-framework/issues/34348";>#34348 Check hasNext when when accessing sessionIds from UserDestinationResult https://redirect.github.com/spring-projects/spring-framework/pull/34333";>#34333 Property binding to Map that implemen
[jira] [Updated] (AXIS2-5881) Small improvement to the listServices.jsp to sort services and operations
[ https://issues.apache.org/jira/browse/AXIS2-5881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Lazarski updated AXIS2-5881: --- Fix Version/s: 2.0.1 > Small improvement to the listServices.jsp to sort services and operations > - > > Key: AXIS2-5881 > URL: https://issues.apache.org/jira/browse/AXIS2-5881 > Project: Axis2 > Issue Type: Improvement >Affects Versions: 1.7.3 >Reporter: Jeff Thomas >Priority: Minor > Fix For: 2.0.1 > > Attachments: listServices.jsp, listServices.jsp.patch > > > One thing that has always bothered me about the "services/listServices.jsp" > was that it is not sorted ... which means scrolling around looking for the > service and/or operations. > In our build I have updated the listServices.jsp with a few changes to sort > the output of services and operations... would just like to suggest the fix > be incorporated in the build. (see attachment). Primarily I replaced the > HashMaps with ConcurrentSkipListMap to naturally sort by the keys > (ServiceName, OperationName) -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-6051) Axis2 Future Roadmap in keeping up with new Java Versions
[ https://issues.apache.org/jira/browse/AXIS2-6051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17926879#comment-17926879 ] Robert Lazarski commented on AXIS2-6051: We have one issue remaining for the Axis2 release - if an Eclipse user can verify the codegen plugin works - or not - that would be appreciated. https://issues.apache.org/jira/browse/AXIS2-5955 We are about a couple of days away from starting release vote. About 20 issues have been closed the last few days. Anything not resolved in a few days will be bumped to 2.0.1 or unassigned. The unit tests pass, though additional testing would be appreciated from the community. [~cortlepp] everything will be released off of master. > Axis2 Future Roadmap in keeping up with new Java Versions > - > > Key: AXIS2-6051 > URL: https://issues.apache.org/jira/browse/AXIS2-6051 > Project: Axis2 > Issue Type: Wish >Affects Versions: 1.8.0 >Reporter: Jeff Thomas >Assignee: Robert Lazarski >Priority: Major > Fix For: 2.0.0 > > > Related to AXIS2-6035. > Hi Robert/Andreas/Axis2 Support, > just a general question about the realistic future of Axis2 (and by extension > Axiom/Rampart) in keeping up with the quickly changing Java releases. > We are getting a lot of push from our customers (and our own internal wish to > use modern java features) to move to java 17+ ... we are hitting more and > more walls with things like: > * java modules > * javax -> jakarta migration // this is a big one! > ** jakarta.activation > ** jakarta.validation > ** jakarta.jms > ** jakarta.mail > ** jakarta.jws > ** jakarta.jaxb > ** ... > * Tomcat 10 + > * and related stuff like > ** ActiveMQ Artemis (jakarta.jms) > ** removal of SecurityManager in JDK 19+ > ** etc. > The sort of general feeling is that unfortunately we are getting pulled > towards a state of complete incompatibility between Axis2 and current > supported JVMs / other Frameworks. > Maybe you can give a bit of feedback about the roadmap for Axis2 and > addressing the growing gap in dependencies? (and would welcome any info > about Axiom/Rampart along the same lines). Good or bad news doesn't > matter...would appreciate having some concrete statement to address our own > internal planning about the way forward. :) > Appreciate any info you can provide. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Resolved] (AXIS2-5781) Maven Build - Module: kernel - generates / modifies file under source-control - should build in output directory
[
https://issues.apache.org/jira/browse/AXIS2-5781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Lazarski resolved AXIS2-5781.
Resolution: Fixed
Seems to have been fixed in 2017 - I see the git commits.
> Maven Build - Module: kernel - generates / modifies file under source-control
> - should build in output directory
>
>
> Key: AXIS2-5781
> URL: https://issues.apache.org/jira/browse/AXIS2-5781
> Project: Axis2
> Issue Type: Bug
> Components: kernel
>Affects Versions: 1.7.3
>Reporter: Jeff Thomas
>Priority: Minor
>
> Maven Build for axis2-kernel (./modules/kernel/pom.xml).
> In the axis2-kernel Maven Module (and at in at least the axis2-integration
> module as well) test ant-scripts and unit-tests run against the
> "./test-resources" directory instead of the "./target/test-resources"
> directory.
> In the interest of Maven "compliance" the build process should not edit,
> touch or otherwise "dirty" source-code files.
> Examples:
> 1. The Ant-script "test-resources/deployment/service2/build.xml" creates
> temporary directories, generates content, and removes these temporary
> directories directly within the "test-resources" source directory.
> 2. The Unit-Test utility method 'readWSDLFromFile' in XMLSchemaTest creates a
> File reference to a file in "test-resources" and performs the following:
> {code:java}XMLPrettyPrinter.prettify(file);{code}
> This updates (dirties) the input source-file - on my windows build it changes
> the line-endings from Unix to Windows.
> The current Maven POMs already take care of copying the "test-resources"
> directory to "target/test-resources" so all of the required input files and
> ant-scripts are available there. Therefore, the POM ANT "dir" properties and
> the JUnit tests just need to be updated to use these instead of the
> source-code originals.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Resolved] (AXIS2-5745) Changing a service name doesn't update its TypeTable struct
[
https://issues.apache.org/jira/browse/AXIS2-5745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Lazarski resolved AXIS2-5745.
Resolution: Feedback Received
This issue is stale and a proposed solution from another committer was the last
comment many years ago.
> Changing a service name doesn't update its TypeTable struct
> ---
>
> Key: AXIS2-5745
> URL: https://issues.apache.org/jira/browse/AXIS2-5745
> Project: Axis2
> Issue Type: Bug
> Components: kernel
>Affects Versions: 1.6.2
> Environment: Windows 8.1 x86-64, Tomcat 7.0.68 x86-64
>Reporter: Thorsten Schöning
>Priority: Major
> Attachments: WsAxis2SvcLc.java
>
>
> I have an implementation of ServiceLifeCycle in which I'm overriding startUp
> and change the name of my service in some special way to make my deployment
> easier. I'm simply implementing some kind of mandator mechanism based on
> exploded services and their unique name in the file system.
> This worked pretty fine the last years, but today I encountered that Axis2 is
> handling structures internally in which the service name is used as some
> component of a key. Those structures were built before startUp was called and
> were not updated on a changed service name. My service generated an exception
> for some reason, Axis2 tried to handle that and failed itself with a NPE,
> which made debugging pretty hard of course because the original exception was
> lost.
> The NPE was thrown in the following line 183 of RPCMessageReceiver and the
> not up to date structure was TypeTable for the service, that's why
> elementQName was null instead of a valid object. Gladly I was able to access
> that map in my ServiceLifeCycle implementation and update the generated keys
> and QNames with my new updated service name. I would have expected that if
> I'm able to change the service name, structs containing it would get updated
> automatically by Axis 2, which at least for TypeTable currently isn't the
> case.
> {CODE}
> 175Class[] exceptionTypes = method.getExceptionTypes();
> 176for (Class exceptionType : exceptionTypes){
> 177if
> (exceptionType.getName().equals(cause.getClass().getName())){
> 178// this is an bussiness logic exception so handle it
> properly
> 179String partQName =
> inMessage.getAxisService().getName() + getSimpleClassName(exceptionType);
> 180TypeTable typeTable =
> inMessage.getAxisService().getTypeTable();
> 181QName elementQName =
> typeTable.getQNamefortheType(partQName);
> 182SOAPFactory fac = getSOAPFactory(inMessage);
> 183OMElement exceptionElement =
> fac.createOMElement(elementQName);
> 184
> 185if
> (exceptionType.getName().equals(Exception.class.getName())){
> 186// this is an exception class. so create a element
> by hand and add the message
> 187 OMElement innterExceptionElement =
> fac.createOMElement(elementQName);
> 188 OMElement messageElement =
> fac.createOMElement("Message",
> inMessage.getAxisService().getTargetNamespace(), null);
> 189 messageElement.setText(cause.getMessage());
> {CODE}
> http://grepcode.com/file/repo1.maven.org/maven2/org.apache.axis2/axis2-adb/1.6.2/org/apache/axis2/rpc/receivers/RPCMessageReceiver.java/#183
> I'm currently unable to build Axis2 from src and am not sure where one would
> implement such a change, therefore can't provide patches, but instead I'll
> simply post my implemantation of the change for TypeTable in my
> ServiceLifeCycle. In my case, TypeTable contained the following data for my
> old service name "SoapAuth":
> {CODE}
> complexTypeMap HashMap (id=165)
> {java.sql={http://sql.java/xsd}SQLException,
> SoapAuthSecurityException={http://soap.ws.clients.backend.docs.docsrv.am_soft.de}SoapAuthSecurityException,
> java.sql.SQLException={http://sql.java/xsd}SQLException,
> logout={http://soap.ws.clients.backend.docs.docsrv.am_soft.de}logout,
> java.io={http://io.java/xsd}FileNotFoundException,
> SoapAuthSQLException={http://soap.ws.clients.backend.docs.docsrv.am_soft.de}SoapAuthSQLException,
>
> cookieAbgleich={http://soap.ws.clients.backend.docs.docsrv.am_soft.de}cookieAbgleich,
>
> SoapAuthClassNotFoundException={http://soap.ws.clients.backend.docs.docsrv.am_soft.de}SoapAuthClassNotFoundException,
>
> SoapAuthFileNotFoundException={http://soap.ws.clients.backend.docs.docsrv.am_soft.de}SoapAuthFileNotFoundException,
> java.io.IOException={http://io.java/xsd}IOException,
> SoapAuthIOException={http://soap.ws.clients.backend.docs.docsrv.am_soft.de}SoapAuthIOException,
> java.i
[jira] [Commented] (AXIS2-5908) There is no provision to set the CACHED_HTTP_STATE with HttpContext object
[
https://issues.apache.org/jira/browse/AXIS2-5908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17926861#comment-17926861
]
Robert Lazarski commented on AXIS2-5908:
I'm unclear on the issue here since using CACHED_HTTP_STATE is the preferred
way to customize this behavior.
If interested in getting a feature implemented in Axis2, the most reliable way
is a GitHub PR. I can work with you on that.
Please note that 2.0.0 is going out very soon, based off of httpclient5.
> There is no provision to set the CACHED_HTTP_STATE with HttpContext object
> --
>
> Key: AXIS2-5908
> URL: https://issues.apache.org/jira/browse/AXIS2-5908
> Project: Axis2
> Issue Type: Bug
> Components: transports
>Affects Versions: 1.7.4
>Reporter: Pavan Kumar Sangyam
>Priority: Major
>
> *Background:*
> *Current Approach:* Currently we are using “commons-httpclient3:” to provide
> stateful webservice capability in our product through httpclient3. As Http
> state management can be maintained with HttpState object in httpClient3, we
> implemented this as follows:
> * Implementation of HttpClient3 in Axis2 Client
> var myHttpState = new
> Packages.org.apache.commons.httpclient.HttpState();
>
> stub._getServiceClient().getOptions().setProperty('*CACHED_HTTP_STATE*',myHttpState);
>
> *Problem with current approach:* Since using httpclient3 is said to be NOT
> secured we want to go-head and use httpclient4. As Http state can be
> maintained with HttpContext object in httpClient4. However, unlike
> HttpState, the current Axis2 Client API implementation does not expose the
> HttpContext to set the HttpClient4.
>
> *Proposed Solution/Fix:* To fix the above problem and make it work, we made
> following changes to the axis2-transport-http-1.7.4.jar that worked to make
> stateful behavior. We would like to go head with the fix and need your
> consent on the next steps in contributing this code so that it continues to
> behave the same way like it used to when using httpclient3.
> * Following change that need to include the Axis2 Client API to retrieve the
> httpContext.
> HttpContext localContext=
>
> (HttpContext)msgContext.getProperty(HTTPConstants.*_CACHED_HTTP_STATE);_*
>
> For HttpClient4, HttpContext is instantiated and not allowed set the
> HttpContext with options
> HttpContext localContext = new BasicHttpContext();
> We replaced the above code with following to get the HttpConext with
> getOptions()
> HttpContext localContext=
> (HttpContext)msgContext.getProperty(HTTPConstants.*_CACHED_HTTP_STATE);_*
> _So that, Client can set the cookie in the httpContext_ _to send it to
> server._
> _org.apache.http.protocol.HttpContext localContext = new
> org.apache.http.protocol.BasicHttpContext();_
> _org.apache.http.client.CookieStore cookieStore = new
> org.apache.http.impl.client.BasicCookieStore();_
> _org.apache.http.impl.cookie.BasicClientCookie newCookie=new
> org.apache.http.impl.cookie.BasicClientCookie("pin","1234");_
> _cookieStore.addCookie(newCookie);_
> _localContext.setAttribute(HttpClientContext.COOKIE_STORE,
> cookieStore);_
>
> _stub._getServiceClient().getOptions().setProperty("CACHED_HTTP_STATE",
> localContext);_
>
>
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Assigned] (AXIS2-6045) NPE after upgrade to 1.8.2
[ https://issues.apache.org/jira/browse/AXIS2-6045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Lazarski reassigned AXIS2-6045: -- Assignee: Robert Lazarski > NPE after upgrade to 1.8.2 > -- > > Key: AXIS2-6045 > URL: https://issues.apache.org/jira/browse/AXIS2-6045 > Project: Axis2 > Issue Type: Bug > Components: kernel, wsdl >Affects Versions: 1.8.2 >Reporter: k >Assignee: Robert Lazarski >Priority: Critical > Fix For: 2.0.0 > > Attachments: axis2_npe.PNG > > > Side effect of AXIS2-6033 which introduced this call, without checking > "definition" for null: > [https://github.com/apache/axis-axis2-java-core/blob/master/modules/kernel/src/org/apache/axis2/description/AxisService.java#L1173] > > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Resolved] (AXIS2-6045) NPE after upgrade to 1.8.2
[ https://issues.apache.org/jira/browse/AXIS2-6045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Lazarski resolved AXIS2-6045. Resolution: Fixed This commit checks for null on the 'definition' var: https://github.com/apache/axis-axis2-java-core/commit/e33ddfdd9d20d6ae80c440421c3dc4dfd3cbb2c9 > NPE after upgrade to 1.8.2 > -- > > Key: AXIS2-6045 > URL: https://issues.apache.org/jira/browse/AXIS2-6045 > Project: Axis2 > Issue Type: Bug > Components: kernel, wsdl >Affects Versions: 1.8.2 >Reporter: k >Assignee: Robert Lazarski >Priority: Critical > Fix For: 2.0.0 > > Attachments: axis2_npe.PNG > > > Side effect of AXIS2-6033 which introduced this call, without checking > "definition" for null: > [https://github.com/apache/axis-axis2-java-core/blob/master/modules/kernel/src/org/apache/axis2/description/AxisService.java#L1173] > > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Updated] (AXIS2-6045) NPE after upgrade to 1.8.2
[ https://issues.apache.org/jira/browse/AXIS2-6045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Lazarski updated AXIS2-6045: --- Fix Version/s: 2.0.0 > NPE after upgrade to 1.8.2 > -- > > Key: AXIS2-6045 > URL: https://issues.apache.org/jira/browse/AXIS2-6045 > Project: Axis2 > Issue Type: Bug > Components: kernel, wsdl >Affects Versions: 1.8.2 >Reporter: k >Priority: Critical > Fix For: 2.0.0 > > Attachments: axis2_npe.PNG > > > Side effect of AXIS2-6033 which introduced this call, without checking > "definition" for null: > [https://github.com/apache/axis-axis2-java-core/blob/master/modules/kernel/src/org/apache/axis2/description/AxisService.java#L1173] > > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5955) Code generator plugin for Eclipse 2018-12 doesn't work
[
https://issues.apache.org/jira/browse/AXIS2-5955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17926986#comment-17926986
]
Steven DH commented on AXIS2-5955:
--
Regarding my build issues, I should have been clearer, I was building the
entire project.
* Missing JAXWS stuff:
{noformat}
[INFO] -< org.apache.axis2:axis2-ant-plugin >--
[INFO] Building Apache Axis2 - tool - Ant Plugin 2.0.0-SNAPSHOT [48/83]
[INFO] [ jar ]-
[INFO]
(snip)
[INFO] --- maven-antrun-plugin:3.1.0:run (default) @ axis2-ant-plugin ---
[INFO] Executing tasks
[WARNING] [echo] Generating extraclasses*.wsdl
[WARNING] Unable to instantiate serviceBuilderClass
org.apache.axis2.jaxws.framework.JAXWSServiceBuilderExtension , error:
org.apache.axis2.jaxws.framework.JAXWSServiceBuilderExtension
java.lang.ClassNotFoundException:
org.apache.axis2.jaxws.framework.JAXWSServiceBuilderExtension
at org.apache.tools.ant.AntClassLoader.findClassInComponents
(AntClassLoader.java:1402)
at org.apache.tools.ant.AntClassLoader.findClass (AntClassLoader.java:1357)
at org.apache.tools.ant.AntClassLoader.loadClass (AntClassLoader.java:1112)
at java.lang.ClassLoader.loadClass (ClassLoader.java:525)
at java.lang.Class.forName0 (Native Method)
at java.lang.Class.forName (Class.java:375)
at org.apache.axis2.util.Loader.loadClass (Loader.java:261)
at org.apache.axis2.deployment.AxisConfigBuilder.processDeployers
(AxisConfigBuilder.java:435)
at org.apache.axis2.deployment.AxisConfigBuilder.populateConfig
(AxisConfigBuilder.java:275)
at
org.apache.axis2.context.ConfigurationContextFactory.createBasicConfigurationContext
(ConfigurationContextFactory.java:343)
at
org.apache.axis2.context.ConfigurationContextFactory.createDefaultConfigurationContext
(ConfigurationContextFactory.java:330)
at org.apache.ws.java2wsdl.Java2WSDLBuilder.
(Java2WSDLBuilder.java:121)
at org.apache.ws.java2wsdl.Java2WSDLCodegenEngine.
(Java2WSDLCodegenEngine.java:54)
at org.apache.axis2.tool.ant.Java2WSDLTask.execute (Java2WSDLTask.java:281)
at org.apache.tools.ant.UnknownElement.execute (UnknownElement.java:299)
at jdk.internal.reflect.GeneratedMethodAccessor34.invoke (Unknown Source)
at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:569)
at org.apache.tools.ant.dispatch.DispatchUtils.execute
(DispatchUtils.java:99)
at org.apache.tools.ant.Task.perform (Task.java:350)
at org.apache.tools.ant.Target.execute (Target.java:449)
at org.apache.tools.ant.Target.performTasks (Target.java:470)
at org.apache.tools.ant.Project.executeSortedTargets (Project.java:1401)
at org.apache.tools.ant.Project.executeTarget (Project.java:1374)
at org.apache.maven.plugins.antrun.AntRunMojo.execute (AntRunMojo.java:297)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
(DefaultBuildPluginManager.java:137)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:210)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:156)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:148)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:81)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
(SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:77)
at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:569)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
(Launcher.java:282)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch
(Launcher.java:225)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
(Launcher.java:406)
at org.codehaus.plexus.classworlds.launcher.Launcher.main
(Launcher.java:347)
[WARNI
[jira] [Commented] (AXIS2-5955) Code generator plugin for Eclipse 2018-12 doesn't work
[
https://issues.apache.org/jira/browse/AXIS2-5955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17926978#comment-17926978
]
Steven DH commented on AXIS2-5955:
--
Unfortunately, I couldn't get the plugin installed. Manual installation
instructions like
[these|https://stackoverflow.com/questions/31553376/eclipse-how-to-install-a-plugin-manually]
failed. I installed Eclipse itself as a snap, so I can't put it in a
'dropins' map. Then I tried the debugging instructions, that yielded:
{quote}g! ss axis2
"Framework is launched."
id State Bundle
g! install
[file:/tmp/org.apache.axis2.eclipse.codegen.plugin_2.0.0.SNAPSHOT.jar|file:///tmp/org.apache.axis2.eclipse.codegen.plugin_2.0.0.SNAPSHOT.jar]
Bundle ID: 3383
g! ss axis2
"Framework is launched."
id State Bundle
3383 INSTALLED org.apache.axis2.eclipse.codegen.plugin_2.0.0.SNAPSHOT
g! start 3383
org.osgi.framework.BundleException: Could not resolve module:
org.apache.axis2.eclipse.codegen.plugin [3383]
Unresolved requirement: Import-Package: android.os
g!
{quote}
The Eclipse plugin installation instructions look quite old to me ("at least
Java 1.5"). Is the plugin code old too? For what it's worth, I found
[https://github.com/eclipse-platform/eclipse.platform/blob/master/docs/FAQ/The_Official_Eclipse_FAQs.md]
in my search for installation instructions and more info, it's not very easy
to find links to current documentation.
> Code generator plugin for Eclipse 2018-12 doesn't work
> --
>
> Key: AXIS2-5955
> URL: https://issues.apache.org/jira/browse/AXIS2-5955
> Project: Axis2
> Issue Type: Bug
> Components: codegen
>Affects Versions: 1.7.9
> Environment: Windows 7 64bits
> Eclipse:
> Version: 2018-12 (4.10.0)
> Build id: 20181214-0600
> java -version:
> java version "1.8.0_60"
> Java(TM) SE Runtime Environment (build 1.8.0_60-b27)
> Java HotSpot(TM) 64-Bit Server VM (build 25.60-b23, mixed mode)
>Reporter: EMERSON MARTINEZ PEPPINELLI
>Assignee: Robert Lazarski
>Priority: Major
> Fix For: 2.0.0
>
> Attachments: contextMenu.PNG
>
>
> I installed the latest version released of code generator plugin for Eclipse,
> but the plugin option doesn't appear at "new=>Select Wizard" in Eclipse menu
> context.
> Why this occur?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5955) Code generator plugin for Eclipse 2018-12 doesn't work
[ https://issues.apache.org/jira/browse/AXIS2-5955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17926938#comment-17926938 ] Robert Lazarski commented on AXIS2-5955: Thanks [~stevendh] , I just made a commit to add the axis2-jaxws jar to the Eclipse codegen plugin zip file - can you please try again? Not sure on that second error, do you see a stack trace? > Code generator plugin for Eclipse 2018-12 doesn't work > -- > > Key: AXIS2-5955 > URL: https://issues.apache.org/jira/browse/AXIS2-5955 > Project: Axis2 > Issue Type: Bug > Components: codegen >Affects Versions: 1.7.9 > Environment: Windows 7 64bits > Eclipse: > Version: 2018-12 (4.10.0) > Build id: 20181214-0600 > java -version: > java version "1.8.0_60" > Java(TM) SE Runtime Environment (build 1.8.0_60-b27) > Java HotSpot(TM) 64-Bit Server VM (build 25.60-b23, mixed mode) >Reporter: EMERSON MARTINEZ PEPPINELLI >Assignee: Robert Lazarski >Priority: Major > Fix For: 2.0.0 > > Attachments: contextMenu.PNG > > > I installed the latest version released of code generator plugin for Eclipse, > but the plugin option doesn't appear at "new=>Select Wizard" in Eclipse menu > context. > Why this occur? -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Updated] (AXIS2-5788) ConfigurationContext.getServiceGroupContext(id) always touches the id - ("Observer Effect")
[
https://issues.apache.org/jira/browse/AXIS2-5788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Lazarski updated AXIS2-5788:
---
Fix Version/s: 2.0.1
> ConfigurationContext.getServiceGroupContext(id) always touches the id -
> ("Observer Effect")
> ---
>
> Key: AXIS2-5788
> URL: https://issues.apache.org/jira/browse/AXIS2-5788
> Project: Axis2
> Issue Type: Bug
> Components: kernel
>Affects Versions: 1.7.3
> Environment: ANY
>Reporter: Jeff Thomas
>Priority: Major
> Fix For: 2.0.1
>
>
> Currently it is not possibel to get a ServiceGroupContext from the
> ConfigurationContext without forcing a touch to the 'lastTouchedTime'.
> This prevents us from performing our own checks against the lastTouchedTime
> because it is always set to the System time ("Observer Effect" - by observing
> the system, we change the system).
> I would propose a second API method which would allow retrieval of the
> ServiceGroupContext by id without touching the lastTouchedTime.
> Here my proposed code change:
> {code:java}
>/**
> * Returns a ServiceGroupContext object associated with the specified ID
> from the internal table.
> *
> * If found, the returned {@code ServiceGroupContext} will be touched
> with the current system time.
> *
> * @param serviceGroupCtxId The ID string associated with the
> ServiceGroupContext object
> * @return The ServiceGroupContext object, or {@code null} if not found
> */
> public ServiceGroupContext getServiceGroupContext(String
> serviceGroupCtxId) {
> return getServiceGroupContext(serviceGroupCtxId, true);
> }
>/**
> * Returns a ServiceGroupContext object associated with the specified ID
> from the internal table.
> *
> * @param serviceGroupCtxId The ID string associated with the
> ServiceGroupContext object
> * @param touchServiceGroupContext if {@code true} the retrieved {@code
> ServiceGroupContext} will be touched on
> *retrieval; otherwise, {@code false}.
> * @return the ServiceGroupContext object, or {@code null} if not found
> */
> public ServiceGroupContext getServiceGroupContext(String
> serviceGroupCtxId, boolean touchServiceGroupContext) {
> if (serviceGroupCtxId == null) {
> // Hashtables require non-null key-value pairs
> return null;
> }
> ServiceGroupContext serviceGroupContext = null;
> if (serviceGroupContextMap != null) {
> serviceGroupContext
> =serviceGroupContextMap.get(serviceGroupCtxId);
> if (serviceGroupContext != null && touchServiceGroupContext) {
> serviceGroupContext.touch();
> } else {
> serviceGroupContext =applicationSessionServiceGroupContexts
> .get(serviceGroupCtxId);
> if (serviceGroupContext != null && touchServiceGroupContext) {
> serviceGroupContext.touch();
> }
> }
> }
>
> return serviceGroupContext;
>
> }
> {code}
> Side note: the javadoc of getServiceGroupContextIDs is incorrect. The method
> returns a String[] array of ids and not a hashmap of ServiceGroupContexts.
> {code:java}
>/**
> * Gets all service groups in the system.
> *
> * @return Returns hashmap of ServiceGroupContexts.
> */
> public String[] getServiceGroupContextIDs() {
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5788) ConfigurationContext.getServiceGroupContext(id) always touches the id - ("Observer Effect")
[
https://issues.apache.org/jira/browse/AXIS2-5788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17926961#comment-17926961
]
Robert Lazarski commented on AXIS2-5788:
I looked at this and it changes some fundamental code, and it is very near the
2.0.0 release date.
So, I will work on this early in the 2.0.1 cycle. I'd like it to go thru more
testing than would happen now.
> ConfigurationContext.getServiceGroupContext(id) always touches the id -
> ("Observer Effect")
> ---
>
> Key: AXIS2-5788
> URL: https://issues.apache.org/jira/browse/AXIS2-5788
> Project: Axis2
> Issue Type: Bug
> Components: kernel
>Affects Versions: 1.7.3
> Environment: ANY
>Reporter: Jeff Thomas
>Priority: Major
> Fix For: 2.0.1
>
>
> Currently it is not possibel to get a ServiceGroupContext from the
> ConfigurationContext without forcing a touch to the 'lastTouchedTime'.
> This prevents us from performing our own checks against the lastTouchedTime
> because it is always set to the System time ("Observer Effect" - by observing
> the system, we change the system).
> I would propose a second API method which would allow retrieval of the
> ServiceGroupContext by id without touching the lastTouchedTime.
> Here my proposed code change:
> {code:java}
>/**
> * Returns a ServiceGroupContext object associated with the specified ID
> from the internal table.
> *
> * If found, the returned {@code ServiceGroupContext} will be touched
> with the current system time.
> *
> * @param serviceGroupCtxId The ID string associated with the
> ServiceGroupContext object
> * @return The ServiceGroupContext object, or {@code null} if not found
> */
> public ServiceGroupContext getServiceGroupContext(String
> serviceGroupCtxId) {
> return getServiceGroupContext(serviceGroupCtxId, true);
> }
>/**
> * Returns a ServiceGroupContext object associated with the specified ID
> from the internal table.
> *
> * @param serviceGroupCtxId The ID string associated with the
> ServiceGroupContext object
> * @param touchServiceGroupContext if {@code true} the retrieved {@code
> ServiceGroupContext} will be touched on
> *retrieval; otherwise, {@code false}.
> * @return the ServiceGroupContext object, or {@code null} if not found
> */
> public ServiceGroupContext getServiceGroupContext(String
> serviceGroupCtxId, boolean touchServiceGroupContext) {
> if (serviceGroupCtxId == null) {
> // Hashtables require non-null key-value pairs
> return null;
> }
> ServiceGroupContext serviceGroupContext = null;
> if (serviceGroupContextMap != null) {
> serviceGroupContext
> =serviceGroupContextMap.get(serviceGroupCtxId);
> if (serviceGroupContext != null && touchServiceGroupContext) {
> serviceGroupContext.touch();
> } else {
> serviceGroupContext =applicationSessionServiceGroupContexts
> .get(serviceGroupCtxId);
> if (serviceGroupContext != null && touchServiceGroupContext) {
> serviceGroupContext.touch();
> }
> }
> }
>
> return serviceGroupContext;
>
> }
> {code}
> Side note: the javadoc of getServiceGroupContextIDs is incorrect. The method
> returns a String[] array of ids and not a hashmap of ServiceGroupContexts.
> {code:java}
>/**
> * Gets all service groups in the system.
> *
> * @return Returns hashmap of ServiceGroupContexts.
> */
> public String[] getServiceGroupContextIDs() {
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Assigned] (AXIS2-5788) ConfigurationContext.getServiceGroupContext(id) always touches the id - ("Observer Effect")
[
https://issues.apache.org/jira/browse/AXIS2-5788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Lazarski reassigned AXIS2-5788:
--
Assignee: Robert Lazarski
> ConfigurationContext.getServiceGroupContext(id) always touches the id -
> ("Observer Effect")
> ---
>
> Key: AXIS2-5788
> URL: https://issues.apache.org/jira/browse/AXIS2-5788
> Project: Axis2
> Issue Type: Bug
> Components: kernel
>Affects Versions: 1.7.3
> Environment: ANY
>Reporter: Jeff Thomas
>Assignee: Robert Lazarski
>Priority: Major
> Fix For: 2.0.1
>
>
> Currently it is not possibel to get a ServiceGroupContext from the
> ConfigurationContext without forcing a touch to the 'lastTouchedTime'.
> This prevents us from performing our own checks against the lastTouchedTime
> because it is always set to the System time ("Observer Effect" - by observing
> the system, we change the system).
> I would propose a second API method which would allow retrieval of the
> ServiceGroupContext by id without touching the lastTouchedTime.
> Here my proposed code change:
> {code:java}
>/**
> * Returns a ServiceGroupContext object associated with the specified ID
> from the internal table.
> *
> * If found, the returned {@code ServiceGroupContext} will be touched
> with the current system time.
> *
> * @param serviceGroupCtxId The ID string associated with the
> ServiceGroupContext object
> * @return The ServiceGroupContext object, or {@code null} if not found
> */
> public ServiceGroupContext getServiceGroupContext(String
> serviceGroupCtxId) {
> return getServiceGroupContext(serviceGroupCtxId, true);
> }
>/**
> * Returns a ServiceGroupContext object associated with the specified ID
> from the internal table.
> *
> * @param serviceGroupCtxId The ID string associated with the
> ServiceGroupContext object
> * @param touchServiceGroupContext if {@code true} the retrieved {@code
> ServiceGroupContext} will be touched on
> *retrieval; otherwise, {@code false}.
> * @return the ServiceGroupContext object, or {@code null} if not found
> */
> public ServiceGroupContext getServiceGroupContext(String
> serviceGroupCtxId, boolean touchServiceGroupContext) {
> if (serviceGroupCtxId == null) {
> // Hashtables require non-null key-value pairs
> return null;
> }
> ServiceGroupContext serviceGroupContext = null;
> if (serviceGroupContextMap != null) {
> serviceGroupContext
> =serviceGroupContextMap.get(serviceGroupCtxId);
> if (serviceGroupContext != null && touchServiceGroupContext) {
> serviceGroupContext.touch();
> } else {
> serviceGroupContext =applicationSessionServiceGroupContexts
> .get(serviceGroupCtxId);
> if (serviceGroupContext != null && touchServiceGroupContext) {
> serviceGroupContext.touch();
> }
> }
> }
>
> return serviceGroupContext;
>
> }
> {code}
> Side note: the javadoc of getServiceGroupContextIDs is incorrect. The method
> returns a String[] array of ids and not a hashmap of ServiceGroupContexts.
> {code:java}
>/**
> * Gets all service groups in the system.
> *
> * @return Returns hashmap of ServiceGroupContexts.
> */
> public String[] getServiceGroupContextIDs() {
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Updated] (AXIS2-6061) Axis2 client parses soap envolope in case of a http-404
[
https://issues.apache.org/jira/browse/AXIS2-6061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Lazarski updated AXIS2-6061:
---
Fix Version/s: 2.0.1
(was: 2.0.0)
> Axis2 client parses soap envolope in case of a http-404
> ---
>
> Key: AXIS2-6061
> URL: https://issues.apache.org/jira/browse/AXIS2-6061
> Project: Axis2
> Issue Type: Bug
> Components: transports
>Affects Versions: 1.8.2
>Reporter: Manfred Weiss
>Assignee: Robert Lazarski
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.0.1
>
>
> If the server returns a 404 with HTML, the client tries to parse a soap
> envelope and fails with:
> {code:java}
> com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character 'd' (code
> 100) after ' I believe the problem was introduced with this commit:
> [https://github.com/apache/axis-axis2-java-core/commit/93d54beb5186803ea7dcb4a806c88d9ae2ea774f]
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-6061) Axis2 client parses soap envolope in case of a http-404
[
https://issues.apache.org/jira/browse/AXIS2-6061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17926963#comment-17926963
]
Robert Lazarski commented on AXIS2-6061:
Are you able to include a stack trace?
I see that you included a GitHub PR however it breaks the unit tests.
That commit was to fix this issue:
AXIS2-5999 Return HTTP 404 instead 500 on 'The service cannot be found'
I'd like to find a way to do both.
> Axis2 client parses soap envolope in case of a http-404
> ---
>
> Key: AXIS2-6061
> URL: https://issues.apache.org/jira/browse/AXIS2-6061
> Project: Axis2
> Issue Type: Bug
> Components: transports
>Affects Versions: 1.8.2
>Reporter: Manfred Weiss
>Assignee: Robert Lazarski
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.0.1
>
>
> If the server returns a 404 with HTML, the client tries to parse a soap
> envelope and fails with:
> {code:java}
> com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character 'd' (code
> 100) after ' I believe the problem was introduced with this commit:
> [https://github.com/apache/axis-axis2-java-core/commit/93d54beb5186803ea7dcb4a806c88d9ae2ea774f]
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Updated] (AXIS2-5901) Redundant conditions in an if statement
[
https://issues.apache.org/jira/browse/AXIS2-5901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Lazarski updated AXIS2-5901:
---
Fix Version/s: 2.0.0
> Redundant conditions in an if statement
> ---
>
> Key: AXIS2-5901
> URL: https://issues.apache.org/jira/browse/AXIS2-5901
> Project: Axis2
> Issue Type: Bug
> Components: kernel
>Reporter: songwanging
>Priority: Minor
> Fix For: 2.0.0
>
>
> Our tool DeepTect has detected a piece of buggy code snippet, in which the if
> branch has exactly the same conditions.
> Path:
> axis2-java/modules/kernel/src/org/apache/axis2/context/OperationContext.java
> {code:java}
> if (mepString.equals(WSDL2Constants.MEP_URI_OUT_ONLY)
> || mepString.equals(WSDL2Constants.MEP_URI_OUT_ONLY)
> || ((mepString.equals(WSDL2Constants.MEP_URI_OUT_IN)
> || mepString.equals(WSDL2Constants.MEP_URI_OUT_IN))
> && !isComplete)) {
>...
> }
> {code}
> In the above code snippet, the if statement contains the same conditions.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Resolved] (AXIS2-5901) Redundant conditions in an if statement
[
https://issues.apache.org/jira/browse/AXIS2-5901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Lazarski resolved AXIS2-5901.
Resolution: Fixed
Thanks for the contribution. The duplicate code has been removed.
> Redundant conditions in an if statement
> ---
>
> Key: AXIS2-5901
> URL: https://issues.apache.org/jira/browse/AXIS2-5901
> Project: Axis2
> Issue Type: Bug
> Components: kernel
>Reporter: songwanging
>Priority: Minor
> Fix For: 2.0.0
>
>
> Our tool DeepTect has detected a piece of buggy code snippet, in which the if
> branch has exactly the same conditions.
> Path:
> axis2-java/modules/kernel/src/org/apache/axis2/context/OperationContext.java
> {code:java}
> if (mepString.equals(WSDL2Constants.MEP_URI_OUT_ONLY)
> || mepString.equals(WSDL2Constants.MEP_URI_OUT_ONLY)
> || ((mepString.equals(WSDL2Constants.MEP_URI_OUT_IN)
> || mepString.equals(WSDL2Constants.MEP_URI_OUT_IN))
> && !isComplete)) {
>...
> }
> {code}
> In the above code snippet, the if statement contains the same conditions.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5955) Code generator plugin for Eclipse 2018-12 doesn't work
[ https://issues.apache.org/jira/browse/AXIS2-5955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17926917#comment-17926917 ] Steven DH commented on AXIS2-5955: -- So this issue would be the last one standing in the way for Axis2 2.0.0? I'm an Eclipse user, I can help. But it's been a while since I worked with the codebase. I did 'mvn clean' and 'mvn install' in the freshly pulled root directory, so now I should try install the file modules/tool/axis2-eclipse-codegen-plugin/target/axis2.eclipse.codegen.plugin-2.0.0-SNAPSHOT-dist.zip, is that right? (I got a stack trace while building the Ant plugin: class not found: org.apache.axis2.jaxws.framework.JAXWSServiceBuilderExtension. And the PausingHandlerExecutionTest in "integration" failed the first time I did 'mvn install', but succeeded on the second try. Should I elaborate?) > Code generator plugin for Eclipse 2018-12 doesn't work > -- > > Key: AXIS2-5955 > URL: https://issues.apache.org/jira/browse/AXIS2-5955 > Project: Axis2 > Issue Type: Bug > Components: codegen >Affects Versions: 1.7.9 > Environment: Windows 7 64bits > Eclipse: > Version: 2018-12 (4.10.0) > Build id: 20181214-0600 > java -version: > java version "1.8.0_60" > Java(TM) SE Runtime Environment (build 1.8.0_60-b27) > Java HotSpot(TM) 64-Bit Server VM (build 25.60-b23, mixed mode) >Reporter: EMERSON MARTINEZ PEPPINELLI >Assignee: Robert Lazarski >Priority: Major > Fix For: 2.0.0 > > Attachments: contextMenu.PNG > > > I installed the latest version released of code generator plugin for Eclipse, > but the plugin option doesn't appear at "new=>Select Wizard" in Eclipse menu > context. > Why this occur? -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Assigned] (AXIS2-5762) Add Transport Ports to MessageContext
[ https://issues.apache.org/jira/browse/AXIS2-5762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Lazarski reassigned AXIS2-5762: -- Assignee: Robert Lazarski > Add Transport Ports to MessageContext > - > > Key: AXIS2-5762 > URL: https://issues.apache.org/jira/browse/AXIS2-5762 > Project: Axis2 > Issue Type: Improvement > Components: kernel, transports >Affects Versions: 1.7.1 >Reporter: Ciprian Florescu >Assignee: Robert Lazarski >Priority: Major > Attachments: addremoteandtransportaddresstomessagecontext.diff > > > At the moment Axis2 is only recording the transport IP addresses in the > kernel MessageContext. > This patch is also recording the REMOTE_PORT and TRANSPORT_PORT in through > the transport-http module. > I have attached an unified diff of the change -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5762) Add Transport Ports to MessageContext
[ https://issues.apache.org/jira/browse/AXIS2-5762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17926890#comment-17926890 ] Robert Lazarski commented on AXIS2-5762: We are about to release 2.0.0 with httpclient5 and that API no longer supports getRemotePort(). I see it here in httpclient4 and its not deprecated but the latest httpclient5 source has nothing like it. I was trying to apply this patch but I couldn't easily figure out how to get the remote port in httpclient 5. https://www.javadoc.io/static/org.apache.httpcomponents/httpcore/4.4.6/org/apache/http/HttpInetConnection.html#getRemoteAddress() > Add Transport Ports to MessageContext > - > > Key: AXIS2-5762 > URL: https://issues.apache.org/jira/browse/AXIS2-5762 > Project: Axis2 > Issue Type: Improvement > Components: kernel, transports >Affects Versions: 1.7.1 >Reporter: Ciprian Florescu >Priority: Major > Attachments: addremoteandtransportaddresstomessagecontext.diff > > > At the moment Axis2 is only recording the transport IP addresses in the > kernel MessageContext. > This patch is also recording the REMOTE_PORT and TRANSPORT_PORT in through > the transport-http module. > I have attached an unified diff of the change -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Updated] (AXIS2-5762) Add Transport Ports to MessageContext
[ https://issues.apache.org/jira/browse/AXIS2-5762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Lazarski updated AXIS2-5762: --- Fix Version/s: 2.0.1 > Add Transport Ports to MessageContext > - > > Key: AXIS2-5762 > URL: https://issues.apache.org/jira/browse/AXIS2-5762 > Project: Axis2 > Issue Type: Improvement > Components: kernel, transports >Affects Versions: 1.7.1 >Reporter: Ciprian Florescu >Assignee: Robert Lazarski >Priority: Major > Fix For: 2.0.1 > > Attachments: addremoteandtransportaddresstomessagecontext.diff > > > At the moment Axis2 is only recording the transport IP addresses in the > kernel MessageContext. > This patch is also recording the REMOTE_PORT and TRANSPORT_PORT in through > the transport-http module. > I have attached an unified diff of the change -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Updated] (AXIS2-6076) OSGI jakarta support is unmaintained
[ https://issues.apache.org/jira/browse/AXIS2-6076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Lazarski updated AXIS2-6076: --- Fix Version/s: 2.0.1 (was: 2.0.0) > OSGI jakarta support is unmaintained > > > Key: AXIS2-6076 > URL: https://issues.apache.org/jira/browse/AXIS2-6076 > Project: Axis2 > Issue Type: Task >Reporter: Robert Lazarski >Assignee: Robert Lazarski >Priority: Major > Fix For: 2.0.1 > > > Currently in the main pom.xml, the OSGI unit tests are commented out due to a > lack of dependencies supporting jakarta - however, maven-bundle-plugin > version 6.0 was just released. > I tried out httpclient5-osgi and httpcore5-osgi as well as some other deps, > however the Felix project deps for OSGI show problems on jakarta, and many of > the deps haven't been updated for years. > This issue is to track progress on Axis2 with OSGI. The unit tests are > commented out, and without community PR's or at least some guidance from > users of OSGI, this code will be triaged out of Axis2 release 2.0.0 and a fix > ETA is indefinite - because of the complexity and lack of users who are > helping maintain it. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Resolved] (AXIS2-6059) Improve logging by default
[
https://issues.apache.org/jira/browse/AXIS2-6059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Lazarski resolved AXIS2-6059.
Resolution: Fixed
Fixed in our GitHub repo.
> Improve logging by default
> --
>
> Key: AXIS2-6059
> URL: https://issues.apache.org/jira/browse/AXIS2-6059
> Project: Axis2
> Issue Type: Improvement
> Components: kernel
>Affects Versions: 1.8.2
>Reporter: Leonid Rozenblyum
>Assignee: Robert Lazarski
>Priority: Major
> Fix For: 2.0.0
>
>
> In case we instantiate an Axis2 client without the *axis2-jaxws* dependency,
> we get the warning:
> {panel:title=Warning}
> WARNING: Unable to instantiate deployer
> org.apache.axis2.deployment.ServiceDeployer; see debug logs for more details
> {panel}
> It's caused by the block of code (424-451) in
> org.apache.axis2.deployment.AxisConfigBuilder
>
> {code:java}
> for (Iterator itr = element.getChildrenWithName(new QName(
> TAG_SERVICE_BUILDER_EXTENSION)); itr.hasNext() {
> ...
> catch (Throwable e) {
> log.warn("Unable to instantiate deployer " + deployerClassName
> + "; see debug logs for more details");
> log.debug(e.getMessage(), e);
> continue;
> }{code}
> and is confusing: actually we were able to instantiate the deployer, we just
> were unable to load an extension for it.
> The actual extension not being found is
> {code:java}
> org.apache.axis2.jaxws.framework.JAXWSServiceBuilderExtension{code}
> It should be explicitly clear that the
> {code:java}
> ServiceDeployer {code}
> is ok.
> It caused questions like this:
> [https://stackoverflow.com/questions/55965081/unable-to-instantiate-deployer-org-apache-axis2-deployment-servicedeployer-how-t]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
