[JBoss JIRA] Created: (JBDS-493) Escaping of Spaces in Project Name when generate Package Names
by Jim Tyrrell (JIRA)
Escaping of Spaces in Project Name when generate Package Names
--------------------------------------------------------------
Key: JBDS-493
URL: https://jira.jboss.org/jira/browse/JBDS-493
Project: Developer Studio
Issue Type: Feature Request
Affects Versions: 2.0.0.beta1
Environment: Linux Fedora 10
Reporter: Jim Tyrrell
Attachments: ProjectNameSpacesAreNotEscaped.png
When using the New Seam Project Wizard the Project name with a space in it was copied into the Package name without escaping or changing out the space to an underscore. I guess this mean that valid characters need to be checked for in the creation of the package name or the project?. Also it would be nice if the First Capital letter Capitalization was made to be lower case. See the attached screen shot. Not sure what the rules are for package naming or what conventions are used, but they should be injected inserted for you automatically.
--
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, 4 months
[JBoss JIRA] Created: (JBIDE-2022) Extend ESB Editor to support some important objects presented in XML with "free content" (not specified by XML schema)
by Viacheslav Kabanovich (JIRA)
Extend ESB Editor to support some important objects presented in XML with "free content" (not specified by XML schema)
----------------------------------------------------------------------------------------------------------------------
Key: JBIDE-2022
URL: http://jira.jboss.com/jira/browse/JBIDE-2022
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: esb
Affects Versions: 2.1.0.beta1
Reporter: Viacheslav Kabanovich
Assigned To: Viacheslav Kabanovich
XML schema for ESB allows <property> tag to have any XML content,
and it allows for elements using tags <property> as its children to declare
any set of properties.
That makes XML quite flexible, but the ESB editor based on that only cannot
assist customers in setting specific properties. We have only common form
for editing elements described as ANY in dtd/schema.
What is done for presentation of <route-to> and <object-path> is just a small
portion of what ESB editor may be customized into.
It seems that since actions, for instance, are based on Java classes,
the structure of a specific action is well defined by its Java class,
both property names and their types.
It means that each action Java class could contribute to XML schema and specific
forms in ESB editor.
Of course, it may not be reasonable to complicate actual ESB XML schema,
but editor may be based on an extended schema.
So, do you think that ESB editor should recognize some specific objects
(e.g. action based on org.jboss.soa.esb.actions.ContentBasedRouter)
and implement for them more sophisticated set of forms and
context commands than those based on generic schema?
--
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, 4 months