[JBoss JIRA] Created: (JBIDE-2586) "Content Assist" did not complete normally" exception is occured for struts cofiguration file.
by Anton Klimkovich (JIRA)
"Content Assist" did not complete normally" exception is occured for struts cofiguration file.
----------------------------------------------------------------------------------------------
Key: JBIDE-2586
URL: https://jira.jboss.org/jira/browse/JBIDE-2586
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: struts/shale, XML Structured Editor
Affects Versions: 3.0.0.alpha
Reporter: Anton Klimkovich
Priority: Critical
Attachments: exception.txt
EXECUTE: Create struts web project kickstart
EXECUTE: Open struts-config.xml
EXECUTE: Try to call CA.
FAILURE: CA is not available.
EXECUTE: Open web.xml
EXECUTE: Call CA.
ASSERT: CA available.
EXECUTE: Switch to opened struts-config.xml
EXECUTE: Try to call CA.
FAILURE: CA available with proposal list from web.xml
EXECUTE: Close web.xml
EXECUTE: Switch to opened struts-config.xml and call CA
FAILURE: CA is not available. java.lang.NullPointerException is occured.
Log attached.
--
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
17 years, 5 months
[JBoss JIRA] Created: (JBIDE-2341) Project Archives View - don't work properly
by Aliaksey Nis (JIRA)
Project Archives View - don't work properly
-------------------------------------------
Key: JBIDE-2341
URL: http://jira.jboss.com/jira/browse/JBIDE-2341
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Archives
Affects Versions: 2.1.1
Environment: WindowsXP SP2
JBoss Tools 2.1.1GA
Reporter: Aliaksey Nis
In Project Archives View:
1. EJB JAR and EAR options don't work properly. They creates files with 22 bytes size, w/o content inside.
2.
EXECUTE: Create Seam Ear project and select it in package explorer.
EXECUTE: In Project Archives view - click on EAR option.
EXECUTE: Select compressed file, destination - Seam project folder, name - default(testseam.ear).
ASSERT: testear.ear created (but w/o content - look [1]).
EXECUTE: In Project Archives view - New Archive > click on EAR option.
EXECUTE: Select exploded archive, destination - Seam project folder, name - default(testseam.ear).
FAILURE: No exploded archive appears.
If you select different name for exploded archive - it will be created(but w/o content - look [1]),
Same issue for JAR and EJB JAR archives.
--
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
17 years, 5 months
[JBoss JIRA] Created: (JBDS-245) New Xpath wizard in server manager
by OLga Chikvina (JIRA)
New Xpath wizard in server manager
-----------------------------------
Key: JBDS-245
URL: http://jira.jboss.com/jira/browse/JBDS-245
Project: Developer Studio
Issue Type: Bug
Components: Doc - JBossAS
Affects Versions: 1.0.0.GA
Environment: RHEL - Linux version
GA JBDS - Studio version
Reporter: OLga Chikvina
Assigned To: Max Andersen
Fix For: 1.0.1
Attachments: bug_.png
Inport the Seam project. Create a new server JBoss AS 4.2 (JBoss 4.2 Runtime ). In the JBoss Server View in the bottom part create a new category for the XML Configuuration. For this category create a new XPath. In appeared New XPath wizard put /server/mbean path into XPath Pattern field making use of autocompleting. Then press Preview button. The apeared list of files under the view doesn't look well. The elements in the list have different heights. Besides, when expanding one element strange elements, like Match 0, Match , etc. , appear.
--
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
17 years, 5 months
[JBoss JIRA] Created: (JBIDE-2018) Deployment support for ESB archives
by Max Andersen (JIRA)
Deployment support for ESB archives
-----------------------------------
Key: JBIDE-2018
URL: http://jira.jboss.com/jira/browse/JBIDE-2018
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: esb, JBossAS
Affects Versions: 2.1
Reporter: Max Andersen
Fix For: 2.2.x
ESB archives are different than anything else (see http://wiki.jboss.org/wiki/JBossESBDeploymentStrategies) so they need custom deployment support.
Things to consider/figure-out:
1) Is jboss esb following some standard or is it jboss esb/jboss as specific ?
- is there more to it than what is in the deployment description on jboss.org ?
2) In WTP terms making a module type sounds the most sensible, but adding template for it for Project Archives would be interesting too
3) Consider utilizing JBoss AS runtime classpath's instead of direct references to jar's on filesystem like the "eclipse esb quickstart plugin"
4) ESB archives has a jar folder, similar to JavaEE 5 so completing our partial "jar folder classpath container" would be relevant
--
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
17 years, 5 months
[JBoss JIRA] Created: (JBIDE-2064) JBossESB graphical node/service designer
by Mark Little (JIRA)
JBossESB graphical node/service designer
----------------------------------------
Key: JBIDE-2064
URL: http://jira.jboss.com/jira/browse/JBIDE-2064
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: esb
Reporter: Mark Little
Attachments: SOA Tooling.pdf
Currently the ESB deployment descriptor is XML based but we need it to be graphically oriented. Each ESB service is a collection of actions that are re-usable components. The graphical tool would allow for the construction (within Eclipse) of a service from action chaining. The action descriptions would be storable in a repository (though that is a second level addition). We want to isolate the user from the XML as much as possible because it is prone to errors. Plus, it makes service re-usability more problematical.
--
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
17 years, 5 months