[jira] [Updated] (OFBIZ-10510) Employee names appear as "Null" in company tree.
[ https://issues.apache.org/jira/browse/OFBIZ-10510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shantanu updated OFBIZ-10510: - Attachment: (was: Untitled.jpg) > Employee names appear as "Null" in company tree. > > > Key: OFBIZ-10510 > URL: https://issues.apache.org/jira/browse/OFBIZ-10510 > Project: OFBiz > Issue Type: Bug > Components: humanres >Affects Versions: 16.11.04 >Reporter: Shantanu >Priority: Blocker > Labels: beginner, newbie, starter > Attachments: Company Tree.jpg, Employee Profile.jpg > > > I've created a sample Internal Organisation called "New Department". > Made a position withing in called "New Postion". > Then created an Employee names "Adi Singh" and added him the "New Postion" > and Employed in "New Department" > But in the company tree the name of employee appears as Null. > Please help. > I've attached two images showing the issues. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10510) Employee names appear as "Null" in company tree.
[ https://issues.apache.org/jira/browse/OFBIZ-10510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shantanu updated OFBIZ-10510: - Description: I've created a sample Internal Organisation called "New Department". Made a position within it called "New Postion". Then created an Employee named "Adi Singh" and added him the "New Postion" and Employed in "New Department" But in the company tree the name of employee appears as Null. Please help. I've attached two images showing the issues. was: I've created a sample Internal Organisation called "New Department". Made a position withing in called "New Postion". Then created an Employee names "Adi Singh" and added him the "New Postion" and Employed in "New Department" But in the company tree the name of employee appears as Null. Please help. I've attached two images showing the issues. > Employee names appear as "Null" in company tree. > > > Key: OFBIZ-10510 > URL: https://issues.apache.org/jira/browse/OFBIZ-10510 > Project: OFBiz > Issue Type: Bug > Components: humanres >Affects Versions: 16.11.04 >Reporter: Shantanu >Priority: Blocker > Labels: beginner, newbie, starter > Attachments: Company Tree.jpg, Employee Profile.jpg > > > I've created a sample Internal Organisation called "New Department". > Made a position within it called "New Postion". > Then created an Employee named "Adi Singh" and added him the "New Postion" > and Employed in "New Department" > But in the company tree the name of employee appears as Null. > Please help. > I've attached two images showing the issues. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10510) Employee names appear as "Null" in company tree.
[ https://issues.apache.org/jira/browse/OFBIZ-10510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shantanu updated OFBIZ-10510: - Attachment: Company Tree.jpg Employee Profile.jpg > Employee names appear as "Null" in company tree. > > > Key: OFBIZ-10510 > URL: https://issues.apache.org/jira/browse/OFBIZ-10510 > Project: OFBiz > Issue Type: Bug > Components: humanres >Affects Versions: 16.11.04 >Reporter: Shantanu >Priority: Blocker > Labels: beginner, newbie, starter > Attachments: Company Tree.jpg, Employee Profile.jpg, Untitled.jpg > > > I've created a sample Internal Organisation called "New Department". > Made a position withing in called "New Postion". > Then created an Employee names "Adi Singh" and added him the "New Postion" > and Employed in "New Department" > But in the company tree the name of employee appears as Null. > Please help. > I've attached two images showing the issues. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10510) Employee names appear as "Null" in company tree.
[ https://issues.apache.org/jira/browse/OFBIZ-10510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shantanu updated OFBIZ-10510: - Attachment: (was: 2.jpg) > Employee names appear as "Null" in company tree. > > > Key: OFBIZ-10510 > URL: https://issues.apache.org/jira/browse/OFBIZ-10510 > Project: OFBiz > Issue Type: Bug > Components: humanres >Affects Versions: 16.11.04 >Reporter: Shantanu >Priority: Blocker > Labels: beginner, newbie, starter > Attachments: Company Tree.jpg, Employee Profile.jpg, Untitled.jpg > > > I've created a sample Internal Organisation called "New Department". > Made a position withing in called "New Postion". > Then created an Employee names "Adi Singh" and added him the "New Postion" > and Employed in "New Department" > But in the company tree the name of employee appears as Null. > Please help. > I've attached two images showing the issues. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (OFBIZ-10510) Employee names appear as "Null" in company tree.
Shantanu created OFBIZ-10510: Summary: Employee names appear as "Null" in company tree. Key: OFBIZ-10510 URL: https://issues.apache.org/jira/browse/OFBIZ-10510 Project: OFBiz Issue Type: Bug Components: humanres Affects Versions: 16.11.04 Reporter: Shantanu Attachments: 2.jpg, Untitled.jpg I've created a sample Internal Organisation called "New Department". Made a position withing in called "New Postion". Then created an Employee names "Adi Singh" and added him the "New Postion" and Employed in "New Department" But in the company tree the name of employee appears as Null. Please help. I've attached two images showing the issues. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (OFBIZ-10509) Disable DTDs for XML-RPC requests
[ https://issues.apache.org/jira/browse/OFBIZ-10509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taher Alkhateeb resolved OFBIZ-10509. - Resolution: Fixed implemented successfully and all DTDs are now rejected in any XML-RPC requests > Disable DTDs for XML-RPC requests > - > > Key: OFBIZ-10509 > URL: https://issues.apache.org/jira/browse/OFBIZ-10509 > Project: OFBiz > Issue Type: Improvement >Affects Versions: Release Branch 16.11, Upcoming Branch, Release Branch > 17.12 >Reporter: Taher Alkhateeb >Assignee: Taher Alkhateeb >Priority: Major > Fix For: Upcoming Branch, Release Branch 17.12, Release Branch > 16.11 > > > Disable all DTDs in XML-RPC by overriding the parsing code and enforcing > stricter settings on the XMLReader -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-6858) Solr logging doesn't work
[ https://issues.apache.org/jira/browse/OFBIZ-6858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16574549#comment-16574549 ] Shi Jinghai commented on OFBIZ-6858: As Solr 7.4 has been released in Jun 27, I'm checking whether this issue could be closed. Solr 7.4 includes NER/ERD, I'll test it if it works for OFBiz-7954 as well. > Solr logging doesn't work > - > > Key: OFBIZ-6858 > URL: https://issues.apache.org/jira/browse/OFBIZ-6858 > Project: OFBiz > Issue Type: Bug > Components: solr >Affects Versions: Trunk, Release Branch 15.12 >Reporter: Pierre Smits >Assignee: Shi Jinghai >Priority: Major > Attachments: Image2.png > > > When looking at the logging screen in demo-trunk > (https://demo-trunk-ofbiz.apache.org/solr/#/~logging) no logging results are > shown. Nor does https://demo-trunk-ofbiz.apache.org/solr/#/~logging/level > provide any insights. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10508) Remove checks to store only 250 characters of URL in VisitHandler.getVisit() & ServerHitBin.saveHit()
[
https://issues.apache.org/jira/browse/OFBIZ-10508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16574497#comment-16574497
]
Jacques Le Roux commented on OFBIZ-10508:
-
+1
> Remove checks to store only 250 characters of URL in VisitHandler.getVisit()
> & ServerHitBin.saveHit()
> -
>
> Key: OFBIZ-10508
> URL: https://issues.apache.org/jira/browse/OFBIZ-10508
> Project: OFBiz
> Issue Type: Improvement
> Components: framework
>Affects Versions: Trunk, Release Branch 17.12
>Reporter: Aditya Sharma
>Assignee: Aditya Sharma
>Priority: Major
>
> Found following checks to restrict "URL" fields for Visit and ServerHit
> entity:
> When storing ServerHit using ServerHitBin.saveHit() method
>
> {code:java}
> serverHit.set("requestUrl", fullRequestUrl.length() > 250 ?
> fullRequestUrl.substring(0, 250) : fullRequestUrl);
> String referrerUrl = request.getHeader("Referer") != null ?
> request.getHeader("Referer") : "";
> serverHit.set("referrerUrl", referrerUrl.length() > 250 ?
> referrerUrl.substring(0, 250) : referrerUrl);
> {code}
> When storing Visit using VisitHandler.getVisit() method
> {code:java}
> if (initialRequest != null) visit.set("initialRequest",
> initialRequest.length() > 250 ? initialRequest.substring(0, 250) :
> initialRequest);
> if (initialReferrer != null) visit.set("initialReferrer",
> initialReferrer.length() > 250 ? initialReferrer.substring(0, 250) :
> initialReferrer);
> if (initialUserAgent != null) visit.set("initialUserAgent",
> initialUserAgent.length() > 250 ? initialUserAgent.substring(0, 250) :
> initialUserAgent);
> {code}
> When the code was committed ( [https://markmail.org/message/fgatg5qyeaibxjxk]
> ) the "URL" field type had a size of 255 characters only which was later
> changed to 2000 characters ( [https://markmail.org/message/anfree2nkyk3imln]
> ).
> So, the above code logic to restrict no of characters can be removed now.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (OFBIZ-10509) Disable DTDs for XML-RPC requests
Taher Alkhateeb created OFBIZ-10509: --- Summary: Disable DTDs for XML-RPC requests Key: OFBIZ-10509 URL: https://issues.apache.org/jira/browse/OFBIZ-10509 Project: OFBiz Issue Type: Improvement Affects Versions: Release Branch 16.11, Upcoming Branch, Release Branch 17.12 Reporter: Taher Alkhateeb Assignee: Taher Alkhateeb Fix For: Upcoming Branch, Release Branch 17.12, Release Branch 16.11 Disable all DTDs in XML-RPC by overriding the parsing code and enforcing stricter settings on the XMLReader -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10438) Add method attribute to request-map to controll a uri can be called GET or POST only
[
https://issues.apache.org/jira/browse/OFBIZ-10438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16574379#comment-16574379
]
Mathieu Lirzin commented on OFBIZ-10438:
Hello [~taher],
Makes sense, please go ahead. :)
> Add method attribute to request-map to controll a uri can be called GET or
> POST only
>
>
> Key: OFBIZ-10438
> URL: https://issues.apache.org/jira/browse/OFBIZ-10438
> Project: OFBiz
> Issue Type: Improvement
> Components: framework
>Affects Versions: Trunk
>Reporter: Shi Jinghai
>Assignee: Shi Jinghai
>Priority: Minor
> Attachments:
> OFBIZ-10438_0001-Add-optional-method-attribute-in-request.patch,
> OFBIZ-10438_0002-Parse-controller-config-in-one-place.patch,
> OFBIZ-10438_0003-Handle-multiple-request-methods.patch
>
>
> As discussed in OFBIZ-4274, OFBiz runs doGet method in ControlServlet no
> matter what request it is.
> I like Mathieu's comment on adding a method attribute to the request-map
> element, it's almost the same as we implemented in our openapi:
>
> {code:java}
>
>
>
>
>
>
> {code}
> The difference is that we DON'T support method list expression:
> {code:java}
> ...
> {code}
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OFBIZ-10438) Add method attribute to request-map to controll a uri can be called GET or POST only
[
https://issues.apache.org/jira/browse/OFBIZ-10438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16574373#comment-16574373
]
Taher Alkhateeb commented on OFBIZ-10438:
-
Hi Mathieu,
The thread you mentioned does not explain the proposal, and jumps directly to
the patches. I think we need to discuss the strategy and direction of what
we're trying to achieve, and let the community decide, then we can discuss the
technical details here after we agree on the general direction.
If you are in agreement then I will start the thread.
> Add method attribute to request-map to controll a uri can be called GET or
> POST only
>
>
> Key: OFBIZ-10438
> URL: https://issues.apache.org/jira/browse/OFBIZ-10438
> Project: OFBiz
> Issue Type: Improvement
> Components: framework
>Affects Versions: Trunk
>Reporter: Shi Jinghai
>Assignee: Shi Jinghai
>Priority: Minor
> Attachments:
> OFBIZ-10438_0001-Add-optional-method-attribute-in-request.patch,
> OFBIZ-10438_0002-Parse-controller-config-in-one-place.patch,
> OFBIZ-10438_0003-Handle-multiple-request-methods.patch
>
>
> As discussed in OFBIZ-4274, OFBiz runs doGet method in ControlServlet no
> matter what request it is.
> I like Mathieu's comment on adding a method attribute to the request-map
> element, it's almost the same as we implemented in our openapi:
>
> {code:java}
>
>
>
>
>
>
> {code}
> The difference is that we DON'T support method list expression:
> {code:java}
> ...
> {code}
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OFBIZ-10438) Add method attribute to request-map to controll a uri can be called GET or POST only
[
https://issues.apache.org/jira/browse/OFBIZ-10438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16574370#comment-16574370
]
Shi Jinghai commented on OFBIZ-10438:
-
Forgot to say, I use postman plugin in chrome to request the
https://localhost:8443/webtools/control/ping.
> Add method attribute to request-map to controll a uri can be called GET or
> POST only
>
>
> Key: OFBIZ-10438
> URL: https://issues.apache.org/jira/browse/OFBIZ-10438
> Project: OFBiz
> Issue Type: Improvement
> Components: framework
>Affects Versions: Trunk
>Reporter: Shi Jinghai
>Assignee: Shi Jinghai
>Priority: Minor
> Attachments:
> OFBIZ-10438_0001-Add-optional-method-attribute-in-request.patch,
> OFBIZ-10438_0002-Parse-controller-config-in-one-place.patch,
> OFBIZ-10438_0003-Handle-multiple-request-methods.patch
>
>
> As discussed in OFBIZ-4274, OFBiz runs doGet method in ControlServlet no
> matter what request it is.
> I like Mathieu's comment on adding a method attribute to the request-map
> element, it's almost the same as we implemented in our openapi:
>
> {code:java}
>
>
>
>
>
>
> {code}
> The difference is that we DON'T support method list expression:
> {code:java}
> ...
> {code}
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
