<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
I think that the term "Microservices" is related to deployment of
apps instead of the artifacts you produce to achieve that. <br>
<br>
That said, I think it would make sense to have a Microservice
category if you intend to create a project that should run by itself
(eg. A Maven project with Wildfly-swarm configured in its pom.xml
for example).<br>
<br>
Something like New Project -> New JavaEE Microservice project<br>
<br>
<div class="moz-cite-prefix">On 05/07/2015 02:44 PM, Mickael Istria
wrote:<br>
</div>
<blockquote cite="mid:554BA46E.70109@redhat.com" type="cite">
<meta http-equiv="content-type" content="text/html;
charset=windows-1252">
Hi all,<br>
<br>
As I'm following some discussions about microservices (which are
more or less regular Jax-RS services in many cases), I'm wondering
whether JBoss Tools could embrace the word "Microservices" in some
ways, for example in wizards or archetypes.<br>
Would a "Microservices" category in the Import wizard, that would
repeat most Jax-RS wizards be a good idea ?<br>
Or just prefixing all occurence of the "service" word with
"(micro)" ?<br>
<br>
WDYT?<br>
<div class="moz-signature">-- <br>
Mickael Istria<br>
Eclipse developer at <a moz-do-not-send="true"
href="http://www.jboss.org/tools">JBoss, by Red Hat</a><br>
<a moz-do-not-send="true"
href="http://mickaelistria.wordpress.com">My blog</a> - <a
moz-do-not-send="true" href="http://twitter.com/mickaelistria">My
Tweets</a></div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
jbosstools-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:jbosstools-dev@lists.jboss.org">jbosstools-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/jbosstools-dev">https://lists.jboss.org/mailman/listinfo/jbosstools-dev</a></pre>
</blockquote>
<br>
</body>
</html>