[jira] [Resolved] (AXIS2-6037) Install axis2-plugin-intelliJ error
[
https://issues.apache.org/jira/browse/AXIS2-6037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Lazarski resolved AXIS2-6037.
Resolution: Fixed
This issue was fixed in this commit as described by the PR in the comments:
https://github.com/apache/axis-axis2-java-core/commit/dd7468386a9b45244974bb12f758d6e7cf76d0e3
> Install axis2-plugin-intelliJ error
> ---
>
> Key: AXIS2-6037
> URL: https://issues.apache.org/jira/browse/AXIS2-6037
> Project: Axis2
> Issue Type: Bug
> Components: ide plugins
>Affects Versions: 1.8.0
> Environment: Ultimate IntelliJ 2022.1.2 Build #IU-221.5787.30
>Reporter: Damijan Kavs
>Assignee: Robert Lazarski
>Priority: Critical
> Fix For: 2.0.0
>
> Attachments: IntelliJ-plugin-install-error.jpg
>
>
> _*What steps will reproduce the issue?*_
> 1. download axis2-idea-plugin-1.8.0.zip from [Apache
> Downloads|https://www.apache.org/dyn/closer.lua/axis/axis2/java/core/1.8.0/axis2-idea-plugin-1.8.0.zip]
> 2. Open IntelliJ ultimate edition (2022.1.2 - latest current version), select
> File-> Settings...
> 3. select Plugins -> "install Plugin from disk" select downloaded zip
> "axis2-idea-plugin-1.8.0.zip"
> _*What is the expected result?*_
> Installing axis2 plugin for IntelliJ.
> _*What happens instead?*_
> {_}Error "Plugin 'Axis2 IDEA tools' (version '1.0') is not compatible with
> the current version of the IDE, because it requires build 2000 or newer but
> the current build is IU-221.5787.30{_}".
> _(see attachment)_
--
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-5971) AxisServlet.processURLRequest use content-type header instead of accept
[
https://issues.apache.org/jira/browse/AXIS2-5971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Lazarski reassigned AXIS2-5971:
--
Assignee: Robert Lazarski
> AxisServlet.processURLRequest use content-type header instead of accept
> ---
>
> Key: AXIS2-5971
> URL: https://issues.apache.org/jira/browse/AXIS2-5971
> Project: Axis2
> Issue Type: Bug
> Components: kernel
>Affects Versions: 1.7.8
>Reporter: Marti Pamies Sola
>Assignee: Robert Lazarski
>Priority: Minor
>
> Class org.apache.axis2.transport.http.AxisServlet has the following code
> {code:java}
> // public void processURLRequest() throws IOException,
> ServletException {
> try {
> RESTUtil.processURLRequest(messageContext,
> response.getOutputStream(),
> request.getContentType());
> this.checkResponseWritten();
> } catch (AxisFault e) {
> setResponseState(messageContext, response);
> processFault(e);
> }
> closeStaxBuilder(messageContext);}
> {code}
> As fas as I understand, this code is involed when diong REST and recieving an
> URL request without body.
> The problem is that this method looks for request.getContentType() instead of
> request Accept Header to determine to messageFormater to use. This behaviour
> make content type mandatory for URL client request which has no sense, as it
> is a header to indicate server response content type.
--
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-5971) AxisServlet.processURLRequest use content-type header instead of accept
[
https://issues.apache.org/jira/browse/AXIS2-5971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Lazarski updated AXIS2-5971:
---
Fix Version/s: 2.0.0
> AxisServlet.processURLRequest use content-type header instead of accept
> ---
>
> Key: AXIS2-5971
> URL: https://issues.apache.org/jira/browse/AXIS2-5971
> Project: Axis2
> Issue Type: Bug
> Components: kernel
>Affects Versions: 1.7.8
>Reporter: Marti Pamies Sola
>Assignee: Robert Lazarski
>Priority: Minor
> Fix For: 2.0.0
>
>
> Class org.apache.axis2.transport.http.AxisServlet has the following code
> {code:java}
> // public void processURLRequest() throws IOException,
> ServletException {
> try {
> RESTUtil.processURLRequest(messageContext,
> response.getOutputStream(),
> request.getContentType());
> this.checkResponseWritten();
> } catch (AxisFault e) {
> setResponseState(messageContext, response);
> processFault(e);
> }
> closeStaxBuilder(messageContext);}
> {code}
> As fas as I understand, this code is involed when diong REST and recieving an
> URL request without body.
> The problem is that this method looks for request.getContentType() instead of
> request Accept Header to determine to messageFormater to use. This behaviour
> make content type mandatory for URL client request which has no sense, as it
> is a header to indicate server response content type.
--
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-5968) ConverterUtil.compare fails when comparing against very small numbers
[
https://issues.apache.org/jira/browse/AXIS2-5968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Lazarski updated AXIS2-5968:
---
Affects Version/s: 2.0.0
(was: 1.7.9)
> ConverterUtil.compare fails when comparing against very small numbers
> -
>
> Key: AXIS2-5968
> URL: https://issues.apache.org/jira/browse/AXIS2-5968
> Project: Axis2
> Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: Alan Morgan
>Assignee: Robert Lazarski
>Priority: Minor
>
> ConverterUtil.compare(0L, "-9223372036854775808") incorrectly returns a
> negative number. The implementation:
> {{public static long compare(long longValue, String value) {}}
> {{ return longValue - Long.parseLong(value);}}
> {{ }}}
> suffers from overflow if "value" is very small. The same bug exists for
> other compare methods.
--
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-5964) AbstractJSONMessageFormatter NOT using CharSetEncoding when reding Json string Bytes
[
https://issues.apache.org/jira/browse/AXIS2-5964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Lazarski reassigned AXIS2-5964:
--
Assignee: Robert Lazarski
> AbstractJSONMessageFormatter NOT using CharSetEncoding when reding Json
> string Bytes
>
>
> Key: AXIS2-5964
> URL: https://issues.apache.org/jira/browse/AXIS2-5964
> Project: Axis2
> Issue Type: Bug
> Components: json
>Affects Versions: 1.7.8, 1.7.9
>Reporter: Marti Pamies Sola
>Assignee: Robert Lazarski
>Priority: Minor
>
> AbstractJSONMessageFormatter is not using input OMOutputFormat when getting
> bytes from the Json string to be written. This happens both on .getBytes and
> writeTo methods.
> {code:java}
> // if (jsonToWrite != null) {
> out.write(jsonToWrite.getBytes());
> } else {
> {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-5964) AbstractJSONMessageFormatter NOT using CharSetEncoding when reding Json string Bytes
[
https://issues.apache.org/jira/browse/AXIS2-5964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Lazarski updated AXIS2-5964:
---
Fix Version/s: 2.0.0
> AbstractJSONMessageFormatter NOT using CharSetEncoding when reding Json
> string Bytes
>
>
> Key: AXIS2-5964
> URL: https://issues.apache.org/jira/browse/AXIS2-5964
> Project: Axis2
> Issue Type: Bug
> Components: json
>Affects Versions: 1.7.8, 1.7.9
>Reporter: Marti Pamies Sola
>Assignee: Robert Lazarski
>Priority: Minor
> Fix For: 2.0.0
>
>
> AbstractJSONMessageFormatter is not using input OMOutputFormat when getting
> bytes from the Json string to be written. This happens both on .getBytes and
> writeTo methods.
> {code:java}
> // if (jsonToWrite != null) {
> out.write(jsonToWrite.getBytes());
> } else {
> {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-5964) AbstractJSONMessageFormatter NOT using CharSetEncoding when reding Json string Bytes
[
https://issues.apache.org/jira/browse/AXIS2-5964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17897315#comment-17897315
]
Robert Lazarski commented on AXIS2-5964:
Actually, I'm not 100% sure "format" is not null always, so the code turned out
this way:
if (format != null && format.getCharSetEncoding() != null) {
out.write(jsonToWrite.getBytes(format.getCharSetEncoding()));
} else {
out.write(jsonToWrite.getBytes());
}
> AbstractJSONMessageFormatter NOT using CharSetEncoding when reding Json
> string Bytes
>
>
> Key: AXIS2-5964
> URL: https://issues.apache.org/jira/browse/AXIS2-5964
> Project: Axis2
> Issue Type: Bug
> Components: json
>Affects Versions: 1.7.8, 1.7.9
>Reporter: Marti Pamies Sola
>Assignee: Robert Lazarski
>Priority: Minor
> Fix For: 2.0.0
>
>
> AbstractJSONMessageFormatter is not using input OMOutputFormat when getting
> bytes from the Json string to be written. This happens both on .getBytes and
> writeTo methods.
> {code:java}
> // if (jsonToWrite != null) {
> out.write(jsonToWrite.getBytes());
> } else {
> {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] [Resolved] (AXIS2-5963) wsdl2java renames the schema
[
https://issues.apache.org/jira/browse/AXIS2-5963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Lazarski resolved AXIS2-5963.
Resolution: Invalid
> wsdl2java renames the schema
>
>
> Key: AXIS2-5963
> URL: https://issues.apache.org/jira/browse/AXIS2-5963
> Project: Axis2
> Issue Type: Bug
> Components: codegen, wsdl
>Reporter: Gustavo Pedrosa
>Priority: Major
>
> wsdl2java always renames the schema to "schema1.xsd" instead of keep the
> original name, so in applications that has more than one jar, all the others
> schemas will replaced after the build assembly.
> Command used:
> {code:bash}
> ../apache-cxf-3.3.3/bin/wsdl2java -client -clientjar santander_cobranca.jar
> -impl -asyncMethods -validate -verbose
> 'https://ymbcash.santander.com.br/ymbsrv/CobrancaV3EndpointService/CobrancaV3EndpointService.wsdl'
> {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] [Comment Edited] (AXIS2-5963) wsdl2java renames the schema
[
https://issues.apache.org/jira/browse/AXIS2-5963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17897316#comment-17897316
]
Robert Lazarski edited comment on AXIS2-5963 at 11/12/24 1:18 AM:
--
The description mentions cxf and this is the Jira board for axis2 - a separate
project though both are Apache projects - so I am going to mark this as
invalid.
was (Author: robertlazarski):
The description mentions cxf and this is the Jira board for axis2 - a separate
project though both are under Apache projects - so I am going to mark this as
invalid.
> wsdl2java renames the schema
>
>
> Key: AXIS2-5963
> URL: https://issues.apache.org/jira/browse/AXIS2-5963
> Project: Axis2
> Issue Type: Bug
> Components: codegen, wsdl
>Reporter: Gustavo Pedrosa
>Priority: Major
>
> wsdl2java always renames the schema to "schema1.xsd" instead of keep the
> original name, so in applications that has more than one jar, all the others
> schemas will replaced after the build assembly.
> Command used:
> {code:bash}
> ../apache-cxf-3.3.3/bin/wsdl2java -client -clientjar santander_cobranca.jar
> -impl -asyncMethods -validate -verbose
> 'https://ymbcash.santander.com.br/ymbsrv/CobrancaV3EndpointService/CobrancaV3EndpointService.wsdl'
> {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] [Resolved] (AXIS2-5964) AbstractJSONMessageFormatter NOT using CharSetEncoding when reding Json string Bytes
[
https://issues.apache.org/jira/browse/AXIS2-5964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Lazarski resolved AXIS2-5964.
Resolution: Fixed
> AbstractJSONMessageFormatter NOT using CharSetEncoding when reding Json
> string Bytes
>
>
> Key: AXIS2-5964
> URL: https://issues.apache.org/jira/browse/AXIS2-5964
> Project: Axis2
> Issue Type: Bug
> Components: json
>Affects Versions: 1.7.8, 1.7.9
>Reporter: Marti Pamies Sola
>Assignee: Robert Lazarski
>Priority: Minor
> Fix For: 2.0.0
>
>
> AbstractJSONMessageFormatter is not using input OMOutputFormat when getting
> bytes from the Json string to be written. This happens both on .getBytes and
> writeTo methods.
> {code:java}
> // if (jsonToWrite != null) {
> out.write(jsonToWrite.getBytes());
> } else {
> {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-5964) AbstractJSONMessageFormatter NOT using CharSetEncoding when reding Json string Bytes
[
https://issues.apache.org/jira/browse/AXIS2-5964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17897309#comment-17897309
]
Robert Lazarski commented on AXIS2-5964:
Thank you for mentioning this. This is how the code looks now. You said "both
on .getBytes and writeTo methods " however since the referenced code is in the
writeTo method, it wasn't clear to me and I see nothing else in this code that
is missing the encoding.
I am marking the issue as fixed, though it can be reopened if something is
missing.
String encoding = format.getCharSetEncoding();
if (encoding != null) {
out.write(jsonToWrite.getBytes(encoding));
} else {
out.write(jsonToWrite.getBytes());
}
> AbstractJSONMessageFormatter NOT using CharSetEncoding when reding Json
> string Bytes
>
>
> Key: AXIS2-5964
> URL: https://issues.apache.org/jira/browse/AXIS2-5964
> Project: Axis2
> Issue Type: Bug
> Components: json
>Affects Versions: 1.7.8, 1.7.9
>Reporter: Marti Pamies Sola
>Assignee: Robert Lazarski
>Priority: Minor
> Fix For: 2.0.0
>
>
> AbstractJSONMessageFormatter is not using input OMOutputFormat when getting
> bytes from the Json string to be written. This happens both on .getBytes and
> writeTo methods.
> {code:java}
> // if (jsonToWrite != null) {
> out.write(jsonToWrite.getBytes());
> } else {
> {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-5963) wsdl2java renames the schema
[
https://issues.apache.org/jira/browse/AXIS2-5963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17897316#comment-17897316
]
Robert Lazarski commented on AXIS2-5963:
The description mentions cxf and this is the Jira board for axis2 - a separate
project though both are under Apache projects - so I am going to mark this as
invalid.
> wsdl2java renames the schema
>
>
> Key: AXIS2-5963
> URL: https://issues.apache.org/jira/browse/AXIS2-5963
> Project: Axis2
> Issue Type: Bug
> Components: codegen, wsdl
>Reporter: Gustavo Pedrosa
>Priority: Major
>
> wsdl2java always renames the schema to "schema1.xsd" instead of keep the
> original name, so in applications that has more than one jar, all the others
> schemas will replaced after the build assembly.
> Command used:
> {code:bash}
> ../apache-cxf-3.3.3/bin/wsdl2java -client -clientjar santander_cobranca.jar
> -impl -asyncMethods -validate -verbose
> 'https://ymbcash.santander.com.br/ymbsrv/CobrancaV3EndpointService/CobrancaV3EndpointService.wsdl'
> {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-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:all-tabpanel ] Robert Lazarski updated AXIS2-5955: --- Fix Version/s: 2.0.0 > 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-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:all-tabpanel ] Robert Lazarski reassigned AXIS2-5955: -- Assignee: Robert Lazarski > 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 > 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
[PR] Bump tomcat.version from 11.0.0 to 11.0.1 [axis-axis2-java-core]
dependabot[bot] opened a new pull request, #804: URL: https://github.com/apache/axis-axis2-java-core/pull/804 Bumps `tomcat.version` from 11.0.0 to 11.0.1. Updates `org.apache.tomcat:tomcat-tribes` from 11.0.0 to 11.0.1 Updates `org.apache.tomcat:tomcat-juli` from 11.0.0 to 11.0.1 Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -- 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
[jira] [Commented] (AXIS2-5991) Rewrite axis2 spring pojo guide so it uses maven for deps
[ https://issues.apache.org/jira/browse/AXIS2-5991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17897246#comment-17897246 ] Robert Lazarski commented on AXIS2-5991: We don't support TCCL anymore with Spring. The jars are all updated now for jakarta. If someone wants to contribute the conversion to Maven for the guide, they can send a link to a Github PR. This is open source and we are all volunteers. I'll leave this issue open for such an effort as it would benefit new users - I doubt existing users will upgrade though some might. > Rewrite axis2 spring pojo guide so it uses maven for deps > - > > Key: AXIS2-5991 > URL: https://issues.apache.org/jira/browse/AXIS2-5991 > Project: Axis2 > Issue Type: Bug >Reporter: Robert Lazarski >Assignee: Robert Lazarski >Priority: Major > > The jars used in the guide below, are very outdated and are not maven based > downloads. > The guide is based on Ant. With minimal effort, the guide could be written > for maven so that dependencies are auto resolved. > Also, the guide uses the TCCL to load spring. That's more complex than need > be for a simple guide. Loading spring via the web.xml is simpler and matches > standard practice. > https://axis.apache.org/axis2/java/core/docs/pojoguide.html > -- 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] [Closed] (AXIS2-5989) Spring sample code is not working with the TCCL in composite mode
[ https://issues.apache.org/jira/browse/AXIS2-5989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Lazarski closed AXIS2-5989. -- Resolution: Won't Fix We don't support TCCL with Spring anymore because of performance issues that impacted everyone else that didn't use it. > Spring sample code is not working with the TCCL in composite mode > - > > Key: AXIS2-5989 > URL: https://issues.apache.org/jira/browse/AXIS2-5989 > Project: Axis2 > Issue Type: Bug >Reporter: Robert Lazarski >Priority: Major > > This sample using the tccl, is not able to find the spring config loaded by > the SpringInit class. The problem is in ApplicationContextUtil. > [https://axis.apache.org/axis2/java/core/docs/pojoguide.html#springpojows] > > -- 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-5975) More specific Runtime Exceptions instead of just "Input values do not follow defined XSD restrictions"
[ https://issues.apache.org/jira/browse/AXIS2-5975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Lazarski updated AXIS2-5975: --- Fix Version/s: 2.0.0 > More specific Runtime Exceptions instead of just "Input values do not follow > defined XSD restrictions" > -- > > Key: AXIS2-5975 > URL: https://issues.apache.org/jira/browse/AXIS2-5975 > Project: Axis2 > Issue Type: Improvement >Reporter: Lino Lendi >Assignee: Robert Lazarski >Priority: Major > Fix For: 2.0.0 > > > As of now the created function checks the XSD restrictions and if they are > not met throws a RuntimeException: > > throw new java.lang.RuntimeException( > "Input values do not follow defined XSD restrictions"); > > As we know more about the restrictions, since we check them, it would be > nice, if these additional informations could also be added to the message of > the exceptions. > For example if the test was: > if ((param != null) && (param.length < 1)) , > instead of just: "Input values do not follow defined XSD restrictions", we > could say more about the param, "Input values do not follow defined XSD > restrictions; param.length < 1". -- 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-5978) provide better error message on error with trailing spaces
[ https://issues.apache.org/jira/browse/AXIS2-5978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Lazarski resolved AXIS2-5978. Resolution: Implemented > provide better error message on error with trailing spaces > -- > > Key: AXIS2-5978 > URL: https://issues.apache.org/jira/browse/AXIS2-5978 > Project: Axis2 > Issue Type: Improvement > Components: databinding >Affects Versions: 1.7.8 >Reporter: Ralf Hauser >Priority: Major > > When there is a trailing space, a useless error message is given via > AxisFault. > Assume you should have entered "a" in a field and happend to give "a ", you > see > > IllegalArgumentException " data=[a ]" > > suggestions: > 1) subclass IllegalArgumentException with 2 extra fields: > a) the calling class name (generated for the xsd field by wsdl2java), must be > handed over to > org.apache.axis2.databinding.utils.ConverterUtil.convertToToken() as a > optional 2nd argument > b) a reference to the explanation as per > [https://www.w3.org/TR/xmlschema-2/#token] > should be set in org.apache.axis2.databinding.types.setValue() when > !Token.isValid(stValue) > > see also AXIS2-5575 -- 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-5975) More specific Runtime Exceptions instead of just "Input values do not follow defined XSD restrictions"
[ https://issues.apache.org/jira/browse/AXIS2-5975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Lazarski reassigned AXIS2-5975: -- Assignee: Robert Lazarski > More specific Runtime Exceptions instead of just "Input values do not follow > defined XSD restrictions" > -- > > Key: AXIS2-5975 > URL: https://issues.apache.org/jira/browse/AXIS2-5975 > Project: Axis2 > Issue Type: Improvement >Reporter: Lino Lendi >Assignee: Robert Lazarski >Priority: Major > > As of now the created function checks the XSD restrictions and if they are > not met throws a RuntimeException: > > throw new java.lang.RuntimeException( > "Input values do not follow defined XSD restrictions"); > > As we know more about the restrictions, since we check them, it would be > nice, if these additional informations could also be added to the message of > the exceptions. > For example if the test was: > if ((param != null) && (param.length < 1)) , > instead of just: "Input values do not follow defined XSD restrictions", we > could say more about the param, "Input values do not follow defined XSD > restrictions; param.length < 1". -- 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-6017) Is Axis2 vulnerable to Log4shell?
[ https://issues.apache.org/jira/browse/AXIS2-6017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Lazarski resolved AXIS2-6017. Resolution: Fixed > Is Axis2 vulnerable to Log4shell? > - > > Key: AXIS2-6017 > URL: https://issues.apache.org/jira/browse/AXIS2-6017 > Project: Axis2 > Issue Type: Bug >Affects Versions: 2.0.0 >Reporter: Maarten Engels >Priority: Major > Labels: Security > > We all recently learned about the Log4j vulnerability “Log4shell”. As the > axis framework uses Log4j, is axis vulnerable? Do you have any mitigation > available? -- 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-6021) change the wsdl url of a soap service in java
[
https://issues.apache.org/jira/browse/AXIS2-6021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Lazarski reassigned AXIS2-6021:
--
Assignee: Robert Lazarski
> change the wsdl url of a soap service in java
> -
>
> Key: AXIS2-6021
> URL: https://issues.apache.org/jira/browse/AXIS2-6021
> Project: Axis2
> Issue Type: Bug
>Reporter: kais alkotamy
>Assignee: Robert Lazarski
>Priority: Major
>
> dears I have developed a soap webservice using java and axis2 and a top down
> approach now when I deploy the service on tomcat8 server the location url of
> the service is being like:
>
> {{"serverIP:port/projectName/services/serviceName"}}
> is there a way to change it to
>
> {{"serverIP:port/projectName/subdomain/anothersubdomain"}}
> I have tried editing the web.xml and axis2.xml note the the the originale
> wsdl have the location tag : "serverIP:port/projectName/servicename"
> therefore I have tried to set the "useOriginalwsdl" to false and set the
> "modifyUserWSDLPortAddress" to false in service.xml file that gave the
> orginal tag location but the when I am trying to use endpoint from SoapUI
> program I can not reach it.
> please any way to change the location of the wsdl
> of a way to redirect the url
> I have aslo tried to redirect using a url-rewrite library but does not wrok
> for the client
> thanks in advance
>
> {{}}
--
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-6017) Is Axis2 vulnerable to Log4shell?
[ https://issues.apache.org/jira/browse/AXIS2-6017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Lazarski updated AXIS2-6017: --- Affects Version/s: 2.0.0 (was: 1.8.0) > Is Axis2 vulnerable to Log4shell? > - > > Key: AXIS2-6017 > URL: https://issues.apache.org/jira/browse/AXIS2-6017 > Project: Axis2 > Issue Type: Bug >Affects Versions: 2.0.0 >Reporter: Maarten Engels >Priority: Major > Labels: Security > > We all recently learned about the Log4j vulnerability “Log4shell”. As the > axis framework uses Log4j, is axis vulnerable? Do you have any mitigation > available? -- 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-6021) change the wsdl url of a soap service in java
[
https://issues.apache.org/jira/browse/AXIS2-6021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17897244#comment-17897244
]
Robert Lazarski commented on AXIS2-6021:
[~kais1995] did you ever to find the right params to get the result you needed?
I thought about the problem and it is pretty complex. I'd like to document how
you would do what you describe, and if you found a solution that would be
ideal.
> change the wsdl url of a soap service in java
> -
>
> Key: AXIS2-6021
> URL: https://issues.apache.org/jira/browse/AXIS2-6021
> Project: Axis2
> Issue Type: Bug
>Reporter: kais alkotamy
>Priority: Major
>
> dears I have developed a soap webservice using java and axis2 and a top down
> approach now when I deploy the service on tomcat8 server the location url of
> the service is being like:
>
> {{"serverIP:port/projectName/services/serviceName"}}
> is there a way to change it to
>
> {{"serverIP:port/projectName/subdomain/anothersubdomain"}}
> I have tried editing the web.xml and axis2.xml note the the the originale
> wsdl have the location tag : "serverIP:port/projectName/servicename"
> therefore I have tried to set the "useOriginalwsdl" to false and set the
> "modifyUserWSDLPortAddress" to false in service.xml file that gave the
> orginal tag location but the when I am trying to use endpoint from SoapUI
> program I can not reach it.
> please any way to change the location of the wsdl
> of a way to redirect the url
> I have aslo tried to redirect using a url-rewrite library but does not wrok
> for the client
> thanks in advance
>
> {{}}
--
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-5929) REST GET request using Accept HTTP Header to indicate JSON, does not working
[
https://issues.apache.org/jira/browse/AXIS2-5929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Lazarski resolved AXIS2-5929.
Resolution: Fixed
I applied the patch - just changed javax to jakarta - I didn't see the Github
PR until I applied the patch so I will close that.
> REST GET request using Accept HTTP Header to indicate JSON, does not working
>
>
> Key: AXIS2-5929
> URL: https://issues.apache.org/jira/browse/AXIS2-5929
> Project: Axis2
> Issue Type: Improvement
> Components: json, transports
>Affects Versions: 2.0.0
>Reporter: Marti Pamies Sola
>Priority: Minor
> Attachments: AbstractJSONOMBuilder.java,
> AbstractJSONOMBuilder.java.patch
>
>
> I am implementing a REST services according to [HL7
> FHIR|[http://www.hl7.org/fhir/],] that must be able to return a Patient
> resource, both on xml or json, depending on http Accept header, and I am not
> able to implement it using axis.
> Request is:
> *
> {color:#505050}[http://localhost:8080/opencdefhirserver/services/FHIR/Binary/4295642378]{color}
> * {color:#505050}Accept =application/fhir+json
> {color}
> Where, FHIR is my service; Binary is the axis2 operation to be executed
> (mapping to a FHIR resource); and {color:#505050}4295642378{color} the
> resource id.
> The exception I get is:
> "{_}No JSON message received through HTTP GET or POST"{_}
> I've been reviewing source code and I guess the issue comes from this
> fragment of code at org.apache.axis2.json.AbstractJSONOMBuilder.java line 85:
>
> {code:java}
> // if ((index = requestURL.indexOf("=")) > 0) {
> jsonString = requestURL.substring(index + 1);
> reader = new StringReader(jsonString);
> } else {
> throw new AxisFault("No JSON message received through HTTP
> GET or POST");
> }
> {code}
> As it only accepts parameters as Query String, and when not provided it raise
> an exception.
> Also once previous code fixed, I realize that axis does not take care or
> Accept HTTP Header, so GET Requests where not payload is provided and so no
> contentType is specified, are just able to return as XML, but not JSON.
> See org.apache.axis2.transport.http.util.RESTUtil line 144
> {code:java}
> if (contentType == null || "".equals(contentType)) {
> contentType = HTTPConstants.MEDIA_TYPE_X_WWW_FORM;
> } {code}
>
> I've implemented and improvement on both classes in order to be able to mange
> those request and done the Pull Request.
> Hope useful.
> Thanks,
> Martí
>
--
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
Re: [PR] Resolved https://issues.apache.org/jira/browse/AXIS2-5929 [axis-axis2-java-core]
robertlazarski closed pull request #388: Resolved https://issues.apache.org/jira/browse/AXIS2-5929 URL: https://github.com/apache/axis-axis2-java-core/pull/388 -- 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
Re: [PR] Resolved https://issues.apache.org/jira/browse/AXIS2-5929 [axis-axis2-java-core]
robertlazarski commented on PR #388: URL: https://github.com/apache/axis-axis2-java-core/pull/388#issuecomment-2469462775 I am closing this since I applied the patch in the Jira - this would have been easier if I saw it in time, so thanks for that. -- 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
