[jira] [Created] (FELIX-3469) Type mismatch JS error using the memoryusage plugin
Type mismatch JS error using the memoryusage plugin --- Key: FELIX-3469 URL: https://issues.apache.org/jira/browse/FELIX-3469 Project: Felix Issue Type: Bug Components: Web Console Affects Versions: webconsole-3.1.2 Environment: Microsoft IE 8 Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: webconsole-3.4.0 When showing the Memory Usage page, IE8 reports a type mismatch error in the support.js script. For example when clicking the Heap Dump button: Result: Type mismatch error in http://localhost:4502/system/console/res/lib/support.js (line: 257, char: 4) Expected: no error, GC and heap dump to execute Also the detail information is not properly listed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (FELIX-3444) DependencyFinder should use JQuery UI table look
DependencyFinder should use JQuery UI table look Key: FELIX-3444 URL: https://issues.apache.org/jira/browse/FELIX-3444 Project: Felix Issue Type: Improvement Components: Web Console Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: webconsole-packageadmin-plugin 1.0.0 The Dependency Finder page of the packageadmin plugin allows you to find package exporters as well as generating a list of Maven project dependencies. This uses tables which are styled after the old pre-JQuery UI design. The tables should be adapted to JQuery UI. This is as simple as using the nicetable class on the table element and removing all class attributes from the tr, td, and th elements. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (FELIX-3415) Disable update button if bundle location URL is invalid
Disable update button if bundle location URL is invalid
---
Key: FELIX-3415
URL: https://issues.apache.org/jira/browse/FELIX-3415
Project: Felix
Issue Type: Improvement
Components: Web Console
Affects Versions: webconsole-3.1.8
Reporter: Felix Meschberger
When clicking the update button on any bundle, the bundle location (or the
bundle's update location header) is taken as an URL to retrieve a bundle
update. If the bundle's update location header is not set and the bundle
location is not a valid URL, this of course fails.
We should probably disable the update button if the bundle location URL fails
to be created:
try {
new URL(bundleLocation);
updatePossible = true;
} catch (MalformedURLException mue) {
updatePossible = false;
}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (FELIX-3403) Provide russian translations for new messages for the Log Service panel
Provide russian translations for new messages for the Log Service panel --- Key: FELIX-3403 URL: https://issues.apache.org/jira/browse/FELIX-3403 Project: Felix Issue Type: Sub-task Components: Web Console Affects Versions: webconsole-3.2.0 Reporter: Felix Meschberger FELIX-3316 adds three new messages to be translated to russian: log.traces=Exception details: log.traces.full=Full Trace log.traces.min=Message Only -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (FELIX-3348) StartLevel thread may terminate on uncaught exception
StartLevel thread may terminate on uncaught exception - Key: FELIX-3348 URL: https://issues.apache.org/jira/browse/FELIX-3348 Project: Felix Issue Type: Bug Components: Framework Affects Versions: framework-4.0.2 Reporter: Felix Meschberger It looks like an uncaught exception is able to terminate the StartLevel thread thus causing the framework to not be properly controllable. Sample issue: Felix.setActiveStartLevel may throw IllegalStateException if global lock cannot be acquired. This exception is not caught and causes StartLevel thread to terminate. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (FELIX-3341) Simple csh-like Command History
Simple csh-like Command History
---
Key: FELIX-3341
URL: https://issues.apache.org/jira/browse/FELIX-3341
Project: Felix
Issue Type: Improvement
Components: Gogo Shell
Affects Versions: gogo.shell-0.10.0
Reporter: Felix Meschberger
Attachments: FELIX-3341.patch
Suggest to add a simple csh like command line history.
* A new command "history" is added to the Shell class listing the command
history
* A new History class is added to manage a bounded, in-memory-only command
history
* Commands can be reused from the history using commands following this simple
syntax:
command = ( '!' spec ) | ( '^' subst ) .
spec = '!' event [ ':' [ 'a' | 'g' ] 's' regex ] .
event = ( '!' | idx | '?' find | string )
idx = [ '-' ] { 0..9 } .
find = string ( '?' | EOL ) .
subst = pat '^' repl '^' EOL .
regex = str pat str repl str EOL .
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (FELIX-3340) Allow the prompt to be a Function
Allow the prompt to be a Function
-
Key: FELIX-3340
URL: https://issues.apache.org/jira/browse/FELIX-3340
Project: Felix
Issue Type: Improvement
Components: Gogo Shell
Affects Versions: gogo.shell-0.10.0
Reporter: Felix Meschberger
It would be nice to have a dynamic command prompt such that for example the
current working directory could be displayed:
prompt = {
dirname = ( ( cd ) name )
"$dirname \$"
}
To implement this, a prompt variable would be checked whether it is a Function
and be executed if so using the result as the prompt.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (FELIX-3339) Consolidate Thread Dump Support
Consolidate Thread Dump Support --- Key: FELIX-3339 URL: https://issues.apache.org/jira/browse/FELIX-3339 Project: Felix Issue Type: Improvement Components: Web Console Affects Versions: webconsole-3.1.8 Reporter: Felix Meschberger The Felix Web Console currently has an embedded plugin only using traditional Java API. Sling has a Web Console plugin leveraging the Java 5 JMX APIs. These two should be consolidated and extended such that: * Separate bundle (not embedded in the Web Console Bundle) * one single plugin in Apache Felix * Uses Java 6 JMX API if available * Falls back to Java 5 JMX API if not Java 6 * Falls back to regular Java API as a last step * Provide Gogo Shell Commands The advantage of using Java 6 API is to be able to inject lock information in the thread dumps to be able to followup on deadlock and similar situations. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (FELIX-3335) Whiteboard Web Console plugin does not properly display filters registered with the same pattern
Whiteboard Web Console plugin does not properly display filters registered with the same pattern Key: FELIX-3335 URL: https://issues.apache.org/jira/browse/FELIX-3335 Project: Felix Issue Type: Bug Components: HTTP Service Affects Versions: http-2.2.0 Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: http-whiteboard-2.3.0 The Whiteboard Web Console plugin uses a TreeMap to sort the registered filters by pattern. This causes to not display filters whose patterns are the same. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (FELIX-3328) "Apply Filter" and "Filter all" on the bundles page result in errors.
"Apply Filter" and "Filter all" on the bundles page result in errors. - Key: FELIX-3328 URL: https://issues.apache.org/jira/browse/FELIX-3328 Project: Felix Issue Type: Bug Components: Web Console Affects Versions: webconsole-3.1.8 Reporter: Felix Meschberger Fix For: webconsole-3.2.0 When clicking on the "Apply Filter" button a POST request is sent to the bundles page which cause a 405/METHOD NOT ALLOWED. I would assume that "Apply Filter" should really be a client side action to apply the filter entered in the search box. Likewise the "Filter All" button causes a dialog to open reporting an "Invalid LDAP filter specified" message, which is not helpfull. Entering a filter and hitting enter works perfectly as well as clicking the "X" icon to clear the filter string. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (FELIX-3327) Gracefully handle Configuration access after Configuration Admin Service has terminated
Gracefully handle Configuration access after Configuration Admin Service has terminated --- Key: FELIX-3327 URL: https://issues.apache.org/jira/browse/FELIX-3327 Project: Felix Issue Type: Improvement Components: Configuration Admin Affects Versions: configadmin-1.2.8 Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: configadmin-1.4.0 When accessing Configuration objects after the Configuration Admin service supplying the Configuration has been unregistered/stopped, all kinds of exceptions may be thrown. This should be cleaned such that defined and controlled exceptions are thrown: * getPid, getFactoryPid, and getProperties just operate as before. They don't need live Configuration Admin access * getBundleLocation, setBundleLocation, update (both methods), and delete throw IllegalStateException This is not required by the spec (in fact the spec remains silent about this case) but is ok. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (FELIX-3319) Add invalid topics when not accepting EventHandler
Add invalid topics when not accepting EventHandler -- Key: FELIX-3319 URL: https://issues.apache.org/jira/browse/FELIX-3319 Project: Felix Issue Type: Improvement Components: Event Admin Affects Versions: eventadmin-1.2.14 Reporter: Felix Meschberger If an EventHandler is registered with invalid topics, the EventAdmin services logs a message along these lines at WARN level: 26.01.2012 14:07:28.593 *WARN* [FelixStartLevel] org.apache.felix.eventadmin Service [xxx,111] EventAdmin: Invalid EVENT_TOPICS - Ignoring ServiceReference [[xxx] | Bundle(smbolic.name [111])] Could this message be improved indicating what exactly the topics are, which are considered invalid ? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (FELIX-3317) Potential concurrency issue during Component Service registration
Potential concurrency issue during Component Service registration - Key: FELIX-3317 URL: https://issues.apache.org/jira/browse/FELIX-3317 Project: Felix Issue Type: Bug Components: Declarative Services (SCR) Affects Versions: scr-1.6.0 Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: scr-1.6.2 In our Sling-based application we saw the following behavior: The Sling ResourceResolverFactory is a component being activated. Yet every now and then a field of that component seems to become null which is not expected for an activated ResourceResolverFactory component and thus causes a NullPointerException. Upon inspection I saw, that for the same Declarative Services component two Services have been registered where only one was actually expected. Turns out that consumers of the ResoureResovlerFactory where all bound to the same service. The component on the other hand has been cycled due to a configuration update. So one service is backed by a deactivated component (whose field has been reset to null already) and the other service is live. The problem is that the service backed by the deactivated method has not been unregistered and thus all consumers are hooked up to the deactivated instance causing all sorts of problems ... This is what most probably happens in the AbstractComponentManager: * T1 Unsatisfied.activate has set the state to Active already before calling registerService * T1 registerService is called but the service registration field field is not assigned yet during registerService ServiceListeners are called * T2 A Configuration update comes in and Satisfied(Active).deactivate is called * T2 calls unregisterComponentService; does nothing because the service registration field is not assigned * T2 destroys component * T1 assigns field from service registration As a result the deactivated object's service registration may be unregistered later when the component is cycled again and the second service registration will only be unregistered when the providing bundle is restarted. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (FELIX-3308) Present a nice error message if a bundle update is not possible
Present a nice error message if a bundle update is not possible --- Key: FELIX-3308 URL: https://issues.apache.org/jira/browse/FELIX-3308 Project: Felix Issue Type: Improvement Components: Web Console Affects Versions: webconsole-3.1.8 Reporter: Felix Meschberger If a bundle has a bundle location which cannot be used to update the bundle through the Bundle.update() method, a nasty error message is logged and displayed: ERROR: Unable to update the bundle. (java.net.MalformedURLException: Unknown protocol: jcrinstall) java.net.MalformedURLException: Unknown protocol: jcrinstall at java.net.URL.(URL.java:601) at org.apache.felix.framework.util.SecureAction.createURL (SecureAction.java:238) at org.apache.felix.framework.cache.JarRevision.initialize (JarRevision.java:153) at org.apache.felix.framework.cache.JarRevision.(JarRevision.java:82) at org.apache.felix.framework.cache.JarRevision.(JarRevision.java:60) at org.apache.felix.framework.cache.BundleArchive.createRevisionFromLocation (BundleArchive.java:868) at org.apache.felix.framework.cache.BundleArchive.reviseInternal (BundleArchive.java:549) at org.apache.felix.framework.cache.BundleArchive.revise (BundleArchive.java:521) at org.apache.felix.framework.BundleImpl.revise(BundleImpl.java:1078) at org.apache.felix.framework.Felix.updateBundle(Felix.java:1959) at org.apache.felix.framework.BundleImpl.update(BundleImpl.java:940) at org.apache.felix.framework.BundleImpl.update(BundleImpl.java:927) at org.apache.felix.webconsole.internal.core.UpdateHelper.updateFromBundleLocation (UpdateHelper.java:108) at org.apache.felix.webconsole.internal.core.UpdateHelper.doRun (UpdateHelper.java:74) at org.apache.felix.webconsole.internal.core.BaseUpdateInstallHelper.run (BaseUpdateInstallHelper.java:121) at java.lang.Thread.run(Thread.java:680) The Web Console UpdateHelper.updateFromBundleLocation should catch this error and return a nicer message indicating that this kind of update is not possible. Maybe the display could be improved to disable the update button if the location URL cannot be used (e.g. with a "simple" URL creation check) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (FELIX-3301) Enforce only using Java 1.3 API use
Enforce only using Java 1.3 API use --- Key: FELIX-3301 URL: https://issues.apache.org/jira/browse/FELIX-3301 Project: Felix Issue Type: Task Components: Configuration Admin Affects Versions: configadmin-1.2.8 Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: configadmin-1.4.0 Building Java 1.3 class files is currently enforced. Yet, this does not mean enforcing Java 1.3 API use. The animal sniffer plugin should be configured to enforce only using Java 1.3 API -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (FELIX-3298) Add animal sniffer plugin to ensure no using any non-Java 1.4 API
Add animal sniffer plugin to ensure no using any non-Java 1.4 API - Key: FELIX-3298 URL: https://issues.apache.org/jira/browse/FELIX-3298 Project: Felix Issue Type: Improvement Components: Web Console Affects Versions: webconsole-3.1.8 Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: webconsole-3.2.0 Currently using modern platforms for development it is not easy to not use non-Java 1.4 API. To ensure using the appropriate API, the animal sniffer plugin should be configured to compare API use against Java 1.4. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (FELIX-3295) Allow configuration of Http Service context path
Allow configuration of Http Service context path Key: FELIX-3295 URL: https://issues.apache.org/jira/browse/FELIX-3295 Project: Felix Issue Type: New Feature Components: HTTP Service Affects Versions: http-2.2.0 Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: http-2.2.2 We have a need that we want our Http Service based application to not always run on the root context path. The use case is that we have a single reverse proxy in front of multiple instances of our application and we forward to the different instances based on the URL path. For simplicity we don't want to rewrite the paths and thus the easiest thing is to run the instances with different context paths. The proposed solution is simple: We add a new configuration property "org.apache.felix.http.context_path" (named after the request property "javax.servlet.include.context_path" indicating the context path on RequestDispatcher.include). This defaults to "/" and may be any path with a leading slash (enforced if missing) and no trailing slash (removed if provided). The value of this property (or the default) is then used to create the Context for Jetty. This is also referred to by a post on the users list [1]. [1] http://markmail.org/message/gwnct4675htaf7jc -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (FELIX-3290) Improve Cookie handling of the Web Console
Improve Cookie handling of the Web Console -- Key: FELIX-3290 URL: https://issues.apache.org/jira/browse/FELIX-3290 Project: Felix Issue Type: Improvement Components: Web Console Affects Versions: webconsole-3.1.8 Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: webconsole-3.2.0 Cookies are created on the client side to persist some setups like the chosen locale or the bundle sort order. These cookies are session cookies (removed when the browser is closed) attached to the root of the URL space, thus globally visible. There has been a fix in FELIX-3236 to persist the locale cookie for twenty years. Still the cookie is attached to URL root space. Propose to addition of a global setCookie(name, value) method to the support.js script, which sets a cookie to a given name and value and defaults the expiry to twenty years and attaches the cookie to the root of the web console (appRoot, /system/console by default). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (FELIX-3285) Wrong vector and array handling in Configuration Admin plugin
Wrong vector and array handling in Configuration Admin plugin - Key: FELIX-3285 URL: https://issues.apache.org/jira/browse/FELIX-3285 Project: Felix Issue Type: Bug Components: Web Console Affects Versions: webconsole-3.1.8 Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: webconsole-3.2.0 There some issues when handling configuration updates: - If a Collection type property is updated with no values, it should not be added as an empty collection, which is invalid. Rather it should be made sure to not set the property at all in the configuration - If an attribute definition for an existing array property is missing, it should be synthesized with Integer.MAX_VALUE cardinality instead of Integer.MIN_VALUE, which would be a Vector/Collection -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (FELIX-3284) NullPointerException may be thrown if asynchronous bundle update fails
NullPointerException may be thrown if asynchronous bundle update fails -- Key: FELIX-3284 URL: https://issues.apache.org/jira/browse/FELIX-3284 Project: Felix Issue Type: Bug Components: Web Console Affects Versions: webconsole-3.1.8 Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: webconsole-3.2.0 If the web console bundle gets restarted while a bundle is being updated in the BaseUpdateInstallerHelper thread and an exception happens during the update, the log message cannot be written causing a NullPointerException. This factually hides the actual problem. The fix is to catch any exception when trying to log the message and just write the error to std err to at least get some indication of problems. One such potential situation is failing to update the web console bundle itself (e.g. due to missing dependencies) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (FELIX-3283) Use generics in the Web Console
Use generics in the Web Console --- Key: FELIX-3283 URL: https://issues.apache.org/jira/browse/FELIX-3283 Project: Felix Issue Type: Task Components: Web Console Affects Versions: webconsole-3.1.8 Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: webconsole-3.2.0 Now that the web console has source level Java 5 (but still generates Java 1.4 class files) we may make use of generics and enhanced for loops to clean up the code. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (FELIX-3282) Generate default fields for configurations without descriptor
Generate default fields for configurations without descriptor - Key: FELIX-3282 URL: https://issues.apache.org/jira/browse/FELIX-3282 Project: Felix Issue Type: Improvement Components: Web Console Affects Versions: webconsole-3.1.8 Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: webconsole-3.2.0 If a configuration has no associated Metatype Descriptor, the Web Console currently presents the data in a single TextArea where the properties are essentially listed in the format of a Java Properties file. This is not very useful and may also loose type information. This problem can be fixed by generating default entry fields for existing configuration. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (FELIX-3281) Use bundle plugin 2.3.6 and BND annotations for package export
Use bundle plugin 2.3.6 and BND annotations for package export -- Key: FELIX-3281 URL: https://issues.apache.org/jira/browse/FELIX-3281 Project: Felix Issue Type: Task Components: Web Console Affects Versions: webconsole-3.1.8 Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: webconsole-3.1.10 Currently the web console does not properly re-import its own exported package. We should update to the latest bundle plugin which also allows for annotation based export declaration. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (FELIX-3280) Update to use parent POM 2.1
Update to use parent POM 2.1 Key: FELIX-3280 URL: https://issues.apache.org/jira/browse/FELIX-3280 Project: Felix Issue Type: Task Components: Web Console Affects Versions: webconsole-3.1.8 Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: webconsole-3.1.10 The web console should make use of the most recent parent POM which improves legal file handling -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (FELIX-3279) Drop default build and use bare profile as the single build
Drop default build and use bare profile as the single build --- Key: FELIX-3279 URL: https://issues.apache.org/jira/browse/FELIX-3279 Project: Felix Issue Type: Task Components: Web Console Affects Versions: webconsole-3.1.8 Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: webconsole-3.1.10 Currently the Web Console comes in two builds: A full-blown embedding the Commons IO, FileUpload, and JSON dependencies and a bare build which does not embed these dependencies. I tend to think, that we should drop the full-blown build and just use the single bare build as the new default build. This would also solve the issue of sharing classes between the web console itself and separate plugins as described in FELIX-3105 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (FELIX-3259) Improve Http Whiteboard Web Console plugin
Improve Http Whiteboard Web Console plugin -- Key: FELIX-3259 URL: https://issues.apache.org/jira/browse/FELIX-3259 Project: Felix Issue Type: Improvement Components: HTTP Service Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: http-whiteboard-2.3.0 Improve the Web Console plugin as follows: * Print Servlet and FilterMappings sorted by the alias and pattern * Add output of unregistered orphan servlets and filters -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (FELIX-3258) Separate parent POM from reactor
Separate parent POM from reactor Key: FELIX-3258 URL: https://issues.apache.org/jira/browse/FELIX-3258 Project: Felix Issue Type: Improvement Components: HTTP Service Affects Versions: http-2.2.0 Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: http-parent-3 The (full) HTTP Service parent POM is currently the same as the reactor pom to build all parts of the service. To support creating independent releases of the parts of the implementation, we should also separate the parent POM from the reactor. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (FELIX-3255) Web Console should not create request URLs with double slashes
Web Console should not create request URLs with double slashes -- Key: FELIX-3255 URL: https://issues.apache.org/jira/browse/FELIX-3255 Project: Felix Issue Type: Bug Components: Web Console Affects Versions: webconsole-3.1.8 Reporter: Felix Meschberger As reported in [1] the web console might generate requests with double slashes. This is not very nice and may in fact lead to failed requests. [1] http://markmail.org/message/27pmmfdrpigdrylo -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (FELIX-3237) Provide Web Console plugin for the Http Whiteboard support
Provide Web Console plugin for the Http Whiteboard support -- Key: FELIX-3237 URL: https://issues.apache.org/jira/browse/FELIX-3237 Project: Felix Issue Type: New Feature Components: HTTP Service Affects Versions: http-2.2.0 Reporter: Felix Meschberger Assignee: Felix Meschberger To check whether Whiteboard Filter, Servlet, and HttpContext service registration properly works a Web Console plugin should be added to the Http Service Whiteboard support bundle. In addition a ConfigurationPrinter is to be added to get a simple information dump. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (FELIX-3236) Make language selection cookie longer lasting
Make language selection cookie longer lasting - Key: FELIX-3236 URL: https://issues.apache.org/jira/browse/FELIX-3236 Project: Felix Issue Type: Improvement Components: Web Console Affects Versions: webconsole-3.1.8 Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: webconsole-3.1.10 The language selection cookie currently is a session cookie. Thus the language selection is lost when the browser is closed. I think this should be changed to be a long-lived cookie. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (FELIX-3233) ConfigurationManager.canReceive may throw NullPointerException
ConfigurationManager.canReceive may throw NullPointerException -- Key: FELIX-3233 URL: https://issues.apache.org/jira/browse/FELIX-3233 Project: Felix Issue Type: Bug Components: Configuration Admin Affects Versions: configadmin-1.2.8 Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: configadmin-1.4.0 The ConfigurationManager.canReceive method checks whether a bundle can receive configuration bound to a certain location. This method may throw a NullPointerException if the bundle is null. This may be the case if the service has been unregistered between the event causing the canReceive to the called and the asynchronous handling. For example: * Register ManagedService * Update Configuration * Unregister ManagedService * --> asynchronous processing of configuration update also calling canReceive At the point in time of processing the configuration update, the service has been unregistered and ServiceReference.getBundle() returns null. Callers of canReceive should be fixed to ensure the bundle is not null. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (FELIX-3232) Re-Import SCR Service API
Re-Import SCR Service API - Key: FELIX-3232 URL: https://issues.apache.org/jira/browse/FELIX-3232 Project: Felix Issue Type: Improvement Components: Declarative Services (SCR) Affects Versions: scr annotations 1.6.0 Reporter: Felix Meschberger Assignee: Felix Meschberger To be a good OSGi citizen it would be nice if the Declarative Services bundle would re-import its own SCR service API. Actually there is also a request from the users list [1] for this, too. [1] http://www.mail-archive.com/users@felix.apache.org/msg11432.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (FELIX-3231) Disable update counter
Disable update counter -- Key: FELIX-3231 URL: https://issues.apache.org/jira/browse/FELIX-3231 Project: Felix Issue Type: Bug Components: Configuration Admin, Specification compliance Affects Versions: configadmin-1.2.8 Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: configadmin-1.4.0 Update counter checks have been added to prevent multiple configuration updates with the same configuration in certain race condition situations. With the new R4.3 Configuration Admin (v1.4) it is now allowed that multiple ManagedService or ManagedServiceFactory services are registered with the same PID and that all receive the same configuration. This of course is incompatible with the current simple update counter mechanism. For now we should just disable this check. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (FELIX-3230) ConfiguartionAdapter.setBundleLocation checks configuration permission incorrectly
ConfiguartionAdapter.setBundleLocation checks configuration permission incorrectly -- Key: FELIX-3230 URL: https://issues.apache.org/jira/browse/FELIX-3230 Project: Felix Issue Type: Bug Components: Configuration Admin, Specification compliance Affects Versions: configadmin-1.2.8 Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: configadmin-1.4.0 The ConfigurationAdapter.setBundleLocation checks the configuration does not check for CP(*,CONFIGURE) if the configurations current location is null. This must be fixed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (FELIX-3229) ConfigurationAdmin.getConfiguration(String, String) and .createConfiguration(String) to generous
ConfigurationAdmin.getConfiguration(String, String) and
.createConfiguration(String) to generous
Key: FELIX-3229
URL: https://issues.apache.org/jira/browse/FELIX-3229
Project: Felix
Issue Type: Bug
Components: Configuration Admin, Specification compliance
Affects Versions: configadmin-1.2.8
Reporter: Felix Meschberger
Assignee: Felix Meschberger
Fix For: configadmin-1.4.0
Similar to FELIX-3228, the ConfigurationAdmin.getConfiguration and
createConfiguration methods with the location parameter do not properly check
the null location properly.
R 4.3 Configuration Admin (v1.4) spec states:
• createFactoryConfiguration(String,String)
• ConfigurationPermission[location,CONFIGURE] - if location is not null
• ConfigurationPermission["*",CONFIGURE] - if location is null
• getConfiguration(String,String)
• ConfigurationPermission[*,CONFIGURE] - if location is null or if the
returned configuration c already exists and c.location is null
• ConfigurationPermission[location,CONFIGURE] - if location is not null
• ConfigurationPermission[c.location,CONFIGURE] - if the returned
configuration c already exists and c.location is not null
Particularly the CP("*", CONFIGURE) case is not properly checked.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (FELIX-3228) Configuration.getBundleLocation to generous
Configuration.getBundleLocation to generous --- Key: FELIX-3228 URL: https://issues.apache.org/jira/browse/FELIX-3228 Project: Felix Issue Type: Bug Components: Configuration Admin, Specification compliance Affects Versions: configadmin-1.2.8 Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: configadmin-1.4.0 R 4.3 Configuration Admin (v.1.4) spec says that permissions on Configuration.getBundleLocation() must be check as follows: • ConfigurationPermission[this.location,CONFIGURE] - if this.location is not null • ConfigurationPermission["*",CONFIGURE] - if this.location is null Currently the special case check in case of "this.location is null" is not correctly done thus granting permission to generously. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (FELIX-3227) ManagedService.update must be called with null if configuration exists but is not visilbe
ManagedService.update must be called with null if configuration exists but is not visilbe - Key: FELIX-3227 URL: https://issues.apache.org/jira/browse/FELIX-3227 Project: Felix Issue Type: Bug Reporter: Felix Meschberger -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (FELIX-3226) Whiteboard servlet service registered with default HttpContext if registered before HttpContext service
Whiteboard servlet service registered with default HttpContext if registered before HttpContext service --- Key: FELIX-3226 URL: https://issues.apache.org/jira/browse/FELIX-3226 Project: Felix Issue Type: Bug Components: HTTP Service Affects Versions: http-2.2.0 Reporter: Felix Meschberger If a Servlet service for whiteboard registration with the HttpService is registered before the HttpContext service referred to, the servlet is registered with a default context. This may cause problems in the service and prevent correct operation. Rather the servlet registration should be delayed until the HttpContext arrives. Likewise, once the HttpContext is unregistered, the servlet must be unregistered from the HttpService, too. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (FELIX-3225) Support flexible use of HttpContext implementations for Servlet whiteboard pattern
Support flexible use of HttpContext implementations for Servlet whiteboard pattern -- Key: FELIX-3225 URL: https://issues.apache.org/jira/browse/FELIX-3225 Project: Felix Issue Type: New Feature Components: HTTP Service Affects Versions: http-2.2.0 Reporter: Felix Meschberger The servlet registration whiteboard pattern is great. But it lacks functionality to use a custom HttpContext implementation. This is particularly annoying in situations where a custom implementation is required e.g. for authentication purposes. The idea is: * HttpContext services are registered with an identification property, e.g. felix.context.id * Servlet services are registered with the same identification property, where the whiteboard support will merge the two * If a Servlet service is registered for which not HttpContext is available, the servlet is not registered with the HttpService (yet). * When an HttpContext is registered any registered servlet services are checked for whether they refer to the newly registered HttpContext * Likewise on HttpContext unregistration, related services must be unregistered from the HttpContext again -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (FELIX-3200) Track PID changes of ManagedService[Factory] services
Track PID changes of ManagedService[Factory] services - Key: FELIX-3200 URL: https://issues.apache.org/jira/browse/FELIX-3200 Project: Felix Issue Type: Task Components: Configuration Admin Affects Versions: configadmin-1.2.8 Reporter: Felix Meschberger Assignee: Felix Meschberger Configuration Admin 1.4 requires implementations to track service.pid changes of registered ManagedService and ManagedServiceFactory services: > The Configuration Admin must track the configuration targets on their actual > PID. That is, if the service.pid service property is modied then the > Configuration Admin must treat it as if the service was unregistered and then > re-registered with the new PID. This means we have to track service registration PIDs and compare them against any service registration changes and appropriately update the services. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (FELIX-3199) Allow configuration of Session timeout
Allow configuration of Session timeout -- Key: FELIX-3199 URL: https://issues.apache.org/jira/browse/FELIX-3199 Project: Felix Issue Type: Improvement Components: HTTP Service Affects Versions: http-2.2.0 Reporter: Felix Meschberger Assignee: Felix Meschberger Currently the Jetty based implementation does not allow the configuration of the HTTP Session life time and thus keeps the Jetty default of "forever". Propose the addition of a configuration property "org.apache.felix.http.session.timeout" which follows the semantics of the session-timeout element of the web application descriptor. Like for the web application descriptor this value is specified in minutes (whereas Jetty would allow for seconds). Choosing minutes should follow the rule of least surprise. See also this comment on FELIX-2687: https://issues.apache.org/jira/browse/FELIX-2687?focusedCommentId=13122559&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13122559 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (FELIX-3198) Support generic configuration properties
Support generic configuration properties Key: FELIX-3198 URL: https://issues.apache.org/jira/browse/FELIX-3198 Project: Felix Issue Type: Improvement Components: HTTP Service Affects Versions: http-2.2.0 Reporter: Felix Meschberger Assignee: Felix Meschberger Currently the Jetty configuration only allows for a hard-coded limited sets of properties provided in either the Configuration Admin configuration or as framework properties. Adding support for generic properties allows administrators to configure the Servlet Container more specifically. Examples of such properties would be Jetty specific session configuration. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (FELIX-3197) Add support to configure the interface to listen on
Add support to configure the interface to listen on --- Key: FELIX-3197 URL: https://issues.apache.org/jira/browse/FELIX-3197 Project: Felix Issue Type: Improvement Components: HTTP Service Affects Versions: http-2.2.0 Reporter: Felix Meschberger Assignee: Felix Meschberger Currently the Http Service implementation only allows to configure the port on which the HTTP or HTTPS connector is listening. For full flexibility it must be possible to also provide information on which interface(s) to listen on. To this avail a new string typed configuration property "org.apache.felix.host" should be added. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (FELIX-3184) Add support for metatype extension by MetatypeProvider services
Add support for metatype extension by MetatypeProvider services --- Key: FELIX-3184 URL: https://issues.apache.org/jira/browse/FELIX-3184 Project: Felix Issue Type: Task Components: Metatype Service Affects Versions: metatype-1.0.4 Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: metatype-1.0.6 Metatype service 1.2 (as defined in the Residential 4.3 final draft) supports dynamic addition of MetatypeInformation by MetatypeProvider services. We should add support for such services. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (FELIX-3183) Attribute requirement is not validated
Attribute requirement is not validated -- Key: FELIX-3183 URL: https://issues.apache.org/jira/browse/FELIX-3183 Project: Felix Issue Type: Bug Components: Metatype Service Affects Versions: metatype-1.0.4 Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: metatype-1.0.6 The AD.validate method validates a false positive for a missing value even if a value would be required. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (FELIX-3182) Update to use parent POM 2.1
Update to use parent POM 2.1 Key: FELIX-3182 URL: https://issues.apache.org/jira/browse/FELIX-3182 Project: Felix Issue Type: Task Components: Metatype Service Affects Versions: metatype-1.0.4 Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: metatype-1.0.6 Make use of the 2.1 parent POM to leverage new plugins and remote resources for the legal files -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (FELIX-3180) Provide MessageFormat based logging method
Provide MessageFormat based logging method -- Key: FELIX-3180 URL: https://issues.apache.org/jira/browse/FELIX-3180 Project: Felix Issue Type: Improvement Components: Configuration Admin Affects Versions: configadmin-1.2.8 Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: configadmin-1.4.0 Currently there is only a single logging method in the ConfigurationManager class: log(int level, String message, Throwable t) This allows fixed strings to be logged at certain levels. If the messages are composed of dynamic content (e.g. configuration PIDs) this requires String concatenations and thus -- to prevent performance issues -- guarding the calls with isEnabled(int level) calls. This clutters the code. To improve this situation a new logging method log(int level, String format, Object[] args) should be added where format is a MessageFormat pattern and args is the MessageFormat argument vector. The message is generated calling MessageFormat.format(format, args) and the result used as the message argument to the existing log method. If the last entry in the args array is a Throwable it is used as the Throwable argument to the log method. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (FELIX-3177) Remove temporary inclusion of OSGi classes
Remove temporary inclusion of OSGi classes -- Key: FELIX-3177 URL: https://issues.apache.org/jira/browse/FELIX-3177 Project: Felix Issue Type: Task Components: Configuration Admin Affects Versions: configadmin-1.4.0 Reporter: Felix Meschberger Once the OSGi Alliance releases an official build of the Configuration Admin 1.4 API classes to the central maven repository, the temporary inclusion of the ConfigurationEvent and ConfigurationPermission classes should be reverted. Also the export and import versions of the Configuration Admin package should be deduced from the official library (again). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (FELIX-3176) Implement Configuration Admin 1.4 changes
Implement Configuration Admin 1.4 changes - Key: FELIX-3176 URL: https://issues.apache.org/jira/browse/FELIX-3176 Project: Felix Issue Type: New Feature Components: Configuration Admin Affects Versions: configadmin-1.2.10 Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: configadmin-1.4.0 As part of the Residential Specification 4.3 the Configuration Admin Service will be updated to Version 1.4 with the following changes (from the spec): • Allow multiple bundles to register with the same PID to access to the same configuration, see Location Binding. • Extended Configuration Permission with a location name so that it can be used to prevent access to Configurations marked with a certain location, enabling regions, see Regions. Our implementation should be adapted to continue to serve as the RI -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (FELIX-3175) RankingComparator results in wrong results
RankingComparator results in wrong results -- Key: FELIX-3175 URL: https://issues.apache.org/jira/browse/FELIX-3175 Project: Felix Issue Type: Bug Components: Configuration Admin Affects Versions: configadmin-1.2.10 Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: configadmin-1.2.12 The RankingComparator class works perfectly ordering ServiceReference instances according to the specification. When applied to array sorting (Arrays.sort) and sorted sets (TreeSet), the resulting order is from lowest to highest ServiceReference thus not returning the highest ranking service first. This is wrong: the highest ranking service should be sorted on the first position and the lowest ranking service should be placed on the last position. To fix this, the RankingComparator should return revers results: -1 if service1 is higher than service2 0 if service1 is the same as service2 (according to service id) +1 if service1 is lower than service2 This should also be tested using unit tests. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (FELIX-3169) Add support for new PASSWORD attribute type of Metatype service
Add support for new PASSWORD attribute type of Metatype service
Key: FELIX-3169
URL: https://issues.apache.org/jira/browse/FELIX-3169
Project: Felix
Issue Type: Improvement
Components: Maven SCR Plugin
Affects Versions: scr annotations 1.6.0, scr generator 1.1.2
Reporter: Felix Meschberger
To complement support for the new PASSWORD attribute type of the Metatype
service (see FELIX-3167) the SCR plugin should add support for this type, too:
Probably by adding a new
String[] passwordValue() default {};
definition which causes the metatype descriptor to use the PASSWORD type and
the DS descriptor to use String.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (FELIX-3167) Add support for new PASSWORD attribute type
Add support for new PASSWORD attribute type --- Key: FELIX-3167 URL: https://issues.apache.org/jira/browse/FELIX-3167 Project: Felix Issue Type: Improvement Components: Metatype Service Affects Versions: metatype-1.0.4 Reporter: Felix Meschberger OSGi Residential Specification 4.3 includes an update to the Metatype service supporting a new attribute type PASSWORD.  -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (FELIX-3168) Add support for new PASSWORD attribute type of Metatype service
Add support for new PASSWORD attribute type of Metatype service --- Key: FELIX-3168 URL: https://issues.apache.org/jira/browse/FELIX-3168 Project: Felix Issue Type: Improvement Components: Web Console Affects Versions: webconsole-3.1.8 Reporter: Felix Meschberger OSGi Residential Specification 4.3 includes an update to the Metatype service supporting a new attribute type PASSWORD. The WebConsole configuration admin page must be extended to support this new attribute type with an appropriate input field (probably password and not maybe even not transferring the actual configuration value to the client ...) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (FELIX-3158) Upgrade to Felix parent POM 2.1 and use managed ant plugin version
Upgrade to Felix parent POM 2.1 and use managed ant plugin version -- Key: FELIX-3158 URL: https://issues.apache.org/jira/browse/FELIX-3158 Project: Felix Issue Type: Task Components: Declarative Services (SCR) Affects Versions: scr-1.6.0 Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: scr-1.6.2 Felix parent POM 2.1 fixes a problem with the generation of the source package, so the scr project should update before the next release. Also the Ant plugin should be used at the managed version instead of a locally coded version. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (FELIX-3134) Wrong default HTTPS port used (433)
Wrong default HTTPS port used (433) --- Key: FELIX-3134 URL: https://issues.apache.org/jira/browse/FELIX-3134 Project: Felix Issue Type: Bug Components: HTTP Service Affects Versions: http-2.2.0 Reporter: Felix Meschberger Assignee: Felix Meschberger The Jetty based implementation of the HTTP Service uses port 433 as the default port for HTTPS. This is problematic for non-root situations on *nix platforms (server ports <1024 are not allowed for non-root users) and is not the standard HTTPS port (which is 443). We should change the default to be 8443 -- which goes along the lines of using 8080 as default for the HTTP port. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
