[JBoss JIRA] (JBIDE-19395) Default template code for Servlet
by Daniel Azarov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19395?page=com.atlassian.jira.plugi... ]
Daniel Azarov edited comment on JBIDE-19395 at 3/17/15 4:06 PM:
----------------------------------------------------------------
[~ArunGupta], how about to use
{code}
response.getWriter().append("Served at: ").append(request.getContextPath());
{code}
instead of:
{code}
response.getOutputStream().print("Served at: " + request.getContextPath());
{code}
Roberto Sanchez Herrera asked in bugzilla:
{quote}
3. Why did you decide to use response.getOutputStream(), which according to the javadoc: "Returns a ServletOutputStream suitable for writing binary data in the response", instead of response.getWriter(), which seems more appropriate (from javadoc: Returns a PrintWriter object that can send character text to the client.)
{quote}
was (Author: dazarov):
[~ArunGupta], how about to use
{code}
response.getWriter().append("Served at: ").append(request.getContextPath());
{code}
instead of:
{code}
response.getOutputStream().print("Served at: " + request.getContextPath());
{code}
Roberto Sanchez Herrera asked in bugzilla:
>3. Why did you decide to use response.getOutputStream(), which according to the javadoc: "Returns a >ServletOutputStream suitable for writing binary data in the response", instead of response.getWriter(), which seems more >appropriate (from javadoc: Returns a PrintWriter object that can send character text to the client.)
> Default template code for Servlet
> ---------------------------------
>
> Key: JBIDE-19395
> URL: https://issues.jboss.org/browse/JBIDE-19395
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: upstream
> Affects Versions: 4.3.0.Alpha1
> Reporter: Arun Gupta
> Assignee: Daniel Azarov
> Fix For: 4.3.x
>
>
> It would be nice to have a default template code generated for Servlet. This will make the generated Servlet a little bit more useful, and much easier to showcase in demos.
> For example, here is one template that could be generated in doGet():
> response.getOutputStream().print("Served at: " + request.getContextPath());
> And doGet() called from doPost().
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month
[JBoss JIRA] (JBIDE-19395) Default template code for Servlet
by Arun Gupta (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19395?page=com.atlassian.jira.plugi... ]
Arun Gupta commented on JBIDE-19395:
------------------------------------
Sounds good.
> Default template code for Servlet
> ---------------------------------
>
> Key: JBIDE-19395
> URL: https://issues.jboss.org/browse/JBIDE-19395
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: upstream
> Affects Versions: 4.3.0.Alpha1
> Reporter: Arun Gupta
> Assignee: Daniel Azarov
> Fix For: 4.3.x
>
>
> It would be nice to have a default template code generated for Servlet. This will make the generated Servlet a little bit more useful, and much easier to showcase in demos.
> For example, here is one template that could be generated in doGet():
> response.getOutputStream().print("Served at: " + request.getContextPath());
> And doGet() called from doPost().
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month
[JBoss JIRA] (JBIDE-19395) Default template code for Servlet
by Daniel Azarov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19395?page=com.atlassian.jira.plugi... ]
Daniel Azarov commented on JBIDE-19395:
---------------------------------------
[~ArunGupta], how about to use
{code}
response.getWriter().append("Served at: ").append(request.getContextPath());
{code}
instead of:
{code}
response.getOutputStream().print("Served at: " + request.getContextPath());
{code}
Roberto Sanchez Herrera asked in bugzilla:
>3. Why did you decide to use response.getOutputStream(), which according to the javadoc: "Returns a >ServletOutputStream suitable for writing binary data in the response", instead of response.getWriter(), which seems more >appropriate (from javadoc: Returns a PrintWriter object that can send character text to the client.)
> Default template code for Servlet
> ---------------------------------
>
> Key: JBIDE-19395
> URL: https://issues.jboss.org/browse/JBIDE-19395
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: upstream
> Affects Versions: 4.3.0.Alpha1
> Reporter: Arun Gupta
> Assignee: Daniel Azarov
> Fix For: 4.3.x
>
>
> It would be nice to have a default template code generated for Servlet. This will make the generated Servlet a little bit more useful, and much easier to showcase in demos.
> For example, here is one template that could be generated in doGet():
> response.getOutputStream().print("Served at: " + request.getContextPath());
> And doGet() called from doPost().
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month
[JBoss JIRA] (JBTIS-396) JBoss Central doesn't recognise that a category item is already installed
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBTIS-396?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBTIS-396:
----------------------------------
If you want things changed in Mylyn itself, open a bug at Eclipse. It's not too late to get stuff fixed/improved in the version of Mylyn in Luna.
Or, if there's something we can do to improve/extend Mylyn, ping [~snjeza] or [~mickael_istria] and maybe they can take a look.
> JBoss Central doesn't recognise that a category item is already installed
> -------------------------------------------------------------------------
>
> Key: JBTIS-396
> URL: https://issues.jboss.org/browse/JBTIS-396
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution
> Reporter: Michelle Murray
> Assignee: Paul Leacu
> Attachments: dv1.png, dv2.png
>
>
> I have JBDS 8.0.2 installed.
> In JBoss Central Software/Update tab, I enabled Early Access. I then selected the check box for 'JBoss Data Virtualization Developer' and clicked installed. I chose to only install ModeShape Client and followed the install through including restarting JBDS.
> In JBoss Central Software/Update tab, 'JBoss Data Virtualization Developer' was still shown as uninstalled - as expected from JBTIS-363. I selected the check box for 'JBoss Data Virtualization Developer' and clicked installed. ModeShape Client is listed and check box autoselected along with all of the Teiid items as available to install. BUT I just installed it!?
> 1) I chose to only install the ModeShape Client again but then get an error message "Cannot complete the request. See the error log for details."
> 2) So I chose to install all, including ModeShape Client, and the install proceeds to the next window without the error message but is listing that it will install ModeShape Client again.
> As a user, this looks like a bug to me.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month
[JBoss JIRA] (JBTIS-396) JBoss Central doesn't recognise that a category item is already installed
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-396?page=com.atlassian.jira.plugin.... ]
Paul Leacu closed JBTIS-396.
----------------------------
Resolution: Won't Fix
I appreciate the feedback - however this would appear to be a Mylyn enhancement request when all is considered. There's really nothing that can be done on our end. Thanks for the input.
> JBoss Central doesn't recognise that a category item is already installed
> -------------------------------------------------------------------------
>
> Key: JBTIS-396
> URL: https://issues.jboss.org/browse/JBTIS-396
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution
> Reporter: Michelle Murray
> Assignee: Paul Leacu
> Attachments: dv1.png, dv2.png
>
>
> I have JBDS 8.0.2 installed.
> In JBoss Central Software/Update tab, I enabled Early Access. I then selected the check box for 'JBoss Data Virtualization Developer' and clicked installed. I chose to only install ModeShape Client and followed the install through including restarting JBDS.
> In JBoss Central Software/Update tab, 'JBoss Data Virtualization Developer' was still shown as uninstalled - as expected from JBTIS-363. I selected the check box for 'JBoss Data Virtualization Developer' and clicked installed. ModeShape Client is listed and check box autoselected along with all of the Teiid items as available to install. BUT I just installed it!?
> 1) I chose to only install the ModeShape Client again but then get an error message "Cannot complete the request. See the error log for details."
> 2) So I chose to install all, including ModeShape Client, and the install proceeds to the next window without the error message but is listing that it will install ModeShape Client again.
> As a user, this looks like a bug to me.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month