Re: [jboss-dev-forums] [JBoss ESB Development] - Naming for webservice endpoints
by Tom Fennelly
Tom Fennelly [http://community.jboss.org/people/tfennelly] replied to the discussion
"Naming for webservice endpoints"
To view the discussion, visit: http://community.jboss.org/message/559712#559712
--------------------------------------------------------------
For SOAPProcessor, how about also supporting the context defined on the "jbossws-endpoint" property (eliminating the need for the "jbossws-context" property) ala:
<property name="jbossws-endpoint" value="myapp:fooservice"/>
Of course, making sure it's backward compatible etc.
For "pure" consistency between SOAPProcessor and SOAPProxy, couldn't they both be coded to also support exactly the same format for internal endpoints i.e.
<property name="jbossws-endpoint" value="foo:HelloWorldWS"/>
and
<property name="wsdl" value="foo:HelloWorldWS"/>
So in the later... the "internal" scheme is implied by the absence of a scheme.... hmmm actually "foo" would be the scheme. Actually... something that looks odd with the SOAPProxy. The wsdl URI is kinda corrupt when defining it ala "internal://foo:HelloWorldWS". Looks like a URI, but "HelloWorldWS" is where a port number would be expected. Wouldn't that be an invalid URI syntax? Maybe ye don't care about that, but I'd have though it would be good to maintain a valid URI (parseable etc).
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/559712#559712]
Start a new discussion in JBoss ESB Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years, 3 months
Re: [jboss-dev-forums] [JBoss AS7 Development] - Thoughts on hot deployment
by Dimitris Andreadis
Dimitris Andreadis [http://community.jboss.org/people/dimitris%40jboss.org] replied to the discussion
"Thoughts on hot deployment"
To view the discussion, visit: http://community.jboss.org/message/559709#559709
--------------------------------------------------------------
What is the rationale for the .deployed marker? It's really counter-intuitive. Just make a copy to avoid locking/classloading issues and leave the original in place.
Also, for exploded deployments have a different META-INF/jboss-deploy marker to trigger the deployment? Counter-intuitive as well. The whole idea with the ./deploy dir (or whatever is called) is you look there and you know what gets deployed, you don't need to traverse directories to find out. Or unzip something and it gets deployed, no need for extra files.
IMO the AS4 model of hot-deployment (no VFS) was the most practival and successful. People knew that to avoid the "early deployment" problem for large or nested deployments they just have to do an atomic filesystem mv. Through stuff in and it just gets deployed, no markers or any other type of magic. I don't see why we need to re-discover the wheel.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/559709#559709]
Start a new discussion in JBoss AS7 Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years, 3 months
Re: [jboss-dev-forums] [JBoss AS7 Development] - Thoughts on hot deployment
by jaikiran pai
jaikiran pai [http://community.jboss.org/people/jaikiran] replied to the discussion
"Thoughts on hot deployment"
To view the discussion, visit: http://community.jboss.org/message/559677#559677
--------------------------------------------------------------
> jaikiran pai wrote:
>
>
> > Brian Stansberry wrote:
> >
> > *For zipped archives*:
> > Scanner will detect an archive in the hot-deploy dir, e.g. hot-deploy/foo.war. Scanner will use the same https://community.jboss.org/thread/155937?tstart=0 deployment API that an external client would use to register the content with the server and deploy it. Once the content is registered the server will maintain it's own copy in an internal directory (e.g. server/data/deployments). Scanner will replace the hot-deploy/foo.war file with a simple marker file hot-deploy/foo.war.deployed.
> Would it be a "rename" or would the foo.war.deployed be a completely different file? From what I understand, I believe it would be a completely different file without any .war semantics, but just wanted to be sure. Furthermore, where would be original foo.war be moved to? Are users expected to know where it's moved to? If not, then they probably will have to maintain a copy of their original deployment somewhere (I know most of them already do that, but again I just wanted to be clear about the expectations).
>
>
Just to be a little more clear about that question - I know that the server will internally maintain it's own copy in an internal directory (server/data/deployments). But the part which I wasn't sure was - would that internal copy in server/data/deployments be an extracted version (like we do in AS6 in server/tmp folder) or the original version? I assumed it would be an extracted and hence that question on locating the "original" deployment. (Note that in our current versions of AS even though we maintain an internal copy of the deployment in tmp folder, we don't change anything directly in the original copy, which means that the user still has access to the original unchanged deployment).
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/559677#559677]
Start a new discussion in JBoss AS7 Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years, 3 months
Re: [jboss-dev-forums] [JBoss AS7 Development] - Thoughts on hot deployment
by jaikiran pai
jaikiran pai [http://community.jboss.org/people/jaikiran] replied to the discussion
"Thoughts on hot deployment"
To view the discussion, visit: http://community.jboss.org/message/559676#559676
--------------------------------------------------------------
Nice! :)
Here's some questions I have:
> Brian Stansberry wrote:
>
> *For zipped archives*:
> Scanner will detect an archive in the hot-deploy dir, e.g. hot-deploy/foo.war. Scanner will use the same https://community.jboss.org/thread/155937?tstart=0 deployment API that an external client would use to register the content with the server and deploy it. Once the content is registered the server will maintain it's own copy in an internal directory (e.g. server/data/deployments). Scanner will replace the hot-deploy/foo.war file with a simple marker file hot-deploy/foo.war.deployed.
Would it be a "rename" or would the foo.war.deployed be a completely different file? From what I understand, I believe it would be a completely different file without any .war semantics, but just wanted to be sure. Furthermore, where would be original foo.war be moved to? Are users expected to know where it's moved to? If not, then they probably will have to maintain a copy of their original deployment somewhere (I know most of them already do that, but again I just wanted to be clear about the expectations).
> Brian Stansberry wrote:
>
> User can trigger a replacement of foo.war (undeploy old, deploy new) by copying a new foo.war into hot-deploy/
Later in your post, I see that special care has to taken to avoid spurious hot deploys (i.e. picking up a deployment even before it is completely copied to hot-deploy folder) for exploded deployments. How do we handle such cases for these zipped archives? i.e. What happens when a zipped foo.war is still being copied to hot-deploy and the scanner picks it up for deployment?
> Brian Stansberry wrote:
>
> *For exploded archives*:
>
> User can trigger an undeploy of foo.war by deleting hot-deploy/foo.war/META-INF/jboss-deploy
>
> +Undeploy by deleting the entire hot-deploy/foo.war/ directory is not supported!+ The user should delete hot-deploy/foo.war/META-INF/jboss-deploy to trigger undeploy, after which they can delete the entire directory if they so choose.
Any specific reason why deleting the hot-deploy/foo.war directory shouldn't undeploy the application? If foo.war is deleted it effectively means foo.war/META-INF/jboss.deploy too is deleted, so I'm not sure why we can't support it. I guess there's something I'm missing :)
In addition to the above, I can think of a few more cases:
*"Leaf" deployments:*
What do we plan to do with "leaf" file hot-deployments? For example, consider a hot-deploy/mail-service.xml (I know for AS-7, *-service.xml may not be relevant, but let's consider it just as an example). How is hot deployment handled for such files? Or for that matter, how is deployment handled for such "leaf" files in the hot-deploy folder? Would it too create a mail-service.xml.deployed marker? Do we plan to (somehow) avoid spurious hot deploys for such files?
*Nested deployments:*
In case of nested deployments, I believe only the top level META-INF/jboss.deploy marker file plays a role. Any marker files in sub-deployments of the top-level deployment, will +not+ have any effect on the hot-deploy semantics. Am I right?
Finally, are the *.deployed and jboss.deploy marker file semantics only specific to a hot deployment enabled folder (like hot-deploy)? Considering a simple foo.war zipped archive in a normal deploy folder (without hot deployment), would it too be replaced with a marker foo.war.deployed file? And would jboss.deploy play a role in exploded deployment in a normal deploy folder?
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/559676#559676]
Start a new discussion in JBoss AS7 Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years, 3 months