[JBoss JIRA] Created: (AS7-810) Change DeploymentRootMountProcessor To Use Marker to Determine Whether to Mount Exploded
by Benjamin Browning (JIRA)
Change DeploymentRootMountProcessor To Use Marker to Determine Whether to Mount Exploded
----------------------------------------------------------------------------------------
Key: AS7-810
URL: https://issues.jboss.org/browse/AS7-810
Project: Application Server 7
Issue Type: Feature Request
Affects Versions: 7.0.0.Beta3
Reporter: Benjamin Browning
Assignee: Jason Greene
Right now DeploymentRootMountProcessor is hard-coded to only mount .war files exploded. For TorqueBox, we have the need to mount .knob files exploded. It would be great if there was some ExplodedRootMarker that DeploymentRootMountProcessor checked instead of looking at the file extension. This would mean moving Phase.STRUCTURE_MOUNT to some value greater than 0 to allow an earlier processor to call ExplodedRootMarker.mark(...) for .war files and let TorqueBox create its own processor to do the same for .knob files.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months
[JBoss JIRA] Created: (AS7-948) "port-offset=0" will be persisted as "undefined"
by Heiko Braun (JIRA)
"port-offset=0" will be persisted as "undefined"
------------------------------------------------
Key: AS7-948
URL: https://issues.jboss.org/browse/AS7-948
Project: Application Server 7
Issue Type: Bug
Components: Domain Management
Reporter: Heiko Braun
Assignee: Brian Stansberry
Priority: Critical
Fix For: 7.0.0.CR1
If I add this to host.xml:
<socket-binding-group ref="standard-sockets" port-offset="0"/>
it will be persisted as
<socket-binding-group ref="standard-sockets" port-offset="undefined"/>
which prevents a successful server boot in a subsequent step
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months
[JBoss JIRA] Created: (JBAS-9394) Web Services no longer deployed with latest checkout
by Frank Langelage (JIRA)
Web Services no longer deployed with latest checkout
----------------------------------------------------
Key: JBAS-9394
URL: https://issues.jboss.org/browse/JBAS-9394
Project: Legacy JBoss Application Server 6
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 6.1.0
Environment: Oracle JDK 1.6.0_25 on Solaris SPARC 10
Reporter: Frank Langelage
Web Services are no longer recognized and deployed with the latest subversion checkout ob JBoss AS 6.1.0.
The older checkout of JBoss AS 6.0.1 running the same app publishes the web services as expected.
Some of the latest checkins broke this. Don't know which one exactly.
I created a test project which creates an ear file containing one war file which contains two webservices.
The first one uses a web.xml file to define the servlet. This service is recognized an deployed.
The second one uses the WebServlet annotation like our app does successfully on 6.0.1. This is not recognized anymore.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months
[JBoss JIRA] Created: (SECURITY-582) Fix principal name parsing for SPNEGO negotiation
by Marcus Moyses (JIRA)
Fix principal name parsing for SPNEGO negotiation
-------------------------------------------------
Key: SECURITY-582
URL: https://issues.jboss.org/browse/SECURITY-582
Project: PicketBox (JBoss Security and Identity Management)
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Negotiation
Affects Versions: Negotiation_2.1.0
Reporter: Marcus Moyses
Assignee: Marcus Moyses
Name parsing is not working correctly. Exception thrown:
Error parsing/decoding ticket: Input length not multiple of 8 bytes
org.jboss.security.negotiation.NegotiationException: Input length not multiple of 8 bytes
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months