dependabot[bot] opened a new pull request, #26:
URL: https://github.com/apache/mina-vysper/pull/26
Bumps
[org.springframework:spring-context](https://github.com/spring-projects/spring-framework)
from 4.3.24.RELEASE to 5.2.22.RELEASE.
Release notes
Sourced from https://github.com
dependabot[bot] opened a new pull request, #25:
URL: https://github.com/apache/mina-vysper/pull/25
Bumps
[org.eclipse.jetty:jetty-webapp](https://github.com/eclipse/jetty.project) from
8.1.3.v20120416 to 9.4.33.v20201020.
Release notes
Sourced from https://github.com/eclipse
dependabot[bot] opened a new pull request, #24:
URL: https://github.com/apache/mina-vysper/pull/24
Bumps [spring-webmvc](https://github.com/spring-projects/spring-framework)
from 4.3.24.RELEASE to 5.2.20.RELEASE.
Release notes
Sourced from https://github.com/spring-projects/spring
dependabot[bot] opened a new pull request, #23:
URL: https://github.com/apache/mina-vysper/pull/23
Bumps jackrabbit-core from 1.5.3 to 2.1.0.
[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name
dependabot[bot] opened a new pull request, #22:
URL: https://github.com/apache/mina-vysper/pull/22
Bumps tomcat-catalina from 7.0.27 to 7.0.81.
[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name
PrivacyDragon edited a comment on issue #21:
URL: https://github.com/apache/mina-vysper/issues/21#issuecomment-940991704
I did something with keytools to create another, selfsigned, certificate
that has a password and that kinda worked. I was able to get a client
connected. But I had yo
PrivacyDragon commented on issue #21:
URL: https://github.com/apache/mina-vysper/issues/21#issuecomment-940991704
I did something with keytools to create another, selfsigned, certificate
that has a password and that kinda worked. I was able to get a client
connected. But I had yo
PrivacyDragon commented on issue #21:
URL: https://github.com/apache/mina-vysper/issues/21#issuecomment-940988682
With my own certificate :
`Exception in thread "main"
org.springframework.beans.factory.BeanCreationException: Error creating bean
with name 'server' d
PrivacyDragon removed a comment on issue #21:
URL: https://github.com/apache/mina-vysper/issues/21#issuecomment-940983118
This is the error with my own certificate
`12:50:00,723 | WARN | org.apache.vysper.mina.XmppIoHandlerAdapter | error
caught on transportation layer
PrivacyDragon commented on issue #21:
URL: https://github.com/apache/mina-vysper/issues/21#issuecomment-940983118
This is the error with my own certificate
`12:50:00,723 | WARN | org.apache.vysper.mina.XmppIoHandlerAdapter | error
caught on transportation layer
PrivacyDragon commented on issue #21:
URL: https://github.com/apache/mina-vysper/issues/21#issuecomment-940888478
This is the error with the standard settings
`06:38:18,115 | WARN | org.apache.vysper.mina.XmppIoHandlerAdapter | error
caught on transportation layer
PrivacyDragon opened a new issue #21:
URL: https://github.com/apache/mina-vysper/issues/21
When I run the server with the standard certificate stuff, the server
successfully starts and is reachable.
Though the TLS-handshakes fail.
And when I try to configure vysper to use my
kkawai commented on issue #15:
URL: https://github.com/apache/mina-vysper/issues/15#issuecomment-875457357
i got the same issue Error: Could not find or load main class
org.apache.vysper.spring.ServerMain
--
This is an automated message from the Apache Git Service.
To respond to the
enexusde commented on issue #13:
URL: https://github.com/apache/mina-vysper/issues/13#issuecomment-758664016
Resolved by
https://github.com/apache/mina-vysper/commit/dbfedf822349f53e1848297145634079b204988f?branch=dbfedf822349f53e1848297145634079b204988f&diff=uni
enexusde closed issue #13:
URL: https://github.com/apache/mina-vysper/issues/13
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
reda-alaoui commented on issue #16:
URL: https://github.com/apache/mina-vysper/issues/16#issuecomment-756648462
This project is undergoing a massive refactoring that I had to pause because
of a lack of time.
If you want to make contributions, you are welcome.
I don't think rele
reda-alaoui commented on issue #16:
URL: https://github.com/apache/mina-vysper/issues/16#issuecomment-756648462
This project is undergoing a massive refactoring that I had to pause because
of a lack of time.
If you want to make contributions, you are welcome.
I don't think rele
karimhm commented on issue #16:
URL: https://github.com/apache/mina-vysper/issues/16#issuecomment-756178027
> Hi,
>
> I don't think the current version is working.
> Did you test it?
No
Thi
reda-alaoui commented on issue #13:
URL: https://github.com/apache/mina-vysper/issues/13#issuecomment-756124692
Please contribute with a pull request
This is an automated message from the Apache Git Service.
To respond to
reda-alaoui commented on pull request #20:
URL: https://github.com/apache/mina-vysper/pull/20#issuecomment-756124172
Thank you !
This is an automated message from the Apache Git Service.
To respond to the message, please log
reda-alaoui merged pull request #20:
URL: https://github.com/apache/mina-vysper/pull/20
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
reda-alaoui commented on issue #16:
URL: https://github.com/apache/mina-vysper/issues/16#issuecomment-756123517
Hi,
I don't think the current version is working.
Did you test it?
This is an automated message
karimhm opened a new pull request #20:
URL: https://github.com/apache/mina-vysper/pull/20
According to [**RFC
6120**](https://xmpp.org/rfcs/rfc6120.html#streams-attr-xmllang) the `xml:lang`
must conform to the language identifier format defined in [**BCP 47, RFC
5646**](https
karimhm edited a comment on issue #16:
URL: https://github.com/apache/mina-vysper/issues/16#issuecomment-756111583
> The development is always here?
`Apache Mina Vysper` seems to be still under active development the latest
[commit](https://github.com/apache/mina-vysper/com
karimhm commented on issue #16:
URL: https://github.com/apache/mina-vysper/issues/16#issuecomment-756111583
> The development is always here?
`Apache Mina Vysper` seems to be still under active development he latest
[commit](https://github.com/apache/mina-vysper/com
Neustradamus opened a new issue #19:
URL: https://github.com/apache/mina-vysper/issues/19
Please add support of XEP-0443: XMPP Compliance Suites 2021:
https://xmpp.org/extensions/xep-0443.html
Which replaces:
- XEP-0423: XMPP Compliance Suites 2020:
https://xmpp.org/extensions
Neustradamus opened a new issue #18:
URL: https://github.com/apache/mina-vysper/issues/18
Can you add supports of :
- SCRAM-SHA-1
- SCRAM-SHA-1-PLUS
- SCRAM-SHA-224
- SCRAM-SHA-224-PLUS
- SCRAM-SHA-256
- SCRAM-SHA-256-PLUS
- SCRAM-SHA-384
- SCRAM-SHA-384-PLUS
Neustradamus opened a new issue #17:
URL: https://github.com/apache/mina-vysper/issues/17
Please add support of last RFCs.
About XMPP RFCs:
- https://tools.ietf.org/html/rfc3920 -> https://tools.ietf.org/html/rfc6120
to https://tools.ietf.org/html/rfc7590
- ht
Neustradamus commented on issue #16:
URL: https://github.com/apache/mina-vysper/issues/16#issuecomment-755799147
The development is always here?
This is an automated message from the Apache Git Service.
To respond to the
karimhm opened a new issue #16:
URL: https://github.com/apache/mina-vysper/issues/16
The latest published version is **0.7** and was released 10 years ago (on
*Feb 24, 2011*) and a lot of changes happened since. It will be a god idea to
release a new version so everyone can take advantage
garysheppardjr commented on issue #15:
URL: https://github.com/apache/mina-vysper/issues/15#issuecomment-668252881
This is no longer urgent for me, as I discovered the [Apache Vysper Embedded
in a WAR
demo](https://github.com/apache/mina-vysper/tree
garysheppardjr opened a new issue #15:
URL: https://github.com/apache/mina-vysper/issues/15
In
https://github.com/apache/mina-vysper/blob/685a690b3aa141f7ab9f275c8c29b0b043232dd4/README.md:
> A ready-to-run setup is created by the build in
> `dist/target/appass
reda-alaoui merged pull request #14: [SECURITY] Use HTTPS to resolve
dependencies in Maven Build
URL: https://github.com/apache/mina-vysper/pull/14
This is an automated message from the Apache Git Service.
To respond to the
JLLeitschuh opened a new pull request #14: [SECURITY] Use HTTPS to resolve
dependencies in Maven Build
URL: https://github.com/apache/mina-vysper/pull/14
[](https
Dirk Doerflinger created VYSPER-352:
---
Summary: Update hbase version to 2.2.2
Key: VYSPER-352
URL: https://issues.apache.org/jira/browse/VYSPER-352
Project: VYSPER
Issue Type: Dependency
enexusde commented on issue #13: TCPEndpoint not offering IoFilterChainBuilder
URL: https://github.com/apache/mina-vysper/issues/13#issuecomment-559588687
I think you could fix this by adding
this.filterChainBuilder = filterChainBuilder;
to the `start` method
enexusde opened a new issue #13: TCPEndpoint not offering IoFilterChainBuilder
URL: https://github.com/apache/mina-vysper/issues/13
```
TCPEndpoint endpoint = new TCPEndpointChainBuilder();
server = new XMPPServer(serverName);
server.addEndpoint(endpoint);
server.start
dependabot[bot] opened a new pull request #12: Bump httpclient from 4.2.5 to
4.3.6
URL: https://github.com/apache/mina-vysper/pull/12
Bumps httpclient from 4.2.5 to 4.3.6.
[
This is an automated message from the Apache Git Service.
To respond to the
reda-alaoui opened a new pull request #9: StanzaSessionContext should not have
precondition on ENCRYPTED state activation
URL: https://github.com/apache/mina-vysper/pull/9
This is an automated message from the Apache Git
reda-alaoui opened a new pull request #8: StateAwareProtocolWorker logic
prevents StanzaHandler proxying
URL: https://github.com/apache/mina-vysper/pull/8
This is the sequel of https://github.com/apache/mina-vysper/pull/7.
Proxyed core *StanzaHandler* like *StartTLSHandler* are
reda-alaoui opened a new pull request #7: Allow to override
ServerRuntimeContext creation in XMPPServer
URL: https://github.com/apache/mina-vysper/pull/7
In our vysper implementation, we need to manage JPA transactions and Spring
security.
Those are transversal feature relying on
reda-alaoui commented on issue #6: Allow override of the StanzaProcessor
URL: https://github.com/apache/mina-vysper/pull/6#issuecomment-515709456
Stanza are not always processed through a StanzaProcessor.
I keep looking for a better solution
reda-alaoui closed pull request #6: Allow override of the StanzaProcessor
URL: https://github.com/apache/mina-vysper/pull/6
This is an automated message from the Apache Git Service.
To respond to the message, please log on
reda-alaoui opened a new pull request #6: Allow override of the StanzaProcessor
URL: https://github.com/apache/mina-vysper/pull/6
In our vysper implementation, we need to manage JPA transactions and Spring
security.
Those are transversal feature relying on ThreadLocal.
In order
reda-alaoui opened a new pull request #5: Upgrade parent to org.apache:apache:21
URL: https://github.com/apache/mina-vysper/pull/5
This is an automated message from the Apache Git Service.
To respond to the message, please
reda-alaoui opened a new pull request #4: Turn ABOUT.txt into README.md
URL: https://github.com/apache/mina-vysper/pull/4
This is an automated message from the Apache Git Service.
To respond to the message, please log on to
reda-alaoui commented on issue #2: Upgrade mina-core to 2.0.21
URL: https://github.com/apache/mina-vysper/pull/2#issuecomment-515588313
Ping :)
This is an automated message from the Apache Git Service.
To respond to the
reda-alaoui opened a new pull request #3: Upgrade to Spring 4
URL: https://github.com/apache/mina-vysper/pull/3
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and
I've asked infra to delete it since it's read-only, I can't even merge any
PR...
https://issues.apache.org/jira/browse/INFRA-18795
Le jeu. 25 juil. 2019 à 08:42, Réda Housni Alaoui a
écrit :
> I created https://github.com/apache/vysper/pull/3 to inform of the old
> reposi
reda-alaoui opened a new pull request #2: Upgrade mina-core to 2.0.21
URL: https://github.com/apache/mina-vysper/pull/2
This is an automated message from the Apache Git Service.
To respond to the message, please log on to
gnodet merged pull request #1: Upgrade to java 8
URL: https://github.com/apache/mina-vysper/pull/1
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL
I created https://github.com/apache/vysper/pull/3 to inform of the old
repository deprecation.
I think it should be useful since it is currently the only one found via a
Google search.
Le jeu. 25 juil. 2019 à 08:33, Réda Housni Alaoui a
écrit :
> Done => https://github.com/apache/mina-
Done => https://github.com/apache/mina-vysper/pull/1
Le jeu. 25 juil. 2019 à 08:29, Réda Housni Alaoui a
écrit :
> Yeah of course.
> Doing it right now
>
> Le jeu. 25 juil. 2019 à 08:25, Guillaume Nodet a
> écrit :
>
>> I think the correct repository is
>>
reda-alaoui opened a new pull request #1: Upgrade to java 8
URL: https://github.com/apache/mina-vysper/pull/1
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and
Yeah of course.
Doing it right now
Le jeu. 25 juil. 2019 à 08:25, Guillaume Nodet a écrit :
> I think the correct repository is
>https://github.com/apache/mina-vysper
> Could you please recreate your PR on that one ?
>
> Le dim. 21 juil. 2019 à 13:47, Réda Housni Alaoui a
&g
I think the correct repository is
https://github.com/apache/mina-vysper
Could you please recreate your PR on that one ?
Le dim. 21 juil. 2019 à 13:47, Réda Housni Alaoui a
écrit :
> I created the pull request:
> https://github.com/apache/vysper/pull/2
>
> Le dim. 21 juil. 2019 à
Le dim. 21 juil. 2019 à 13:37, Réda Housni Alaoui a
écrit :
> Hi everyone,
>
> I recently discovered Vysper. I think this is exactly what I need as I want
> to use it to expose an existing chat application through XMPP.
> I need to add non jetty webapp support to Vysper.
> Th
Should we consider https://github.com/apache/vysper as deprecated?
--
*Réda Housni Alaoui*
I created the pull request:
https://github.com/apache/vysper/pull/2
Le dim. 21 juil. 2019 à 13:37, Réda Housni Alaoui a
écrit :
> Hi everyone,
>
> I recently discovered Vysper. I think this is exactly what I need as I
> want to use it to expose an existing chat application throu
Hi everyone,
I recently discovered Vysper. I think this is exactly what I need as I want
to use it to expose an existing chat application through XMPP.
I need to add non jetty webapp support to Vysper.
The project does not build on JDK 8 (java 5 currently). I started a fork to
upgrade the project
Le 16/07/2018 à 01:47, Reijhanniel Jearl Campos a écrit :
> Hi!
>
> I was recently working on a test that involves setting up an embedded XMPP
> server with Vysper, and Smack[1]. I encountered an issue[2] and posted on
> the Smack forum, and a developer pointed out that it mi
Hi!
I was recently working on a test that involves setting up an embedded XMPP
server with Vysper, and Smack[1]. I encountered an issue[2] and posted on
the Smack forum, and a developer pointed out that it might be a server
issue.
Has the Vysper project lost steam? The last commit was indeed 7
k"
>>
>> Modified:
>> mina/site/trunk/content/vysper-project/download_0.7.mdtext
>>
>> Modified: mina/site/trunk/content/vysper-project/download_0.7.mdtext
>> URL:
>> http://svn.apache.org/viewvc/mina/s
On 17 August 2016 at 15:00, wrote:
> Author: buildbot
> Date: Wed Aug 17 14:00:53 2016
> New Revision: 995313
>
> Log:
> Staging update by buildbot for mina
>
> Modified:
> websites/staging/mina/trunk/content/ (props changed)
> websites/staging/min
On 17 August 2016 at 15:00, wrote:
> Author: elecharny
> Date: Wed Aug 17 14:00:48 2016
> New Revision: 1756636
>
> URL: http://svn.apache.org/viewvc?rev=1756636&view=rev
> Log:
> Fixed a broken link"
>
> Modified:
> mina/site/trunk/content/vysper-p
Hi,
Are there any plans to implement creation of websockets using JSR 356 in
Vysper? I plan to use Vysper in our webapp, which runs in tomcat 8. The
current existing websocket implementation present in Vysper is based on the
old tomcat websocket api which is no longer supported in tomcat 8.
[
https://issues.apache.org/jira/browse/VYSPER-334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15372839#comment-15372839
]
Venugopal edited comment on VYSPER-334 at 7/12/16 1:02 PM:
--
[
https://issues.apache.org/jira/browse/VYSPER-334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Venugopal updated VYSPER-334:
-
Attachment: screenshot-1.png
> Plain.java doesn't decode correctly, error appears in multi-byte c
[
https://issues.apache.org/jira/browse/VYSPER-334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15372839#comment-15372839
]
Venugopal commented on VYSPER-334:
--
I too facing similar issue.i have commons-codec
[
https://issues.apache.org/jira/browse/VYSPER-351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lauri updated VYSPER-351:
-
Description:
This affects fetching vcard of a user in MUC.
Suggested patch is attched [^vysper-351.patch].
It
[
https://issues.apache.org/jira/browse/VYSPER-351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lauri updated VYSPER-351:
-
Attachment: vysper-351.patch
The patch.
Makes use of includeJidInItem(...) on presence broadcast
> NonAnonym
[
https://issues.apache.org/jira/browse/VYSPER-351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lauri updated VYSPER-351:
-
Description:
This affects fetching vcard of a user in MUC.
Suggested patch ( http://pastebin.com/2nMQ2Cbe
Lauri created VYSPER-351:
Summary: NonAnonymous and SemiAnonymous rooms do not expose real
jid on room join
Key: VYSPER-351
URL: https://issues.apache.org/jira/browse/VYSPER-351
Project: VYSPER
I am using strophe library in my web app to communicate with vysper xmpp
server and we want to allow user name to be in Chinese. But strophe is not
able to connect to vysper with Chinese user name and gives error stanza
as
. Is there any setting I need to do in strophe or vysper? Any help on
wutianbiao created VYSPER-350:
-
Summary: Newer to start a in-memery demo
Key: VYSPER-350
URL: https://issues.apache.org/jira/browse/VYSPER-350
Project: VYSPER
Issue Type: Question
Le 19/03/16 09:45, Praveen Prabhu a écrit :
> Hi,
> I have recently downloaded the source from the vysper svn trunk and have made
> it compatible with jdk 1.7.
> Also, a number of changes made:
> 1. Upgraded the deprecated DocumentSpecCompliantAnnot
Hi,
I have recently downloaded the source from the vysper svn trunk and have made
it compatible with jdk 1.7.
Also, a number of changes made:
1. Upgraded the deprecated DocumentSpecCompliantAnnotationFactory to
DocumentSpecCompliantAnnotationProcessor to support latest annotations
processor
[
https://issues.apache.org/jira/browse/VYSPER-349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
alexander zakshevskii updated VYSPER-349:
-
Description:
Please check "insertRequest" method of "BoshBacke
alexander zakshevskii created VYSPER-349:
Summary: New request is counted as "Resend" request
Key: VYSPER-349
URL: https://issues.apache.org/jira/browse/VYSPER-349
Proje
[
https://issues.apache.org/jira/browse/VYSPER-348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebb resolved VYSPER-348.
-
Resolution: Fixed
URL: http://svn.apache.org/r1678382
Log:
VYSPER-348 Syntax error in DOAP file
Modified
Sebb created VYSPER-348:
---
Summary: Syntax error in DOAP file
Key: VYSPER-348
URL: https://issues.apache.org/jira/browse/VYSPER-348
Project: VYSPER
Issue Type: Bug
Environment: http
rryl (Darryl)
wrote:
> Hi,
>
> When a client connects to Vysper server, it opens the stream . And
> typically when the client disconnects, it will close the stream with
> . However, I could not find a way for Vysper to send stream-close,
> e.g. in some e
Hi,
When a client connects to Vysper server, it opens the stream . And
typically when the client disconnects, it will close the stream with
. However, I could not find a way for Vysper to send stream-close, e.g. in
some error scenario. I can definitely send the and invoke
Hi guys,
so I tested all the mina sub-project with MINA 2.0.8, and beside the
change I suggested for SSHD, there is no error : tests are passing green.
I'll shortly start a vote for this release.
1 - 100 of 2911 matches
Mail list logo
