[
https://jira.jboss.org/jira/browse/JBIDE-2808?page=com.atlassian.jira.plu...
]
Alexey Kazakov commented on JBIDE-2808:
---------------------------------------
We seem to have to add new builder that will build a model for our new KB.
The idea is to have a few kinds of resources to collect all info about
tag/attributes/values:
ITagLibrary - basic intarface
And a few subinterfaces:
ITLDLibrary - tld
IFacesConfigTagLibrary - collects an info about components from faces-config
IFaceletTagLibrary - facelet tag lib.
ICustomTagLibrary - collects an info from our old-style static xmls from KB plugin.
So I think the best way to collect all this info is introducing new builder.
This new builder will build the model for project and all clients (CA, OpenOns,
Validators,...) will use it.
And I would unite the builder with JSF nature.
Is it ok that our KB will work only with JSF projects? We woun't lose any
functionality because our old KB worked only with JSF. There weren't any artfitiont
restriction. We just didn't have any need to use our KB for not JSF projects
(struts/plain jsp).
Improve/refactor org.jboss.tools.common.kb plugin.
--------------------------------------------------
Key: JBIDE-2808
URL:
https://jira.jboss.org/jira/browse/JBIDE-2808
Project: Tools (JBoss Tools)
Issue Type: Task
Components: common
Affects Versions: 3.0.0.beta1
Reporter: Alexey Kazakov
Assignee: Alexey Kazakov
Priority: Blocker
Fix For: 3.1.0.M1
Current KB plugin has some problems, which we have to solve.
- KB uses a set of XMLs. One XML for one tag library. If we want to support some new tag
library we have to convert it to special XML and add it to KB plugin manually. It would be
nice to have some default behavior for unknown TLDs.
- It doesn't work with facelets tag libraries.
- Our XMLs are quite big. It consumes memory in case some JSP/Facelet pages use a lot of
tag libraries. Also parsing big XML is quite slow process. It effects time of first
starting JSP/HTML editors.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira