7:04 p.m.
JBoss AS 5 copies exploded ear to tmp directory
-----------------------------------------------
Key: JBAS-6590
URL: https://jira.jboss.org/jira/browse/JBAS-6590
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Deployers
Affects Versions: JBossAS-5.0.1.GA
Environment: JBoss AS 5.0.1.GA
JDK 1.5
Mac OS X 10.5.6
Reporter: Kenneth Christensen
Assignee: Ales Justin
Priority: Critical
I have an explode ear file (directory) - see attached file: ear.jpg
When I deploy the exploded ear file to JBoss AS 4.2.3 and later want to update a xhtml
file in the exploded ear by my ANT script everything works fine (i.e. I can refresh my
browser and see the changes without redeployment of the ear or war):
<!-- Target: deploy.xhtml.to.jboss -->
<target name="deploy.xhtml.to.jboss" description="Deploy xhtml files
to JBoss" if="deployed">
<copy
todir="${jboss.deploy.dir}/${jboss.context.path}/${war.file.name}/xhtml">
<fileset dir="${view.dir}/xhtml" includes="**/*"/>
</copy>
</target>
Because the exploded ear file is not copied to JBoss tmp dir.
But JBoss AS 5 always makes a copy of my exploded ear file and copies it to the tmp dir
where it's the current 'working copy/version' used by JBoss AS - see attached
file: tmp-ear.jpg
My ANT task will not work anymore because the 'working copy/version' used by JBoss
AS now is in the tmp dir and not in the deploy dir.
I really don't want to 'touch' web.xml (or other meta files) to trigger a full
redeployment when I need to make changes to my web files (xhtml, css, javascript, images
etc.).
Could we please have the 'old' behaviour from JBoss AS 4.2.X implemented into
JBoss AS 5 - or is there a workaround to above problem?
--
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
7:06 p.m.
New subject: [JBoss JIRA] Updated: (JBAS-6590) JBoss AS 5 copies exploded ear to tmp directory
[
https://jira.jboss.org/jira/browse/JBAS-6590?page=com.atlassian.jira.plug...
]
Kenneth Christensen updated JBAS-6590:
--------------------------------------
Attachment: ear.jpg
tmp-ear.jpg
JBoss AS 5 copies exploded ear to tmp directory
-----------------------------------------------
Key: JBAS-6590
URL: https://jira.jboss.org/jira/browse/JBAS-6590
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Deployers
Affects Versions: JBossAS-5.0.1.GA
Environment: JBoss AS 5.0.1.GA
JDK 1.5
Mac OS X 10.5.6
Reporter: Kenneth Christensen
Assignee: Ales Justin
Priority: Critical
Attachments: ear.jpg, tmp-ear.jpg
I have an explode ear file (directory) - see attached file: ear.jpg
When I deploy the exploded ear file to JBoss AS 4.2.3 and later want to update a xhtml
file in the exploded ear by my ANT script everything works fine (i.e. I can refresh my
browser and see the changes without redeployment of the ear or war):
<!-- Target: deploy.xhtml.to.jboss -->
<target name="deploy.xhtml.to.jboss" description="Deploy xhtml
files to JBoss" if="deployed">
<copy
todir="${jboss.deploy.dir}/${jboss.context.path}/${war.file.name}/xhtml">
<fileset dir="${view.dir}/xhtml" includes="**/*"/>
</copy>
</target>
Because the exploded ear file is not copied to JBoss tmp dir.
But JBoss AS 5 always makes a copy of my exploded ear file and copies it to the tmp dir
where it's the current 'working copy/version' used by JBoss AS - see attached
file: tmp-ear.jpg
My ANT task will not work anymore because the 'working copy/version' used by
JBoss AS now is in the tmp dir and not in the deploy dir.
I really don't want to 'touch' web.xml (or other meta files) to trigger a
full redeployment when I need to make changes to my web files (xhtml, css, javascript,
images etc.).
Could we please have the 'old' behaviour from JBoss AS 4.2.X implemented into
JBoss AS 5 - or is there a workaround to above problem?
--
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
7:13 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-6590) JBoss AS 5 copies exploded ear to tmp directory
[
https://jira.jboss.org/jira/browse/JBAS-6590?page=com.atlassian.jira.plug...
]
Kenneth Christensen commented on JBAS-6590:
-------------------------------------------
BTW: It's really critical for me and my co-workers when we're developing to JBoss
AS 5 - I really hope there is a workaround, otherwise we can be forced to go back to JBoss
AS 4.2.3.
JBoss AS 5 copies exploded ear to tmp directory
-----------------------------------------------
Key: JBAS-6590
URL: https://jira.jboss.org/jira/browse/JBAS-6590
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Deployers
Affects Versions: JBossAS-5.0.1.GA
Environment: JBoss AS 5.0.1.GA
JDK 1.5
Mac OS X 10.5.6
Reporter: Kenneth Christensen
Assignee: Ales Justin
Priority: Critical
Attachments: ear.jpg, tmp-ear.jpg
I have an explode ear file (directory) - see attached file: ear.jpg
When I deploy the exploded ear file to JBoss AS 4.2.3 and later want to update a xhtml
file in the exploded ear by my ANT script everything works fine (i.e. I can refresh my
browser and see the changes without redeployment of the ear or war):
<!-- Target: deploy.xhtml.to.jboss -->
<target name="deploy.xhtml.to.jboss" description="Deploy xhtml
files to JBoss" if="deployed">
<copy
todir="${jboss.deploy.dir}/${jboss.context.path}/${war.file.name}/xhtml">
<fileset dir="${view.dir}/xhtml" includes="**/*"/>
</copy>
</target>
Because the exploded ear file is not copied to JBoss tmp dir.
But JBoss AS 5 always makes a copy of my exploded ear file and copies it to the tmp dir
where it's the current 'working copy/version' used by JBoss AS - see attached
file: tmp-ear.jpg
My ANT task will not work anymore because the 'working copy/version' used by
JBoss AS now is in the tmp dir and not in the deploy dir.
I really don't want to 'touch' web.xml (or other meta files) to trigger a
full redeployment when I need to make changes to my web files (xhtml, css, javascript,
images etc.).
Could we please have the 'old' behaviour from JBoss AS 4.2.X implemented into
JBoss AS 5 - or is there a workaround to above problem?
--
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
12:53 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-6590) JBoss AS 5 copies exploded ear to tmp directory
[
https://jira.jboss.org/jira/browse/JBAS-6590?page=com.atlassian.jira.plug...
]
Max Rydahl Andersen commented on JBAS-6590:
-------------------------------------------
I haven't confirmed this myself yet, but if this is true that is a major regression
compared to what we rely on in tooling too...interested to hear what causes it ?
JBoss AS 5 copies exploded ear to tmp directory
-----------------------------------------------
Key: JBAS-6590
URL: https://jira.jboss.org/jira/browse/JBAS-6590
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Deployers
Affects Versions: JBossAS-5.0.1.GA
Environment: JBoss AS 5.0.1.GA
JDK 1.5
Mac OS X 10.5.6
Reporter: Kenneth Christensen
Assignee: Ales Justin
Priority: Critical
Attachments: ear.jpg, tmp-ear.jpg
I have an explode ear file (directory) - see attached file: ear.jpg
When I deploy the exploded ear file to JBoss AS 4.2.3 and later want to update a xhtml
file in the exploded ear by my ANT script everything works fine (i.e. I can refresh my
browser and see the changes without redeployment of the ear or war):
<!-- Target: deploy.xhtml.to.jboss -->
<target name="deploy.xhtml.to.jboss" description="Deploy xhtml
files to JBoss" if="deployed">
<copy
todir="${jboss.deploy.dir}/${jboss.context.path}/${war.file.name}/xhtml">
<fileset dir="${view.dir}/xhtml" includes="**/*"/>
</copy>
</target>
Because the exploded ear file is not copied to JBoss tmp dir.
But JBoss AS 5 always makes a copy of my exploded ear file and copies it to the tmp dir
where it's the current 'working copy/version' used by JBoss AS - see attached
file: tmp-ear.jpg
My ANT task will not work anymore because the 'working copy/version' used by
JBoss AS now is in the tmp dir and not in the deploy dir.
I really don't want to 'touch' web.xml (or other meta files) to trigger a
full redeployment when I need to make changes to my web files (xhtml, css, javascript,
images etc.).
Could we please have the 'old' behaviour from JBoss AS 4.2.X implemented into
JBoss AS 5 - or is there a workaround to above problem?
--
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
3:38 p.m.
New subject: [JBoss JIRA] Updated: (JBAS-6590) JBoss AS 5 copies exploded ear to tmp directory
[
https://jira.jboss.org/jira/browse/JBAS-6590?page=com.atlassian.jira.plug...
]
Kenneth Christensen updated JBAS-6590:
--------------------------------------
Attachment: jboss5-test.ear.zip
JBoss AS 5 copies exploded ear to tmp directory
-----------------------------------------------
Key: JBAS-6590
URL: https://jira.jboss.org/jira/browse/JBAS-6590
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Deployers
Affects Versions: JBossAS-5.0.1.GA
Environment: JBoss AS 5.0.1.GA
JDK 1.5
Mac OS X 10.5.6
Reporter: Kenneth Christensen
Assignee: Ales Justin
Priority: Critical
Attachments: ear.jpg, jboss5-test.ear.zip, tmp-ear.jpg
I have an explode ear file (directory) - see attached file: ear.jpg
When I deploy the exploded ear file to JBoss AS 4.2.3 and later want to update a xhtml
file in the exploded ear by my ANT script everything works fine (i.e. I can refresh my
browser and see the changes without redeployment of the ear or war):
<!-- Target: deploy.xhtml.to.jboss -->
<target name="deploy.xhtml.to.jboss" description="Deploy xhtml
files to JBoss" if="deployed">
<copy
todir="${jboss.deploy.dir}/${jboss.context.path}/${war.file.name}/xhtml">
<fileset dir="${view.dir}/xhtml" includes="**/*"/>
</copy>
</target>
Because the exploded ear file is not copied to JBoss tmp dir.
But JBoss AS 5 always makes a copy of my exploded ear file and copies it to the tmp dir
where it's the current 'working copy/version' used by JBoss AS - see attached
file: tmp-ear.jpg
My ANT task will not work anymore because the 'working copy/version' used by
JBoss AS now is in the tmp dir and not in the deploy dir.
I really don't want to 'touch' web.xml (or other meta files) to trigger a
full redeployment when I need to make changes to my web files (xhtml, css, javascript,
images etc.).
Could we please have the 'old' behaviour from JBoss AS 4.2.X implemented into
JBoss AS 5 - or is there a workaround to above problem?
--
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
3:44 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-6590) JBoss AS 5 copies exploded ear to tmp directory
[
https://jira.jboss.org/jira/browse/JBAS-6590?page=com.atlassian.jira.plug...
]
Kenneth Christensen commented on JBAS-6590:
-------------------------------------------
Looks like it have something to do with JBoss Seam !? - You can try to deploy the unzipped
jboss5-test.ear.zip to JBoss AS 5 deploy dir.
I have tried it with a simple EAR and WAR file, and it works fine - i.e. no copy of the
EAR or WAR file in the tmp dir.
JBoss AS 5 copies exploded ear to tmp directory
-----------------------------------------------
Key: JBAS-6590
URL: https://jira.jboss.org/jira/browse/JBAS-6590
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Deployers
Affects Versions: JBossAS-5.0.1.GA
Environment: JBoss AS 5.0.1.GA
JDK 1.5
Mac OS X 10.5.6
Reporter: Kenneth Christensen
Assignee: Ales Justin
Priority: Critical
Attachments: ear.jpg, jboss5-test.ear.zip, tmp-ear.jpg
I have an explode ear file (directory) - see attached file: ear.jpg
When I deploy the exploded ear file to JBoss AS 4.2.3 and later want to update a xhtml
file in the exploded ear by my ANT script everything works fine (i.e. I can refresh my
browser and see the changes without redeployment of the ear or war):
<!-- Target: deploy.xhtml.to.jboss -->
<target name="deploy.xhtml.to.jboss" description="Deploy xhtml
files to JBoss" if="deployed">
<copy
todir="${jboss.deploy.dir}/${jboss.context.path}/${war.file.name}/xhtml">
<fileset dir="${view.dir}/xhtml" includes="**/*"/>
</copy>
</target>
Because the exploded ear file is not copied to JBoss tmp dir.
But JBoss AS 5 always makes a copy of my exploded ear file and copies it to the tmp dir
where it's the current 'working copy/version' used by JBoss AS - see attached
file: tmp-ear.jpg
My ANT task will not work anymore because the 'working copy/version' used by
JBoss AS now is in the tmp dir and not in the deploy dir.
I really don't want to 'touch' web.xml (or other meta files) to trigger a
full redeployment when I need to make changes to my web files (xhtml, css, javascript,
images etc.).
Could we please have the 'old' behaviour from JBoss AS 4.2.X implemented into
JBoss AS 5 - or is there a workaround to above problem?
--
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
4:23 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-6590) JBoss AS 5 copies exploded ear to tmp directory
[
https://jira.jboss.org/jira/browse/JBAS-6590?page=com.atlassian.jira.plug...
]
Ales Justin commented on JBAS-6590:
-----------------------------------
Yes, this is Seam specific.
This is what Seam guys wanted:
* https://jira.jboss.org/jira/browse/JBSEAM-3702
* http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4203667#...
You can remove this SeamModificationTypeMatcher in seam-deployers-jboss-beans.xml in
seam.deployer in deployers/.
JBoss AS 5 copies exploded ear to tmp directory
-----------------------------------------------
Key: JBAS-6590
URL: https://jira.jboss.org/jira/browse/JBAS-6590
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Deployers
Affects Versions: JBossAS-5.0.1.GA
Environment: JBoss AS 5.0.1.GA
JDK 1.5
Mac OS X 10.5.6
Reporter: Kenneth Christensen
Assignee: Ales Justin
Priority: Critical
Attachments: ear.jpg, jboss5-test.ear.zip, tmp-ear.jpg
I have an explode ear file (directory) - see attached file: ear.jpg
When I deploy the exploded ear file to JBoss AS 4.2.3 and later want to update a xhtml
file in the exploded ear by my ANT script everything works fine (i.e. I can refresh my
browser and see the changes without redeployment of the ear or war):
<!-- Target: deploy.xhtml.to.jboss -->
<target name="deploy.xhtml.to.jboss" description="Deploy xhtml
files to JBoss" if="deployed">
<copy
todir="${jboss.deploy.dir}/${jboss.context.path}/${war.file.name}/xhtml">
<fileset dir="${view.dir}/xhtml" includes="**/*"/>
</copy>
</target>
Because the exploded ear file is not copied to JBoss tmp dir.
But JBoss AS 5 always makes a copy of my exploded ear file and copies it to the tmp dir
where it's the current 'working copy/version' used by JBoss AS - see attached
file: tmp-ear.jpg
My ANT task will not work anymore because the 'working copy/version' used by
JBoss AS now is in the tmp dir and not in the deploy dir.
I really don't want to 'touch' web.xml (or other meta files) to trigger a
full redeployment when I need to make changes to my web files (xhtml, css, javascript,
images etc.).
Could we please have the 'old' behaviour from JBoss AS 4.2.X implemented into
JBoss AS 5 - or is there a workaround to above problem?
--
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
4:25 p.m.
New subject: [JBoss JIRA] Resolved: (JBAS-6590) JBoss AS 5 copies exploded ear to tmp directory
[
https://jira.jboss.org/jira/browse/JBAS-6590?page=com.atlassian.jira.plug...
]
Ales Justin resolved JBAS-6590.
-------------------------------
Resolution: Rejected
This is not a bug, it's a known feature.
JBoss AS 5 copies exploded ear to tmp directory
-----------------------------------------------
Key: JBAS-6590
URL: https://jira.jboss.org/jira/browse/JBAS-6590
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Deployers
Affects Versions: JBossAS-5.0.1.GA
Environment: JBoss AS 5.0.1.GA
JDK 1.5
Mac OS X 10.5.6
Reporter: Kenneth Christensen
Assignee: Ales Justin
Priority: Critical
Attachments: ear.jpg, jboss5-test.ear.zip, tmp-ear.jpg
I have an explode ear file (directory) - see attached file: ear.jpg
When I deploy the exploded ear file to JBoss AS 4.2.3 and later want to update a xhtml
file in the exploded ear by my ANT script everything works fine (i.e. I can refresh my
browser and see the changes without redeployment of the ear or war):
<!-- Target: deploy.xhtml.to.jboss -->
<target name="deploy.xhtml.to.jboss" description="Deploy xhtml
files to JBoss" if="deployed">
<copy
todir="${jboss.deploy.dir}/${jboss.context.path}/${war.file.name}/xhtml">
<fileset dir="${view.dir}/xhtml" includes="**/*"/>
</copy>
</target>
Because the exploded ear file is not copied to JBoss tmp dir.
But JBoss AS 5 always makes a copy of my exploded ear file and copies it to the tmp dir
where it's the current 'working copy/version' used by JBoss AS - see attached
file: tmp-ear.jpg
My ANT task will not work anymore because the 'working copy/version' used by
JBoss AS now is in the tmp dir and not in the deploy dir.
I really don't want to 'touch' web.xml (or other meta files) to trigger a
full redeployment when I need to make changes to my web files (xhtml, css, javascript,
images etc.).
Could we please have the 'old' behaviour from JBoss AS 4.2.X implemented into
JBoss AS 5 - or is there a workaround to above problem?
--
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
4:34 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-6590) JBoss AS 5 copies exploded ear to tmp directory
[
https://jira.jboss.org/jira/browse/JBAS-6590?page=com.atlassian.jira.plug...
]
Pete Muir commented on JBAS-6590:
---------------------------------
I spoke to Ales, he says that even with tmp copying that the original should still be
monitored, so this should work still.
JBoss AS 5 copies exploded ear to tmp directory
-----------------------------------------------
Key: JBAS-6590
URL: https://jira.jboss.org/jira/browse/JBAS-6590
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Deployers
Affects Versions: JBossAS-5.0.1.GA
Environment: JBoss AS 5.0.1.GA
JDK 1.5
Mac OS X 10.5.6
Reporter: Kenneth Christensen
Assignee: Ales Justin
Priority: Critical
Attachments: ear.jpg, jboss5-test.ear.zip, tmp-ear.jpg
I have an explode ear file (directory) - see attached file: ear.jpg
When I deploy the exploded ear file to JBoss AS 4.2.3 and later want to update a xhtml
file in the exploded ear by my ANT script everything works fine (i.e. I can refresh my
browser and see the changes without redeployment of the ear or war):
<!-- Target: deploy.xhtml.to.jboss -->
<target name="deploy.xhtml.to.jboss" description="Deploy xhtml
files to JBoss" if="deployed">
<copy
todir="${jboss.deploy.dir}/${jboss.context.path}/${war.file.name}/xhtml">
<fileset dir="${view.dir}/xhtml" includes="**/*"/>
</copy>
</target>
Because the exploded ear file is not copied to JBoss tmp dir.
But JBoss AS 5 always makes a copy of my exploded ear file and copies it to the tmp dir
where it's the current 'working copy/version' used by JBoss AS - see attached
file: tmp-ear.jpg
My ANT task will not work anymore because the 'working copy/version' used by
JBoss AS now is in the tmp dir and not in the deploy dir.
I really don't want to 'touch' web.xml (or other meta files) to trigger a
full redeployment when I need to make changes to my web files (xhtml, css, javascript,
images etc.).
Could we please have the 'old' behaviour from JBoss AS 4.2.X implemented into
JBoss AS 5 - or is there a workaround to above problem?
--
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
4:42 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-6590) JBoss AS 5 copies exploded ear to tmp directory
[
https://jira.jboss.org/jira/browse/JBAS-6590?page=com.atlassian.jira.plug...
]
Ales Justin commented on JBAS-6590:
-----------------------------------
> I really don't want to 'touch' web.xml (or other meta
files) to trigger a full redeployment when I need to make changes to my web files (xhtml,
css, javascript, images etc.).
Afaik JBossWeb is running on temp anyway,
so in order to get those changes you would have to modify the temp.
Or was this somehow hidden with 4.x WarDeployer?
In JBoss5 we still monitor the original, but currently we only monitor root and metadata
locations.
You can easily add to monitor for anything you like - see
MetaDataStructureModificationChecker in profile.xml.
JBoss AS 5 copies exploded ear to tmp directory
-----------------------------------------------
Key: JBAS-6590
URL: https://jira.jboss.org/jira/browse/JBAS-6590
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Deployers
Affects Versions: JBossAS-5.0.1.GA
Environment: JBoss AS 5.0.1.GA
JDK 1.5
Mac OS X 10.5.6
Reporter: Kenneth Christensen
Assignee: Ales Justin
Priority: Critical
Attachments: ear.jpg, jboss5-test.ear.zip, tmp-ear.jpg
I have an explode ear file (directory) - see attached file: ear.jpg
When I deploy the exploded ear file to JBoss AS 4.2.3 and later want to update a xhtml
file in the exploded ear by my ANT script everything works fine (i.e. I can refresh my
browser and see the changes without redeployment of the ear or war):
<!-- Target: deploy.xhtml.to.jboss -->
<target name="deploy.xhtml.to.jboss" description="Deploy xhtml
files to JBoss" if="deployed">
<copy
todir="${jboss.deploy.dir}/${jboss.context.path}/${war.file.name}/xhtml">
<fileset dir="${view.dir}/xhtml" includes="**/*"/>
</copy>
</target>
Because the exploded ear file is not copied to JBoss tmp dir.
But JBoss AS 5 always makes a copy of my exploded ear file and copies it to the tmp dir
where it's the current 'working copy/version' used by JBoss AS - see attached
file: tmp-ear.jpg
My ANT task will not work anymore because the 'working copy/version' used by
JBoss AS now is in the tmp dir and not in the deploy dir.
I really don't want to 'touch' web.xml (or other meta files) to trigger a
full redeployment when I need to make changes to my web files (xhtml, css, javascript,
images etc.).
Could we please have the 'old' behaviour from JBoss AS 4.2.X implemented into
JBoss AS 5 - or is there a workaround to above problem?
--
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
5:08 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-6590) JBoss AS 5 copies exploded ear to tmp directory
[
https://jira.jboss.org/jira/browse/JBAS-6590?page=com.atlassian.jira.plug...
]
Max Rydahl Andersen commented on JBAS-6590:
-------------------------------------------
How can this be rejected ? This is a major inconveniance..
JBoss AS 5 copies exploded ear to tmp directory
-----------------------------------------------
Key: JBAS-6590
URL: https://jira.jboss.org/jira/browse/JBAS-6590
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Deployers
Affects Versions: JBossAS-5.0.1.GA
Environment: JBoss AS 5.0.1.GA
JDK 1.5
Mac OS X 10.5.6
Reporter: Kenneth Christensen
Assignee: Ales Justin
Priority: Critical
Attachments: ear.jpg, jboss5-test.ear.zip, tmp-ear.jpg
I have an explode ear file (directory) - see attached file: ear.jpg
When I deploy the exploded ear file to JBoss AS 4.2.3 and later want to update a xhtml
file in the exploded ear by my ANT script everything works fine (i.e. I can refresh my
browser and see the changes without redeployment of the ear or war):
<!-- Target: deploy.xhtml.to.jboss -->
<target name="deploy.xhtml.to.jboss" description="Deploy xhtml
files to JBoss" if="deployed">
<copy
todir="${jboss.deploy.dir}/${jboss.context.path}/${war.file.name}/xhtml">
<fileset dir="${view.dir}/xhtml" includes="**/*"/>
</copy>
</target>
Because the exploded ear file is not copied to JBoss tmp dir.
But JBoss AS 5 always makes a copy of my exploded ear file and copies it to the tmp dir
where it's the current 'working copy/version' used by JBoss AS - see attached
file: tmp-ear.jpg
My ANT task will not work anymore because the 'working copy/version' used by
JBoss AS now is in the tmp dir and not in the deploy dir.
I really don't want to 'touch' web.xml (or other meta files) to trigger a
full redeployment when I need to make changes to my web files (xhtml, css, javascript,
images etc.).
Could we please have the 'old' behaviour from JBoss AS 4.2.X implemented into
JBoss AS 5 - or is there a workaround to above problem?
--
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
5:24 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-6590) JBoss AS 5 copies exploded ear to tmp directory
[
https://jira.jboss.org/jira/browse/JBAS-6590?page=com.atlassian.jira.plug...
]
Kenneth Christensen commented on JBAS-6590:
-------------------------------------------
> Afaik JBossWeb is running on temp anyway,
> so in order to get those changes you would have to modify the temp.
> Or was this somehow hidden with 4.x WarDeployer?
I never modified the temp in JBoss AS 4.2.3, because my exploded EAR never was created in
the temp.
> You can easily add to monitor for anything you like - see
MetaDataStructureModificationChecker in profile.xml.
Do you have any documentation on how to configure the
MetaDataStructureModificationChecker?
> You can remove this SeamModificationTypeMatcher in
seam-deployers-jboss-beans.xml in seam.deployer in deployers/.
No copy is created in tmp after I removed the SeamModificationTypeMatcher in
seam-deployers-jboss-beans.xml and now I can modify the original EAR
in the deploy dir and (sometimes) see my changes without redeployment - sometimes I need
to modify and deploy the same file more than once before
JBoss AS 5 pick up the changes. I guess something goes wrong, timestamp check fails or
something is cached in JBoss AS 5, I don't know?
But I think there is a problem with the current solution, because (default) it doesn't
work like JBoss AS 4.2.3 and documentation is missing about this importent issue.
JBoss AS 5 and JBoss Seam needs some documentation about this issue.
JBoss AS 5 copies exploded ear to tmp directory
-----------------------------------------------
Key: JBAS-6590
URL: https://jira.jboss.org/jira/browse/JBAS-6590
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Deployers
Affects Versions: JBossAS-5.0.1.GA
Environment: JBoss AS 5.0.1.GA
JDK 1.5
Mac OS X 10.5.6
Reporter: Kenneth Christensen
Assignee: Ales Justin
Priority: Critical
Attachments: ear.jpg, jboss5-test.ear.zip, tmp-ear.jpg
I have an explode ear file (directory) - see attached file: ear.jpg
When I deploy the exploded ear file to JBoss AS 4.2.3 and later want to update a xhtml
file in the exploded ear by my ANT script everything works fine (i.e. I can refresh my
browser and see the changes without redeployment of the ear or war):
<!-- Target: deploy.xhtml.to.jboss -->
<target name="deploy.xhtml.to.jboss" description="Deploy xhtml
files to JBoss" if="deployed">
<copy
todir="${jboss.deploy.dir}/${jboss.context.path}/${war.file.name}/xhtml">
<fileset dir="${view.dir}/xhtml" includes="**/*"/>
</copy>
</target>
Because the exploded ear file is not copied to JBoss tmp dir.
But JBoss AS 5 always makes a copy of my exploded ear file and copies it to the tmp dir
where it's the current 'working copy/version' used by JBoss AS - see attached
file: tmp-ear.jpg
My ANT task will not work anymore because the 'working copy/version' used by
JBoss AS now is in the tmp dir and not in the deploy dir.
I really don't want to 'touch' web.xml (or other meta files) to trigger a
full redeployment when I need to make changes to my web files (xhtml, css, javascript,
images etc.).
Could we please have the 'old' behaviour from JBoss AS 4.2.X implemented into
JBoss AS 5 - or is there a workaround to above problem?
--
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
5:26 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-6590) JBoss AS 5 copies exploded ear to tmp directory
[
https://jira.jboss.org/jira/browse/JBAS-6590?page=com.atlassian.jira.plug...
]
Kenneth Christensen commented on JBAS-6590:
-------------------------------------------
> How can this be rejected ? This is a major inconveniance..
+1
JBoss AS 5 copies exploded ear to tmp directory
-----------------------------------------------
Key: JBAS-6590
URL: https://jira.jboss.org/jira/browse/JBAS-6590
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Deployers
Affects Versions: JBossAS-5.0.1.GA
Environment: JBoss AS 5.0.1.GA
JDK 1.5
Mac OS X 10.5.6
Reporter: Kenneth Christensen
Assignee: Ales Justin
Priority: Critical
Attachments: ear.jpg, jboss5-test.ear.zip, tmp-ear.jpg
I have an explode ear file (directory) - see attached file: ear.jpg
When I deploy the exploded ear file to JBoss AS 4.2.3 and later want to update a xhtml
file in the exploded ear by my ANT script everything works fine (i.e. I can refresh my
browser and see the changes without redeployment of the ear or war):
<!-- Target: deploy.xhtml.to.jboss -->
<target name="deploy.xhtml.to.jboss" description="Deploy xhtml
files to JBoss" if="deployed">
<copy
todir="${jboss.deploy.dir}/${jboss.context.path}/${war.file.name}/xhtml">
<fileset dir="${view.dir}/xhtml" includes="**/*"/>
</copy>
</target>
Because the exploded ear file is not copied to JBoss tmp dir.
But JBoss AS 5 always makes a copy of my exploded ear file and copies it to the tmp dir
where it's the current 'working copy/version' used by JBoss AS - see attached
file: tmp-ear.jpg
My ANT task will not work anymore because the 'working copy/version' used by
JBoss AS now is in the tmp dir and not in the deploy dir.
I really don't want to 'touch' web.xml (or other meta files) to trigger a
full redeployment when I need to make changes to my web files (xhtml, css, javascript,
images etc.).
Could we please have the 'old' behaviour from JBoss AS 4.2.X implemented into
JBoss AS 5 - or is there a workaround to above problem?
--
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
5:44 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-6590) JBoss AS 5 copies exploded ear to tmp directory
[
https://jira.jboss.org/jira/browse/JBAS-6590?page=com.atlassian.jira.plug...
]
Ales Justin commented on JBAS-6590:
-----------------------------------
> How can this be rejected ? This is a major inconveniance..
This is an expected effect, hence definitely not a bug as listed.
If this is to be changed it needs a proper forum discussion first.
JBoss AS 5 copies exploded ear to tmp directory
-----------------------------------------------
Key: JBAS-6590
URL: https://jira.jboss.org/jira/browse/JBAS-6590
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Deployers
Affects Versions: JBossAS-5.0.1.GA
Environment: JBoss AS 5.0.1.GA
JDK 1.5
Mac OS X 10.5.6
Reporter: Kenneth Christensen
Assignee: Ales Justin
Priority: Critical
Attachments: ear.jpg, jboss5-test.ear.zip, tmp-ear.jpg
I have an explode ear file (directory) - see attached file: ear.jpg
When I deploy the exploded ear file to JBoss AS 4.2.3 and later want to update a xhtml
file in the exploded ear by my ANT script everything works fine (i.e. I can refresh my
browser and see the changes without redeployment of the ear or war):
<!-- Target: deploy.xhtml.to.jboss -->
<target name="deploy.xhtml.to.jboss" description="Deploy xhtml
files to JBoss" if="deployed">
<copy
todir="${jboss.deploy.dir}/${jboss.context.path}/${war.file.name}/xhtml">
<fileset dir="${view.dir}/xhtml" includes="**/*"/>
</copy>
</target>
Because the exploded ear file is not copied to JBoss tmp dir.
But JBoss AS 5 always makes a copy of my exploded ear file and copies it to the tmp dir
where it's the current 'working copy/version' used by JBoss AS - see attached
file: tmp-ear.jpg
My ANT task will not work anymore because the 'working copy/version' used by
JBoss AS now is in the tmp dir and not in the deploy dir.
I really don't want to 'touch' web.xml (or other meta files) to trigger a
full redeployment when I need to make changes to my web files (xhtml, css, javascript,
images etc.).
Could we please have the 'old' behaviour from JBoss AS 4.2.X implemented into
JBoss AS 5 - or is there a workaround to above problem?
--
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
2:30 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-6590) JBoss AS 5 copies exploded ear to tmp directory
[
https://jira.jboss.org/jira/browse/JBAS-6590?page=com.atlassian.jira.plug...
]
Dimitris Andreadis commented on JBAS-6590:
------------------------------------------
Do not under-estimate the user's needs & expectations.
JBoss AS 5 copies exploded ear to tmp directory
-----------------------------------------------
Key: JBAS-6590
URL: https://jira.jboss.org/jira/browse/JBAS-6590
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Deployers
Affects Versions: JBossAS-5.0.1.GA
Environment: JBoss AS 5.0.1.GA
JDK 1.5
Mac OS X 10.5.6
Reporter: Kenneth Christensen
Assignee: Ales Justin
Priority: Critical
Attachments: ear.jpg, jboss5-test.ear.zip, tmp-ear.jpg
I have an explode ear file (directory) - see attached file: ear.jpg
When I deploy the exploded ear file to JBoss AS 4.2.3 and later want to update a xhtml
file in the exploded ear by my ANT script everything works fine (i.e. I can refresh my
browser and see the changes without redeployment of the ear or war):
<!-- Target: deploy.xhtml.to.jboss -->
<target name="deploy.xhtml.to.jboss" description="Deploy xhtml
files to JBoss" if="deployed">
<copy
todir="${jboss.deploy.dir}/${jboss.context.path}/${war.file.name}/xhtml">
<fileset dir="${view.dir}/xhtml" includes="**/*"/>
</copy>
</target>
Because the exploded ear file is not copied to JBoss tmp dir.
But JBoss AS 5 always makes a copy of my exploded ear file and copies it to the tmp dir
where it's the current 'working copy/version' used by JBoss AS - see attached
file: tmp-ear.jpg
My ANT task will not work anymore because the 'working copy/version' used by
JBoss AS now is in the tmp dir and not in the deploy dir.
I really don't want to 'touch' web.xml (or other meta files) to trigger a
full redeployment when I need to make changes to my web files (xhtml, css, javascript,
images etc.).
Could we please have the 'old' behaviour from JBoss AS 4.2.X implemented into
JBoss AS 5 - or is there a workaround to above problem?
--
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
4:03 a.m.
New subject: [JBoss JIRA] Reopened: (JBAS-6590) JBoss AS 5 copies exploded ear to tmp directory
[
https://jira.jboss.org/jira/browse/JBAS-6590?page=com.atlassian.jira.plug...
]
Max Rydahl Andersen reopened JBAS-6590:
---------------------------------------
reopening to change title to its real problem
JBoss AS 5 copies exploded ear to tmp directory
-----------------------------------------------
Key: JBAS-6590
URL: https://jira.jboss.org/jira/browse/JBAS-6590
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Deployers
Affects Versions: JBossAS-5.0.1.GA
Environment: JBoss AS 5.0.1.GA
JDK 1.5
Mac OS X 10.5.6
Reporter: Kenneth Christensen
Assignee: Ales Justin
Priority: Critical
Attachments: ear.jpg, jboss5-test.ear.zip, tmp-ear.jpg
I have an explode ear file (directory) - see attached file: ear.jpg
When I deploy the exploded ear file to JBoss AS 4.2.3 and later want to update a xhtml
file in the exploded ear by my ANT script everything works fine (i.e. I can refresh my
browser and see the changes without redeployment of the ear or war):
<!-- Target: deploy.xhtml.to.jboss -->
<target name="deploy.xhtml.to.jboss" description="Deploy xhtml
files to JBoss" if="deployed">
<copy
todir="${jboss.deploy.dir}/${jboss.context.path}/${war.file.name}/xhtml">
<fileset dir="${view.dir}/xhtml" includes="**/*"/>
</copy>
</target>
Because the exploded ear file is not copied to JBoss tmp dir.
But JBoss AS 5 always makes a copy of my exploded ear file and copies it to the tmp dir
where it's the current 'working copy/version' used by JBoss AS - see attached
file: tmp-ear.jpg
My ANT task will not work anymore because the 'working copy/version' used by
JBoss AS now is in the tmp dir and not in the deploy dir.
I really don't want to 'touch' web.xml (or other meta files) to trigger a
full redeployment when I need to make changes to my web files (xhtml, css, javascript,
images etc.).
Could we please have the 'old' behaviour from JBoss AS 4.2.X implemented into
JBoss AS 5 - or is there a workaround to above problem?
--
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
4:03 a.m.
New subject: [JBoss JIRA] Updated: (JBAS-6590) AS5 is not reliably picking up changes in exploded EAR
[
https://jira.jboss.org/jira/browse/JBAS-6590?page=com.atlassian.jira.plug...
]
Max Rydahl Andersen updated JBAS-6590:
--------------------------------------
Summary: AS5 is not reliably picking up changes in exploded EAR (was: JBoss AS 5
copies exploded ear to tmp directory)
AS5 is not reliably picking up changes in exploded EAR
------------------------------------------------------
Key: JBAS-6590
URL: https://jira.jboss.org/jira/browse/JBAS-6590
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Deployers
Affects Versions: JBossAS-5.0.1.GA
Environment: JBoss AS 5.0.1.GA
JDK 1.5
Mac OS X 10.5.6
Reporter: Kenneth Christensen
Assignee: Ales Justin
Priority: Critical
Attachments: ear.jpg, jboss5-test.ear.zip, tmp-ear.jpg
I have an explode ear file (directory) - see attached file: ear.jpg
When I deploy the exploded ear file to JBoss AS 4.2.3 and later want to update a xhtml
file in the exploded ear by my ANT script everything works fine (i.e. I can refresh my
browser and see the changes without redeployment of the ear or war):
<!-- Target: deploy.xhtml.to.jboss -->
<target name="deploy.xhtml.to.jboss" description="Deploy xhtml
files to JBoss" if="deployed">
<copy
todir="${jboss.deploy.dir}/${jboss.context.path}/${war.file.name}/xhtml">
<fileset dir="${view.dir}/xhtml" includes="**/*"/>
</copy>
</target>
Because the exploded ear file is not copied to JBoss tmp dir.
But JBoss AS 5 always makes a copy of my exploded ear file and copies it to the tmp dir
where it's the current 'working copy/version' used by JBoss AS - see attached
file: tmp-ear.jpg
My ANT task will not work anymore because the 'working copy/version' used by
JBoss AS now is in the tmp dir and not in the deploy dir.
I really don't want to 'touch' web.xml (or other meta files) to trigger a
full redeployment when I need to make changes to my web files (xhtml, css, javascript,
images etc.).
Could we please have the 'old' behaviour from JBoss AS 4.2.X implemented into
JBoss AS 5 - or is there a workaround to above problem?
--
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
4:10 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-6590) AS5 is not reliably picking up changes in exploded EAR
[
https://jira.jboss.org/jira/browse/JBAS-6590?page=com.atlassian.jira.plug...
]
Max Rydahl Andersen commented on JBAS-6590:
-------------------------------------------
changed title to reflect the real problem and started thread at
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4216107#...
AS5 is not reliably picking up changes in exploded EAR
------------------------------------------------------
Key: JBAS-6590
URL: https://jira.jboss.org/jira/browse/JBAS-6590
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Deployers
Affects Versions: JBossAS-5.0.1.GA
Environment: JBoss AS 5.0.1.GA
JDK 1.5
Mac OS X 10.5.6
Reporter: Kenneth Christensen
Assignee: Ales Justin
Priority: Critical
Attachments: ear.jpg, jboss5-test.ear.zip, tmp-ear.jpg
I have an explode ear file (directory) - see attached file: ear.jpg
When I deploy the exploded ear file to JBoss AS 4.2.3 and later want to update a xhtml
file in the exploded ear by my ANT script everything works fine (i.e. I can refresh my
browser and see the changes without redeployment of the ear or war):
<!-- Target: deploy.xhtml.to.jboss -->
<target name="deploy.xhtml.to.jboss" description="Deploy xhtml
files to JBoss" if="deployed">
<copy
todir="${jboss.deploy.dir}/${jboss.context.path}/${war.file.name}/xhtml">
<fileset dir="${view.dir}/xhtml" includes="**/*"/>
</copy>
</target>
Because the exploded ear file is not copied to JBoss tmp dir.
But JBoss AS 5 always makes a copy of my exploded ear file and copies it to the tmp dir
where it's the current 'working copy/version' used by JBoss AS - see attached
file: tmp-ear.jpg
My ANT task will not work anymore because the 'working copy/version' used by
JBoss AS now is in the tmp dir and not in the deploy dir.
I really don't want to 'touch' web.xml (or other meta files) to trigger a
full redeployment when I need to make changes to my web files (xhtml, css, javascript,
images etc.).
Could we please have the 'old' behaviour from JBoss AS 4.2.X implemented into
JBoss AS 5 - or is there a workaround to above problem?
--
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
4:39 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-6590) AS5 is not reliably picking up changes in exploded EAR
[
https://jira.jboss.org/jira/browse/JBAS-6590?page=com.atlassian.jira.plug...
]
Kenneth Christensen commented on JBAS-6590:
-------------------------------------------
> No copy is created in tmp after I removed the
SeamModificationTypeMatcher in seam-deployers-jboss-beans.xml and now I can modify the
original EAR
> in the deploy dir and (sometimes) see my changes without redeployment - sometimes I
need to modify and deploy the same file more than once before
> JBoss AS 5 pick up the changes. I guess something goes wrong, timestamp check fails
or something is cached in JBoss AS 5, I don't know?
I tried to set Facelets 'facelets.REFRESH_PERIOD' to 0. Looks like it have
something to do with above problem. Everything works fine if I use the default value of
'facelets.REFRESH_PERIOD'.
The conclusion is that it seems to work if you remove the SeamModificationTypeMatcher. The
default installation of JBoss AS 5 have the SeamModificationTypeMatcher enabled by
default.
But what is the consequence for one's Seam app when you choose to remove the
SeamModificationTypeMatcher from JBoss AS 5?
The important thing here is that there have been some changes compared to JBoss AS 4.2 and
it must be documented.
AS5 is not reliably picking up changes in exploded EAR
------------------------------------------------------
Key: JBAS-6590
URL: https://jira.jboss.org/jira/browse/JBAS-6590
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Deployers
Affects Versions: JBossAS-5.0.1.GA
Environment: JBoss AS 5.0.1.GA
JDK 1.5
Mac OS X 10.5.6
Reporter: Kenneth Christensen
Assignee: Ales Justin
Priority: Critical
Attachments: ear.jpg, jboss5-test.ear.zip, tmp-ear.jpg
I have an explode ear file (directory) - see attached file: ear.jpg
When I deploy the exploded ear file to JBoss AS 4.2.3 and later want to update a xhtml
file in the exploded ear by my ANT script everything works fine (i.e. I can refresh my
browser and see the changes without redeployment of the ear or war):
<!-- Target: deploy.xhtml.to.jboss -->
<target name="deploy.xhtml.to.jboss" description="Deploy xhtml
files to JBoss" if="deployed">
<copy
todir="${jboss.deploy.dir}/${jboss.context.path}/${war.file.name}/xhtml">
<fileset dir="${view.dir}/xhtml" includes="**/*"/>
</copy>
</target>
Because the exploded ear file is not copied to JBoss tmp dir.
But JBoss AS 5 always makes a copy of my exploded ear file and copies it to the tmp dir
where it's the current 'working copy/version' used by JBoss AS - see attached
file: tmp-ear.jpg
My ANT task will not work anymore because the 'working copy/version' used by
JBoss AS now is in the tmp dir and not in the deploy dir.
I really don't want to 'touch' web.xml (or other meta files) to trigger a
full redeployment when I need to make changes to my web files (xhtml, css, javascript,
images etc.).
Could we please have the 'old' behaviour from JBoss AS 4.2.X implemented into
JBoss AS 5 - or is there a workaround to above problem?
--
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
7:19 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-6590) AS5 is not reliably picking up changes in exploded EAR
[
https://jira.jboss.org/jira/browse/JBAS-6590?page=com.atlassian.jira.plug...
]
Daniel munford commented on JBAS-6590:
--------------------------------------
I have confirmed that this is still happening in JBoss AS 5.1.0 GA release. Is there an
ETA on when the bug will be fixed?
AS5 is not reliably picking up changes in exploded EAR
------------------------------------------------------
Key: JBAS-6590
URL: https://jira.jboss.org/jira/browse/JBAS-6590
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Deployers
Affects Versions: JBossAS-5.0.1.GA
Environment: JBoss AS 5.0.1.GA
JDK 1.5
Mac OS X 10.5.6
Reporter: Kenneth Christensen
Assignee: Ales Justin
Priority: Critical
Attachments: ear.jpg, jboss5-test.ear.zip, tmp-ear.jpg
I have an explode ear file (directory) - see attached file: ear.jpg
When I deploy the exploded ear file to JBoss AS 4.2.3 and later want to update a xhtml
file in the exploded ear by my ANT script everything works fine (i.e. I can refresh my
browser and see the changes without redeployment of the ear or war):
<!-- Target: deploy.xhtml.to.jboss -->
<target name="deploy.xhtml.to.jboss" description="Deploy xhtml
files to JBoss" if="deployed">
<copy
todir="${jboss.deploy.dir}/${jboss.context.path}/${war.file.name}/xhtml">
<fileset dir="${view.dir}/xhtml" includes="**/*"/>
</copy>
</target>
Because the exploded ear file is not copied to JBoss tmp dir.
But JBoss AS 5 always makes a copy of my exploded ear file and copies it to the tmp dir
where it's the current 'working copy/version' used by JBoss AS - see attached
file: tmp-ear.jpg
My ANT task will not work anymore because the 'working copy/version' used by
JBoss AS now is in the tmp dir and not in the deploy dir.
I really don't want to 'touch' web.xml (or other meta files) to trigger a
full redeployment when I need to make changes to my web files (xhtml, css, javascript,
images etc.).
Could we please have the 'old' behaviour from JBoss AS 4.2.X implemented into
JBoss AS 5 - or is there a workaround to above problem?
--
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
6:21 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-6590) AS5 is not reliably picking up changes in exploded EAR
[
https://jira.jboss.org/jira/browse/JBAS-6590?page=com.atlassian.jira.plug...
]
Ales Justin commented on JBAS-6590:
-----------------------------------
> I have confirmed that this is still happening in JBoss AS 5.1.0
GA release. Is there an ETA on when the bug will be fixed?
Yes, this was already filed under JBDEPLOY-192.
It will be resolved with a new Deployers release.
AS5 is not reliably picking up changes in exploded EAR
------------------------------------------------------
Key: JBAS-6590
URL: https://jira.jboss.org/jira/browse/JBAS-6590
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Deployers
Affects Versions: JBossAS-5.0.1.GA
Environment: JBoss AS 5.0.1.GA
JDK 1.5
Mac OS X 10.5.6
Reporter: Kenneth Christensen
Assignee: Ales Justin
Priority: Critical
Attachments: ear.jpg, jboss5-test.ear.zip, tmp-ear.jpg
I have an explode ear file (directory) - see attached file: ear.jpg
When I deploy the exploded ear file to JBoss AS 4.2.3 and later want to update a xhtml
file in the exploded ear by my ANT script everything works fine (i.e. I can refresh my
browser and see the changes without redeployment of the ear or war):
<!-- Target: deploy.xhtml.to.jboss -->
<target name="deploy.xhtml.to.jboss" description="Deploy xhtml
files to JBoss" if="deployed">
<copy
todir="${jboss.deploy.dir}/${jboss.context.path}/${war.file.name}/xhtml">
<fileset dir="${view.dir}/xhtml" includes="**/*"/>
</copy>
</target>
Because the exploded ear file is not copied to JBoss tmp dir.
But JBoss AS 5 always makes a copy of my exploded ear file and copies it to the tmp dir
where it's the current 'working copy/version' used by JBoss AS - see attached
file: tmp-ear.jpg
My ANT task will not work anymore because the 'working copy/version' used by
JBoss AS now is in the tmp dir and not in the deploy dir.
I really don't want to 'touch' web.xml (or other meta files) to trigger a
full redeployment when I need to make changes to my web files (xhtml, css, javascript,
images etc.).
Could we please have the 'old' behaviour from JBoss AS 4.2.X implemented into
JBoss AS 5 - or is there a workaround to above problem?
--
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
12:38 p.m.
New subject: [JBoss JIRA] Resolved: (JBAS-6590) AS5 is not reliably picking up changes in exploded EAR
[
https://jira.jboss.org/jira/browse/JBAS-6590?page=com.atlassian.jira.plug...
]
Ales Justin resolved JBAS-6590.
-------------------------------
Resolution: Done
New Deployers 2.2.x should handle this properly - only checking known files.
AS5 is not reliably picking up changes in exploded EAR
------------------------------------------------------
Key: JBAS-6590
URL: https://jira.jboss.org/jira/browse/JBAS-6590
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Deployers
Affects Versions: JBossAS-5.0.1.GA
Environment: JBoss AS 5.0.1.GA
JDK 1.5
Mac OS X 10.5.6
Reporter: Kenneth Christensen
Assignee: Ales Justin
Priority: Critical
Attachments: ear.jpg, jboss5-test.ear.zip, tmp-ear.jpg
I have an explode ear file (directory) - see attached file: ear.jpg
When I deploy the exploded ear file to JBoss AS 4.2.3 and later want to update a xhtml
file in the exploded ear by my ANT script everything works fine (i.e. I can refresh my
browser and see the changes without redeployment of the ear or war):
<!-- Target: deploy.xhtml.to.jboss -->
<target name="deploy.xhtml.to.jboss" description="Deploy xhtml
files to JBoss" if="deployed">
<copy
todir="${jboss.deploy.dir}/${jboss.context.path}/${war.file.name}/xhtml">
<fileset dir="${view.dir}/xhtml" includes="**/*"/>
</copy>
</target>
Because the exploded ear file is not copied to JBoss tmp dir.
But JBoss AS 5 always makes a copy of my exploded ear file and copies it to the tmp dir
where it's the current 'working copy/version' used by JBoss AS - see attached
file: tmp-ear.jpg
My ANT task will not work anymore because the 'working copy/version' used by
JBoss AS now is in the tmp dir and not in the deploy dir.
I really don't want to 'touch' web.xml (or other meta files) to trigger a
full redeployment when I need to make changes to my web files (xhtml, css, javascript,
images etc.).
Could we please have the 'old' behaviour from JBoss AS 4.2.X implemented into
JBoss AS 5 - or is there a workaround to above problem?
--
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
12:40 p.m.
New subject: [JBoss JIRA] Updated: (JBAS-6590) AS5 is not reliably picking up changes in exploded EAR
[
https://jira.jboss.org/jira/browse/JBAS-6590?page=com.atlassian.jira.plug...
]
Ales Justin updated JBAS-6590:
------------------------------
Fix Version/s: JBossAS-6.0.0.M2
AS5 is not reliably picking up changes in exploded EAR
------------------------------------------------------
Key: JBAS-6590
URL: https://jira.jboss.org/jira/browse/JBAS-6590
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Deployers
Affects Versions: JBossAS-5.0.1.GA
Environment: JBoss AS 5.0.1.GA
JDK 1.5
Mac OS X 10.5.6
Reporter: Kenneth Christensen
Assignee: Ales Justin
Priority: Critical
Fix For: JBossAS-6.0.0.M2
Attachments: ear.jpg, jboss5-test.ear.zip, tmp-ear.jpg
I have an explode ear file (directory) - see attached file: ear.jpg
When I deploy the exploded ear file to JBoss AS 4.2.3 and later want to update a xhtml
file in the exploded ear by my ANT script everything works fine (i.e. I can refresh my
browser and see the changes without redeployment of the ear or war):
<!-- Target: deploy.xhtml.to.jboss -->
<target name="deploy.xhtml.to.jboss" description="Deploy xhtml
files to JBoss" if="deployed">
<copy
todir="${jboss.deploy.dir}/${jboss.context.path}/${war.file.name}/xhtml">
<fileset dir="${view.dir}/xhtml" includes="**/*"/>
</copy>
</target>
Because the exploded ear file is not copied to JBoss tmp dir.
But JBoss AS 5 always makes a copy of my exploded ear file and copies it to the tmp dir
where it's the current 'working copy/version' used by JBoss AS - see attached
file: tmp-ear.jpg
My ANT task will not work anymore because the 'working copy/version' used by
JBoss AS now is in the tmp dir and not in the deploy dir.
I really don't want to 'touch' web.xml (or other meta files) to trigger a
full redeployment when I need to make changes to my web files (xhtml, css, javascript,
images etc.).
Could we please have the 'old' behaviour from JBoss AS 4.2.X implemented into
JBoss AS 5 - or is there a workaround to above problem?
--
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
6018
days inactive
6355
days old
22 comments
6 participants
participants (6)
-
Ales Justin (JIRA) -
Daniel munford (JIRA)
-
Dimitris Andreadis (JIRA)
-
Kenneth Christensen (JIRA)
-
Max Rydahl Andersen (JIRA)
-
Pete Muir (JIRA)