Menu
▾
▴
jboss-dev-forums
|
From: <tho...@jb...> - 2006-07-10 08:04:05
|
I have a little knowledge with WTP and how you relate to it. I had a quick look at WTP since i never played with it before and had to realize by myself (even though i have been told) that you cannot deploy an exploded EAR with exploded WARs inside. That is just too bad :( A 'basic' Seam application using EJB3 will have 3 projects most of the time. An EAR, a JAR, a WAR but one could want more than a single JAR or single WAR. I will have a talk with Max and see what we can do. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956511#3956511 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956511 |
|
From: <max...@jb...> - 2006-07-10 08:48:39
|
Let's have lunch today about it ;) The deployment issue is something that Stryker should be able to shed a light on. I was hoping he could make that happen somehow ;) Rob? Additional jar's I can understand, but when is additional WAR's interesting/relevant ? I'll also have to give it some thought on how the app generation templates and UI can be adjusted to generated into this more scalable structure. e.g. right now it assumes one root where as here we will have three roots. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956520#3956520 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956520 |
|
From: <max...@jb...> - 2006-07-10 12:47:52
|
Optimally it would be cool to get a deployment to point directly to the web src tree in the project, but i don't think that is easily doable ? Andy talked about being able to specify what URL's a jboss installation should look at? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956564#3956564 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956564 |
|
From: <max...@jb...> - 2006-07-10 12:47:55
|
..hopefully something that will work toegether with marshall's packaging "thingy" and then optimally can "copy-on-save" so edits will be instant for e.g. JSF pages. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956561#3956561 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956561 |
|
From: <rob...@jb...> - 2006-07-10 12:48:44
|
Right now default behavior for running the WTP projects on a server is to package them up. Having the option to deploy exploded is a feature I'll try to work in. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956560#3956560 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956560 |
|
From: <tho...@jb...> - 2006-07-10 13:12:11
|
You can easily add a new directory to scan for deployment on JBoss but the packaging is not correct on WTP (You can't have a War inside a Ear). A copy-on-save would do the magic. Having exploded archived is a *Very important* feature it lets you fix your JSF pages without having to redeploy. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956579#3956579 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956579 |
|
From: <max...@jb...> - 2006-07-10 13:14:49
|
ok - but how do you (easily) add a new directory for scan for deployment ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956581#3956581 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956581 |
|
From: <tho...@jb...> - 2006-07-10 13:38:14
|
It's in jboss-service.xml it's the URLDeploymentScanner mbean
| <!-- URLs are comma separated and resolve relative to the server home URL
| unless the given path is absolute. If the URL ends in "/" it is
| considered a collection and scanned, otherwise it is simply deployed;
| this follows RFC2518 convention and allows discrimination between
| collections and directories that are simply unpacked archives.
|
| URLs may be local (file:) or remote (http:). Scanning is supported
| for remote URLs but unpacked deployment units are not.
|
| Example URLs:
| deploy/
| scans ${jboss.server.url}/deploy/, which is local or remote
| depending on the URL used to boot the server
| ${jboss.server.home}/deploy/
| scans ${jboss.server.home}/deploy, which is always local
| file:/var/opt/myapp.ear
| deploy myapp.ear from a local location
| file:/var/opt/apps/
| scans the specified directory
| http://www.test.com/netboot/myapp.ear
| deploys myapp.ear from a remote location
| http://www.test.com/netboot/apps/
| scans the specified WebDAV location
| -->
| <attribute name="URLs">
| deploy/
| </attribute>
|
And you can do it at runtime too, since this is an mbean.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956584#3956584
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956584
|
|
From: <tho...@jb...> - 2006-07-10 13:49:57
|
I now have the booking app as WTP projects with configuration for JBoss AS. (In our current examples we do Ant filtering to configure the examples for one app server or the other (or Tomcat) I will document the elements that need customization and how names are related (for example you build the JNDI name from the EAR Name followed by some stuff) If you need my Eclipse Workspace for this example, let me know we will try to find a way to send the 13MB of compressed files... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956590#3956590 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956590 |
|
From: <max...@jb...> - 2006-07-10 14:04:00
|
13 megs? insane ;) just zip it and attach it to the jira case. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956594#3956594 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956594 |
|
From: <tho...@jb...> - 2006-07-10 15:00:22
|
The limit is 10Mb ;) You can FTP it from my machine Max. For others, if you are interested let me know and we'll find a way View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956610#3956610 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956610 |
|
From: <mcu...@jb...> - 2006-07-10 19:58:54
|
Hey guys -- FYI.. My new packaging tools includes API for auto-generating both exploded and standard JAR/WAR/whatever. The only thing extra we need is for the AS Adapter to support exploded deployments (which should be really easy). Max.. adding your project as a deployment URL to JBoss isn't an option unless we enforce the standard J2EE structure on the users.. (which is something we're trying to get away from? ;) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956736#3956736 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956736 |
|
From: <max...@jb...> - 2006-07-10 20:22:32
|
well, people like to change their JSF's today while they are in some structure that J2EE can deploy...can't you just tell it to monitor some rootdirectory ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956746#3956746 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956746 |
|
From: <mcu...@jb...> - 2006-07-10 20:27:52
|
Again, it's a JBoss configuration issue.. so yes maybe the AS adapter could have a list of deployment directories.. Rob care to chime in? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956750#3956750 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956750 |
|
From: <rob...@jb...> - 2006-07-10 20:50:56
|
If Marshall's packaging can already package to an exploded directory, the user can manually change the service.xml to allow it to deploy. But, since we're IDE, it really wouldn't difficult in the least for me to grab the exploded directory it's being sent to and throw it in the service.xml for them. But then I'd have very little to do except on initial deployment (where i'd have to add it as a module to the server and change the .xml) and on removal from the server. I'd have almost no role in publishing. I suppose I could listen in for the events just so I can post them in my event log but that'd be it really. Eventually I intend to have all sorts of descriptor helpers in my AS bridge, from adding exploded directories to listen to, to other things as well. Pretty much anything descriptor. So this would fit in pretty easily with the general idea. The use-case i see for this is once they set up their packaging with marshall, they right-click on the project, run as -> run on server. I then take the project, and if there's an exploded-style directory in marshall's model for this project, as my deploy action I add that directory to the service.xml. Sound peachy? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956770#3956770 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956770 |
|
From: <max...@jb...> - 2006-07-10 21:08:24
|
users doing less = Good! you code doing less = Even better! The simpler it is, more likely it will work. What i hope to see is: Zero to almost no user setup. One easy action to deploy a seam app and from that point if the user changes a file in the deployed stuff we just do copy of changed files making it scale to almost infinitly big deployments. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956778#3956778 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956778 |
|
From: <mcu...@jb...> - 2006-07-10 21:25:12
|
Rob I think what your code should do should be relatively simple: 1) Allow a user to deploy exploded packages 2) Give an option on _any_ deployment (exploded or not) to automatically copy/deploy to JBoss on any changes. You can do this easily by just having a resourcechangelistener or using my packagesbuildlistener. Deploying an entire project to JBoss would be hard to define.. i.e.. what if there are 4 different JARs for that project? do we deploy all of them? only the EARs? etc.. Let's only let a project be deployed to JBoss if it is a WTP project. As Max said, KISS. =) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956789#3956789 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956789 |
Thanks for helping keep SourceForge clean.
X