[JBoss JIRA] Created: (JBIDE-2399) Validation of ESB files for specific SOA-P versions
by John Graham (JIRA)
Validation of ESB files for specific SOA-P versions
---------------------------------------------------
Key: JBIDE-2399
URL: http://jira.jboss.com/jira/browse/JBIDE-2399
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: esb
Reporter: John Graham
Assigned To: John Graham
Given that the SOA-P run time will change from release to release, we need some generic way of validating ESB files in Eclipse projects for specific run time versions. This might be done at the package level (that is, when creating a deployment package), but ideally would be done "live:" as the user makes changes, warnings/errors would appear in the Eclipse Problems view. To accomplish this, we would need to set a (minimum? probably not, because backward compatibility is not supported) "SOA-P run time level" (like the JVM level) and have a validation model for checking. The idea is to avoid simple compatibility errors appearing at run time where they could have been noticed at design time.
(This is related to, but larger than, the ESB reference tracking work.)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months
[JBoss JIRA] Created: (JBIDE-2808) Improve/refactor org.jboss.tools.common.kb plugin.
by Alexey Kazakov (JIRA)
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
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
14 years, 10 months
[JBoss JIRA] Created: (JBIDE-2190) Seam 2.0.1 EAR web project can not be started on JBoss AS 4.3
by Anton Klimkovich (JIRA)
Seam 2.0.1 EAR web project can not be started on JBoss AS 4.3
-------------------------------------------------------------
Key: JBIDE-2190
URL: http://jira.jboss.com/jira/browse/JBIDE-2190
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Seam
Affects Versions: 2.1.0.CR1
Environment: JDK 1.5.0
OS=win32, ARCH=x86, WS=win32
1.1.0.CR1
Reporter: Anton Klimkovich
Attachments: exception.txt
EXECUTE: Create Seam 2.0.1 Ear web project
ASSERT: jboss-seam.jar deployed to server
EXECUTE: Press Clean/Publish button
ASSERT: *-ejb.jar appeares in deploy directory
EXECUTE: Run project on Jboss AS 4.3
FAILURE: The project can not be started because of some exceptions in console.
Log attached. (exception.txt)
Created Seam 2.0.1 Ear web project can be started on Jboss AS 4.2
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 11 months