[PR] Bump tomcat.version from 11.0.3 to 11.0.4 [axis-axis2-java-core]

2025-02-17 Thread via GitHub


dependabot[bot] opened a new pull request, #855:
URL: https://github.com/apache/axis-axis2-java-core/pull/855

   Bumps `tomcat.version` from 11.0.3 to 11.0.4.
   Updates `org.apache.tomcat:tomcat-tribes` from 11.0.3 to 11.0.4
   
   Updates `org.apache.tomcat:tomcat-juli` from 11.0.3 to 11.0.4
   
   
   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-5955) Code generator plugin for Eclipse 2018-12 doesn't work

2025-02-17 Thread Robert Lazarski (Jira)


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

Robert Lazarski commented on AXIS2-5955:


Seems like I accidentally dropped my commit for a fix on the class issue, could 
you please try again? 

Good suggestion to remove the plugin from the downloads page, so I did that. 

> 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.1
>
> 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-5858) soap:address location's value is wrong with IPv6

2025-02-17 Thread Robert Lazarski (Jira)


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

Robert Lazarski updated AXIS2-5858:
---
Fix Version/s: 2.0.1
   (was: 2.0.0)

> soap:address location's value is wrong  with IPv6
> -
>
> Key: AXIS2-5858
> URL: https://issues.apache.org/jira/browse/AXIS2-5858
> Project: Axis2
>  Issue Type: Bug
>Affects Versions: 1.6.2
>Reporter: yeqing Li
>Assignee: Robert Lazarski
>Priority: Critical
> Fix For: 2.0.1
>
> Attachments: IPv4.PNG, IPv6.PNG
>
>   Original Estimate: 12h
>  Remaining Estimate: 12h
>
> When I access the wsdl url with IPv4,it worked well,but if with IPv6,the 
> soap:address location’s value is wrong.
> IPv6: [fe80::a9a8:18be:bb91:8787]
> Please check the 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] [Commented] (AXIS2-6051) Axis2 Future Roadmap in keeping up with new Java Versions

2025-02-17 Thread Robert Lazarski (Jira)


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

Robert Lazarski commented on AXIS2-6051:


[~cortlepp] thanks for finding that, I upgraded the pom.xml files to use 
jakarta.transaction-api instead. 

> 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