[JBoss JIRA] Created: (JBDS-1167) SOA-P5 , Security , and the ESB XML in JBDS 3.0
by Gary Lamperillo (JIRA)
SOA-P5 , Security , and the ESB XML in JBDS 3.0
-----------------------------------------------
Key: JBDS-1167
URL: https://jira.jboss.org/jira/browse/JBDS-1167
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Affects Versions: 3.0.0.CR1
Reporter: Gary Lamperillo
Using security setting within an ESB Service definition requires a Security element to be added. An example of this is the PicketLink sample, security_saml. When bringing this over to a JBDS project and editing the esb.xml, the only way to add the security element is to add it in the source view.
Here is an example of the xml section to be added to a service:
<service category="SamlSecurityQuickstart"
description="This service demonstrates how a service can be configured to issue and validate a security token"
invmScope="GLOBAL" name="issueTokenService">
<security
callbackHandler="org.jboss.soa.esb.services.security.auth.login.JBossSTSIssueCallbackHandler" moduleName="saml-issue-token">
<!-- disable the security context timeout so that our security context is re-evaluated -->
<property name="org.jboss.soa.esb.services.security.contextTimeout" value="0"/>
</security>
<listeners>
......
The tooling should have "Security Settings" as an option for services.
Also, Soap Proxy should have the addition of a "Content Type Settings" as an option to allow compatibility with endpoints.
--
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
15 years, 8 months
[JBoss JIRA] Created: (JBIDE-6303) Edit Action Dialog doesn't allow to select methods with non-void return type.
by Alexey Kazakov (JIRA)
Edit Action Dialog doesn't allow to select methods with non-void return type.
-----------------------------------------------------------------------------
Key: JBIDE-6303
URL: https://jira.jboss.org/browse/JBIDE-6303
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JSF
Affects Versions: 3.1.0.GA
Reporter: Alexey Kazakov
Assignee: Viacheslav Kabanovich
Fix For: 3.2.next
1. Create JSF project. Use any KickStart template from New JSF Project wizard.
2. Add following method to the managed bean:
public String checkGuess() {
...
}
3. Open inputname.xhtml/jsp.
4. Add <h:commandButton action=""/>
5. Select this component in visual part, right click. Select <h:commandButton> Attributes.
6. Select action attribute.
7. Select its value and click "..." button.
8. There is no checkGuess method among available Managed Beans methods.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 8 months
[JBoss JIRA] Created: (JBIDE-3315) Incomplete delete of generic exporter from .lauch file
by Francisco Jose Peredo Noguez (JIRA)
Incomplete delete of generic exporter from .lauch file
------------------------------------------------------
Key: JBIDE-3315
URL: https://jira.jboss.org/jira/browse/JBIDE-3315
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 2.1.2
Reporter: Francisco Jose Peredo Noguez
If I save my code generation options in a .launch and I try to delete one of the Generic Exporters, and then I open the file in a text editor to see if it actually deleted it, I see that it deleted the line that says:
<listEntry value="hbmtemplate1"/>
but it did not delete the this:
<mapAttribute key="org.hibernate.tools.exporters.hbmtemplate1.properties">
<mapEntry key="hibernatetool.something.toolclass" value="somepackage.SomeClass"/>
<mapEntry key="outputdir" value="/myapp/WebContent/Crud"/>
<mapEntry key="for_each" value="entity"/>
<mapEntry key="template_name" value="view/list.xhtml.ftl"/>
<mapEntry key="file_pattern" value="{class-name}List.xhtml"/>
<mapEntry key="hibernatetool.util.toolclass" value="org.hibernate.eclipse.launch.SeamUtil"/>
</mapAttribute>
This mapAttribute stuff stays there, and can only be removed if I do it manually.
--
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
15 years, 8 months
[JBoss JIRA] Created: (JBIDE-5551) ESB Editor - ScriptingAction needs additional details for language property
by Brian Fitzpatrick (JIRA)
ESB Editor - ScriptingAction needs additional details for language property
---------------------------------------------------------------------------
Key: JBIDE-5551
URL: https://jira.jboss.org/jira/browse/JBIDE-5551
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: esb
Affects Versions: 3.1.0.GA
Reporter: Brian Fitzpatrick
Assignee: Viacheslav Kabanovich
Also for the ScriptingAction, we had this comment from Kevin Conner:
> * Do we need to also include the "language" property in the UI?
>By default the ScriptingAction will determine the language based on the
extension of the file, but this can be specified explicitly should it be
necessary. I'm not sure what the options are for this section, but if
the resource name is free-form then I would suggest adding support for
the "language" property.
We should look into this further for the next release.
--
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
15 years, 8 months