Gerolf Seitz wrote:
hi,
i was rather surprised about the heavy usage of spring for wiring the
different
parts of the system together.
imho, OSGi would be a much better fit, given the there are lots of
extensions.
so you could enable/disable/install/... a new feature/service to the server
while i
hi,
i was rather surprised about the heavy usage of spring for wiring the
different
parts of the system together.
imho, OSGi would be a much better fit, given the there are lots of
extensions.
so you could enable/disable/install/... a new feature/service to the server
while it's running, etc...
va
Hi Bernd,
both "SpecCompliant" and o.a.v.compliance sound good.
btw, i hope you don't mind me committing (for now) minor changes to the
repository :)
Gerolf
On Thu, Apr 17, 2008 at 7:04 PM, Bernd Fondermann <[EMAIL PROTECTED]>
wrote:
> Hi Gerolf,
>
> great, thanks for starting to commit to th
Hi Gerolf,
great, thanks for starting to commit to the labling. :-)
The RFCs are one class of relevant specs, the others are XEPs (see
xmpp.org/extensions).
WDYT, should we use another annotation for them (XEPCompliant) or should
we change RFCCompliant to something like "SpecCompliant"?
If w
Improve stanza relaying
---
Key: LABS-124
URL: https://issues.apache.org/jira/browse/LABS-124
Project: Labs
Issue Type: Improvement
Components: Vysper
Reporter: Bernd Fondermann
Stanza relaying ade
[
https://issues.apache.org/jira/browse/LABS-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerolf Seitz resolved LABS-123.
---
Resolution: Fixed
oops, didn't notice i have commit karma already.
so i took the liberty to commit, si
[
https://issues.apache.org/jira/browse/LABS-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerolf Seitz updated LABS-123:
--
Attachment: rfcCompliant.patch
attached patch includes @RfcComplient annotation and modification to build
use @RfcCompliant to mark specific code elements and unit tests that implement
or check RFC compliance
--
Key: LABS-123
URL: https://issues.apache.org/jira/browse/
On Thu, Apr 17, 2008 at 8:53 AM, Bernd Fondermann <
[EMAIL PROTECTED]> wrote:
> what about putting a special doclet tag or documenting attribute at
> the unit test which is covering a section.
i'd also annotate the classes/methods/... in the non-testing code, so that
this
is also generated with j