2:30 a.m.
Rob Stryker created JBIDE-11660:
-----------------------------------
Summary: restart module pattern cached, does not update
Key: JBIDE-11660
URL: https://issues.jboss.org/browse/JBIDE-11660
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Reporter: Rob Stryker
Assignee: Rob Stryker
Fix For: 3.3.0.Beta1
AS7 may wish to restart modules when even a .class or a .jsp file changes. In order to
even test this and investigate the speed difference, API must be refactored to allow this
logic to be different per server-type as required.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:30 a.m.
[
https://issues.jboss.org/browse/JBIDE-11660?page=com.atlassian.jira.plugi...
]
Rob Stryker updated JBIDE-11660:
--------------------------------
Fix Version/s: 3.3.0.Beta3
(was: 3.3.0.Beta1)
Affects Version/s: 3.3.0.Beta1
(was: 3.3.0.M5)
Description:
It should now be possible to only do a full redeploy based on the reg exp. But sometimes
it doesn't work. Sometimes when you set a new reg exp, save it and restart the server,
the old pattern is still used. This should reproduce it:
1. Set up AS 7.1.1 server
2. Create Dynamic Web Project dynproj
3. Add index.jsp and home.jsp in WebContents of your project
4. In Server View open the server in server editor
5. In Application Reload Behavior check "Customize application reload..."
6. In Application Reload Behavior change the pattern to \.jsp$ - this will ensure that
every change in jsp files forces full publish - save the server editor
7. Start the server and deploy dynproj
8. Change home.jsp and save - in a few seconds you will see JBAS018565: Replaced
deployment "dynproj.war" with deployment "dynproj.war" in the Console
9. Change index.jsp and save - you will see the same as in step 8.
10. Stop the server
11. Change the pattern in server editor to index\.jsp$ - only changes in the index.jsp
should force full publish - save the editor
12. repeat steps 7.-9. - in both cases the file change will cause full publish which is
wrong - FAIL
was:AS7 may wish to restart modules when even a .class or a .jsp file changes. In order
to even test this and investigate the speed difference, API must be refactored to allow
this logic to be different per server-type as required.
restart module pattern cached, does not update
----------------------------------------------
Key: JBIDE-11660
URL: https://issues.jboss.org/browse/JBIDE-11660
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: JBossAS/Servers
Affects Versions: 3.3.0.Beta1
Reporter: Rob Stryker
Assignee: Rob Stryker
Fix For: 3.3.0.Beta3
It should now be possible to only do a full redeploy based on the reg exp. But sometimes
it doesn't work. Sometimes when you set a new reg exp, save it and restart the server,
the old pattern is still used. This should reproduce it:
1. Set up AS 7.1.1 server
2. Create Dynamic Web Project dynproj
3. Add index.jsp and home.jsp in WebContents of your project
4. In Server View open the server in server editor
5. In Application Reload Behavior check "Customize application reload..."
6. In Application Reload Behavior change the pattern to \.jsp$ - this will ensure that
every change in jsp files forces full publish - save the server editor
7. Start the server and deploy dynproj
8. Change home.jsp and save - in a few seconds you will see JBAS018565: Replaced
deployment "dynproj.war" with deployment "dynproj.war" in the Console
9. Change index.jsp and save - you will see the same as in step 8.
10. Stop the server
11. Change the pattern in server editor to index\.jsp$ - only changes in the index.jsp
should force full publish - save the editor
12. repeat steps 7.-9. - in both cases the file change will cause full publish which is
wrong - FAIL
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:36 a.m.
[
https://issues.jboss.org/browse/JBIDE-11660?page=com.atlassian.jira.plugi...
]
Rob Stryker resolved JBIDE-11660.
---------------------------------
Resolution: Done
I've removed the cache, so the pattern will compile each time it is retrieved,
however, I've added error checking to the editor to ensure that the users are aware
whether their pattern compiles or not. This lowers the risk of endless errors in the error
log.
restart module pattern cached, does not update
----------------------------------------------
Key: JBIDE-11660
URL: https://issues.jboss.org/browse/JBIDE-11660
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: JBossAS/Servers
Affects Versions: 3.3.0.Beta1
Reporter: Rob Stryker
Assignee: Rob Stryker
Fix For: 3.3.0.Beta3
It should now be possible to only do a full redeploy based on the reg exp. But sometimes
it doesn't work. Sometimes when you set a new reg exp, save it and restart the server,
the old pattern is still used. This should reproduce it:
1. Set up AS 7.1.1 server
2. Create Dynamic Web Project dynproj
3. Add index.jsp and home.jsp in WebContents of your project
4. In Server View open the server in server editor
5. In Application Reload Behavior check "Customize application reload..."
6. In Application Reload Behavior change the pattern to \.jsp$ - this will ensure that
every change in jsp files forces full publish - save the server editor
7. Start the server and deploy dynproj
8. Change home.jsp and save - in a few seconds you will see JBAS018565: Replaced
deployment "dynproj.war" with deployment "dynproj.war" in the Console
9. Change index.jsp and save - you will see the same as in step 8.
10. Stop the server
11. Change the pattern in server editor to index\.jsp$ - only changes in the index.jsp
should force full publish - save the editor
12. repeat steps 7.-9. - in both cases the file change will cause full publish which is
wrong - FAIL
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:36 a.m.
[
https://issues.jboss.org/browse/JBIDE-11660?page=com.atlassian.jira.plugi...
]
Martin Malina closed JBIDE-11660.
---------------------------------
Verified in JBT nightly 2010-04-29
restart module pattern cached, does not update
----------------------------------------------
Key: JBIDE-11660
URL: https://issues.jboss.org/browse/JBIDE-11660
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: JBossAS/Servers
Affects Versions: 3.3.0.Beta1
Reporter: Rob Stryker
Assignee: Rob Stryker
Fix For: 3.3.0.Beta3
It should now be possible to only do a full redeploy based on the reg exp. But sometimes
it doesn't work. Sometimes when you set a new reg exp, save it and restart the server,
the old pattern is still used. This should reproduce it:
1. Set up AS 7.1.1 server
2. Create Dynamic Web Project dynproj
3. Add index.jsp and home.jsp in WebContents of your project
4. In Server View open the server in server editor
5. In Application Reload Behavior check "Customize application reload..."
6. In Application Reload Behavior change the pattern to \.jsp$ - this will ensure that
every change in jsp files forces full publish - save the server editor
7. Start the server and deploy dynproj
8. Change home.jsp and save - in a few seconds you will see JBAS018565: Replaced
deployment "dynproj.war" with deployment "dynproj.war" in the Console
9. Change index.jsp and save - you will see the same as in step 8.
10. Stop the server
11. Change the pattern in server editor to index\.jsp$ - only changes in the index.jsp
should force full publish - save the editor
12. repeat steps 7.-9. - in both cases the file change will cause full publish which is
wrong - FAIL
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5089
days inactive
5093
days old
jbosstools-issues@lists.jboss.org
3 comments
2 participants
participants (2)
-
Martin Malina (JIRA) -
Rob Stryker (JIRA)