[
https://issues.apache.org/jira/browse/VYSPER-157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Fondermann resolved VYSPER-157.
-
Resolution: Cannot Reproduce
My internal contact subscription config was apparently
Components: core protocol
Reporter: Bernd Fondermann
If u1 sends message to u2 and ommits the from attribute, the server must add
it on outbound handling, so the receiver knows whos messaging him.
--
This message is automatically generated by JIRA.
-
You can reply to this email
[
https://issues.apache.org/jira/browse/VYSPER-165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Fondermann resolved VYSPER-165.
-
Resolution: Fixed
Unhandled missing/incomplete 'from' in outbound message stanzas
Reporter: Bernd Fondermann
Assignee: Bernd Fondermann
Due to the recent project split, we have more than one jar and classpath.
To allow for adding modules as runtime properties of ServerMain.java and to
allow storage provider registries to reference providers from other
[
https://issues.apache.org/jira/browse/VYSPER-167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Fondermann updated VYSPER-167:
Component/s: storage
Allow for adding of modules and storage providers by class name
Keep config files in one place
--
Key: VYSPER-168
URL: https://issues.apache.org/jira/browse/VYSPER-168
Project: VYSPER
Issue Type: Improvement
Reporter: Bernd Fondermann
Let's keep all config files
[
https://issues.apache.org/jira/browse/VYSPER-91?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Fondermann reassigned VYSPER-91:
--
Assignee: (was: Bernd Fondermann)
Implement Jabber Component Protocol (XEP-0114
Implement Ad-Hoc Commands XEP-0050
--
Key: VYSPER-169
URL: https://issues.apache.org/jira/browse/VYSPER-169
Project: VYSPER
Issue Type: New Feature
Components: extension
Reporter: Bernd
Reporter: Bernd Fondermann
Service Administration specifies Ad-hoc commands to admin the server (manage
users, sessions, roster, etc).
see http://xmpp.org/extensions/xep-0133.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue
[
https://issues.apache.org/jira/browse/VYSPER-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Fondermann resolved VYSPER-10.
Resolution: Fixed
implemented and in use.
Implement Service Discovery XEP-0030
[
https://issues.apache.org/jira/browse/VYSPER-167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Fondermann resolved VYSPER-167.
-
Resolution: Fixed
Allow for adding of modules and storage providers by class name
[
https://issues.apache.org/jira/browse/VYSPER-175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12743985#action_12743985
]
Bernd Fondermann commented on VYSPER-175:
-
what would collision mean
routing
Reporter: Bernd Fondermann
XMPP extensions provide storage for stanzas which are addressed to offline
recipients for delayed delivery.
Inbound delivery should provide a mechanism for those extensions to hook to.
--
This message is automatically generated by JIRA.
-
You can
Reporter: Bernd Fondermann
Message stanzas have sophisticed delivery rules, see draft-ietf-xmpp-3921bis-00
section 8.3.1.1. Message
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[
https://issues.apache.org/jira/browse/VYSPER-181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Fondermann updated VYSPER-181:
Description: Stanzas have sophisticed delivery rules, see
draft-ietf-xmpp-3921bis-00
[
https://issues.apache.org/jira/browse/VYSPER-179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Fondermann resolved VYSPER-179.
-
Resolution: Fixed
Deliver stanza to the highest priorized client
[
https://issues.apache.org/jira/browse/VYSPER-176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Fondermann reassigned VYSPER-176:
---
Assignee: Bernd Fondermann
Internally route stanzas to a component
[
https://issues.apache.org/jira/browse/VYSPER-172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Fondermann reopened VYSPER-172:
-
Assignee: Bernd Fondermann (was: Niklas Gustavsson)
let's take a different approach
[
https://issues.apache.org/jira/browse/VYSPER-172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12748758#action_12748758
]
Bernd Fondermann commented on VYSPER-172:
-
component: 'component' is a word from
[
https://issues.apache.org/jira/browse/VYSPER-172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Fondermann resolved VYSPER-172.
-
Resolution: Fixed
Allow modules to register for a subdomain
[
https://issues.apache.org/jira/browse/VYSPER-176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Fondermann resolved VYSPER-176.
-
Resolution: Fixed
Internally route stanzas to a component
[
https://issues.apache.org/jira/browse/VYSPER-6?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Fondermann resolved VYSPER-6.
---
Resolution: Fixed
Support Directed Presence
-
Key
[
https://issues.apache.org/jira/browse/VYSPER-24?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Fondermann resolved VYSPER-24.
Resolution: Fixed
Allow stanza handling without active session
Issue Type: Improvement
Components: extension
Reporter: Bernd Fondermann
Assignee: Bernd Fondermann
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[
https://issues.apache.org/jira/browse/VYSPER-183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Fondermann resolved VYSPER-183.
-
Resolution: Fixed
fix in r813348
Exception thrown
Reporter: Bernd Fondermann
Assignee: Bernd Fondermann
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[
https://issues.apache.org/jira/browse/VYSPER-184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12841740#action_12841740
]
Bernd Fondermann commented on VYSPER-184:
-
Oh Norman, I've already shamelessly
[
https://issues.apache.org/jira/browse/VYSPER-184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Fondermann resolved VYSPER-184.
-
Resolution: Fixed
bin packages land in server/core/target
Make build create pret
[
https://issues.apache.org/jira/browse/VYSPER-185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Fondermann reassigned VYSPER-185:
---
Assignee: Bernd Fondermann
Send unavailable on lost connection
[
https://issues.apache.org/jira/browse/VYSPER-185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Fondermann updated VYSPER-185:
Attachment: VYSPER-185.2.patch
Please see if this patch is behaving more correctly
[
https://issues.apache.org/jira/browse/VYSPER-186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12843456#action_12843456
]
Bernd Fondermann commented on VYSPER-186:
-
the described behavior is reproducible
[
https://issues.apache.org/jira/browse/VYSPER-186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Fondermann reassigned VYSPER-186:
---
Assignee: Bernd Fondermann
Roster contact receives available twice
[
https://issues.apache.org/jira/browse/VYSPER-186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Fondermann resolved VYSPER-186.
-
Resolution: Fixed
Roster contact receives available twice
[
https://issues.apache.org/jira/browse/VYSPER-185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Fondermann resolved VYSPER-185.
-
Resolution: Fixed
@Thomas: Thanks for helping with this improvment
Send unavailable
[
https://issues.apache.org/jira/browse/VYSPER-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Fondermann resolved VYSPER-23.
Resolution: Fixed
trunk is now on MINA2, yet pre-final
Upgrade to MINA 2.0
[
https://issues.apache.org/jira/browse/VYSPER-74?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Fondermann resolved VYSPER-74.
Resolution: Later
XMPP spec states we can savely ignore/override the client resource string
[
https://issues.apache.org/jira/browse/VYSPER-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Fondermann updated VYSPER-18:
---
Priority: Blocker (was: Major)
Recognize and act upon closing stream tag
[
https://issues.apache.org/jira/browse/VYSPER-179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Fondermann reopened VYSPER-179:
-
Deliver stanza to the highest priorized client
[
https://issues.apache.org/jira/browse/VYSPER-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12844139#action_12844139
]
Bernd Fondermann commented on VYSPER-179:
-
The current solution is not enough
[
https://issues.apache.org/jira/browse/VYSPER-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12844742#action_12844742
]
Bernd Fondermann commented on VYSPER-179:
-
the prev comment applies to message
[
https://issues.apache.org/jira/browse/VYSPER-179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Fondermann resolved VYSPER-179.
-
Resolution: Fixed
Deliver stanza to the highest priorized client
[
https://issues.apache.org/jira/browse/VYSPER-82?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Fondermann reassigned VYSPER-82:
--
Assignee: (was: Bernd Fondermann)
Namespace definitions aren't propagated
[
https://issues.apache.org/jira/browse/VYSPER-95?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12846846#action_12846846
]
Bernd Fondermann commented on VYSPER-95:
Niklas, isn't this largely resolved
[
https://issues.apache.org/jira/browse/VYSPER-189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12848320#action_12848320
]
Bernd Fondermann commented on VYSPER-189:
-
Students who want to make themselves
[
https://issues.apache.org/jira/browse/VYSPER-191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Fondermann reassigned VYSPER-191:
---
Assignee: Bernd Fondermann
roster javadoc
--
Key
[
https://issues.apache.org/jira/browse/VYSPER-191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Fondermann resolved VYSPER-191.
-
Resolution: Fixed
javadoc added, please feel free to re-open for anything still missing
Versions: 0.5
Environment: Vysper 0.5, Psi 0.14
Reporter: Bernd Fondermann
Priority: Minor
Psi client do not display it's own sent messages while it displays messages
sent from other clients properly
Message sent from Psi client:
message type=groupchat to=ch
[
https://issues.apache.org/jira/browse/VYSPER-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12851898#action_12851898
]
Bernd Fondermann commented on VYSPER-197:
-
This looks like a Psi glitch, but maybe
[
https://issues.apache.org/jira/browse/VYSPER-192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Fondermann reassigned VYSPER-192:
---
Assignee: Bernd Fondermann
javadoc on org/apache/vysper/xmpp/delivery
[
https://issues.apache.org/jira/browse/VYSPER-192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Fondermann resolved VYSPER-192.
-
Resolution: Fixed
javadoc on org/apache/vysper/xmpp/delivery
[
https://issues.apache.org/jira/browse/VYSPER-189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12858102#action_12858102
]
Bernd Fondermann commented on VYSPER-189:
-
I think before we dig too deep into any
Reporter: Bernd Fondermann
Assignee: Bernd Fondermann
Fix For: 0.6
Currently, IQ stanzas are not routed when 'to' is another client. But this is
needed for example for in-band file transfer.
--
This message is automatically generated by JIRA.
-
You can reply
[
https://issues.apache.org/jira/browse/VYSPER-199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Fondermann resolved VYSPER-199.
-
Resolution: Fixed
IQ can now be sent from client to client if their subscription matches
Fondermann
Assignee: Bernd Fondermann
Priority: Minor
While MUC is already a component (available under chat.vysper.org), PubSub
would also profit from this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
PubSub
Reporter: Bernd Fondermann
Assignee: Bernd Fondermann
VYSPER-199 introduced a regression. IQ stanzas are no longer properly routed to
components.
We have those scenarios we have to properly dispatch: IQ from local client to:
+ server (e.g. vysper.org)
+ component (e.g
[
https://issues.apache.org/jira/browse/VYSPER-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Fondermann resolved VYSPER-200.
-
Resolution: Fixed
Turn PubSub into a component
[
https://issues.apache.org/jira/browse/VYSPER-197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Fondermann resolved VYSPER-197.
-
Resolution: Fixed
fixed in rev 938927. do not print xmlns='' and everything works fine
[
https://issues.apache.org/jira/browse/VYSPER-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Fondermann resolved VYSPER-182.
-
Resolution: Fixed
meanwhile, this feature was implemented
Allow for components
[
https://issues.apache.org/jira/browse/VYSPER-175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Fondermann resolved VYSPER-175.
-
Resolution: Not A Problem
Don't know what the problem is.
Verify that two PubSub
[
https://issues.apache.org/jira/browse/VYSPER-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Fondermann resolved VYSPER-20.
Resolution: Later
Later, maybe.
Extend the set of session states
[
https://issues.apache.org/jira/browse/VYSPER-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Fondermann closed VYSPER-2.
-
Resolution: Fixed
those tags are long gone
Subversion properties wrong within the source files
[
https://issues.apache.org/jira/browse/VYSPER-15?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Fondermann updated VYSPER-15:
---
Issue Type: New Feature (was: Bug)
Implement SASL authorization
[
https://issues.apache.org/jira/browse/VYSPER-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Fondermann updated VYSPER-3:
--
Issue Type: New Feature (was: Bug)
Implement XEP-0009: Jabber-RPC
Components: extension
Affects Versions: 0.6
Reporter: Bernd Fondermann
Priority: Blocker
Just before making a new release, we need to code the right release number into
SoftwareVersionIQHandler.VYSPER_RELEASE
--
This message is automatically generated by JIRA.
-
You can
[
https://issues.apache.org/jira/browse/VYSPER-202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12864335#action_12864335
]
Bernd Fondermann commented on VYSPER-202:
-
+1, that's exactly what i missed to ask
[
https://issues.apache.org/jira/browse/VYSPER-202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12864348#action_12864348
]
Bernd Fondermann commented on VYSPER-202:
-
deal.
Make Vysper report the correct
[
https://issues.apache.org/jira/browse/VYSPER-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12871548#action_12871548
]
Bernd Fondermann commented on VYSPER-203:
-
initial candidates: jetty, strophe.js
: Bernd Fondermann
Priority: Blocker
BOSH introduces new dependencies. License must be checked and records be made
in our release notes.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[
https://issues.apache.org/jira/browse/VYSPER-206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12876041#action_12876041
]
Bernd Fondermann commented on VYSPER-206:
-
I'd like to propose the following
Client-side SCP
---
Key: SSHD-90
URL: https://issues.apache.org/jira/browse/SSHD-90
Project: MINA SSHD
Issue Type: New Feature
Reporter: Bernd Fondermann
Adding client-side SCP tools.
--
This message
[
https://issues.apache.org/jira/browse/SSHD-90?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Fondermann updated SSHD-90:
-
Attachment: PureScpWithSSHDTestCase.java
contains a first try of scp file upload.
Client-side SCP
[
https://issues.apache.org/jira/browse/VYSPER-202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Fondermann reassigned VYSPER-202:
---
Assignee: Bernd Fondermann
Make Vysper report the correct version on Version-IQ
[
https://issues.apache.org/jira/browse/VYSPER-202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Fondermann resolved VYSPER-202.
-
Fix Version/s: 0.6
Resolution: Fixed
Make Vysper report the correct version
[
https://issues.apache.org/jira/browse/VYSPER-40?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12902469#action_12902469
]
Bernd Fondermann commented on VYSPER-40:
for my opinion, see
https
Reporter: Bernd Fondermann
Scattered around the codebase is code to determine if an entity is addressing a
component of the server. example: chat.vysper.org is component of server
vysper.org.
We should establish a centralized method for this, like
EntityUtils.isComponent(entity, serverEntity
[
https://issues.apache.org/jira/browse/VYSPER-246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Fondermann resolved VYSPER-246.
-
Resolution: Fixed
added EntityUtils
Unify determination if a entity domain is from
: 0.5, 0.6
Reporter: Bernd Fondermann
Assignee: Bernd Fondermann
PubSub announces nodes on server domain instead of component domain.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[
https://issues.apache.org/jira/browse/VYSPER-247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Fondermann resolved VYSPER-247.
-
Resolution: Fixed
PubSub announces nodes on wrong domain
Reporter: Bernd Fondermann
Fix For: 0.7
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[
https://issues.apache.org/jira/browse/VYSPER-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Fondermann reassigned VYSPER-80:
--
Assignee: (was: Bernd Fondermann)
Improve SpecCompliant javadoc
[
https://issues.apache.org/jira/browse/VYSPER-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Fondermann closed VYSPER-44.
--
Resolution: Fixed
we released at least once, so I consider this done.
IP: Vysper code due
[
https://issues.apache.org/jira/browse/VYSPER-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Fondermann updated VYSPER-3:
--
Priority: Minor (was: Major)
Implement XEP-0009: Jabber-RPC
[
https://issues.apache.org/jira/browse/VYSPER-174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Fondermann closed VYSPER-174.
---
Resolution: Fixed
duplicate. see VYSPER-91
Implement XEP-0114 (Component Protocol
[
https://issues.apache.org/jira/browse/VYSPER-173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Fondermann resolved VYSPER-173.
-
Resolution: Fixed
Introduce a constructor for the PublishSubscribeModule to enable
[
https://issues.apache.org/jira/browse/VYSPER-173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Fondermann updated VYSPER-173:
Assignee: Bernd Fondermann (was: Michael Jakl)
Fix Version/s: 0.7
[
https://issues.apache.org/jira/browse/VYSPER-250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Fondermann reassigned VYSPER-250:
---
Assignee: Bernd Fondermann
Make BOSH configurable from Spring
Make BOSH endpoint more configurable
Key: VYSPER-251
URL: https://issues.apache.org/jira/browse/VYSPER-251
Project: VYSPER
Issue Type: New Feature
Reporter: Bernd Fondermann
[
https://issues.apache.org/jira/browse/VYSPER-250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Fondermann resolved VYSPER-250.
-
Resolution: Fixed
BOSH is now configurable from main spring config
Make BOSH
[
https://issues.apache.org/jira/browse/VYSPER-251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Fondermann resolved VYSPER-251.
-
Fix Version/s: 0.7
Resolution: Fixed
Make BOSH endpoint more configurable
Affects Versions: 0.6
Reporter: Bernd Fondermann
Priority: Critical
When the server receives a stanza which contains not well-formed (NWF) XML, the
XMPP stream must be closed immediately.
Vysper detects, but currently doesn't close on NWF XML:
item miltjackson
: Bernd Fondermann
The spec mandates to terminate the connection when not-wellformed stanzas are
encountered
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[
https://issues.apache.org/jira/browse/VYSPER-252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Fondermann closed VYSPER-252.
---
Not well formed XML does not terminate XMPP stream
[
https://issues.apache.org/jira/browse/VYSPER-252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Fondermann resolved VYSPER-252.
-
Resolution: Duplicate
duplicate of VYSPER-254
Not well formed XML does not terminate
MUC: Fix invites
Key: VYSPER-256
URL: https://issues.apache.org/jira/browse/VYSPER-256
Project: VYSPER
Issue Type: Bug
Components: XEP-0045 MUC
Affects Versions: 0.6
Reporter: Bernd Fondermann
[
https://issues.apache.org/jira/browse/VYSPER-256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Fondermann closed VYSPER-256.
---
Resolution: Fixed
MUC: Fix invites
Key: VYSPER-256
[
https://issues.apache.org/jira/browse/VYSPER-257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Fondermann resolved VYSPER-257.
-
Resolution: Fixed
Entity constructor does no String preparation
[
https://issues.apache.org/jira/browse/VYSPER-170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Fondermann reassigned VYSPER-170:
---
Assignee: Bernd Fondermann
Implement Service Administration XEP-0133
[
https://issues.apache.org/jira/browse/VYSPER-169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Fondermann reassigned VYSPER-169:
---
Assignee: Bernd Fondermann
Implement Ad-Hoc Commands XEP-0050
[
https://issues.apache.org/jira/browse/VYSPER-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Fondermann resolved VYSPER-61.
Resolution: Fixed
Fix Version/s: 0.7
Server Support for XEP-0004 - Data Forms
[
https://issues.apache.org/jira/browse/VYSPER-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12975499#action_12975499
]
Bernd Fondermann commented on VYSPER-61:
2. decode: we now have a basic parser
601 - 700 of 864 matches
Mail list logo
