[JBoss JIRA] Created: (JBIDE-9076) Port text field in server editor should not allow you to enter alphanumeric values
by Andre Dietisheim (JIRA)
Port text field in server editor should not allow you to enter alphanumeric values
----------------------------------------------------------------------------------
Key: JBIDE-9076
URL: https://issues.jboss.org/browse/JBIDE-9076
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: JBossAS
Affects Versions: 3.3.0.M1
Reporter: Andre Dietisheim
Assignee: Rob Stryker
Fix For: 3.3.x
Attachments: invalid-port-value.png, saved-even-though-invalid.png
The server editor allows you to enter alphanumeric aka invalid port values. If you then try to save the editor, you'll get an error that tells you that the editor could not be saved because of invalid values.
!invalid-port-value.png!
The editor gets saved though - the editor gets clean even though the value is still present in the editor.
!saved-even-though-invalid.png!
We can avoid this easily by disallowing alphanumeric values while typing.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years
[JBoss JIRA] Created: (JBIDE-9326) Replace Delegates-mapping by proper solution
by Andre Dietisheim (JIRA)
Replace Delegates-mapping by proper solution
--------------------------------------------
Key: JBIDE-9326
URL: https://issues.jboss.org/browse/JBIDE-9326
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: JBossAS
Affects Versions: 3.3.0.M3
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Fix For: 3.3.x
We implementation our own delegation on top of the wtp delegation because WTP is not flexible enough for our needs. We did not want to have separate servers for remote/local behavior and we therefore provide a single server which may be switch to local/remote behavior and delegates to appropriate components.
The components are currently mapped to local/remote behaviors on behalf of static maps:
* DelegatingJBoss7ServerBehavior#addDelegateMapping
* DelegatingJBoss7ServerBehavior#getDelegateMap
* DelegatingServerBehavior#addDelegateMapping
* DelegatingServerBehavior#getDelegate
etc.
This solution works but is far from optimal since all those statics make subclassing pretty hard. Furthermore it basically does what the platform provides by extensions and osgi services.
We should replace the current implementation by those platform mechanisms.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years
[JBoss JIRA] Created: (JBIDE-8458) Mavenized Seam EAR Project can't be deployed to JBoss AS 6.0.0.Final
by Snjezana Peco (JIRA)
Mavenized Seam EAR Project can't be deployed to JBoss AS 6.0.0.Final
--------------------------------------------------------------------
Key: JBIDE-8458
URL: https://issues.jboss.org/browse/JBIDE-8458
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: maven
Affects Versions: 3.2.0.Final
Reporter: Snjezana Peco
Assignee: Snjezana Peco
Fix For: 3.3.0.M1
If you create a mavenized Seam EAR project using the New Seam Web Project wizard, it will create application.xml that contains the following entries:
...
<module>
<ejb>/test-ejb.jar</ejb>
</module>
<module>
<ejb>/jboss-seam-2.2.1.Final.jar</ejb>
</module>
<module>
<web>
<web-uri>/test.war</web-uri>
<context-root>test</context-root>
</web>
</module>
...
Such a project can be deployed to JBoss AS <= 6.0, but can't to JBoss AS 6.0.0
A workaround is to open the EAR's pom.xml and remove the bundleDir element for ejb and web modules.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years
[JBoss JIRA] Created: (JBIDE-9748) Openshift service: JSonSanitizer should be able to handle valid json objects with escaped quotes
by Andre Dietisheim (JIRA)
Openshift service: JSonSanitizer should be able to handle valid json objects with escaped quotes
------------------------------------------------------------------------------------------------
Key: JBIDE-9748
URL: https://issues.jboss.org/browse/JBIDE-9748
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M4
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Fix For: 3.3.0.M4
The JSonSanitzer currently is in place to 'sanitize' invalid json that is being responded by the openshift service. It corrects erroneously quotes json objects with escaped quotes in it:
{code}
...
"aJsonObjectHere": "{
\"aNestedProperty\" : \"withAStringValue\"
}"
...
{code}
*This sanitizer should be able to handle valid and invalid json since openshift could fix their bug after we release our plugins. *
The current implementation would most likely sanitize string values erroneously, if they have escaped quotes in the value:
{code}
"aStringValueWithA\"Quote"
{code}
The above value would get transformed into an invalid value if the json object would be reported in a valid way (aka not quoted and the quotes in it not escaped):
{code}
...
"aJsonObjectHere": {
"aNestedProperty\" : "withAStringValueWithA\"Quote"
}
{code}
The above would become:
{code}
...
"aJsonObjectHere": {
"aNestedProperty\" : "withAStringValueWithA\"Quote"
}
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years