[ 
https://issues.apache.org/jira/browse/FELIX-587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12604990#action_12604990
 ] 

Dieter Wimberger commented on FELIX-587:
----------------------------------------

I have checked out a fresh working copy.

Creation is possible, but it does not seem to work properly, because it reports:
This configuration has no associated description

Here are the values returned from the Ajax call:
{"pid":"net.wimpi.telnetd.service.TelnetListenerServiceFactory-1213394666652-2","isFactory":false,"title"
:"net.wimpi.telnetd.service.TelnetListenerServiceFactory-1213394666652-2","description":"Please
 enter
 configuration properties for this configuration in the field below. This 
configuration has no associated
 description","propertylist":"properties","properties":{}}

There is a corresponding metatype description.

The way you approached to fix the chain of issues I reported (sorry for the 
messed up patch), it occurs difficult to me to track them properly. Also, I 
have a question for you: 
Do you actually have a test case? If yes, which one is it?

Regards,
Dieter




> org.apache.felix.webconsole.internal.compendium.AjaxConfigManagerAction.configForm():
>  Configuration instance for a ManagedServiceFactory will cause Exception
> -------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: FELIX-587
>                 URL: https://issues.apache.org/jira/browse/FELIX-587
>             Project: Felix
>          Issue Type: Bug
>          Components: Web Console
>            Reporter: Dieter Wimberger
>         Attachments: AjaxConfigManagerAction.java.diff, 
> FELIX-587-fmeschbe.patch
>
>
> A Configuration instance for  a ManagedServiceFactory will cause an Exception 
> in 
> org.apache.felix.webconsole.internal.compendium.AjaxConfigManagerAction.configForm(),
>  because the implementation will try to obtain an ObjectClassDefinition for 
> the Configuration pid, rather than for the corresponding factoryPid.
> Fix:
> The method should verify if a factoryPid is assigned to the Configuration 
> instance and handle this case properly.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to